EOF Connection Pooling?
EOF Connection Pooling?
- Subject: EOF Connection Pooling?
- From: Dov Rosenberg <email@hidden>
- Date: Tue, 22 Nov 2005 10:15:25 -0500
- Thread-topic: EOF Connection Pooling?
Title: EOF Connection Pooling?
Is there any way to convince EOF to use a database connection pool? I noticed that there appears to be some JNDI lookup for a datasource but I could not get it to use a Tomcat connection pool. It looks like there needs to be something set up in the EOModel but could not come up with the correct combination of chicken blood and ritual sacrifice to get it to work properly.
My primary motivation is that our apps are deployed as servlets which makes it harder to run multiple instances of an app in the same container like JavaMonitor enables when you run as a regular WO application. The only way we can get multiple db connections seems to start multiple instances on different machines or run multiple servlet containers on the same box.
I saw some references to EOF and multiple connection stacks that looked promising but very complex. Has anyone done this, if so are there any rules that we should follow.
We have 2 apps. One is a regular WO app deployed as a servlet the other is a little different. It uses a sharededitingcontext for performance caching. We may be changing that in the future, but I am a little concerned with dealing with multiple EOF stacks while using a SharedEditingContext
--
Dov Rosenberg
Conviveon/Inquira
Knowledge Management Experts
http://www.conviveon.com
http://www.inquira.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden