db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-17) Network Server Needs to generate CRRTKN on ACCRDB if client does not send it
Date Thu, 02 Jun 2005 18:07:08 GMT
     [ http://issues.apache.org/jira/browse/DERBY-17?page=comments#action_66893 ]
     
David Van Couvering commented on DERBY-17:
------------------------------------------

I'd like to understand why JCC cannot guarantee uniqueness.  Reading the spec, the CRRTKN
is a combination of the specific host and port *of the client* and a long value of the current
timestamp, and that's how it's implemented in the client code (although for some reason I
don't fully fathom it only uses half of the bytes of each part of the IP address).  Since
each client uses a different TPC-IP port, this value should be unique, even across VMs where
the timestamp might match.  The timestamp is just intended to guarantee uniqueness within
the same VM.  

That said, if the CRRTKN is null, yes, according to the spec the network server should generate
it.  But unless I can understand how the CRRTKN generated by the client is not unique across
VMs, I don't think it makes sense for the client to stop generating the CRRTKN. 

> 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


Mime
View raw message