This content has been marked as final.
Show 3 replies
-
1. Re: DurableSubscriber
adrian.brock Jun 15, 2007 10:55 AM (in response to jp_ammu)This just looks like you are doing it wrong - an anti-pattern.
Session beans can "vanish at anytime" and are certainly not the place
to establish long lived jms connections for receiving. That is what MDBs are for. -
2. Re: DurableSubscriber
jp_ammu Jun 15, 2007 2:28 PM (in response to jp_ammu)Hi Adrian,
Yes you are right. We were not able to configure RemoteTopic ( to Sun eGate eWays JMS server) from the MDB residing on JBOSS. I haven't seen much info in configuring the remote invokes from JBOSS.Hence we used Session bean to directly calling the remote topics.
Even if able to configure the MDB succesfully, i still have DurableSubscriber() with same subscription name. My application( after restart) will get the duplicate subscription name exception and can't proceed further. -
3. Re: DurableSubscriber
adrian.brock Jun 18, 2007 10:07 AM (in response to jp_ammu)"jp_ammu" wrote:
Even if able to configure the MDB succesfully, i still have DurableSubscriber() with same subscription name. My application( after restart) will get the duplicate subscription name exception and can't proceed further.
???? Restarting an MDB will close the previous connection so the client id/subscritpion name
will not be a duplicate. The MDB uses only one connection with many sessions.