Well, that's good (in a bad way). At least I'm not the only one to have
experienced this. Unfortunately, I can't use message-driven beans (restricted
to EJB1.1, for now).
Memo to Orion team: could you please respond to this. I've sent email to
support regarding this. I'm hesitant to file this as a bug report since I
haven't verified that it isn't a problem with my approach/configuration.
Vidur
Arved Sandstrom wrote:
> 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
