Tomasz Mazan wrote:
>
>
>
> djencks wrote:
>>
>>
>> On Jan 18, 2008, at 12:05 AM, Tomasz Mazan wrote:
>>
>>>
>>>
>>>
>>> djencks wrote:
>>>>
>>>> Do you have a second resource adapter configured for the inbound
>>>> messages to the mdb?
>>>>
>>>> I seem to recall someone reporting a similar problem if they sent the
>>>> same message they received. If they copied the message into a new
>>>> message and sent that everything worked as expected. Are you sending
>>>> the same message or copying it? I don't know which behavior is
>>>> expected by the jms spec.
>>>>
>>>> thanks
>>>> david jencks
>>>>
>>>
>>> David,
>>>
>>> 1) I use the same resource adapter for the inbound/outbound messages.
>>> 2) I create new Message to send as reply
>>>
>>> Following your advice I had tried to drop received messages and I
>>> remarked
>>> that problem is in creating new connection. There's no problem with
>>> delivering messages since I've commented that part of my code, but....
>>> obviously... that doesn't solve my problem.
>>>
>>> I've tried something else which looks as good solution - change
>>> connectionmanager transaction's setting from xa-transaction to
>>> local-transaction. I don't see any reason to use XA for my MDB
>>> which only
>>> receives message - process it using webservice client - and return
>>> response
>>> to another jms queue.
>>
>> If using local-transaction in your connector configuration fixes the
>> problem then there is a bug in activemq xa handling or possibly our
>> transaction manager. I wonder if activemq 5 would work better, but
>> it seems to be non-trivial to integrate it.
>>
>> thanks
>> david jencks
>>
>>>
>>>
>>> Beniamin
>>> --
>>> View this message in context: http://www.nabble.com/Strange-plug-
>>> with-delivering-messages-to-MDB-tp14923100s134p14947998.html
>>> Sent from the Apache Geronimo - Users mailing list archive at
>>> Nabble.com.
>>>
>>
>>
>>
>
> David
> Using local-transaction causes strange effect:
> - MDB says that response has been sent
> - logs shows transaction COMMIT
> but no message is not delivered to destination
>
> Only using independent RA for inbound and outbound messages solving my
> problem.
>
> Beniamin
>
Another case which I noticed after sending over 2000 messages to MDB (this
MDB only receive message, and doesn't create any new Connection). After
delivering a bit over 1000 messages MDB stopped receiving any new.
Beniamin
--
View this message in context:
http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-tp14923100s134p15016851.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
