After 3 days of continual operation ( I barely managed 9hrs before )
it seems I have narrowed this down to the saddeningly basic cause of
the process being sent the SIGHUP signal when its owner process dies.
Using the nohup prefix solves the problem.
Thanks for all the help on this everyone!
Hi Cameron,
On 18 February 2011 04:33, Cameron Kerr came...@humbledown.org wrote:
On 17/02/2011, at 9:35 PM, Mathieu Baudier wrote:
I've been running our apps as purely as I can (java -cp
/path/to/libs/* path.to.the.App) and they're still being send SIGHUP
signals for reasons I can't
On 18 February 2011 09:49, Michael Gliwinski
michael.gliwin...@henderson-group.com wrote:
On Friday 18 Feb 2011 09:53:39 Martin Hewitt wrote:
My command is something along the lines of:
java -cp /path/to/shared/libs/*:/path/to/class/directory/
path.to.MyApp out.log 21
Does anyone have
On 14 February 2011 12:17, Mathieu Baudier mbaud...@argeo.org wrote:
When I package a Runnable JAR using the Eclipse Export wizard, in
the manifest file, the main-class is given as
org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader, which I presume
is a little bit of code to redirect the
without jar
packaging.
Martin
On 11 February 2011 14:13, m.r...@5-cent.us wrote:
Martin Hewitt wrote:
Hi Mark,
I've exhausted the Java avenues for debugging this issue, but, since
my last email, the process I pointed strace at has been killed, but
I'm afraid the rather raw format of the strace
Hi Mathieu,
Can you please give more details about this additional code? How did
you find out?
When I package a Runnable JAR using the Eclipse Export wizard, in
the manifest file, the main-class is given as
org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader, which I presume
is a little bit
Hi Mathieu,
On 14 Feb 2011, at 12:17, Mathieu Baudier wrote:
When I package a Runnable JAR using the Eclipse Export wizard, in
the manifest file, the main-class is given as
org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader, which I presume
is a little bit of code to redirect the main
Roberts wrote:
On Fri, 11 Feb 2011, Martin Hewitt wrote:
To: CentOS mailing list centos@centos.org
From: Martin Hewitt martin.hew...@gmail.com
Subject: Re: [CentOS] CentOS 5.5 Java Process Death
Hi Mark,
I've exhausted the Java avenues for debugging this issue, but, since
my last email
Hi all,
I'm running CentOS 5.5 Final, Java version 1.6.0_17 OpenJDK Runtime
Environment (IcedTea6 1.7.5) (rhel-1.16.b17.el5-x86_64) OpenJDK 64-Bit
Server VM (build 14.0-b16, mixed mode) installed via Yum.
We have a java application, packaged as a jar, running on our servers
which, periodically,
a difference.
Thanks for the help.
Martin
On 10 February 2011 18:58, m.r...@5-cent.us wrote:
Martin Hewitt wrote:
Hi all,
I'm running CentOS 5.5 Final, Java version 1.6.0_17 OpenJDK Runtime
Environment (IcedTea6 1.7.5) (rhel-1.16.b17.el5-x86_64) OpenJDK 64-Bit
Server VM (build 14.0-b16
Java should be aware of the Interrupted
system call?
There are no other signals in the output file, and the only EINTRs are
in the passage above.
Looks like I need to delve back into Java...
Martin
On 10 February 2011 19:37, m.r...@5-cent.us wrote:
Hey, Martin,
Martin Hewitt wrote:
Thanks
11 matches
Mail list logo
