|
From: Leif M. <le...@ta...> - 2004-03-14 15:36:28
|
Stefan, You say that your servlet makes use of a JNI native library to operate? Are you sure that the library is correctly located on your library path. When you run Tomcat standalone the library path will default to looking on the PATH. But when using the Wrapper, you need to specifically specify the full library path in the wrapper.conf file. This is not anything that has changed between 2.2.4 and 3.0.5 however. Try setting the wrapper.debug=true property. This will let you see the full library path being used on startup and it may give some clues as to why exactly the application is shutting down. Is the problem servlet something that you have source for? My guess is that it is calling System.exit when it fails to locate its native library. Because of your comment on load_on_startup, I assume that this is happening in the servlet's init method. Cheers, Leif sou...@m4... wrote: > Hi, > > I recently used this smart tool (ServiceWrapper 2.2.4) for starting > Tomcat and everything worked fine (SimpleApp). Now I updated to 3.0.5 > and am confronted with the strange problem that Tomcat shuts down > immediately after starting. I am clueless because no log contains any > error - it seems to stop right after a certain instruction. > > Recently I tracked it down to be a problem with a certain dynamic > servlet which is the main part of a server - client architecture - > therefore I cannot go on without using it ... Tomcat itself will start > without any problem if I do use its startup.bat. > Also using the wrapper and Tomcat as a simple Webserver works ok but > in this case when I try to load the servlet on startup time Tomcat and > the wrapper also shut down immediately. If I leave out the > load-on-startup it shuts down right after the first call to the > servlets address. > > Additionally let me add that I am using another native dll in my > servlet for storing data. Could that cause any problems? > > Any help will be appreciated, > Stefan Dingfelder |