I have an auto-started client that listens for JMS messages (pub-sub)
without any problems. I don't know what your code looks like, but some
things I am doing are creating a durable subscriber and making sure that my
thread for the listener doesn't die.
I know that probably doesn't help much, but w/out any source examples it is
hard to tell what the difference could be.
jason
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Arved
> Sandstrom
> Sent: Monday, October 30, 2000 8:17 AM
> To: Orion-Interest
> Subject: RE: Using JMS with auto-started client
>
>
> Funny you should bring this up. I wanted a JMS listener as a
> "service", and
> in order to keep it more compliant with most app servers, the
> first thing I
> tried was exactly what you describe, with the same results.
>
> Eventually I went with a message-driven bean, even if that only
> avoided the
> problem.
>
> Arved Sandstrom
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Vidur Dhanda
> Sent: Saturday, October 28, 2000 4:46 PM
> To: Orion-Interest
> Subject: Using JMS with auto-started client
>
>
> Hello,
>
> In my application.xml I have a <module> block and in
> orion-application.xml I have a <client-module> block with
> auto-start=true. This correctly starts up some application code along
> with the orion server. One of the classes that are started, subscribes
> to a JMS queue. It is able to get a connection factory, create a
> subscriber etc. but _never_ gets any messages. When I run the same
> class from the command-line and not have orion auto-start it, it gets
> messages fine. Actually, I'm rather impressed with the speed with which
> messages are delivered.
>
> How do I understand this further? Since the code runs fine when not
> auto-started and when auto-started it doesn't throw any exceptions, I'm
> assuming this is a problem with my configuration. Can anyone help me
> with fix it, please.
>
>
> Thanks,
> Vidur
>
>
>
>
