部署在本地没有问题，但是上传到SAE上面，总是报502错误 - JEECMS官方论坛|开源java cms,jsp cms,jsp bbs

wangaowell

级别: 秀才

UID: 66774
积分:69 加为好友
威望: 1 精华: 0
主题:5 回复:36
注册时间:2014-09-10
在线时长:0

11# 发表于:2014-09-23 14:06:54 IP:221.83.*.*

回复第9楼

JAVA_SAE_Fatal_error:
Failed startup of context c.s.s.w.SaeWebAppContext{/1/wellscms,file:/data1/jetty_work/142/wellscms/jetty-0.0.0.0-12092-wellscms.war-_1_wellscms-any-/webapp/},/data1/www/htdocs/142/wellscms/1/wellscms.warjava.lang.RuntimeException: thread number upper limit of normal
at java.lang.Thread$Controlor.incrementNumber(Thread.java:343)
at java.lang.Thread.init(Thread.java:364)
at java.lang.Thread.<init>(Thread.java:472)
at java.util.TimerThread.<init>(Timer.java:478)
at java.util.Timer.<init>(Timer.java:100)
at org.eclipse.jetty.server.session.HashSessionManager.doStart(HashSessionManager.java:91)
at com.sina.sae.server.session.SaeHashSessionManager.doStart(SaeHashSessionManager.java:45)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:58)
at org.eclipse.jetty.server.session.SessionHandler.doStart(SessionHandler.java:112)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:58)
at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:89)
at org.eclipse.jetty.server.handler.ScopedHandler.doStart(ScopedHandler.java:97)
at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:629)
at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:229)
at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1208)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:586)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:449)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:58)
at org.eclipse.jetty.deploy.bindings.StandardStarter.processBinding(StandardStarter.java:36)
at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:180)
at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(Depl yq37.javaruntime

Failed startup of context c.s.s.w.SaeWebAppContext{/1/wellscms,file:/data1/jetty_work/142/wellscms/jetty-0.0.0.0-12092-wellscms.war-_1_wellscms-any-/webapp/},/data1/www/htdocs/142/wellscms/1/wellscms.warjava.lang.RuntimeException: thread number upper limit of normal
at java.lang.Thread$Controlor.incrementNumber(Thread.java:343)
at java.lang.Thread.init(Thread.java:364)
at java.lang.Thread.<init>(Thread.java:472)
at java.util.TimerThread.<init>(Timer.java:478)
at java.util.Timer.<init>(Timer.java:100)
at org.eclipse.jetty.server.session.HashSessionManager.doStart(HashSessionManager.java:91)
at com.sina.sae.server.session.SaeHashSessionManager.doStart(SaeHashSessionManager.java:45)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:58)
at org.eclipse.jetty.server.session.SessionHandler.doStart(SessionHandler.java:112)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:58)
at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:89)
at org.eclipse.jetty.server.handler.ScopedHandler.doStart(ScopedHandler.java:97)
at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:629)
at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:229)
at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1208)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:586)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:449)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:58)
at org.eclipse.jetty.deploy.bindings.StandardStarter.processBinding(StandardStarter.java:36)
at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:180)
at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(Depl yq37.javaruntime