您的位置:程序门 -> websphere ->



请教高人关于websphere启动的时候出现的错误如何解决!


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


请教高人关于websphere启动的时候出现的错误如何解决!
发表于:2007-09-20 16:01:03 楼主

启动server1的时候出现的错误。最后server1是可以起来的,但是时间很长,侦听器端口   bpeapilistenerport   将尝试在   60   秒内重新启动,会出现个5-6次。而且我的was上未启动jms和mq。
请教如何处理,或者说如何设置!
再此十分感谢1!

07-9-20   15:30:03:080   gmt+08:00]   7cf8da6b   mdblistenerim   w   wmsg0017e:   无法查找   jms   资源,jndi   查找异常:idl:omg.org/cosnaming/namingcontext/notfound:1.0
[07-9-20   15:30:03:118   gmt+08:00]   73f25a6b   mdblistenerim   w   wmsg0017e:   无法查找   jms   资源,jndi   查找异常:idl:omg.org/cosnaming/namingcontext/notfound:1.0
[07-9-20   15:30:03:147   gmt+08:00]   7cf8da6b   mdblistenerim   w   wmsg0019e:   无法启动   mdb   侦听器   generic   process   choreographer   jms   api,jmsdestination   jms/bpeapiqueue:javax.naming.namenotfoundexception:   context:   npg520d/nodes/npg520d/servers/server1,   name:   jms/bpeapiqueue:   first   component   in   name   jms/bpeapiqueue   not   found.     root   exception   is   org.omg.cosnaming.namingcontextpackage.notfound:   idl:omg.org/cosnaming/namingcontext/notfound:1.0
at   com.ibm.ws.naming.ipcos.wsnoptimizednamingimpl.handlenamenotfound(wsnoptimizednamingimpl.java:1983)
at   com.ibm.ws.naming.ipcos.wsnoptimizednamingimpl.getnextwsnoptimizednamingcontext(wsnoptimizednamingimpl.java:1320)
at   com.ibm.ws.naming.cosbase.wsnoptimizednamingimplbase.gettargetcontext(wsnoptimizednamingimplbase.java:2500)
at   com.ibm.ws.naming.cosbase.wsnoptimizednamingimplbase$leafoperationdata. <init> (wsnoptimizednamingimplbase.java:2965)
at   com.ibm.ws.naming.cosbase.wsnoptimizednamingimplbase.resolve_complete_info(wsnoptimizednamingimplbase.java:1423)
at   com.ibm.wsnoptimizednaming._namingcontextstub.resolve_complete_info(unknown   source)
at   com.ibm.ws.naming.jndicos.cncontextimpl.cosresolve(cncontextimpl.java:3493)
at   com.ibm.ws.naming.jndicos.cncontextimpl.dolookup(cncontextimpl.java:1521)
at   com.ibm.ws.naming.jndicos.cncontextimpl.dolookup(cncontextimpl.java:1482)
at   com.ibm.ws.naming.jndicos.cncontextimpl.lookupext(cncontextimpl.java:1189)
at   com.ibm.ws.naming.jndicos.cncontextimpl.lookup(cncontextimpl.java:1069)
at   com.ibm.ws.naming.util.wsninitctx.lookup(wsninitctx.java:145)
at   javax.naming.initialcontext.lookup(initialcontext.java:361)
at   com.ibm.ejs.jms.listener.mdblistenerimpl.createresources(mdblistenerimpl.java:234)
at   com.ibm.ejs.jms.listener.mdblistenerimpl.internalstart(mdblistenerimpl.java:611)
at   com.ibm.ejs.jms.listener.mdblistenerimpl.restart(mdblistenerimpl.java:585)
at   com.ibm.ejs.jms.listener.mdblistenerimpl.alarm(mdblistenerimpl.java:930)
at   com.ibm.ejs.util.am._alarm.run(_alarm.java:80)
at   com.ibm.ws.util.threadpool$worker.run(threadpool.java:936)

[07-9-20   15:30:03:267   gmt+08:00]   7cf8da6b   mdblistenerim   i   wmsg0043i:   已为   jmsdestination   jms/bpeapiqueue   停止   mdb   侦听器   bpeapilistenerport
[07-9-20   15:30:03:267   gmt+08:00]   7cf8da6b   mdblistenerim   i   wmsg0058i:   侦听器端口   bpeapilistenerport   将尝试在   60   秒内重新启动
[07-9-20   15:30:03:183   gmt+08:00]   73f25a6b   mdblistenerim   w   wmsg0019e:   无法启动   mdb   侦听器   processcontainer   mdb,jmsdestination   jms/bpeintqueue:javax.naming.namenotfoundexception:   context:   npg520d/nodes/npg520d/servers/server1,   name:   jms/bpeintqueue:   first   component   in   name   jms/bpeintqueue   not   found.     root   exception   is   org.omg.cosnaming.namingcontextpackage.notfound:   idl:omg.org/cosnaming/namingcontext/notfound:1.0
at   com.ibm.ws.naming.ipcos.wsnoptimizednamingimpl.handlenamenotfound(wsnoptimizednamingimpl.java:1983)
at   com.ibm.ws.naming.ipcos.wsnoptimizednamingimpl.getnextwsnoptimizednamingcontext(wsnoptimizednamingimpl.java:1320)
at   com.ibm.ws.naming.cosbase.wsnoptimizednamingimplbase.gettargetcontext(wsnoptimizednamingimplbase.java:2500)
at   com.ibm.ws.naming.cosbase.wsnoptimizednamingimplbase$leafoperationdata. <init> (wsnoptimizednamingimplbase.java:2965)
at   com.ibm.ws.naming.cosbase.wsnoptimizednamingimplbase.resolve_complete_info(wsnoptimizednamingimplbase.java:1423)
at   com.ibm.wsnoptimizednaming._namingcontextstub.resolve_complete_info(unknown   source)
at   com.ibm.ws.naming.jndicos.cncontextimpl.cosresolve(cncontextimpl.java:3493)
at   com.ibm.ws.naming.jndicos.cncontextimpl.dolookup(cncontextimpl.java:1521)
at   com.ibm.ws.naming.jndicos.cncontextimpl.dolookup(cncontextimpl.java:1482)
at   com.ibm.ws.naming.jndicos.cncontextimpl.lookupext(cncontextimpl.java:1189)
at   com.ibm.ws.naming.jndicos.cncontextimpl.lookup(cncontextimpl.java:1069)
at   com.ibm.ws.naming.util.wsninitctx.lookup(wsninitctx.java:145)
at   javax.naming.initialcontext.lookup(initialcontext.java:361)
at   com.ibm.ejs.jms.listener.mdblistenerimpl.createresources(mdblistenerimpl.java:234)
at   com.ibm.ejs.jms.listener.mdblistenerimpl.internalstart(mdblistenerimpl.java:611)
at   com.ibm.ejs.jms.listener.mdblistenerimpl.restart(mdblistenerimpl.java:585)
at   com.ibm.ejs.jms.listener.mdblistenerimpl.alarm(mdblistenerimpl.java:930)
at   com.ibm.ejs.util.am._alarm.run(_alarm.java:80)
at   com.ibm.ws.util.threadpool$worker.run(threadpool.java:936)
发表于:2007-10-06 19:20:401楼 得分:0
估计跟配置有关,检查一下是否配置正确
发表于:2007-10-07 17:16:512楼 得分:0
把你没有用的企业应用ear卸载掉,这样启动快一点


快速检索

最新资讯
热门点击