[
https://issues.apache.org/jira/browse/GERONIMO-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671013#action_12671013
]
Ivan commented on GERONIMO-4257:
--------------------------------
I try it with the 2.2 snapshot of 20090202
1) When message is waiting for delivery to MDB i cannot undeploy module with
this MDB from command line. I have to stop module via G-console and then
undeploy
-> Could not reproduce it, I could undeploy the module while there are messages
waiting for delivery to the MDB.
2) If messages are waiting for delivery and I shutdown server (geronimo stop)
and the run it again none of messages are delivered to listener
-> After refering to the ActiveMQ document, add the ?consumer.retroactive=true
to the queue name, those messages would be redeliveried to the MDB
Please refer to the link http://activemq.apache.org/retroactive-consumer.html
3) When MDB onMessage method throws i.e. NullPointerException, the transaction
is rolledback but a) message is not being redelivered anymore, b) module
couldn't be restarted == application stops working
Could not reproduce, the message is redeliveried.
Thanks !
> Problem with processing and delivery jms messages
> -------------------------------------------------
>
> Key: GERONIMO-4257
> URL: https://issues.apache.org/jira/browse/GERONIMO-4257
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ, OpenEJB, transaction manager
> Affects Versions: 2.1.1, 2.1.2
> Environment: Windows XPPro SP2, JDK 6
> Reporter: Tomasz Mazan
> Priority: Critical
>
> I've found strange Geronimo 2.1.2 behaviour with using JMS.
> 1) When message is waiting for delivery to MDB i cannot undeploy module with
> this MDB from command line. I have to stop module via G-console and then
> undeploy
> 2) If messages are waiting for delivery and I shutdown server (geronimo stop)
> and the run it again none of messages are delivered to listener
> 3) When MDB onMessage method throws i.e. NullPointerException, the
> transaction is rolledback but a) message is not being redelivered anymore,
> b) module couldn't be restarted == application stops working
> :(
> Geronimo 2.1 hadn't these "features".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
