Hi,
my simple_chat.jsp work with ActiveMQ JMS.if this run in windows,there is no problem.(means:when send a message to a topic such as chatCannel,the simple_chat can Subscribe the message immediately),but when i let this sample to run in linux ,a problem come out.
the problem is:when i send a message,the simple_chat can Subscribe the message after 3 seconds. it's too slow to Subscribe that no one can accept it.
does this matter with smartclient or we do need to modify any config files?
thank in advance.
joy_cz
this is the running environment:
CentOS 5.0, Tomcat 5.5.23, ActiveMQ 4.1.1
Hi joy_cz,
This is probably an ActiveMQ issue or other issue with your server. We actually run the Messaging server on Tomcat/CentOS at Isomorphic HQ, and we don’t see the delays you describe.
Hi Isomorphic,
does the smartclient's messaging need to via the tomcat to send or subscribe message?
i have do some test on activeMQ, and i can’t find the thing that i describe before.
we have a MQ server pc1 and a web application server pc2 which is tomcat and smartclient running on(these two server's os is CentOS).if the server pc2's os is CentOS the delays i had describe will come out,but if its os is window ,the delays problem does't exist. the server pc1's os is CentOS always.
thanks in advance.
joy_cz
Hello Joy,
We did understand the deployment environment when you described it the first time. As we explained, at Isomorphic HQ we run the Messaging module against a CentOS/Tomcat server and there are no delays.
So, it seems this is a problem with ActiveMQ or a problem with your linux server, not a problem with SmartClient. If you find something that seems to indicate this is a SmartClient problem, please let us know.
Hello Isomorphic,
i was solved the problem.just modify the value of messaging.keepaliveInterval in
the config file of server.properties.the init value of it is 3000,if i change it to below 1000,so we can’t feel any delay while chating. this maybe the value of messaging.keepaliveInterval is different between window and centOS.
Joy
Hi Joy,
Just for future reference, that seems to indicate that something in your Tomcat or perhaps Apache config (if you’re using Apache) is causing messages to be buffered and not sent immediately. The SmartClient keepAlive message then presumably fills this buffer so that the message is actually sent.
So, you may want to try to resolve the underlying problem in the future, as you have configured SmartClient to send keepAlives more often than necessary, which wastes bandwidth.
This doesn’t happen in Jetty.