Return
-
Title
Tomcat service created by java wrapper not showing in Application Servers Administration dashboard -
Description
The Java Service Wrapper program was used to create a Tomcat 7 window service. Although Tomcat service can be startup successfully, it is not appearing up in Application Servers Administration dashboard. -
Cause
The problem is with wrapper.conf file is Incomplete and some invalid 'wrapper.java.additional. properties were used in wrapper.conf file. -
Resolution
The Java Wrapper program supports the ability to define environment variables from within a configuration file "wrapper.conf" and used to intialize starting up Tomcat window service.The following examples of wrapper options were added in wrapper.conf file to resolve this
wrapper.java.additional.5=-Dquest.agent.appserverinfo=Tomcathost:Tomcat:Version_no:Clusternamewrapper.java.additional.6=-Dquest.debug=0wrapper.java.additional.7=-Dquest.integrationid=IR85eUnke1qWI4Bwrapper.java.additional.8=-Xbootclasspath/p:"C:\Program Files\Common Files\Dell\Foglight Agent Manager\agents\JavaEE\5.9.8-20160405-1524\bootstrap\IR85eUnke1qWI4B\C---apache-tomcat-7.0.57_Windows_64bit_1-jre.jar"wrapper.java.additional.9=-javaagent:"C:\Program Files\Common Files\Dell\Foglight Agent Manager\agents\JavaEE\5.9.8-20160405-1524\lib\performasure-agent.jar"wrapper.java.additional.10=-Dcatalina.home=C:\apache-tomcat-7.0.57_Windows_64bit_1More information about wrapper.conf can be found in link Integrating a Java Service Wrapper Windows Service with a Java EE agent
-
Additional Information
Integrating a Java Service Wrapper Windows Service with a Java EE agent under Jboss, but not Tomcat