-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Startup problem with Liferay 6.2 GA1 SP1 #4
Comments
Testing with deployment of portlet from store with vanilla 6.2 EE SP1 is not showing the error, investigating further: 00:57:35,387 INFO [http-bio-8080-exec-4][PortletAutoDeployListener:79] Copying portlets for /home/chun/Projects/Servers/liferay-portal-6.2-ee-sp1/tomcat-7.0.42/temp/20140228245735384/webcontent-workflow-portlet-6.2.0.2.war |
and restart: |
Problem is still there for us even after redeploying the theme: De After restart: Feb 28, 2014 12:07:17 PM org.apache.catalina.startup.HostConfig deployDirectory Feb 28, 2014 12:07:17 PM org.apache.catalina.core.StandardContext loadOnStartup |
Hi, same here using liferay 6.2, jbossa7 bundle, after restart: 19:21:27,833 INFO [au.com.permeance.liferay.util.startup.StartupListener](MSC service thread 1-8) Starting up Web Content Workflow Configuration Portlet 19:21:27,857 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/webcontent-workflow-portlet]](MSC service thread 1-8) Servlet /webcontent-workflow-portlet threw load() exception: java.lang.NullPointerException |
The startup action throws a NPE at portal startup:
Feb 27, 2014 11:24:58 AM org.apache.catalina.core.StandardContext loadOnStartup
SEVERE: Servlet /webcontent-workflow-portlet threw load() exception
java.lang.NullPointerException
at com.liferay.portal.kernel.workflow.WorkflowHandlerRegistryUtil.getWorkflowHandler(WorkflowHandlerRegistryUtil.java:47)
at au.com.permeance.liferay.util.startup.StartupListener.applicationStart(StartupListener.java:52)
at au.com.permeance.liferay.util.startup.StartupServlet.init(StartupServlet.java:39)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5015)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5302)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:895)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:871)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1095)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1617)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
The text was updated successfully, but these errors were encountered: