Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.

Cannot start adobe-livecycle-weblogic.ear from ES4 on weblogic 12.1.2.0.0

Avatar

Former Community Member

I am trying to install Adobe LiveCycle ES4 on the following

OS: Win 2008 R2

DB: Oracle 11.2.0.1.0

AppServer: 12.1.2.0.0

Java: jdk1.6.0_43 (64 bit)

Using Configuration Manager, all the validations passed, but deploy failed.

When I tried to manually deploy,  adobe-livecycle-native-weblogic-x86_win32.ear and adobe-workspace-client.ear deployed and started successfully.

However adobe-livecycle-weblogic.ear deploys but cannot start.

The error in the managed server's out file is:

####<Sep 12, 2013 12:35:40 AM IST> <Info> <Deployer> <pnv6s162> <AdminServer> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <adobelc11> <> <> <1378926340732> <BEA-149038> <Initiating task for adobe-livecycle-weblogic : [Deployer:149026]start application adobe-livecycle-weblogic on AdobeLCServer..>

####<Sep 12, 2013 12:36:12 AM IST> <Warning> <Deployer> <pnv6s162> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1378926372937> <BEA-149004> <Failures were detected while initiating start task for application "adobe-livecycle-weblogic".>

####<Sep 12, 2013 12:36:12 AM IST> <Warning> <Deployer> <pnv6s162> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1378926372937> <BEA-149078> <Stack trace for message 149004

weblogic.application.ModuleException: java.util.ServiceConfigurationError: javax.servlet.ServletContainerInitializer: Provider com.sun.xml.ws.transport.http.servlet.WSServletContainerInitializer not found

    at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:140)

    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)

    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:213)

    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:208)

    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)

    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:70)

    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:24)

    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729)

    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)

    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258)

    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:61)

    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165)

    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)

    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:586)

    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:148)

    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:114)

    at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:151)

    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:339)

    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:846)

    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1275)

    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:442)

    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:176)

    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)

    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)

    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)

    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:550)

    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)

    at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)

Caused By: java.util.ServiceConfigurationError: javax.servlet.ServletContainerInitializer: Provider com.sun.xml.ws.transport.http.servlet.WSServletContainerInitializer not found

    at java.util.ServiceLoader.fail(ServiceLoader.java:214)

    at java.util.ServiceLoader.access$300(ServiceLoader.java:164)

    at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:348)

    at java.util.ServiceLoader$1.next(ServiceLoader.java:428)

    at weblogic.jaxrs.onwls.deploy.util.JaxRsDeployer.getJaxRsInitializerFromUserApp(JaxRsDeployer.java:133)

    at weblogic.jaxrs.server.portable.servlet.JerseyServletContainerInitializer.onStartup(JerseyServletContainerInitializer.java:75)

    at weblogic.servlet.internal.WebAppServletContext.initContainerInitializer(WebAppServletContext.java:1339)

    at weblogic.servlet.internal.WebAppServletContext.initContainerInitializers(WebAppServletContext.java:1276)

    at weblogic.servlet.internal.WebAppServletContext.initContainerInitializers(WebAppServletContext.java:1262)

    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1779)

    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2807)

    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1661)

    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:822)

    at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:360)

    at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:356)

    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)

    at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:138)

    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)

    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:213)

    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:208)

    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)

    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:70)

    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:24)

    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729)

    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)

    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258)

    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:61)

    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165)

    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)

    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:586)

    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:148)

    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:114)

    at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:151)

    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:339)

    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:846)

    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1275)

    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:442)

    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:176)

    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)

    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)

    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)

    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:550)

    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)

    at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)

>

I downloaded jaxws-rt.jar (which contains the com.sun.xml.ws.transport.http.servlet.WSServletContainerInitializer class) and added it to the classpath of the managed server and the admin server, but that did not solve the problem.

5 Replies

Avatar

Employee

Hi Aniruddha,

LiveCycle doesn’t support any other JDK with Oracle WebLogic on non-Solaris™ platforms other than Oracle JRockit JDK.

for more info visit http://helpx.adobe.com/livecycle/help/livecycle-es4-supported-platforms.html#LiveCycle%20client%20su... and go through the exceptions list

--Santosh

Avatar

Former Community Member

Hi Santosh,

I switched to Oracle JRockit. Still facing the same issue.

Thanks,

Aniruddha

Avatar

Level 2

Hi Aniruddha,

This seems application server issue.

Can you check other ears deployment? Are they starting well?

Do you have any other non-livecycle war/ear on the server? if not please check deployment of any such application.

Thanks,

Pankaj Parashar

Avatar

Former Community Member

Hi Pankaj,

I was able to successfully deploy and start the other 2 war files i.e. adobe-livecycle-native-weblogic-x86_win32.ear and adobe-workspace-client.ear.

Only adobe-livecycle-weblogic.ear deploys but cannot start.

Thanks,

Aniruddha

Avatar

Level 1

I was having a similar problem. Switching to Oracle JRockit and restarting the Weblogic server after making Security Realms settings fixed the issue. For restarting the server, Shut down Managed Server followed by Admin Server and then the Node Manager. Then start NodeManager, Admin Server and Managed Server in this order.

Also make sure that you have done the memory settings for the managed server as mentioned in http://help.adobe.com/en_US/livecycle/11.0/PrepareInstallSingle/lc_prepare_install_single.pdf