Re: NPE when shutting H2 down after integration tests run

90 views
Skip to first unread message

Thomas Mueller

unread,
Sep 20, 2012, 2:11:57 PM9/20/12
to h2-da...@googlegroups.com
Hi,

Does it happend with the latest version as well?

Regards,
Thomas



On Tue, Sep 18, 2012 at 2:03 PM, Sanjeev Gour <sanjee...@gmail.com> wrote:
On out build system, we have seen this error a couple of time when shutting H2 down after integration tests run, has anyone seen this before and knows what could be causing it?

org.h2.jdbc.JdbcSQLException: General error: "java.lang.NullPointerException"; SQL statement: SHUTDOWN [50000-162]
org.h2.jdbc.JdbcSQLException: General error: "java.lang.NullPointerException"; SQL statement:
SHUTDOWN [50000-162]
    at org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
    at org.h2.message.DbException.get(DbException.java:158)
    at org.h2.message.DbException.convert(DbException.java:281)
    at org.h2.command.Command.executeUpdate(Command.java:230)
    at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:177)
    at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:152)
    at com.ca.mfui.chorusR2.server.service.ServiceModuleForITTesting.shutdownDatabase(ServiceModuleForITTesting.java:231)
    at com.ca.mfui.chorusR2.server.service.IntegrationTstUI.shutdownDatabase(IntegrationTstUI.java:52)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
    at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:37)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
    at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59)
    at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:120)
    at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:103)
    at org.apache.maven.surefire.Surefire.run(Surefire.java:169)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350)
    at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021)
Caused by: java.lang.NullPointerException
    at org.h2.table.RegularTable.removeRow(RegularTable.java:344)
    at org.h2.engine.UndoLogRecord.undo(UndoLogRecord.java:98)
    at org.h2.engine.Session.rollbackTo(Session.java:530)
    at org.h2.engine.Session.rollback(Session.java:507)
    at org.h2.command.dml.TransactionCommand.update(TransactionCommand.java:104)
    at org.h2.command.CommandContainer.update(CommandContainer.java:73)
    at org.h2.command.Command.executeUpdate(Command.java:226)
    ... 23 more

--
You received this message because you are subscribed to the Google Groups "H2 Database" group.
To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/yCdjktU9CfIJ.
To post to this group, send email to h2-da...@googlegroups.com.
To unsubscribe from this group, send email to h2-database...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.

Sanjeev Gour

unread,
Sep 26, 2012, 8:38:12 AM9/26/12
to h2-da...@googlegroups.com
We haven't tested that yet. We are using 1.3.162 currently and upgrading to 1.3.169. We will keep an eye if it happen with the latest version.

Thanks.

Ryan How

unread,
Jun 3, 2013, 2:58:13 AM6/3/13
to h2-da...@googlegroups.com
The stack trace indicates version 1.3.170 ?


On 3/06/2013 5:51 AM, Martin Lichtin wrote:
We are using 1.3.172 and have seen a very similar NPE.

2013-06-01 14:48:14,035 [Atomikos:1 ] WARN XAResourceTransaction - XA resource 'JDBC-H2RuleExecCamelITest': rollback for XID '3137322E32322E33302E37332E746D30303030313030303137:3137322E32322E33302E37332E746D31' raised 0: unknown
javax.transaction.xa.XAException: General error: "java.lang.NullPointerException"; SQL statement:
ROLLBACK [50000-170]
        at org.h2.jdbcx.JdbcXAConnection.convertException(JdbcXAConnection.java:397)
        at org.h2.jdbcx.JdbcXAConnection.rollback(JdbcXAConnection.java:282)
        at com.atomikos.datasource.xa.XAResourceTransaction.rollback(XAResourceTransaction.java:703)
        at com.atomikos.icatch.imp.RollbackMessage.send(RollbackMessage.java:70)
        at com.atomikos.icatch.imp.PropagationMessage.submit(PropagationMessage.java:110)
        at com.atomikos.icatch.imp.Propagator$PropagatorThread.run(Propagator.java:87)
        at com.atomikos.icatch.imp.Propagator.submitPropagationMessage(Propagator.java:66)
        at com.atomikos.icatch.imp.CoordinatorStateHandler.rollback(CoordinatorStateHandler.java:700)
        at com.atomikos.icatch.imp.ActiveStateHandler.onTimeout(ActiveStateHandler.java:102)
        at com.atomikos.icatch.imp.CoordinatorImp.alarm(CoordinatorImp.java:930)
        at com.atomikos.timing.PooledAlarmTimer.notifyListeners(PooledAlarmTimer.java:113)
        at com.atomikos.timing.PooledAlarmTimer.run(PooledAlarmTimer.java:100)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:722)
Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.NullPointerException"; SQL statement:
ROLLBACK [50000-170]
        at org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
        at org.h2.message.DbException.get(DbException.java:158)
        at org.h2.message.DbException.convert(DbException.java:281)
        at org.h2.command.Command.executeUpdate(Command.java:234)
        at org.h2.jdbc.JdbcConnection.rollbackInternal(JdbcConnection.java:1423)
        at org.h2.jdbc.JdbcConnection.rollback(JdbcConnection.java:464)
        at org.h2.jdbcx.JdbcXAConnection.rollback(JdbcXAConnection.java:269)
        ... 13 more
Caused by: java.lang.NullPointerException
        at org.h2.table.RegularTable.removeRow(RegularTable.java:345)
        at org.h2.engine.UndoLogRecord.undo(UndoLogRecord.java:98)
        at org.h2.engine.Session.rollbackTo(Session.java:529)
        at org.h2.engine.Session.rollback(Session.java:506)
        at org.h2.command.dml.TransactionCommand.update(TransactionCommand.java:49)
        at org.h2.command.CommandContainer.update(CommandContainer.java:75)
        at org.h2.command.Command.executeUpdate(Command.java:230)
        ... 16 more

On Thursday, September 20, 2012 8:12:03 PM UTC+2, Thomas Mueller wrote:
Hi,

Does it happend with the latest version as well?

Regards,
Thomas
--
You received this message because you are subscribed to the Google Groups "H2 Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to h2-database...@googlegroups.com.

To post to this group, send email to h2-da...@googlegroups.com.

Ryan How

unread,
Jun 3, 2013, 3:27:02 AM6/3/13
to h2-da...@googlegroups.com
Sorry, so do you mean you are still getting a very similar stack in 1.3.172?, You just don't have a record of it?

On 3/06/2013 3:12 PM, Martin Lichtin wrote:
Yeah, you're right. I already updated the version, but the stack indeed came from 1.3.170.


On Monday, June 3, 2013 8:58:13 AM UTC+2, Kartweel wrote:
The stack trace indicates version 1.3.170 ?
--

Martin Lichtin

unread,
Jun 3, 2013, 4:05:44 AM6/3/13
to h2-da...@googlegroups.com
Can't say yet, I am in the process of upgrading to 1.3.172. But there is a new OSGi dependency, I am getting:

Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle org.h2 [71]: Unable to resolve 71.0: missing requirement [71.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.service.jdbc)(version>=1.0.0))

Need to figure this one out first...

Thomas Mueller

unread,
Jun 3, 2013, 1:27:41 PM6/3/13
to h2-da...@googlegroups.com
Hi,

The change in the OSGi part is issue 365. I understand that OSGi issues are annoying. Personally, I avoid using OSGi whenever possible - as well as using javax by the way :-)

The reason for the NPE seems to be caused by rolling back a transaction while the session is already closed. That's weird.

What is your database URL?

Regards,
Thomas




Andre de Lima e Silva

unread,
Feb 20, 2015, 12:19:32 PM2/20/15
to h2-da...@googlegroups.com
Sorry guys for reopening this.

I'm having the same issue on 1.3.173.

I think my shutdown script, drop all objects, comes before the rollback statement, so I think it could be looking for tables that does not exist anymore, that's the NPE.

If anyone has any clue about it I want to know :).


Em segunda-feira, 3 de junho de 2013 14:27:41 UTC-3, Thomas Mueller escreveu:
Hi,

The change in the OSGi part is issue 365. I understand that OSGi issues are annoying. Personally, I avoid using OSGi whenever possible - as well as using javax by the way :-)

The reason for the NPE seems to be caused by rolling back a transaction while the session is already closed. That's weird.

What is your database URL?

Regards,
Thomas




On Monday, June 3, 2013, Martin Lichtin wrote:
Can't say yet, I am in the process of upgrading to 1.3.172. But there is a new OSGi dependency, I am getting:

Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle org.h2 [71]: Unable to resolve 71.0: missing requirement [71.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.service.jdbc)(version>=1.0.0))

Need to figure this one out first...

On Monday, June 3, 2013 9:27:02 AM UTC+2, Kartweel wrote:
Sorry, so do you mean you are still getting a very similar stack in 1.3.172?, You just don't have a record of it?

On 3/06/2013 3:12 PM, Martin Lichtin wrote:
Yeah, you're right. I already updated the version, but the stack indeed came from 1.3.170.

On Monday, June 3, 2013 8:58:13 AM UTC+2, Kartweel wrote:
The stack trace indicates version 1.3.170 ?

--
You received this message because you are subscribed to the Google Groups "H2 Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscribe@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages