我創(chuàng)建了一個(gè)簡(jiǎn)單的CMP，是基于數(shù)據(jù)庫(kù)中的一個(gè)表的。
創(chuàng)建過(guò)程和部署過(guò)程都很正常，但我在向應(yīng)用服務(wù)器（WebSphere）發(fā)布時(shí)卻出現(xiàn)以下報(bào)錯(cuò)：
[06-4-27 11:59:52:531 CST] 3e725b31 Helpers?????? W NMSV0605W: 使用名稱(chēng)“
comp/PM/WebSphereCMPConnectionFactory”從上下文“java:”中查找的引用對(duì)象發(fā)送到
JNDI 命名管理器并且導(dǎo)致異常。引用數(shù)據(jù)如下：
引用工廠(chǎng)類(lèi)名：com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory
引用工廠(chǎng)類(lèi)位置 URL：<null>
Reference Class Name: java.lang.Object
Type: JndiLookupInfo
Content: JndiLookupInfo: jndiName="jdbc/Default"; providerURL="";
initialContextFactory=""
異常數(shù)據(jù)如下：
javax.naming.NameNotFoundException: Context:
localhost/nodes/localhost/servers/server1, name: jdbc/Default: First
component in name Default 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.do_resolve_complete_info(Ws
nOptimizedNamingImpl.java:968)
?at
com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info
(WsnOptimizedNamingImplBase.java:1399)
?at
com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(Unknow
n Source)
?at
com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:3491
)
?at
com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1519)
?at
com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1480)
?at
com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1187)
?at
com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiL
ookupObjectFactory.java:372)
?at
com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.ja
va:111)
?at
com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstanceEx
t(IndirectJndiLookupObjectFactory.java:221)
?at
com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers
.java:868)
?at
com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(Url
ContextHelper.java:152)
?at
com.ibm.ws.naming.java.javaURLContextRoot.processBoundObjectForLookup(java
URLContextRoot.java:398)
?at
com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1278)
?at
com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:1
96)
?at
com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:1
37)
?at javax.naming.InitialContext.lookup(InitialContext.java:360)
?at
com.ibm.ws.ejbpersistence.beanextensions.ConcreteBeanClassExtensionImpl.lo
okup(Unknown Source)
?at
com.ibm.ws.ejbpersistence.beanextensions.ConcreteBeanClassExtensionImpl.ge
tConnectionFactory(Unknown Source)
?at
com.ibm.ws.ejbpersistence.beanextensions.PMModuleCookieImpl.beanInstall(Un
known Source)
?at
com.ibm.ws.ejbpersistence.beanextensions.PersistenceManagerImpl.beanInstal
l(Unknown Source)
?at
com.ibm.ejs.container.EJSContainer.loadBeanMetaData(EJSContainer.java:1367
)
?at
com.ibm.ejs.container.EJSContainer.getHomeWrapperCommon(EJSContainer.java:
1012)
?at
com.ibm.ejs.container.EJSContainer.getHomeInstance(EJSContainer.java:934)
?at
com.ibm.ejs.container.EJSContainer.startBean(EJSContainer.java:913)
?at
com.ibm.ws.runtime.component.EJBContainerImpl.startBean(EJBContainerImpl.j
ava:1301)
?at
com.ibm.ws.runtime.component.EJBContainerImpl.install(EJBContainerImpl.jav
a:1034)
?at
com.ibm.ws.runtime.component.EJBContainerImpl.start(EJBContainerImpl.java:
1508)
?at
com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.j
ava:505)
?at
com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectSta
rt(DeployedApplicationImpl.java:808)
?at
com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.j
ava:354)
?at
com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplica
tionImpl.java:578)
?at
com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(Applicati
onMgrImpl.java:299)
?at
com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.j
ava:256)
?at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.j
ava:536)
?at
com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
?at
com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServer
Impl.java:128)
?at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.j
ava:536)
?at
com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
?at
com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
?at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
?at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
?at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
?at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
79)
?at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
pl.java:41)
?at java.lang.reflect.Method.invoke(Method.java:386)
?at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:105)
?at
com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunne
rV5.java:97)
從報(bào)錯(cuò)信息中看出好像是CMP的連接初始化工廠(chǎng)配置有問(wèn)題。由于我剛上手使用Eclipse +
WebSphere（以前使用的是Jbuilder + Weblogic），但我有一個(gè)疑問(wèn)：
在部署成功后發(fā)布時(shí)怎么會(huì)出現(xiàn)初始化工廠(chǎng)的問(wèn)題呢？我還沒(méi)有調(diào)用這個(gè)CMP啊？只是發(fā)布到
WebSphere而已（相當(dāng)于發(fā)布到Weblogic應(yīng)用服務(wù)器），為什么會(huì)初始化環(huán)境工廠(chǎng)呢？以我的
經(jīng)驗(yàn)只有在發(fā)布成功后，客戶(hù)端調(diào)用CMP時(shí)才會(huì)涉及到這個(gè)問(wèn)題吧！
我實(shí)在弄不明白。難道這兩個(gè)應(yīng)用服務(wù)期在這一點(diǎn)上有區(qū)別？
另外，如果發(fā)布時(shí)進(jìn)行初始化環(huán)境工廠(chǎng)，那我創(chuàng)建的SessionBean為什么就沒(méi)有這個(gè)問(wèn)題，部署
發(fā)布都很正常，不知道為什么？
問(wèn)題困擾我很久了。期望解決方案！