When deploying Tomcat 4.1.31 as a Windows service, the service fails to start and returns the following exception:

Usually, the above exception is not the first exception to occur, but follows the initial exception. This problem does not occur with Tomcat 4.1.18.

Tomcat will start using the BAT file that is generated by SAS® software, even though it does not start as the Windows service. The cause of this problem is that Tomcat fails to see the necessary JAR file (mx4j-jmx.jar) from the class loading path. This file is in {Tomcat_Home}/server/lib.

The following line in Install_Tomcat_Service.bat is the apparent cause of the problem:

To resolve the problem, perform the following steps:

1. Change the line of code to the following:
   set JAVA_ENDORSED_DIRS=%CATALINA_HOME%\common\endorsed
2. Remove the Tomcat service if it is still installed.
3. Re-run Install_Tomcat_Service.bat to install the Tomcat service correctly.

Operating System and Release Information

Product Family	Product	System	SAS Release
			Reported	Fixed*
SAS System	Apache Jakarta Tomcat	Microsoft Windows Server 2003 Standard Edition	9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Enterprise Edition	9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Datacenter Edition	9.1 TS1M3 SP4

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

Tomcat starts with .bat file but fails to start as a service with java.lang.NoClassDefFound, related to Tomcat jmx mbean classes.

Type:	Problem Note
Priority:

Date Modified:	2008-10-13 13:39:24
Date Created:	2008-10-06 14:08:00