首页
学习
活动
专区
圈层
工具
发布
首页
学习
活动
专区
圈层
工具
MCP广场
社区首页 >问答首页 >JNDI NamingManager处理javax.naming.Reference对象时发生异常

JNDI NamingManager处理javax.naming.Reference对象时发生异常
EN

Stack Overflow用户
提问于 2016-12-28 16:16:57
回答 1查看 7.4K关注 0票数 1

我正在尝试从web sphere application server中的java代码连接db2。我正在关注exception.please在这方面的建议。

原因: JNDI NamingManager处理javax.naming.Reference对象时发生com.ibm.websphere.naming.CannotInstantiateObjectException:异常。

根异常是javax.xml.stream.FactoryConfigurationError:未能实例化提供程序类型: java.util.ServiceConfigurationError: javax.xml.stream.XMLInputFactory: Provider javax.xml.stream.XMLInputFactory不是子类型

在com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:1232)在com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:925)在com.ibm.ws.naming.jndicos.CNContextImpl.processBoundObjectForLookup(CNContextImpl.java:2877)在com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:3974)在com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1876)在com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(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.的CNContextImpl.java:1777)com.deere.u90.iaf.jdbc.connection.ConnectionManager.initializeEnvironment(ConnectionManager.java:276):428)在com.deere.u90.iaf.jdbc.connection.ConnectionManager.initializeEnvironment(ConnectionManager.java:276) ... 38更多原因:无法实例化: javax.xml.stream.FactoryConfigurationError: Provider javax.xml.stream.XMLInputFactory无法实例化: java.util.ServiceConfigurationError: javax.xml.stream.XMLInputFactory: Provider com.sun.xml.internal.stream.XMLInputFactoryImpl不是java源代码中的子类型)在java源代码中)在com.ibm.websphere中.product.metadata.im.IMMetadata.setHistoryEventsFromHistoryXml(IMMetadata.java:745)在com.ibm.websphere.product.metadata.im.IMMetadata.parseHistoryXmlFile(IMMetadata.java:587)在com.ibm.websphere.product.metadata.im.IMMetadata.parseInstallRegistryFiles(IMMetadata.java:399)在com.ibm.websphere.product.metadata.im.IMMetadata.(IMMetadata.java:269)在com.ibm.websphere.product.metadata.im.IMMetadata.getIMMetadataInstance(IMMetadata.java:133)在com.ibm.websphere.product.metadata.WASMetadatacom.ibm.websphere.product.metadata.WASMetadata.(WASMetadata.java:784) at com.ibm.websphere.product.metadata.WASMetadata.getWASMetadataInstance(WASMetadata.java:215) at com.ibm.websphere.product.WASDirectory.initMetadataInstance(WASDirectory.java:1415) at com.ibm.websphere.product.WASDirectory.getIMLogLocation(WASDirectory.java:435) at com.ibm.websphere.product.VersionInfo.printSource(VersionInfo.java:1534) at com.ibm.websphere.product.VersionInfo.printReport(的.parseMetadataFiles(WASMetadata.java:939)com.ibm.websphere.product.VersionInfo.runReport(VersionInfo.java:1064) at com.ibm.websphere.product.VersionInfo.runReport(VersionInfo.java:1025) at com.ibm.ws.rsadapter.spi.ServerFunction$7.run(ServerFunction.java:596) at com.ibm.ws.rsadapter.spi.ServerFunction$7.run(ServerFunction.java:590) at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118) at com.ibm.ws.rsadapter.spi.ServerFunction )。com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.(WSManagedConnectionFactoryImpl.java:748) at java.lang.J9VMInternals.newInstanceImpl(Native Method的getServerVersion(ServerFunction.java:588) ) at com.ibm.ejs.j2c.ConnectionFactoryBuilderServerImpl.createMCFandPM(ConnectionFactoryBuilderServerImpl.java:592) at com.ibm.ejs.j2c.ConnectionFactoryBuilderServerImpl.processObjectInstance(ConnectionFactoryBuilderServerImpl.java:1185) at com.ibm.ejs.j2c的java.lang.Class.newInstance(Class.java:1899).ServerFunction.processObjectInstance(ServerFunction.java:2009)在com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:662)在org.apache.aries.jndi.ObjectFactoryHelper.getObjectInstanceUsingObjectFactoryBuilders(ObjectFactoryHelper.java:349)在org.apache.aries.jndi.ObjectFactoryHelper.getObjectInstance(ObjectFactoryHelper.java:89)在org.apache.aries.jndi.OSGiObjectFactoryBuilder.getObjectInstance(OSGiObjectFactoryBuilder.java:62)在javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:311)在com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:1122) ... 50多

EN

回答 1

Stack Overflow用户

发布于 2018-05-16 18:57:13

我也面临着同样的问题,下面是我的解决方案:我在IBM管理控制台中错误地拼写了我的jta数据源,并且在我的persistence xml中使用了一个不同的名称,因此Websphere无法连接。请检查管理控制台中的[资源]选项卡,并验证持久性xml中声明的jta数据源名称

票数 0
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/41358008

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档