geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <>
Subject [jira] Closed: (GERONIMO-507) ConnectException occurs after MDB deployment and server restart. MDB deploying before Broker
Date Fri, 03 Dec 2004 00:37:28 GMT
     [ ]
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
> ---------------------------------------------------------------------------------------------
>          Key: GERONIMO-507
>          URL:
>      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(
>         at org.codehaus.activemq.ra.ActiveMQResourceAdapter.endpointActivation(
>         at org.apache.geronimo.connector.ResourceAdapterWrapper.endpointActivation(
>         at org.apache.geronimo.connector.ResourceAdapterWrapper$$FastClassByCGLIB$$4ab28e73.invoke(<generated>)
>         at net.sf.cglib.reflect.FastMethod.invoke(
>         at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(
> ...
>         at org.apache.geronimo.kernel.Kernel.startRecursiveGBean(
>         at org.apache.geronimo.system.main.Daemon.main(
> Caused by: javax.jms.JMSException: Initialization of TcpTransportChannel failed. URI
was: tcp://localhost:61616 Reason: Connection refused: connect
>         at org.codehaus.activemq.util.JMSExceptionHelper.newJMSException(
>         at org.codehaus.activemq.transport.tcp.TcpTransportChannel.<init>(
>         at org.codehaus.activemq.transport.tcp.TcpTransportChannelFactory.create(
> ...
>         at org.codehaus.activemq.ra.ActiveMQBaseEndpointWorker.getPhysicalConnection(
>         at org.codehaus.activemq.ra.ActiveMQAsfEndpointWorker.start(
>         ... 76 more
> Caused by: Connection refused: connect
>         at Method)
>         at
> ...
>         at<init>(
>         at org.codehaus.activemq.transport.tcp.TcpTransportChannel.createSocket(
>         at org.codehaus.activemq.transport.tcp.TcpTransportChannel.<init>(
> 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:
If you want more information on JIRA, or have a bug to report see:

View raw message