Logo 
Search:

Java Forum

Ask Question   UnAnswered
Home » Forum » Java       RSS Feeds

can anyone helpout the problem in starting an application

  Asked By: Jada    Date: Jan 26    Category: Java    Views: 1868
  

I am working on Websphere Administration Server V5.0. I have
installed Technology Samples Application on Server1 & Samples
Gallery on Cluster. When i try to start the Technology Samples
Application it shows the following error. Can anynoe help me out in
this problem.

ERROR:

[1/2/06 13:23:32:031 IST] 7ddf6859 EJBContainerI I WSVR0207I:
Preparing to start EJB jar: AddressBookEJB.jar
[1/2/06 13:23:32:391 IST] 7ddf6859 Helpers W NMSV0605W: A
Reference object looked up from the context "java:" with the
name "comp/env/WSsamples/TechSampDatasource" was sent to the JNDI
Naming Manager and an exception resulted. Reference data follows:
Reference Factory Class Name:
com.ibm.ws.util.ResRefJndiLookupObjectFactory
Reference Factory Class Location URLs: <null>
Reference Class Name: java.lang.Object
Type: ResRefJndiLookupInfo
Content: com.ibm.ws.util.ResRefJndiLookupInfo@59cee84d
ResRefJndiLookupInfo: Look up
Name="WSsamples/TechSampDatasource";JndiLookupInfo:
jndiName="WSsamples/TechSampDatasource"; providerURL="";
initialContextFactory=""

Exception data follows:
javax.naming.NameNotFoundException: Context:
ranjithNetwork/nodes/base/servers/SERVER1, name:
WSsamples/TechSampDatasource: First component in name
TechSampDatasource 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_in
fo(WsnOptimizedNamingImpl.java:968)
at
com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete
_info(WsnOptimizedNamingImplBase.java:1398)
at
com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info
(Unknown 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
(IndirectJndiLookupObjectFactory.java:372)
at com.ibm.ws.security.util.AccessController.doPrivileged
(AccessController.java:111)
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.jndicos.CNContextImpl.lookup
(CNContextImpl.java:1067)
at com.ibm.ws.naming.util.WsnInitCtx.lookup
(WsnInitCtx.java:132)
at javax.naming.InitialContext.lookup
(InitialContext.java:360)
at com.ibm.ws.cpi.JDBCPersisterFactoryImpl.create
(JDBCPersisterFactoryImpl.java:97)
at com.ibm.ejs.container.BeanMetaData.completeInitialization
(BeanMetaData.java:1247)
at
com.ibm.ws.runtime.component.EJBContainerImpl.createBeanMetaData
(EJBContainerImpl.java:981)
at
com.ibm.ws.runtime.component.EJBContainerImpl.createModuleMetaData
(EJBContainerImpl.java:796)
at
com.ibm.ws.runtime.component.EJBContainerImpl.createMetaData
(EJBContainerImpl.java:1517)
at
com.ibm.ws.runtime.component.MetaDataMgrImpl.createFactoryMetaData
(MetaDataMgrImpl.java:115)
at
com.ibm.ws.runtime.component.MetaDataMgrImpl.createMetaData
(MetaDataMgrImpl.java:159)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start
(DeployedModuleImpl.java:350)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start
(DeployedApplicationImpl.java:575)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication
(ApplicationMgrImpl.java:271)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start
(ApplicationMgrImpl.java:249)

Share: 

 

3 Answers Found

 
Answer #1    Answered By: Jackson Bouchard     Answered On: Jan 26

Make sure that server  names used in clusters are unique within the cell.

You should apply fixpack 1 to fix this problem  permanently.

 
Answer #2    Answered By: Isaac Williams     Answered On: Jan 26

I aplied fixpack 1 as u specfied, but my whole WAS failed to start,,, it shows  Server1 not found error...
can u suggest me what gone wrong with my WAS

 
Answer #3    Answered By: Luki Fischer     Answered On: Jan 26

If you still receive the following error:
Reference Factory Class Location URLs: <null>

means that the name space is not constructed correctly in certain servers in a cell
such that the server  name is used as a cluster  member and for some other server in the cell.

This causing a name not found exception. You should make sure that server names used in clusters are unique within the cell.

The problem  should be fixed by applying fixpack1. Otherwise, try to change the server name manually.

Be aware that if you map the DefaultApplication to the newly created server or deploy the DefaultApplication on the newly created server, the application  fails to start  if you do not select to use the existing server as a template when creating the new application server.

 
Didn't find what you were looking for? Find more on can anyone helpout the problem in starting an application Or get search suggestion and latest updates.




Tagged: