Connection pooling won't really do anything for you because each stack is single threaded. You want object store coordinator pooling.
Sent from my iPhone
On Aug 26, 2010, at 8:45 PM, Dov Rosenberg <DRosenber..nquira.Com> wrote:
> During some testing today I turned on support for connection pooling in my application using the ERXJDBCAdaptor and the ERXJDBCConnectionBroker. I could see the connections being used fine and all of the things that did fetches seemed to work without any issues. However when I tried doing something that generated an INSERT the transactions did not commit and no changes were made. I could see the SQL being generated as expected and the saveChanges() happened without throwing any exception – just no data got written to the database. As soon as I disabled the use of the connection pool everything worked properly again.
>
> Any thoughts would be appreciated
>
> Dov Rosenberg
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (Webobjects-de..ists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/webobjects-dev/mschrag%40pobox.com
>
> This email sent to mschra..obox.com
This archive was generated by hypermail 2.0.0 : Fri Aug 27 2010 - 01:01:54 UTC