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 y
Pascal <[EMAIL PROTECTED]> 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 t
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?
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 shouldn't be any) I don't think this is
true. If it is, then each case is a coding error that should be fixed.
--
Oskar Sandberg
o
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 m
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 goto
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 ther
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 got
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 yo
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?
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 the
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 shouldn't be any) I don't think this is
true. If it is, then each case is a coding error that should be fixed.
--
Oskar Sandberg
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 y
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.
>
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
16 matches
Mail list logo