Ben - can you add a bug report in JIRA?
BTW 1.2 will be out very soon which will have real transparent failover and
clustering.
1.0 is really only intended as a single server installation - but it's
obviously a plus if you can get it to work with more than one server.
View the original post :
After some re-testing of this issue I can confirm it is still present.
I've developed a new test case that creates a message producer and consumer on
two separate JBoss Messaging servers. By continually shutting down and
restarting each JBoss Messaging server I can eventually cause the shutting
Can one of the developers please tell me if the change discussed here was
eventually backported to the 1.x branch? e.g. is it in 1.0.1.SP4?
It would be nice to have to ability to programatically dispatch to more than
one JBoss Messaging server.
Thanks,
Ben
View the original post :
I have made the changes suggested and patched them into my 1.0.1.GA deployment.
The classes that I needed to change were:
| org.jboss.jms.client.container.ConsumerAspect
| org.jboss.jms.client.remoting.CallbackManager
| org.jboss.jms.server.endpoint.ClientDelivery
|
Assuming the problem is related to what I suspect then it's a fairly simple fix.
Have a look at the differences in the class
org.jboss.jms.client.remoting.CallbackManager between the 1.0 branch and TRUNK.
Basically the version in trunk also uses the server id in the key - this is
what you want
Also would need to change the ClientDelivery class to pass the server id
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3984835#3984835
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3984835
Thanks Tim. Will have a look at patching those classes in on Monday and
re-testing. Is there any configuration option that will make the exception
listeners fire faster in the case of a failed connection?
View the original post :
anonymous wrote : If you uncomment the code to try and close the session and
connection, then the sending of messages to the second server doesn't work at
all, with the same Object with oid was not found in the Dispatcher error
mentioned previously. On the server, the following entry is logged:
Anyway... your example here is kind of confusing IMHO... you are opening the
connection out of the loop, and closing it within the loop.
Are you sure you don't have a coding problem within your example?
I have tried two conenctions from the same client (as I'm coding HA support)
and never had
I have a feeling I might know what the problem is (not 100%)
In 1.0.x the callbackservers are keyed only on the consumer id, which is
created on the server from a sequence that starts from zero on startup.
So, if you have more than one server you can have more than one consumer with
the same
Ah... ok... Im using trunk. That's why I didn't see any problems
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3984592#3984592
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3984592
The uncommenting that I was talking about referred to the code in my example
that is currently commented out for when any exception is caught on sending a
message on connection1. I was attempting to see if cleaning up (i.e. trying to
close) the defunct connection on an exception affected the
anonymous wrote : Is there any chance of getting the fix that Tim is talking
about into a 1.0.x release? We are hoping to offer JBoss Messaging support as
part of our application, but with this problem we cannot as we need some form
of high availability. Was it a relatively confined change that
I just ran another test in which our application connected to a single JBoss
Messaging server 10 times, before then introducing the second server. I
thought this would get the sequence number that Tim mentioned out of step
between the two servers. Sure enough, if I stop the first server our
Can you replicate this in a simple test case and send it to us?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3984097#3984097
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3984097
Simple test class is attached below. It basically sends messages to one server
until it gets an exception, at which point it starts sending them to a second
server.
I am running this test case on the server1 (localhost) machine. I run it and
leave it for a few minutes sending messages to the
I have tried Clebert's suggestion mentioned in the other post of changing the
server id in messaging-server.xml:
| constructor
| !-- ServerPeerID --
| arg type=java.lang.String value=server.0 /
| !-- DefaultQueueJNDIContext --
| arg type=java.lang.String value=/queue
Also, we are running 1.0.1.GA on JBoss 4.0.4.GA deployed as
standalone-messaging.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3984009#3984009
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3984009
18 matches
Mail list logo
