Xanana,

It could be that you're hitting
https://issues.apache.org/jira/browse/DERBY-2084
or https://issues.apache.org/jira/browse/DERBY-638

Bernt

>>>>>>>>>>>> Xanana Gusmao wrote (2006-12-06 09:26:40):
> Kristian,
> 
> In terms of upgrading, I will come back to you later on that. This is a
> production system running with a JDO layer. I encountered this problem when I
> wanted to access the data via pure JDBC.
> 
> Currently for my test code, I'm just doing a Class.forName() and
> DriverManager.getConnection(). I'll be using DBCP for pooling later.
> 
> The SQLException happens within JdbcUtil.closeConnection(..)
> That means, any updates to the database has already been "committed" when this
> error occurs. It seems benign enough to ignore ?
> 
> The implementation of JdbcUtil.rollback(conn) just does conn.rollback(). No
> rollback took place.
> 
> One more thing, the application is running under "equinox", an OSGI container.
> 
> Thanks
> 
> Xanana
> 

-- 
Bernt Marius Johnsen, Database Technology Group, 
Staff Engineer, Technical Lead Derby/Java DB
Sun Microsystems, Trondheim, Norway

Attachment: pgpMvLueHlI6A.pgp
Description: PGP signature

Reply via email to