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 134913 - Even setting MaxWaitInMills and IdleTimeOut value to Null its taking default value
Summary: Even setting MaxWaitInMills and IdleTimeOut value to Null its taking default ...
Status: RESOLVED DUPLICATE of bug 134914
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: Sun Windows XP
: P3 blocker (vote)
Assignee: Nitya Doraisamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-13 06:39 UTC by dpkumar
Modified: 2008-07-15 05:16 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dpkumar 2008-05-13 06:39:50 UTC
NB Build:NetBeans IDE Build 200805030003
Appeserver Build
:glassfish-installer-v2.1-b31-windows(https://glassfish.dev.java.net/public/alldownloads.html#Promoted_binary_builds)

JDK Build :jdk1.5.0_13

Steps to reproduce:
1.Install NB and GF2.1
2.Start IDE and register GF2.1
3.Start GF2.1
4.Create web application (webapplication1)
5.Right click on the web application select New/Other/GF/JDBC Resource
6.Select create new JDBC Connection Pool select Next>Next>Next>Next.
7.Remove default values of "Max Wait Time" and "Idle Timeout" in the dialog window "Specify optional Properties for
Connection Pool" and select Finish
8.Right click on the web application select Build/Undeploy & Deploy
9.Right click on the deployed resource select Properties and check MaxWaitTimeInMillis and IdleTimeoutInSeconds
(server/GF2.1/Resources/JDBC/Connection pool)
10.Undeploy the application.Delete deployed resource.

Even after setting those value to null, It sets to default value.But I am able to set those values to null in the
properties of deployed resource(server/GF2.1/Resources/JDBC/Connection pool)
Comment 1 Nitya Doraisamy 2008-07-15 05:12:30 UTC
Cannot reproduce. Setting MaxWaitInMills and IdleTimeOut to null results in being over-ridden by the previous value.
The server log shows 
Validation error: [ADMVAL1043: Attribute(max-wait-time-in-millis=null) : null Invalid integer]
Validation error: [ADMVAL1043: Attribute(max-wait-time-in-millis=null) : null Invalid integer]

Comment 2 Nitya Doraisamy 2008-07-15 05:16:38 UTC
This is the same test as in IZ 134914. Closing this as duplicate.

*** This issue has been marked as a duplicate of 134914 ***