SV: MDB in orion 1.5.2 using Queue
Hi. 1) In 1.5.3 Orion will tell you if you havent implemented MessageDrivenBean and MessageListener in your MDB. 2) Orion will use the default JMS resource if you dont specify a destination-location etc in orion-ejb-jar.xml. ResourceProviders, made public in 1.5.2, lets you use 3rd party resources in a very simple way. A document on this issue is in progress and will be released shortly, with examples, samples and details. A MDB document is also in progress, but other documents have higher prio right now. WR -Ursprungligt meddelande- Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]För Romen Law Skickat: den 19 oktober 2001 03:39 Till: Orion-Interest Ämne: RE: MDB in orion 1.5.2 using Queue ello, Thanks for all the replies. I must apologise: my MDB using Queue was working all along. It's just that I was using System.out.println() for logging so I couldn't see it on the console. But after using log4j I could see it. Well, there is first time for everything. I did find two things though: 1. someone posted before saying that in Orion you should not make MDB implement MessageListener, otherwise it will not work. I found that to be false. 2. I still do need to modify the destination-location in orion-ejb-jar.xml. If I don't it still works provided that I only have one Queue or Topic defined in jms.xml. Orion seems to use that one disregarding the queue name you specify in the sender. cheers romen
RE: MDB in orion 1.5.2 using Queue
On Fri, 2001-10-19 at 02:38, Romen Law wrote: I did find two things though: 1. someone posted before saying that in Orion you should not make MDB implement MessageListener, otherwise it will not work. I found that to be false. Cool. Sorry for the false info. I was referring to this previous post: http://www.mail-archive.com/orion-interest%40orionserver.com/msg14877.html Obviously one needs onMessage() to receive the messages...But it compiles and deploys fine without the MessageListener declaration. oh well. cheers, - Renaud -- Renaud Bruyeron [EMAIL PROTECTED] Fullsix London - http://www.fullsix.com/
Re: SV: MDB in orion 1.5.2 using Queue
Magnus, When could we expect the durable subscription-type tag to work? Currently it does not work. I have used resource-provider to connect my MDB to an external JMS server and I noticed that if I set the subscription-type to durable then when I use my declared connectionfactories in resource-provider to send messages to the same topic that my mdb is listening to I do not receive those messages in my mdb. It seems that you are creating a subscriber and if durable is set then you are setting the boolean value that tells the subscriber whether to pick up messages that it sent in to false. Just a guess though. Just curious,thanks, Tim Pouyer On Fri, 2001-10-19 at 04:41, Magnus Rydin wrote: Hi. 1) In 1.5.3 Orion will tell you if you havent implemented MessageDrivenBean and MessageListener in your MDB. 2) Orion will use the default JMS resource if you dont specify a destination-location etc in orion-ejb-jar.xml. ResourceProviders, made public in 1.5.2, lets you use 3rd party resources in a very simple way. A document on this issue is in progress and will be released shortly, with examples, samples and details. A MDB document is also in progress, but other documents have higher prio right now. WR -Ursprungligt meddelande- Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]För Romen Law Skickat: den 19 oktober 2001 03:39 Till: Orion-Interest Ämne: RE: MDB in orion 1.5.2 using Queue ello, Thanks for all the replies. I must apologise: my MDB using Queue was working all along. It's just that I was using System.out.println() for logging so I couldn't see it on the console. But after using log4j I could see it. Well, there is first time for everything. I did find two things though: 1. someone posted before saying that in Orion you should not make MDB implement MessageListener, otherwise it will not work. I found that to be false. 2. I still do need to modify the destination-location in orion-ejb-jar.xml. If I don't it still works provided that I only have one Queue or Topic defined in jms.xml. Orion seems to use that one disregarding the queue name you specify in the sender. cheers romen
Re: SV: MDB in orion 1.5.2 using Queue
Magnus, I created my own resource provider for Tibco JMS and it would work, but only for the Queue/Topic returned by getDefaultResource() (can't remember the exact method name off the top of my head). Anyway, my orion-ejb-jar.xml would like like: message-driven-deployment name=MyMessageDriven My queue would be located at java:comp/resource/TibcoProvider/myQueue But if I put in my orion-ejb-jar.xml file the complete signature, (jms/MyQueue), my MDB can't locate the proper queue/connection factory. It appears that jms/MyQueue would imply that the root of the lookup must take place at java:comp/env, which is a sibling to java:comp/resource. My JNDI knowledge is very limited, so if you can explain to me how I can specify which queue to use with my resource provider, that would be great! message-driven-deployment cache-timeout=60|never connection-factory-location=jms/MyQueueConnection destination-location=jms/MyQueue max-instances=50 min-instances=5 name=MyMessageDriven -Pat At 10:41 AM 10/19/2001 +0200, you wrote: Hi. 1) In 1.5.3 Orion will tell you if you havent implemented MessageDrivenBean and MessageListener in your MDB. 2) Orion will use the default JMS resource if you dont specify a destination-location etc in orion-ejb-jar.xml. ResourceProviders, made public in 1.5.2, lets you use 3rd party resources in a very simple way. A document on this issue is in progress and will be released shortly, with examples, samples and details. A MDB document is also in progress, but other documents have higher prio right now. WR -Ursprungligt meddelande- Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]För Romen Law Skickat: den 19 oktober 2001 03:39 Till: Orion-Interest Ämne: RE: MDB in orion 1.5.2 using Queue ello, Thanks for all the replies. I must apologise: my MDB using Queue was working all along. It's just that I was using System.out.println() for logging so I couldn't see it on the console. But after using log4j I could see it. Well, there is first time for everything. I did find two things though: 1. someone posted before saying that in Orion you should not make MDB implement MessageListener, otherwise it will not work. I found that to be false. 2. I still do need to modify the destination-location in orion-ejb-jar.xml. If I don't it still works provided that I only have one Queue or Topic defined in jms.xml. Orion seems to use that one disregarding the queue name you specify in the sender. cheers romen
RE: MDB in orion 1.5.2 using Queue
Hi Romen, did you specify the admin security credentials? its -Djava.naming.security.credentials=admin password If you don't give this, it pops up a textbox asking for the password. Maybe you are tabbing off this before it pops up? Did you enable jms from server.xml by uncommenting the jms-config node? I did not have to do anything to orion-ejb-jar.xml. I configured my ejb-jar.xml as follows: ejb-jar descriptionMessage Driven Bean/description enterprise-beans message-driven ejb-nameMyMDB/ejb-name ejb-classpackage.MyMDB/ejb-class transaction-typeContainer/transaction-type acknowledge-modeauto-acknowledge/acknowledge-mode message-driven-destination destination-typejavax.jms.Queue/destination-type subscription-durabilitydurable/subscription-durability /message-driven-destination resource-ref res-ref-namejms/QueueConnectionFactory/res-ref-name res-typejavax.jms.QueueConnectionFactory/res-type res-authContainer/res-auth /resource-ref resource-env-ref resource-env-ref-namejms/theQueue/resource-env-ref-name resource-env-ref-typejavax.jms.Queue/resource-env-ref-type /resource-env-ref /message-driven Hope that helps, Justin -Original Message- From: Romen Law [mailto:[EMAIL PROTECTED]] Sent: 18 October 2001 01:05 To: Orion-Interest Subject: MDB in orion 1.5.2 using Queue ello, I tested MDB using topic and it worked fine. What I did was to deploy the MDB using the 'jms/theTopic' as the destination-location in orion-ejb-jar.xml. Then I ran the sample jmschat.jar and saw that my MDB got called. But I could not repeat the same using Queue as the destination. I deployed the same MDB using destination-typejavax.jms.Queue/destination-type in ejb-jar.xml and destination-location=jms/theQueue in orion-ejb-jar.xml. Then I ran the coffeemaker.jar sample using the -order flag. My bean did not get called. Did I do something wrong? Has anyone tried using MDB with Queue? Any clues? cheers romen
RE: MDB in orion 1.5.2 using Queue
ello, Thanks for all the replies. I must apologise: my MDB using Queue was working all along. It's just that I was using System.out.println() for logging so I couldn't see it on the console. But after using log4j I could see it. Well, there is first time for everything. I did find two things though: 1. someone posted before saying that in Orion you should not make MDB implement MessageListener, otherwise it will not work. I found that to be false. 2. I still do need to modify the destination-location in orion-ejb-jar.xml. If I don't it still works provided that I only have one Queue or Topic defined in jms.xml. Orion seems to use that one disregarding the queue name you specify in the sender. cheers romen
MDB in orion 1.5.2 using Queue
ello, I tested MDB using topic and it worked fine. What I did was to deploy the MDB using the 'jms/theTopic' as the destination-location in orion-ejb-jar.xml. Then I ran the sample jmschat.jar and saw that my MDB got called. But I could not repeat the same using Queue as the destination. I deployed the same MDB using destination-typejavax.jms.Queue/destination-type in ejb-jar.xml and destination-location=jms/theQueue in orion-ejb-jar.xml. Then I ran the coffeemaker.jar sample using the -order flag. My bean did not get called. Did I do something wrong? Has anyone tried using MDB with Queue? Any clues? cheers romen
