Re: [Wrapper-user] service does not start anymore (10035)

[Leif M. <lei...@ta...>]

Josh,
Could you please set the wrapper.java.command.loglevel=INFO property
and then reply with the resulting java command line?  I would like to
try and reproduce this here.  We test with large classpaths, but I may
not be testing large enough.

If possible, please also attach your wrapper.conf file.

Cheers,
Leif

On Tue, May 5, 2009 at 5:11 AM, Simon Lemay <sim...@gm...> wrote:
> hello :)
>
> I have been using the service wrapper for quit sometime now and I have just
> encountered a problem I cannot seem to solve.
>
> recently, my classpath has been growing a lot, and the more it grew, the
> more problem i had with the wrapper; the service does not start anymore.
>
> so i tested the problem and added a LOT more jar to statup command line and
> the service wrapper does not start anymore.  it will try 5 time (the default
> value) and than will exit saying that the application could not be started.
> in the log, i found this:
>
> Send a packet START : start
> socket send Failed (10035)
> unable to send the start command to the JVM
>
> and if i reduce the lenght of the startup command line, the problem seems to
> go away
>
> so i dont know if anybody else got the problem
>
> thanks in advance for you help
>
> Josh