Liferay DEployment issue weblogic

[8年前 に sam md によって更新されました。]

Hi,

I am trying to deploy .war file to weblogic server 10g in XLdeploy. I am getting the below error. Can you please let me know where am I going wrong in this.


Starting an edit session ...
Started edit session, please be sure to save and activate your
changes once you are done.
raw install args:{'deleteProcessedArtifact': 1, 'stageMode': 'Stage', 'activationTimeout': -10, 'retireTimeout': -1, 'block': 1, 'versioned': 0, 'deleteUploadedArtifact': 1, 'fetchLiferayArtifact': 0, 'timeout': 10}
stage mode
Deploying application to prt_server_01 with the following options {'deleteProcessedArtifact': 1, 'stageMode': 'stage', 'block': 1, 'deleteUploadedArtifact': 1, 'fetchLiferayArtifact': 0, 'timeout': 10, 'upload': 'true'}
Warning: Unrecognized option deleteUploadedArtifact is being ignored
Warning: Unrecognized option fetchLiferayArtifact is being ignored
Warning: Unrecognized option deleteProcessedArtifact is being ignored
Deploying application from /stage/****/**********/a1fdeff2-ff40-42bf-8599-a2df5249d291/ to targets prt_server_01 (upload=true) ...
<Nov 23, 2015 8:56:14 AM HST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, [archive: /stage/******/*****/a1fdeff2-ff40-42bf-8599-a2df5249d291/], to prt_server_01 .>
You have an edit session in progress, hence WLST will not
block for your deployment to complete.
Started the Deployment of Application. Please refer to the returned WLSTProgress object or variable LAST to track the status.
Validating changes ...
Validated the changes successfully
Saving all your changes ...
Saved all your changes successfully.
Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released
once the activation is completed.
This Exception occurred at Mon Nov 23 08:56:18 HST 2015.
weblogic.application.ModuleException: [HTTP:101216]Servlet: "view-servlet" failed to preload on startup in Web application:r".
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
at org.springframework.web.servlet.DispatcherServlet.<clinit>(DispatcherServlet.java:246)
at org.springframework.web.servlet.ViewRendererServlet.<clinit>(ViewRendererServlet.java:53)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.lang.Class.newInstance(Class.java:374)
at weblogic.servlet.internal.WebComponentContributor.getNewInstance(WebComponentContributor.java:225)
at weblogic.servlet.internal.WebComponentContributor.createServletInstance(WebComponentContributor.java:249)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:255)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
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:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:671)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:44)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
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:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
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:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory
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:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
... 51 more

activation error
No stack trace available.
Traceback (most recent call last):
File "/tmp/ot-20151123T135605094/daemon.py", line 372, in ?
exec command
File "<string>", line 1, in ?
File "/tmp/ot-20151123T135605094/daemon.py", line 264, in runScriptFromDaemon
execfile(scriptPath)
File "/tmp/ot-20151123T135603946/deploy-application.py", line 361, in ?
saveAndActivate(activationTimeout)
File "/tmp/ot-20151123T135605094/daemon.py", line 204, in saveAndActivate
task = activate(block="true")
File "<iostream>", line 376, in activate
File "<iostream>", line 1847, in raiseWLSTException
WLSTException: Error occured while performing activate : Error while Activating changes. : [HTTP:101216]Servlet: "view-servlet" failed to preload on startup in Web application: ".war".
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
at org.springframework.web.servlet.DispatcherServlet.<clinit>(DispatcherServlet.java:246)
at org.springframework.web.servlet.ViewRendererServlet.<clinit>(ViewRendererServlet.java:53)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.lang.Class.newInstance(Class.java:374)
at weblogic.servlet.internal.WebComponentContributor.getNewInstance(WebComponentContributor.java:225)
at weblogic.servlet.internal.WebComponentContributor.createServletInstance(WebComponentContributor.java:249)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:255)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
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:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:671)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:44)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
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:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
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:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory
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:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
... 51 more

Use dumpStack() to view the full stacktrace
Discarded all your changes successfully.
Edit session has been stopped successfully.


Thank you
Sam

[8年前 に David H Nebinger によって更新されました。]

When you're building for weblogic, make sure you use the "direct-deploy" target. The normal war is not fully instrumented for cluster deployment...

[8年前 に David H Nebinger によって更新されました。]

I think you misunderstood me, Sam.

When you're building your portlet war, use the "direct-deploy" target. For the SDK, you do "ant direct-deploy". For Maven, you do "mvn liferay:direct-deploy".

This builds the fully instrumented war file.

Use that war file in conjunction with your app container's console for deployment. Use your normal war deployment process.

[8年前 に sam md によって更新されました。]

Hi David,


Awesome ! It worked out for me. Deployment is successful.



Thank you SO much.

Best Regards

Sam

[8年前 に sam md によって更新されました。]

David,


I have a query. In web logic. the normal war file is not configured fro deployment directly? Can I know the reason please.


Thank you
Best Regards
Sam

[8年前 に David H Nebinger によって更新されました。]

By default Liferay uses an "auto deploy" mechanism. This process is responsible for many things such as:

• Copying portal dependency jars listed in liferay-plugin-package.properties into the /WEB-INF/lib directory.
• Injecting servlet(s) into /WEB-INF/web.xml.
• Injecting default jars into /WEB-INF/lib.

All of these things allow you to build a slimmed down war file that is easy to upload to a target system (due to size). The auto deploy will take care of injecting all of this stuff and then the app container will pick up with the deployment.

When you use the "direct-deploy" target, the stuff done in the normal auto-deploy process is moved into the build step instead of during the deploy step.

App containers like weblogic and websphere can face issues with the Liferay auto deploy mechanism because they don't like relinquishing control to a webapp. In Weblogic clusters, the control system is not even a node in the cluster yet it is responsible for cluster deployment. So you won't have Liferay running on that one, but since Liferay isn't there it doesn't handle auto-deploy at all.

The direct-deploy build target will give you the deployable artifact for these environs, but you only want to use it if you really need to. For example, if you're using WebLogic in production but tomcat in test and/or dev, use the direct-deploy artifact only for weblogic and the normal deploy process for tomcat.

[8年前 に sam md によって更新されました。]

Thank you David




Best Regards
Sam

[8年前 に sam md によって更新されました。]

HI David,

Hope you are doing very well from your end.
I am doing Liferay deployments in Xldeploy tool to weblogic console as a part of automation work. IS it mandatory to restart the portal servers after deployment. Because I don't see any restart of services during deployment.


Can you please reply me back



Thank you

Sam

[8年前 に David H Nebinger によって更新されました。]

Restart is often not a requirement, but personally I recommend a restart after deployment.

Different app servers have different issues and clean things up differently for undeploys and redeploys and the like. Performing a clean restart just puts your environment in a clean and consistent state after a deployment and helps to ensure that it's good to go for the long haul.

Now admittedly I don't know much about the Xideploy tool, so it may introduce it's own usage requirements...

[8年前 に sam md によって更新されました。]

Hi David,



Thank you for your response.




Best Regards
SAM