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 107697

Summary: Resource conflict on Glassfish when page uses 2 derby datasources
Product: serverplugins Reporter: Yousuf Haider <yousufh>
Component: Sun Appserver 9Assignee: Nitya Doraisamy <nityad>
Status: VERIFIED FIXED    
Severity: blocker CC: jbaker, jimdavidson
Priority: P2    
Version: 6.x   
Hardware: PC   
OS: Windows XP   
Issue Type: DEFECT Exception Reporter:
Bug Depends on:    
Bug Blocks: 111037    
Attachments: Server Output
sun-resources.xml

Description Yousuf Haider 2007-06-21 18:26:02 UTC 
Build:200706211330
JDk6.
Glassfish v2b50

Steps to reproduce:
1. Create new VWP project.
2. Drop a listbox on the page.
3. Bind the listbox to a table from Sample APP schema.
At this point a new JDBC resource is defined in sun-resources.xml which uses a connection pool 'derby_netpool' (also
newly defined).
4. Now bind the listobx to a table from the Sample Travel schema.
At this point another JDBC resource as well as another connection pool with the same name 'derby_netpool' but with
differing parameter values is defined.

This causes  2 connection pools with the same name to be defined. As a result deployment fails with this error:

"The resource derby_netPool at META-INF\sun-resources.xml is having a conflict with another resource defined within
archive."

I've atttached the server log and sun-resources.xml.

Workaround is to change pool name in the sun-resources.xml in the 2nd connection pool entry as well as in the second
jdbc resource definition.

I believe this would also happen for other databases as well.
Comment 1 Yousuf Haider 2007-06-21 18:26:29 UTC 
Created attachment 44210 [details]
Server Output
Comment 2 Yousuf Haider 2007-06-21 18:27:19 UTC 
Created attachment 44211 [details]
sun-resources.xml
Comment 3 _ jimdavidson 2007-07-23 23:24:35 UTC 
It looks like the problem is in ResourceConfigurator.createDataSource().

It checks whether the required pool already exists (which fails, because the database name is not the same), then
creates the pool with the same name.  I think it should either reuse the existing pool, or use a different name for the
new pool.
Comment 4 Nitya Doraisamy 2007-07-24 04:00:12 UTC 
The plugin should extend its check to the database name,user and password of the connection when attempting to create
a connection pool resource.
Comment 6 Yousuf Haider 2007-08-04 00:55:15 UTC 
Verified fix on build : 200708031200
Comment 7 John Baker 2007-08-21 19:32:44 UTC 
*** Issue 111520 has been marked as a duplicate of this issue. ***