RE: BEA and Java Connection Pooling
- To: <MFontana@xxxxxxxxx>, "Oracle-L" <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 19 Oct 2005 11:41:22 -0400
Michael,
This is a common practice with a lot of third party
applications. And NO it is not a database problem, but an error
handling problem with the application server. We're using Weblogic (more
appropriately named Webillogic around here) and it does perform as you
suggest. Also BEA simply states that it is the users responsibility to
maintain reliable communications between the app server and database.
Specifically they do not recommend having a firewall between the app
server and database. Nor do they recommend having one between the user
and the app server, but at least they'll try to help you there.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Fontana
Sent: Wednesday, October 19, 2005 11:28 AM
To: Oracle-L
Subject: BEA and Java Connection Pooling
Has anyone had experience with BEA weblogic and powerportal creating
large amounts of oracle connections (connection pooling is what they
call it)?
This is certainly fine as long as oracle process and session parameters
are set with a size to support them. However, we have seen, when
changes or outages to the network/firewall occur (and they often do, due
to routine maintenance as well as unplanned disruptions), that while
these connections persist, they no longer successfully query databases.
This is, of course, as I am told by our development management, a
"DATABASE PROBLEM". Given that Oracle has similar methods to accomplish
the same things as the java connection pools are supposed to, does
anyone have any suggestions/experience/advice about the use of these
techniques?
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
