[
https://issues.apache.org/jira/browse/DERBY-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ole Solberg updated DERBY-3162:
-------------------------------
Attachment: derby-3162.6_v1.stat.txt
derby-3162.6_v1.diff.txt
Patch 3162.6-v1 for replicationtests:
Fix to allow ReplicationSuite to run on JVM 1.4 and 1.5:
The replicationTest framework (ReplicationRun) used
Drivermanager.getConnection()
to do startMaster=true and startSlave=true concurrently.
On 1.5 (and 1.4), but not on 1.6, it turned out that this caused a deadlock (on
DriverManager.class?).
Using DataSource instead of DriverManager solved the problem.
Big thanks to Kristian Waagan who helped analyzing this!
The patch has been tested on
Linux: jars: 1.4, 1.5, 1.6. classes: 1.4, 1.5, 1.6
Solaris: jars: 1.4, 1.5, 1.6
Windows: jars: 1.4, 1.5, 1.6
> Create a framework for replication tests
> ----------------------------------------
>
> Key: DERBY-3162
> URL: https://issues.apache.org/jira/browse/DERBY-3162
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Fix For: 10.5.0.0
>
> Attachments: derby-3162.1-v1.diff.txt, derby-3162.2-v2.diff.txt,
> derby-3162.2-v2.stat.txt, derby-3162.3-v1.diff.txt, derby-3162.3-v1.stat.txt,
> derby-3162.3-v2.diff.txt, derby-3162.3-v2.stat.txt, derby-3162.3-v3.diff.txt,
> derby-3162.3-v3.stat.txt, derby-3162.3-v4c.diff.txt,
> derby-3162.3-v4c.stat.txt, derby-3162.3-v4d.diff.txt,
> derby-3162.3-v4d.stat.txt, derby-3162.4-v3.diff.txt,
> derby-3162.4-v3.stat.txt, derby-3162.5-v1.diff.txt, derby-3162.5-v1.stat.txt,
> derby-3162.6_v1.diff.txt, derby-3162.6_v1.stat.txt
>
>
> Handle
> - starting and stopping Derby servers to have the master and slave
> replication roles,
> - doing administrative commands like startreplication, startslave,
> stopreplication, failover,
> - performing consistency checks on the slave vs. the master,
> - running load clients against master and slave in the various states of
> replication,
> - provoking error situations on master and slave, and network,
> - ...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
