This sounds similar to part of my experience just posted in a message entitled 'Has anyone used Session.recover() ?' I hope someone answers one of us...
This sound like and old bug that is fixed in the 3.0 line (had to be fixed to get DLQ to work). I also have some vauge recollection of that it is possible to fix by changing the PM to:
I had a similiar problem. Set the maximum-size parm to 1 in the jboss.jcml and it should sort out the problem.
Hi I am having similar troubles,
but which maximum-size parameter should I set? I have no such a parameter, but I have quite a lot MaxSize parameters. So what should I set to 1?
I'm getting the same problem as the others:
This is what I see currently in my jboss.jcml
So changing code to "org.jboss.mq.pm.PersistenceManager" will fix this?
The only section in jboss.jcml that looks related to JMS and has a MaxSize parameter is the JMS XA Resource Adapter mbean definition. Is this what should be changed?
I would like to ask if there is someone who really make the JMS working?
I would like to use durable subscription with topic and CLIENT_ACK. I am accessing the JMS for external app (not running as a EJB) and the JBoss is v2.4.3.
I have set the PM to file and MaxSize in JMS XA Resource Adapter mbean definition to 1. But still I need to restart the JBoss to receive unACKed messages.
Could anyone provide me jboss.jcml file which makes JMS working?
I will greatly appreciate any help.
btw. does anyone know how to unsubscribe from the durable subscription? I always got just an exception when I try it.