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 57345 - REGRESSION: empty database password cause server resource registration failure
Summary: REGRESSION: empty database password cause server resource registration failure
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Nitya Doraisamy
URL:
Keywords:
: 65179 (view as bug list)
Depends on: 68758
Blocks:
  Show dependency tree
 
Reported: 2005-04-01 15:46 UTC by Daria Titova
Modified: 2006-04-06 05:56 UTC (History)
0 users

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 Daria Titova 2005-04-01 15:46:52 UTC 
Step to reproduce:
- establish JDBC connection to database with empty password;
- create CMP Entity Bean from established JDBC connection;
Note, generated connection pool resource has 3 Extra Properties, one of them
named Password and has empty value.
- try to registered this connection pool resource;
Registration fail saying that Password property can not be deleted.
Comment 1 _ ludo 2005-04-01 17:11:47 UTC 
Not sure first this is a regression or a bug...
Nitya, test via Admin GUI to see the beahviour....
If this is a backend constraint to requires a psswd, then it;s not a bug, but a
feature.
Also, this is not a P3, as the workaround is to add the password, as notified in
the error message.
Comment 2 Nitya Doraisamy 2005-04-01 18:21:47 UTC 
This issue is a bug in resource creation through the ejb wizards and
UseDatabaseAction calls in the project. The error is not because of empty
password, the extra properties are name value pairs. The server will complain if
there is an empty value is passed for any of the pairs.

Resource Creation in wizards does not cause this since appropriate checks are in
place to ensure there are valid values.
Comment 3 Nam Nguyen 2005-04-03 19:21:24 UTC 
Nitya, I am a bit confused.  Could you confirm my understanding: even if the
database allow user with empty password, it is impossible to have a AS81
connection pool with such user?

Anyway, agree with Ludo, this does not consist of a show-stopper.
Comment 4 Nitya Doraisamy 2005-11-02 22:14:26 UTC 
*** Issue 65179 has been marked as a duplicate of this issue. ***
Comment 5 _ ludo 2005-11-11 03:09:25 UTC 
Nitya: we absolutely need to know why the password can be null in some cases.
Maybe this will imply a change in the db explorer module, but we need to fix this.
I was in a lab today and many students got this issue. It was hard to detect...
Comment 6 Nitya Doraisamy 2005-11-23 23:19:57 UTC 
Password being null in some cases was due to issue 68758. This issue has been fixed.
This issue will not pop as frequently now. But plugin should handle case where
it might receive a resource with null/empty user/password value.  
The server will not accept a name value pair with null/empty value. The plugin
should either strip such invalid pairs from it's resource before attempting to
register and inform the user of this action or ask for user input.
Comment 7 Jaroslav Pospisil 2006-03-13 13:49:31 UTC 
TM 5.0->TBD
Comment 8 Nitya Doraisamy 2006-04-06 05:56:10 UTC 
Plugin strips invalid pairs from it's resource before registering the resource
to the server.