今天下午启动webSphere,死活无法启动,数据库配置都很正常,唯独替换ear包后就各种起不来,想想连接地址的配置应该都对,咋回事呢?
异常如下
[18-12-24 0:18:46:245 CST] 0000004e ThreadMonitor W WSVR0605W: 线程“server.startup : 2”(00000075)已保持活动状态 713733 毫秒,此线程可能已挂起。在服务器中共有 1 个线程可能处于挂起状态。
at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:719)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1179)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1390)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:639)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:979)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:778)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$5.run(ApplicationMgrImpl.java:2198)
at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:5486)
at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:5612)
at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:255)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2203)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:435)
at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:378)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access 500 ( C o m p o s i t i o n U n i t M g r I m p l . j a v a : 126 ) a t c o m . i b m . w s . r u n t i m e . c o m p o n e n t . C o m p o s i t i o n U n i t M g r I m p l 500(CompositionUnitMgrImpl.java:126) at com.ibm.ws.runtime.component.CompositionUnitMgrImpl 500(CompositionUnitMgrImpl.java:126)at
启动websphere提示线程可能已挂起
最新推荐文章于 2021-05-09 06:53:52 发布
本文记录了在启动Websphere时遇到线程可能已挂起的问题,详细列出了错误日志,通过分析发现是由于配置的远程IP错误导致连接问题,从而使得服务器无法正常启动。纠正IP配置后,问题得到解决,提醒开发者在遇到类似问题时要检查网络配置。
摘要由CSDN通过智能技术生成