Issue Details (XML | Word | Printable)

Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Unassigned
Reporter: Andy Jefferson
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
DataNucleus Store RDBMS

Any secondary (schema/sequence) connection should call release() rather than close() when finished with

Created: 14/Dec/12 10:00 AM   Updated: 31/Dec/12 07:59 PM   Resolved: 14/Dec/12 10:01 AM
Component/s: Schema, Value Generation
Affects Version/s: None
Fix Version/s: 3.2.0.m2

 Description  « Hide
close() should be handled by the connection itself, we simply release it back

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 14/Dec/12 10:01 AM
SVN trunk fixes this

Chris Colman added a comment - 20/Dec/12 12:51 AM
Is it likely that this issue could have caused 'Communications link failure' exceptions like the following or does this look like something else?

Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet successfully received from the server was 3,384,375 milliseconds ago. The last packet sent successfully to the server was 1 milliseconds ago.
        at sun.reflect.GeneratedConstructorAccessor84.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
        at java.lang.reflect.Constructor.newInstance(
        at com.mysql.jdbc.Util.handleNewInstance(
        at com.mysql.jdbc.SQLError.createCommunicationsException(
        at com.mysql.jdbc.MysqlIO.send(
        at com.mysql.jdbc.MysqlIO.sendCommand(
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(
        at com.mysql.jdbc.ConnectionImpl.execSQL(
        at com.mysql.jdbc.ConnectionImpl.setAutoCommit(
        at org.apache.tomcat.dbcp.dbcp.DelegatingConnection.setAutoCommit(
        at org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.setAutoCommit(
        at org.datanucleus.state.JDOStateManager.internalMakePersistent(
        at org.datanucleus.state.JDOStateManager.flush(
        at org.datanucleus.ObjectManagerImpl.flushInternalWithOrdering(
        at org.datanucleus.ObjectManagerImpl.flushInternal(
        at org.datanucleus.api.jdo.JDOQuery.execute(
        ... 48 more
Caused by: Broken pipe
        at Method)
        at com.mysql.jdbc.MysqlIO.send(
        ... 72 more

Andy Jefferson added a comment - 20/Dec/12 07:05 AM
No. You're using a query and this issue is for schema/sequence connections. Your MySQL lost its connection with the world