|
From: hail z. <hai...@gm...> - 2006-11-23 09:49:02
|
Hi, Leif Thanks for you answer! I have fixed this problem, it is the problem as you said! Thanks a lot! Best regards, Hail ======================================================== | Zhang, | I have had a JMF application running for several years under various | wrapper versions on | XP and 2000 without any problems. It runs as the default system account. | | How have you set up your library path? The command that you mention | to run as a | standalone java app does not specify a library path. This makes me | wonder if you have | forgotten to do that in your wrapper.conf. By default, java will | search the system PATH | for JNI libraries to load. When a specific library path is specified, | as is done with the | wrapper, this will not happen. Using the PATH, like CLASSPATH, is | actually rather | unreliable anyway. Try adding the location of your JNI dlls to the | library path in the | wrapper.conf. | | If that doesn't work, post your wrapper.conf and a wrapper.log | showing the full | stack track. | | You should also always try to run the wrapper as a console app | BEFORE trying | to run as a service. This makes it much easier to track down common | problems. | | Cheers, | Leif -- Best regards, Hail.zhang |