To make durable subscriptions work properly,
you need to supply a user id and subscription name.
Otherwise, you will see subscriptions with
anonymous users like ID:4 in jbossmq-state.xml
Which don't work across redeployments.
However since you are getting some messages,
your problem is elsewhere. Do you see the same
problem with JBoss 3.0.8?
Thanks much for the reply...
I will try with 3.0.8 or 3.2.1 and see what happens...
Also, will use a userid in the jboss.xml for these
MDB's before I go ahead and try with 3.0.8 and
3.2.1...will let you know if that fixed the problem...
One quick question though...when I use the
rolling persistence, even when the beans are
deployed, mesgs are being persisted, not consumed by the MDB's...do you think that's because I am not using the userid in the deplyoment descriptor? only when I use file persistence, mesgs are being consumed.
I'm not familiar with the rolling logged pm.
File is the default in 3.0
JDBC2 in 3.2
I was able to get the problem resolved after using the userid in the deployment descriptor for both the
MDB's. Now, Durable Subscriptions work!!!
Thanks much for all your help...
Rolling Logged PM is something I came across after
looking at a thread here, regarding persistence...I
believe it would help roll over the messages every
day...for your info...the thread is,
http://www.jboss.org/modules/bb/index.html?module=bb&op=viewtopic&t= much again...for all your help.