The frustrating part is that we are not able to reproduce any of the errors our client is getting in-house.
Our clients are running on Java 1.7, Windows Server 2008R2 running on a Virtual Server.
Any help would be appreciated. Thanks.]]>Chad Curtis2012-07-10T20:13:57-00:00Re: EclipseLink + Foxprohttps://www.eclipse.org/forums/index.php/mv/msg/367282/899625/#msg_899625
What is different between your clients setup, and your own, are you using the same Foxpro version and ODBC driver version? Did the client try Java 1.6?

EclipseLink should never be leaving any locks open, but ensure your application is always committing or rolling back all open transactions, and closing all open EntityManagers.

EclipseLink does use a connection pool, maybe Foxpro has issues with this, you could configure your minimum connections size to be 0, to always disconnect after each request. This will have performance issues though, but something to test anyway.
]]>James Sutherland2012-08-01T15:44:26-00:00Re: EclipseLink + Foxprohttps://www.eclipse.org/forums/index.php/mv/msg/367282/899830/#msg_899830
Pavel Zelenka2012-08-02T13:44:21-00:00