| tracing, connection pools, java programs [message #340657] |
Wed, 13 August 2008 12:32  |
eaganfox
Messages: 6
Registered: July 2008
Location: Minnesota
|
Junior Member |
|
|
I hope this is the right forum to post this as it is related to performance monitoring. However, the question involves understanding connection pools. We have a Java OLTP application that uses a connection pool, and for every action on the page, the Java programs connects to Oracle, execute the embedded SQL and close the connection (pretty much standard connection methods). However, I would like to set up tracing and more instrumentation for this application. What I am not clear about is where an Oracle session starts and ends. Does an Oracle session start with every Java "open connection" method and end with the "close connection" method or does the session remain as long as the connection pool exists (which is as long as the application is open or has not timed out). In other words, does the session id differ for each and every action performed or would it be one and the same as long as the connection pool established by this application remains available? I just need to know how many trace files I need to deal with. Thanks in advance.
[Updated on: Wed, 13 August 2008 12:34] Report message to a moderator |
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
