Weblogic.application.ModuleException: Context path is already is use

Hi,
I am using ALSB 3.0 and I am trying to deploy a ALSB configuration jar. I am seeing the following exception during deployment.
+weblogic.application.ModuleException: Context path '/alsb/internal/transports/ejb/UserAccounts_1_0_businessservices_C-6414' is already in use by the module: /alsb/internal/transports/ejb/UserAccounts_1_0_businessservices_C-6414 application: EJBALSB_1290003713346+
If i restart the Weblogic server and redeploy it works. I will not have the convenience of restart on the production systems. I need to nail this issue on my test system and I am looking for help.
My configuration details are
SunOS camden 5.10 Generic_120011-14 sun4v sparc SUNW,SPARC-Enterprise-T2000
WebLogic Server 10.0 MP1
AquaLogic Service Bus 3.0.0.0
java version "1.5.0_21"
My set up is as below
One Admin server and two Managed server which are in a cluster. All deployments are done using the Admin server.
The ALSB configuration Jar uses the ALSB business service to lookup to a JNDI provider.
I am a newbie and I am not sure if I have provided all the details for someone to help me out. Please let me know if you need more information.
Thank you.
Support.

Looking at the information provided I assume that you are modifying some BS related to EJB and activating the session with new changes.
Instead of restarting servers you can also see if this workaround is working.
1) disable the BS and commit the session
2) modify changes to BS and enable BS and commit session.
Let me know if the above work-around is working.Ideally we should not see the behavior what you are observing. Track it through support to get a fix. While activating the changes, OSB deletes the old resource and creates a new resource. During this stage something is going wrong inside OSB (clash of JNDI names for old and new resources OSB deploys).
I also vaguely remember that some issues with JNDI that got resolved in later releases.Please check with support to confirm if there is an existing patch already.
My two cents
Manoj
Edited by: Manoj Neelapu on Nov 29, 2010 9:02 AM

Similar Messages

  • Weblogic.application.ModuleException: Context path '/app-Model' is already

    Everything was working in Jdev 11g, but suddenly I started getting this error:
    weblogic.application.ModuleException: Context path '/app-Model' is already in use by the module: app-Model application: APP
    ...when using the weblogic integrated server. Any ideas?

    am also seeing this error:
    Weblogic Server Exception: weblogic.application.ModuleException:
    [10:12:20 AM] Caused by: java.lang.ClassNotFoundException: oracle.bc4j.mbean.BC4JConfigLifeCycleCallBack

  • Weblogic.application.ModuleException

    Hi,
    I am trying to deploy an Web application with EJB's. But it is giving me the below error. Please if anyone can help me out.
    Message:
    weblogic.application.ModuleException: Context path '/HelloWorldWeb' is already in use by the module: HelloWorldWeb application: HelloWorldWebEAR
    Exception stack trace :
    java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.
         at com.bea.workshop.wls.core.server.internal.WlsJ2EEDeploymentHelper$DeploymentProgressListener.watch(WlsJ2EEDeploymentHelper.java:1557)
         at com.bea.workshop.wls.core.server.internal.WlsJ2EEDeploymentHelper.deploy(WlsJ2EEDeploymentHelper.java:469)
         at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1328)
         at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:786)
         at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:606)
         at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:502)
         at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:887)
         at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874)
         at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:72)
         at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: weblogic.application.ModuleException: Context path '/HelloWorldWeb' is already in use by the module: HelloWorldWeb application: HelloWorldWebEAR
         at weblogic.servlet.internal.WebAppModule.initAndValidateContextPath(WebAppModule.java:1076)
         at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:908)
         at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
         at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:423)
         at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:182)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:48)
         at weblogic.application.internal.flow.ScopedModuleDriver.activate(ScopedModuleDriver.java:194)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:66)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    Remove the project from WLS, right click server, select publish, then add the project back and publish, see if that helps.
    Or dDouble click the WLS server in Servers View, look at the tree view listing deployed modules, select HelloWorldWebEAR in the tree
    and undeploy.

  • 'weblogic.application.ModuleException:'while deploying the EAR file to WLS

    Hi
    i am trying to deploy the ADf11g app on to external WLS 10.3 server.
    My WLS is having the shared libraries .so i didn't include the liibraries in WAR.
    while deploying i am facing errors.
    My domain log:
    Nov 12, 2008 2:40:30 PM EST     J2EE     Warning     BEA-160195     The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Dep2EARapplication1 is not versioned.
         Nov 12, 2008 2:40:30 PM EST     HTTP     Error     BEA-101371     There was a failure when processing annotations for application F:\oracleWls\user_projects\domains\sailu1base_domain\servers\AdminServer\tmp\_WL_user\Dep2EARapplication1\6e738n\Dep2webapp1.war. Please make sure that the annotations are valid. The error is org.apache.myfaces.trinidad.webapp.ResourceServlet
         Nov 12, 2008 2:40:30 PM EST     Deployer     Error     BEA-149265     Failure occurred in the execution of deployment request with ID '1226518830484' for task '4'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'usrDep2Application1-ViewController-context-root'' weblogic.application.ModuleException: Failed to load webapp: 'usrDep2Application1-ViewController-context-root' at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: org.apache.myfaces.trinidad.webapp.ResourceServlet at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:54) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176) at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:35) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:227) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:211) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:107) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1287) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
         Nov 12, 2008 2:40:30 PM EST     Deployer     Warning     BEA-149004     Failures were detected while initiating deploy task for application 'Dep2EARapplication1'.
         Nov 12, 2008 2:40:30 PM EST     Deployer     Warning     BEA-149078     Stack trace for message 149004 weblogic.application.ModuleException: Failed to load webapp: 'usrDep2Application1-ViewController-context-root' at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: org.apache.myfaces.trinidad.webapp.ResourceServlet at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:54) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176) at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:35) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:227) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:211) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:107) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1287) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
         Nov 12, 2008 2:40:30 PM EST     Console     Error     BEA-240003     init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
         Nov 12, 2008 2:41:04 PM EST     netuix     Warning     BEA-423420     Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=DiagnosticsViewDomainLogTablePage&DiagnosticsViewDomainLogTablePortlethandle=com.bea.console.handles.LogDispatchHandle%28%22AdminServer%3BDomainLog%22%29.
    Can anyone plz tell me why i am getting errors.
    what is the 'weblogic.application.ModuleException:' error.
    and the HTTP error.

    Hi,
    My EAR file size is about 25 MB.this size is becoz of libraries.so i decided to make a jar file of all libraries.and i installed that jar as library on wls10.3. so that my ear apps later refer this jar.by this no need to include the libraries in every EAR and also size of ear is reduced.
    In my weblogic-application.xml file i refer this jar using the <library-ref> tag.when i am trying to install ear file i am facing this weblogic.application.ModuleException: error as posted above .
    Can you tell me where i went wrong.
    Is the way i am doing is right or not.

  • Startup error, weblogic.application.ModuleException

    startup error, weblogic.application.ModuleException
    I got a error when I startup my server. Here is the trace."workspace " is my application.
    <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating distribute task for application 'workspace'.>
    <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException:
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:295)
    at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    Truncated. see log file for complete stacktrace
    java.lang.ClassCastException: com.ctc.wstx.stax.WstxInputFactory
    at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136)
    at weblogic.servlet.internal.WebAppHelper.addListenerElements(WebAppHelper.java:244)
    at weblogic.servlet.internal.WebAppHelper$IOHelperImpl.parseXML(WebAppHelper.java:224)
    at weblogic.descriptor.DescriptorCache.parseXML(DescriptorCache.java:324)
    at weblogic.servlet.internal.WebAppHelper.registerTagLibListeners(WebAppHelper.java:174)
    Truncated. see log file for complete stacktrace
    Here is the weblogic.xml in my application.
    <?xml version="1.0" encoding="UTF-8"?>
    <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
    <context-root>/workspace</context-root>
    <container-descriptor>
    <prefer-web-inf-classes>true</prefer-web-inf-classes>
    </container-descriptor>
    </weblogic-web-app>
    I have two ways to deploy my application,using installer or deploying it manually.
    Using installer is ok,but I deployed it by myself,the problem came up.That's odd
    I need the weblogic.xml to resovle another problem.

    some one can help,thanks.

  • Weblogic.application.ModuleException: Failed to load webapp: 'oim'

    Hi All,
    1----> i am getting the following error while starting the OIM11g.
    <Apr 20, 2012 10:31:57 AM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'oim [Version=11.1.1.3.0]' due to error weblogic.application.ModuleException: Failed to load webapp: 'oim'.
    weblogic.application.ModuleException: Failed to load webapp: 'oim'
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:393)
    at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: oracle.iam.consoles.faces.navigation.common.ShortcutNavigationServlet
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
    at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
    Truncated. see log file for complete stacktrace
    >
    2-----> OIM is in to Running Mode but when we tried to access it we are getting the following error.
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
    If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
    Thank you

    Hi even I am getting the same error now. I had done some branding changes in iam-consoles-faces war file and then replaced the original one and restarted the server. But then the server started throwing this error and OIM application is not deployed at all so unable to access the oim console. Did you find a solution for this?? Can anyone please help me. Its rather urgent. Also before these errors stated above are thrown I get the following two lines on the server logs :
    <Jul 25, 2012 9:22:29 AM IST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element ejb-jar in the deployment descriptor in C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\iam-async-mdb.jar/META-INF/ejb-jar.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Jul 24, 2012 7:26:38 PM IST> <Error> <HTTP> <BEA-101371> <There was a failure when processing annotations for application C:\Oracle\Middleware\Oracle_IDM1\serv
    er\apps\oim.ear\iam-consoles-faces.war. Please make sure that the annotations are valid. The error is oracle.iam.consoles.faces.navigation.common.ShortcutNavigationServlet>
    Thanks,
    $id

  • FAIL - Application at context path /webapp could not be started

    Hi,
    I have the code under c:\my_name_ccview\source\code\MyWebApplication.
    I use Netbeans 5.5.1 and bundled tomcat 5.5.17. I can compile and build the MyWebApplication.war file.
    In the context file I defined <Context path="/webapp">
    </Context>
    When I try to deploy it to the bundled tomcat I get the error FAIL - Application at context path /webapp could not be started.
    I also tried building the application and then try Run Debug without deploying application. Still the same problem. My application wont start. When I check the runtime tab on netbeans and check applications under bundled tomcat I see /webapp -[stop]
    Please any help is much appreciated

    What you should do is test ur application by deploying it in the examples folder of tomcat and them try to run it and it will work. But this is only the temporary solution.

  • FAIL - Application at context path /TemperatureConversion could not be star

    FAIL - Application at context path /TemperatureConversion could not be started
    I get the above error when trying to deploy my web service (which is a very simple web service - very much on the lines of the HelloWorld web service).
    Please help me fix this issue! What am I missing?

    As I had posted elsewhere, post the stacktrace.
    There can be many reasons why your web app did not start.

  • Weblogic.application.ModuleException: java.lang.NoClassDefFoundError -

    Hi
    I receive a problem when deploying a resource adapter - but it is not very informative on where to look for the problem
    weblogic.application.ModuleException: java.lang.NoClassDefFoundError
    at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:217)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    Caused by: java.lang.NoClassDefFoundError
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:242)
    at weblogic.connector.outbound.RAOutboundManager.initializeMCF(RAOutboundManager.java:485)
    at weblogic.connector.outbound.RAOutboundManager.createConnectionFactory(RAOutboundManager.java:440)
    at weblogic.connector.outbound.RAOutboundManager.initialize(RAOutboundManager.java:385)
    at weblogic.connector.outbound.RAOutboundManager.<init>(RAOutboundManager.java:116)
    at weblogic.connector.common.RAInstanceManager.initialize(RAInstanceManager.java:1181)
    at weblogic.connector.common.RAInstanceManager.<init>(RAInstanceManager.java:343)
    at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:178)
    usually ClassDefNotFoundError would mention which class it has a problem with - but in this case nothing .

    when problem is
    [12:21:26 PM] Weblogic Server Exception: weblogic.application.ModuleException:
    [12:21:26 PM] Caused by: java.lang.NullPointerException:
    [12:21:26 PM] See server logs or server console for more details.
    For deploy Fussion Web aplication
    The problem is weblogic 10.3.5.0 you need install Realtime Software the package name is ofm_appdev_generic_11.1.1.5.0_disk1_1of1.zip and install jdeveloper the package name is jdevstudio11121install.bin when installation is finished, you need extend domain to Oracle JRF 11.1.10 is redy only you need restart weblogic server. The problen to deploy Fussion Web Aplication is resolved

  • [help]FAIL - Application at context path

    im going crazy here.
    I see other people have had this same problem....
    I'm doing some tutorials in a book called core javaserver pages.
    I've followed each step to what appears to be a "t" and i still cannot get my application to start. I've placed my .war file in my webapps directory. The .war file expands and all the content appears to be there. When i go into the tomcat manager to start the app manually;I get the error FAIL - Application at context path /login could not be started.
    I had it working before- by fluke. But now it's gone and i can't get it back.
    I'm having a tough time even finding where to look. Can someone offer any suggestions?

    here is one of the errors i get in my tomcat/log directory
    Caused by: java.lang.ClassCastException: components.renderkit.AreaRenderer
         at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:876)

  • Fail to deploy ws application at context path /Books using tomcat  6.0

    Hi,
    I was not able to deploying in Tomcat 6.0 a web service application.
    Thanks for hlep.

    Can you provide some more details?

  • FAIL - Application at context path /hostel-jaxrpc could not be started

    hi,
    when i deploy my application, i build it in a dos window but when i view it in tomcat manager i get the above error sayin that it failed to start....any ideas!!! is it a classpath issue!!
    thanks in advance jimbo

    I have a similar problem; I have a JSF application that was working fine under Tomcat 4.1, however it fails to deploy under Tomcat 5. With Tomcat 4.1 deployment simply meant putting the WAR in the webapps directory and starting the server. Is this the same for Tomcat 5? Are there any other settups required that I'm missing.
    Thanks for the help,
    Ben.

  • Multiple EARs packaging the same resource adapter -- Weblogic Application S

    Hello,
    I had a question regarding JNDI and deploying multiple applications (EAR's) which package the same resource adapter running on Webloigc Application Server 9.1. I have an EAR file, ear1, which contains a resource adapter with connection factory with JNDI name say 'xyz' specified in the weblogic-ra.xml file. I have another EAR file, ear2, which again packages the same resource adapter with the same connection factory with JNDI name 'xyz'. Upon activating the 2nd EAR file, I get an exception 'javax.naming.NoPermissionException: A Resource Adapter may only be accessed from within the same application from which it was deployed.', as seen below:
    <May 8, 2006 10:29:27 AM PDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating distribute task for application 'JMS2JMS_eInsightweblogic2'.>
    <May 8, 2006 10:29:27 AM PDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: java.lang.AssertionError: Internal Error occurred, Assertion Failed: No Initial Context for Jndi: javax.naming.NoPermissionException: A Resource Adapter may only be accessed from within the same application from which it was deployed.
    at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:217)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
    Truncated. see log file for complete stacktrace
    javax.naming.NoPermissionException: A Resource Adapter may only be accessed from within the same application from which it was deployed.
    at weblogic.connector.outbound.RAOutboundManager.getConnectionFactory(RAOutboundManager.java:721)
    at weblogic.connector.deploy.JNDIHandler.getConnectionFactory(JNDIHandler.java:1017)
    at weblogic.connector.deploy.JNDIHandler.lookupObject(JNDIHandler.java:871)
    at weblogic.connector.deploy.JNDIHandler.getObjectInstance(JNDIHandler.java:845)
    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
    Truncated. see log file for complete stacktrace
    It seems like the 2nd EAR is trying to go across and lookup the connection factory from the 1st EAR. Does weblogic bind the RA's connection factory jndi name in the global jndi and is not specific to each EAR? Is there some flag or switch I can turn on to make the JNDI specific to each EAR?
    My weblogic deployment descriptor for the ra looks like the following:
    <weblogic-connector xmlns="http://www.bea.com/ns/weblogic/90"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.bea.com/ns/weblogic/90
    http://www.bea.com/ns/weblogic/90/weblogic-ra.xsd">
    <jndi-name>JMS2JMS_eInsightDeployment4_stcbpelra</jndi-name>
    <enable-access-outside-app>false</enable-access-outside-app>
    <enable-global-access-to-classes>false</enable-global-access-to-classes>
    <outbound-resource-adapter>
    <connection-definition-group>
    <connection-factory-interface>javax.resource.cci.ConnectionFactory</connection-factory-interface>
    <connection-instance>
              <b><jndi-name>BPELConnectionFactory</jndi-name></b>
              <connection-properties>
              <pool-params>
              <initial-capacity>0</initial-capacity>
              <max-capacity>10000</max-capacity>
              <capacity-increment>1</capacity-increment>
              <shrinking-enabled>true</shrinking-enabled>
              <shrink-frequency-seconds>60</shrink-frequency-seconds>
              <match-connections-supported>false</match-connections-supported>
              </pool-params>
              <properties>
                   <property>
                        <name>BPELConnectionFactory</name>
                        <value>BPELConnectionFactory</value>
                   </property>
              </properties>
              </connection-properties>
         </connection-instance>
    </connection-definition-group>
    </outbound-resource-adapter>
    </weblogic-connector>

    Thanks for the reply... in my case this would be done by the active synch process so no GUI form is required. I will be getting a list of application ID for the user by LDAP AS. One i get it i will have to parse it and get the list of application user id. I am passing those ID;s to a workflow where I am forming the resource name as you mentioned
    for example:
    If i get user1#user2#user3 from AS i am separating them based on # using split and getting 3 different user id;s
    now i am forming a string with the resource name and passing it to the sub process in which i am checking out the user object, setting the user attributes and checking in the new view.
    user1#LDAP
    user2#LDAP|1
    user3#LDAP|2
    Problem ; When i run this user1 is getting created in LDAP but user2 and user3 are not. There entry is getting created in IDM.
    When I open the IDM object I get a yellow triangle (warning) and if I open the user object and hit save button IDM creates the user account on the LDAP.
    any help for further solving this problem would be appreciated.
    Regards,

  • Trobule in saving log in file which is in my context path

    Hello all, i am facing problem while saving log into Log file from servlet. I am using Log4j library and eclipse as IDE. When i push any log information to log file, it make log file default to eclipse path not in my servlet context path. I am using log4j.properties file for configuration. Which has following contents :
    log4j.rootLogger=DEBUG, FA
    log4j.appender.FA=org.apache.log4j.FileAppender
    log4j.appender.FA.File=log.txt
    log4j.appender.FA.layout=org.apache.log4j.PatternLayout
    log4j.appender.FA.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n
    and servlet code for configuring properties file is : PropertyConfigurator.configure(context.getResource("/log4j.properties"));
    what when i push content to log.txt it create file in my eclipse path. How can i set the file path as my context path for log.txt?
    thanks in advance.
    sanjeev

    I don't know such way. But maybe You can read the file when application starts (in ServletContextListener) and change this property when it's already running. Don't know if this helps, but may try.

  • Weblogic application module exception(need very urgent)

    hi when i try to deploy application im getting the following error,application status shows as failed
    <BEA-149265> <Failure occurred in the execution of deployment request with ID '1295628973050' for task '8
    4'. Error is: 'weblogic.application.ModuleException: '
    weblogic.application.ModuleException:
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:18
    1)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    java.lang.NullPointerException

    You have a java.lang.NullPointerException when you are trying to start the application contexts in the application lifecycle startup. I would open a case with support as the stack trace you sent didn't really provide any additional obvious clues to me.

Maybe you are looking for

  • How to call methods from within run()

    Seems like this must be a common question, but I cannot for the life of me, find the appropriate topic. So apologies ahead of time if this is a repeat. I have code like the following: public class MainClass implements Runnable { public static void ma

  • Transfer music and photos back to my computer

    I had a virus and resulted in my having to change my hard disk. I did not have back up of my photos or music, which they are safe on my Ipod photo. Now my computer is fully repaired and have downlowded my software for i-pod again, obviusly is empty.

  • Dialog  programing

    Hi In dialog programming if i enter the vendor code and press enter then it should automatically display the vendor name. how to do this. Thanks, Madhu

  • BT Broadband Phone how to switch on in router

    my blue light use to be on on my home hub for phone, its now out, when i go in to hub it says not activate on hub then a box says try to fix click here, so i do, it then tells me to press restart button on hub, which i do, i then click box to activat

  • "sqlplus / as sysdba" and "sqlplus /nolog;conn / as sysdba"

    Hi, What is the difference between "sqlplus / as sysdba" and "sqlplus /nolog;conn / as sysdba"? when "sqlplus / as sysdba", it could not "alter user system identified by password; when "sqlplus /nolog;conn / as sysdba", it could "alter user system id