[JBoss Messaging] - "Connection failure has been detected" message
by nbhatia
I am having trouble receiving messages reliably using JBM 2.0.0.BETA3 deployed in JBoss AS 5. Every once in a while I am getting a "Connection failure has been detected" message and then I start loosing messages. Can someone help me identify the issue?
I have simplified my web application down to the bare bones. At this point I can send 1000 messages as fast as I can and then see if I receive all of them. Few times I have gotten all 1000, but several times I get much less, say about 600. I get the following warnings in between:
| 22:58:26.968 WARNING [Thread-44 (group:JBM-client-global-threads-27401341)] [org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl] Connection failure has been detected Did not receive ping from server:3
| ...
| 23:02:56.984 WARNING [Thread-3 (group:JBM-scheduled-threads-10153586)] [org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl] Connection failure has been detected Did not receive ping from client. It is likely a client has exited or crashed without closing its connection, or the network between the server and client has failed. The connection will now be closed.:3
| 23:02:56.984 WARNING [Thread-3 (group:JBM-scheduled-threads-10153586)] [org.jboss.messaging.core.server.impl.ServerSessionImpl] Client connection failed, clearing up resources for session ceb2cc8d-69d8-11de-9025-0016d433fcb5
| 23:02:57.000 WARNING [Thread-3 (group:JBM-scheduled-threads-10153586)] [org.jboss.messaging.core.server.impl.ServerSessionImpl] Cleared up resources for session ceb2cc8d-69d8-11de-9025-0016d433fcb5
|
The message listener code is as simple as this:
| @MessageDriven(activationConfig={
| @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),
| @ActivationConfigProperty(propertyName="destination", propertyValue="queue/jmstest")
| })
| public class TestMessageListener implements MessageListener {
|
| private static final Logger logger =
| LoggerFactory.getLogger(TestMessageListener.class);
|
| @Override
| public void onMessage(Message message) {
|
| if (message instanceof TextMessage) {
| String messageText = null;
| try {
| messageText = ((TextMessage)message).getText();
| logger.debug("Received message: {}", messageText);
| }
| catch (JMSException e) {
| throw new RuntimeException(e);
| }
| }
| }
| }
|
I can send my small Maven project if someone could try it out.
Thanks.
Naresh
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241878#4241878
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241878
16 years, 9 months
[Clustering/JBoss] - SSO fails on compressed response
by ozguy
I am using Jboss 4.2.3 with jboss portal 2.7.2
Running 2 jboss nodes in a cluster, everything works as expected including SSO , session replication etc.
Onces i enable compression on the Tomcat Http connector or even on our load balancer , SSO no loger works.
Scenario ( with compression="on" on tomcat connector )
1. start both server nodes
2. run web page that requires authentication
3. user authenticated by node 1 ( SSO replicated to the node2 correctly)
3. shut down node 1 ( this was the node that originally authenticated the user)
4. run the page again, node 2 pops up authentication dialog
(only the authentication part is having problems when compression is on, every other session object associated with the page seems to work as after re-entrying authentication details, i do see the updated session values that i was expecting.)
Is there anything special needs to be done so that SSO works properly when running compression="on" in tomcat.
Thanks in advance.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241877#4241877
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241877
16 years, 9 months
jndi service take too much time to response
by Sam Wun
Hi,
I have built the sample stateless application Calculator in JBOSS EJB3
tutorial. The Calculator and JBOSS is installed in another machine
192.168.1.242; whereby I execute "ant run" in another machine
192.168.1.235. But it takes about more 1 minute to show up the result
from the command "ant run".
The property of the jndi.properties file is shown below:
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=192.168.1.242
The 192.168.1.242 and 192.168.1.235 systems has no internet access. I
don't know whether I need a DNS server setup for that?
Thanks
16 years, 9 months
