| ||ping-connection-pool - tests that a connection pool is usable
| ||ping-connection-pool --user admin_user [ --password admin_password ] [ --host localhost ] [ --port 4848 ] [ --secure|-s ] [ --passwordfile filename ] [ --terse=false ] [ --echo=false ] [ --interactive=true ] pool_name
Tests that a connection pool is usable for both JDBC connection pools and connector connection pools. For example, if you create a new JDBC connection pool for use with an application that is expected to be deployed, before deploying the application, the previously created pool is tested with this
This command is supported in remote mode only.
- authorized domain application server administrative username.
- password to administer the domain application server.
- machine name where the domain application server is running.
- port number of the domain application server listening for administration requests.
- if true, uses SSL/TLS to communicate with the domain application server.
- file containing the domain application server password.
- indicates that any output data must be very concise, typically avoiding human-friendly sentences and favoring well-formatted data for consumption by a script. Default is false.
- setting to true will echo the command line statement on the standard output. Default is false.
- if set to true (default), only the required password options are prompted.
- name of the connection pool to be tested.
| ||Example 1. Using ping-connection-pool
Before you can ping a connection pool, you must:
- Create a connection pool with authentication.
- Make sure the Enterprise Information Server (can be the database) is started.
asadmin> ping-connection-pool --user admin1 --password adminadmin1
--host pigeon --port 5001 sampleConnectionPool
Command ping-connection-pool executed successfully
- command executed successfully
- error in executing the command
Copyright 2003 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.