• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • core
    • None
    • Microsoft Windows Server 2003 R2
      Microsoft Windows 2008 server w/Tomcat
      Microsoft Windows XP SP3
      Microsoft Windows 7 x64 SP1
      Microsoft Windows Server 2012

      When I try to start Jenkins 1.540, it attempts to do so and eventually fails. When it fails, it tries to start again, which then fails. This repeats indefinitely. I've attached a log file from one such iteration.

      I am able to start 1.539 successfully. I've attached the log file from this as well.

        1. hs_err_pid1000.log
          17 kB
        2. hs_err_pid1788.log
          22 kB
        3. hs_err_pid35184.log
          24 kB
        4. hs_err_pid4584.log
          13 kB
        5. hs_err_pid4968.log
          20 kB
        6. hs_err_pid5660.log
          21 kB
        7. hs_err_pid5960.log
          21 kB
        8. jenkins.out.log
          0.8 kB
        9. jenkins 1.539.err.log
          40 kB
        10. jenkins 1.540.err.log
          27 kB

          [JENKINS-20630] Jenkins fails to start

          Matt Kraai created issue -

          Matt Kraai added a comment -

          Java appears to be crashing. jenkins.out.log contains:

          Running from: C:\Jenkins\jenkins.war
          
          webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")
          
          Jenkins home directory: C:\Jenkins found at: EnvVars.masterEnvVars.get("JENKINS_HOME")
          
          
          [error occurred during error reporting (null), id 0xc0000005]
          
          #
          # A fatal error has been detected by the Java Runtime Environment:
          #
          #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x7c82a5c4, pid=1788, tid=1368
          #
          # JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
          # Java VM: Java HotSpot(TM) Client VM (24.45-b08 mixed mode, sharing windows-x86 )
          # Problematic frame:
          # C  [ntdll.dll+0x2a5c4]
          #
          # Failed to write core dump. 
          #
          # An error report file with more information is saved as:
          # C:\Jenkins\hs_err_pid1788.log
          #
          # If you would like to submit a bug report, please visit:
          #   http://bugreport.sun.com/bugreport/crash.jsp
          # The crash happened outside the Java Virtual Machine in native code.
          # See problematic frame for where to report the bug.
          #
          

          Matt Kraai added a comment - Java appears to be crashing. jenkins.out.log contains: Running from: C:\Jenkins\jenkins.war webroot: EnvVars.masterEnvVars.get( "JENKINS_HOME" ) Jenkins home directory: C:\Jenkins found at: EnvVars.masterEnvVars.get( "JENKINS_HOME" ) [error occurred during error reporting ( null ), id 0xc0000005] # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x7c82a5c4, pid=1788, tid=1368 # # JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18) # Java VM: Java HotSpot(TM) Client VM (24.45-b08 mixed mode, sharing windows-x86 ) # Problematic frame: # C [ntdll.dll+0x2a5c4] # # Failed to write core dump. # # An error report file with more information is saved as: # C:\Jenkins\hs_err_pid1788.log # # If you would like to submit a bug report, please visit: # http: //bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. #
          Matt Kraai made changes -
          Attachment New: hs_err_pid1788.log [ 24693 ]

          Michael H. added a comment - - edited

          Jenkins 1.540 also fails to start for me.
          I am running it on Windows 7 x64 as a Service.

          While 1.539 starts up fine 1.540 just dies at some point.

          I cannot find anything related to it in any of the log files.

          Michael H. added a comment - - edited Jenkins 1.540 also fails to start for me. I am running it on Windows 7 x64 as a Service. While 1.539 starts up fine 1.540 just dies at some point. I cannot find anything related to it in any of the log files.

          loyal parsons added a comment -

          Also failing for me on Win7, SP1, x64 as a Service. As noted by the others, 1.539 is fine and the standard log files have no error. There is a java error in ntdll.dll listed in the Event Viewer.

          loyal parsons added a comment - Also failing for me on Win7, SP1, x64 as a Service. As noted by the others, 1.539 is fine and the standard log files have no error. There is a java error in ntdll.dll listed in the Event Viewer.

          Michael H. added a comment - - edited

          A clean install on another Windows-7 machine using the 1.540 installer also fails for me. So it cannot be related to an old Jenkins installation.

          Michael H. added a comment - - edited A clean install on another Windows-7 machine using the 1.540 installer also fails for me. So it cannot be related to an old Jenkins installation.

          Adam Ocsvari added a comment -

          The same here:
          Windows7 x64, running Jenkins as a service. Before the update to 1.540, it was working fine.

          Adam Ocsvari added a comment - The same here: Windows7 x64, running Jenkins as a service. Before the update to 1.540, it was working fine.

          Andy Bigos added a comment - - edited

          +1. Running Win7 x64 as a service and got the same errors. Reverting to 1.539 works.

          Andy Bigos added a comment - - edited +1. Running Win7 x64 as a service and got the same errors. Reverting to 1.539 works.

          Confirmed: There is something wrong with 1.540 that causes the JVM it to crash on Windows just after startup.

          I have a very similar issue. Windows 8, java 7_45, downloaded the latest Windows install of Jenkins version 1.540. Ran the the msi install and ran this command as administrator:

          C:\Program Files (x86)\Jenkins>java -jar jenkins.war

          When it got to "INFO: Loaded all jobs" in the command console log output the JVM crashed and popped up a Java Virtual Machine has unexpected shut down dialog message.

          After a few more ties with no success I downloaded the previous build 1.539 war file from

          http://mirrors.jenkins-ci.org/war/1.539/

          Overwrote C:\Program Files (x86)\Jenkins>jenkins.war

          Ran this again

          C:\Program Files (x86)\Jenkins>java -jar jenkins.war

          and Jenkins started normally.

          Jonathan Johnson added a comment - Confirmed: There is something wrong with 1.540 that causes the JVM it to crash on Windows just after startup. I have a very similar issue. Windows 8, java 7_45, downloaded the latest Windows install of Jenkins version 1.540. Ran the the msi install and ran this command as administrator: C:\Program Files (x86)\Jenkins>java -jar jenkins.war When it got to "INFO: Loaded all jobs" in the command console log output the JVM crashed and popped up a Java Virtual Machine has unexpected shut down dialog message. After a few more ties with no success I downloaded the previous build 1.539 war file from http://mirrors.jenkins-ci.org/war/1.539/ Overwrote C:\Program Files (x86)\Jenkins>jenkins.war Ran this again C:\Program Files (x86)\Jenkins>java -jar jenkins.war and Jenkins started normally.

          Having the same issue running Jenkins 1.540 on Tomcat 7.0.47 on Windows Server 2008 R2 Standard. Tomcat is running as a Windows Service. Once I downgraded to 1.539 it starts up perfectly.

          Brandon Oakley added a comment - Having the same issue running Jenkins 1.540 on Tomcat 7.0.47 on Windows Server 2008 R2 Standard. Tomcat is running as a Windows Service. Once I downgraded to 1.539 it starts up perfectly.

            kohsuke Kohsuke Kawaguchi
            kraai Matt Kraai
            Votes:
            58 Vote for this issue
            Watchers:
            66 Start watching this issue

              Created:
              Updated:
              Resolved: