Re: BEA and Java Connection Pooling
- From: Richard Ji <richard.c.ji@xxxxxxxxx>
- To: MFontana@xxxxxxxxx
- Date: Wed, 19 Oct 2005 11:39:45 -0400
Database problem, yeah right. It's a network problem, LOL.
If the application employees a connection pool, in this case
BEA, then it's the application responsibility to manage the pool
of connections. When a network problem causes the connection
to DB killed, then the application show detect that and reinitiate
connections. Depends on how the application tests connections.
A simple test of whether the object is NULL or not, or test the
Connection.close() method isn't sufficient. They need to test
it by either submit a query to db or catch specific SQLException
that are related to ORA-3113 or the likes.
Richard Ji
On 10/19/05, Michael Fontana <MFontana@xxxxxxxxx> wrote:
>
>
> 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
>
Other related posts:
