[
https://issues.jboss.org/browse/JBTM-1139?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1139:
-------------------------------------
Could it be a process was killed by the oom killer?
Log onto the machine that crashed and grep dmesg for "emor" (Memory)
[hudson@beacon ~]$ dmesg | grep emo
That said, the dmesg isn't cleared on each node, so you will probably need to know the
current state of dmesg and the pre-existence of these messages on each node.
e.g. beacon atm has:
[hudson@beacon ~]$ dmesg | grep emo
Memory: 4100300k/4202496k available (2545k kernel code, 93488k reserved, 1753k data, 196k
init)
Non-volatile memory driver v1.2
[<ffffffff802c1bc6>] out_of_memory+0x8b/0x203
Out of memory: Killed process 17059, UID 502, (java).
[<ffffffff802c1bc6>] out_of_memory+0x8b/0x203
[<ffffffff802c1bc6>] out_of_memory+0x8b/0x203
[<ffffffff8029dc2e>] autoremove_wake_function+0x0/0x2e
Out of memory: Killed process 24308, UID 502, (java).
No timestamps :(
BACrashDuringOnePhaseCommit:SingleCoordinatorCompletionParticipantCloseTest Failed to
start
-------------------------------------------------------------------------------------------
Key: JBTM-1139
URL:
https://issues.jboss.org/browse/JBTM-1139
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 5.0.0.M1
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.16.4, 5.0.0.M2
Looking at the following log:
http://172.17.131.2/view/XTS%20recovery/job/narayana-xts-recovery-java6/8...
You will see that the server starts for the first test, but no scenario is ran:
{code}
16:37:24,606 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS
7.1.2.Final-SNAPSHOT "Brontes" started in 9755ms - Started 272 of 360 services
(87 services are passive or on-demand)
16:37:24,783 INFO [org.jboss.as.repository] (management-handler-thread - 4) JBAS014900:
Content added at location
/home/hudson/workspace/narayana-xts-recovery-java6/jboss-as/build/target/jboss-as-7.1.2.Final-SNAPSHOT/standalone/data/content/9c/b09ed5c8a11739141e8a5b2e5eefb74c508183/content
DEBUG [Remoting "endpoint" read-1] (WorkerThread.java:88)
org.xnio.nio.WorkerThread.run(WorkerThread.java:88) - Started channel thread 'Remoting
"endpoint" read-1', selector sun.nio.ch.EPollSelectorImpl@308bd98e
DEBUG [Remoting "endpoint" write-1] (WorkerThread.java:88)
org.xnio.nio.WorkerThread.run(WorkerThread.java:88) - Started channel thread 'Remoting
"endpoint" write-1', selector sun.nio.ch.EPollSelectorImpl@384f33c1
DEBUG [Remoting "endpoint" task-4] (VersionedConectionFactory.java:129)
org.jboss.remotingjmx.VersionedConectionFactory$ClientVersionReceiver.handleMessage(VersionedConectionFactory.java:129)
- Available version (Versions 0x01)
DEBUG [Remoting "endpoint" task-4] (VersionedConectionFactory.java:135)
org.jboss.remotingjmx.VersionedConectionFactory$ClientVersionReceiver.handleMessage(VersionedConectionFactory.java:135)
- Calling a stable server
Apr 23, 2012 4:37:25 PM
org.jboss.arquillian.container.test.impl.client.container.ClientContainerController kill
INFO: Hard killing of a server instance
Apr 23, 2012 4:37:25 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
INFO: waiting for byteman to kill server
Apr 23, 2012 4:37:36 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
INFO: jboss-as is alive
Apr 23, 2012 4:37:47 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
INFO: jboss-as is alive
Apr 23, 2012 4:37:58 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
INFO: jboss-as is alive
Apr 23, 2012 4:38:09 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
INFO: jboss-as is alive
Apr 23, 2012 4:38:20 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
INFO: jboss-as is alive
Apr 23, 2012 4:38:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
INFO: jboss-as is alive
Apr 23, 2012 4:38:42 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
INFO: jboss-as is alive
Apr 23, 2012 4:38:53 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
INFO: jboss-as is alive
Apr 23, 2012 4:39:04 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
INFO: jboss-as is alive
Apr 23, 2012 4:39:16 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
{code}
The trace output for this test is also empty:
http://172.17.131.2/view/XTS%20recovery/job/narayana-xts-recovery-java6/8...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira