This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 178223 - The deployment of a J2EE 5.0 Appl. do not update the Glassfish 2.1.1 JNDI with JDBC resources
Summary: The deployment of a J2EE 5.0 Appl. do not update the Glassfish 2.1.1 JNDI wit...
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 normal (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-07 04:20 UTC by cistox
Modified: 2011-11-16 16:41 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description cistox 2009-12-07 04:20:47 UTC 
Using either Netbeans 6.7.1 and 6.8 RC2,
the deployment of a J2EE 5.0 Application into a Glassfish 2.1.1 server creates all JDBC Pools and Resources provided with sun-resources.xml but do not updates the JNDI.

Using the Glassfish Admin it is possible to check this situation using the JNDI browser that is not showing any JDBC resource under jdbc/ even if there are many pools and resources available.

The web.xml contains JDBC references that should provide the availability of java:comp/env/jdbc/... resources into JNDI

The sun-references.xml is at Application Server level and contains the mappings between the resource-ref in the web.xml and the actual resource/pool on the server.

Randomly I was able to see the JNDI updated but at every deployment or run the JNDI not consistent with available JDBC resources.

I'll appreciate any help.

Roberto
Comment 1 cistox 2009-12-07 10:00:20 UTC 
By applying manually:

asadmin add-resources C:\NetBeansProjects\CSIPortal\setup\sun-resources.xml

the JDBC connection pools and resources are registered correctly (apparently as before) and additionally the JNDI is correctly updated.

This confirm the Netbeans deployer is bugged for this part, but could be dependent of Glassfish 2.1.1
Comment 2 Petr Jiricka 2010-01-11 08:00:55 UTC 
Is this an issue with the GF plugin, or with the deployment infrastructure?
Comment 3 cistox 2010-03-22 18:34:26 UTC 
(In reply to comment #2)
> Is this an issue with the GF plugin, or with the deployment infrastructure?

If you deploy the Enterprise Application using netbeans, the sun-resources.xml are configure in the application server but the JNDI is not updated.... this means either the deployment infrastructure is not capable to connect and update a JNDI context or the GF plugin is not providing the necessary settings to allow the JNDI connection.
A reason could be the JNDI context is not initialised because the deployment process should be able to reach the jar META-INF of the Glassfish server containing the JNDI service settings (without this you should connect to JNDI manually)

hope this help

Roberto
Comment 4 Vince Kraemer 2010-03-23 21:10:03 UTC 
are you locale it_IT?
Comment 5 Vince Kraemer 2010-03-23 21:41:01 UTC 
started a thread on dev@glassfish... related to my investigation so far... (I think there is a bug in the admin layer, which would trickle up to the admin gui)
Comment 6 cistox 2010-03-24 15:18:42 UTC 
(In reply to comment #4)
> are you locale it_IT?

yes, but remember that I also experienced the same error for the default locale: English
Comment 7 Vince Kraemer 2010-03-24 16:23:38 UTC 
Thanks for the confirmation.
Comment 8 Vince Kraemer 2010-03-24 23:03:57 UTC 
It looks like this is really a bug in the asadmin command list-jndi-entries and the GF admin console. https://glassfish.dev.java.net/issues/show_bug.cgi?id=11726

This is a valid bug, entered in the invalid tracker... closing as invalid (now that the proper tracker has been updated)