Can you generate a stack trace during the hang?
On 7/10/06, John Apling <[EMAIL PROTECTED]> wrote:
Hi,
We're experiencing an intermittent problem (roughly 1 in 15 times) whereby
sometimes our Java application hangs soon after starting. It all started after
we upgraded the version of Java from 1.3.1.16 to 1.5.0.06 (everything was fine
before). We are using Log4J version 1.2.6. We have 2 threads that are started
from the static initialiser of the initial class. When the problem occurs
within each thread (in every case of failure) they both hang at the point where
the following statement is called:
if (m_logger.isEnabledFor(Level.INFO))
(where m_logger is defined as "private static final Logger m_logger =
Logger.getLogger(Server.class.getName());")
We know it hangs at this point as we have system.out.println() statements
immediately before and after this statement.
The Java process still exists but the process hangs indefinitely.
I have tried upgrading Log4J to version 1.2.13 but the same problem still
occurs.
I have searched every Log4J bug on the buglist and also searched the Log4J
mailing lists as well as google searches and cannot find anything similar.
Does anyone have any idea why this might be failing?
(c) Message Copyright EMX Company Limited 2006. All rights reserved.
Full email disclaimer can be viewed at:
http://www.emx.co.uk/disclaimer.html
EMX Company Limited.
Tel: 01279 858300, Fax: 01279 858301, Client Services Tel: 01279 858333,
Website: www.emx.co.uk
Calls, e-mails and written correspondence may be monitored to assist with
training, policy enforcement and resolution of disputes.
____________________________________________________________________
This email has been scanned for all viruses by MessageLabs.
--
James Stauffer
Are you good? Take the test at http://www.livingwaters.com/good/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
