NNTP-Posting-Date: Mon, 07 Jul 2003 14:45:44 -0500 Reply-To: "Charles" From: "Charles" Newsgroups: comp.lang.java.databases,comp.databases.oracle References: <999ced66.0306010651.78d56b2@posting.google.com> Subject: Re: Verify JDBC Connection Pooling Date: Mon, 7 Jul 2003 15:45:43 -0400 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Message-ID: Lines: 44 NNTP-Posting-Host: 68.39.32.125 X-Trace: sv3-qlYMLFMJ4YZIOTRRuWrtMH8u3sPNNqDwODFTzJC8VKgoAxr2MVQIoIPOUUSY8Rvuo2HGj/nGgcS+Q6x!1kfyTAgDV0okM6zrRN91ZMHj6fK76+wIsb3A2vpBy4ZmWbQR+lffEAdT8G/Q X-Complaints-To: abuse@comcast.net X-DMCA-Complaints-To: dmca@comcast.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.1 On AIX or UNIX platform, Oracle listener just sits at 1521 and reroute the incoming connections to avaiable ports/sockets. I think you need to 'tcpdump' the incoming packets from a defined list of clients. Charles "Sean" wrote in message news:999ced66.0306010651.78d56b2@posting.google.com... > 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.