[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1838) Improve DataSource retry mechanism

[Yong Hao Gao (JIRA)]

    [ https://issues.jboss.org/browse/JBMESSAGING-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572859#comment-12572859 ] 

Yong Hao Gao commented on JBMESSAGING-1838:
-------------------------------------------

You need to update the xxx-persistence-service.xml in order to change the retry parameters, like:


      <attribute name="MaxRetry">-1</attribute>

      <attribute name="RetryInterval">2000</attribute>

      <attribute name="RetryOnConnectionFailure">true</attribute>

These paramters apply to thress mbeans, i.e. jboss.messaging:service=PersistenceManager, jboss.messaging:service=PostOffice, jboss.messaging:service=JMSUserManager
because they each have some operations on DB. They all have the same set of params but they need to configure separately.

The meanings of those parameters are:

MaxRetry

The maximum number of retries when any Database operation fails.
Default value is 25. Setting a value of -1 means retry forever.

RetryInterval

The interval (in milliseconds) between two DB retries. Default value
is 1000 (1 second).</para>

This attribute should be used in combination with MaxRetry.

RetryOnConnectionFailure

It controls whether or not to retry connection creation on a DataSource
if it is failed to get a connection. Default value is false.


> Improve DataSource retry mechanism
> ----------------------------------
>
>                 Key: JBMESSAGING-1838
>                 URL: https://issues.jboss.org/browse/JBMESSAGING-1838
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core Persistence
>    Affects Versions: 1.4.0.SP3.CP11, 1.4.7.GA
>            Reporter: Yong Hao Gao
>            Assignee: Yong Hao Gao
>             Fix For: 1.4.0.SP3.CP12, 1.4.8.GA
>
>
> Currently JBM will retry max 25 times for a non connection failure. That's not good enough when a DB is disconnected and reconnected after max retry has reached. JBM will be in a 'failure' state and requires a re-start of the node. 
> If we allow user to configure the retry until the DB connection is back, JBM can work on without restart. We can also enable retry on connection failure too.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira