geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-2364) Update geronimo to use ActiveMQ 4.1.x
Date Tue, 29 Aug 2006 19:27:22 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-2364?page=comments#action_12431332 ] 
            
Hiram Chirino commented on GERONIMO-2364:
-----------------------------------------

The broker seems to be working good with this patch.  But it seems that on shutdown it throws
an error: 

{code}
15:18:42,042 INFO  [TransportConnector] Connector tcp://0.0.0.0:61616 Stopped
Server shutdown completed
15:18:46,727 WARN  [GeronimoConnectionEventListener] connectionErrorOccurred called with null
SQL Exception: 08003 : 
        at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.rollback(Unknown Source)
        at org.apache.derby.iapi.jdbc.BrokeredConnection.rollback(Unknown Source)
        at org.tranql.connector.jdbc.ManagedXAConnection.localTransactionRollback(ManagedXAConnection.java:124)
        at org.tranql.connector.AbstractManagedConnection$LocalTransactionImpl.rollback(AbstractManagedConnection.java:196)
        at org.tranql.connector.jdbc.ConnectionHandle.rollback(ConnectionHandle.java:135)
        at org.apache.activemq.store.jdbc.DefaultDatabaseLocker.stop(DefaultDatabaseLocker.java:80)
        at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stop(JDBCPersistenceAdapter.java:202)
        at org.apache.activemq.store.journal.JournalPersistenceAdapter.stop(JournalPersistenceAdapter.java:248)
        at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:42)
        at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:433)
        at org.apache.activemq.broker.BrokerService.containerShutdown(BrokerService.java:1235)
        at org.apache.activemq.broker.BrokerService$3.run(BrokerService.java:1212)
15:18:46,731 ERROR [JournalPersistenceAdapter] Could not stop service: org.apache.activemq.store.journal.JournalPersistenceAdapter@9ae2d3.
Reason: org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid
org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid
        at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87)
        at org.apache.geronimo.connector.outbound.connectiontracking.ConnectionTracker$$EnhancerByCGLIB$$b426a8b3.handleReleased(<generated>)
        at org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor.returnConnection(ConnectionTrackingInterceptor.java:81)
        at org.apache.geronimo.connector.outbound.GeronimoConnectionEventListener.connectionErrorOccurred(GeronimoConnectionEventListener.java:81)
        at org.tranql.connector.AbstractManagedConnection.unfilteredConnectionError(AbstractManagedConnection.java:119)
        at org.tranql.connector.jdbc.ManagedXAConnection.access$000(ManagedXAConnection.java:44)
        at org.tranql.connector.jdbc.ManagedXAConnection$1.connectionErrorOccurred(ManagedXAConnection.java:65)
        at org.apache.derby.jdbc.EmbedPooledConnection.notifyError(Unknown Source)
        at org.apache.derby.jdbc.EmbedPooledConnection.notifyException(Unknown Source)
        at org.apache.derby.iapi.jdbc.BrokeredConnection.notifyException(Unknown Source)
        at org.apache.derby.iapi.jdbc.BrokeredConnection.rollback(Unknown Source)
        at org.tranql.connector.jdbc.ManagedXAConnection.localTransactionRollback(ManagedXAConnection.java:124)
        at org.tranql.connector.AbstractManagedConnection$LocalTransactionImpl.rollback(AbstractManagedConnection.java:196)
        at org.tranql.connector.jdbc.ConnectionHandle.rollback(ConnectionHandle.java:135)
        at org.apache.activemq.store.jdbc.DefaultDatabaseLocker.stop(DefaultDatabaseLocker.java:80)
        at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stop(JDBCPersistenceAdapter.java:202)
        at org.apache.activemq.store.journal.JournalPersistenceAdapter.stop(JournalPersistenceAdapter.java:248)
        at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:42)
        at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:433)
        at org.apache.activemq.broker.BrokerService.containerShutdown(BrokerService.java:1235)
        at org.apache.activemq.broker.BrokerService$3.run(BrokerService.java:1212)
java.lang.NoClassDefFoundError: org/apache/activemq/broker/BrokerService$2$1
        at org.apache.activemq.broker.BrokerService$2.stop(BrokerService.java:1065)
        at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:42)
        at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:436)
        at org.apache.activemq.broker.BrokerService.containerShutdown(BrokerService.java:1235)
        at org.apache.activemq.broker.BrokerService$3.run(BrokerService.java:1212)
{code}

Not sure if we have to fix this before the patch is applied.  But I just wanted to make the
patch avail so that interested folks like Jason can start playing with the 4.1.x integration.

I suspect that the error may be due to some order of shutdown problems.  Not sure yet.

> Update geronimo to use ActiveMQ 4.1.x
> -------------------------------------
>
>                 Key: GERONIMO-2364
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2364
>             Project: Geronimo
>          Issue Type: RTC
>      Security Level: public(Regular issues) 
>          Components: ActiveMQ
>            Reporter: Hiram Chirino
>         Assigned To: Hiram Chirino
>             Fix For: 1.2
>
>         Attachments: GERONIMO-2364.patch
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message