Solved: TMSPE service not starting anymore - 14.1

Danny Meyer · ‎05-10-2013

Hi.

Since a while I cannot start the TMSPE service anymore. It used to work fine for the longer time.

Here is the wrapper log text from my failed service starts.

FATAL | wrapper | 2013/05/10 11:21:37 | Critical error: wait for JVM process failed

STATUS | wrapper | 2013/05/10 13:02:43 | --> Wrapper Started as Service

STATUS | wrapper | 2013/05/10 13:02:43 | Java Service Wrapper Standard Edition 32-bit 3.5.13

STATUS | wrapper | 2013/05/10 13:02:43 | http://wrapper.tanukisoftware.com

STATUS | wrapper | 2013/05/10 13:02:43 | Licensed to Cisco Systems, Inc. for Cisco TMS Provisioning Extension

STATUS | wrapper | 2013/05/10 13:02:43 |

STATUS | wrapper | 2013/05/10 13:02:44 | Launching a JVM...

FATAL | wrapper | 2013/05/10 13:02:44 | Unable to execute Java command. The system cannot find the file specified. (0x2)

FATAL | wrapper | 2013/05/10 13:02:44 | "java" -Dfile.encoding=UTF-8 -Duser.timezone=UTC -DLOG_HOME=logs -Dapp.pid="logs/tmsprovisioningextension.pid" -Ddatabase.name=mssql -Duser.language=en -Duser.country=US -XX:PermSize=128M -XX:MaxPermSize=384M -Xms256m -Xmx1024m -Djava.library.path="lib" -classpath "lib/wrapper.jar;etc/;../repo/appassembler-1.0.159.jar;../repo/security-1.0.159.jar;../repo/bouncycastle-jce-jdk13-112.jar;../repo/logging-common-1.0.159.jar;../repo/logback-classic-0.9.30.jar;../repo/logback-core-0.9.30.jar;../repo/jetty-server-7.2.2.v20101205.jar;../repo/servlet-api-2.5.jar;../repo/jetty-continuation-7.2.2.v20101205.jar;../repo/jetty-http-7.2.2.v20101205.jar;../repo/jetty-io-7.2.2.v20101205.jar;../repo/jetty-webapp-7.2.2.v20101205.jar;../repo/jetty-servlet-7.2.2.v20101205.jar;../repo/jetty-security-7.2.2.v20101205.jar;../repo/jetty-jmx-7.2.2.v20101205.jar;../repo/jetty-xml-7.2.2.v20101205.jar;../repo/jetty-util-7.2.2.v20101205.jar;../repo/jsp-2.1-glassfish-9.1.1.B60.25.p2.jar;../repo/core-3.1.1.jar;../repo/jsp-api-2.1-glassfish-9.1.1.B60.25.p2.jar;../repo/ant-1.6.5.jar;../repo/servlet-api-2.5-6.1.14.jar;../repo/commons-beanutils-1.7.0.jar;../repo/commons-codec-20041127.091804.jar;../repo/commons-collections-3.1.jar;../repo/collections-generic-4.01.jar;../repo/commons-dbcp-1.4.jar;../repo/commons-digester-1.6.jar;../repo/xml-apis-1.0.b2.jar;../repo/commons-el-1.0.jar;../repo/commons-email-1.2.jar;../repo/mail-1.4.1.jar;../repo/activation-1.1.jar;../repo/commons-io-1.4.jar;../repo/commons-lang-2.5.jar;../repo/commons-logging-1.1.1.jar;../repo/commons-management-1.0.jar;../repo/commons-net-2.0.jar;../repo/commons-pool-1.5.4.jar;../repo/ehcache-1.6.2.jar;../repo/commons-validator-1.3.1.jar;../repo/dom4j-1.6.1.jar;../repo/log4j-over-slf4j-1.6.1.jar;../repo/slf4j-api-1.6.1.jar;../repo/jcl-over-slf4j-1.6.1.jar;../repo/jul-to-slf4j-1.6.1.jar;../repo/oro-2.0.8.jar" -Dwrapper.key="Tl7K-qpy6rRkvwn-RYGXy3mMAaqthYpc" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=5776 -Dwrapper.version="3.5.13-st" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 -Dwrapper.lang.domain=wrapper -Dwrapper.lang.folder=../lang org.tanukisoftware.wrapper.WrapperSimpleApp com.cisco.ts.mgmt.app.JettyLauncher

ADVICE | wrapper | 2013/05/10 13:02:44 |

ADVICE | wrapper | 2013/05/10 13:02:44 | --------------------------------------------------------------------

ADVICE | wrapper | 2013/05/10 13:02:44 | Advice:

ADVICE | wrapper | 2013/05/10 13:02:44 | Usually when the Wrapper fails to start the JVM process, it is

ADVICE | wrapper | 2013/05/10 13:02:44 | because of a problem with the value of the configured Java command.

ADVICE | wrapper | 2013/05/10 13:02:44 | Currently:

ADVICE | wrapper | 2013/05/10 13:02:44 | wrapper.java.command=java

ADVICE | wrapper | 2013/05/10 13:02:44 | Please make sure that the PATH or any other referenced environment

ADVICE | wrapper | 2013/05/10 13:02:44 | variables are correctly defined for the current environment.

ADVICE | wrapper | 2013/05/10 13:02:44 | --------------------------------------------------------------------

ADVICE | wrapper | 2013/05/10 13:02:44 |

The installed Java version is 1.7.0.17 as I verifeid in the TMSPE install doc. TMS is 14.1.1.

Thanks for any advice.

Regards

Danny

aborodai · ‎05-10-2013

Hi Denny,

As you can see from the logs:

AL | wrapper | 2013/05/10 13:02:44 | Unable to execute Java command. The system cannot find the file specified. (0x2)

TMSPE service cannot find Java. I wil advise you to completely uninstall Java and install it again, it should be 32 bit version. Please restart server after installation.

Best Regards,

Artem Borodai

View solution in original post

aborodai · ‎05-10-2013

Hi Denny,

As you can see from the logs:

AL | wrapper | 2013/05/10 13:02:44 | Unable to execute Java command. The system cannot find the file specified. (0x2)

TMSPE service cannot find Java. I wil advise you to completely uninstall Java and install it again, it should be 32 bit version. Please restart server after installation.

Best Regards,

Artem Borodai

Danny Meyer · ‎05-10-2013

Hi Artem.

Thank you very much. That was indeed helpful. For whatever reason this was necessary again... :-)

Looks like I am back on the TMSPE diag screen (after some longer waiting).

Cheers

Danny

daleritc · ‎05-10-2013

Hi Danny/Artem;

Reference this sentence in your original post:

The installed Java version is 1.7.0.17 as I verifeid in the TMSPE install doc. TMS is 14.1.1.

This Java version your referencing is for TMSPE v1.1...which was just released recently...and as a dependency to TMS 14.2. Meaning your looking at the wrong deployment guide

Dale

Danny Meyer · ‎05-11-2013

Dale.

You are very right. For whatever reason there was also a Java7 version laying on the TMS server. No idea how that came there. 14.1 has indeed the requriements for TMSPE1.0.

Thanks and regards

Danny