db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lily Wei (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4709) Create test that parse client trace file to detect round-trips for Derby-4653
Date Wed, 23 Jun 2010 21:25:50 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881888#action_12881888
] 

Lily Wei commented on DERBY-4709:
---------------------------------

Thanks Kristian for the alternative test. I think it is very promising. I just have two heads
up.
1. typo on invokations for testConnectionFlowCommitRollback. I am assuming it intent for invocation
for comments and variable name
2. When we check RDBCMM or RDBLLBCK,  do care about when it was print to the trace file? I
think it is also matter because it will show whether the Connection.commit() flow the commit
or not and same goes to rollback.
3. Do we care about how frequent the token is print to trace file? Will it be persistent throught
out different releases? Does it depend on different department effort in turn of the trace
message?

> 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.


Mime
View raw message