Re: [Wrapper-user] Wrapper shuts down on Linux

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Hi Leif,

Since my last email I configured the nexus to not use the wrapper. This
isolation of the problem would prove if I have (a,b,c). The situation is
that nexus without wrapper works without any restarting (since one week).

There should be a problem regarding VM (not with JavaVM!).

Look at the latest "send a packet PING : ping" -- it has a response. The
after the I don't see any "send a packet PING". In this way the timeout
occurs. (The JVM does not receives any packet to respond.)

Thanks,
Tibor

2008/11/5 Leif Mortenson <lei...@ta...>

> Tibor,
> This does not appear to be a ping timeout issue.   For some reason,
> the log file you have sent does not contain any of the debug output
> from the JVM so it is difficult to tell exactly what is happening
> there.

> The Wrapper is initiating a shutdown because the JVM sent a STOP
> packet to the Wrapper.  This could have been caused by any number of
> things.  a) Someone called System.exit(0) b) Runtime.halt(0), c) All
> non-daemon threads stopped, etc.
>
> The shutdown appears to be normal from the Wrapper perspective however.
>
> Cheers,
> Leif
>
> On Thu, Oct 16, 2008 at 6:13 PM, Kiss Tibor <kis...@gm...> wrote:
> > Hi,
> >
> > I am evaluating Nexus Maven repository http://nexus.sonatype.org/ wich
> has
> > Wrapper (Version 3.2.3).
> > Unfortunately often get restarted or more precisely stopped even if I
> > increased the timeout value.
> >
> > DEBUG  | wrapperp | 2008/10/16 10:31:09 | read a packet PING : ok
> > DEBUG  | wrapper  | 2008/10/16 10:31:09 | Got ping response from JVM
> > DEBUG  | wrapperp | 2008/10/16 10:31:13 | send a packet PING : ping
> > DEBUG  | wrapperp | 2008/10/16 10:31:13 | read a packet PING : ok
> > DEBUG  | wrapper  | 2008/10/16 10:31:13 | Got ping response from JVM
> > DEBUG  | wrapperp | 2008/10/16 10:41:13 | read a packet STOP : 0
> > DEBUG  | wrapper  | 2008/10/16 10:41:13 | JVM requested a shutdown. (0)
> > DEBUG  | wrapper  | 2008/10/16 10:41:13 | wrapperStopProcess(0) called.
> > DEBUG  | wrapper  | 2008/10/16 10:41:13 | Sending stop signal to JVM
> > DEBUG  | wrapperp | 2008/10/16 10:41:13 | send a packet STOP : NULL
> > DEBUG  | wrapperp | 2008/10/16 10:41:14 | read a packet LOG(INFO) :
> Stopping
> > the Plexus Container.
> > DEBUG  | wrapper  | 2008/10/16 10:41:14 | Got a log message from JVM:
> > Stopping the Plexus Container.
> > DEBUG  | wrapperp | 2008/10/16 10:41:14 | read a packet LOG(INFO) :
> Plexus
> > Container stopped.
> > DEBUG  | wrapper  | 2008/10/16 10:41:14 | Got a log message from JVM:
> Plexus
> > Container stopped.
> > DEBUG  | wrapperp | 2008/10/16 10:41:14 | read a packet STOPPED : 0
> > DEBUG  | wrapper  | 2008/10/16 10:41:14 | JVM signalled that it was
> stopped.
> > DEBUG  | wrapperp | 2008/10/16 10:41:14 | socket read no code (closed?).
> > DEBUG  | wrapperp | 2008/10/16 10:41:15 | server listening on port 32001.
> > DEBUG  | wrapper  | 2008/10/16 10:41:15 | JVM exited normally.
> > DEBUG  | wrapper  | 2008/10/16 10:41:15 | Signal trapped.  Details:
> > DEBUG  | wrapper  | 2008/10/16 10:41:15 |   signal number=17 (SIGCHLD),
> > source="unknown"
> > DEBUG  | wrapper  | 2008/10/16 10:41:15 | Received SIGCHLD, checking JVM
> > process status.
> > DEBUG  | wrapper  | 2008/10/16 10:41:15 | JVM process exited with a code
> of
> > 1, setting the wrapper exit code to 1.
> > STATUS | wrapper  | 2008/10/16 10:41:15 | <-- Wrapper Stopped
> >
> > Looking into the debug log, I see that the sending of the ping is getting
> > stopped. Not the ping-back.
> >
> > I have a Red Hat Enterprise Linux server v 5.1 running inside a virtual
> > machine. The processor load is near zero, there is no process to bother
> my
> > process.
> >
> > Except the enlarging of the timeout written in the FAQ and
> >
> http://sourceforge.net/mailarchive/forum.php?thread_name=d049fb4f0809031947t267aa72fhb4d7965a936d811a%40mail.gmail.com&forum_name=wrapper-user
> > I see no solution yet. The latter thread says that the JVM is the problem
> > My jvm is Java HotSpot(TM) Client VM (build 1.5.0_13-b05, mixed mode,
> > sharing)
> > I don't think so that the JVM is the problem...
> >
> > Regards,
> > Tibor
> >
> > -------------------------------------------------------------------------
> > This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> > Build the coolest Linux based applications with Moblin SDK & win great
> > prizes
> > Grand prize is a trip for two to an Open Source event anywhere in the
> world
> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> > _______________________________________________
> > Wrapper-user mailing list
> > Wra...@li...
> > https://lists.sourceforge.net/lists/listinfo/wrapper-user
> >
> >
>
>
>
> --
> Leif Mortenson
> President
> Tanuki Software, Ltd.
> 6-16-7-1001 Nishi-Kasai, Edogawa-ku
> Tokyo 134-0088 Japan
> Tel/Fax: +81-3-3878-0415
> モートンソン リーフ
> 取締役
> タヌキソフトウェア有限会社
> 〒134-0088 東京都江戸川区西葛西6-16-7-1001 第2 白子ビル
> Tel/Fax: 03-3878-0415
> http://www.tanukisoftware.com
> lei...@ta...
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>