[jbossts-issues] [JBoss JIRA] Updated: (JBTM-542) Slow memory leak / Thread lock on transaction initiated by MDB on jboss 4.2.3

LESCARRET Vincent (JIRA) jira-events at lists.jboss.org
Mon May 4 08:44:50 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBTM-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

LESCARRET Vincent updated JBTM-542:
-----------------------------------

    Description: 
This problem is already related in JIRA (https://jira.jboss.org/jira/browse/JBTM-444) . Our production server reachs UserLoad value of 100% in 3 our 4 days, and the only solution is to stop and restart the server. 
We intensively use JMS queue (JBOSS MQ and Oracle for persistence) and MDB which use XA transactions.  

  
What is the actual workaround  for this problem ?
Is the problem still in the Jboss 5 server ?
Is the problem the surce of following logs ? :


log:
2009-05-04 00:07:04,640 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_3] - TORecoveryModule - first pass
2009-05-04 00:07:04,640 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.firstpass] Local XARecoveryModule - first pass
2009-05-04 00:07:14,642 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery - second pass <lun., 4 mai 2009 00:07:14>


  was:
This problem is already related in JIRA (https://jira.jboss.org/jira/browse/JBTM-444) . Our production server reachs UserLoad value of 100% in 3 our 4 days, and the only solution is to stop and restart the server. 
We intensively use JMS queue (JBOSS MQ and Oracle for persistence) and MDB which use XA transactions.  
  
What is the actual workaround  for this problem ?
Is the problem still in the Jboss 5 server ?



log:
2009-05-04 00:07:04,640 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_3] - TORecoveryModule - first pass
2009-05-04 00:07:04,640 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.firstpass] Local XARecoveryModule - first pass
2009-05-04 00:07:14,642 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery - second pass <lun., 4 mai 2009 00:07:14>




> Slow memory leak  / Thread lock on transaction initiated by MDB on jboss 4.2.3
> ------------------------------------------------------------------------------
>
>                 Key: JBTM-542
>                 URL: https://jira.jboss.org/jira/browse/JBTM-542
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Application Server Integration
>    Affects Versions: 4.2.3.SP7
>         Environment: Linux RH 4 , JDK 1.5.0_15 , jboss AS 4.2.3
>            Reporter: LESCARRET Vincent
>            Priority: Critical
>
> This problem is already related in JIRA (https://jira.jboss.org/jira/browse/JBTM-444) . Our production server reachs UserLoad value of 100% in 3 our 4 days, and the only solution is to stop and restart the server. 
> We intensively use JMS queue (JBOSS MQ and Oracle for persistence) and MDB which use XA transactions.  
>   
> What is the actual workaround  for this problem ?
> Is the problem still in the Jboss 5 server ?
> Is the problem the surce of following logs ? :
> log:
> 2009-05-04 00:07:04,640 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_3] - TORecoveryModule - first pass
> 2009-05-04 00:07:04,640 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.firstpass] Local XARecoveryModule - first pass
> 2009-05-04 00:07:14,642 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery - second pass <lun., 4 mai 2009 00:07:14>

-- 
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 jbossts-issues mailing list