Re: [Wrapper-user] Wrapper start problems

[Christian M. <chr...@ta...>]

Manjiri,

Thank you for your mail.

The JVM received a sigkill from somewhere, and it doesn't look like it
came from the Wrapper, so could you please send me the full log file
and the conf file you are using? This should give me more information
if there is some other issue.

Thank you,
Christian

On Sat, Apr 2, 2011 at 12:33 AM, Manjiri <man...@gm...> wrote:
>
> Hello,
>
> I am trying to start ApacheDS server, which launches a Tanuki Wrapper:
>
> The wrapper stops, causing me issues while starting the ApacheDS server.
>
> Running Apache Directory Server - default...
> wrapper  | --> Wrapper Started as Console
> wrapper  | Using tick timer.
> wrapperp | server listening on port 32000.
> wrapper  | Command[0] : java
> wrapper  | Command[1] :
> -Dlog4j.configuration=file:////var/lib/apacheds-1.5.7/default/conf/log4j.properties
> wrapper  | Command[2] : -Dapacheds.var.dir=/var/lib/apacheds-1.5.7/default
> wrapper  | Command[3] :
> -Dapacheds.log.dir=/var/lib/apacheds-1.5.7/default/log
> wrapper  | Command[4] :
> -Dapacheds.run.dir=/var/lib/apacheds-1.5.7/default/run
> wrapper  | Command[5] : -Dapacheds.instance=default
> wrapper  | Command[6] :
> -Dbootstrap.start.class=org.apache.ldap.server.Service
> wrapper  | Command[7] :
> -Dbootstrap.stop.class=org.apache.ldap.server.Service
> wrapper  | Command[8] : -Xms384m
> wrapper  | Command[9] : -Xmx384m
> wrapper  | Command[10] : -Djava.library.path=../lib
> wrapper  | Command[11] : -classpath
> ...
> wrapper  | Pause reading child output to share cycles.
> wrapper  | JVM exited on its own while waiting to kill the application.
> wrapper  | JVM did not exit on request, terminated
> wrapper  | Signal trapped.  Details:
> wrapper  |   signal number=17 (SIGCHLD), source="unknown"
> wrapper  | Received SIGCHLD, checking JVM process status.
> wrapper  | JVM exited in response to signal SIGKILL (9).
> wrapper  | JVM process exited with a code of 1, setting the wrapper exit
> code to 1.
> ...
> wrapperp | server listening on port 32000.
> wrapper  | JVM was only running for 34 seconds leading to a failed restart
> count of 1.
> wrapper  | There were 1 failed launches in a row, each lasting less than 300
> seconds.  Giving up.
> wrapper  |   There may be a configuration problem: please check the logs.
> wrapper  | <-- Wrapper Stopped
>
>
>
> Following are some of the wrapper properties:
>
> wrapper.shutdown.timeout=30
> wrapper.startup.timeout=120
> wrapper.ping.timeout=300
> wrapper.on_exit.default=RESTART
> wrapper.port=15013
> wrapper.java.command=/usr/local/jdk1.6.0_03/bin/java
> apacheds.instance.start=auto
>
> Thank You.
>
> Sincerely,
> Manjiri
>
> --
> View this message in context: http://old.nabble.com/Wrapper-start-problems-tp31295824p31295824.html
> Sent from the Java Service Wrapper mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Create and publish websites with WebMatrix
> Use the most popular FREE web apps or write code yourself;
> WebMatrix provides all the features you need to develop and
> publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>