Very the JDBC Connection Pooling

By the theory, the connection pooling is a frame work for caches of database connections --- "Physically". Some of the connection have been "established", which can be verified from v$session, and others may be the open . These open connections in the pool are no way to be verified at the database level, because they have not been used for the database connections yet. How can I find/verify those have not been used the connections in the pool? Because they should be the "sockets" , can very find out at OS level. I used the following unix command, it gives all the established connections, but I want to find out not-yet connections:
 lsof -i TCP:1521.
If you or anyone could help to find out the open connections of jdbc at OS level, I will be very thankful.

As you might suggest to use 9iAS monitoring tools to find out the jdbc connection pooling infor, I used the OEM Website, it give very misleading results as such as
One time:
JDBC Usage:

Open JDBC Connections                    11,207
 Total JDBC Connections                    22,387
    Active Transactions                    0
   Transaction Commits                    0
  Transaction Rollbacks                    0

At a other time
JDBC Usage:

Open JDBC Connections                    0
 Total JDBC Connections                    0
    Active Transactions                    0
   Transaction Commits                    0
  Transaction Rollbacks                    0

We know the result were not correct/realistic. Received on Fri May 30 2003 - 10:47:15 CDT