Bug 45304 - using log4j with OAS for some reasone all the logging activty hangs from all the applications deployed
Summary: using log4j with OAS for some reasone all the logging activty hangs from all ...
Status: NEEDINFO
Alias: None
Product: Log4j - Now in Jira
Classification: Unclassified
Component: Other (show other bugs)
Version: 1.2
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: log4j-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-29 03:51 UTC by Amgad Muhammad
Modified: 2009-01-15 07:05 UTC (History)
0 users



Attachments
The log4j property file (5.72 KB, text/plain)
2008-07-03 04:23 UTC, Amgad Muhammad
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Amgad Muhammad 2008-06-29 03:51:13 UTC
 
Comment 1 Thorbjørn Ravn Andersen 2008-07-02 16:58:18 UTC
Please provide additional information on this issue.  

Can you provide a small example which behaves like you describe?
Comment 2 Amgad Muhammad 2008-07-03 00:49:09 UTC
(In reply to comment #1)
> Please provide additional information on this issue.  
> Can you provide a small example which behaves like you describe?

I'm using log4j on Oracle Application Server.and i'm configuring the log4j from a property file not on runtime, and am using category instead of logger.

everything is working fine but suddenly all the logging activity hangs. to restore the logging activity i have to restart the OC4j.

non from the applications deployed on the OC4J configure the log4j on runtime so it's configured only once on startup.

i need to know what is causing this.
-----------------------------------
example of loading the log4j:

private org.apache.log4j.Category logger;

logger = org.apache.log4j.Category.getInstance("ZainKSABilling");
-----------------------------------
does the deprecated method getinstance could have something to do with this issue?
Comment 3 Thorbjørn Ravn Andersen 2008-07-03 03:53:43 UTC
Please provide the property file you use, and a thread dump (JVM and OS dependant) of OC4J of the situation where logging has stopped.  My guess is that this is a resource deadlock.

How many web applications do you run in OC4J?
Comment 4 Amgad Muhammad 2008-07-03 04:23:00 UTC
Created attachment 22212 [details]
The log4j property file

as soon as the hanging starts all the logging files defined in this property file stop being updated.

there are 18 different application
Comment 5 Amgad Muhammad 2008-07-03 04:33:08 UTC
I'll provide the thread dump as soon as the hanging starts