您的位置:程序门 -> websphere -> 应用服务器/was



windows平台下websphere6.1 配置数据源后发现的奇怪问题


[收藏此页] [打印本页]选择字色:背景色:字体:[][][]


windows平台下websphere6.1 配置数据源后发现的奇怪问题
发表于:2008-01-25 09:22:48 楼主
websphere6.1   补丁6.1.0.13

现象   :发布应用后,配置数据源,测试成功,并且在应用中能正常使用。但是,重新启动websphere服务后,发现控制台进不去了,报http   500   的错误。但是应用程序还能够正常访问,折腾了好久了,也不知道问题出在哪里了.....   异常信息如下:
[08-1-24   10:03:51:281   cst]   0000001f   servletwrappe   e       deregister   the   mbean   because   of   uncaught   init()   exception   thrown   by   servlet   action:   javax.servlet.unavailableexception:   io   error   while   parsing   file   '/web-inf/com.ibm.ws.console.core/console-defs.xml'.   connection   reset
at   org.apache.struts.action.actionservlet.init(actionservlet.java:368)
at   javax.servlet.genericservlet.init(genericservlet.java:256)
at   com.ibm.ws.webcontainer.servlet.servletwrapper.init(servletwrapper.java:190)
at   com.ibm.ws.wswebcontainer.servlet.servletwrapper.init(servletwrapper.java:317)
at   com.ibm.ws.webcontainer.servlet.servletwrapper.handlerequest(servletwrapper.java:346)
at   com.ibm.ws.wswebcontainer.servlet.servletwrapper.handlerequest(servletwrapper.java:464)
at   com.ibm.ws.webcontainer.webapp.webapprequestdispatcher.forward(webapprequestdispatcher.java:321)
at   com.ibm.ws.webcontainer.servlet.filterproxyservlet.dispatch(filterproxyservlet.java:73)
at   com.ibm.ws.webcontainer.servlet.filterproxyservlet.service(filterproxyservlet.java:52)
at   com.ibm.ws.webcontainer.servlet.servletwrapper.service(servletwrapper.java:989)
at   com.ibm.ws.webcontainer.servlet.servletwrapper.service(servletwrapper.java:930)
at   com.ibm.ws.webcontainer.filter.webappfilterchain.dofilter(webappfilterchain.java:118)
at   com.ibm.ws.webcontainer.filter.webappfilterchain._dofilter(webappfilterchain.java:87)
at   com.ibm.ws.webcontainer.filter.webappfiltermanager.dofilter(webappfiltermanager.java:766)
at   com.ibm.ws.webcontainer.filter.webappfiltermanager.dofilter(webappfiltermanager.java:674)
at   com.ibm.ws.webcontainer.filter.webappfiltermanager.invokefilters(webappfiltermanager.java:689)
at   com.ibm.ws.wswebcontainer.filter.webappfiltermanager.invokefilters(webappfiltermanager.java:101)
at   com.ibm.ws.webcontainer.extension.defaultextensionprocessor.invokefilters(defaultextensionprocessor.java:791)
at   com.ibm.ws.webcontainer.extension.defaultextensionprocessor.handlerequest(defaultextensionprocessor.java:563)
at   com.ibm.ws.wswebcontainer.extension.defaultextensionprocessor.handlerequest(defaultextensionprocessor.java:113)
at   com.ibm.ws.webcontainer.webapp.webapp.handlerequest(webapp.java:3276)
at   com.ibm.ws.webcontainer.webapp.webgroup.handlerequest(webgroup.java:267)
at   com.ibm.ws.webcontainer.webcontainer.handlerequest(webcontainer.java:811)
at   com.ibm.ws.wswebcontainer.webcontainer.handlerequest(webcontainer.java:1455)
at   com.ibm.ws.webcontainer.channel.wcchannellink.ready(wcchannellink.java:113)
at   com.ibm.ws.http.channel.inbound.impl.httpinboundlink.handlediscrimination(httpinboundlink.java:454)
at   com.ibm.ws.http.channel.inbound.impl.httpinboundlink.handlenewinformation(httpinboundlink.java:383)
at   com.ibm.ws.http.channel.inbound.impl.httpiclreadcallback.complete(httpiclreadcallback.java:102)
at   com.ibm.ws.tcp.channel.impl.aioreadcompletionlistener.futurecompleted(aioreadcompletionlistener.java:165)
at   com.ibm.io.async.abstractasyncfuture.invokecallback(abstractasyncfuture.java:217)
at   com.ibm.io.async.asyncchannelfuture.firecompletionactions(asyncchannelfuture.java:161)
at   com.ibm.io.async.asyncfuture.completed(asyncfuture.java:136)
at   com.ibm.io.async.resulthandler.complete(resulthandler.java:195)
at   com.ibm.io.async.resulthandler.runeventprocessingloop(resulthandler.java:743)
at   com.ibm.io.async.resulthandler$2.run(resulthandler.java:873)
at   com.ibm.ws.util.threadpool$worker.run(threadpool.java:1469)
,  
发表于:2008-01-25 09:23:191楼 得分:0
日志过长   接着

websphere6.1   补丁6.1.0.13

现象   :发布应用后,配置数据源,测试成功,并且在应用中能正常使用。但是,重新启动websphere服务后,发现控制台进不去了,报http   500   的错误。但是应用程序还能够正常访问,折腾了好久了,也不知道问题出在哪里了.....   异常信息如下:
[08-1-24   10:03:51:281   cst]   0000001f   servletwrappe   e       deregister   the   mbean   because   of   uncaught   init()   exception   thrown   by   servlet   action:   javax.servlet.unavailableexception:   io   error   while   parsing   file   '/web-inf/com.ibm.ws.console.core/console-defs.xml'.   connection   reset
at   org.apache.struts.action.actionservlet.init(actionservlet.java:368)
at   javax.servlet.genericservlet.init(genericservlet.java:256)
at   com.ibm.ws.webcontainer.servlet.servletwrapper.init(servletwrapper.java:190)
at   com.ibm.ws.wswebcontainer.servlet.servletwrapper.init(servletwrapper.java:317)
at   com.ibm.ws.webcontainer.servlet.servletwrapper.handlerequest(servletwrapper.java:346)
at   com.ibm.ws.wswebcontainer.servlet.servletwrapper.handlerequest(servletwrapper.java:464)
at   com.ibm.ws.webcontainer.webapp.webapprequestdispatcher.forward(webapprequestdispatcher.java:321)
at   com.ibm.ws.webcontainer.servlet.filterproxyservlet.dispatch(filterproxyservlet.java:73)
at   com.ibm.ws.webcontainer.servlet.filterproxyservlet.service(filterproxyservlet.java:52)
at   com.ibm.ws.webcontainer.servlet.servletwrapper.service(servletwrapper.java:989)
at   com.ibm.ws.webcontainer.servlet.servletwrapper.service(servletwrapper.java:930)
at   com.ibm.ws.webcontainer.filter.webappfilterchain.dofilter(webappfilterchain.java:118)
at   com.ibm.ws.webcontainer.filter.webappfilterchain._dofilter(webappfilterchain.java:87)
at   com.ibm.ws.webcontainer.filter.webappfiltermanager.dofilter(webappfiltermanager.java:766)
at   com.ibm.ws.webcontainer.filter.webappfiltermanager.dofilter(webappfiltermanager.java:674)
at   com.ibm.ws.webcontainer.filter.webappfiltermanager.invokefilters(webappfiltermanager.java:689)
at   com.ibm.ws.wswebcontainer.filter.webappfiltermanager.invokefilters(webappfiltermanager.java:101)
at   com.ibm.ws.webcontainer.extension.defaultextensionprocessor.invokefilters(defaultextensionprocessor.java:791)
at   com.ibm.ws.webcontainer.extension.defaultextensionprocessor.handlerequest(defaultextensionprocessor.java:563)
at   com.ibm.ws.wswebcontainer.extension.defaultextensionprocessor.handlerequest(defaultextensionprocessor.java:113)
at   com.ibm.ws.webcontainer.webapp.webapp.handlerequest(webapp.java:3276)
at   com.ibm.ws.webcontainer.webapp.webgroup.handlerequest(webgroup.java:267)
at   com.ibm.ws.webcontainer.webcontainer.handlerequest(webcontainer.java:811)
at   com.ibm.ws.wswebcontainer.webcontainer.handlerequest(webcontainer.java:1455)
at   com.ibm.ws.webcontainer.channel.wcchannellink.ready(wcchannellink.java:113)
at   com.ibm.ws.http.channel.inbound.impl.httpinboundlink.handlediscrimination(httpinboundlink.java:454)
at   com.ibm.ws.http.channel.inbound.impl.httpinboundlink.handlenewinformation(httpinboundlink.java:383)
at   com.ibm.ws.http.channel.inbound.impl.httpiclreadcallback.complete(httpiclreadcallback.java:102)
at   com.ibm.ws.tcp.channel.impl.aioreadcompletionlistener.futurecompleted(aioreadcompletionlistener.java:165)
at   com.ibm.io.async.abstractasyncfuture.invokecallback(abstractasyncfuture.java:217)
at   com.ibm.io.async.asyncchannelfuture.firecompletionactions(asyncchannelfuture.java:161)
at   com.ibm.io.async.asyncfuture.completed(asyncfuture.java:136)
at   com.ibm.io.async.resulthandler.complete(resulthandler.java:195)
at   com.ibm.io.async.resulthandler.runeventprocessingloop(resulthandler.java:743)
at   com.ibm.io.async.resulthandler$2.run(resulthandler.java:873)
at   com.ibm.ws.util.threadpool$worker.run(threadpool.java:1469)
,  


快速检索

最新资讯
热门点击