I have found my problem. It was being caused by some classes being loaded
by the system class loader and other files being loaded by the servlet class
loader.
By adding the servlet jar files to wrapper.properties, they were being
loaded by the system class loader. But, they could not find any of the
servlet supporting classes because these classes, which were in the classes
directory of the servlet's context, were being loaded by the servlet class
loader. When I removed all of my entries from wrapper.properties and put
the jars into the lib directory under my servlet's context, everything
worked.
- ron
-----Original Message-----
From: Hunor Nam [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 21, 2001 10:23 AM
To: [EMAIL PROTECTED]
Subject: RE: Running Tomcat as an NT Service
just make sure that your enviroment varibles are set for SYSTEM !!! not
for USER varables
Hades
-----Original Message-----
From: Ronald G. Louzon [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 21, 2001 3:35 PM
To: '[EMAIL PROTECTED]'
Subject: Running Tomcat as an NT Service
When running Tomcat as a Windows NT service, the NT wrapper
jk_nt_service.exe must be installed and run instead of using the startup
batch file. It appears that the jk_nt_service application reads its
entire
configuration from the wrapper.properties file. What this means is that
the
classes and jar files under WEB-INF/classes and WEB-INF/lib are not
automatically loaded for a servlet. Instead, they must all be added
manually in the wrapper.properties file.
Has anyone else run Tomcat as an NT Service and seen this same
behaviour?
If this behaviour is correct, why is so much functionality lost when
running
with the wrapper service?
Thanks,
ron
