I just reread the postings I linked and it seems that temporary queues just don't work. Is this assertion correct? I'd really hate for all the clients to share a server based queue, since this doesn't seem to make sense for my purpose.
Just verified, my code works as expected in the J2EE RI 1.3.1!
The reason I used JBoss 3.0.6 is that 3.2.1 informs me that DefaultJMSProvider is not bound despite the fact that it is within the XML file. I couldn't get deployment to work on JBoss 4.0 alpha, it throws many exceptions on startup and deployment fails. I have no idea why. Anyway I can't use a none production version since our deadline isn't far off and we can't afford tying it to a JBoss release.
Again, after further investigation I found a test case for QueueRequestor which I guess runs correctly (otherwise a release wouldn't be made, right?). Anyway it seems to be flawed since it uses the same connection and session etc... to send and receive messages within the same VM. While this might test something, my problem is with two separate VM's and with (obviously) different instances of these members.
For 3.2.1 you need to set RecursiveSearch to true
For temporary queues, there was a bug in there
in previous versions. It should work with the latest
I would recommend writing your version of the QueueRequestor
that has a timeout if you don't want it to hang forever.