we used the PoolingJDBCContext from wocode http://wocode.com/cgi-bin/WebObjects/WOCode.woa/1/wa/ShareCodeItem?itemId=330 with is based on the commons pooling from jakarta. the reason behind the switch was that we needed a seperate EOObjectStoreCoordinator for each user and we run quickly out of database connections ;-)
hope that helps, oliver >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. _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
