Eclipse Community Forums: EclipseLink

Help

Home

Home » Eclipse Projects » EclipseLink » EclipseLink + Foxpro(Using eclipselink and JPA 2.0 with foxpro database.)

Show: Today's Messages :: Show Polls :: Message Navigator

EclipseLink + Foxpro [message #894861]

Tue, 10 July 2012 20:13

Chad Curtis

Messages: 8
Registered: July 2012
Location: Minnesota

Junior Member

I am having some issues using eclipselink with a foxpro database. Connecting and using the database isn't the problem. The problem is that we use another foxpro application on the same database and there are times when the other app can't update a record. The java app that uses eclipselink doesn't have a problem updating. But the only way to fix the problem in the foxpro app is to actually close the java app. So the question is, is there something that might not be obvious that I am missing that either eclipselink or jdbc:odbc does that would cause a lock on a table?

Here is the persistance.xml setup
<property name="eclipselink.target-database" value="org.eclipse.persistence.platform.database.DatabasePlatform"/>
<property name="javax.persistence.jdbc.url" value="jdbc:odbc:MyODBC"/>
<property name="javax.persistence.jdbc.password" value=""/>
<property name="javax.persistence.jdbc.driver" value="sun.jdbc.odbc.JdbcOdbcDriver"/>
<property name="javax.persistence.jdbc.user" value=""/>

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.

Report message to a moderator

Re: EclipseLink + Foxpro [message #899625 is a reply to message #894861]

Wed, 01 August 2012 15:44

James Sutherland

Messages: 1939
Registered: July 2009
Location: Ottawa, Canada

Senior Member

I'm not that familiar with Foxpro, but does seem like an odd issue.

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 : Wiki : Book : Blog : Twitter

Report message to a moderator