水手博客

Wealthy is ability to share.


« [转载]网页病毒清除后IE可能出现的故障AIX系统 学习、培训、认证资料链接 »

WebSphere不能登录管理控制台的解决办法

  启动WebSphere的Deployment Manager(dmgr,命令:./startManager.sh)后,通过浏览器登录WebSphere的管理控制台(http://192.168.1.1:9090/admin,自动转到https://192.168.1.1:9043/admin/logon.jsp),输入完用户名和密码后,进入不了管理界面,出现一个错误页面。显示:

错误 500
处理请求时发生一个错误: /admin/secure/securelogon.do
消息:
java.lang.NullPointerException
at org.apache.jsp._console._jspService(_console.java:172)
at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java:89)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.cache.servlet.ServletWrapper.serviceProxied(ServletWrapper.java:257)
at com.ibm.ws.cache.servlet.CacheHook.handleFragment(CacheHook.java:250)
at com.ibm.ws.cache.servlet.CacheHook.handleServlet(CacheHook.java:141)
at com.ibm.ws.cache.servlet.ServletWrapper.service(ServletWrapper.java:239)
at com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:344)
at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(JspServlet.java:683)
at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java:781)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:1171)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:676)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:203)
at org.apache.struts.tiles.ActionComponentServlet.processForward(ActionComponentServlet.java:295)
at org.apache.struts.tiles.ActionComponentServlet.processActionForward(ActionComponentServlet.java:104)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1596)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.cache.servlet.ServletWrapper.serviceProxied(ServletWrapper.java:257)
at com.ibm.ws.cache.servlet.CacheHook.handleFragment(CacheHook.java:250)
at com.ibm.ws.cache.servlet.CacheHook.handleServlet(CacheHook.java:141)
at com.ibm.ws.cache.servlet.ServletWrapper.service(ServletWrapper.java:239)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:1171)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:676)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:203)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:125)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:294)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:116)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:912)

  在IBM的网站上找到了解决办法:Admin console throws error 500 with java.lang.NullPointerExcetion and SAXParseException Premature end of file。按照文章中提供的方法,先清理一下磁盘空间(之前磁盘空间满了),然后把/wstemp//prefrences.xml这个文件删除掉,就可以了。

  除此之外,还可以尝试以下办法:
1)只启动dmgr,其他node不启动,进入系统管理-Deployment Manager(dmgr)-进程定义-Java虚拟机,修改初始堆大小和最大堆大小(原来默认值都是0)为128、256,如果单元中节点比较多,应用服务器也很多,那么调到256、512就可以了,通常不需要再大了。
2)把/tmp/,/temp/,/wstemp/中的内容都删除掉,然后重新启动dmgr或nodeagent。
 

发表评论:

◎欢迎参与讨论,请在这里发表您的看法、交流您的观点。

日历

最新留言

最近发表

AD

Powered By Z-Blog 1.6 Final Build 60802

Copyright 2005-2006 BosunLand.com. Some Rights Reserved.