[GLASSFISH-18915] JDBC Resource lookup failed Created: 18/Jul/12  Updated: 13/Dec/12  Resolved: 13/Dec/12

Status: Resolved
Project: glassfish
Component/s: admin_gui
Affects Version/s:
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Vitaliy Kalayda Assignee: Anissa Lam
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified



When i create JDBC Connection Pool then JDBC Resource i can't see it in Server -> Resources and when i try to lookup
JDBC Resource:
InitialContext ic = new InitialContext();
DataSource dataSource = (DataSource) ic.lookup("jdbc/MyPool");
Connection connection = dataSource.getConnection();

i get exception

javax.naming.NamingException: Lookup failed for 'jdbc/MyPool' in SerialContext[myEnv=

{java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl, java.naming.factory.url.pkgs=com.sun.enterprise.naming}

[Root exception is javax.naming.NameNotFoundException: MyPool not found

Comment by Vitaliy Kalayda [ 18/Jul/12 ]

But when i add <resource-ref ref="jdbc/MyPool"></resource-ref> into domain config servers->server section all gone OK

Comment by Vitaliy Kalayda [ 26/Sep/12 ]

Looks like web administration panel is broken.
When i create JDBC Connection Pool from "asadmin" console all going fine.

Comment by Shalini [ 26/Sep/12 ]

Transferring to admin console team for investigation as per the reporter's comments.

Comment by Anissa Lam [ 26/Sep/12 ]

Is there any cluster created ? Can you give the steps on how to reproduce this in console ? thanks

Comment by Vitaliy Kalayda [ 26/Sep/12 ]

Without cluster.

Just create JDBC Connection Pool and JDBC Resource.

Comment by Vitaliy Kalayda [ 30/Nov/12 ]

I am sorry, looks like something is wrong with new postgresql jdbc driver
Because with old driver all working fine.

Thank You.

Comment by Anissa Lam [ 13/Dec/12 ]

Based on the reporter's comment, I am closing this bug invalid.
If this isn't the case, please reopen the bug and gives exact step to reproduce.

Generated at Tue Dec 01 22:41:27 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.