Log4j conflict???

I am trying to move an app from CFusion Standard MX7 to
CFusion Enterprise MX7. I've copied over all the CF pages and java
classes. The app makes use of log4j and we use the same log4j.jar
that CF does. All works fine on CF Standard. While the app works
fine on CF Enterprise (in its own instance), logging doesn't work.
Looking through the CF log I see this:
log4j:ERROR A "org.apache.log4j.DailyRollingFileAppender"
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@53ba3d] whereas
object of type
log4j:ERROR "org.apache.log4j.DailyRollingFileAppender" was
loaded by [coldfusion.bootstrap.BootstrapClassLoader@dc9065].
log4j:ERROR Could not instantiate appender named "A2".
I thought there may be different or multiple versions of
log4j.jar, but the only log4.jar is in the app instances
WEB-INF/cfusion/lib directory.
Any help would be appreciated.

Not necesary the file must be named as log4j.properties , right ?
So I think it is bad architecture decision to have this file at the classpath level ... so what about if you deploy another app with the same requirements ?
Cheers !
Jin

Similar Messages

NoClassDefFoundError / ExceptionInInitializerError

Jdev 9.0.5, WinNT
I'll try to keep it general at first: I have a webapp which runs fine in the standalone installation of oc4j on NT (deployed as a .war/.ear file). However within JDeveloper/embedded oc4j, I get first ExeptionInInitializerError, then on subsequent tries I get NoClassDefFoundError. The class in question is in my WEB-INF/classes directory (it used to be in a .jar but I exctracted it into classes and removed all references to the jar file). There are many many other classes that are found and used successfully in that directory before it blows up trying to find this particular class.
I've seen similar posts all having to do with a log4j conflict. This is not a log4j issue. I'm hoping there is some general information someone can give that might point me in the direction of solving this problem, or diagnosing the exact issue. I'm new to JDev/oc4j, but I would think anything in WEB-INF/classes ought to be found.

do u mean that u r not able to get response from ur webservice when u call it from ur client code???
r u able to see the wsdl file of the webservice that u have deployed in axis??

Error starting Enterprise Manager in WebLogic 10.3.2 - library conflict?

I've just installed WebLogic 11g (10.3.2) and the Application Developer Runtime (11.1.1.2.0). I then used the domain 'Configuration Wizard' to extend my domain (base_domain) and add:
- Oracle JRF - 11.1.1.0 \[oracle_common]
- Oracle Enterprise Manager - 11.1.1.0 \[oracle_common]
Now when I start the server, I get the following error in the log
<Jan 21, 2010 11:48:21 AM GMT> <Warning> <HTTP> <BEA-101162> <User defined listener oracle.sysman.eml.app.ContextInitializer failed: java.lang.NoSuchFieldError: level.
java.lang.NoSuchFieldError: level
        at org.apache.log4j.spi.RootLogger.setLevel(RootLogger.java:65)
        at org.apache.log4j.spi.RootLogger.<init>(RootLogger.java:44)
        at org.apache.log4j.LogManager.<clinit>(LogManager.java:78)
        at org.apache.log4j.Logger.getLogger(Logger.java:117)
        at oracle.sysman.core.intg.RfbIntegration.<clinit>(RfbIntegration.java:44)
        Truncated. see log file for complete stacktrace
<Jan 21, 2010 11:48:21 AM GMT> <Warning> <HTTP> <BEA-101162> <User defined listener oracle.sysman.eml.app.ContextInitializer failed: java.lang.NullPointerException.
java.lang.NullPointerException
        at oracle.sysman.emdrep.repoless.RepolessTargetManager.stop(RepolessTargetManager.java:713)
        at oracle.sysman.eml.app.ContextInitializer.contextDestroyed(ContextInitializer.java:1229)
        at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:482)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
        Truncated. see log file for complete stacktrace
<Jan 21, 2010 11:48:21 AM GMT> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'em'.
weblogic.application.ModuleException:
        at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1399)
        at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
        at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
        at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
        Truncated. see log file for complete stacktrace
Caused By: java.lang.NoSuchFieldError: level
        at org.apache.log4j.spi.RootLogger.setLevel(RootLogger.java:65)
        at org.apache.log4j.spi.RootLogger.<init>(RootLogger.java:44)
        at org.apache.log4j.LogManager.<clinit>(LogManager.java:78)
        at org.apache.log4j.Logger.getLogger(Logger.java:117)
        at oracle.sysman.core.intg.RfbIntegration.<clinit>(RfbIntegration.java:44)
        Truncated. see log file for complete stacktraceIt appears that there's a logging library conflict somewhere. I haven't installed any of my own applications at all, only extended the domain with the two features described above. Can anyone help?

Just completely uninstalled everything and tried again. The problem seems to have disappeared.
I can't be sure, but suspect one of the following fixed it:
- I had JDeveloper 11.1.1.2.0 installed to the same Oracle Middleware home. This could have been where the conflicting library was coming from. Second time around I didn't install JDeveloper.
- When I reinstalled WebLogic, I unchecked 'Oracle Enterprise Pack for Eclipse'
- When I reinstalled WebLogic, I didn't install the Oracle JRockit JDK

Log4J and OAS 10.1.2.0.2

Greetings, all!
I've searched this forum and the OC4J forum and have not found any clues to help with my log4j woes. I'm hoping someone may have encountered similar issues and can share their thoughts.
I am developing a web application and would like to use log4j. I have successfully integrated it in my development environment (JDev 10.1.2.1.0/Standalone OC4J 10.1.2.0.2) by placing the log4j jar (log4j-1.2.14) in WEB-INF/lib. I have not been successful in moving it to our staging OAS environment, however. We are running 10gR2 OAS (10.1.2.0.2) on Windows 2003.
Since I read in the docs (http://download-west.oracle.com/docs/cd/B14099_19/web.1012/b14017/jkosfram.htm#sthref698)that the log4j jar should not be put in the applib directory of the OAS_HOME I have been trying to deploy the application with the jar file within the WEB-INF/lib location. Every time I try to deploy, I get the following error complaining that it cannot find the correct classes.
Base Exception:
com.evermind.server.rmi.OrionRemoteException
Class not found: org.apache.commons.logging.LogConfigurationException; nested exception is:
java.lang.ClassNotFoundException: org.apache.commons.logging.LogConfigurationException. Class not found: org.apache.commons.logging.LogConfigurationException; nested exception is:
java.lang.ClassNotFoundException: org.apache.commons.logging.LogConfigurationException
I understand it is probably a classloader issue, but using an orion-web.xml file with the search-local-classes-first set to true does not work either. I was successful in deploying the app and writing to a log when the log4j jar was in the applib directory, but since the docs state that this could cause conflicts with OEM, I removed the jar. I have also been able to log to the application.log file by using context.log() statements, but this is less than optimal.
I know 10.1.3 may solve this issue, but we are not planning on that version for some time. How are others using log4j in the OAS? Should I just place the jar in the applib and hope for the best?
TIA for any help or insight,
Dixie.

I resolved the problem and wanted to post the solution in case anyone had similar problems. The issue was related to the commons.logging package used by JSF. I had version 1.0.4 in the applib directory of the OAS_HOME along with the other jars needed for JSF. Once I upgraded to the 1.1 version of commons-logging I was able to deploy the app and use log4j. I received this metalink reference from a colleague and it helped me solve the problem: Note:413981.1
Dixie.

Problem weblogic 9.2 with quartz and log4j : url-template-config.xml

Hello,
I configure a Servlet Quartz to run when WebLogic 9.2 starts, but i have an exception, here is my log :
2009-04-15 11:52:52,424 ERROR Logger.error(): Exception while loading URL templates, /WEB-INF/url-template-config.xml
Throwable: javax.servlet.ServletException: error: The document is not a url-template-config: document element namespace mismatch expected "" got "http://www.bea.com/servers/weblogic/url-template-config/8.0"
Stack Trace:
javax.servlet.ServletException: error: The document is not a url-template-config: document element namespace mismatch expected "" got "http://www.bea.com/servers/weblogic/url-template-config/8.0"
     at org.apache.beehive.netui.core.urltemplates.URLTemplatesFactory.getTemplates(URLTemplatesFactory.java:131)
     at org.apache.beehive.netui.core.urltemplates.URLTemplateDescriptor.load(URLTemplateDescriptor.java:133)
     at org.apache.beehive.netui.pageflow.PageFlowContextListener.performInitializations(PageFlowContextListener.java:102)
     at org.apache.beehive.netui.pageflow.PageFlowActionServlet.init(PageFlowActionServlet.java:120)
     at com.bea.console.internal.ConsoleActionServlet.init(ConsoleActionServlet.java:185)
     at javax.servlet.GenericServlet.init(GenericServlet.java:256)
     at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:94)
     at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
     at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:276)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:68)
     at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
     at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:493)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1688)
     at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1665)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1585)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2678)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:874)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:326)
     at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:114)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:25)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:640)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:252)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:176)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:347)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.activate(DeploymentAdapter.java:50)
     at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
     at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:168)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Caused by: org.apache.xmlbeans.XmlException: error: The document is not a url-template-config: document element namespace mismatch expected "" got "http://www.bea.com/servers/weblogic/url-template-config/8.0"
     at org.apache.xmlbeans.impl.store.Locale.verifyDocumentType(Locale.java:449)
     at org.apache.xmlbeans.impl.store.Locale.autoTypeDocument(Locale.java:354)
     at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1270)
     at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1254)
     at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345)
     at org.apache.beehive.netui.core.urltemplates.schema.UrlTemplateConfigDocument$Factory.parse(Unknown Source)
     at org.apache.beehive.netui.core.urltemplates.DefaultURLTemplateFileParser.parse(DefaultURLTemplateFileParser.java:34)
     at org.apache.beehive.netui.core.urltemplates.URLTemplatesFactory.getTemplates(URLTemplatesFactory.java:118)
     ... 43 more
The problem may be a conflict with the different version. My versions are quartz-1.6.0.jar, log4j-1.2.15.jar.
When i rename the file url-template-config.xml i don't have this exception but just a log4j Warning but i don't know if it's not dangerous for my application (run with WebLogic 9.2) if i rename this file.
Can you give me a solution to remove this exception or tell me if rename this file it's not dangerous ?
Thank you,
MH.

url-template-config.xml is part of Apache Beehive. This file is used to provide a template mechanism for URL's. Is your application using Apache Beehive purposefully?
http://beehive.apache.org/docs/1.0.2/netui/apidocs/javadoc/org/apache/beehive/netui/core/urls/URLRewriterService.html
If not, you may have inadvertently added a reference to Apache Beehive when you created the application and now there are references to the Apache Beehive shared libraries in either weblogic-applicaiton.xml or weblogic.xml

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.>

Log4j works in local tomcat, not in the remote one.

hi,
actually i have this in log4j.properties:
log4j.appender.R.File=${catalina.home}/log/logging.logand it works in local tomcat but it doesn't on remote one.
I have to get it to work on a remote server. I doesn't know where catalina.home is set on the remote server and i don't have a shell to check it out.
I can only see the WEB-INF dir under public_html directory.
I tried already:
log4j.appender.R.File=/public_html/logging.logbut no luck. No files created.
Is there a way to point to WEB-INF dir, that is the only dir of tomcat i can see in the remote ftp?
Something like ${WEB-INF} ?
Thanks in advance.

we ran into a similar problem at work yesterday with no logging appearing when adding a log4j config file to an application but logging appearing in the server config when it wasn't there.
Answer: the app server (JBoss in this case) uses log4j itself and the 2 config files were in conflict so nothing was logged at all.
Removing the application specific config cured the problem.
You probably have something similar going on, with the remote server having its own log4j logging already in place and conflicting with yours.
You might have to switch to another logging system or get in contact with the server admins and have them set things up so the server generates your logs where you can access them.

Comms6 IM java.lang.NoClassDefFoundError: org/apache/log4j/Layout

Hi,
After install (and configure) Comms6 Instant Messaging Server I cannot turn on IM services:
bash-3.00# svcadm enable sunim
bash-3.00# svcs -xv
svc:/application/sunim:default (Sun Instant Messaging Server)
State: offline since Thu Sep 18 18:57:15 2008
Reason: Start method is running.
See: http://sun.com/msg/SMF-8000-C4
See: /var/svc/log/application-sunim:default.log
Impact: This service is not running.
(I added some debug lines to the /opt/sun/comms/im/sbin/imadmin)
bash-3.00# tail /var/svc/log/application-sunim:default.log
at com.iplanet.im.server.Watchdog.main(Watchdog.java:224)
[TIMEOUT]
[ Sep 18 18:41:57 Method "start" exited with status 1 ]
[ Sep 18 18:44:57 Leaving maintenance because disable requested. ]
[ Sep 18 18:44:57 Disabled. ]
[ Sep 18 18:57:15 Enabled. ]
[ Sep 18 18:57:15 Executing start method ("/opt/sun/comms/im/sbin/imadmin start") ]
Starting Watchdog /opt/sun/comms/im/sbin/../lib/execdaemon /usr/jdk/entsys-j2se/bin/java -Dlogdir=/var/opt/SUNWiim/default/log -Djava.awt.headless=true -cp /opt/sun/comms/im/sbin/../lib/imcommon.jar:/opt/SUNWmfwk/lib/mfwk_instrum_tk.jar:/opt/SUNWmfwk/lib/mfwk_agent.jar:/opt/SUNWmfwk/lib/rmi2rpc.jar:/opt/SUNWmfwk/lib/xml-apis.jar:/opt/SUNWmfwk/lib/javax77.jar:/opt/SUNWmfwk/lib/jdom.jar:/opt/SUNWmfwk/lib/xercesImpl.jar:/opt/SUNWjdmk/5.1/lib/jmx.jar:/opt/SUNWjdmk/5.1/lib/jmxremote.jar:/opt/SUNWjdmk/5.1/lib/jmxremote_optional.jar:/opt/SUNWjdmk/5.1/lib/jdmkrt.jar:/usr/share/lib/xmpp/improvider.jar:/usr/share/lib/imservice.jar:/opt/sun/comms/im/sbin/../lib/xmppd.jar:/usr/share/lib/jso.jar:/usr/share/lib/xp.jar:/usr/share/lib/log4j.jar:/usr/share/lib/jaxen-core.jar:/usr/share/lib/saxpath.jar com.iplanet.im.server.Watchdog -m noncluster -c /opt/sun/comms/im/sbin/../config/iim.conf
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/log4j/Layout
at com.iplanet.im.server.Watchdog.main(Watchdog.java:224)
Anyway,
When I try to start it manually I get the same error:
bash-3.00# /opt/sun/comms/im/lib/execdaemon /usr/jdk/entsys-j2se/bin/java -Dlogdir=/var/opt/SUNWiim/default/log -Djava.awt.headless=true -cp /opt/sun/comms/im/sbin/../lib/imcommon.jar:/opt/SUNWmfwk/lib/mfwk_instrum_tk.jar:/opt/SUNWmfwk/lib/mfwk_agent.jar:/opt/SUNWmfwk/lib/rmi2rpc.jar:/opt/SUNWmfwk/lib/xml-apis.jar:/opt/SUNWmfwk/lib/javax77.jar:/opt/SUNWmfwk/lib/jdom.jar:/opt/SUNWmfwk/lib/xercesImpl.jar:/opt/SUNWjdmk/5.1/lib/jmx.jar:/opt/SUNWjdmk/5.1/lib/jmxremote.jar:/opt/SUNWjdmk/5.1/lib/jmxremote_optional.jar:/opt/SUNWjdmk/5.1/lib/jdmkrt.jar:/usr/share/lib/xmpp/improvider.jar:/usr/share/lib/imservice.jar:/opt/sun/comms/im/sbin/../lib/xmppd.jar:/usr/share/lib/jso.jar:/usr/share/lib/xp.jar:/usr/share/lib/log4j.jar:/usr/share/lib/jaxen-core.jar:/usr/share/lib/saxpath.jar com.iplanet.im.server.Watchdog -m noncluster -c /opt/sun/comms/im/sbin/../config/iim.conf
bash-3.00# Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/log4j/Layout
at com.iplanet.im.server.Watchdog.main(Watchdog.java:224)
It comes from non global zone on Solaris 10u5.

The package SUNWiimdv was not installed.
bash-3.00# pwd
/install/SunOS_i386/IMAPI/Packages
bash-3.00# pkgadd -d . SUNWiimdv
Processing package instance <SUNWiimdv> from </export/install/comms/SunOS_i386/IMAPI/Packages>
Sun Java System Instant Messaging and Presence APIs(i386) 7.3,REV=2008.01.14
Copyright (c) 2006 Sun Microsystems, Inc. All rights reserved.
PROPRIETARY/CONFIDENTIAL
Use is subject to license terms.
Using </> as the package base directory.
## Processing package information.
## Processing system information.
3 package pathnames are already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
Installing Sun Java System Instant Messaging and Presence APIs as <SUNWiimdv>
## Installing part 1 of 1.
/usr/share/lib/imservice.jar
/usr/share/lib/jaxen-core.jar
/usr/share/lib/jso.jar
/usr/share/lib/log4j.jar
/usr/share/lib/saxpath.jar
/usr/share/lib/xmpp/improvider.jar
/usr/share/lib/xmpp/xmppd
/usr/share/lib/xmpp/xmppd.conf
/usr/share/lib/xp.jar
[ verifying class <none> ]
Installation of <SUNWiimdv> was successful.
bash-3.00# /opt/sun/comms/im/sbin/imadmin stop
Stopping IM services using SMF. Please see the SMF logs for progress messages
bash-3.00# /opt/sun/comms/im/sbin/imadmin start
Starting IM services using SMF. Please see the SMF logs for progress messages
bash-3.00# /opt/sun/comms/im/sbin/imadmin status
Server [UP]
Multiplexor [UP]
Agent:calendar [UP]
Watchdog [UP]

Log4j levels

Hi,
I am in need of one requirements. That is changing log levels dynamically through web application.
I can do that by setting logger.setLevel(Level.DEBUG) or other levels. But If I set as DEBUG i am able to get error/info/fatal errors which we don't want. Is there any way to break the priority levels?

They are our paying customers....I question this. Sorry, obviously you know your project and your customer better than me, but...
If the customer explicitly forbids custom appenders, then it also explicitly mentions using log4j. So it is his responsibility to have choosen log4j, and it his his responsibility if there are conflicting requirements (such as, log only DEBUG but no higher log levels).
If the customer hasn't mandated log4j, I don't see how it can forbid custom appenders ( a log4j notion).
If the customer has mandated log4j, forbidden custom appenders, and required logging at DEBUG level but not higher, then it is you who made a wrong decision (you shouldn't implement the DEBUG-only log using lo4j).
Nothing that a good requirements clarification meeting shouldn't solve.

OTD AdminNode conflicts with Coherence nodes running on same server???

I set up a traditional OTD failover group exposing private proxy to storage nodes. Strangely when I run OTD admin nodes they seem to create conflict with Coherence nodes running on same server. Any clues on what could cause the problem (same default ports?). The msgs I get are the followings:
WARN 2014-08-27 13:09:12,585 [com.tangosol.coherence.component.util.logOutput.Log4j] - 2014-08-27 13:09:12.585/299.393 Oracle Coherence GE 12.1.2.0.2 <Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; IpMonitor failed to verify the reachability of senior Member(Id=2, Timestamp=2014-08-27 12:15:34.775, Address=192.168.10.98:50124, MachineId=41903, xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, Role=jmx-connector); if this persists it is likely the result of a local or remote firewall rule blocking either ICMP pings, or connections to TCP port 7
WARN 2014-08-27 13:09:17,598 [com.tangosol.coherence.component.util.logOutput.Log4j] - 2014-08-27 13:09:17.597/304.405 Oracle Coherence GE 12.1.2.0.2 <Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; IpMonitor failed to verify the reachability of senior Member(Id=2, Timestamp=2014-08-27 12:15:34.775, Address=192.168.10.98:50124, MachineId=41903, xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, Role=jmx-connector); if this persists it is likely the result of a local or remote firewall rule blocking either ICMP pings, or connections to TCP port 7
ERROR 2014-08-27 13:09:21,725 [com.tangosol.coherence.component.util.logOutput.Log4j] - 2014-08-27 13:09:21.724/308.532 Oracle Coherence GE 12.1.2.0.2 <Error> (thread=main, member=n/a): Error while starting cluster: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster

I set up a traditional OTD failover group exposing private proxy to storage nodes. Strangely when I run OTD admin nodes they seem to create conflict with Coherence nodes running on same server. Any clues on what could cause the problem (same default ports?). The msgs I get are the followings:
WARN 2014-08-27 13:09:12,585 [com.tangosol.coherence.component.util.logOutput.Log4j] - 2014-08-27 13:09:12.585/299.393 Oracle Coherence GE 12.1.2.0.2 <Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; IpMonitor failed to verify the reachability of senior Member(Id=2, Timestamp=2014-08-27 12:15:34.775, Address=192.168.10.98:50124, MachineId=41903, xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, Role=jmx-connector); if this persists it is likely the result of a local or remote firewall rule blocking either ICMP pings, or connections to TCP port 7
WARN 2014-08-27 13:09:17,598 [com.tangosol.coherence.component.util.logOutput.Log4j] - 2014-08-27 13:09:17.597/304.405 Oracle Coherence GE 12.1.2.0.2 <Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; IpMonitor failed to verify the reachability of senior Member(Id=2, Timestamp=2014-08-27 12:15:34.775, Address=192.168.10.98:50124, MachineId=41903, xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, Role=jmx-connector); if this persists it is likely the result of a local or remote firewall rule blocking either ICMP pings, or connections to TCP port 7
ERROR 2014-08-27 13:09:21,725 [com.tangosol.coherence.component.util.logOutput.Log4j] - 2014-08-27 13:09:21.724/308.532 Oracle Coherence GE 12.1.2.0.2 <Error> (thread=main, member=n/a): Error while starting cluster: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster

Logging with log4j in a Web app that uses TopLink

The deployment engineer in my company is reporting problems with our first Web app that uses both log4j and TopLink. Apparently TopLink is failing to initialize correctly when log4j-1.2.8.jar is deployed to the WEB-INF/classes directory within the Web app.
I know that 9iAS's Enterprise Manager uses an older version of log4j and I wonder if TopLink uses an older version too.
Are there any known problems when using log4j 1.2.8 with TopLink 9.0.3?
Thanks,
Al Margheim

Unfortunately, when I asked the deployment engineer for more information on the problem, he couldn't provide any, and since he moved the log4j library out of the application's WEB-INF\classes directory he can't reproduce the problem (whatever it was).
Based on a variety of factors (including your response) I suspect that the people who encountered the problem misinterpreted the cause.
If I can get him to put the log4j library back in WEB-INF\classes and get more specific information about the problem, and it still looks like a conflict between TopLink and log4j, I'll post the errors here.
Thanks,
Al Margheim

Getting log4j's SocketNode and SocketAppender to work

For the past week I've been struggeling hard to get remote logging working using the log4j SocketNode and SocketAppender, but failed to succeed. Unfortunately there is not so much information on the log4j.net package to be found on the internet, lets forget about a working example.
This is what I've been doing so far:
SimpleSocketServer
On the server I'm running a SimpleSocketServer instance on port 4445 through the command:
java -classpath D:\RemoteLog4JServer\lib\log4j-1.2.12.jar org.apache.log4j.net.SimpleSocketServer 4445 simplesocketserver.properties
The simplesocketserver.properties file looks like:
log4j.rootLogger=debug,stdout,R
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
# Pattern to output the caller's file name and line number.
log4j.appender.stdout.layout.ConversionPattern=%5p [%t] (%F:%L) - %m%n
log4j.appender.R=org.apache.log4j.RollingFileAppender
log4j.appender.R.File=remote_log.log
log4j.appender.R.MaxFileSize=1024KB
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%p %t %c - %m%nOn the system console I see this server is running fine.
Next step is to start a SocketNode-instance through a Java application.
The main code of this class looks like:
//-- Start a new SocketNode
try {
System.out.println("Accessing socket on host " + m_hostName + " through port " + m_port);
Socket socket = new Socket(m_hostName, new Integer(m_port).intValue());
//-- All right so far, now create the SocketNode
System.out.println("Create the SocketNode listener");
new SocketNode(socket, new Hierarchy(Logger.getRootLogger()));
catch ..... Host and port are passed through application parameters and are 127.0.0.1 and 4445
Again on the server console it confirms the listener is bound to the socket on port 4445 ...
The last part of the puzzle is a test client application which sends remote logging events to the server.
The body of this class looks like:
static Logger logger = Logger.getRootLogger();
public static void main(String argv[]) {
// Try sending logging events through the SocketAppender in the log4j_remote.properties file
System.out.println("Try sending logs through the SocketAppender in the log4j.properties file");
PropertyConfigurator.configure("log4j_remote.properties"); //Logs to a SocketAppender; host 127.0.0.1, port 4445
logger.debug("Hello world");
logger.info("What a beatiful day.");
// And try sending logging events through SocketAppender instance
System.out.println("Try sending logs through a SocketAppender instance");
SocketAppender sa = new SocketAppender("171.21.241.122", 4445);
System.out.println("Created SocketAppender instance");
String logMsg = "Writing log event through SocketAppender instance";
LoggingEvent le = new LoggingEvent("fox.teststuff.TestLog4J",Logger.getRootLogger(),Level.DEBUG,logMsg, new Throwable());
sa.append(le);
sa.close();
}As you can see I tried remote logging on two ways:
1.
Through the log4j_remote.properties file by configuring a SocketAppender. This file looks like:
log4j.rootCategory=DEBUG,stdout,A1
# ConsoleAppender
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
# Pattern to output the caller's file name and line number.
log4j.appender.stdout.layout.ConversionPattern=%5p [%t] (%F:%L) - %m%n
# A1 is set to be a SocketAppender sending its output to the server running on the remote host, port 12345.
log4j.appender.A1=org.apache.log4j.net.SocketAppender
log4j.appender.A1.Port=4445
log4j.appender.A1.RemoteHost=[IP_ADDRESS_SERVER]2.
By using a SocketAppender instance.
But unfortunately neither work. The log remote_log.log gets created as the SimpleSocketServer is started. It contains entries of the successfull starting of the server and the SocketNode.
I also see the logs coming in the client console on running the test applicattion.
There is no firewall between client and server, and I am able to setup a tellnet session from client to server and vice versa through port 4445 (after launching the SimpleSocketServer).
Furthermore I used some IP-sniffing tools to check the IP-traffic from client to server, and this shows me the TCP/IP packet is successfully sent on the client, and successfully received on the server.
But no client-entries appear in the server log :-(
I would be very gratefull if someone has got a clue. And you can be sure I will pass this knowledge on to the community.
Thanks in advance, kind greetings,
Harro de Vos

UPDATE:
Meanwhile I discovered 2 problems, with many thanks to my collegue Pattrick.
1.
The SimpleSocketServer is a server/listener which makes use of the SocketNode-class. Therefore it was needless and wrong for me to launch a SocketNode-instance in my StartSocketNode-class. This probably only caused conflicts.
2.
In my testclass I tried to create remote logging events on 2 ways, though the SocketAppender in the log4j.properties file and through the use of a programmed instance of the SocketAppender-class.
It could very well be running these two methods in the same thread also causes conflicts, so I tried them seperately.
I didn't get the first one to work (through the properties file), but the second solution (SocketAppender instance) did the trick for me!!
Only remaining issue is this solution causes an EOFException.
Anybody any ideas about this?

DSP App deployment and log4j problem

Hi:
We've found that bea/weblogic81/common/lib/log4j.jar has to be in the weblogic starting script in order to deploy DSP application successfully. However, this log4j provided by weblogic conflicts with another version of log4j used by other applications running on the same weblogic instance.
Is there any workaround to avoid the need of putting log4j in the starting script for DSP app deployment?
thanks!!
John

Thanks for helping! Here is the stack trace when log4j is not in the weblogic server starting script, and the deployment failed:
<Jan 16, 2007 2:43:11 PM PST> <Info> <Deployer> <BEA-149060> <Module ProductInfo
App_ejb.jar of application ProductInfoApp successfully transitioned from prepare
d to active on server gws2devapp1.>
<Jan 16, 2007 2:43:11 PM PST> <Info> <Deployer> <BEA-149059> <Module ProductInfo
WS of application ProductInfoApp is transitioning from prepared to active on ser
ver gws2devapp1.>
<Jan 16, 2007 2:43:11 PM PST> <Error> <Deployer> <BEA-149231> <Unable to set the
activation state to true for the application ProductInfoApp.
java.lang.NoClassDefFoundError: org/apache/log4j/AppenderSkeleton
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12
3)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at com.bea.wlw.runtime.core.util.InternalLogger.<clinit>(InternalLogger.
java:23)
at com.bea.wlw.runtime.core.servlet.WebappContextListener.<clinit>(Webap
pContextListener.java:38)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at weblogic.servlet.internal.WebAppServletContext.registerEventListener(
WebAppServletContext.java:2992)
at weblogic.servlet.internal.WebAppServletContext.activateFromDescriptor
s(WebAppServletContext.java:2532)
at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServlet
Context.java:6217)
at weblogic.servlet.internal.WebAppServletContext.setActive(WebAppServle
tContext.java:6195)
at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:864
at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplication
Container.java:3385)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
ner.java:2248)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
ner.java:2221)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
ner.java:2169)
at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivat
ion(SlaveDeployer.java:3111)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForA
llApplications(SlaveDeployer.java:1769)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:352)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
--------------- nested within: ------------------
weblogic.management.ManagementException: [Deployer:149233]An unexpected error wa
s encountered during the deployment process. - with nested exception:
[java.lang.NoClassDefFoundError: org/apache/log4j/AppenderSkeleton]
at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(Slave
Deployer.java:1035)
at weblogic.management.deploy.slave.SlaveDeployer.access$500(SlaveDeploy
er.java:117)
at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivat
ion(SlaveDeployer.java:3114)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForA
llApplications(SlaveDeployer.java:1769)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:352)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
>

Crystal Report 2008 SP3 and BO XI 3.1 conflict

Hi every body,
We have a BOE system:
BO XI 3.1
Oracle db 10g
All running successful and can create some types of WebI report.
But we also want reports with Crystal Report.
1> So we install Crystal Report 2008 SP3 (without knowing the conflict error between BO XI 3.1 and Crystal Report 2008 SP3 and overwrite some .dll file). After installing, we can not create WebI report any more. And a error message box display: "DBDriver failed to load: C:\Program File\Business Objects\BusinessObjects ENterprise12.0\win32_x86\dataAccess\connectionServer\dbd_oci.dll ".
2> We uninstall Crystal Report SP3. But this is not the solution. Still error because of missing .dll files.
3> We open BO XI 3.1 setup and repair BO XI 3.1. Even we uninstall BO XI 3.1, delete all of its components and delete in regedit key. We install BO XI 3.1 again. Now we have full .dll file, not missing them any more. But when we open universe and click on Table browser, cannot fetching any tables.
We set rights for Oracle DB user again. But still error: cannot fetching.
4> We searched the solution for this problem on the internet. But not worked, no answer.
Can somebody help me bring back the BOE system state again ? pls :"<
T______T

Hi Paul,
I hope I read your question right!
Yes, It is possible to run XIR2 and 3.1 on the same server although it's not recommended by BO. You will need to make sure they are both pointing to different CMS databases and different FRS repositories, like you already mentioned you will need to specify different ports for the CMS db and Tomcat.
Why not uninstall Business Objects XI R2 in your BO development environment or a spare server (if you have one), and do a clean install of XI 3.1 SP3.
Tip: If you were already having performance issues with your XI R2 environment, I would seriously consider upgrading the hardware. XI 3.1 needs a bit more RAM and CPU than XI R2
Regards
Rim Geurts

OIM 9.1.0.2 - User group permission conflict issue

Hi Gurus,
IHAC who have faced a strange behavior about permission conflict.
User has been assigned to a user group (ANALISTA DRSI) who have permission to disable resource of the users he administrates. The user group has been assigned to resource's administrator.
The same use has been assigned to other user group (ANALISTA ADM DRSI) who have other permission. The user group has been not assigned to resource's administrator.
If the user has been only assigned to ANALISTA DRSI user group the user is able to see records on Rogue Account report. If the customer has been assigned to both ANALISTA DRSI and ANALISTA ADM the user is not able to see the record on Rogue Account report. He got a display error message (You do not have permission). Both user groups have the Report menu item assigned.
My question: if the customer is assigned to a user group who have permission to see the reports, should not the user is able to see the report even though he is also into the other group who do not have permission?
Is there conflit in the OIM???
Any tip will be very appreciated.

Orgnaization > Manage > Select Org in which users are getting created > Administrative Group (Drop Down) > Select Group for which users are not coming.

Log4j conflict???

Similar Messages

Maybe you are looking for