[
https://issues.apache.org/jira/browse/DERBY-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567603#action_12567603
]
Jørgen Løland commented on DERBY-3359:
--------------------------------------
I tried running replication with the new log shipper. Seems mf is never
initialized in ReplicationLogBuffer.
Master-side start replication (slave side behaves normally):
$ ij
ij version 10.4
ij> connect 'jdbc:derby:t1';
ij> connect 'jdbc:derby:t1;startMaster=true;slaveHost=localhost';
ij(CONNECTION1)> Exception in thread "Thread-1" java.lang.NullPointerException
at
org.apache.derby.impl.services.replication.buffer.ReplicationLogBuffer.switchDirtyBuffer(ReplicationLogBuffer.java:319)
at
org.apache.derby.impl.services.replication.buffer.ReplicationLogBuffer.next(ReplicationLogBuffer.java:187)
at
org.apache.derby.impl.services.replication.master.AsynchronousLogShipper.shipALogChunk(AsynchronousLogShipper.java:213)
at
org.apache.derby.impl.services.replication.master.AsynchronousLogShipper.run(AsynchronousLogShipper.java:165)
> The log shipper needs to be modified to vary the shipping intervals
> dynamically (based on load)
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-3359
> URL: https://issues.apache.org/jira/browse/DERBY-3359
> Project: Derby
> Issue Type: Sub-task
> Reporter: V.Narayanan
> Assignee: V.Narayanan
> Attachments: DynamicLogShipping_v1.diff, DynamicLogShipping_v1.stat,
> DynamicLogShipping_v2.diff, DynamicLogShipping_v2.stat,
> DynamicLogShipping_v3.diff, DynamicLogShipping_v3.stat
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
