JDBC issue with JNDI lookup

Hello, I was hoping someone might have run into something like this. I am porting an existing Weblogic application to WAS5.1. In the Weblogic application, datasources are referred to by their JNDI names. My application is working in WAS, but I get this info message: **************************** [1/9/04 16:01:04:505 EST] 4a84ce88 ConnectionFac I J2CA0122I: Resource reference NCRCRMDB could not be located, so default values of the following are used: [Resource-ref settings] res-auth: 1 (APPLICATION) res-isolation-level: 0 (TRANSACTION_NONE) res-sharing-scope: true (SHAREABLE) res-resolution-control: 999 (undefined) [Other attributes] isCMP1_x: false (not CMP1.x) isJMS: false (not JMS)

**************************** I found on an IBM pub site that this means that since I am referencing the datasource via JNDI directly the container can't manage these values, so it sets defaults. Has anyone seen something similar, and if so, have you been able to solve it? It's my impression that this is akin to a warning since the code works, but the log is getting filled with these. Thanks, Eric McEntee

Go to EJB Deployment Descriptor, click on references tab, Click on Add button at the bottom, select Resource reference radio button. Name = (New ResourceRef) - replace this with the jndi name you gave in ur program. For example if you gave java:comp/env/jdbc/testds, type jdbc/typeds. Type = javax.sql.DataSource (Make sure you havent selected javax.activation.DataSource) Autentication: CONTAINER Under Websphere Bindings jndiname - name you gave while created your datasource (ie jdbc/typeds) Save everything and Restart your server.

eric mcentee
Ranch Hand

Joined: May 02, 2001
Posts: 66

posted Jan 12, 2004 11:36:00

0

Sorry, excuse my ignorance, I'm a WAS newbie. Where do I find this EJB Deployment Descriptor menu? Is this through the admin console, or WSAD? Thanks, Eric

chandubcs
Ranch Hand

Joined: Jun 03, 2001
Posts: 47

posted Jan 12, 2004 12:56:00

0

Its using WSAD, If you want the same be done in WAS also using different approach.