Thank you so much for your kind help! Yes, you are right, there was a
typo in my client code. I originally copied my send method from an EJB,
so on the EJB side it was correct to use "true" since the EJB is
transacted. I am so blind! Certainly it all works pretty well as soon as
using "false".
On the other hand, this was worth the discussion: So at least I learned
how to use the imqcmd command, which seems to be pretty useful. :-)
Thanks a lot
Markus
Ramesh Parthasarathy schrieb:
> Hi Markus,
> It should not be necessary if you created a non-transacted session
> connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
>
> as mentioned in Chapter 23 of Java EE 5 tutorial.
>
> Thanks
> -Ramesh
>
>
>
> Markus KARG wrote:
>> Ramesh,
>>
>> as soon as I add the session.commit() it works pretty well! The
>> message is consumed by the MDB and I see the message box! Thanks for
>> that tip!
>>
>> But, is that manual commit really necessary? I thought that the
>> default is that commits are implied?
>>
>> Thanks
>> Markus
>>
>> Ramesh schrieb:
>>> 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
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
--
QUIPSY QUALITY GmbH & Co. KG
Ein Unternehmen der MES-Gruppe
Stuttgarter Strasse 23
D-75179 Pforzheim
Tel: 07231-9189-52
Fax: 07231-9189-59
www.quipsy.de
karg_at_quipsy.de
Registergericht Mannheim HRA 701214
Geschäftsführer: Nils Schroeder
Diese E-Mail enthält persönliche, vertrauliche und vor Weitergabe geschützte Informationen und ist ausschließlich für den vorgesehenen o.g. Empfänger (Adressaten) bestimmt. Falls Sie diese E-Mail versehentlich erhalten haben und nicht der vorgesehene Empfänger sind, bitten wir Sie, die E-Mail und deren Anhänge nicht aufzubewahren, nicht zu vervielfältigen, nicht zu nutzen und nicht weiterzugeben. Bitte informieren Sie uns als Absender über diesen Zustellungsfehler und löschen Sie die E-Mail.