Pascal writes:
> I modified Fred's logger some time ago to redirect StdErr and StdOut
> to the logfile if they did not exist. If this is not happening on
> your JVM your patch will certainly act as a workaround, but the
> preferred solution would be to submit a bug report to the developers
> of
That shows nothing. A lot of files contain main() methods used for
testing and alike that contain such calls. Some are external programs
(config.Setup, client.cli, etc) that actually use it independently of the
node.
The real question is, what is being written to out/err when a node is
running?
Hi,
I'm running Fred as a service in the background, and so won't see
exceptions that are not logged. The most likely culprits are fatal
datastore corruptions. All I see is that Fred is no longer running
after a boot.
So to get more information, I wrote code to catch unhandled exceptions
in the
On Sun, Sep 01, 2002 at 09:33:18PM +0200, Robert Bihlmeyer wrote:
> Hi,
>
> I'm running Fred as a service in the background, and so won't see
> exceptions that are not logged. The most likely culprits are fatal
> datastore corruptions. All I see is that Fred is no longer running
> after a boot.
>
In main.java alone exception handling for BadAddressException,
DiagnosticsException, and ListenException write nothing to the log but
instead send the output to StdErr. On JVMs that do not work correctly
these error messages are simply lost even with today's patch. Making
these errors always
Windows find shows 50 files containing system.out.print and 71
containing system.err.print
-Pascal
Oskar Sandberg wrote:
>
> On Sun, Sep 01, 2002 at 04:27:41PM -0500, Pascal wrote:
> > There are many places in Fred where output is sent to StdErr and
> > StdOut.
>
> Except for cruft (which
There are many places in Fred where output is sent to StdErr and
StdOut. This patch will only catch the specific instance of an
unhandled exception occurring. I modified Fred's logger some time ago
to redirect StdErr and StdOut to the logfile if they did not exist. If
this is not happening on
Hi,
I'm running Fred as a service in the background, and so won't see
exceptions that are not logged. The most likely culprits are fatal
datastore corruptions. All I see is that Fred is no longer running
after a boot.
So to get more information, I wrote code to catch unhandled exceptions
in the
On Sun, Sep 01, 2002 at 09:33:18PM +0200, Robert Bihlmeyer wrote:
Hi,
I'm running Fred as a service in the background, and so won't see
exceptions that are not logged. The most likely culprits are fatal
datastore corruptions. All I see is that Fred is no longer running
after a boot.
So
There are many places in Fred where output is sent to StdErr and
StdOut. This patch will only catch the specific instance of an
unhandled exception occurring. I modified Fred's logger some time ago
to redirect StdErr and StdOut to the logfile if they did not exist. If
this is not happening on
Windows find shows 50 files containing system.out.print and 71
containing system.err.print
-Pascal
Oskar Sandberg wrote:
On Sun, Sep 01, 2002 at 04:27:41PM -0500, Pascal wrote:
There are many places in Fred where output is sent to StdErr and
StdOut.
Except for cruft (which there
That shows nothing. A lot of files contain main() methods used for
testing and alike that contain such calls. Some are external programs
(config.Setup, client.cli, etc) that actually use it independently of the
node.
The real question is, what is being written to out/err when a node is
running?
In main.java alone exception handling for BadAddressException,
DiagnosticsException, and ListenException write nothing to the log but
instead send the output to StdErr. On JVMs that do not work correctly
these error messages are simply lost even with today's patch. Making
these errors always
13 matches
Mail list logo
