I don't know, but i my case it sure did. For eg. i noticed that every running process not properly terminated held 2 pool connections with my postgres database, one in either 'commit' or 'update' mode and the other in 'in transaction' status. Say, 3 services in running status, blocked 6 pool connections.
After restarting ofbiz, the pool connections would be released, but when ofbiz tried to run the same service again, it probably tries to complete the older tasks not properly closed. this further caused the database pool error. I am not aware in detail of how the pool connections are used by ofbiz. But after removing the services not properly closed from the jobsandox database, i witnessed significant change in performance in ofbiz. Rohit Scott Gray-2 wrote: > > On 13/01/2010, at 12:05 AM, Jacques Le Roux wrote: > >> From: "rohit" <rohitksur...@yahoo.com> >>> Hi, >>> >>> Please also check the jobsandbox database for any service not >>> properly >>> terminated, for eg. they are still in the running status. >>> >>> i had a lot of problem with us service not ending properly. even >>> with the >>> latest code running i have to manually delete some running process >>> on the >>> database. Each running process seems to block 1 - 2 pool connection >>> and >>> hence the error. currently for eg. the sendorderconfirmation email >>> gets >>> stuck as a running process for a long time. >> >> A Jira issue is pending for that >> https://issues.apache.org/jira/browse/OFBIZ-2974 > > I don't think that issue would be relevant to this discussion, a job > left in the running status after an improper shutdown won't have any > effect on database connections. > > Regards > Scott > >> >> Jacques >> >>> Hope it help. >>> >>> Rohit >>> >>> >>> Juan Pablo wrote: >>>> >>>> Hi Community. >>>> >>>> Today I had a lot of error messages when I execute some >>>> operations: Update >>>> Product, Facility Receipt, etc. >>>> >>>> This is one of the error messages: >>>> >>>> ------ >>>> >>>> Error en la llamada el evento: >>>> org.ofbiz.webapp.event.EventHandlerException: >>>> Service invocation error (Could not commit transaction for service >>>> [updateProduct] call: Roll back error, could not commit >>>> transaction, was >>>> rolled back instead because of: Failure in findByCondition >>>> operation for >>>> entity [ProductDimension]: >>>> org.ofbiz.entity.GenericDataSourceException: >>>> Unable to esablish a connection with the database. (Unable to >>>> acquire a >>>> new >>>> connection from the pool). Rolling back >>>> transaction.org.ofbiz.entity.GenericDataSourceException: Unable to >>>> esablish >>>> a connection with the database. (Unable to acquire a new >>>> connection from >>>> the >>>> pool) (Unable to esablish a connection with the database. (Unable to >>>> acquire >>>> a new connection from the pool))) >>>> >>>> ------ >>>> I understand that the main erro is "Unable to acquire a new >>>> connection >>>> from >>>> the pool" but I don´t understand how I can resolve. >>>> >>>> I use a local installation with a unique user! >>>> >>>> Thaks. >>>> >>>> -- >>>> Juan Pablo >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://n4.nabble.com/Unable-to-acquire-a-new-connection-from-the-pool-tp1012609p1012691.html >>> Sent from the OFBiz - User mailing list archive at Nabble.com. >> >> > > > > -- View this message in context: http://n4.nabble.com/Unable-to-acquire-a-new-connection-from-the-pool-tp1012609p1014491.html Sent from the OFBiz - User mailing list archive at Nabble.com.
