0 Replies Latest reply on May 6, 2011 2:27 PM by Phanikanth

    Error while processing library references. Unresolved application library r

    Phanikanth
      Hi Experts,

      When i try to deploy .ear file in weblogic 11g server (linux 64-bit redhat OEL 5.46), I am facing following error.
      Please help me out to resolve it.


      Eror Message

      <May 6, 2011 7:32:40 PM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1304690560384' for task '8'. Error is: 'weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: org.apache.commons.httpclient, exact-match: false].'
      weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: org.apache.commons.httpclient, exact-match: false].
      at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
      at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
      at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
      at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
      Truncated. see log file for complete stacktrace
      >
      <May 6, 2011 7:44:58 PM IST> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by weblogic>
      <May 6, 2011 7:44:58 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
      [JCABindingManager] : This operation is not supported for JCA based MDB
      <May 6, 2011 7:45:00 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
      <May 6, 2011 7:45:00 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
      <May 6, 2011 7:45:00 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[3]" listening on fe80:0:0:0:be30:5bff:fed3:5db0:8001 was shutdown.>
      <May 6, 2011 7:45:00 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[1]" listening on 10.108.26.246:8001 was shutdown.>
      <May 6, 2011 7:45:00 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[7]" listening on 0:0:0:0:0:0:0:1:8001 was shutdown.>
      <May 6, 2011 7:45:00 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[6]" listening on 127.0.0.1:8001 was shutdown.>
      <May 6, 2011 7:45:00 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[2]" listening on fe80:0:0:0:200:ff:fe00:0:8001 was shutdown.>
      <May 6, 2011 7:45:00 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 192.168.122.1:8001 was shutdown.>
      <May 6, 2011 7:45:00 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[4]" listening on fe80:0:0:0:fcff:ffff:feff:ffff:8001 was shutdown.>
      <May 6, 2011 7:45:01 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
      Caller should ensure that a DefaultContext is proper for this use.
      Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
      This message may be avoided by performing initADFContext before using getCurrent().
      To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
      <May 6, 2011 7:45:01 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
      Caller should ensure that a DefaultContext is proper for this use.
      Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
      This message may be avoided by performing initADFContext before using getCurrent().
      To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
      <May 6, 2011 7:45:01 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
      Caller should ensure that a DefaultContext is proper for this use.
      Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
      This message may be avoided by performing initADFContext before using getCurrent().
      To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
      <May 6, 2011 7:45:01 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
      Caller should ensure that a DefaultContext is proper for this use.
      Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
      This message may be avoided by performing initADFContext before using getCurrent().
      To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
      <May 6, 2011 7:45:01 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
      Caller should ensure that a DefaultContext is proper for this use.
      Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
      This message may be avoided by performing initADFContext before using getCurrent().
      To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
      <May 6, 2011 7:45:05 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
      Caller should ensure that a DefaultContext is proper for this use.
      Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
      This message may be avoided by performing initADFContext before using getCurrent().
      To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
      [TopLink Info]: 2011.05.06 19:45:06.235--ServerSession(255740887)--deferred_session logout successful
      [TopLink Info]: 2011.05.06 19:45:06.236--ServerSession(256131953)--tracking_session logout successful
      <May 6, 2011 7:45:06 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
      Caller should ensure that a DefaultContext is proper for this use.
      Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
      This message may be avoided by performing initADFContext before using getCurrent().
      To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
      <May 6, 2011 7:45:06 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
      Caller should ensure that a DefaultContext is proper for this use.
      Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
      This message may be avoided by performing initADFContext before using getCurrent().
      To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
      <May 6, 2011 7:45:06 PM IST> <Warning> <oracle.adf.share.ADFContext> <BEA-000000> <Automatically initializing a DefaultContext for getCurrent.
      Caller should ensure that a DefaultContext is proper for this use.
      Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
      This message may be avoided by performing initADFContext before using getCurrent().
      To see the stack trace for thread that is initializing this, set the logging level of oracle.adf.share.ADFContext to FINEST>
      <May 6, 2011 7:45:09 PM> <FINEST> <NodeManager> <Waiting for the process to die: 20074>
      <May 6, 2011 7:45:09 PM> <INFO> <NodeManager> <Server was shut down normally>
      <May 6, 2011 7:45:09 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>

      Thanks
      Phani