Here are a few tips that will help track down issues with the service
installation.
In the service.bat modify or add the following options (uninstall and
reinstall, and check logs):
--LogLevel=Debug
--LogJniMessages=1
Those options will reveal much more about what is going on during the
install and start-up.
There is also in the service.bat and service.readme.txt information on
setting JAVA_HOME locally:
rem The following line can be used to define a specific jre or jdk path
rem set "JAVA_HOME=C:/JDK"
Something I like to do personally, and may suggest adding to the default
batch, is to add a check for a local JRE or JDK in the bin directory:
REM Prefer a local JRE if we find one in the current directory
IF EXIST "%~dp0jre" (
SET "JRE_HOME=%~dp0"
GOTO gotJreHome
)
This way we you can just drop in a JRE or JDK of your choice into the bin
directory and be sure which one is being used to run the service.
And finally (this is a bug in our script), tuning the jvm memory in jvm mode
can only be performed by the service:
--JvmMs=512 ^
--JvmMx=1024 ^
--JvmSs=2048 ^
...and not ++JvmOptions "-Xss2048k;-Xmx1024m"
Andy.
--
View this message in context:
http://openejb.979440.n4.nabble.com/TomEE-as-a-Service-Windows-7-x64-tp4662996p4663007.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
