系统集成jndiWAS 8.5.5.9

WAS 8.5.5.9 JNDI报错

首先确认JNDI名称是正确的,在控制台测试连接是ok的。但是启动实例就会报错。[16-9-21 14:15:28:067 CST] 000000a1 WASSession    W DatabaseHashMap getConnection SESN0038E: 尝试获取与数据库的连接时出错。[16-9-21 14:15:28:066 CST] 000000bf WASSessionC...显示全部

首先确认JNDI名称是正确的,在控制台测试连接是ok的。但是启动实例就会报错。

[16-9-21 14:15:28:067 CST] 000000a1 WASSession    W DatabaseHashMap getConnection SESN0038E: 尝试获取与数据库的连接时出错。

[16-9-21 14:15:28:066 CST] 000000bf WASSessionCor E DatabaseHashMap getDataSource 异常为:

                                 javax.naming.NameNotFoundException: Context: SR12Cell01/clusters/ERP, name: jdbc/Sessions: First component in name Sessions not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]

at com.ibm.ws.naming.jndicos.CNContextImpl.mapNotFoundException(CNContextImpl.java:4564)

at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1822)

at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1777)

at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1434)

at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:616)

at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:165)

at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)

at org.apache.aries.jndi.DelegateContext.lookup(DelegateContext.java:161)

at javax.naming.InitialContext.lookup(InitialContext.java:423)

at com.ibm.ws.session.store.db.DatabaseHashMap.getDataSource(DatabaseHashMap.java:657)

at com.ibm.ws.session.store.db.DatabaseHashMap.getConnection(DatabaseHashMap.java:1160)

at com.ibm.ws.session.store.db.DatabaseHashMap.performInvalidation(DatabaseHashMap.java:2761)

at com.ibm.ws.session.store.common.BackedStore.runInvalidation(BackedStore.java:133)

at com.ibm.ws.session.WsSessionInvalidatorWithThreadPool$InvalidationTask.run(WsSessionInvalidatorWithThreadPool.java:87)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:483)

at java.util.concurrent.FutureTask.run(FutureTask.java:274)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:190)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627)

at java.lang.Thread.run(Thread.java:801)

Caused by: org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0

at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.do_resolve_complete_info(WsnOptimizedNamingImpl.java:590)

at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info(WsnOptimizedNamingImplBase.java:2216)

at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(_NamingContextStub.java:538)

at com.ibm.ws.naming.jndicos.CNContextImpl$2.run(CNContextImpl.java:2958)

at com.ibm.ws.naming.jndicos.CNContextImpl$2.run(CNContextImpl.java:2954)

at com.ibm.ws.naming.util.CommonHelpers.retry(CommonHelpers.java:871)

at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:2952)

at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1818)

... 19 more

收起
参与2

返回bean001的回答

bean001bean001系统工程师金恒科技

我集群实例中“Middleware servers > SR01 > Session management > Distributed environment settings > Database settings” 中 “

                                Datasource JNDI name” 的会话数据库未调整成正确的,采用的是系统自带的配置,即为上述错误中的 jdbc/Sessions。将此默认jdbc/Sessions修改正确后,重启集群问题解决了。

系统集成 · 2016-09-22
浏览2611

回答者

bean001
系统工程师金恒科技
擅长领域: 中间件服务器WAS

bean001 最近回答过的问题

回答状态

  • 发布时间:2016-09-22
  • 关注会员:1 人
  • 回答浏览:2611
  • X社区推广