geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: AMQ stopped to sent messages to MDB
Date Thu, 15 Nov 2007 13:01:26 GMT
These errors are not a problem here:

08:16:12,760 ERROR [Transaction] Please correct the integration and  
supply a NamedXAResource
java.lang.IllegalStateException: Cannot log transactions as  
org.apache.activemq.ra.LocalAndXATransaction@1c90b7c is not a  

These errors are definitely a problem:
08:16:12,870 ERROR [Transaction] Unexpected exception  
continuing to commit other RMs
javax.transaction.xa.XAException: The connection is already closed
Caused by: org.apache.activemq.ConnectionClosedException: The  
connection is already closed
...	... 22 more
08:16:13,089 ERROR [Transaction] The Transaction Manager has  
encountered an unexpected error condition while attempting to commit  
the transaction: null

Figuring out why the connection got closed would be very useful, but  
I'm not sure how to do it without digging into the code.

david jencks

On Nov 15, 2007, at 6:36 AM, Marcin Waldowski wrote:

> Hello.
> I have an information what was happen after Geronimo restart.
> gronimo.log is:
> MDB received 10 messages. That is equal to JMS ConnectorThreadPool  
> size.
> Regards,
> Marcin
> Marcin Waldowski wrote:
>> Hello.
>> I'm using Geronimo 2.0.1.
>> I faced problem during starting Geronimo. After 3 exceptions  
>> (stack trace: MDB didn't receive  
>> any message for few days.
>> After restarting Geronimo (today) only about 20 messages was sent  
>> to MDB, but we know that there must be thousand times as much.  
>> Unfortunately I haven't got any access to logs after restart.
>> Does anyone knows what can be a reason of "hang"? What can I do to  
>> make AMQ and MDB work together again?
>> Regards,
>> Marcin

View raw message