[jboss-jira] [JBoss JIRA] Commented: (JBAS-6568) PersistenceManager should retry all DB operations for a reasonable amount of tries
Rico Neubauer (JIRA)
jira-events at lists.jboss.org
Wed Mar 4 04:10:23 EST 2009
[ https://jira.jboss.org/jira/browse/JBAS-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12455345#action_12455345 ]
Rico Neubauer commented on JBAS-6568:
-------------------------------------
Wrong component - should have been "JMS (JBossMQ)" - please move, thx.
> PersistenceManager should retry all DB operations for a reasonable amount of tries
> ----------------------------------------------------------------------------------
>
> Key: JBAS-6568
> URL: https://jira.jboss.org/jira/browse/JBAS-6568
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JMS (JBoss Messaging)
> Affects Versions: JBossAS-4.2.3.GA
> Reporter: Rico Neubauer
> Assignee: Clebert Suconic
> Attachments: PersistenceManager_4_2_3_GA.diff
>
>
> org.jboss.mq.pm.jdbc2.PersistenceManager does contain a simple logic in method remove(MessageReference, Tx) to retry a DB operation and therefore bypass sporadic temporary DB failures.
> This should be extended to the other DB-operations of PersistenceManager.
> Tests using a JDBC-driver throwing randomly arbitrary SQLExceptions showed this resolving most of them and keeping the system in a consistent state.
> Tests without a patched PersistenceManager ran quite fast into a dead end where JMS messages were not being processed anymore until restart of the AS - also see http://www.jboss.org/index.html?module=bb&op=viewtopic&t=151023 for this symptom.
> Proposed patch will get attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list