synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Upul Godage (JIRA)" <>
Subject [jira] Resolved: (SYNAPSE-184) JMS connections lost due to NW issues should be attempted for recovery
Date Thu, 13 Dec 2007 08:03:43 GMT


Upul Godage resolved SYNAPSE-184.

    Resolution: Fixed

When jms connection is down, it will try to reconnect every 30 seconds.
Reconnect duration can be configured by property transport.jms.ReconnectTimeout in axis2.xml.
(default 30 seconds)

    <transportReceiver name="jms" class="org.apache.synapse.transport.jms.JMSListener">
        <parameter name="myTopicConnectionFactory">
        	<parameter name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
        	<parameter name="java.naming.provider.url">tcp://localhost:61616</parameter>
        	<parameter name="transport.jms.ConnectionFactoryJNDIName">TopicConnectionFactory</parameter>
                <parameter name="transport.jms.ReconnectTimeout">10</parameter>

> JMS connections lost due to NW issues should be attempted for recovery
> ----------------------------------------------------------------------
>                 Key: SYNAPSE-184
>                 URL:
>             Project: Synapse
>          Issue Type: Improvement
>    Affects Versions: 1.1
>            Reporter: Asankha C. Perera
>            Assignee: Upul Godage
> JMS connections must be attempted to be recovered if they are lost due to the JMS provider
going down or NW issues

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message