[GLASSFISH-3942] Provide a cluster-aware Database "Ping" feature Created: 24/Dec/07  Updated: 26/Apr/11

Status: Open
Project: glassfish
Component/s: jca
Affects Version/s: 9.1peur1
Fix Version/s: None

Type: Improvement Priority: Critical
Reporter: Alexis MP Assignee: Shalini
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 3,942
Status Whiteboard:

clusteradmin


 Description   

Database Ping works well with a single instance. In cluster mode, having the DAS
be able to ping the database doesn't mean all cluster instances can do it as
well (the JDBC driver may not be present or correctly loaded on each local
instance for instance).



 Comments   
Comment by km [ 13/Jan/08 ]

....

Comment by Tom Mueller [ 14/May/10 ]

Once the infrastructure work for dynamic configuration is done for 3.1, this
behavior should be implemented automatically. So this feature just needs to be
tested later during the release cycle.

The relevant subcommand is ping-connection-pool.

Comment by Tom Mueller [ 17/May/10 ]

Marking as referenced by the clustering admin one-pager.

Comment by Tom Mueller [ 25/Jan/11 ]

Clear the Fix version since this issue isn't going to be fixed for 3.1.

Generated at Wed May 27 01:44:22 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.