[ http://issues.apache.org/jira/browse/DERBY-17?page=comments#action_12312572 ]
David Van Couvering commented on DERBY-17: ------------------------------------------ OK. I thought each connection to the server got a different port number, so since you are using local host and port as part of the CRRTKN it should be unique for each connection to the server. But what I'll do is just test this out. > Network Server Needs to generate CRRTKN on ACCRDB if client does not send it > ---------------------------------------------------------------------------- > > Key: DERBY-17 > URL: http://issues.apache.org/jira/browse/DERBY-17 > Project: Derby > Type: Bug > Components: Network Server > 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. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
