[
https://issues.apache.org/jira/browse/DERBY-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden resolved DERBY-17.
---------------------------------
Resolution: Won't Fix
There doesn't seem to be much interest in fixing this issue and no problems
seen with clients generating duplicate correlation tokens. From David's
analysis, they should be unique. The issue can be reopened if someone decides
to fix.
> Network Server Needs to generate CRRTKN on ACCRDB if client does not send it
> ----------------------------------------------------------------------------
>
> Key: DERBY-17
> URL: https://issues.apache.org/jira/browse/DERBY-17
> Project: Derby
> Issue Type: Bug
> Components: Network Server, Newcomer
> Affects Versions: 10.0.2.0
> Reporter: Ramandeep Kaur
> Priority: Minor
>
> Opening this bug on behalf of Katherine Marsden
> --------------------------------------------------------------
> JCC cannot guarantee that the CRRTKN that they send is unique
> because it may come from many jvms.
> According to the DDM Spec in ACCRDBRM we should generate and
> send CRRTKN if it was not sent to us.
> crrtkn INSTANCE_OF CRRTKN - Correlation Token
> 1810 OPTIONAL
> 1811 DFTVAL â??â??
> 1812 NOTE Source server product-specific value is used.
> 1813 This parameter is returned if and only if the
> 1814 CRRTKN parameter is not received on
> 1815 ACCRDB.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
