12:51 a.m.
OutOfMemory Errors
------------------
Key: JBAS-4386
URL: http://jira.jboss.com/jira/browse/JBAS-4386
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-4.2.0.GA
Environment: x86_64, Windows 2003, Sun JVM
Reporter: Richard Achmatowicz
Priority: Blocker
The AS testsuite is encountering OOMEs during testing against the 'all'
configuration.
The testsuite completes its run, and the problem is detected by noting that only 4022 of
the 4103 tests in the testsuite have completed - the remainder have timed out due to an
unresponsive server. Upon inspection of the server logs, the OOME messages are
discovered.
I have attached the server.log and output.log from the AS server, as well as the test.log
from the client side testsuite. These logs are not complete, as I terminated the testsuite
run after noticing the error.
It is not clear which tests are causing the OOME. By looking at the timestamps on both
logs, and noting that the first OOME occurred at 14:49:05 in the server log, this was at
the time that the test org.jboss.test.jmx.test.RedeployStressTestCase was executing on the
client side, but rerunning that test with a newly started AS did not reproduce the error.
--
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
1:09 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-4386) OutOfMemory Errors
[ http://jira.jboss.com/jira/browse/JBAS-4386?page=comments#action_12361080 ]
Richard Achmatowicz commented on JBAS-4386:
-------------------------------------------
I'm putting my comments on the JBPAPP issue linked to this one.
OutOfMemory Errors
------------------
Key: JBAS-4386
URL: http://jira.jboss.com/jira/browse/JBAS-4386
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-4.2.0.GA
Environment: x86_64, Windows 2003, Sun JVM
Reporter: Richard Achmatowicz
Priority: Blocker
The AS testsuite is encountering OOMEs during testing against the 'all'
configuration.
The testsuite completes its run, and the problem is detected by noting that only 4022 of
the 4103 tests in the testsuite have completed - the remainder have timed out due to an
unresponsive server. Upon inspection of the server logs, the OOME messages are
discovered.
I have attached the server.log and output.log from the AS server, as well as the test.log
from the client side testsuite. These logs are not complete, as I terminated the testsuite
run after noticing the error.
It is not clear which tests are causing the OOME. By looking at the timestamps on both
logs, and noting that the first OOME occurred at 14:49:05 in the server log, this was at
the time that the test org.jboss.test.jmx.test.RedeployStressTestCase was executing on the
client side, but rerunning that test with a newly started AS did not reproduce the error.
--
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:33 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-4386) OutOfMemory Errors
[ http://jira.jboss.com/jira/browse/JBAS-4386?page=all ]
Dimitris Andreadis updated JBAS-4386:
-------------------------------------
Affects Version/s: JBossAS-4.2.0.CR2
(was: JBossAS-4.2.0.GA)
It can't be 'affects 4.2.0.GA', it's not released yet. Do you mean CR1/CR2
?
OutOfMemory Errors
------------------
Key: JBAS-4386
URL: http://jira.jboss.com/jira/browse/JBAS-4386
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-4.2.0.CR2
Environment: x86_64, Windows 2003, Sun JVM
Reporter: Richard Achmatowicz
Priority: Blocker
The AS testsuite is encountering OOMEs during testing against the 'all'
configuration.
The testsuite completes its run, and the problem is detected by noting that only 4022 of
the 4103 tests in the testsuite have completed - the remainder have timed out due to an
unresponsive server. Upon inspection of the server logs, the OOME messages are
discovered.
I have attached the server.log and output.log from the AS server, as well as the test.log
from the client side testsuite. These logs are not complete, as I terminated the testsuite
run after noticing the error.
It is not clear which tests are causing the OOME. By looking at the timestamps on both
logs, and noting that the first OOME occurred at 14:49:05 in the server log, this was at
the time that the test org.jboss.test.jmx.test.RedeployStressTestCase was executing on the
client side, but rerunning that test with a newly started AS did not reproduce the error.
--
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
9:59 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4386) OutOfMemory Errors
[ http://jira.jboss.com/jira/browse/JBAS-4386?page=comments#action_12362916 ]
David commented on JBAS-4386:
-----------------------------
I may be experiencing this issue as well.
I have many of these in my logs:
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:574)
at
org.jboss.remoting.transport.socket.SocketServerInvoker.start(SocketServerInvoker.java:235)
at org.jboss.remoting.transport.Connector.start(Connector.java:322)
at org.jboss.remoting.Client.addListener(Client.java:894)
at
org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:221)
at
org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:287)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectio
nDelegate$aop(ClientConnectionFactoryDelegate.java:146)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFacto
ryDelegate$createConnectionDelegate_4579211046834694258.java)
at
org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83)
at
org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFacto
ryDelegate$createConnectionDelegate_4579211046834694258.java)
at
org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFacto
ryDelegate$createConnectionDelegate_4579211046834694258.java)
at
org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFacto
ryDelegate$createConnectionDelegate_4579211046834694258.java)
at
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
at
org.jboss.jms.client.container.ClusteringAspect.handleCreateConnectionDelegate(ClusteringAspect.java:126)
at sun.reflect.GeneratedMethodAccessor316.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
at
org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientCluste
redConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
at
org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71)
at
org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientCluste
redConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
at
org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
at
org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientCluste
redConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
at
org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.createConnectionDelegate(ClientClusteredConnectionFactoryDelegate.ja
va)
at
org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
at
org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:87)
at
org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:82)
Seem to originate from jboss messaging
I did a stack dump(kill -3) and found that there 876 AcceptorThread and 1752
ServerSocketRefresh threads. I'll attach the thread dump.
I'm using JBoss 4.2.0.GA
OutOfMemory Errors
------------------
Key: JBAS-4386
URL: http://jira.jboss.com/jira/browse/JBAS-4386
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-4.2.0.CR2
Environment: x86_64, Windows 2003, Sun JVM
Reporter: Richard Achmatowicz
Priority: Blocker
Attachments: joker-oom-thread-dump
The AS testsuite is encountering OOMEs during testing against the 'all'
configuration.
The testsuite completes its run, and the problem is detected by noting that only 4022 of
the 4103 tests in the testsuite have completed - the remainder have timed out due to an
unresponsive server. Upon inspection of the server logs, the OOME messages are
discovered.
I have attached the server.log and output.log from the AS server, as well as the test.log
from the client side testsuite. These logs are not complete, as I terminated the testsuite
run after noticing the error.
It is not clear which tests are causing the OOME. By looking at the timestamps on both
logs, and noting that the first OOME occurred at 14:49:05 in the server log, this was at
the time that the test org.jboss.test.jmx.test.RedeployStressTestCase was executing on the
client side, but rerunning that test with a newly started AS did not reproduce the error.
--
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
10:32 p.m.
New subject: [JBoss JIRA] Closed: (JBAS-4386) OutOfMemory Errors
[
https://jira.jboss.org/jira/browse/JBAS-4386?page=com.atlassian.jira.plug...
]
Shelly McGowan closed JBAS-4386.
--------------------------------
Resolution: Cannot Reproduce Bug
OOM no longer seen in AS 4.2.x testsuite runs.
OutOfMemory Errors
------------------
Key: JBAS-4386
URL: https://jira.jboss.org/jira/browse/JBAS-4386
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-4.2.0.CR2
Environment: x86_64, Windows 2003, Sun JVM
Reporter: Richard Achmatowicz
Priority: Blocker
Attachments: joker-oom-thread-dump
The AS testsuite is encountering OOMEs during testing against the 'all'
configuration.
The testsuite completes its run, and the problem is detected by noting that only 4022 of
the 4103 tests in the testsuite have completed - the remainder have timed out due to an
unresponsive server. Upon inspection of the server logs, the OOME messages are
discovered.
I have attached the server.log and output.log from the AS server, as well as the test.log
from the client side testsuite. These logs are not complete, as I terminated the testsuite
run after noticing the error.
It is not clear which tests are causing the OOME. By looking at the timestamps on both
logs, and noting that the first OOME occurred at 14:49:05 in the server log, this was at
the time that the test org.jboss.test.jmx.test.RedeployStressTestCase was executing on the
client side, but rerunning that test with a newly started AS did not reproduce the error.
--
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
5730
days inactive
6352
days old
4 comments
4 participants
participants (4)
-
David (JIRA) -
Dimitris Andreadis (JIRA)
-
Richard Achmatowicz (JIRA)
-
Shelly McGowan (JIRA)