Hi Markus,
I dont think there is a problem in consuming the message, the
problem could be at the producer. Did you check if the message is sent
to the topic properly by your client, (after undeploying your MDB). Just
do query the destination after executing your client and check if there
are messages in the topic. Also, you could add a session.commit() after
the producer.send is called.
Thanks
Ramesh
Markus KARG wrote:
> Ramesh Parthasarathy schrieb:
>> Hi Markus,
>> From what i can interpret from the output looks like you have one
>> consumer, I guess "Aktuelle Zahl Konsumenten 1" means one consumer.
>> Which means any message to this topic should be received by the MDB
>> (assuming MDB is the only consumer you have).
>>
>> Can you undeploy the MDB and check if the swing client is actually
>> sending the message to this destination where the MDB is listening to.
>> Are QUIPSY_TOPIC and MY_TOPIC the same destination ?
> Yes, "Aktuelle Zahl Konsumenten 1" means that there is only one
> consumer. I undeployed the MDB and the number now is zero.
>
> There is only one physical destination "QUIPSY_TOPIC" (Topic) besides
> mq.sys.dmq, and I now have aligned all names to be QUIPSY_TOPIC (no
> more using MY_TOPIC now).
>
> Still the same behaviour. No exception. No error message. Nothing.
>
> Weird.
>
> Thanks
> Markus
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>