|
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Bogdan Dziedzic [Atlassian] - 25/Jun/07 08:02 PM
It looks like the issue here is that Tomcat doesn't have 64bit support: http://blog.advantern.com/2007/06/running-tomcat-as-64-bit-windows.html
 Bogdan,
Is this really a Tomcat issue and not a JIRA bug? I think we should update our docs (the section that talks about running JIRA as a Windows Service) to mention this problem. What do you think? Cheers, Yes, it is a Tomcat issue. Although since Tomcat is bundled into JIRA standalone I thought that it is also our issue.
Maybe we should have to two separate installers one for i368 and the other for x64? The standalone version suppose to "work of the box" - no adjustments needed  also I think next OS from MS is going to be x64 only.
Cheers, So does JIRA's installer fail when run on a 64 bit Windows while trying to install it as a service?
I thought the problem only happens when users try to use 64bit JDK with JIRA Standalone. Cheers, Hey Bogdan,
Any update on this? Cheers, If you use the installer and not set JAVA_HOME you will experience the installer bug where the installer is failing to set windows service correctly - mentioned at JRA-12785
. Although if you set JAVA_HOME to x64 bit JDK, you will get right into this problem. By the way, the installer issue is closed, but I have heard that it might not work in some cases (Jeff). Despite that, if you have JAVA_HOME x64 starting JIRA from startup_bundled_jre.bat you will receive exactly the same error (who do that anyway). I have not performed any other test, but those ones. If you take into account the above, I think it is a formula for a few support requests. Bogi Thanks for the information.
The bug
If there is a problem regarding this, can you ask Jeff to log the problem as a bug? Cheers, Currently we don't have any resources to perform additional testing.
Steve is working on creating a new hardware platform for testing purposes. Bogi – ATLASSIAN - http://www.atlassian.com Australia's Fastest Growing Software Company 2002-06 [BRW Magazine] Hey,
Thanks for the info again. I have spoken to Jeff and he said that there was nothing wrong with the
Did we actually do any testing on the x64 plantform? If so, on what hardware?
Awesome! Great work. Cheers, I have done a quick test and would like to confirm that the standalone version of JIRA 3.9.2 installed on a clean windows xp x64 will not start the service.
The jakarta_service log file is recoded: [2007-06-28 05:43:22] [info] Service JIRA280607054248 name Atlassian JIRA Enterprise Edition 3.9.2 [2007-06-28 05:43:23] [info] Service JIRA280607054248 installed [2007-06-28 05:43:23] [info] Procrun finished. [2007-06-28 05:43:23] [info] Updating service... [2007-06-28 05:43:24] [info] Service JIRA280607054248 updated [2007-06-28 05:43:24] [info] Update service finished. [2007-06-28 05:43:24] [info] Procrun finished. [2007-06-28 05:43:24] [info] Updating service... [2007-06-28 05:43:24] [info] Service JIRA280607054248 updated [2007-06-28 05:43:24] [info] Update service finished. [2007-06-28 05:43:24] [info] Procrun finished. [2007-06-28 05:43:25] [info] Running Service... [2007-06-28 05:43:25] [info] Starting service... [2007-06-28 05:43:25] [173 javajni.c] [error] The specified module could not be found. [2007-06-28 05:43:25] [924 prunsrv.c] [error] Failed creating java C:\JIRA-Enterprise-3.9.2\jre\bin\client\jvm.dll [2007-06-28 05:43:25] [1179 prunsrv.c] [error] ServiceStart returned 1 [2007-06-28 05:43:25] [info] Run service finished. Thanks!
Looks like we have a problem. Again, thank you for taking the time to do this. We realy appreciate it! Cheers, I've installed JIRA 3.10.2 EE (zip standalone) on a clean win xp x64, JAVA_HOME was set to Sun JDK 1.6
C:\>"%java_home%\bin\java" -version java version "1.6.0_02" Java(TM) SE Runtime Environment (build 1.6.0_02-b05) Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_02-b05, mixed mode) The service was installed successfully, although couldn't be started. [2007-09-06 16:12:49] [info] Running Service... [2007-09-06 16:12:49] [info] Starting service... [2007-09-06 16:12:49] [173 javajni.c] [error] %1 is not a valid Win32 application. [2007-09-06 16:12:49] [924 prunsrv.c] [error] Failed creating java C:\Program Files\Java\jdk1.6.0_02\jre\bin\server\jvm.dll [2007-09-06 16:12:49] [1179 prunsrv.c] [error] ServiceStart returned 1 [2007-09-06 16:12:49] [info] Run service finished. [2007-09-06 16:12:49] [info] Procrun finished. I don't think, this issue is somehow related to I'll check again, if apache.org has any thing on x64 support for Tomcat. Well... it seems to me that a solution to this problem is given in a mini HOW-TO at http://issues.apache.org/bugzilla/attachment.cgi?id=20323
in bugs at apache.org issues ID 39327 and more generic one 35869. So far there isn't much development happening on the Apache web regarding to this issue.Extract from it: 1) Download and install the 64 bit edition of Java for Windows 2) Download and install the 32 bit version of Tomcat 5.5.x for Windows 3) Recompile 'procrun' (which is the binary $CATALINA_ROOT/bin/Tomcat5.exe in the Windows distribution) using the patch listed in Bugzilla ticket 39327 (http://issues.apache.org/bugzilla/show_bug.cgi?id=39327) and replace Tomcat5.exe with the newly compiled "prunsrv.exe". 4) Since Tomcat installs it's registry keys under the WOW6432Node you must add the registry keys to Windows which are listed at the end of this email (don't forget to adjust them to use your server's paths for the JVM and Tomcat) or move your own registry keys via the export/import tool in regedit. 5) Using regedit, edit the HKLM\SOFTWARE\Apache Software Foundation\Procrun 2.0\Tomcat5\Parameters\Java\Options and adjust for memory settings appropriate to your environment. 6) Start (or restart) the Apache Tomcat service. Note that although you can stop/start the Tomcat service via the bundled Tomcat service helper, if you need to change its configuration you will need to manually edit the registry key mentioned in step 5. The problem is with Tomcat, and more specifically with Commons Daemon that Tomcat uses.
If this issue is hurting you please add comments to Tomcat's: This issue on the apache side is tracked at https://issues.apache.org/jira/browse/DAEMON-76
Tomcat running as a 64-bit service on a Windows 2003 R2 64-bit server.
I have been able to get Tomcat running as a 64-bit service on Windows 2003 R2 64-bit server using the 64-bit wrappers mentioned in the above links (I have attached them to this issue). Additional information was used from the following links:
http://blog.granilus.com/2007/06/running-tomcat-as-64-bit-windows.html http://mail-archives.apache.org/mod_mbox/tomcat-users/200701.mbox/%3CFE41002D68817843B6D00DFE12D89C3C4274B0@EXCHANGE01.connaughtplc.local%3E
The key is to use the the Tomcat zip download not the service installer. Make sure that you have a 64-bit JDK installed. After unzipping Tomcat, run "service install" at the command prompt. Download the attached wrappers and rename them to tomcat5.exe and tomcat5w.exe. You should be able to run tomcat5w to configure your service. Start the service and you should be up and running in 64-bits. Hi David,
Thank you for sharing this with us! We really appreciate your help. Cheers, |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Third-party issue
Open
Critical
JIRA doesn't run as a Windows service on JDK 1.5 x64 edition
and in the log file was recoded: