You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Rich Newcomb (JIRA)" <ji...@apache.org> on 2012/09/14 08:47:07 UTC
[jira] [Created] (CAMEL-5613) Provide robust connection support for
JMX consumers
Rich Newcomb created CAMEL-5613:
-----------------------------------
Summary: 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
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.
--
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
[jira] [Commented] (CAMEL-5613) Provide robust connection support
for JMX consumers
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455730#comment-13455730 ]
Claus Ibsen commented on CAMEL-5613:
------------------------------------
Thanks Rich for the patch. Its in trunk now. Feel free to update the documentation.
> 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
> Assignee: Claus Ibsen
> 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
[jira] [Commented] (CAMEL-5613) Provide robust connection support
for JMX consumers
Posted by "Rich Newcomb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455853#comment-13455853 ]
Rich Newcomb commented on CAMEL-5613:
-------------------------------------
Docs updated. Thanks Claus.
> 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
> Assignee: Claus Ibsen
> 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
[jira] [Assigned] (CAMEL-5613) Provide robust connection support
for JMX consumers
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-5613:
----------------------------------
Assignee: Claus Ibsen
> 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
> Assignee: Claus Ibsen
> 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
[jira] [Updated] (CAMEL-5613) Provide robust connection support for
JMX consumers
Posted by "Rich Newcomb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Newcomb updated CAMEL-5613:
--------------------------------
Attachment: CAMEL-5613.patch
Patch for trunk attached. I will update docs once patch is committed.
> 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 :
> * *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.
--
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
[jira] [Resolved] (CAMEL-5613) Provide robust connection support
for JMX consumers
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-5613.
--------------------------------
Resolution: Fixed
> 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
> Assignee: Claus Ibsen
> 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
[jira] [Updated] (CAMEL-5613) Provide robust connection support for
JMX consumers
Posted by "Rich Newcomb (JIRA)" <ji...@apache.org>.
[ 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