This works on my machine. I am running 3.0.2 as well but I have jvm 1.4.1 installed... Does your message producer set the individual messages to non-persistant, I believe this overrides system and queue settings?
Thanks for your quick reply. I installed 1.4.1, and that didn't seem to make a difference. I'm not explicitly setting any non-persist attribute on the message. The message is getting persisted, for I see the files created on the filesystem. They are even there after a restart. For whatever reason, the JBossMQ doesn't pick them up. In fact, that directory just starts to fill up with old messages.
Do you know of any specific debug that I might look for? I'm sure this works, I'd just like it to work for me. :)
My queue names had '/' characters in it. It wasn't getting translated correctly in all places. After s/\//\./ I was OK, and my queues began to work after restarts.
I am just getting started with JbossMQ myself. I sent you email that contained my jboss-service.xml and my destinations.xml as well. As you can see it really is just the stock example config from the all server.
If you would like I can send you my jms client source that simply posts a text message containing the string "test message" 10000 times to the example queue testQueue.
Now I am checking queuedepth from the jmx-console under jboss.mq or somewhere like that you can see the list of destination queues. I dont remember seeing qdepth in JNDIView.
Also I did a graceful shutdown via the same JNDIView I havent done any sort of testing persistance through a crash or anything like that, but in my system they come back up fine. And if I deploy my simple consumer MDB after I do the restart it kicks off and goes to the task of processing the messages so I am definately sure that they are there.