You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2016/11/01 13:38:58 UTC
[jira] [Commented] (BEAM-748) Issues with local processes in
MongoDbIO and JdbcIO
[ https://issues.apache.org/jira/browse/BEAM-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15625456#comment-15625456 ]
Jean-Baptiste Onofré commented on BEAM-748:
-------------------------------------------
It could be related to BEAM-856 (when several jobs are running on the same machine). Let's try to see if BEAM-856 (and related) helps.
> Issues with local processes in MongoDbIO and JdbcIO
> ---------------------------------------------------
>
> Key: BEAM-748
> URL: https://issues.apache.org/jira/browse/BEAM-748
> Project: Beam
> Issue Type: Bug
> Components: testing
> Affects Versions: Not applicable
> Reporter: Daniel Halperin
> Assignee: Jean-Baptiste Onofré
>
> Hey JB, Can you take a look at these issues? Causing flakes in precommit testing.
> https://builds.apache.org/job/beam_PreCommit_MavenVerify/3931/
> A few different types, likely due to issues setting up databases and reusing them across tests?
> {code}
> java.net.ConnectException : Error connecting to server localhost on port 1,527 with message Connection refused.
> {code}
> {code}
> A lock could not be obtained due to a deadlock, cycle of locks and waiters is:
> Lock : ROW, SYSCOLUMNS, (4,42)
> Waiting XID : {187, S} , APP, insert into BEAM values (?,?)
> Granted XID : {185, S}
> Lock : ROW, SYSTABLES, (1,30)
> Waiting XID : {185, X} , APP, drop table BEAM
> Granted XID : {185, S} , {187, S}
> . The selected victim is XID : 187.
> Stacktrace
> java.sql.SQLTransactionRollbackException:
> A lock could not be obtained due to a deadlock, cycle of locks and waiters is:
> Lock : ROW, SYSCOLUMNS, (4,42)
> Waiting XID : {187, S} , APP, insert into BEAM values (?,?)
> Granted XID : {185, S}
> Lock : ROW, SYSTABLES, (1,30)
> Waiting XID : {185, X} , APP, drop table BEAM
> Granted XID : {185, S} , {187, S}
> . The selected victim is XID : 187.
> at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
> at org.apache.derby.client.am.ClientConnection.prepareStatement(Unknown Source)
> at org.apache.beam.sdk.io.jdbc.JdbcIOTest.initTable(JdbcIOTest.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runners.Suite.runChild(Suite.java:127)
> at org.junit.runners.Suite.runChild(Suite.java:26)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> Suppressed: java.sql.SQLException: Cannot close a connection while a transaction is still active.
> at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
> at org.apache.derby.client.am.ClientConnection.closeResourcesX(Unknown Source)
> at org.apache.derby.client.am.ClientConnection.closeX(Unknown Source)
> at org.apache.derby.client.am.ClientConnection.close(Unknown Source)
> at org.apache.derby.client.net.NetConnection.close(Unknown Source)
> at org.apache.beam.sdk.io.jdbc.JdbcIOTest.initTable(JdbcIOTest.java:117)
> ... 36 more
> Caused by: ERROR 25001: Cannot close a connection while a transaction is still active.
> at org.apache.derby.client.am.ClientConnection.checkForTransactionInProgress(Unknown Source)
> ... 41 more
> Caused by: ERROR 40001: A lock could not be obtained due to a deadlock, cycle of locks and waiters is:
> Lock : ROW, SYSCOLUMNS, (4,42)
> Waiting XID : {187, S} , APP, insert into BEAM values (?,?)
> Granted XID : {185, S}
> Lock : ROW, SYSTABLES, (1,30)
> Waiting XID : {185, X} , APP, drop table BEAM
> Granted XID : {185, S} , {187, S}
> . The selected victim is XID : 187.
> at org.apache.derby.client.am.ClientStatement.completeSqlca(Unknown Source)
> at org.apache.derby.client.net.NetStatementReply.parsePrepareError(Unknown Source)
> at org.apache.derby.client.net.NetStatementReply.parsePRPSQLSTTreply(Unknown Source)
> at org.apache.derby.client.net.NetStatementReply.readPrepareDescribeOutput(Unknown Source)
> at org.apache.derby.client.net.StatementReply.readPrepareDescribeOutput(Unknown Source)
> at org.apache.derby.client.net.NetStatement.readPrepareDescribeOutput_(Unknown Source)
> at org.apache.derby.client.am.ClientStatement.readPrepareDescribeOutput(Unknown Source)
> at org.apache.derby.client.am.ClientPreparedStatement.readPrepareDescribeInputOutput(Unknown Source)
> at org.apache.derby.client.am.ClientPreparedStatement.flowPrepareDescribeInputOutput(Unknown Source)
> at org.apache.derby.client.am.ClientPreparedStatement.prepare(Unknown Source)
> at org.apache.derby.client.am.ClientConnection.prepareStatementX(Unknown Source)
> ... 38 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)