Daniel Dumitrescu [
http://community.jboss.org/people/danezu] created the discussion
"JBM clients hangs when creating connections/sessions"
To view the discussion, visit:
http://community.jboss.org/message/644597#644597
--------------------------------------------------------------
Hello guys
We're facing a problem with JMS remote clients hanging like forever when trying to
create connections/sessions on a JBoss Messaging 1.4.5.SP1 on JBoss 4.2.3 GA
The setup is the following:
- JBoss Servers:
# 3 JBoss 4.2.3 GA set up in cluster, with the same multi-cast IP address and partition
name
# JBoss Messaging 1.4.5 SP1 installed on each one of them, with one queue and 5 topics,
all clustered and with durable subscriptions
# MySQL 5.5.9 as persistence layer for JBM
# persisten messages needed, no message should be ever lost
- remote clients
# simple clients that looks up for {code}XAConnectionFactory{code}, and send every 30 secs
more than one message, every time with JNDI lookup, create connection & session (all
are closed in the finally clause). One addition: on the client side is made XA resource
enlisting with the remote target queue and the transaction is managed by hand on both
client and JBM side.
The load from the client side to the server is not so high, like 10,000 - 20,000 messages
per day, but after 8-10 days the cluster gets unresponsive to new JMS remote connections,
and the clinet threads are hanging. The local message processing, i.e. on each node on the
topics works, which led me to the fact that can be a problem with JBoss Remoting
The client threads are locking in this point:
{code}
Thread: JMS SessionPool Worker-0 : priority:5, demon:true, threadId:228,
threadState:RUNNABLE, lockName:null
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:129)
java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
java.io.BufferedInputStream.read(BufferedInputStream.java:237)
java.io.FilterInputStream.read(FilterInputStream.java:66)
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1077)
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:682)
org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:458)
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:141)
org.jboss.remoting.Client.invoke(Client.java:1925)
org.jboss.remoting.Client.invoke(Client.java:786)
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:178)
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:80)
org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
org.jboss.jms.client.JBossConnectionFactory.createXAQueueConnection(JBossConnectionFactory.java:142)
{code}
Have anyone encountered this behavior?
Regards,
Daniel
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/644597#644597]
Start a new discussion in JBoss Messaging at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]