[
https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564184#action_12564184
]
David Jencks commented on GERONIMO-3783:
----------------------------------------
Kevan and I did some experiments and found a configuration that works. I'm
pretty sure there's a bug in the AMQ transaction handling causing the actual
issue, but we didn't look for it.
You need 2 amq resource adapters set up.
The mdb uses one, and in the ra config properties you set useInboundSession to
true.
The session bean (that sends the original messages) uses the other, and it has
the default useInboundSession false set.
This makes the mdb reuse the inbound session to send out the response messages
and it appears to work fine for lots of messages. Maybe kevan can post a patch
or the updated code we used.
> MessageDrivenBean delivery problem
> ----------------------------------
>
> Key: GERONIMO-3783
> URL: https://issues.apache.org/jira/browse/GERONIMO-3783
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.1
> Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo
> 2.1-snapshot (2008-01-02)
> Reporter: Tomasz Mazan
> Priority: Critical
> Attachments: mdb-issue.zip
>
>
> MessageDrivenBean that listens on the Queue receive (and process) some
> messages and then stop receiving any new message until next module's restart.
> After restart a few next messages are delivered to MDB, and it stops again.
> Some additional information I put here
> http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
