Highly unlikely the fix will apply to JBoss MQ.
Please can you post in the JBoss MQ forum.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3948941#3948941
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3948941
_
Hi there,
We have similar "read timed out" problem with JBoss MQ (4.0.3sp1 and 4.0.4.GA),
instead of JBoss Messaging. Could JBoss experts here advice if the fix is
applicable to JBoss MQ as well?
Regards/Brian
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3
It seems that Remoting behavior changed recently.
I am following up on this on the Remoting forum
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3941996#3941996
Until this is clarified, I changed Messaging to conform to the new Remoting
behavior, and added a test to detect such change
It's a bug. Thanks for reporting it. Use this to track it:
http://jira.jboss.org/jira/browse/JBMESSAGING-371
Will be fixed in 1.0.1.CR2.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3941641#3941641
Reply to the post :
http://www.jboss.com/index.html?module
The following are two classes, SimpleTopicListener, and SimpleTopicSender. Here
is what I did:
(1) Installed JBoss 4.0.3 SP1 and JBoss Messaging 1.0.0.GA with the standard
process.
(2) Start JBoss with "run -c messaging" command.
(3) Start the SimpleTopicListener class from the same computer.
(4
I haven't seen this behavior yet.
Could you write a simple test case (for an example, look at
org.jboss.test.messaging.jms.JMSTest) that I can use to reproduce it?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3941013#3941013
Reply to the post :
http://www.j
