Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-12293

Installing Confluence as a service on XP-64 fails due to 32-bit binaries of Tomcat

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 2.9
    • 2.8.1
    • None
    • Used the standard 2.8.1 zip file and did a standard installation on a windows XP 64-bit SP2 machine using a personal Confluence License. I am using JDK 6 Update 6 (x64 version).

      Confluence runs fine except when trying to set it up as a service. Registering the service using service.bat works fine. However, when trying to start the service windows indicates an error 0 is returned by tomcat.

      When taking a look in the logs, the following error messages are found (jakarta_service_DDMMYYYY.log):

      [2008-06-30 23:40:21] [info] Running Service...
      [2008-06-30 23:40:21] [info] Starting service...
      [2008-06-30 23:40:21] [174 javajni.c] [error] %1 is not a valid Win32 application.
      [2008-06-30 23:40:21] [947 prunsrv.c] [error] Failed creating java C:\Program Files\Java\jdk1.6.0_06\jre\bin\server\jvm.dll
      [2008-06-30 23:40:21] [1202 prunsrv.c] [error] ServiceStart returned 1
      [2008-06-30 23:40:25] [info] Run service finished.
      [2008-06-30 23:40:25] [info] Procrun finished.

      After replacing the tomcat.exe and tomcatw.exe binaries by 64-bit versions, downloaded from the internet everything seems to work fine.

      The following links are related:

      I think either the installation guide should be adjusted to indicate this problem for 64-bit users (current verions) or the installation package should be adjusted such that the right version of tomcat is called, depending on the OS (new versions).

            [CONFSERVER-12293] Installing Confluence as a service on XP-64 fails due to 32-bit binaries of Tomcat

            TonyA added a comment -

            Just to summarize, this is a Tomcat bug, and it still isn't fixed in release versions. The replacement binaries need to come from the trunk version of tomcat.

            There is a knowledgebase article that summarizes the problem and the workaround here:

            http://confluence.atlassian.com/display/CONFKB/Problems+installing+Confluence+as+a+service+on+a+Windows+64bit

            TonyA added a comment - Just to summarize, this is a Tomcat bug, and it still isn't fixed in release versions. The replacement binaries need to come from the trunk version of tomcat. There is a knowledgebase article that summarizes the problem and the workaround here: http://confluence.atlassian.com/display/CONFKB/Problems+installing+Confluence+as+a+service+on+a+Windows+64bit

            The bug is "Fixed" but where is the fix? I'm expiriencing the problem on WinServer x64 with Confluence 2.10.2

            Sergei Dorogin added a comment - The bug is "Fixed" but where is the fix? I'm expiriencing the problem on WinServer x64 with Confluence 2.10.2

            b added a comment -

            Hi Atlassian-Team,

            if we replace the tomcat*.exe files, is support from Atlassian still valid?

            Regards,
            Stefan

            b added a comment - Hi Atlassian-Team, if we replace the tomcat*.exe files, is support from Atlassian still valid? Regards, Stefan

            David Yu added a comment -

            David Yu added a comment - Tomcat 5 builds here: http://svn.apache.org/viewvc/tomcat/connectors/trunk/procrun/bin/

            b added a comment -

            Hi,

            where can i find the suitable tomcat.exe and tomcatw.exe 64-bit binaries for Confluence 2.9.2?

            Thanks!

            b added a comment - Hi, where can i find the suitable tomcat.exe and tomcatw.exe 64-bit binaries for Confluence 2.9.2? Thanks!

            You can find the latest 6.x 32bit as well as the amd64 and ia64 builds here:

            http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/res/procrun/

            Sam Johnston added a comment - You can find the latest 6.x 32bit as well as the amd64 and ia64 builds here: http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/res/procrun/

            Hi Bert,

            Thanks for raising this. We have now documented on http://confluence.atlassian.com/display/DOC/Start+Confluence+automatically+on+Windows+as+a+Service that a 32-bit JDK is required to start Confluence as a service.

            Cheers,
            Andrew Lynch

            Andrew Lynch (Inactive) added a comment - Hi Bert, Thanks for raising this. We have now documented on http://confluence.atlassian.com/display/DOC/Start+Confluence+automatically+on+Windows+as+a+Service that a 32-bit JDK is required to start Confluence as a service. Cheers, Andrew Lynch

            David,

            that's a good question.

            Actually, I wanted to include that link in my initial post, but I couldn't reproduce the google-search that brought me to the forum where the 64-bit executables were linked...

            My best suggestion is to search for terms like "tomcat service error 0 not a valid win32" or similar...

            good luck,
            Bert

            Bert Pluymers added a comment - David, that's a good question. Actually, I wanted to include that link in my initial post, but I couldn't reproduce the google-search that brought me to the forum where the 64-bit executables were linked... My best suggestion is to search for terms like "tomcat service error 0 not a valid win32" or similar... good luck, Bert

            I'm running into the same issue. Where did you download the tomcat.exe and tomcatw.exe 64-bit binaries?

            David Gitman added a comment - I'm running into the same issue. Where did you download the tomcat.exe and tomcatw.exe 64-bit binaries?

              Unassigned Unassigned
              2051a32c637d Bert Pluymers
              Affected customers:
              0 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: