Tim,
Thanks for attempting and succesfully reproducing. I have been away from the
net for awhile with heath issues. I was able to figure out what was happening.
I was attempting to re-subscribe with the same clientID (not subscription ID),
and it was taking awhile for the jboss server to tim
Ok I fixed this.
The problem here was not that the message was getting lost (it wasn't) - if you
restart the server the "lost" message re-appears. That would be spec compliant
- but annoying.
So I've changed it so that if a client dies then it's outstanding deliveries
get cancelled and redeliv
Ok I have replicated this - a fix should be on it's way soon...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952719#3952719
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952719
Using Tomcat but need to do more? Need
Hi-
I was wondering if you are still seeing this problem?
We are going to cut a release fairly soon, so if there is an issue here we want
to get a fix in ASAP
Thanks for your patience.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952602#3952602
Reply to
Just to clarify:
You have 3 consumers in different VMs consuming using durable subscriptions, a
producer in another VM and a server in another VM, they are all on different
physical nodes.
You start them up and then kill one of the consumers.
You then send 10 messages.
The 2 remaining consume
Whoops- forgot to mention the version of messaging- using
jboss-messaging-1.0.1.CR2
/DPF
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951130#3951130
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951130
__
