From: Leif M. <le...@ta...> - 2008-06-26 01:35:31
|
Vin, Given that the error message is not displaying correctly, I am wondering if there is a general character encoding problem. The Wrapper is not yet localized and double byte safe. This is on our todo list. 1) What is the locale of your Windows? ie. Japanese, English, etc. 2) What is the full path to where the wrapper.exe file is located? You have several relative paths in your configuration which in itself should be fine. 3) When you ran your "-version" test with the testwrapper configuration file, what was the full path to that wrapper.exe? 4) In case either of the above two paths contain non-ascii characters, could you try your test in a simple directory like c:\myapp\ ? Cheers, Leif Vincent Finn wrote: > Ok, > > If there is anything I can do to help narrow it down further let me know. > > Vin > > On Tue, Jun 24, 2008 at 6:12 PM, Leif Mortenson > <le...@ta... <mailto:le...@ta...>> wrote: > > Vincent, > One of the lines of output from your log file does not display the > error message that should be telling me what the cause of your > problems is. > > Your log file has the line: > Unable to execute Java command. > > But when I run the released Windows 3.3.0 release it generates the > following message: > Unable to execute Java command. The system cannot find the file > specified. (0x2) > > That error message is generated with the following code: > log_printf(WRAPPER_SOURCE_WRAPPER, LEVEL_FATAL, > "Unable to execute Java command. %s", > getLastErrorText()); > > For some reason, your log output does not include the error > message and I am > trying to understand why. I had added that error message back in 2004 > to help track > down the cause of problems like this. > > If as I assume, you are indeed using the official release then I need > to figure out why > the getLastErrorText() function is returning "" on your machine. That > line in your log > file does include trailing spaces so I think this is what is > happening. > > Thanks, > Leif > > > > On Tue, Jun 24, 2008 at 10:14 PM, Vincent Finn <v.f...@gm... > <mailto:v.f...@gm...>> wrote: > > Hi, > > > > Yeah, I am just running it in from the console. > > > > I have attached the log file but there not a lot in it. > > > > I also tried the trivial sample attached, all it does is run "java > > -version". > > That fails with the same error. > > > > Vin > > > > On Tue, Jun 24, 2008 at 12:47 PM, Leif Mortenson > <le...@ta... <mailto:le...@ta...>> > > wrote: > >> > >> Vincent, > >> To confirm, when you run with the Wrapper, you are running in a > console > >> and not > >> as a Service correct? > >> > >> Looking at your wrapper.conf, I did not see anything that stood > out as > >> incorrect. > >> > >> Could you please set the wrapper.debug=true property and then > reply back > >> with > >> the full resulting wrapper.log file. Delete the only file > before you > >> start so we only > >> get a single JVM run. > >> > >> Thanks, > >> Leif > >> > >> On Tue, Jun 24, 2008 at 7:08 PM, Vincent Finn > <v.f...@gm... <mailto:v.f...@gm...>> wrote: > >> > Hi, > >> > > >> > I have seen this error mentioned in the forum but it doesn't > to be for > >> > the > >> > same problem as I am having. > >> > > >> > I am using JSW 3.3.0 on Windows XP (32bit). > >> > I am simply trying to run the batch file in the bin folder > >> > (serviceName.bat) > >> > and I get the error > >> > "Critical error: wait for JVM process failed" > >> > > >> > I have attached my config file, and a file containing the > command line > >> > output by the wrapper (without the -Dwrapper.key argument). > >> > > >> > When I run the wrapper the output is: > >> > > >> > wrapper | Launching a JVM... > >> > wrapper | Unable to execute Java command. > >> > wrapper | C:\...\java ... > >> > wrapper | Critical error: wait for JVM process failed > >> > > >> > > >> > If I run the command directly on the command line it works > perfectly, it > >> > only fails when run through the wrapper. > >> > > >> > Any ideas as to what might be wrong? > >> > > >> > Thanks, Vin > >> > > |