[
https://issues.apache.org/jira/browse/DERBY-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882616#action_12882616
]
Lily Wei commented on DERBY-4709:
---------------------------------
I want the number of RDBCMM or RDBRLLBCK right after [common_wok], then after
[unnecessary_commit_work]. As I recall I was reading them from the trace
number, the number is different. Is that true?
This is the stack trace I am getting when applying your patch:
$ java junit.textui.TestRunner
org.apache.derbyTesting.functionTests.tests.jdbcap
i.J2EEDataSourceTest
.........................................
..........F.......
Time: 36.77
There was 1 failure:
1) Client/Serverjunit.framework.AssertionFailedError:
extinout\ds_cp_base_commit.trace
at
org.apache.derbyTesting.junit.DropDatabaseSetup.removeDir(DropDatabaseSetup.java:130)
at
org.apache.derbyTesting.junit.DropDatabaseSetup.access$000(DropDatabaseSetup.java:35)
at
org.apache.derbyTesting.junit.DropDatabaseSetup$1.run(DropDatabaseSetup.java:105)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.derbyTesting.junit.DropDatabaseSetup.removeDirectory(DropDatabaseSetup.java:10
2)
at
org.apache.derbyTesting.junit.DropDatabaseSetup.removeDirectory(DropDatabaseSetup.java:98
)
at
org.apache.derbyTesting.junit.SupportFilesSetup.tearDown(SupportFilesSetup.java:128)
at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
FAILURES!!!
Tests run: 58, Failures: 1, Errors: 0
Do I miss something or is it something in my environment?
> Create test that parse client trace file to detect round-trips for Derby-4653
> -----------------------------------------------------------------------------
>
> Key: DERBY-4709
> URL: https://issues.apache.org/jira/browse/DERBY-4709
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.7.0.0
> Reporter: Lily Wei
> Priority: Minor
> Attachments: derby-4709-1a-alternative_test.diff
>
>
> In DERBY-4653, Kristian suggested we have a test that parse the trace file to
> detect round-trip Connection.flowcommit() instead of calling
> getClientTransactionID() method. The existing test for DERBY-4653 is in
> J2EEDataSourceTest.testConnectionFlowCommit(). When this issue get fixed, the
> call for getClientTransactionID can be replace with trace file parsing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
