You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Hiram Chirino (JIRA)" <de...@geronimo.apache.org> on 2004/11/30 23:42:28 UTC
[jira] Created: (GERONIMO-507) ConnectException occurs after MDB deployment and server restart. MDB deploying before Broker
ConnectException occurs after MDB deployment and server restart. MDB deploying before Broker
---------------------------------------------------------------------------------------------
Key: GERONIMO-507
URL: http://nagoya.apache.org/jira/browse/GERONIMO-507
Project: Apache Geronimo
Type: Bug
Components: ActiveMQ
Versions: 1.0-M3
Reporter: Hiram Chirino
Assigned to: Hiram Chirino
MDB deploys fine to the server. Server is restarted and you get the following error:
14:30:17,048 WARN [GBeanSingleReference] Exception occured while attempting to fully start: objectName=geronimo.server:EJBModule=activemq-itest-ejb-1.3-SNAPSHOT.jar,J2EEAppli
Could not start the endpoint.
at org.codehaus.activemq.ra.ActiveMQAsfEndpointWorker.start(ActiveMQAsfEndpointWorker.java:98)
at org.codehaus.activemq.ra.ActiveMQResourceAdapter.endpointActivation(ActiveMQResourceAdapter.java:179)
at org.apache.geronimo.connector.ResourceAdapterWrapper.endpointActivation(ResourceAdapterWrapper.java:96)
at org.apache.geronimo.connector.ResourceAdapterWrapper$$FastClassByCGLIB$$4ab28e73.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:87)
at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
...
at org.apache.geronimo.kernel.Kernel.startRecursiveGBean(Kernel.java:423)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:150)
Caused by: javax.jms.JMSException: Initialization of TcpTransportChannel failed. URI was: tcp://localhost:61616 Reason: java.net.ConnectException: Connection refused: connect
at org.codehaus.activemq.util.JMSExceptionHelper.newJMSException(JMSExceptionHelper.java:49)
at org.codehaus.activemq.transport.tcp.TcpTransportChannel.<init>(TcpTransportChannel.java:102)
at org.codehaus.activemq.transport.tcp.TcpTransportChannelFactory.create(TcpTransportChannelFactory.java:43)
...
at org.codehaus.activemq.ra.ActiveMQBaseEndpointWorker.getPhysicalConnection(ActiveMQBaseEndpointWorker.java:117)
at org.codehaus.activemq.ra.ActiveMQAsfEndpointWorker.start(ActiveMQAsfEndpointWorker.java:90)
... 76 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
...
at java.net.Socket.<init>(Socket.java:178)
at org.codehaus.activemq.transport.tcp.TcpTransportChannel.createSocket(TcpTransportChannel.java:472)
at org.codehaus.activemq.transport.tcp.TcpTransportChannel.<init>(TcpTransportChannel.java:98)
It seems like the MDB is being deployed before the ActiveMQ broker is up and running. Since the message Broker is a remote resource that may be up or down, the Resource Adapter should support automatic recovery and should show a sincer error message when the message broker is down.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-507) ConnectException occurs after MDB deployment and server restart. MDB deploying before Broker
Posted by "Hiram Chirino (JIRA)" <de...@geronimo.apache.org>.
[ http://nagoya.apache.org/jira/browse/GERONIMO-507?page=history ]
Hiram Chirino closed GERONIMO-507:
----------------------------------
Resolution: Fixed
Fix Version: 1.0-M4
The resource adapter no implements recovery with exponential rollback. The max delay of the reconnect is currently 30 seconds. Once the max delay is hit, the adapter will issue warning log messages so that a adminstrator can look into why a connection cannot be established to the broker.
> ConnectException occurs after MDB deployment and server restart. MDB deploying before Broker
> ---------------------------------------------------------------------------------------------
>
> Key: GERONIMO-507
> URL: http://nagoya.apache.org/jira/browse/GERONIMO-507
> Project: Apache Geronimo
> Type: Bug
> Components: ActiveMQ
> Versions: 1.0-M3
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 1.0-M4
>
> MDB deploys fine to the server. Server is restarted and you get the following error:
> 14:30:17,048 WARN [GBeanSingleReference] Exception occured while attempting to fully start: objectName=geronimo.server:EJBModule=activemq-itest-ejb-1.3-SNAPSHOT.jar,J2EEAppli
> Could not start the endpoint.
> at org.codehaus.activemq.ra.ActiveMQAsfEndpointWorker.start(ActiveMQAsfEndpointWorker.java:98)
> at org.codehaus.activemq.ra.ActiveMQResourceAdapter.endpointActivation(ActiveMQResourceAdapter.java:179)
> at org.apache.geronimo.connector.ResourceAdapterWrapper.endpointActivation(ResourceAdapterWrapper.java:96)
> at org.apache.geronimo.connector.ResourceAdapterWrapper$$FastClassByCGLIB$$4ab28e73.invoke(<generated>)
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:87)
> at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
> ...
> at org.apache.geronimo.kernel.Kernel.startRecursiveGBean(Kernel.java:423)
> at org.apache.geronimo.system.main.Daemon.main(Daemon.java:150)
> Caused by: javax.jms.JMSException: Initialization of TcpTransportChannel failed. URI was: tcp://localhost:61616 Reason: java.net.ConnectException: Connection refused: connect
> at org.codehaus.activemq.util.JMSExceptionHelper.newJMSException(JMSExceptionHelper.java:49)
> at org.codehaus.activemq.transport.tcp.TcpTransportChannel.<init>(TcpTransportChannel.java:102)
> at org.codehaus.activemq.transport.tcp.TcpTransportChannelFactory.create(TcpTransportChannelFactory.java:43)
> ...
> at org.codehaus.activemq.ra.ActiveMQBaseEndpointWorker.getPhysicalConnection(ActiveMQBaseEndpointWorker.java:117)
> at org.codehaus.activemq.ra.ActiveMQAsfEndpointWorker.start(ActiveMQAsfEndpointWorker.java:90)
> ... 76 more
> Caused by: java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> ...
> at java.net.Socket.<init>(Socket.java:178)
> at org.codehaus.activemq.transport.tcp.TcpTransportChannel.createSocket(TcpTransportChannel.java:472)
> at org.codehaus.activemq.transport.tcp.TcpTransportChannel.<init>(TcpTransportChannel.java:98)
> It seems like the MDB is being deployed before the ActiveMQ broker is up and running. Since the message Broker is a remote resource that may be up or down, the Resource Adapter should support automatic recovery and should show a sincer error message when the message broker is down.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira