-
Bug
-
Resolution: Not A Defect
-
Major
-
None
-
Hudson 1.352 master on Linux, slave (1.352) on Windows Server 2003
The slave is installed as a windows service.
The command line was (according to hudson-slave.wrapper.log):
2010-03-29 12.29.46 - Starting C:\Program Files\Java\jre6\bin\java.exe -Xrs -jar "C:\DeveloperTools\HudsonSlave\slave.jar" -jnlpUrl http://hudson.mondidinamici.com/computer/Ceres/slave-agent.jnlp
The slave died because of an exception reported in slave.out.log
#
- A fatal error has been detected by the Java Runtime Environment:
# - EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x037235e0, pid=1632, tid=1388
# - JRE version: 6.0_17-b04
- Java VM: Java HotSpot(TM) Client VM (14.3-b01 mixed mode, sharing windows-x86 )
- Problematic frame:
- C 0x037235e0
# - An error report file with more information is saved as:
- C:\WINDOWS\system32\hs_err_pid1632.log
# - If you would like to submit a bug report, please visit:
- http://java.sun.com/webapps/bugreport/crash.jsp
- The crash happened outside the Java Virtual Machine in native code.
- See problematic frame for where to report the bug.
#
I have attached also C:\WINDOWS\system32\hs_err_pid1632.log file.
- is duplicated by
-
JENKINS-10582 slave connection breaks thru EXCEPTION_ACCESS_VIOLATION
- Closed
-
JENKINS-22864 JVM Failure:Windows Slave Connection Reset
- Closed