also there are 2 other queue that JBoss provides by default : DLQ and ExpireyQueue.
When I push one message to my own configured queue[SIClusterQueue] and is of the type javax.jms.Message, My Receiver is able to receive that message and everything is fine.
But now the problem is, when my sender puts the customized message object to queue[SIClusterQueue], i.e not of the type javax.jms.Message, but my own object - which implements serializable interface. following occurs.
Sender is able to send message to Queue, this time message is not visible under my configured queue[SIClusterQueue], instead its available under JBOSS default DLQ [as shown in attached screenshot from JBOSS Admin Page].
I can confirm that both my sender and receiver are referring to my configured queue [SIClusterQueue], not to the default DLQ. and there is no Exception while sending/receiving the Message in any case.
My onMessage Method logic in receiver is as follow. where MessgeEvent Object is my own customized object.
Following is the sender code which shows how it packed my customizedObject[MessageEvent].
can someone please help here and share your expertise.
Why my JMS Queue messege is redirected to default DLQ, it should redirect to my own configured Queue to which my consumers are listen to.
Mehul Kaps Kapadia
Joined: Mar 01, 2012
I got the solution, so thought to share with you all.
In first try I have created the JMS Queue from backend, means - I directly kept the MyQueue-service.xml file in <JBOSS_HOME>/server/default/deploy/ directory. in which queue xml config doesn't have the JNDI config.
then I tried creating from the JBOSS Admin Console in following way, and it worked perferctly fine.
JMS Destination > Queue > Add new Resource
provide required details and your queue is ready to go.
Queue Service XML file:
subject: JBoss JMS Queue Message not reached to configured queue, but its wrongly redirected to default DLQ.