This content has been marked as final. Show 4 replies
Open a support case. Do you have pinned-to-thread turned on? Give them your
XML file that defines the datasource (config\jdbc\something.xml), and ask support
to put this exact text in the SR:
“Issue requires deep dive, so engage tech leads/ARE/BDE per standard process.
Upon which, if it requires SE assistance, it can be positioned appropriately”.
We do have pinned-to-thread turned on, does that have an impact on this? I'll open the ticket.
Yes, pinned-to-thread is documented to override your init-max settings because it must make
a connection per WebLogic execute-thread. If your application also spawns it's own threads
which get pool connections, you might have 800 threads (ugly), each with a connection.
It would indicate sub-optimal pool use too, which is best used by getting a connection, using it,
and closing it ASP, all within a single method call, so connections are not retained for long periods
by any thread.
It makes perfect sense. We unchecked the pinned-to-thread setting, restarted the server, and connection usage seems much more reasonable and predictable now.
Thanks a lot!