Hi B.J., There are two application types. 0 for normal webapp and 1 for Jetspeed-specific local app. (Defined in org.apache.jetspeed.om.portlet.PortletApplication interface.) Because your previous deployment was registered as a local app before, the deployment this time seems failed. One simple solution is to reinitialize the registry by reinitializing the Jetspeed database. If you installed by installer, then you can find out how to do it here (The "Changing the Database" section):
http://portals.apache.org/jetspeed-2/getting-started-installer.html HTH, Woonsan --- On Thu, 7/9/09, bhardage <[email protected]> wrote: > From: bhardage <[email protected]> > Subject: Re: Problem deploying Spring Portlet MVC webapp > To: [email protected] > Date: Thursday, July 9, 2009, 8:40 PM > > Changing the log level to DEBUG produced the following in > jetspeed-deployment: > > 2009-07-09 13:21:52,093 [Timer-3] DEBUG deployment - Is > portlet application > petportal monitored? -> false > 2009-07-09 13:21:52,093 [Timer-3] DEBUG deployment - Try to > start portlet > application petportal. > 2009-07-09 13:21:52,093 [Timer-3] DEBUG deployment - New > checksum for > portlet application petportal is 766526751 > 2009-07-09 13:21:52,140 [Timer-3] DEBUG deployment - > Portlet Application > petportal found in registry. > 2009-07-09 13:21:52,156 [Timer-3] ERROR deployment - Error > starting portlet > application petportal > org.apache.jetspeed.components.portletregistry.RegistryException: > Cannot > start portlet application petportal: as Application Types > don't match: 1 != > 0 > at > org.apache.jetspeed.tools.pamanager.PortletApplicationManager.attemptStartPA(PortletApplicationManager.java:504) > at > org.apache.jetspeed.tools.pamanager.PortletApplicationManager.tryStartPortletApplication(PortletApplicationManager.java:244) > at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at > java.lang.reflect.Method.invoke(Method.java:597) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) > at > org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at > $Proxy13.tryStartPortletApplication(Unknown Source) > at > org.apache.jetspeed.tools.pamanager.PortletApplicationManager.retryStartPortletApplication(PortletApplicationManager.java:214) > at > org.apache.jetspeed.tools.pamanager.PortletApplicationManager.startPortletApplication(PortletApplicationManager.java:195) > at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at > java.lang.reflect.Method.invoke(Method.java:597) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198) > at > $Proxy13.startPortletApplication(Unknown Source) > at > org.apache.jetspeed.container.JetspeedContainerServlet.attemptStart(JetspeedContainerServlet.java:191) > at > org.apache.jetspeed.container.JetspeedContainerServlet$1.run(JetspeedContainerServlet.java:162) > at > java.util.TimerThread.mainLoop(Timer.java:512) > at > java.util.TimerThread.run(Timer.java:462) > 2009-07-09 13:21:52,156 [Timer-3] DEBUG deployment - Add > change monitor for > application petportal and set unsuccessful starts to 1. > 2009-07-09 13:21:52,203 [Timer-3] DEBUG deployment - Is > portlet application > petportal monitored? -> true > 2009-07-09 13:21:52,203 [Timer-3] DEBUG deployment - Try to > start portlet > application petportal. > 2009-07-09 13:21:52,203 [Timer-3] DEBUG deployment - New > checksum for > portlet application petportal is 766526751 > 2009-07-09 13:21:52,203 [Timer-3] DEBUG deployment - > Portlet Application > petportal found in registry. > 2009-07-09 13:21:52,203 [Timer-3] ERROR deployment - Error > starting portlet > application petportal > org.apache.jetspeed.components.portletregistry.RegistryException: > Cannot > start portlet application petportal: as Application Types > don't match: 1 != > 0 > at > org.apache.jetspeed.tools.pamanager.PortletApplicationManager.attemptStartPA(PortletApplicationManager.java:504) > ... > > basically repeating for 10 tries. > > The jetspeed-layouts portlet produced the following: > > 2009-07-09 13:21:50,671 [main] DEBUG deployment - Is > portlet application > jetspeed-layouts monitored? -> false > 2009-07-09 13:21:50,671 [main] DEBUG deployment - Try to > start portlet > application jetspeed-layouts. > 2009-07-09 13:21:50,671 [main] DEBUG deployment - New > checksum for portlet > application jetspeed-layouts is 2454617269 > 2009-07-09 13:21:51,296 [main] DEBUG deployment - Portlet > Application > jetspeed-layouts found in registry. > 2009-07-09 13:21:51,296 [main] DEBUG deployment - > unregistering portlet > application jetspeed-layouts... > 2009-07-09 13:21:51,296 [main] DEBUG deployment - > Re-register existing > portlet application jetspeed-layouts. > 2009-07-09 13:21:51,296 [main] DEBUG deployment - Node for > Portlet > application jetspeed-layouts is SAVED. > 2009-07-09 13:21:51,296 [main] DEBUG deployment - Register > Portlet > application jetspeed-layouts in portlet factory. > 2009-07-09 13:21:51,296 [main] DEBUG deployment - Add > change monitor for > application jetspeed-layouts with checksum 2454617269. > 2009-07-09 13:21:51,296 [main] INFO deployment - > Deployment scanner > successfuly started! > > So, it looks like the petportal portlet is crashing right > before it tries to > unregister the petportal application. I'm not exactly sure > what the error > "Application Types don't match: 1 != 0" means though. > > I'm afraid I'm not familiar enough with Jetspeed to know > exactly what this > is saying. > > Thanks, > B.J. > -- > View this message in context: > http://www.nabble.com/Problem-deploying-Spring-Portlet-MVC-webapp-tp24399589p24415051.html > Sent from the Jetspeed - Dev mailing list archive at > Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
