I recently upgraded to JBM 1.4.0.CR3/Remoting 2.2.2.SP1, and all appears to
work fine.
However, I noticed that if you accidently try to connect a client to the JBM
server using an incorrect client remoting library, then all future client
createConnection calls will hang (even with the correct
bob_walker99 wrote : Hi,
| I've been seeing this for a while and alsways put it down to classpath
issues, but I'm quite an expert at which jboss client jars work and which
don't, and what needs to go where, so I'm no longer convinced that this is the
issue.
|
With JBM 1.4 the jars are
Updating to JBM 1.4.0.CR2/Remoting 2.2.0GA appears to have resolved this issue
for me.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4085205#4085205
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4085205
Thanks Clebert, I've mailed you the thead dumps.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4084376#4084376
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4084376
___
jboss-user
I am in the process of migrating from from JBoss MQ to JBoss Messaging, and
have a scenario that will consistently hang createTopicConnection with a
similar stack trace, although with JBoss AS 4.2.1GA/JBoss Messaging 1.3.0GA.
Clebert, I will mail client/server thread dumps as additional input.
I would need a thread dump on client/server to verify...
Trace logs would also help!
Clebert
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4084174#4084174
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4084174
