[
https://issues.apache.org/jira/browse/DERBY-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730586#action_12730586
]
Mamta A. Satoor commented on DERBY-4053:
----------------------------------------
I looked through derby.log and see that it has observers error in derby.log
[main] FAIL - org.apache.derby.shared.common.sanity.AssertFailure: ASSERT
FAILED There should be 0 observers, but we still have 1 observers.
org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED There should
be 0 observers, but we still have 1 observers.
at
org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:162)
at
org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:147)
at org.apache.derby.impl.store.raw.xact.Xact.doComplete(Xact.java:1969)
at org.apache.derby.impl.store.raw.xact.Xact.preComplete(Xact.java:1925)
at
org.apache.derby.impl.store.raw.xact.Xact.prepareCommit(Xact.java:769)
at org.apache.derby.impl.store.raw.xact.Xact.commit(Xact.java:882)
at org.apache.derby.impl.store.raw.xact.Xact.commit(Xact.java:679)
at
org.apache.derbyTesting.unitTests.store.T_Util.t_commit(T_Util.java:840)
at
org.apache.derbyTesting.unitTests.store.T_RawStoreFactory.TC001(T_RawStoreFactory.java:7310)
at
org.apache.derbyTesting.unitTests.store.T_RawStoreFactory.runTempTests(T_RawStoreFactory.java:417)
at
org.apache.derbyTesting.unitTests.store.T_RawStoreFactory.runTestSet(T_RawStoreFactory.java:248)
at
org.apache.derbyTesting.unitTests.harness.T_MultiIterations.runTests(T_MultiIterations.java:95)
at
org.apache.derbyTesting.unitTests.harness.T_MultiThreadedIterations.runTests(T_MultiThreadedIterations.java:92)
at
org.apache.derbyTesting.unitTests.harness.T_Generic.Execute(T_Generic.java:118)
at
org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.runATest(BasicUnitTestManager.java:184)
at
org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.runTests(BasicUnitTestManager.java:246)
at
org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.boot(BasicUnitTestManager.java:93)
at
org.apache.derby.impl.services.monitor.BaseMonitor.boot(BaseMonitor.java:2021)
at
org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java:333)
at
org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1858)
at
org.apache.derby.impl.services.monitor.BaseMonitor.startServices(BaseMonitor.java:997)
at
org.apache.derby.impl.services.monitor.BaseMonitor.runWithState(BaseMonitor.java:429)
at
org.apache.derby.impl.services.monitor.FileMonitor.<init>(FileMonitor.java:60)
at
org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Monitor.java:289)
at
org.apache.derbyTesting.unitTests.harness.UnitTestMain.main(UnitTestMain.java:51)
> suites.All hang with message java.net.BindException: Address already in use:
> NET_Bind in derby.log
> ---------------------------------------------------------------------------------------------------
>
> Key: DERBY-4053
> URL: https://issues.apache.org/jira/browse/DERBY-4053
> Project: Derby
> Issue Type: Bug
> Components: Network Server, Test
> Affects Versions: 10.5.1.1
> Reporter: Kathey Marsden
> Assignee: Mamta A. Satoor
> Attachments: derby-4053_repro_dont_commit_diff.txt, derby.log,
> DERBY4053_patch1_diff_July092009.txt, DERBY4053_patch2_diff_July102009.txt,
> DERBY4053_patch2_stat_July102009.txt, DERBY4053_patch3_diff_July102009.txt,
> DERBY4053_patch3_stat_July102009.txt, javacore-20090420-1735.txt,
> javacore.20090211.123031.4000.0001.txt, mamtaDerby4053.java, suites.All.out
>
>
> Running suites.All with IBM 1.5 on 10.5.0.0 alpha - (743198) I got a hang
> in the test run. The last test to run successfully was
> xtestNestedSavepoints, but I am not sure exactly what test caused the hang.
> I took a thread dump which I will attach, which showed network server up and
> running but no ClientThread and a ping attempt blocked.
> This hang is very similar to the hang that was seen after the fix attempts
> for DERBY-1465 but that change was backed out so it is not related to that
> change. It could be that the change for DERBY-1465 just made this highly
> intermittent problem more likely.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
