11:57 a.m.
Threads in endless loop in TransactionReaper.
---------------------------------------------
Key: JBTM-213
URL: http://jira.jboss.com/jira/browse/JBTM-213
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JTA Implementation
Reporter: Phillip Thurmond
Assigned To: Mark Little
After generating a load against JBossAS 4.2 beta1, the cpu is pegged at 100% even after
the load has stopped. A thread dump reveals several threads at
TransactionReaper.insert(). These threads are all doing a WeakHashMap.get(). Looking at
TransactionReaper, I believe this is caused by unsynchronized access to the _timeouts
WeakHahsMap. This is line 324 in TransactionReaper.java.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:59 a.m.
New subject: [JBoss JIRA] Commented: (JBTM-213) Threads in endless loop in TransactionReaper.
[ http://jira.jboss.com/jira/browse/JBTM-213?page=comments#action_12361032 ]
Phillip Thurmond commented on JBTM-213:
---------------------------------------
"http-10.16.70.105-8080-98" daemon prio=1 tid=0x0000002ac9fca230 nid=0x2656
runnable [0x0000000050b58000..0x0000000050b59db0]
at java.util.WeakHashMap.get(WeakHashMap.java:348)
at
com.arjuna.ats.arjuna.coordinator.TransactionReaper.insert(TransactionReaper.java:320)
at com.arjuna.ats.arjuna.AtomicAction.begin(AtomicAction.java:147)
at
com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.<init>(TransactionImple.java:116)
at
com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:98)
at
com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.begin(BaseTransactionManagerDelegate.java:77)
at
org.jboss.ejb.plugins.TxInterceptorCMT.startTransaction(TxInterceptorCMT.java:476)
at
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:329)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138)
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
at org.jboss.ejb.Container.invoke(Container.java:960)
at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at
org.jboss.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:169)
at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:118)
at
org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:209)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:195)
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
at
org.jboss.proxy.ejb.StatefulSessionInterceptor.invoke(StatefulSessionInterceptor.java:121)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
at $Proxy155.getItems(Unknown Source)
at
org.spec.jappserver.servlet.helper.SpecAction.getVehicleQuotes(SpecAction.java:368)
at
org.spec.jappserver.servlet.helper.SpecServletAction.doVehicleQuotes(SpecServletAction.java:653)
at
org.spec.jappserver.servlet.SpecAppServlet.performTask(SpecAppServlet.java:197)
at org.spec.jappserver.servlet.SpecAppServlet.doGet(SpecAppServlet.java:96)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:228)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:216)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:624)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:445)
at java.lang.Thread.run(Thread.java:595)
Threads in endless loop in TransactionReaper.
---------------------------------------------
Key: JBTM-213
URL: http://jira.jboss.com/jira/browse/JBTM-213
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JTA Implementation
Reporter: Phillip Thurmond
Assigned To: Mark Little
After generating a load against JBossAS 4.2 beta1, the cpu is pegged at 100% even after
the load has stopped. A thread dump reveals several threads at
TransactionReaper.insert(). These threads are all doing a WeakHashMap.get(). Looking at
TransactionReaper, I believe this is caused by unsynchronized access to the _timeouts
WeakHahsMap. This is line 324 in TransactionReaper.java.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:17 p.m.
New subject: [JBoss JIRA] Commented: (JBTM-213) Threads in endless loop in TransactionReaper.
[ http://jira.jboss.com/jira/browse/JBTM-213?page=comments#action_12361038 ]
Jonathan Halliday commented on JBTM-213:
----------------------------------------
Right, that's a particularly big "D'Oh" especially since the declaration
for the troublesome data structure is on the very next line to one that is synchronized to
avoid this same issue. 'scuse me whilst I die of embarrassment.
...
private SortedSet _transactions = Collections.synchronizedSortedSet(new TreeSet()); // C
of ReaperElement
private Map _timeouts = new WeakHashMap(); // key = Reapable, value = Integer
...
Threads in endless loop in TransactionReaper.
---------------------------------------------
Key: JBTM-213
URL: http://jira.jboss.com/jira/browse/JBTM-213
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JTA Implementation
Reporter: Phillip Thurmond
Assigned To: Mark Little
After generating a load against JBossAS 4.2 beta1, the cpu is pegged at 100% even after
the load has stopped. A thread dump reveals several threads at
TransactionReaper.insert(). These threads are all doing a WeakHashMap.get(). Looking at
TransactionReaper, I believe this is caused by unsynchronized access to the _timeouts
WeakHahsMap. This is line 324 in TransactionReaper.java.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:35 p.m.
New subject: [JBoss JIRA] Assigned: (JBTM-213) Threads in endless loop in TransactionReaper.
[ http://jira.jboss.com/jira/browse/JBTM-213?page=all ]
Mark Little reassigned JBTM-213:
--------------------------------
Assignee: Jonathan Halliday (was: Mark Little)
Threads in endless loop in TransactionReaper.
---------------------------------------------
Key: JBTM-213
URL: http://jira.jboss.com/jira/browse/JBTM-213
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JTA Implementation
Affects Versions: 4.2.3.SP1
Reporter: Phillip Thurmond
Assigned To: Jonathan Halliday
Fix For: 4.2.3.SP1
After generating a load against JBossAS 4.2 beta1, the cpu is pegged at 100% even after
the load has stopped. A thread dump reveals several threads at
TransactionReaper.insert(). These threads are all doing a WeakHashMap.get(). Looking at
TransactionReaper, I believe this is caused by unsynchronized access to the _timeouts
WeakHahsMap. This is line 324 in TransactionReaper.java.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:35 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-213) Threads in endless loop in TransactionReaper.
[ http://jira.jboss.com/jira/browse/JBTM-213?page=all ]
Mark Little updated JBTM-213:
-----------------------------
Fix Version/s: 4.2.3.SP1
Affects Version/s: 4.2.3.SP1
Threads in endless loop in TransactionReaper.
---------------------------------------------
Key: JBTM-213
URL: http://jira.jboss.com/jira/browse/JBTM-213
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JTA Implementation
Affects Versions: 4.2.3.SP1
Reporter: Phillip Thurmond
Assigned To: Jonathan Halliday
Fix For: 4.2.3.SP1
After generating a load against JBossAS 4.2 beta1, the cpu is pegged at 100% even after
the load has stopped. A thread dump reveals several threads at
TransactionReaper.insert(). These threads are all doing a WeakHashMap.get(). Looking at
TransactionReaper, I believe this is caused by unsynchronized access to the _timeouts
WeakHahsMap. This is line 324 in TransactionReaper.java.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:06 a.m.
New subject: [JBoss JIRA] Updated: (JBTM-213) Threads in endless loop in TransactionReaper.
[ http://jira.jboss.com/jira/browse/JBTM-213?page=all ]
Jonathan Halliday updated JBTM-213:
-----------------------------------
Affects Version/s: 4.2.3.SP2
(was: 4.2.3.SP1)
Threads in endless loop in TransactionReaper.
---------------------------------------------
Key: JBTM-213
URL: http://jira.jboss.com/jira/browse/JBTM-213
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JTA Implementation
Affects Versions: 4.2.3.SP1
Reporter: Phillip Thurmond
Assigned To: Jonathan Halliday
Fix For: 4.2.3.SP2
After generating a load against JBossAS 4.2 beta1, the cpu is pegged at 100% even after
the load has stopped. A thread dump reveals several threads at
TransactionReaper.insert(). These threads are all doing a WeakHashMap.get(). Looking at
TransactionReaper, I believe this is caused by unsynchronized access to the _timeouts
WeakHahsMap. This is line 324 in TransactionReaper.java.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:06 a.m.
New subject: [JBoss JIRA] Updated: (JBTM-213) Threads in endless loop in TransactionReaper.
[ http://jira.jboss.com/jira/browse/JBTM-213?page=all ]
Jonathan Halliday updated JBTM-213:
-----------------------------------
Fix Version/s: 4.2.3.SP2
(was: 4.2.3.SP1)
Affects Version/s: 4.2.3.SP1
(was: 4.2.3.SP2)
Threads in endless loop in TransactionReaper.
---------------------------------------------
Key: JBTM-213
URL: http://jira.jboss.com/jira/browse/JBTM-213
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JTA Implementation
Affects Versions: 4.2.3.SP1
Reporter: Phillip Thurmond
Assigned To: Jonathan Halliday
Fix For: 4.2.3.SP2
After generating a load against JBossAS 4.2 beta1, the cpu is pegged at 100% even after
the load has stopped. A thread dump reveals several threads at
TransactionReaper.insert(). These threads are all doing a WeakHashMap.get(). Looking at
TransactionReaper, I believe this is caused by unsynchronized access to the _timeouts
WeakHahsMap. This is line 324 in TransactionReaper.java.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:08 a.m.
New subject: [JBoss JIRA] Resolved: (JBTM-213) Threads in endless loop in TransactionReaper.
[ http://jira.jboss.com/jira/browse/JBTM-213?page=all ]
Jonathan Halliday resolved JBTM-213.
------------------------------------
Resolution: Done
Fixed in 4.2.3.SP2 and trunk.
Threads in endless loop in TransactionReaper.
---------------------------------------------
Key: JBTM-213
URL: http://jira.jboss.com/jira/browse/JBTM-213
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JTA Implementation
Affects Versions: 4.2.3.SP1
Reporter: Phillip Thurmond
Assigned To: Jonathan Halliday
Fix For: 4.2.3.SP2
After generating a load against JBossAS 4.2 beta1, the cpu is pegged at 100% even after
the load has stopped. A thread dump reveals several threads at
TransactionReaper.insert(). These threads are all doing a WeakHashMap.get(). Looking at
TransactionReaper, I believe this is caused by unsynchronized access to the _timeouts
WeakHahsMap. This is line 324 in TransactionReaper.java.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6442
days inactive
6444
days old
7 comments
3 participants
participants (3)
-
Jonathan Halliday (JIRA) -
Mark Little (JIRA)
-
Phillip Thurmond (JIRA)