So I was able to download this and replicate your results.
I've adjusted my logger config to account for other classes in a
different package (org.comtor rather than org.comtor.drivers) and that
works. Thus, my issue apparently is specific to this particular one
class. Debugging continues as I
That is good to know. However, your test has spawned a suspicion that the
problem may be related to one class starting with the name of the other. Try
renaming Comtor or ComtorStandAlone so they don't overlap and see if the
problem goes away. If it does then it is a bug in Log4j.
I'll try
OK - I tried my theory and didn't have any problems.
Ralph
On Oct 23, 2012, at 10:59 AM, Ralph Goers wrote:
That is good to know. However, your test has spawned a suspicion that the
problem may be related to one class starting with the name of the other. Try
renaming Comtor or
OK, I'll try as you suggested when I can... I'm leaving to head to a
talk at Google in NYC, so this may not happen for a day or two...
trying to avoid shipping you code, but if we have to I will.
Thanks for the help!
On Tue, Oct 23, 2012 at 2:36 PM, Ralph Goers ralph.go...@dslextreme.com wrote:
BTW - I just want to make sure that you are aware that instead of unzipping all
your jars and rezipping into one new jar that another alternative you have is
to just place all the jars in one directory. Then, instead of placing the
log4j jars in lib/ext or combining them with your classes you
No more unzipping/rejarring. Will try to see utility there is a difference in
behavior when they are in the same base dir.
Ralph Goers ralph.go...@dslextreme.com wrote:
BTW - I just want to make sure that you are aware that instead of
unzipping all your jars and rezipping into one new jar that
Debugging on the train it's in the name of the class More later
Ralph Goers ralph.go...@dslextreme.com wrote:
BTW - I just want to make sure that you are aware that instead of
unzipping all your jars and rezipping into one new jar that another
alternative you have is to just place
