Hi All, 

I posted the following issue on Jboss Messaging earlier. Am I in right place 
this time??? :)

For now I am running single jBoss 4.2.3GA (which is going to be part of a jBoss 
cluster). I want to test the JMS FailOver. I am using two Queues called 'Queue' 
where my browser will put message and MDB will post it to my remote app server 
let say port '20005' using Resource Adaptor and 'ReplyQueue' from where 
response will be fetched and give it back to browser. 

Now I have stoped my app server on 20005 and started back on 20003. In the 
meantime I have deployed one more MDB called MDB-DLQ which will get activated 
when default DLQ will recieve message when my first MDB should get failed to 
post message. 

I have check the jBoss console and it shows that my Queue depth is '1' but 
after failure message is not re-directed to defaul jBoss DLQ (DLQ depth= 0) 
where my other MDB is waiting??? 

My configuartions are... 

destinations-service.xml 


  | <?xml version="1.0" encoding="UTF-8"?>
  | 
  | <!-- $Id: jbossmq-destinations-service.xml 25907 2004-11-16 04:32:39Z ejort 
$ -->
  | 
  | <!-- 
  |    | This file defines the default Queues and Topics that JBossMQ
  |    | ships with.  The default Queues and Topics are used by the 
  |    | JBoss test suite and by the sample jms programs.
  |    |
  |    | You can add other destinations to this file, or you can create other
  |    | *-service.xml files to contain your application's destinations.
  |  -->
  | 
  | <server>
  |   <!-- Destination without a configured SecurityManager or without a 
  |        a SecurityConf will default to role guest with read=true, write=true,
  |        create=false.
  |   -->
  |   <mbean code="org.jboss.mq.server.jmx.Queue"
  |      name="jboss.mq.destination:service=Queue,name=Queue">
  |     <depends 
optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
  |   </mbean>
  |   <mbean code="org.jboss.mq.server.jmx.Queue"
  |      name="jboss.mq.destination:service=Queue,name=ReplyQueue">
  |     <depends 
optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
  |   </mbean>
  |   </server> 
  | 

For More Info: there is default DLQ present when I start my jBoss using 
following command with above custom queues.

run.bat -b 0.0.0.0 -c all

Note: -c all --> because I am going to start my other instance when I am going 
to finish testing this one to make it cluster.

Any help and suggestions will be appreciated :)

Regards,

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244087#4244087

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244087
_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to