|
From: Todd E. <ten...@te...> - 2002-11-28 06:23:15
|
Yeah, my app is not setting it to that at all. My only guess is that since the %os% variable says "windows_nt" on xp, that either the system or some java lib is returning c:\winnt by defualt for windir. Obviously that is a huge shot in the dark, but windows, actually any os, can be weird. I will will definitely be exercising the wrapper in a full QA environment and writing several apps using it, so I am sure to have more feedback in the future for you. ----- Original Message ----- From: "Leif Mortenson" <le...@ta...> To: <wra...@li...> Sent: Wednesday, November 27, 2002 11:51 PM Subject: Re: [Wrapper-user] environment variables > Todd Enright wrote: > > > Hi Leif, > > I needed to pass the parameters to the wrapper.java.additional > > section, as they are called from system.getProperty(). Things are up > > and working properly now! Thank you for the assistance. This wrapper > > is excellent, and very flexible. By far the best out there! > > Thanks. Glad you got it working. > > If you don't set the windir property manually is it defaulting to > C:\WinNT? Or is that something that your application is doing. Ie > using that default if the property is not set? It The JVM is defaulting > to C:\WinNT, that sounds like a Java bug or something. > > Leif > > > > > Cheers, > > Todd > > > > ----- Original Message ----- > > From: Leif Mortenson <mailto:le...@ta...> > > To: wra...@li... > > <mailto:wra...@li...> > > Sent: Wednesday, November 27, 2002 8:06 PM > > Subject: Re: [Wrapper-user] environment variables > > > > Todd Enright wrote: > > > >> Hey Leif, > >> Sorry.... totally forgot some good information. I am passing in > >> windir as an argument, then returning the value to web server > >> scripts through a cgi. I don't think I'm getting the argument > >> passed properly. Here is what I have in my wrapper.conf for > >> application parameters. > >> > >> wrapper.app.parameter.1=P2PShell > >> wrapper.app.parameter.3=-DasService=yes > >> wrapper.app.parameter.4=-Dwindir=%windir% > > > > This looks ok but because you are using -D... I have to ask. Do > > you intend to be passing these parameters to the main method of > > P2PShell.class? Or do you mean to be setting them as properties > > that you get from System.getProperty(...)? If it is the later, > > then you will need to move them to the wrapper.java.additional > > section. This will pass the parameters to the JVM rather than to > > the class's main method as you are doing now. > > > > wrapper.java.additional.1=-DasService=yes > > wrapper.java.additional.2=-Dwindir=%windir% > > > >> I told java to return verbose information, and although it breaks > >> the command, it shows the construction of the command. Here's > >> what it shows. Can you tell me if the construction of the > >> command looks good (other than the -v which breaks things) > > > > You can do this by enabling debug output to the console using the > > following: > > wrapper.console.loglevel=DEBUG > > > >> wrapper | --> Wrapper Started as Console > >> wrapper | Launching a JVM... > >> wrapper | can not execute ""C:\WINDOWS\java.exe -v" -Xms16m > >> -Xmx128m -Djava.lib > >> rary.path="./lib" -classpath > >> "./lib/wrapper.jar;./lib/wrappertest.jar;C:\Program > >> Files\ClearCube Management Suite\DataFailover\.;C:\Program > >> Files\ClearCube Mana > >> gement Suite\DataFailover\jaxp1.0.1\parser.jar;C:\Program > >> Files\ClearCube Manage > >> ment Suite\DataFailover\jaxp1.0.1\jaxp.jar;C:\Program > >> Files\ClearCube Management > >> Suite\DataFailover\lf\oyoahalnf\oyoahalnf.jar;C:\Program > >> Files\ClearCube Manage > >> ment Suite\DataFailover\soap.jar;C:\Program Files\ClearCube > >> Management Suite\Dat > >> aFailover;C:\Program Files\ClearCube Management > >> Suite\DataFailover\xerces.jar;C: > >> \Program Files\ClearCube Management Suite\DataFailover\xalan.jar" > >> -Dwrapper.key= > >> "nsYL7tEdn_k1zaW1" -Dwrapper.port=1777 -Dwrapper.debug="TRUE" > >> -Dwrapper.cpu.time > >> out="10" -Dwrapper.jvmid=1 com.silveregg.wrapper.WrapperSimpleApp > >> P2PShell -Dshu > >> tdown.method=stopApplication -Dwindir=C:\WINDOWS" (ERR=2) > >> wrapper | Critical error: wait for JVM process failed > > > > > > Other than the comment above, this all looks ok. The only thing > > is that you most likely do not need to be including the > > wrapertest.jar file in your classpath. > > > > Cheers, > > Leif > > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Get the new Palm Tungsten T > handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |