You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "K (JIRA)" <ji...@apache.org> on 2018/09/13 13:17:00 UTC
[jira] [Created] (TOMEE-2235) not getting latest tomee plume to
work as a windows service
K created TOMEE-2235:
------------------------
Summary: not getting latest tomee plume to work as a windows service
Key: TOMEE-2235
URL: https://issues.apache.org/jira/browse/TOMEE-2235
Project: TomEE
Issue Type: Bug
Components: TomEE Core Server
Affects Versions: 7.1
Environment: Tomee Plume 7.1.0 & Tomee Plus 1.7.2
Windows 10 & Server 2008
JDK 9.0.1 & 10.0.2
JRE 10.0.2
(plus I have some older JDK's & JRE's)
Reporter: K
Attachments: apache-tomee-windows-service-error.png, apache-tomee-windows-service-error2.png
I originally had just the Tomee Plus 1.7.2, which ran as a windows service, but, since I upgraded the jdk's to 9.0.1, the windows service stopped running automatically (and I can't even get it to start when I click the start button in the windows services window). The errors I get for this are attached, but in essence, they either say "... service specific error code 4" or "Error: 1053 The service did not respond to the start or control request in a timely fashion."
From command prompt, when I go to the tomee bin directory and select the service.bat file, I go the error "The JAVA_HOME environment variable is not defined correctly ...". When I checked the service.bat file, I see it's pointing to a sub folder within the main JAVA_HOME folder, that no longer exists.
The Windows Event Viewer logs say "The Apache TomEE service terminated with service-specific error The system cannot open the file.."
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)