Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Feedback

"...I always seem to find what I need in previous threads without starting my own. I have started a couple but that's it..."

Geography

Where in the world do Tek-Tips members come from?

Warning when doing JNDI lookup without "resource-ref"

solmyr72 (Programmer)
19 Dec 05 7:06
I need to do a JNDI lookup *without* using "resource-ref" :

CODE

Object dataSrouce= new InitialContext().lookup("jndi/myDataSource");
// I do *not* want to register a "resource-ref" and
// use  lookup("java:comp:/env/myDataSource")

Websphere, of course, issues the following well-known message :

CODE

[12/19/05 13:31:14:775 GMT+02:00] 1a258697 ConnectionFac I J2CA0122I: Resource reference myDataSource 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:        false (UNSHAREABLE)
    res-resolution-control:   999 (undefined)
[Other attributes]

I know the message can be avoided if you use "resource-ref", but unfortunately I have a good reason for avoiding "resource-ref" (it's a long story, involving a JNDI structure that's dynamic and not known in advance...  Anyway, please take my word for it - I have a reason to avoid "resource-ref"....)

Could anyone please offer another solution, that would still prevent WAS from issuing this message ? It is logged over and over again, completely cluttering my logs...

Thanx

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Back To Forum

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close