Serializing objects that use Loggers

Question

i am trying to clean-up a lot of java code i have written. so please allow me one more post:
the issue is objects that use Loggers :
public class MyClass implements Serializable {
  private static Logger logger = Logger.getLogger("baselib.utilities"); // <-- must be marked transient
}no serializable objects can use Loggers , right? in my imagination i see that:
(1) Logger settings are global to a jvm . [read out of a "logging.properies" at start-time].
(2) so, a MyClass object is created in jvm1 and gets its log settings.
(3) it is serialized and sent to jvm2.
(4) it pops-up after de-deserialization, and the jvm2 global log settings are different.
the Logger in the MyClass object is hopelessly confused.
so, by hook or crook,
its fair to say that you cannot use Loggers with serializable objects, right?
(i don't like Loggers anyway).
please just answer this one last question, then i can get back to writing code rather
than cleaning it. thanks to all.

Answer 1

i am running at least 4 threads (and sometimes as many as 20) leading to chaotic
asynchronous output. and this Logger output is very hard to look at. in production, then it makes sense.
CONFIG: Main::_loadConfigSettings()__checking config file :: remoteRunnPort = #7002
Jun 8, 2008 11:31:48 AM kuai.Main loadConfigSettings
CONFIG: Main::_loadConfigSettings()__checking config file :: fileSharePort = #7001
Jun 8, 2008 11:31:48 AM maui.engine.FileShareService run
FINER: ----FileShareService::_run()___running....
Jun 8, 2008 11:31:48 AM maui.engine.DataService openNewConnections
FINER: ____----DataService::_openConnections()___opening 3 new connections___pool size = 0__idle = 0
Jun 8, 2008 11:31:48 AM maui.engine.FileShareService run
FINEST: ----FileShareService::_run()___LISTENING on port #7001....
Jun 8, 2008 11:31:48 AM maui.engine.DataService openNewConnections
FINEST: ____----DataService::_openConnections()___new connection___pool size = 1__idle = 1
Jun 8, 2008 11:31:48 AM maui.engine.DataService openNewConnections
FINEST: ____----DataService::_openConnections()___new connection___pool size = 2__idle = 2
what i want to see:
Main::_loadConfigSettings()__checking config file :: resultsHandlerPort = #7002
Main::_loadConfigSettings()__checking config file :: fileSharePort = #7001
----FileShareService::_run()___running....
____----DataService::_openConnections()___opening 3 new connections___pool size = 0__idle = 0
----FileShareService::_run()___LISTENING on port #7001....
____----DataService::_openConnections()___new connection___pool size = 1__idle = 1
____====____====________ResultsHandler::_run()__starting....
_______________________________UserThread-01::_run()__starting....
____----DataService::_openConnections()___new connection___pool size = 2__idle = 2
____----DataService::_openConnections()___new connection___pool size = 3__idle = 3
____====____====________ResultsHandler::_run()__LISTENING on port #7002
i don't know how to use the NetBeans debugger with so much threading (or really at all).
so, i use the good-old: " +System.out.println():+ "
and, once i get a thread working ok, i comment out all the print lines:
// ____----DataService::_openConnections()___new connection___pool size = 2__idle = 2
// ____----DataService::_openConnections()___new connection___pool size = 3__idle = 3
the Logger gives way too much output, and i need to do like:
"thread #1 = nothing ; thread #2 = *FINEST* ; thread #3 = *INFO* ; ...."
if some can tell me a better way to debug heavily threaded code, that would be the
greatest gift of all. i get confused too often and waste so much time.
JUnit testing threaded code.. its just not possible with so much asynchronousity (right?).
Edited by: pdFrog on Jun 8, 2008 5:14 PM