
Signature
Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.
>This sounds possibly like you are logging with many threads but your
>logging class is not thread safe.
As I mentioned, we are using log4j with no customizations. log4j
claims to be thread-safe. The log4j code has syncrhronized blocks of
code for accessing resources for which there might be contention. At
any rate, our log4j configuration specifies only console logging, for
which contention should not be an issue, right?
>As for System.out stuff getting mixed in, your first job is to track which line in the
>code could have generated those lines, and make sure System.out is not
>redirected at that point or if those lines are being logged instead of System.outed.
I did a search and System.setOut appears nowhere in our codebase, nor
in the log4j code. The code which generates the lines in question is
simply that I described in my first message, i.e. simple calls to
log4j's Logger.info() method.
>Unless you are using some home-grown spooling software, I would put
>blaming generic spooling low on my list of suspects. The problem would
>likely show up all over the place, not just this program if that were
>the source of the problem.
As I mentioned above, I recently discovered that other java apps on
this machine *are* having intermittent trouble writing to stdout.
However, the common thing among these apps is that they run under
Weblogic 8.1. Each app runs in its own JVM, i.e. its own Weblogic
server (keep in mind Weblogic servers are virtual).
Thanks for your help.