Hi Matthias,
Thanks for the logs, did not find anything unusual.
Have you tried it on GFV2 ? Was it working ?
Thanks
-Ramesh
matthias.fraass_at_tricoder.net wrote:
> Hi Ramesh,
>
> 2010/1/7 Ramesh <Ramesh.Parthasarathy_at_sun.com>:
>
>> Does undeploying the MDB also cause the message to be put back in the Queue
>> ?
>>
>
> Yes.
>
>
>> Could you please attach logs with generic jms ra log level FINEST
>>
> Yes. I turned logging in genericra to FINEST.
>
>
>> Could you turn on jts and jts logging to FINEST in Glassfish
>> and see if it prints the transactions.
>>
>
> I turned "Transaction Service" in GFv3 Monitoring to "HIGH". Is that right?
>
> See the attachments:
> log1_deploy -> Deployment
> log2_afterdeploy -> some log entries after deployment, but before I
> started sending messages
> log3_messaging.log -> thats when I sent a message to the sonic ("INFO:
> called putMessageAdapter->Sonic") and got it back ("INFO: ####
> MySonicRemoteMessageDrivenBean got message:"...).
> log4_undeploy -> undeploying the application. This caused the message
> to be back again in the sonic Queue.
>
> When I deployed the application again, I got the message again.
>
> I hope that helps - just ask and I can provide you with more information.
>
> Best regards,
>
> Matthias
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_genericjmsra.dev.java.net
> For additional commands, e-mail: users-help_at_genericjmsra.dev.java.net
>