Re: Database pools in Shark 1.0

Monique Maker <[email protected]>
Newsgroups gmane.comp.java.enhydra.shark
Message-ID <[email protected]>
Hello David,

There should be some connection pool in the DODS (to be honest, we looked at the sources of latest DODS version, so I am not 100% sure, the pools are in the DODS that is comming with Shark 1.0). To be honest, it is not realised very good.

You can use data sources (if your application is running in an application server) only in the latest Shark version (1.1-2).

If you want to make you own pool you will need to change the DODS. We we had similar problems and intentions but we gave up at the perspective to fix DODS and decided to live with all flaws of Shark database connection realisation - it seems you will need to rewrite about 70% of Shark and almost all DODS. Sorry for the bad news.

I would avise you to make your best to migrate to Shark version 1.1-2. We are also in production and we know how difficult can be such decision.

Best Regards,
Monique

David Simón wrote:
> Hi all,
> 
> Does anybody know if it is possible to configure a database pool in 
> Shark 1.0? I have changed recently from Hypersonic to Oracle and I would 
> like to use a pool to increase the performance of connections. The best 
> solution would be getting the pool through "jndi" but i am not sure if 
> this is possible in Shark 1.0 with the DODs implementation that it comes 
> with. So if jndi access is not possible I would like to configure a pool 
> directly in Shark at least.
> 
> 
> Best regards,
> 
> David.
message-footer.txt (text/plain, 271 B)
--
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.