|
From: Javier M. <jav...@at...> - 2010-06-15 15:43:26
|
Thanks Leif, we'll try 1-3 asap but wanted to let you know the version info. I think I mentioned in my first email, but here it is again, we have wrapper-3.3.0, Standard Edition. If you would like us to try a newer one let me know javier > -----Original Message----- > From: Leif Mortenson [mailto:lei...@ta...] > Sent: martes, 15 de junio de 2010 16:58 > To: wra...@li... > Subject: Re: [Wrapper-user] Antw: service not starting on Windows > 2008R1 64b > > Javier, > Sorry for the delay getting back to you. We reviewed your > wrapper.conf files and there are a few things I would like to ask you > to try out. > > 1) The configured wrapper.log file location depends on an environment > variable. > wrapper.logfile=E:\ADAM\adam/runtime/logs/%ADAM_PROCESS_NAME%.service.l > og.ROLLNUM > That is being set in the parent configuration file, so it should be > fine, but could you please try a simple logfile like the following: > wrapper.logfile=C:¥TEMP¥wrapper.log > Where that directory is known to exist. I would like to see if you > get a configuration file in this case. > > 2) Could you please try downloading the wrapper distribution and then > installing the default TestWrapper application as a service to see > what happens? If that is having the same problem then we know that > it is not something to do with your configuration. > > 3) You have the following property configured, but I do not see where > you are defining ADAM_RUNTIME > wrapper.java.additional.4=-XX:HeapDumpPath=%ADAM_RUNTIME%/logs > If that did not exist then it might cause the JVM to fail to start. > But You should be seeing a wrapper.log with other output long before > the JVM is launched. > > You asked about a newer version of the Wrapper. What version are you > using? I am not aware of anything in a newer version that would > correct what you are seeing. I am still quite puzzled as to why the > Wrapper32 bit version is working but the Wrapper64 bit version is not. > The fact that the Wrapper 64-bit works when running as the > Administrator user proves that the Wrapper binary itself is fine and > that the configuration is correct. The only differences left are > permissions, and environment differences. I am not aware of any > permission configurations which would prevent a 64-bit program from > running, but allow a 32-bit program. > > Please let me know the results of 1-3 above. If they all fail, lets > set up a phone or Skype meeting to walk through what could be > happening and try to get this resolved. > > Cheers, > Leif > > On Tue, Jun 15, 2010 at 10:25 PM, Javier Muguruza > <jav...@at...> wrote: > > Hi, is there anything else we could try? Using a newer version of > wrapper or anything? > > > > Thanks > > javier > > -- > Leif Mortenson > Tanuki Software, Ltd. > 6-16-7-1001 Nishi-Kasai, Edogawa-ku > Tokyo 134-0088 Japan > Tel/Fax: +81-3-3878-3211 > http://www.tanukisoftware.com > lei...@ta... > > ----------------------------------------------------------------------- > ------- > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |