Question on Best Practice for Database Connections

Ranch Hand

Posts: 96

posted 19 years ago

Number of slices to send:

Optional 'thank-you' note:

Send

Hi,

What is the best practice when utilizing a WebSphere connection pool? Currently, a application that I am working on, opens a connection when needed and passes the object to the Data Access Object which then closes the connection when it is finished with it. Would it be better to open ONE connection and store it in a session, that way all DAOs can access it whenever needed?

Thanks,
Lulu

Horatio Westock

Ranch Hand

Posts: 221

posted 19 years ago

Number of slices to send:

Optional 'thank-you' note:

Send

In general, get a connection only when you need it, then return it to the pool as soon as you are finished with it.

Rene Smith

Greenhorn

Posts: 21

posted 19 years ago

Number of slices to send:

Optional 'thank-you' note:

Send

I would not store the connection in a session. Depending on your site you probably do not want a connection hanging open that long

Ilja Preuss

author

Posts: 14112

posted 19 years ago

Number of slices to send:

Optional 'thank-you' note:

Send

Moving to JDBC...

The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus

Shailesh Chandra

Ranch Hand

Posts: 1087

I like...

posted 19 years ago

Number of slices to send:

Optional 'thank-you' note:

Send

I would suggest don't put connection in session. Create a datasource in websphere make connection from datasource when you need and close it as soon as you are done.

rest leave on websphere.

Gravitation cannot be held responsible for people falling in love ~ Albert Einstein

Consider Paul's rocket mass heater.