[
https://issues.apache.org/jira/browse/DERBY-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884309#comment-15884309
]
Bryan Pendleton commented on DERBY-6923:
----------------------------------------
Assuming that this is in fact a strange behavior of Derby's locator
implementation in the NetworkClient, DERBY-2496 is probably the relevant code
to study.
> Passing a ClientClob or ClientBlob from another connection to an INSERT
> statement results in 'null' being written.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6923
> URL: https://issues.apache.org/jira/browse/DERBY-6923
> Project: Derby
> Issue Type: Bug
> Components: Network Client, Network Server
> Affects Versions: 10.13.1.1
> Environment: Java 8
> MacOS
> Windows
> Reporter: Gordon Innes
> Priority: Critical
> Attachments: DerbyEmbeddedOnly.java, DerbyNetworkOnly.java,
> DerbyNetworkRead.java, DerbyNetworkWrite.java
>
>
> When assigning a Blob or Clob from a ResultSet to a PreparedStatement
> parameter on a second connection, null is written to the column instead.
> Attached the same example using Embedded->Embedded, Embedded->Network,
> Network->Embedded and Network->Network.
> Only the Network->Network example exhibits the fault.
> Originally discovered in HA-JDBC's sync code with 2 derby instances on
> Windows. Example were tested using MacOS. Both were running on Oracle Java 8
> VMs.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
