Alex the Rocker created TOMEE-652:
-------------------------------------

             Summary: service.bat install fails on 64-bit Windows with TomEE+ 
1.5.1
                 Key: TOMEE-652
                 URL: https://issues.apache.org/jira/browse/TOMEE-652
             Project: TomEE
          Issue Type: Bug
    Affects Versions: 1.5.1
         Environment: Windows 7 x64, Windows Server 2008 R2
            Reporter: Alex the Rocker
            Priority: Critical


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.

Since 1.5.1 is released, I badly need a by-pass, otherwise I feel like TomEE 
will be kicked out my company :(

Alex.





--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to