-
1. Re: MDB and Durable subscriptions
pra Dec 6, 2001 3:06 AM (in response to chewitty)jboss-state: client id must be defined here.
Pooling: there is only one connection and one consumer, so no problem here. Its the sessions and beans that are pooled (the real gain is that you may have multithreaded topics which is not possible on strait JMS).
//Peter -
2. Re: MDB and Durable subscriptions
chewitty Dec 6, 2001 5:53 AM (in response to chewitty)Hi Peter,
I am sorry, I am not with you here. How do you do that - I have not seen any config file called "jboss-state" and how to configure this.
Would you mind to elaborate please.
Regards,
Ferdinand -
3. Re: MDB and Durable subscriptions
pra Dec 6, 2001 12:27 PM (in response to chewitty)Should have been jbossmq-state, but I do not know anything more about this stuff than I have covered in the chapter (MDB:s I know more about, since I wrote that container). Sorry.
//Peter -
4. Re: MDB and Durable subscriptions
chewitty Dec 7, 2001 3:11 AM (in response to chewitty)Hi,
I have spotted my own errors. I had omitted the corresponding entries in the jboss.xml file which would have associated the user/password for the MDB with the corresponding topic.
So the correct entry in y jboss.xml to match the entries in the jbossmq-state.xml should have been:
jboss.xml:
<message-driven>
<ejb-name>OrderValidationMDB</ejb-name>
<configuration-name>Standard Message Driven Bean</configuration-name>
<destination-jndi-name>topic/IncomingOrdersTopic</destination-jndi-name>
<mdb-user>someOtheruser</mdb-user>
<mdb-passwd>someOtherpasswd</mdb-passwd>
<mdb-client-id>OrderValidationMDB</mdb-client-id>
</message-driven>
To match: (jbossmq-state.xml)
someOtheruser
someOtherpasswd
OrderValidationMDB
OrderValidationMDB
IncomingOrdersTopic
Thanks for your help Peter.
Regards,
Ferdinand