RE: log4j/Trace class Threading and STDOUT -- JAVA400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Hi Thorbjørn,
I am sure that my processing continues as I am able to return the messages I need, and when using System.out it logs ok.

I will try and put together some kind of working example and post it later.
Kind regards
Luke

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Thorbjoern Ravn Andersen
Sent: 07 March 2011 19:33
To: Java Programming on and around the IBM i
Subject: Re: log4j/Trace class Threading and STDOUT

Den 07/03/11 16.53, Klugman, Luke skrev:

Subsequently in my RPG I have a DoW loop which calls the getMessage method of my ConnectionManager object. When this message successfully returns a message it should log (" Recevied message " + message); but when this happens all my logging stops for the whole job.

Are you sure that processing continues, and logging does not stop
because the whole application deadlocks?

Since this is not a runnable, minimal example it is hard to run it to
see what happens (you may want to create such an example), but that
would be my guess. Also note you cannot use a single AS400 object in
more than one thread at a time.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.