Hi all, @Kasun, Yes. This is the complete stack trace. see below [1].
@Tanya No we do not have any jars inside the jaggery application. I can be certain that this issue is coming with this CarbonTomcatSessionManager configuration. First we isolated that, this issue is coming only when we install web-app mgt 4.2.3 features and finally found that this configuration causes the issue in APIM. [1] [2015-05-13 23:28:50,105] ERROR - ServerManager Error while stopping tomcat org.apache.catalina.LifecycleException: Failed to stop component [StandardServer[8005]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) at org.apache.catalina.startup.Tomcat.stop(Tomcat.java:351) at org.wso2.carbon.tomcat.internal.ServerManager.stop(ServerManager.java:113) at org.wso2.carbon.tomcat.internal.TomcatBundleActivator.stop(TomcatBundleActivator.java:65) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:771) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:764) at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:510) at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:566) at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1206) at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:592) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:257) at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:215) at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:284) at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:692) at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:600) at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:399) at org.wso2.carbon.core.init.CarbonServerManager.shutdown(CarbonServerManager.java:849) at org.wso2.carbon.core.init.CarbonServerManager.shutdownGracefully(CarbonServerManager.java:883) at org.wso2.carbon.core.init.CarbonServerManager$4.run(CarbonServerManager.java:894) Caused by: org.apache.catalina.LifecycleException: Failed to stop component [StandardService[Catalina]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) at org.apache.catalina.core.StandardServer.stopInternal(StandardServer.java:760) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 19 more Caused by: org.apache.catalina.LifecycleException: Failed to stop component [StandardEngine[Catalina]] at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) at org.apache.catalina.core.StandardService.stopInternal(StandardService.java:502) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 21 more Caused by: org.apache.catalina.LifecycleException: A child container failed during stop at org.apache.catalina.core.ContainerBase.stopInternal(ContainerBase.java:1186) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) ... 23 more [2015-05-13 23:28:50,107] INFO - CarbonTomcatServiceComponent Stopping the carbon web-app registered under : / [2015-05-13 23:28:51,011] INFO - CarbonServerManager Shutdown complete [2015-05-13 23:28:51,011] INFO - CarbonServerManager Halting JVM Thanks, Lakmali On 14 May 2015 at 06:37, Tanya Madurapperuma <[email protected]> wrote: > The error in [1] occurs if the WEB-INF/lib or WEB-INF/classes directory > has jars in the jaggery application. Does any of the jaggery apps has jars > in the above folders? > > [1] https://wso2.org/jira/browse/JAGGERY-403 > > Thanks, > Tanya > > On Thu, May 14, 2015 at 1:15 AM, KasunG Gajasinghe <[email protected]> > wrote: > >> Hi Lakmali, >> >> Is this the complete error? There was an issue with Jaggery webapp >> deployer, and we have fixed that recently. See [1]. Could that be the case >> for you as well? In that case, the stack trace clearly mentioned that the >> issue occurred with CarbonTomcatSessionManager. >> >> [1] https://wso2.org/jira/browse/JAGGERY-403 >> >> On Wed, May 13, 2015 at 11:38 PM, Lakmali Baminiwatta <[email protected]> >> wrote: >> >>> Hi all, >>> >>> Found out that, this issue is occurring due >>> to org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager setting in the >>> tomcat/context.xml. Issue get resolved and exception is no more thrown when >>> I comment it out. >>> >>> <Manager >>> >>> className="org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager" >>> sessionIdLength="16"> >>> </Manager> >>> >>> @Supun, >>> Can this be due to jaggery apps not supporting this setting [1]? I can >>> remember that the improvement done in [2] was not applicable to >>> sessionId length of Jagger applications. Because the improvement is done >>> only in TomcatGenericWebappsDeployer, but for jaggery app deployment we >>> use TomcatJaggeryWebappsDeployer. >>> >>> >>> [1]https://wso2.org/jira/browse/JAGGERY-400 >>> [2]https://wso2.org/jira/browse/WSAS-1818 >>> >>> Thanks, >>> Lakmali >>> >>> >>> On 12 May 2015 at 11:19, Manoj Kumara <[email protected]> wrote: >>> >>>> Hi Kishanthan, >>>> >>>> Did you faced similar issues during tomcat upgrading ? >>>> >>>> >>>> >>>> *Manoj Kumara* >>>> Software Engineer >>>> WSO2 Inc. http://wso2.com/ >>>> *lean.enterprise.middleware* >>>> Mobile: +94713448188 >>>> >>>> On Mon, May 11, 2015 at 8:36 PM, Lakmali Baminiwatta <[email protected]> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> After including kernel patch0010 into APIM 1.9.0, we can see below >>>>> exception in each server shutdown. Note that we >>>>> upgraded org.wso2.carbon.webapp.mgt.server.feature version >>>>> into 4.2.3-SNAPSHOT. >>>>> >>>>> Any idea? >>>>> >>>>> [2015-05-11 19:09:57,241] ERROR - ServerManager Error while stopping >>>>> tomcat >>>>> org.apache.catalina.LifecycleException: Failed to stop component >>>>> [StandardServer[8005]] >>>>> at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) >>>>> at org.apache.catalina.startup.Tomcat.stop(Tomcat.java:345) >>>>> at >>>>> org.wso2.carbon.tomcat.internal.ServerManager.stop(ServerManager.java:113) >>>>> at >>>>> org.wso2.carbon.tomcat.internal.TomcatBundleActivator.stop(TomcatBundleActivator.java:65) >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:771) >>>>> at java.security.AccessController.doPrivileged(Native Method) >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:764) >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:510) >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:566) >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1206) >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:592) >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:257) >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:215) >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:284) >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:692) >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:600) >>>>> at >>>>> org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:399) >>>>> at >>>>> org.wso2.carbon.core.init.CarbonServerManager.shutdown(CarbonServerManager.java:849) >>>>> at >>>>> org.wso2.carbon.core.init.CarbonServerManager.shutdownGracefully(CarbonServerManager.java:883) >>>>> at >>>>> org.wso2.carbon.core.init.CarbonServerManager$4.run(CarbonServerManager.java:894) >>>>> Caused by: org.apache.catalina.LifecycleException: Failed to stop >>>>> component [StandardService[Catalina]] >>>>> at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) >>>>> at >>>>> org.apache.catalina.core.StandardServer.stopInternal(StandardServer.java:753) >>>>> at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) >>>>> ... 19 more >>>>> Caused by: org.apache.catalina.LifecycleException: Failed to stop >>>>> component [StandardEngine[Catalina]] >>>>> at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236) >>>>> at >>>>> org.apache.catalina.core.StandardService.stopInternal(StandardService.java:502) >>>>> at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) >>>>> ... 21 more >>>>> Caused by: org.apache.catalina.LifecycleException: A child container >>>>> failed during stop >>>>> at >>>>> org.apache.catalina.core.ContainerBase.stopInternal(ContainerBase.java:1186) >>>>> at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) >>>>> ... 23 more >>>>> >>>>> Thanks, >>>>> Lakmali >>>>> >>>>> >>>>> -- >>>>> Lakmali Baminiwatta >>>>> Senior Software Engineer >>>>> WSO2, Inc.: http://wso2.com >>>>> lean.enterprise.middleware >>>>> mobile: +94 71 2335936 >>>>> blog : lakmali.com >>>>> >>>>> >>>> >>> >>> >>> -- >>> Lakmali Baminiwatta >>> Senior Software Engineer >>> WSO2, Inc.: http://wso2.com >>> lean.enterprise.middleware >>> mobile: +94 71 2335936 >>> blog : lakmali.com >>> >>> >> >> >> -- >> >> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. >> email: kasung AT spamfree wso2.com >> linked-in: http://lk.linkedin.com/in/gajasinghe >> blog: http://kasunbg.org >> >> >> > > > > -- > Tanya Madurapperuma > > Senior Software Engineer, > WSO2 Inc. : wso2.com > Mobile : +94718184439 > Blog : http://tanyamadurapperuma.blogspot.com > -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
