Log4j-1.2.7 axis weblogic 6.1

Hi,
I'm trying to deploy a J2EE application composed by two stateless ejb
(say A and B) in weblogic 6.1.
The A ejb uses log4j as logging tool.
The B ejb use axis for accessing remote web services and
weblogic.logging.NonCatalogLogger as logging tool.
There aren't errors when I deploy the ear, but when I try to access
the B ejb I obtain the errors reported later (I can call the B ejb's
method, but the method fails when it invokes the web service...).
Note: If I **not** use log4j in the A ejb, the B ejb works fine!!!
I suppose that log4j creates some conflicts when used in conjuction
with axis in weblogic environment...
If other informations are nedeed, please ask to me.
Every comment is greatly appreciated.
Thanx in advance,
Simone
############################ logs from StartDefaultServer Window
log4j: Threshold ="null".
log4j: Level value for root is [debug].
log4j: root level set to DEBUG
log4j: Class name: [org.apache.log4j.ConsoleAppender]
log4j: Setting property [threshold] to [FATAL].
log4j: Setting property [target] to [System.out].
log4j: Parsing layout of class: "org.apache.log4j.PatternLayout"
log4j: Setting property [conversionPattern] to [%d{yyyy-MM-dd
HH:mm:ss} [CNFG] %
-5p %c{1}(%F:%L) - %m%n].
log4j: Adding appender named [console] to category [root].
log4j: Class name: [org.apache.log4j.DailyRollingFileAppender]
log4j: Setting property [file] to [cnfg.log].
log4j: Setting property [append] to [true].
log4j: Setting property [datePattern] to ['.'yyyy-MM-dd'.log'].
log4j: Parsing layout of class: "org.apache.log4j.PatternLayout"
log4j: Setting property [conversionPattern] to [%d{yyyy-MM-dd
HH:mm:ss} [CNFG] %
-5p %c{1}(%F:%L) - %m%n].
log4j: setFile called: cnfg.log, true
log4j: setFile ended
log4j: Appender [file] to be rolled at midnight.
log4j: Adding appender named [file] to category [root].
log4j: Class name: [org.apache.log4j.FileAppender]
log4j: Setting property [threshold] to [FATAL].
log4j: Setting property [file] to [fatal-wls.log].
log4j: Parsing layout of class: "org.apache.log4j.PatternLayout"
log4j: Setting property [conversionPattern] to [%d{yyyy-MM-dd
HH:mm:ss} [CNFG] %
-5p %c{1}(%F:%L) - %m%n].
log4j: setFile called: fatal-wls.log, true
log4j: setFile ended
log4j: Adding appender named [fatalLog] to category [root].
log4j: cnfg.log -> cnfg.log.2003-05-15.log
log4j: setFile called: cnfg.log, false
log4j: setFile ended
<16-mag-03 10.12.14 CEST> <Error>
<com.reply.trilogy.self.EAI_PublisherCOM.EAI_P
ublisherEJBBean_9ox0hf_Impl> <; nested exception is:
org.xml.sax.SAXParseException: The root element is required in
a well-fo
rmed document.
org.xml.sax.SAXParseException: The root element is required in a
well-formed doc
ument.
org.xml.sax.SAXParseException: The root element is required in a
well-formed doc
ument.
at weblogic.apache.xerces.framework.XMLParser.reportError(XMLParser.java
:1090)
at weblogic.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLErr
or(XMLDocumentScanner.java:655)
at weblogic.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher
.endOfInput(XMLDocumentScanner.java:875)
at weblogic.apache.xerces.framework.XMLDocumentScanner.endOfInput(XMLDoc
umentScanner.java:447)
at weblogic.apache.xerces.validators.common.XMLValidator.sendEndOfInputN
otifications(XMLValidator.java:691)
at weblogic.apache.xerces.readers.DefaultEntityHandler.changeReaders(Def
aultEntityHandler.java:1036)
at weblogic.apache.xerces.readers.XMLEntityReader.changeReaders(XMLEntit
yReader.java:168)
at weblogic.apache.xerces.readers.AbstractCharReader.changeReaders(Abstr
actCharReader.java:150)
at weblogic.apache.xerces.readers.AbstractCharReader.lookingAtChar(Abstr
actCharReader.java:217)
at weblogic.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher
.dispatch(XMLDocumentScanner.java:771)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocu
mentScanner.java:396)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:975)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:123)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:125)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:346)
at org.apache.axis.encoding.DeserializationContextImpl.parse(Deserializa
tionContextImpl.java:201)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:428)
at org.apache.axis.client.Call.invoke(Call.java:1794)
at org.apache.axis.client.Call.invoke(Call.java:1596)
at org.apache.axis.client.Call.invoke(Call.java:1515)
at org.apache.axis.client.Call.invoke(Call.java:1095)
at com.reply.trilogy.self.EAI_PublisherCOM.IPublisherSoapBindingStub.get
ComponentVersion(Unknown Source)
at com.reply.trilogy.self.EAI_PublisherCOM.EAI_PublisherEJBBean.getCompo
nentVersion(Unknown Source)
at com.reply.trilogy.self.EAI_PublisherCOM.EAI_PublisherEJBBean_9ox0hf_E
OImpl.getComponentVersion(EAI_PublisherEJBBean_9ox0hf_EOImpl.java:36)
at com.reply.trilogy.self.EAI_PublisherCOM.EAI_PublisherEJBBean_9ox0hf_E
OImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
ef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:274)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
########################## logs from weblogic.log
####<16-mag-03 10.11.10 CEST> <Info> <EJB> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <010008> <EJB Deploying file: cnfg-ejb.jar>
####<16-mag-03 10.11.10 CEST> <Info> <EJB> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <010009> <EJB Deployed EJB with JNDI name
com.etnoteam.trilogy.cnfg.ejb.CnfgDBAccessor.>
####<16-mag-03 10.11.10 CEST> <Info> <J2EE> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <160003> <Deployed : cnfg-ejb>
####<16-mag-03 10.11.10 CEST> <Info> <EJB> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <010008> <EJB Deploying file: self-ejb.jar>
####<16-mag-03 10.11.11 CEST> <Info> <EJB> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <010009> <EJB Deployed EJB with JNDI name EAI_PublisherEJB.>
####<16-mag-03 10.11.11 CEST> <Info> <EJB> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <010009> <EJB Deployed EJB with JNDI name WAPConfigEJB.>
####<16-mag-03 10.11.11 CEST> <Info> <EJB> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <010009> <EJB Deployed EJB with JNDI name HandsetConfigEJB.>
####<16-mag-03 10.11.11 CEST> <Info> <J2EE> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <160003> <Deployed : self-ejb>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101183> <[HTTP myserver] Unloading web app: certificate>
####<16-mag-03 10.11.11 CEST> <Info> <J2EE> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <160004> <Undeployed : certificate>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101053> <[HTTP myserver] Loading web app: certificate>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101059> <[myserver] Loading certificate from WAR file:
C:\bea\wlserver6.1\.\config\mydomain\applications\.wlnotdelete\wl_comp41793.war>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101031> <[WebAppServletContext(2620057,certificate,/certificate)]
extracting classfiles to
C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\WEB-INF\_tmp_war_certificate:>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101032> <[WebAppServletContext(2620057,certificate,/certificate)]
extracted classfiles successfully...>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP Session> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <100037> <Creating SessionContext of type: memory for webapp:
/certificate>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(2620057,certificate,/certificate)]
registering classpath servlet with initArgs 'null'>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(2620057,certificate,/certificate)]
registering getior servlet with initArgs 'null'>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(2620057,certificate,/certificate)]
registering tunneling servlets with initArgs
'wl-dispatch-policy=direct'>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(2620057,certificate,/certificate)]
registering JSPServlet with initArgs '[JspConfig:
verbose=true,packagePrefix=jsp_servlet,-compiler=javac,compileFlags=,workingDir=C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\WEB-INF\_tmp_war_certificate,pageCheckSeconds=1,superclass=null,keepgenerated=false,precompileContinue=false,compilerSupportsEncoding=true,encoding=null,defaultfilename=index.jsp,compilerclass=null,noTryBlocks=false]'>
####<16-mag-03 10.11.11 CEST> <Debug> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101097> <Registering ServletContext: "certificate:/certificate">
####<16-mag-03 10.11.11 CEST> <Info> <J2EE> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <160003> <Deployed : certificate>
####<16-mag-03 10.12.14 CEST> <Error>
<com.reply.trilogy.self.EAI_PublisherCOM.EAI_PublisherEJBBean_9ox0hf_Impl>
<obi> <myserver> <ExecuteThread: '14' for queue: 'default'> <>
<0:aa08131a7f28edb9> <000000> <; nested exception is:
     org.xml.sax.SAXParseException: The root element is required in a
well-formed document.>
org.xml.sax.SAXParseException: The root element is required in a
well-formed document.
org.xml.sax.SAXParseException: The root element is required in a
well-formed document.
     at weblogic.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1090)
     at weblogic.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:655)
     at weblogic.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.endOfInput(XMLDocumentScanner.java:875)
     at weblogic.apache.xerces.framework.XMLDocumentScanner.endOfInput(XMLDocumentScanner.java:447)
     at weblogic.apache.xerces.validators.common.XMLValidator.sendEndOfInputNotifications(XMLValidator.java:691)
     at weblogic.apache.xerces.readers.DefaultEntityHandler.changeReaders(DefaultEntityHandler.java:1036)
     at weblogic.apache.xerces.readers.XMLEntityReader.changeReaders(XMLEntityReader.java:168)
     at weblogic.apache.xerces.readers.AbstractCharReader.changeReaders(AbstractCharReader.java:150)
     at weblogic.apache.xerces.readers.AbstractCharReader.lookingAtChar(AbstractCharReader.java:217)
     at weblogic.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:771)
     at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:396)
     at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:975)
     at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:123)
     at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:125)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:346)
     at org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:201)
     at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:428)
     at org.apache.axis.client.Call.invoke(Call.java:1794)
     at org.apache.axis.client.Call.invoke(Call.java:1596)
     at org.apache.axis.client.Call.invoke(Call.java:1515)
     at org.apache.axis.client.Call.invoke(Call.java:1095)
     at com.reply.trilogy.self.EAI_PublisherCOM.IPublisherSoapBindingStub.getComponentVersion(Unknown
Source)
     at com.reply.trilogy.self.EAI_PublisherCOM.EAI_PublisherEJBBean.getComponentVersion(Unknown
Source)
     at com.reply.trilogy.self.EAI_PublisherCOM.EAI_PublisherEJBBean_9ox0hf_EOImpl.getComponentVersion(EAI_PublisherEJBBean_9ox0hf_EOImpl.java:36)
     at com.reply.trilogy.self.EAI_PublisherCOM.EAI_PublisherEJBBean_9ox0hf_EOImpl_WLSkel.invoke(Unknown
Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
####<16-mag-03 10.15.32 CEST> <Info> <Management> <obi> <myserver>
<ExecuteThread: '10' for queue: 'default'> <system> <> <140009>
<Configuration changes for domain saved to the repository.>

Hi Rob,
thanks for the response.
I'll report later the SOAP messages involved in web service
invocation.
Note the SOAP messages are the **same** in the case the A ejb dont't
uses log4j (...and the B ejb works fine) and in the case the A ejb
uses log4j (the B ejb report the error in invoking the web service).
P.S. I obtain the same errors if I don't include the A ejb in the EAR
and the B ejb use log4j instead of weblogic.logging.NonCatalogLogger.
Any idea?
This is the dump:
==== Request ====
POST /app/EAI_Publisher.WSDL HTTP/1.0
Content-Length: 487
Host: 10.254.2.114
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://10.254.2.114:3333/EAI_Publisher/action/iPublisher.GetComponentVersion"
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<ns1:GetComponentVersion
xmlns:ns1="http://10.254.2.114:3333/EAI_Publisher/message/"/>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
==== Response ====
HTTP/1.1 200 OK
Server: Microsoft-IIS/4.0
Date: Thu, 22 May 2003 13:35:59 GMT
Content-Type: text/xml; charset="UTF-16"
Content-Length: 1168
Expires: -1;
ÿþ
< ? x m l v e r s i o n = " 1 . 0 " e n c o d i n g = " U T F - 1
6 " s t a n d a l o n e = " n o " ? >
< S O A P - E N V : E n v e l o p e x m l n s : S O A P S D K 1 = "
h t t p : / / w w w . w 3 . o r g / 2 0 0 1 / X M L S c h e m a " x
m l n s : S O A P S D K 2 = " h t t p : / / w w w . w 3 . o r g / 2 0
0 1 / X M L S c h e m a - i n s t a n c e " x m l n s : S O A P S D
K 3 = " h t t p : / / s c h e m a s . x m l s o a p . o r g / s o a p
/ e n c o d i n g / " x m l n s : S O A P - E N V = " h t t p : / /
s c h e m a s . x m l s o a p . o r g / s o a p / e n v e l o p e / "
>
< S O A P - E N V : B o d y S O A P - E N V : e n c o d i n g S t
y l e = " h t t p : / / s c h e m a s . x m l s o a p . o r g / s o a
p / e n c o d i n g / " >
< S O A P S D K 4 : G e t C o m p o n e n t V e r s i o n R e s p o
n s e x m l n s : S O A P S D K 4 = " h t t p : / / 1 0 . 2 5 4 . 2
. 1 1 4 : 3 3 3 3 / E A I _ P u b l i s h e r / m e s s a g e / " >
< R e s u l t > 1 . 0 . 8
< / R e s u l t >
< / S O A P S D K 4 : G e t C o m p o n e n t V e r s i o n R e
s p o n s e >
< / S O A P - E N V : B o d y >
< / S O A P - E N V : E n v e l o p e >
Rob Woollen <[email protected]> wrote in message news:<[email protected]>...
I think you'll need to do some more debugging here before we can help
you. It looks like AXIS is failing to parse an XML document it receives
as a Web Service response. I would suggest printing out the XML
document it receives. I suspect it is not XML.
-- Rob
Simone wrote:
Hi,
I'm trying to deploy a J2EE application composed by two stateless ejb
(say A and B) in weblogic 6.1.
The A ejb uses log4j as logging tool.
The B ejb use axis for accessing remote web services and
weblogic.logging.NonCatalogLogger as logging tool.
There aren't errors when I deploy the ear, but when I try to access
the B ejb I obtain the errors reported later (I can call the B ejb's
method, but the method fails when it invokes the web service...).
Note: If I **not** use log4j in the A ejb, the B ejb works fine!!!
I suppose that log4j creates some conflicts when used in conjuction
with axis in weblogic environment...
If other informations are nedeed, please ask to me.
Every comment is greatly appreciated.
Thanx in advance,
Simone
############################ logs from StartDefaultServer Window
log4j: Threshold ="null".
log4j: Level value for root is [debug].
log4j: root level set to DEBUG
log4j: Class name: [org.apache.log4j.ConsoleAppender]
log4j: Setting property [threshold] to [FATAL].
log4j: Setting property [target] to [System.out].
log4j: Parsing layout of class: "org.apache.log4j.PatternLayout"
log4j: Setting property [conversionPattern] to [%d{yyyy-MM-dd
HH:mm:ss} [CNFG] %
-5p %c{1}(%F:%L) - %m%n].
log4j: Adding appender named [console] to category [root].
log4j: Class name: [org.apache.log4j.DailyRollingFileAppender]
log4j: Setting property [file] to [cnfg.log].
log4j: Setting property [append] to [true].
log4j: Setting property [datePattern] to ['.'yyyy-MM-dd'.log'].
log4j: Parsing layout of class: "org.apache.log4j.PatternLayout"
log4j: Setting property [conversionPattern] to [%d{yyyy-MM-dd
HH:mm:ss} [CNFG] %
-5p %c{1}(%F:%L) - %m%n].
log4j: setFile called: cnfg.log, true
log4j: setFile ended
log4j: Appender [file] to be rolled at midnight.
log4j: Adding appender named [file] to category [root].
log4j: Class name: [org.apache.log4j.FileAppender]
log4j: Setting property [threshold] to [FATAL].
log4j: Setting property [file] to [fatal-wls.log].
log4j: Parsing layout of class: "org.apache.log4j.PatternLayout"
log4j: Setting property [conversionPattern] to [%d{yyyy-MM-dd
HH:mm:ss} [CNFG] %
-5p %c{1}(%F:%L) - %m%n].
log4j: setFile called: fatal-wls.log, true
log4j: setFile ended
log4j: Adding appender named [fatalLog] to category [root].
log4j: cnfg.log -> cnfg.log.2003-05-15.log
log4j: setFile called: cnfg.log, false
log4j: setFile ended
<16-mag-03 10.12.14 CEST> <Error>
<com.reply.trilogy.self.EAI_PublisherCOM.EAI_P
ublisherEJBBean_9ox0hf_Impl> <; nested exception is:
org.xml.sax.SAXParseException: The root element is required in
a well-fo
rmed document.
org.xml.sax.SAXParseException: The root element is required in a
well-formed doc
ument.
org.xml.sax.SAXParseException: The root element is required in a
well-formed doc
ument.
at weblogic.apache.xerces.framework.XMLParser.reportError(XMLParser.java
:1090)
at weblogic.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLErr
or(XMLDocumentScanner.java:655)
at weblogic.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher
.endOfInput(XMLDocumentScanner.java:875)
at weblogic.apache.xerces.framework.XMLDocumentScanner.endOfInput(XMLDoc
umentScanner.java:447)
at weblogic.apache.xerces.validators.common.XMLValidator.sendEndOfInputN
otifications(XMLValidator.java:691)
at weblogic.apache.xerces.readers.DefaultEntityHandler.changeReaders(Def
aultEntityHandler.java:1036)
at weblogic.apache.xerces.readers.XMLEntityReader.changeReaders(XMLEntit
yReader.java:168)
at weblogic.apache.xerces.readers.AbstractCharReader.changeReaders(Abstr
actCharReader.java:150)
at weblogic.apache.xerces.readers.AbstractCharReader.lookingAtChar(Abstr
actCharReader.java:217)
at weblogic.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher
.dispatch(XMLDocumentScanner.java:771)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocu
mentScanner.java:396)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:975)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:123)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:125)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:346)
at org.apache.axis.encoding.DeserializationContextImpl.parse(Deserializa
tionContextImpl.java:201)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:428)
at org.apache.axis.client.Call.invoke(Call.java:1794)
at org.apache.axis.client.Call.invoke(Call.java:1596)
at org.apache.axis.client.Call.invoke(Call.java:1515)
at org.apache.axis.client.Call.invoke(Call.java:1095)
at com.reply.trilogy.self.EAI_PublisherCOM.IPublisherSoapBindingStub.get
ComponentVersion(Unknown Source)
at com.reply.trilogy.self.EAI_PublisherCOM.EAI_PublisherEJBBean.getCompo
nentVersion(Unknown Source)
at com.reply.trilogy.self.EAI_PublisherCOM.EAI_PublisherEJBBean_9ox0hf_E
OImpl.getComponentVersion(EAI_PublisherEJBBean_9ox0hf_EOImpl.java:36)
at com.reply.trilogy.self.EAI_PublisherCOM.EAI_PublisherEJBBean_9ox0hf_E
OImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
ef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:274)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
########################## logs from weblogic.log
####<16-mag-03 10.11.10 CEST> <Info> <EJB> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <010008> <EJB Deploying file: cnfg-ejb.jar>
####<16-mag-03 10.11.10 CEST> <Info> <EJB> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <010009> <EJB Deployed EJB with JNDI name
com.etnoteam.trilogy.cnfg.ejb.CnfgDBAccessor.>
####<16-mag-03 10.11.10 CEST> <Info> <J2EE> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <160003> <Deployed : cnfg-ejb>
####<16-mag-03 10.11.10 CEST> <Info> <EJB> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <010008> <EJB Deploying file: self-ejb.jar>
####<16-mag-03 10.11.11 CEST> <Info> <EJB> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <010009> <EJB Deployed EJB with JNDI name EAI_PublisherEJB.>
####<16-mag-03 10.11.11 CEST> <Info> <EJB> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <010009> <EJB Deployed EJB with JNDI name WAPConfigEJB.>
####<16-mag-03 10.11.11 CEST> <Info> <EJB> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <010009> <EJB Deployed EJB with JNDI name HandsetConfigEJB.>
####<16-mag-03 10.11.11 CEST> <Info> <J2EE> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <160003> <Deployed : self-ejb>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101183> <[HTTP myserver] Unloading web app: certificate>
####<16-mag-03 10.11.11 CEST> <Info> <J2EE> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <160004> <Undeployed : certificate>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101053> <[HTTP myserver] Loading web app: certificate>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101059> <[myserver] Loading certificate from WAR file:
C:\bea\wlserver6.1\.\config\mydomain\applications\.wlnotdelete\wl_comp41793.war>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101031> <[WebAppServletContext(2620057,certificate,/certificate)]
extracting classfiles to
C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\WEB-INF\_tmp_war_certificate:>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101032> <[WebAppServletContext(2620057,certificate,/certificate)]
extracted classfiles successfully...>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP Session> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <100037> <Creating SessionContext of type: memory for webapp:
/certificate>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(2620057,certificate,/certificate)]
registering classpath servlet with initArgs 'null'>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(2620057,certificate,/certificate)]
registering getior servlet with initArgs 'null'>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(2620057,certificate,/certificate)]
registering tunneling servlets with initArgs
'wl-dispatch-policy=direct'>
####<16-mag-03 10.11.11 CEST> <Info> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(2620057,certificate,/certificate)]
registering JSPServlet with initArgs '[JspConfig:
verbose=true,packagePrefix=jsp_servlet,-compiler=javac,compileFlags=,workingDir=C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\WEB-INF\_tmp_war_certificate,pageCheckSeconds=1,superclass=null,keepgenerated=false,precompileContinue=false,compilerSupportsEncoding=true,encoding=null,defaultfilename=index.jsp,compilerclass=null,noTryBlocks=false]'>
####<16-mag-03 10.11.11 CEST> <Debug> <HTTP> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <101097> <Registering ServletContext: "certificate:/certificate">
####<16-mag-03 10.11.11 CEST> <Info> <J2EE> <obi> <myserver>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <system>
<> <160003> <Deployed : certificate>
####<16-mag-03 10.12.14 CEST> <Error>
<com.reply.trilogy.self.EAI_PublisherCOM.EAI_PublisherEJBBean_9ox0hf_Impl>
<obi> <myserver> <ExecuteThread: '14' for queue: 'default'> <>
<0:aa08131a7f28edb9> <000000> <; nested exception is:
     org.xml.sax.SAXParseException: The root element is required in a
well-formed document.>
org.xml.sax.SAXParseException: The root element is required in a
well-formed document.
org.xml.sax.SAXParseException: The root element is required in a
well-formed document.
     at weblogic.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1090)
     at weblogic.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:655)
     at weblogic.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.endOfInput(XMLDocumentScanner.java:875)
     at weblogic.apache.xerces.framework.XMLDocumentScanner.endOfInput(XMLDocumentScanner.java:447)
     at weblogic.apache.xerces.validators.common.XMLValidator.sendEndOfInputNotifications(XMLValidator.java:691)
     at weblogic.apache.xerces.readers.DefaultEntityHandler.changeReaders(DefaultEntityHandler.java:1036)
     at weblogic.apache.xerces.readers.XMLEntityReader.changeReaders(XMLEntityReader.java:168)
     at weblogic.apache.xerces.readers.AbstractCharReader.changeReaders(AbstractCharReader.java:150)
     at weblogic.apache.xerces.readers.AbstractCharReader.lookingAtChar(AbstractCharReader.java:217)
     at weblogic.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:771)
     at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:396)
     at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:975)
     at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:123)
     at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:125)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:346)
     at org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:201)
     at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:428)
     at org.apache.axis.client.Call.invoke(Call.java:1794)
     at org.apache.axis.client.Call.invoke(Call.java:1596)
     at org.apache.axis.client.Call.invoke(Call.java:1515)
     at org.apache.axis.client.Call.invoke(Call.java:1095)
     at com.reply.trilogy.self.EAI_PublisherCOM.IPublisherSoapBindingStub.getComponentVersion(Unknown
Source)
     at com.reply.trilogy.self.EAI_PublisherCOM.EAI_PublisherEJBBean.getComponentVersion(Unknown
Source)
     at com.reply.trilogy.self.EAI_PublisherCOM.EAI_PublisherEJBBean_9ox0hf_EOImpl.getComponentVersion(EAI_PublisherEJBBean_9ox0hf_EOImpl.java:36)
     at com.reply.trilogy.self.EAI_PublisherCOM.EAI_PublisherEJBBean_9ox0hf_EOImpl_WLSkel.invoke(Unknown
Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
####<16-mag-03 10.15.32 CEST> <Info> <Management> <obi> <myserver>
<ExecuteThread: '10' for queue: 'default'> <system> <> <140009>
<Configuration changes for domain saved to the repository.>

Similar Messages

Using log4j v.1.2 with Weblogic 7.0

I try to use logging pissibilities of Log4j with Weblogic 7.0 using com.bea.logging.WeblogicAppender
class from logtoolkit.jar.
When I use Weblogic's version of Log4j (v. 1.1.3), all is OK. When I try to use
current version of Log4j (v.1.2.6), I receive java.lang.NoSuchFieldError: priority
at com.bea.logging.WeblogicAppender.append(Unknown Source)
     at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)
     at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:57)
     at org.apache.log4j.Category.callAppenders(Category.java:187)
     at org.apache.log4j.Category.forcedLog(Category.java:372)
     at org.apache.log4j.Category.info(Category.java:674)
     at com.mydomain.framework.log.Log4JLogger.logInfo(Log4JLogger.java:73)
There is configuration file:
<log4j:configuration>
<appender name="WeblogicAppender" class="com.bea.logging.WeblogicAppender">
     <layout class="org.apache.log4j.PatternLayout"></layout>
</appender>
<root>
<priority value ="debug" />
<appender-ref ref="WeblogicAppender"/>
</root>
</log4j:configuration>
Does anybody know this problem?

Try changing "priority" to "level".
Kevin

Log4j Error while deploying application in weblogic

Hi All,
I am deploying one web application in weblogic, which uses log4j jar file to write logs. But ahile deploying it shows the following error in weblogic console.
Please help on this.
log4j:ERROR A "org.apache.log4j.RollingFileAppender" object is not assignable to a "org.apache.log4j.Appender" variable.
log4j:ERROR The class "org.apache.log4j.Appender" was loaded by
log4j:ERROR [sun.misc.Launcher$AppClassLoader@169e11] whereas object of type
log4j:ERROR "org.apache.log4j.RollingFileAppender" was loaded by [weblogic.utils.classloaders.ChangeAwareClassLoader@169baee finder: weblogic.utils.classloaders.CodeGenClassFinder@44c4a4 annotation: Server@Server].
log4j:ERROR Could not instantiate appender named "log".
log4j:WARN No appenders could be found for logger (com.servion.citigreece.util.LoggerUtil).
log4j:WARN Please initialize the log4j system properly.
Thanks & Regards,
Raja Mohammed.

Seems like a classic case of having log4j both in the war and the app-server's own libraries.
At least in JBoss this would be fixed by making sure that common/lib's log4j jar is being used (or alternatively, removing that and using the one in the war, but that might not go as smooth).

Log4j not logging messages out to weblogic console for custom automatplugin

Hi,
We have a custom automation plugin for the OSM application build 381 in our environment(HP-UX Itanium platform). The plugins are bundled in a single ear application "A.ear" which is a mixed bag of pre-defined automation plugins of type XsltSender, XsltAutomator(both InternalReciever as well ExternalReceiver) as well other custom automators(java). For logging of messages in order to aid debugging of custom automators, we are using a logger "com.xyz.osm.plugin" which is also declared in log4j.xml file that is within omslogging.jar. You must already be aware that the build scripts of assembling, deploying ansd registering plugins also includes omslogging.jar are part of the application ear.
<category name="com.mtsa.osm.plugin">
<priority value="debug"/>
</category>
Below java code snippet is taken from our custom automation plugin classes indicating how the above logger is being used for printing messages.
//Declaration
private static Log log = LogFactory.getLog("com.mtsa.osm.plugin");
mthod1(){
log.info("xyz");
In addition to the above logger, the pre-defined automators XsltSender, XsltReceiver also enable logging from xsl files by making the "log" parameter available. Thus we have lines such as the one below in our xsl files that should print messages to the weblogic console.
<xsl:variable name="addLog1" select="java:info($log, 'transformSiebelActivationRequest: ***** Starting *****')"/>
The logger that allows printing of these lines is "com.mslv.oms.automation".
<category name="com.mslv.oms.automation">
<priority value="info"/>
</category>
These configurations should have ideally allowed one to see messages such as one below getting printed out to weblogic console:
<16-Mar-2012 8:59:36,931 CDT PM> <INFO> <plugin.XSLTReceiver> <ExecuteThread: '19' for queue: 'oms.automation'> <transformSiebelActivationRequest: ***** Starting *****>
Unfotunately after having done all the above configuration, we are still unable to see any such log messages in the console apart from those emitting from SOP and from <xsl:message> inserted in java & xsl files respectively.
I also checked if the log4j sub-system is able to correctly initialize after parsing the log4j.xml. It does and one can confirm it by setting system property log4j.debug=true in setDomainEnv.sh file.
$$$$$$$$ log4j initialization by application classloader for oms.ear application $$$$$$$$$$$$$$$$$$
log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1592141 finder: weblogic.utils.classloaders.CodeGenClassFinder@1112e85 annotation: oms@.
log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/oms/amuube/omslogging.jar!/log4j.xml] for automatic log4j configuration.
log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
log4j: System property is :null
log4j: Standard DocumentBuilderFactory search succeded.
log4j: DocumentBuilderFactory is: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
$$$$$$$$ log4j initialization by application classloader for custom automation plugin xyz.ear application $$$$$$$$$$$$$$$$$$
log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1b7a8c5 finder: weblogic.utils.classloaders.CodeGenClassFinder@10bc849 annotation: xyz.ear@.
log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/xyz.ear/ah0eeq/omslogging.jar!/log4j.xml] for automatic log4j configuration.
log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
log4j: System property is :null
log4j: Standard DocumentBuilderFactory search succeded.
log4j: DocumentBuilderFactory is: weblogic.xml.jaxp.RegistryDocumentBuilderFactory
log4j: debug attribute= "false".
Ironically, logging levels for loggers defined in log4j.xml of oms.ear could be dynamically changed from log4jAdmin.jsp page and the results are immediately visible. However for some reason, loggers defined in log4j.xml of custom plugin application were completely getting ignored. I don't see any warnings or erro messages in the logs indicating that log4j configuration failed for custom application failed. We want to refrain using SOP and <xsl:message> but I am afraid we have no option other than filling up our sources files with them.
Bottomline, how do we get application B(which in our case is the custom plugin) to log messaged the console just like that done by application A(oms.ear).
I am sure OSM developers would like to leverage log4j bundled with OSM SDK to log messages that would aid in trouble-shooting during development cycles. Both application ear files have commons-logging-1.1.jar,log4j-1.2.13.jar, omslogging.jar available in their classpaths. In other words, META-INF/MANIFEST.MF file of oms.war(web module within oms.ear) and xyz.jar(ejb module within xyz.ear) has references to these jars.
Appreciate if one can reply and let me know if they could get log messages to print from custom plugin.
Thanks
Edited by: user3693508 on Mar 18, 2012 11:38 AM

Hi,
We have a custom automation plugin for the OSM application build 381 in our environment(HP-UX Itanium platform). The plugins are bundled in a single ear application "A.ear" which is a mixed bag of pre-defined automation plugins of type XsltSender, XsltAutomator(both InternalReciever as well ExternalReceiver) as well other custom automators(java). For logging of messages in order to aid debugging of custom automators, we are using a logger "com.xyz.osm.plugin" which is also declared in log4j.xml file that is within omslogging.jar. You must already be aware that the build scripts of assembling, deploying ansd registering plugins also includes omslogging.jar are part of the application ear.
<category name="com.mtsa.osm.plugin">
<priority value="debug"/>
</category>
Below java code snippet is taken from our custom automation plugin classes indicating how the above logger is being used for printing messages.
//Declaration
private static Log log = LogFactory.getLog("com.mtsa.osm.plugin");
mthod1(){
log.info("xyz");
In addition to the above logger, the pre-defined automators XsltSender, XsltReceiver also enable logging from xsl files by making the "log" parameter available. Thus we have lines such as the one below in our xsl files that should print messages to the weblogic console.
<xsl:variable name="addLog1" select="java:info($log, 'transformSiebelActivationRequest: ***** Starting *****')"/>
The logger that allows printing of these lines is "com.mslv.oms.automation".
<category name="com.mslv.oms.automation">
<priority value="info"/>
</category>
These configurations should have ideally allowed one to see messages such as one below getting printed out to weblogic console:
<16-Mar-2012 8:59:36,931 CDT PM> <INFO> <plugin.XSLTReceiver> <ExecuteThread: '19' for queue: 'oms.automation'> <transformSiebelActivationRequest: ***** Starting *****>
Unfotunately after having done all the above configuration, we are still unable to see any such log messages in the console apart from those emitting from SOP and from <xsl:message> inserted in java & xsl files respectively.
I also checked if the log4j sub-system is able to correctly initialize after parsing the log4j.xml. It does and one can confirm it by setting system property log4j.debug=true in setDomainEnv.sh file.
$$$$$$$$ log4j initialization by application classloader for oms.ear application $$$$$$$$$$$$$$$$$$
log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1592141 finder: weblogic.utils.classloaders.CodeGenClassFinder@1112e85 annotation: oms@.
log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/oms/amuube/omslogging.jar!/log4j.xml] for automatic log4j configuration.
log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
log4j: System property is :null
log4j: Standard DocumentBuilderFactory search succeded.
log4j: DocumentBuilderFactory is: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
$$$$$$$$ log4j initialization by application classloader for custom automation plugin xyz.ear application $$$$$$$$$$$$$$$$$$
log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1b7a8c5 finder: weblogic.utils.classloaders.CodeGenClassFinder@10bc849 annotation: xyz.ear@.
log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/xyz.ear/ah0eeq/omslogging.jar!/log4j.xml] for automatic log4j configuration.
log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
log4j: System property is :null
log4j: Standard DocumentBuilderFactory search succeded.
log4j: DocumentBuilderFactory is: weblogic.xml.jaxp.RegistryDocumentBuilderFactory
log4j: debug attribute= "false".
Ironically, logging levels for loggers defined in log4j.xml of oms.ear could be dynamically changed from log4jAdmin.jsp page and the results are immediately visible. However for some reason, loggers defined in log4j.xml of custom plugin application were completely getting ignored. I don't see any warnings or erro messages in the logs indicating that log4j configuration failed for custom application failed. We want to refrain using SOP and <xsl:message> but I am afraid we have no option other than filling up our sources files with them.
Bottomline, how do we get application B(which in our case is the custom plugin) to log messaged the console just like that done by application A(oms.ear).
I am sure OSM developers would like to leverage log4j bundled with OSM SDK to log messages that would aid in trouble-shooting during development cycles. Both application ear files have commons-logging-1.1.jar,log4j-1.2.13.jar, omslogging.jar available in their classpaths. In other words, META-INF/MANIFEST.MF file of oms.war(web module within oms.ear) and xyz.jar(ejb module within xyz.ear) has references to these jars.
Appreciate if one can reply and let me know if they could get log messages to print from custom plugin.
Thanks
Edited by: user3693508 on Mar 18, 2012 11:38 AM

How to make integrated weblogic server use log4j

Hi all,
I use Jdeveloper 11.1.1.6, WL 10.3 on Win7. JDK 1.6.0.3x64
I tried to configure for 1 day during according to guides and informations on net. But i can not make it works unfortunately. Just after i start wls, encountered this:
<14-12-2012 10:42:00 o'clock EET> <Error> <Log Management> <BEA-170022> <Log4j failed to initialize for DefaultServer. The default JDK Logging implementation will be used.
java.lang.ClassNotFoundException: weblogic.logging.log4j.JDKLog4jAdapterFactory
     at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
     Truncated. see log file for complete stacktrace
>
I followed up basically through those links log4j Configuration in Standalone Weblogic Server - ADF and http://docs.oracle.com/cd/E15051_01/wls/docs103/logging/config_logs.html#using_log4j
I changed Logging implementation as Log4j from JDK: http://www.2hotfile.com/image.php?di=72YU
I created log4j.xml file under my %DOMAINHOME%\config : http://www.2hotfile.com/image.php?di=JHLI
<?xml version="1.0" encoding="UTF-8" ?><!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration>
<appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
<param name="Threshold" value="INFO"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern"
value="%d{ABSOLUTE} %-5p [%c{1}] %m%n"/>
</layout>
</appender>
<appender name="FILE" class="org.apache.log4j.DailyRollingFileAppender">
<param name="File" value="/log/daily.log"/>
<param name="Append" value="false"/>

<param name="DatePattern" value="'.'yyyy-MM-dd"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
</layout>
</appender>
<logger name="org.apache">
<level value="WARN"/>
</logger>
<root>
<level value="DEBUG"/>
<appender-ref ref="FILE"/>

</root>
</log4j:configuration>
i copied log4j.jar, wllog.jar into my %DOMAINHOME%\lib : http://www.2hotfile.com/image.php?di=BYB3
Even i copied commons-logging-1.0.4.jar and com.bea.core.weblogic.commons.logging_1.4.0.0.jar files into the lib folder and then i set CLASSPATH accordingly, result was negative.
I added these lines into startWeblogic.cmd
@REM customized here for log4j
set LOG4J_CONFIG_FILE=%DOMAIN_HOME%\config\log4j.xml
set SAVE_JAVA_OPTIONS=%JAVA_OPTIONS% -Dweblogic.log.Log4jLoggingEnabled=true -Dlog4j.debug -Dlog4j.configuration=%LOG4J_CONFIG_FILE%
set SAVE_CLASSPATH=%CLASSPATH%;%DOMAIN_HOME%\config;
Additionally, i have tried adding log4j.jar into sysyem classpath becuse of classloading problem suspicion: http://www.2hotfile.com/image.php?di=7Y3N after view this link http://www.coderanch.com/t/479763/BEA-Weblogic/Log-Weblogic-ClassNotFoundException
Thanks in advance...
Edited by: webyildirim on 14.Ara.2012 02:45

I resolved the exception; Jdeveloper 11.1.1.4 was setted up on my pc as well. That was the cause of problem. System was looking some paths on 11.1.1.4 server folders that belong to 11.1.14 version.
Now, created server log which i defined in log4j.xml but no log line found in file, nothing logged according to log4j.xml config file and wls still writes its own log into its own log file which is under $domain_home$\servers\DefaultServer\logs\DefaultServer.log. What might be the reason?
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/"
debug="true">

<appender name="FILE" class="org.apache.log4j.DailyRollingFileAppender">
<param name="File" value="./server.log"/>
<param name="Append" value="false"/>

<param name="DatePattern" value="'.'yyyy-MM-dd"/>

<layout class="org.apache.log4j.PatternLayout">

<param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>

</layout>
</appender>
<appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
<param name="Target" value="System.out"/>
<param name="Threshold" value="INFO"/>
<layout class="org.apache.log4j.PatternLayout">

<param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c{1}] %m%n"/>
</layout>
</appender>
<category name="org.apache">
<priority value="DEBUG"/>
</category>
<category name="com.weblogic">
<priority value="DEBUG"/>
</category>
<category name="com.roketsan">
<priority value="DEBUG"/>
</category>
<category name="org.hibernate">
<priority value="DEBUG"/>
</category>
<category name="log4j.category.org.hibernate">
<priority value="DEBUG"/>
</category>
<category name="log4j.category.org.hibernate.SQL">
<priority value="STDOUT"/>
</category>
<root>
<appender-ref ref="CONSOLE"/>
<appender-ref ref="FILE"/>
</root>
</log4j:configuration>
jdeveloper integrated weblogic console output: http://www.2hotfile.com/image.php?di=TPY2
*** Using port 7101 ***
C:\Users\Dijitaluser\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\bin\startWebLogic.cmd
[waiting for the server to complete its initialization...]
this is suuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuun
'LOG4J_CONFIG_FILE' i‡ ya da dis komut, ‡alistirilabilir
program ya da toplu is dosyasi olarak taninmiyor.
JAVA Memory arguments: -Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
WLS Start Mode=Development
CLASSPATH=C:\Oracle\MIDDLE~1.6\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C:\Oracle\MIDDLE~1.6\patch_wls1035\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1.6\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\PROGRA~1\Java\JDK16~1.0_3\lib\tools.jar;C:\Oracle\MIDDLE~1.6\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1.6\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1.6\modules\features\weblogic.server.modules_10.3.5.0.jar;C:\Oracle\MIDDLE~1.6\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1.6\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1.6\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Users\DIJITA~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\wcps-lib\derby-10.6.1.0.jar;C:\Users\DIJITA~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\wcps-lib\derbytools-10.6.1.0.jar;C:\Oracle\Middleware_11.1.1.6\jdeveloper\webcenter\modules\oracle.portlet.server_11.1.1\oracle-portlet-api.jar;C:\Oracle\Middleware_11.1.1.6\jdeveloper\webcenter\modules\wcps_11.1.1.6.0\wcps-connection-mbeans.jar;C:\Oracle\MIDDLE~1.6\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~1.6\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~1.6\WLSERV~1.3\server\lib\xqrl.jar;.
PATH=C:\Oracle\MIDDLE~1.6\patch_wls1035\profiles\default\native;C:\Oracle\MIDDLE~1.6\patch_jdev1111\profiles\default\native;C:\Oracle\MIDDLE~1.6\WLSERV~1.3\server\native\win\32;C:\Oracle\MIDDLE~1.6\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1.6\modules\ORGAPA~1.1\bin;C:\PROGRA~1\Java\JDK16~1.0_3\jre\bin;C:\PROGRA~1\Java\JDK16~1.0_3\bin;C:\Program Files\Java\jre6X64;C:\Program Files\Java\jre6X64\bin;C:\Oracle\database\app\oracle\product\11.2.0\server\bin;C:\Oracle\database\app\oracle\product\11.2.0\server;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Dell\Dell Wireless WLAN Card;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\OpenVPN\bin;C:\Users\Dijitaluser\Desktop\Yeni klas”r\commons-logging-1.0.4.jar;;C:\Oracle\MIDDLE~1.6\WLSERV~1.3\server\native\win\32\oci920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.6.0_30"
Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode)
Starting WLS with line:
C:\PROGRA~1\Java\JDK16~1.0_3\bin\java -client -Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\Oracle\MIDDLE~1.6\WLSERV~1.3\server\lib\weblogic.policy -agentlib:jdwp=transport=dt_socket,server=y,address=52130 -Djavax.net.ssl.trustStore=C:\Oracle\Middleware_11.1.1.6\wlserver_10.3\server\lib\DemoTrust.jks -Dweblogic.nodemanager.ServiceEnabled=true -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1.6\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1.6\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1.6\WLSERV~1.3\server -Djps.app.credential.overwrite.allowed=true -Dcommon.components.home=C:\Oracle\MIDDLE~1.6\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\Users\DIJITA~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1.6\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\Users\DIJITA~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\FMWCON~1\servers\DefaultServer -Doracle.domain.config.dir=C:\Users\DIJITA~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Users\DIJITA~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Users\DIJITA~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Users\DIJITA~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\Users\DIJITA~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\servers\DefaultServer\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1.6\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1.6\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=C:\Users\DIJITA~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\oracle\store\gmds -DUSE_JAAS=false -Djps.policystore.hybrid.mode=false -Djps.combiner.optimize.lazyeval=true -Djps.combiner.optimize=true -Djps.auth=ACC -Doracle.core.ojdl.logging.usercontextprovider=oracle.core.ojdl.logging.impl.UserContextImpl -noverify -Doracle.webcenter.analytics.disable-native-partitioning=false -Doracle.webcenter.tagging.scopeTags=false -XX:+UseParallelGC -XX:+DisableExplicitGC -Dportlet.oracle.home=C:\Oracle\Middleware_11.1.1.6\jdeveloper -Dwc.oracle.home=C:\Oracle\Middleware_11.1.1.6\jdeveloper -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1.6\patch_wls1035\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1.6\patch_jdev1111\profiles\default\sysext_manifest_classpath -Dlog4j.ignoreTCL=true -Dweblogic.log.Log4jLoggingEnabled=true -Dlog4j.debug weblogic.Server
Listening for transport dt_socket at address: 52130
Debugger connected to local process.
<18-Dec-2012 13:58:09 o'clock EET> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<18-Dec-2012 13:58:10 o'clock EET> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<18-Dec-2012 13:58:10 o'clock EET> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
C:\Users\Dijitaluser\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\lib\com.bea.core.weblogic.commons.logging_1.4.0.0.jar;C:\Users\Dijitaluser\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\lib\commons-logging-1.0.4.jar;C:\Users\Dijitaluser\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\lib\log4j-1.2.15.jar;C:\Users\Dijitaluser\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\lib\mbeantypes\csp-id-asserter.jar;C:\Users\Dijitaluser\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\lib\mbeantypes\jps-wls-trustprovider.jar;C:\Users\Dijitaluser\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\lib\wllog4j.jar>
<18-Dec-2012 13:58:10 o'clock EET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.5-b03 from Sun Microsystems Inc.>
<18-Dec-2012 13:58:11 o'clock EET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<18-Dec-2012 13:58:12 o'clock EET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<18-Dec-2012 13:58:12 o'clock EET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<18-Dec-2012 13:58:12 o'clock EET> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\Dijitaluser\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<18-Dec-2012 13:58:12 o'clock EET> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Users\Dijitaluser\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log00016. Log messages will continue to be logged in C:\Users\Dijitaluser\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log.>
<18-12-2012 13:58:12 o'clock EET> <Notice> <Log Management> <WL-170019> <The server log file C:\Users\Dijitaluser\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.>
log4j: Trying to find [log4j.xml] using context classloader java.net.URLClassLoader@7df44ec7.
log4j: Using URL [file:/C:/Users/Dijitaluser/AppData/Roaming/JDeveloper/system11.1.1.6.38.61.92/DefaultDomain/log4j.xml] for automatic log4j configuration.
log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
log4j: System property is :null
log4j: Standard DocumentBuilderFactory search succeded.
log4j: DocumentBuilderFactory is: weblogic.xml.jaxp.RegistryDocumentBuilderFactory
log4j: debug attribute= "true".
log4j: reset attribute= "false".
log4j: Threshold ="null".
log4j: Retreiving an instance of org.apache.log4j.Logger.
log4j: Setting [org.apache] additivity to [true].
log4j: Level value for org.apache is [DEBUG].
log4j: org.apache level set to DEBUG
log4j: Retreiving an instance of org.apache.log4j.Logger.
log4j: Setting [com.weblogic] additivity to [true].
log4j: Level value for com.weblogic is [DEBUG].
log4j: com.weblogic level set to DEBUG
log4j: Retreiving an instance of org.apache.log4j.Logger.
log4j: Setting [com.roketsan] additivity to [true].
log4j: Level value for com.roketsan is [DEBUG].
log4j: com.roketsan level set to DEBUG
log4j: Retreiving an instance of org.apache.log4j.Logger.
log4j: Setting [org.hibernate] additivity to [true].
log4j: Level value for org.hibernate is [DEBUG].
log4j: org.hibernate level set to DEBUG
log4j: Retreiving an instance of org.apache.log4j.Logger.
log4j: Setting [log4j.category.org.hibernate] additivity to [true].
log4j: Level value for log4j.category.org.hibernate is [DEBUG].
log4j: log4j.category.org.hibernate level set to DEBUG
log4j: Retreiving an instance of org.apache.log4j.Logger.
log4j: Setting [log4j.category.org.hibernate.SQL] additivity to [true].
log4j: Level value for log4j.category.org.hibernate.SQL is [STDOUT].
log4j: log4j.category.org.hibernate.SQL level set to DEBUG
log4j: Class name: [org.apache.log4j.ConsoleAppender]
log4j: Setting property [target] to [System.out].
log4j: Setting property [threshold] to [INFO].
log4j: Parsing layout of class: "org.apache.log4j.PatternLayout"
log4j: Setting property [conversionPattern] to [%d{ABSOLUTE} %-5p [%c{1}] %m%n].
log4j: Adding appender named [CONSOLE] to category [root].
log4j: Class name: [org.apache.log4j.DailyRollingFileAppender]
log4j: Setting property [file] to [./server.log].
log4j: Setting property [append] to [false].
log4j: Setting property [datePattern] to ['.'yyyy-MM-dd].
log4j: Parsing layout of class: "org.apache.log4j.PatternLayout"
log4j: Setting property [conversionPattern] to [%d %-5p [%c] %m%n].
log4j: setFile called: ./server.log, false
log4j: setFile ended
log4j: Appender [FILE] to be rolled at midnight.
log4j: Adding appender named [FILE] to category [root].
<18-12-2012 13:58:12 o'clock EET> <Warning> <NodeManager> <WL-300043> <Node manager native library not found - server process id not saved.>
<18-12-2012 13:58:13 o'clock EET> <Error> <Socket> <WL-000438> <Unable to load performance pack. Using Java I/O instead. Please ensure that wlntio.dll is in: 'C:\PROGRA~1\Java\JDK16~1.0_3\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Oracle\MIDDLE~1.6\patch_wls1035\profiles\default\native;C:\Oracle\MIDDLE~1.6\patch_jdev1111\profiles\default\native;C:\Oracle\MIDDLE~1.6\WLSERV~1.3\server\native\win\32;C:\Oracle\MIDDLE~1.6\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1.6\modules\ORGAPA~1.1\bin;C:\PROGRA~1\Java\JDK16~1.0_3\jre\bin;C:\PROGRA~1\Java\JDK16~1.0_3\bin;C:\Program Files\Java\jre6X64;C:\Program Files\Java\jre6X64\bin;C:\Oracle\database\app\oracle\product\11.2.0\server\bin;C:\Oracle\database\app\oracle\product\11.2.0\server;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Dell\Dell Wireless WLAN Card;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\OpenVPN\bin;C:\Users\Dijitaluser\Desktop\Yeni klasör\commons-logging-1.0.4.jar;;C:\Oracle\MIDDLE~1.6\WLSERV~1.3\server\native\win\32\oci920_8;.'
>
<18-12-2012 13:58:19 o'clock EET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<18-12-2012 13:58:20 o'clock EET> <Warning> <Store> <WL-280101> <The persistent file store "_WLS_DefaultServer" is forced to use buffered I/O and so may have significantly degraded performance. Either the OS/hardware environment does not support the chosen write policy or the native wlfileio library is missing. See store open log messages for the requested and final write policies. See the documentation on store synchronous write policy configuration for advice.>
<18-Dec-2012 13:58:20 o'clock EET> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\Dijitaluser\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\logs\access.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<18-Dec-2012 13:58:20 o'clock EET> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Users\Dijitaluser\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\logs\access.log00001. Log messages will continue to be logged in C:\Users\Dijitaluser\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\logs\access.log.>
<18-12-2012 13:58:23 o'clock EET> <Notice> <StdErr> <BEA-000000> <java.util.logging.ErrorManager: 0: oracle.core.ojdl.weblogic.DomainLogHandler ERROR: unable to find instance of weblogic.logging.DomainLogBroadcastHandler>
<18-12-2012 13:58:25 o'clock EET> <Notice> <WebLogicServer> <WL-000365> <Server state changed to STANDBY>
<18-12-2012 13:58:25 o'clock EET> <Notice> <WebLogicServer> <WL-000365> <Server state changed to STARTING>
<18-12-2012 13:58:29 o'clock EET> <Warning> <J2EE> <WL-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Roketsan is not versioned.>
<18-Dec-2012 13:58:37 o'clock EET> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\Dijitaluser\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<18-Dec-2012 13:58:37 o'clock EET> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Users\Dijitaluser\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log00016. Log messages will continue to be logged in C:\Users\Dijitaluser\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log.>
<18-12-2012 13:58:37 o'clock EET> <Notice> <Log Management> <WL-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<18-12-2012 13:58:37 o'clock EET> <Notice> <WebLogicServer> <WL-000365> <Server state changed to ADMIN>
<18-12-2012 13:58:37 o'clock EET> <Notice> <WebLogicServer> <WL-000365> <Server state changed to RESUMING>
<18-12-2012 13:58:38 o'clock EET> <Notice> <Server> <WL-002613> <Channel "Default[11]" is now listening on 0:0:0:0:0:0:0:1:7101 for protocols iiop, t3, ldap, snmp, http.>
<18-12-2012 13:58:38 o'clock EET> <Warning> <Server> <WL-002611> <Hostname "AD190", maps to multiple IP addresses: 169.254.50.94, 192.168.26.212, fe80:0:0:0:a1be:61f:f156:325e%38>
<18-12-2012 13:58:38 o'clock EET> <Notice> <Server> <WL-002613> <Channel "Default[3]" is now listening on fe80:0:0:0:a1be:61f:f156:325e:7101 for protocols iiop, t3, ldap, snmp, http.>
<18-12-2012 13:58:38 o'clock EET> <Notice> <Server> <WL-002613> <Channel "Default[10]" is now listening on 127.0.0.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<18-12-2012 13:58:38 o'clock EET> <Notice> <Server> <WL-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:0:5efe:a9fe:325e:7101 for protocols iiop, t3, ldap, snmp, http.>
<18-12-2012 13:58:38 o'clock EET> <Notice> <Server> <WL-002613> <Channel "Default[7]" is now listening on fe80:0:0:0:a0d0:352d:6b23:d7dc:7101 for protocols iiop, t3, ldap, snmp, http.>
<18-12-2012 13:58:38 o'clock EET> <Notice> <Server> <WL-002613> <Channel "Default[8]" is now listening on fe80:0:0:0:648c:26dc:32a5:1300:7101 for protocols iiop, t3, ldap, snmp, http.>
<18-12-2012 13:58:38 o'clock EET> <Notice> <Server> <WL-002613> <Channel "Default[4]" is now listening on fe80:0:0:0:0:5efe:c0a8:1ad4:7101 for protocols iiop, t3, ldap, snmp, http.>
<18-12-2012 13:58:38 o'clock EET> <Notice> <Server> <WL-002613> <Channel "Default[5]" is now listening on fe80:0:0:0:34a0:7762:7e2f:fca8:7101 for protocols iiop, t3, ldap, snmp, http.>
<18-12-2012 13:58:38 o'clock EET> <Notice> <Server> <WL-002613> <Channel "Default[9]" is now listening on fe80:0:0:0:0:100:7f:fffe:7101 for protocols iiop, t3, ldap, snmp, http.>
<18-12-2012 13:58:38 o'clock EET> <Notice> <Server> <WL-002613> <Channel "Default" is now listening on 192.168.26.212:7101 for protocols iiop, t3, ldap, snmp, http.>
<18-12-2012 13:58:38 o'clock EET> <Notice> <Server> <WL-002613> <Channel "Default[2]" is now listening on 169.254.50.94:7101 for protocols iiop, t3, ldap, snmp, http.>
<18-12-2012 13:58:38 o'clock EET> <Notice> <Server> <WL-002613> <Channel "Default[6]" is now listening on fe80:0:0:0:fdaf:7651:30df:acb6:7101 for protocols iiop, t3, ldap, snmp, http.>
<18-12-2012 13:58:38 o'clock EET> <Notice> <WebLogicServer> <WL-000331> <Started WebLogic Admin Server "DefaultServer" for domain "DefaultDomain" running in Development Mode>
<18-12-2012 13:58:38 o'clock EET> <Notice> <WebLogicServer> <WL-000365> <Server state changed to RUNNING>
<18-12-2012 13:58:38 o'clock EET> <Notice> <WebLogicServer> <WL-000360> <Server started in RUNNING mode>
IntegratedWebLogicServer startup time: 30110 ms.
IntegratedWebLogicServer started.
Edited by: webyildirim on 18.Ara.2012 04:17

Log4J on Weblogic vs Log4J on JBoss

I am working on migrating from JBoss to WebLogic 10. I am able to successfully setup Log4J on WL with a small problem. What I did to configure Log4J was the following.
. Change the Logging implementation from the WL console to use Log4J
. Replace the jboss appenders in the Log4J.xml(org.jboss.appender.DailyRollingFileAppender) to Log4J's DailyRollingFileAppender.
. Added the required Log4J jars to the server classpath
The problem I am having is, WL is logging too much information onto the console and since it is doing that, the same app with similar Log4J's is slower on WebLogic as compared to JBoss.
Is there another setting I need to change to not have WebLogic spit everything out to the console? I compared the thresholds in the JBoss' Log4J vs WL Log4J and everything is the same. Can someone please explain why the difference?
Thanks.

You can add your.properties and log4j.properties to the classpath cant you?
You just need to edit setEnv.cmd (if i remember correctly) in your weblogic server folder to add the folder containing the properties files to the classpath variable.

Getting empty log files with log4j and WebLogic 10.0

Hi!
I get empty log files with log4j 1.2.13 and WebLogic 10.0. If I don't run the application in the application server, then the logging works fine.
The properties file is located in a jar in the LIB folder of the deployed project. If I change the name of the log file name in the properties file, it just creates a new empty file.
What could be wrong?
Thanks!

I assume that when you change the name of the expected log file in the properties file, the new empty file is that name, correct?
That means you're at least getting that properties file loaded by log4j, which is a good sign.
As the file ends up empty, it appears that no logger statements are being executed at a debug level high enough for the current debug level. Can you throw in a logger.error() call at a point you're certain is executed?

Configuring Log4j for weblogic

Hi
can any one tell me how to configure Log4j for weblogic. I have added the log4j jar files to the weblogic classpath but it does not seem to work..
Thanks and Regards
Narayan

You must make a new directory on the same level with applications directory, place "log4j.properties" file in it, include this directory in the "PRE_CLASSPATH" entry in your startup script and that's all.
Sample line in "startWebLogic.cmd" script
'set PRE_CLASSPATH=%_LIBJARS%;classes'
in classes dir you have "log4j.properties"
Should work,
Cristian Negoita

Not sure how to configure Weblogic with log4j.xml

I tried something VERY similar to this. I wasn't sure where to put this code below. I figured in a Servlet environment, it should probably go in a Listener. I found an existing class inside of Spring that does exactly that: org.springframework.web.util.Log4jConfigListener
I put my log4j configuration file into an entry in the classpath and configured web.xml as follows:

        <context-param>
            <param-name>log4jConfigLocation</param-name>
            <param-value>classpath:gov/pa/dep/formu/resources/log4j.properties</param-value>
        </context-param>
        <context-param>
            <param-name>log4jRefreshInterval</param-name>
            <param-value>30000</param-value>
        </context-param>
        
     <listener>
          <listener-class>org.springframework.web.util.Log4jConfigListener</listener-class>
     </listener>The server admin placed the actual log4j.properties file into an AppFileOverrides folder instead of under WEB-INF\classes. I don't know if this caused the problem or not. Since I also was using the DailyRollingFileAppender and running into problems LOSING my log entries each day because he file didn't get renamed, I followed Metalink BUG# 8459807, and used the datedFileAppender available at http://minaret.biz/tips/datedFileAppender.html.
When the application started, the server log showed that log4j was being configured but none of my logging statements were going into the logs. It wasn't until the server admin placed a copy of log4j.properties (a different log4j.properties with a rolling file appender) that the log statements started going into the file that was configured based on web.xml.
Surely, things can't be this difficult with log4j, and commons logging under WebLogic.
All I want is APPLICATION LEVEL LOGS that are specific to the day.
Can someone else elaborate on how they got this working?
thanks a bunch,
Eric

Hi,
The configuration wizard (config.sh) lets you create a WebLogic Domain, however and depending on others "Oracle Middleware" products installed on the same "Oracle Home" (directory where weblogic has been installed) the configuration wizard allows you create the new weblogic domain to support the others middleware products such as WebCenter.
When I say support It means that Configuration Wizard allows you to create the weblogic resources like JDBC connections, JMS services, and deploys all applications that integrates another product such as WebCenter.
I suggest create your domain with support for WebCenter and then from Admin Console create the JDBC resource to connect to other database such as JD Edwards database.
I hope this help.

Log4j issue with two ears in weblogic cluster

Hi,
I am having issue with log4j.I am having 2 ear files say AppA and AppB.I have used log4j(DailyRollingFileAppender) in both so that logs from AppA gets written to a.log and from AppB gets written to b.log.
This approach is working fine in non-clustered environment(weblogic admin server).
But when i try the same in a clustered(weblogic cluster) environment the logs from both AppA and AppB gets written to a.log.
Could you please help me to resolve this issue.

Include ${weblogic.Name} in your log4j property file thiis will create the log file name with server name
log4j.appender.TEST_LOGGER.File=/logs/${weblogic.Name}_TEST_LOGGER_LOG.txt
Do not keep log4j within your ear
move it to server and include it in your class path of your server.

Log4J and WebLogic

What's the best way to integrate the two? WebLogic has its own logging
mechanism that does file writing and what not but I really like log4j
because it's independent, fast, and easy.
Does anybody have a glue class that will allow log4j to write through to the
WebLogic logs?
thanks,
greg

We've chosen to use Log4J simply because of its extensibility as well as
able to centralize all logging results into one place from a bank of WLS
app servers.
"Dejan Predovic" <[email protected]> wrote in message
news:[email protected]..
I found this one on www.theserverside.com quite some time ago. I hopeauthor
will not mind if I attach it here.
"Gregory Gerard" <[email protected]> schrieb im Newsbeitrag
news:[email protected]..
What's the best way to integrate the two? WebLogic has its own logging
mechanism that does file writing and what not but I really like log4j
because it's independent, fast, and easy.
Does anybody have a glue class that will allow log4j to write through tothe
WebLogic logs?
thanks,
greg

Axis2 dumping Debug msgs in Weblogic logs

Hi,
I have axis2 with weblogic 10.3.6 and the weblogic logs are dumping a lot of axis debug messages like below.
213215 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] DEBUG org.apache.axis2.transport.TransportUtils username: oss.eai, client id: 3270976000000, API user: true, database: myhost, Server: myhost.acc.com - Found RequestResponseTransport returning isResponseWritten()
213215 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] DEBUG org.apache.axis2.transport.TransportUtils username: oss.eai, client id: 3270976000000, API user: true, database: myhost, Server: myhost.acc.com - Exiting deleteAttachments()
213221 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] DEBUG org.apache.axis2.transport.TransportUtils username: oss.eai, client id: 3270976000000, API user: true, database: myhost, Server: myhost.acc.com - Exiting deleteAttachments()
Inorder to get rid of these debug messages I tried the below in vain
JVM arguments: -Dlog4j.debug=true -Dweblogic.log.StdoutSeverity="Info" -Dweblogic.log.LoggerSeverity="Warning" -Dweblogic.log.LoggerSeverityProperties="org.apache.axis2=Warning;EJB=Info" -Dlog4j.properties=/oss/tgi/bea/user_projects/domains/mydomain/config/log4j.properties"
log4j.properties has been given the below entries:
log4j.category.org.apache.commons.httpclient=INFO
log4j.category.org.apache.commons=INFO
log4j.category.org.apache.commons.digester=INFO
log4j.category.org.apache.commons.httpclient=INFO
log4j.category.org.apache.axis=INFO
log4j.category.org.apache.struts=ERROR
I also tried suppressing the Axis2 Debug messages in the weblogic logs by configuring filtering like below:
Domain ->LogFilters->here I added log filter as AxisLogFilter Expression is (MESSAGE != 'Exiting deleteAttachments()')
Added this log filter to the weblogic server under logging tab.
Below are more expressions that I tried.
(MESSAGE != '%Exiting deleteAttachments%')
NOT(MESSAGE = 'Exiting deleteAttachments')
NOT(MESSAGE LIKE 'Exiting deleteAttachments')
NOT(MESSAGE = '%Exiting deleteAttachments%')
NOT(MESSAGE LIKE '%Exiting deleteAttachments%')
All these does not seem to help.
Can you please suggest ?

Hi,
I have axis2 with weblogic 10.3.6 and the weblogic logs are dumping a lot of axis debug messages like below.
213215 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] DEBUG org.apache.axis2.transport.TransportUtils username: oss.eai, client id: 3270976000000, API user: true, database: myhost, Server: myhost.acc.com - Found RequestResponseTransport returning isResponseWritten()
213215 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] DEBUG org.apache.axis2.transport.TransportUtils username: oss.eai, client id: 3270976000000, API user: true, database: myhost, Server: myhost.acc.com - Exiting deleteAttachments()
213221 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] DEBUG org.apache.axis2.transport.TransportUtils username: oss.eai, client id: 3270976000000, API user: true, database: myhost, Server: myhost.acc.com - Exiting deleteAttachments()
Inorder to get rid of these debug messages I tried the below in vain
JVM arguments: -Dlog4j.debug=true -Dweblogic.log.StdoutSeverity="Info" -Dweblogic.log.LoggerSeverity="Warning" -Dweblogic.log.LoggerSeverityProperties="org.apache.axis2=Warning;EJB=Info" -Dlog4j.properties=/oss/tgi/bea/user_projects/domains/mydomain/config/log4j.properties"
log4j.properties has been given the below entries:
log4j.category.org.apache.commons.httpclient=INFO
log4j.category.org.apache.commons=INFO
log4j.category.org.apache.commons.digester=INFO
log4j.category.org.apache.commons.httpclient=INFO
log4j.category.org.apache.axis=INFO
log4j.category.org.apache.struts=ERROR
I also tried suppressing the Axis2 Debug messages in the weblogic logs by configuring filtering like below:
Domain ->LogFilters->here I added log filter as AxisLogFilter Expression is (MESSAGE != 'Exiting deleteAttachments()')
Added this log filter to the weblogic server under logging tab.
Below are more expressions that I tried.
(MESSAGE != '%Exiting deleteAttachments%')
NOT(MESSAGE = 'Exiting deleteAttachments')
NOT(MESSAGE LIKE 'Exiting deleteAttachments')
NOT(MESSAGE = '%Exiting deleteAttachments%')
NOT(MESSAGE LIKE '%Exiting deleteAttachments%')
All these does not seem to help.
Can you please suggest ?

Axis and NoClassDefFoundError

We have software that was developed using Axis to connect to a webservice. It
works fine. However, when we add the software to another system that is run under
weblogic 5.1 we get the following error when the axis classes are trying to be
invoked:
java.lang.reflect.InvocationTargetException: java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
Any ideas as to why this would happen?
Thanks,
Tim

Hi Tim,
I don't really follow what you are saying. Are you saying that you are receiving
these exceptions in an instance of WLS 5.1, when you deploy the Apache Axis stuff
in it? If so, here's the JAVACLASSPATH and WEBLOGICCLASSPATH I use:
JAVACLASSPATH=d:\bea\WLS\5.1\lib\weblogic510sp9boot.jar;c:\beasys\licenses\WLS;d
:\bea\WLS\5.1\classes\boot;d:\bea\jdk130\lib\rt.jar
WEBLOGICCLASSPATH=c:\apache\xalan\2.2.0\bin\xerces.jar;c:\apache\xalan\2.2.0\bin
\xalan.jar;d:\bea\WLS\5.1\lib\weblogic510sp9.jar;d:\bea\WLS\5.1\lib\persistence\
WebLogic_RDBMS.jar;d:\bea\WLS\5.1\lib\weblogic-tags-510.jar;d:\bea\WLS\5.1\class
es;d:\bea\WLS\5.1\lib\weblogicaux.jar;.\webservices;.\webapps\axis\WEB-INF\lib\c
ommons-logging.jar;.\webapps\axis\WEB-INF\lib\log4j-1.2.4.jar;.\webapps\axis\WEB
-INF\lib\axis.jar;.\webapps\axis\WEB-INF\lib\jaxrpc.jar;.\webapps\axis\WEB-INF\l
ib\saaj.jar;.\webapps\axis\WEB-INF\lib\tt-bytecode.jar;.\webapps\axis\WEB-INF\li
b\wsdl4j.jar;.\webapps\axis\WEB-INF\lib\xmlsec.jar
I copied the Apache Axis stuff to a directory under my WLS 5.1 install, so I can
modify things without affecting the original files. My startWebLogic.cmd is in:
d:\bea\WLS\5.1\apache
The weblogic.properties file for my server is in:
d:\bea\WLS\5.1\apache\webapps
Here's all I have in there:
######## START OF weblogic.properties #########
weblogic.httpd.webApp.axis=webapps/axis
weblogic.security.ssl.enable=true
weblogic.httpd.logFileName=../logs/axis/access.log
weblogic.httpd.logRotationType=size
weblogic.httpd.maxHttpHeaderSize=4096
weblogic.system.logFile=../logs/axis/weblogic.log
weblogic.jdbc.logFileName=../logs/axis/jdbc.log
weblogic.password.axisadmin=password
######## END OF weblogic.properties #########
The Axis web application is in exploded into:
d:\bea\WLS\5.1\apache\webapps\axis
That directory contains:
WEB-INF
index.htm
happyaxis.jsp
StockQuoteService.jws
I am able to run all the samples, and server-config.wsdd is in the WEB-INF directory.
I think I had to change code in the happyaxis.jsp, to get things to work. I have
attached it.
The d:\bea\WLS\5.1\apache\webapps\axis\WEB-INF\lib directory contains:
axis.jar
commons-logging.jar
jaxrpc.jar
log4j-1.2.4.jar
saaj.jar
tt-bytecode.jar
wsdl4j.jar
xmlsec.jar
Regards,
Mike Wooten
"Tim " <[email protected]> wrote:
>
We have software that was developed using Axis to connect to a webservice.
It
works fine. However, when we add the software to another system that
is run under
weblogic 5.1 we get the following error when the axis classes are trying
to be
invoked:
java.lang.reflect.InvocationTargetException: java.lang.NoClassDefFoundError:
java/lang/reflect/InvocationHandler
Any ideas as to why this would happen?
Thanks,
Tim[happyaxis.jsp]

Configuring Log4j for a EJB Project.

Hi,
I have a weblogic EJB project as a Ear file. The project has no web components (so war file). I want to know which is the ideal way to initialize log4j in this situation.
I can use listener class thro' weblogic-application.xml. But there is no neat way to passing the log4j.xml thro' parameter from weblogic-applicaiton.xml file.
If we are using servlet we could use init-parm to passing xml file. I don't want to hard code the xml file location in the listener class.
What is the best practice to initialize log4j for a EJB project?
Thanks in advance.
Anand

Dan,
I had a similar problem because I wanted to define my own log4j config regardless of what other portal apps were deployed in the BEA domain or what log4j was the default for the domain. This is what I do:
1) Put your log4j config file in the WEB-INF classes dir (or I guess it could be in some other place that the CLASSPATH knows of)
2) Create a servlet that looks like:
import javax.servlet.*;
import javax.servlet.http.*;
import org.apache.log4j.xml.*;
public class Log4jInitServlet extends HttpServlet {
private static final long serialVersionUID = 23456;
public void init(ServletConfig config) throws ServletException {
super.init(config);
DOMConfigurator.configure(Thread.currentThread().getContextClassLoader().getResource("myLog4jConfigFile.xml"));
public void doGet(HttpServletRequest req, HttpServletResponse resp) {
3) Add the servlet definition in the web.xml and add a <load-on-startup>1</load-on-startup>
That should do it.
- Peter

Is application level logging possible in weblogic server 10.3.3

Hi,
I wanted to know whether application logging is possible or not. i.e. customer deploys an application, a log should be created that would contain the name of the application, size of it, timestamp etc.
Thanks
Edited by: user10196088 on Mar 24, 2011 6:17 AM

Hi Yesha,
Yes, you can do application level logging in weblogic server 10.3.3 using log4j . To get the steps how to do it do have a look at the below link.
Topic: Log4j At Application Level in WebLogic
http://middlewaremagic.com/weblogic/?p=633
Regards,
Ravish Mody
http://middlewaremagic.com/weblogic
Come, Join Us and Experience The Magic…

Log4j-1.2.7 axis weblogic 6.1

Similar Messages

Maybe you are looking for