|
From: Leif M. <lei...@ta...> - 2009-08-11 12:43:03
|
Most likely you are not running the correct JVM. This is actually a fairly common problem when running as a service if you have the Wrapper configured to locate its JVM on the system PATH. The problem is that your PATH as the "you" user is not the same as the SYSTEM user. To confirm this, try adding the following property to see the full command line used to launch JAVA. It will have the java command path normalized. wrapper.java.command.loglevel=INFO You probably want to either update the SYSTEM path or change your configuration file to something like the following. The first line sets the JAVA_HOME environment variable. You may want to skip that and define it globally. set.JAVA_COMMAND=C:¥path¥to¥JVM wrapper.java.command=%JAVA_HOME%/bin/java Hope this helps. Cheers, Leif On Tue, Aug 11, 2009 at 9:14 PM, CraZyWolF -<cra...@ho...> wrote: > Hello, > > > I'm using the wrapper 3.3.5 to launch an application based on JBoss. > > When executing the command line from the console it works, but when I'm > launching the wrapper (WrapperSimpleApp method) I've got a Sax parse > exception on the xml configuration file of the application. The thing is : > there is no validation document for this xml file, so I think the > validation is disabled in "my" program. It seems that using the wrapper > causes the validation to be active. But i've no idea how to disable it, I > can't modify the application. I could create a validation document for this > particular xml file, but I'm worried about having the same problem with > other xml files. > > Any idea would be greatly appreciated. > > > Thanks, > Crazywolf |