Nothing stands out. This is probably a misconfiguration on your side. You should validate your XML document against the DTD just to make sure JBoss isn't mis-parsing your file.
JBoss 3.2.3 doesn't have fixes related to anything like this, but it doesn't hurt to upgrade.
Thanks for the reply.
Unfortunately, my jboss.xml file validates successfully against the 3.2 DTD.
I guess I'll have to play around a bit more with it. I'll post again once I find out more.
As the rest of my project's subsystems are being developed for JBoss 3.2.0, I have retried my MDB on 3.2.0, with the same negative results.
I've even tried changing the name of the queue (to apex-DVInbox), just in case JBoss didn't like the original name. Here's some log snippets:
13:47:01,125 INFO [apex-DVInbox] Creating
13:47:01,125 INFO [apex-DVInbox] Created
13:47:01,484 INFO [apex-DVInbox] Starting
13:47:01,484 INFO [apex-DVInbox] Bound to JNDI name: queue/apex-DVInbox
13:47:01,484 INFO [apex-DVInbox] Started
13:47:01,484 INFO [SecurityManager] Starting
13:47:01,765 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
13:47:01,781 INFO [EJBDeployer] looking for nested deployments in : file:/C:/jb
13:47:02,031 INFO [EjbModule] Creating
13:47:02,046 INFO [EjbModule] Deploying DocumentVerifierBean
13:47:02,125 INFO [MessageDrivenContainer] Creating
13:47:02,125 INFO [MessageDrivenInstancePool] Creating
13:47:02,125 INFO [MessageDrivenInstancePool] Created
13:47:02,125 INFO [JMSContainerInvoker] Creating
13:47:02,140 INFO [JMSContainerInvoker] Created
13:47:02,140 INFO [MessageDrivenContainer] Created
13:47:02,140 INFO [EjbModule] Created
13:47:02,140 INFO [EjbModule] Starting
13:47:02,140 INFO [MessageDrivenContainer] Starting
13:47:02,140 INFO [JMSContainerInvoker] Starting
13:47:02,140 INFO [DLQHandler] Creating
13:47:02,203 INFO [DLQHandler] Created
13:47:02,203 WARN [JMSContainerInvoker] destination not found: queue/DocumentVerifierBean reason: javax.naming.NameNotFoundException: DocumentVerifierBean not bound
13:47:02,203 WARN [JMSContainerInvoker] creating a new temporary destination: queue/DocumentVerifierBean
13:47:02,218 INFO [DocumentVerifierBean] Creating
13:47:02,218 INFO [DocumentVerifierBean] Created
13:47:02,218 INFO [DocumentVerifierBean] Starting
13:47:02,218 INFO [DocumentVerifierBean] Bound to JNDI name: queue/DocumentVerifierBean
It looks to me that the 'apex-DVInbox' queue is being created and bound before the temporary 'DocumentVerifierBean' queue is created, so that's not the problem.
Please, does anyone have any more insights?
I've looked at plenty of examples. My jboss.xml validates. I've even used MDBs in JBoss before (v3.0.x) and I don't remember having this problem.
-Matthew S. Ring
This was fixed in the 3.2.1
The MDB no longer assumes all queues are directly in the queue/ namespace