• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Problem with EJB test client , JNDI look up

 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am using WASAD 5.0 , When I try to test my EJB using the IBM Universal Test Client , the JNDI look up is unable to locate my Bean. I get the following message :

IWAD0402E Could not perform lookup with the JNDI name:


What could be the problem , I have been struggling with this for the last two days. Where to start looking for the issue? Can someone advice please? thanks
 
author & internet detective
Posts: 41860
908
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Sami,
Are there any errors, starting up the server? Do you see anything when you navigate through the tree of available JNDI objects?

And welcome to JavaRanch!
[ September 20, 2004: Message edited by: Jeanne Boyarsky ]
 
Sami Amour
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks Jeanne for welcoming me. Well the server starts fine but since you mention the server console , I went back to see if any error happen before the message that showing the success start and yes I found the follwoing:

I see the following in the Server Console:


EJBContainerI E WSVR0042E: Unable to stop WBOnlineEAR#WBOnlineEJB.jar#Txn: unknown bean home name - WBOnlineEAR#WBOnlineEJB.jar#Txn
EJBContainerI E WSVR0043E: Unbind failed for WBOnlineEAR#WBOnlineEJB.jar#Txn: Name ejb not found in context "local:ejb".
EJBContainerI E WSVR0044E: Unable to stop EJB jar, WBOnlineEJB.jar: PM Module Post Uninstall Failed: - java.lang.NullPointerException
DeployedAppli W WSVR0206E: Module, WBOnlineEJB.jar, of application, WBOnlineEAR.ear/deployments/WBOnlineEAR, failed to start
ApplicationMg W WSVR0101W: An error occurred starting, WBOnlineEAR
ApplicationMg A WSVR0217I: Stopping application: WBOnlineEAR
ApplicationMg A WSVR0220I: Application stopped: WBOnlineEAR
HttpTransport A SRVE0171I: Transport http is listening on port 9,080.
HttpTransport A SRVE0171I: Transport https is listening on port 9,443.
RMIConnectorC A ADMC0026I: RMI Connector available at port 2809
WsServer A WSVR0001I: Server server1 open for e-business

but the first error at the top of the console :
ConnectionFac E J2CA0036E: An exception occurred while invoking method setDataSourceProperties on com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used by resource jdbc/salim : java.lang.reflect.InvocationTargetException: com.ibm.ws.exception.WsException: DSRA0023E: The DataSource implementation class "COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource" could not be found.
at java.lang.Throwable.<init>(Throwable.java)



that was in the console but in the JNDI exploere I get the follwoing :

ejb
com
wbonline
ejbs
Context has no contents


I am not sure if I missed somthing as far as JNDI ,,, like setting a classpath or somthing . Let me know if you see the issue. Thanks again
[ September 20, 2004: Message edited by: Sami Amour ]
 
Jeanne Boyarsky
author & internet detective
Posts: 41860
908
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
As you pointed out, WSAD is having trouble finding db2. That is undoubtedly the cause of your error.

In the server perspective, go to where the drivers are defined (datasource tab, first section.) Edit the driver you are using and check that the path corresponds to where you have db2 installed.
 
Sami Amour
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Jeanne , thanks for the reply but I found the issue which was the classpath. I had classes111.zip instead of classes12.zip in my path

I changed it and everything worked fine.

thanks
 
You had your fun. Now it's time to go to jail. Thanks for your help tiny ad.
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic