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 134653 - idle-timeout-in-seconds valid range for this value is from 1 to 2147483638
Summary: idle-timeout-in-seconds valid range for this value is from 1 to 2147483638
Status: RESOLVED WONTFIX
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-07 11:10 UTC by dpkumar
Modified: 2008-12-12 18:40 UTC (History)
1 user (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 dpkumar 2008-05-07 11:10:12 UTC 
NetBeans Build:NB dev (200805030003)
Appserver 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 glassfish-installer-v2.1.
2.Start IDE.
3.Right click on the server node select GlassFish V2 and give platform location for the installed GlassFish V2.1 and
start the server.
3.Create a web application.
4.Right click on the web application, select New/other/GlassFish/JMS Resource.
5.Create different JMS resource of type(Queue,Topic,QueueConnectionFactory,TopicConnectionFactory and ConnectionFactory)
6.Right click on the web application select Undeploy&Deploy
7.Right click on the deployed JMS resource and select properties/IdleTimeOutInSeconds(Select Server/GlassFish
V2/Resource/JMS Resource/ConnectionFactory/)

Actual range of IdleTimeOutInSeconds specified is 1 to 2147483638
It accepts,If we give range above than the actual range(ex:2147483647)
Comment 1 Nitya Doraisamy 2008-07-15 05:23:41 UTC 
The server accepts a value greater than 2147483638. Could you confirm that this is the limit of the valid range and if
so file an issue against the server instead.
Comment 2 Vince Kraemer 2008-09-09 17:23:41 UTC 
what is the status of this?
Comment 3 dpkumar 2008-12-12 06:00:06 UTC 
Filed an issue against server: https://glassfish.dev.java.net/issues/show_bug.cgi?id=6914
Comment 4 Nitya Doraisamy 2008-12-12 18:40:40 UTC 
Server issue. Closing as wontfix