[ https://issues.apache.org/jira/browse/DERBY-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jørgen Løland updated DERBY-3184: --------------------------------- Attachment: derby-3184-3b.diff Hi Øystein, Thanks for reviewing the patch. v3b addresses your comments. All tests pass - the patch is ready for review. > Replication: Connection attempts to a database in slave mode must fail > ---------------------------------------------------------------------- > > Key: DERBY-3184 > URL: https://issues.apache.org/jira/browse/DERBY-3184 > Project: Derby > Issue Type: Sub-task > Components: Services > Affects Versions: 10.4.0.0 > Reporter: Jørgen Løland > Assignee: Jørgen Løland > Attachments: derby-3184-1.diff, derby-3184-1.stat, > derby-3184-2a.diff, derby-3184-2a.stat, derby-3184-2b.diff, > derby-3184-2b.stat, derby-3184-2c.diff, derby-3184-3a.diff, > derby-3184-3a.stat, derby-3184-3b.diff, derby-3184-bugfix-1a.diff, > derby-3184-bugfix-1a.stat > > > When a database 'X' is booted in slave mode, the call to > Monitor.startPersistentService("X",...) will not complete because the call > gets stuck in LogToFile#recover. This is intentional. > For as long as startPersistentService is blocked, however, other threads that > try to connect to 'X' (effectively calling Monitor.findService("X", ...)) > will also hang. This is unacceptable, and needs to raise an error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.