Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
1.5.1
-
None
-
None
-
Windows 7 x64, Windows Server 2008 R2
Description
Hello,
There's (yet another) bug in TomEE registration as a service : it fails at least on the two x64 Windows operating systems I have tested: Windows 7 and Windows Server 2008 R2.
Steps to reproduce:
Unzip TomEE+ 1.5.1 distribution to a given directory (here:E:\NoSave\tomEE)
In a Windows Command Prompt, type:
set JAVA_HOME=c:\Program Files\Java\jdk1.7.0_09
cd E:\NoSave\tomEE\apache-tomee-plus-1.5.1\bin
service.bat install
Installing the service 'TomEE' ...
Using CATALINA_HOME: "E:\NoSave\tomEE\apache-tomee-plus-1.5.1"
Using CATALINA_BASE: "E:\NoSave\tomEE\apache-tomee-plus-1.5.1"
Using JAVA_HOME: "c:\Program Files\Java\jdk1.7.0_09"
Using JRE_HOME: "c:\Program Files\Java\jdk1.7.0_09\jre"
Using JVM: "c:\Program Files\Java\jdk1.7.0_09\jre\bin\server\jvm.dll"
""E:\NoSave\tomEE\apache-tomee-plus-1.5.1\bin\TomEE.AMD64.exe"" //IS//TomEE
[2012-12-15 00:11:52] [error] Unrecognized cmd option E:\NoSave\tomEE\apache-tomee-plus-1.5.1\bin\TomEE.AMD64.exe
[2012-12-15 00:11:52] [error] Invalid command line arguments
[2012-12-15 00:11:52] [error] Commons Daemon procrun failed with exit value: 1 (Failed to parse command line arguments)
Failed installing 'TomEE' service
This is really a pity, since registering TomEE as a Windows service was already broken in 1.0.0, 1.5.0, each time in a slightly different maner (the service registration issue on 1.5.0 is linked to this JIRA: https://issues.apache.org/jira/browse/TOMEE-446, but that's not the same output so I have opened a new 1.5.0-specific JIRA).
Since 1.5.1 is released, I badly need a by-pass, otherwise I feel like TomEE will be kicked out my company
Alex.