camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich Newcomb (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-5613) Provide robust connection support for JMX consumers
Date Fri, 14 Sep 2012 06:53:07 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rich Newcomb updated CAMEL-5613:
--------------------------------

    Description: 
A Camel JMX consumer that connects to a JMX server on the network currently needs the JMX
server to be active before the consumer is started.  The consumer also has no ability to re-initialize
lost connections to the JMX server.

The attached patch eliminates the timing dependency between the JMX consumer and JMX server,
by allowing the JMX consumer to optionally poll for the JMX server connection at startup.
 The patch also allows the consumer to optionally re-initialize (via polling) connections
to a JMX server after an active connection is broken.

The patch enables the following URI parameters for JMX consumers :

 * *testConnectionOnStartup* -- if true the consumer will throw an exception if unable to
establish the JMX connection upon startup.  If false, the consumer will attempt to establish
the JMX connection every 'x' seconds until the connection is made -- where 'x' is the configured
 reconnectDelay.  Default is _true_.

 * *reconnectOnConnectionFailure* -- If true the consumer will attempt to reconnect to the
JMX server when any connection failure occurs.  The consumer will attempt to re-establish
the JMX connection every 'x' seconds until the connection is made-- where 'x' is the configured
 reconnectDelay.  Default is _false_.

 * *reconnectDelay* -- The number of seconds to wait before attempting to retry establishment
of the initial connection or attempt to reconnect a lost connection.  Default is _10_ seconds.

  was:
A Camel JMX consumer that connects to a JMX server on the network currently needs the JMX
server to be active before the consumer is started.  The consumer also has no ability to re-initialize
lost connections to the JMX server.

The attached patch eliminates the timing dependency between the JMX consumer and JMX server,
by allowing the JMX consumer to optionally poll for the JMX server connection at startup.
 The patch also allows the consumer to optionally re-initialize (via polling) connections
to a JMX server after an active connection is broken.

The patch enables the following URI parameters for JMX consumers :

 * *testConnectionsOnStartup* -- if true the consumer will throw an exception if unable to
establish the JMX connection upon startup.  If false, the consumer will attempt to establish
the JMX connection every 'x' seconds until the connection is made -- where 'x' is the configured
 reconnectDelay.  Default is _true_.

 * *reconnectOnConnectionFailure* -- If true the consumer will attempt to reconnect to the
JMX server when any connection failure occurs.  The consumer will attempt to re-establish
the JMX connection every 'x' seconds until the connection is made-- where 'x' is the configured
 reconnectDelay.  Default is _false_.

 * *reconnectDelay* -- The number of seconds to wait before attempting to retry establishment
of the initial connection or attempt to reconnect a lost connection.  Default is _10_ seconds.

    
> Provide robust connection support for JMX consumers
> ---------------------------------------------------
>
>                 Key: CAMEL-5613
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5613
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jmx
>            Reporter: Rich Newcomb
>             Fix For: 2.11.0
>
>         Attachments: CAMEL-5613.patch
>
>
> A Camel JMX consumer that connects to a JMX server on the network currently needs the
JMX server to be active before the consumer is started.  The consumer also has no ability
to re-initialize lost connections to the JMX server.
> The attached patch eliminates the timing dependency between the JMX consumer and JMX
server, by allowing the JMX consumer to optionally poll for the JMX server connection at startup.
 The patch also allows the consumer to optionally re-initialize (via polling) connections
to a JMX server after an active connection is broken.
> The patch enables the following URI parameters for JMX consumers :
>  * *testConnectionOnStartup* -- if true the consumer will throw an exception if unable
to establish the JMX connection upon startup.  If false, the consumer will attempt to establish
the JMX connection every 'x' seconds until the connection is made -- where 'x' is the configured
 reconnectDelay.  Default is _true_.
>  * *reconnectOnConnectionFailure* -- If true the consumer will attempt to reconnect to
the JMX server when any connection failure occurs.  The consumer will attempt to re-establish
the JMX connection every 'x' seconds until the connection is made-- where 'x' is the configured
 reconnectDelay.  Default is _false_.
>  * *reconnectDelay* -- The number of seconds to wait before attempting to retry establishment
of the initial connection or attempt to reconnect a lost connection.  Default is _10_ seconds.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message