confirmed. I had left the jboss.xml file out of the ear file. when I included
it (and re-added the JNDIName attribute to the jbossmq-destinations-service.xml
file) it worked as expected.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153093#4153093
Reply t
pretty sure I found the problem (can't verify for a bit but wanted to put this
here before I forget) I think the problem is that I neglected to put the
jboss.xml file in my ear file :( I found that my build script was sending it
somewhere other than the ear file will try to confirm in t
note the poor copy-paste results the code section of previous post... i
included the closing mbean tag from the previous element...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150154#4150154
Reply to the post :
http://www.jboss.com/index.html?module=bb&o
well... i deleted the contents of the file related to that queue b/c it wasn't
working... but this is what I'm pretty sure I had:
|
|
| jboss.mq:service=DestinationManager
| jms/OrderQueue
|
|
btw: the file in which I put this block is
$JBOSS_INSTALL\server\def
I had correctly set up the queue correctly using the JNDIName attribute - and
after starting JBoss the queue showed up in the Administration console as
expected so I'm confident my queue was set up correctly.
The link below indicates that this (MDB deployer not "seeing" the destination
queu
got this thing working - looks like a bug in the JBoss MDB deployer code...
basically the deployer was not paying any attention to the
destination-jndi-name that I provided for the EJB in the jboss.xml file.
Instead, it would see that I'm deploying SQMessageHandler, realize that there
was no q
ok... the tail end of that post was a bit confusing: when deploying my app,
JBoss sees my MDB and creates BOTH a JNDI name for it (queue/SQMessageHandler)
AND a Queue (named SQMessageHandler, referenced by JNDI
queue/SQMessageHandler)
hopefully that's clearer
View the original post :
htt
Still battling with this issue I downloaded the sample MDB code provided
by JBoss and successfully deployed and ran it - it works as expected.
Naturally I've compared the configuration of the two applications and made them
the same where I could - one difference is that my MDB has a select
JBoss 4.2.2
EJB 2.1
I have an MDB configured to process messages off of a given queue but it
doesn't seem to realize that messages are accumulating in the queue it's
like it doesn't even see the queue.
ejb-jar snippet:
SQMessageHandler
com.scott.messaging.MessageHandlerEJB
javax.jms.Messag
