• 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:
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Al Hobbs
  • salvin francis

not able to get the connection in custom class

 
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Custom class is able to get the connection using thin driver but not from the websphere pool.

It is giving the Naming exception.How to set the classpath for the custom class in websphere 6.1.Web application is working fine with same datasource which is used for custom class.

can we get the connection from th pool in custom class using lookup method
 
Ranch Hand
Posts: 4864
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
A naming exception is quite often thrown simply because you tried to look up the DataSource by the wrong name. Make sure that the name you're using for the lookup is the same as the name you defined in the WebSphere Admin Console.
 
padmakar reddy kadem
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Using the same jndi name web application is able to get the connection from the pool.
But the custom class is not getting the connection.Here i am using the same jndi name what i used in web application.
the exception i am getting is

javax.naming.NameNotFoundException: Context: IFLMUD6DLGBLGNode01Cell/nodes/IFLMUD6DLGBLGNode01/servers/server1, name: orcads: First component in name orcads not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL mg.org/CosNaming/NamingContext/NotFound:1.0]
 
reply
    Bookmark Topic Watch Topic
  • New Topic