You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "V.Narayanan (JIRA)" <ji...@apache.org> on 2008/03/16 16:00:24 UTC
[jira] Created: (DERBY-3549) Unable to start slave mode after
authentication failure on a previous startSlave attempt
Unable to start slave mode after authentication failure on a previous startSlave attempt
----------------------------------------------------------------------------------------
Key: DERBY-3549
URL: https://issues.apache.org/jira/browse/DERBY-3549
Project: Derby
Issue Type: Bug
Components: Replication
Affects Versions: 10.4.0.0, 10.5.0.0
Reporter: V.Narayanan
Trying a startSlave after an initial startSlave fails due to an authentication failure throws an error
saying that the database has already been booted
vn@vn-laptop:~/work/workspaces/freshworkspace/slave$ java org.apache.derby.tools.ij
ij version 10.5
ij> connect 'jdbc:derby:mydb;startSlave=true;slaveHost=localhost;slavePort=8001';
ERROR 08004: Connection authentication failure occurred. Reason: Invalid authentication..
ij> connect 'jdbc:derby:mydb;startSlave=true;user=oystein;password=pass;slaveHost=localhost;slavePort=8001';
ERROR XRE09: Cannot start replication slave mode for database 'mydb'. The database has already been booted.
ij>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3549) Unable to start slave mode after
authentication failure on a previous startSlave attempt
Posted by "Øystein Grøvlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582273#action_12582273 ]
Øystein Grøvlen commented on DERBY-3549:
----------------------------------------
I am also not quite sure what is the best error to get in the case
that you try start a slave on a already booted database with invalid
credentials. Should a a user that is not authorized to boot the
database, be able to learn whether it is booted or not through a
startSlave command?
> Unable to start slave mode after authentication failure on a previous startSlave attempt
> ----------------------------------------------------------------------------------------
>
> Key: DERBY-3549
> URL: https://issues.apache.org/jira/browse/DERBY-3549
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.0.0, 10.5.0.0
> Reporter: V.Narayanan
> Assignee: Jørgen Løland
> Attachments: derby-3549-1a.diff, derby-3549-1a.stat
>
>
> Trying a startSlave after an initial startSlave fails due to an authentication failure throws an error
> saying that the database has already been booted
> vn@vn-laptop:~/work/workspaces/freshworkspace/slave$ java org.apache.derby.tools.ij
> ij version 10.5
> ij> connect 'jdbc:derby:mydb;startSlave=true;slaveHost=localhost;slavePort=8001';
> ERROR 08004: Connection authentication failure occurred. Reason: Invalid authentication..
> ij> connect 'jdbc:derby:mydb;startSlave=true;user=oystein;password=pass;slaveHost=localhost;slavePort=8001';
> ERROR XRE09: Cannot start replication slave mode for database 'mydb'. The database has already been booted.
> ij>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3549) Unable to start slave mode after
authentication failure on a previous startSlave attempt
Posted by "Øystein Grøvlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582274#action_12582274 ]
Øystein Grøvlen commented on DERBY-3549:
----------------------------------------
Do you plan to add any test cases for this issue to the replication test suite?
> Unable to start slave mode after authentication failure on a previous startSlave attempt
> ----------------------------------------------------------------------------------------
>
> Key: DERBY-3549
> URL: https://issues.apache.org/jira/browse/DERBY-3549
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.0.0, 10.5.0.0
> Reporter: V.Narayanan
> Assignee: Jørgen Løland
> Attachments: derby-3549-1a.diff, derby-3549-1a.stat
>
>
> Trying a startSlave after an initial startSlave fails due to an authentication failure throws an error
> saying that the database has already been booted
> vn@vn-laptop:~/work/workspaces/freshworkspace/slave$ java org.apache.derby.tools.ij
> ij version 10.5
> ij> connect 'jdbc:derby:mydb;startSlave=true;slaveHost=localhost;slavePort=8001';
> ERROR 08004: Connection authentication failure occurred. Reason: Invalid authentication..
> ij> connect 'jdbc:derby:mydb;startSlave=true;user=oystein;password=pass;slaveHost=localhost;slavePort=8001';
> ERROR XRE09: Cannot start replication slave mode for database 'mydb'. The database has already been booted.
> ij>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3549) Unable to start slave mode after
authentication failure on a previous startSlave attempt
Posted by "Øystein Grøvlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Øystein Grøvlen updated DERBY-3549:
-----------------------------------
Derby Info: (was: [Patch Available])
Fix Version/s: 10.5.0.0
Thanks, Jørgen. Committed patch derby-3549-1b.diff at revision 642219.
> Unable to start slave mode after authentication failure on a previous startSlave attempt
> ----------------------------------------------------------------------------------------
>
> Key: DERBY-3549
> URL: https://issues.apache.org/jira/browse/DERBY-3549
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.0.0, 10.5.0.0
> Reporter: V.Narayanan
> Assignee: Jørgen Løland
> Fix For: 10.5.0.0
>
> Attachments: derby-3549-1a.diff, derby-3549-1a.stat, derby-3549-1b.diff, derby-3549-1b.stat
>
>
> Trying a startSlave after an initial startSlave fails due to an authentication failure throws an error
> saying that the database has already been booted
> vn@vn-laptop:~/work/workspaces/freshworkspace/slave$ java org.apache.derby.tools.ij
> ij version 10.5
> ij> connect 'jdbc:derby:mydb;startSlave=true;slaveHost=localhost;slavePort=8001';
> ERROR 08004: Connection authentication failure occurred. Reason: Invalid authentication..
> ij> connect 'jdbc:derby:mydb;startSlave=true;user=oystein;password=pass;slaveHost=localhost;slavePort=8001';
> ERROR XRE09: Cannot start replication slave mode for database 'mydb'. The database has already been booted.
> ij>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DERBY-3549) Unable to start slave mode after
authentication failure on a previous startSlave attempt
Posted by "Jørgen Løland (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jørgen Løland reassigned DERBY-3549:
------------------------------------
Assignee: Jørgen Løland
> Unable to start slave mode after authentication failure on a previous startSlave attempt
> ----------------------------------------------------------------------------------------
>
> Key: DERBY-3549
> URL: https://issues.apache.org/jira/browse/DERBY-3549
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.0.0, 10.5.0.0
> Reporter: V.Narayanan
> Assignee: Jørgen Løland
>
> Trying a startSlave after an initial startSlave fails due to an authentication failure throws an error
> saying that the database has already been booted
> vn@vn-laptop:~/work/workspaces/freshworkspace/slave$ java org.apache.derby.tools.ij
> ij version 10.5
> ij> connect 'jdbc:derby:mydb;startSlave=true;slaveHost=localhost;slavePort=8001';
> ERROR 08004: Connection authentication failure occurred. Reason: Invalid authentication..
> ij> connect 'jdbc:derby:mydb;startSlave=true;user=oystein;password=pass;slaveHost=localhost;slavePort=8001';
> ERROR XRE09: Cannot start replication slave mode for database 'mydb'. The database has already been booted.
> ij>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3549) Unable to start slave mode after
authentication failure on a previous startSlave attempt
Posted by "Jørgen Løland (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582679#action_12582679 ]
Jørgen Løland commented on DERBY-3549:
--------------------------------------
> Do you plan to add any test cases for this issue to the replication test suite?
Yes, but a security manager is required for that. Currently, the replication test framework does not support the security manager. I added this issue to the list of missing regression tests on DERBY-3403.
> Unable to start slave mode after authentication failure on a previous startSlave attempt
> ----------------------------------------------------------------------------------------
>
> Key: DERBY-3549
> URL: https://issues.apache.org/jira/browse/DERBY-3549
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.0.0, 10.5.0.0
> Reporter: V.Narayanan
> Assignee: Jørgen Løland
> Attachments: derby-3549-1a.diff, derby-3549-1a.stat, derby-3549-1b.diff, derby-3549-1b.stat
>
>
> Trying a startSlave after an initial startSlave fails due to an authentication failure throws an error
> saying that the database has already been booted
> vn@vn-laptop:~/work/workspaces/freshworkspace/slave$ java org.apache.derby.tools.ij
> ij version 10.5
> ij> connect 'jdbc:derby:mydb;startSlave=true;slaveHost=localhost;slavePort=8001';
> ERROR 08004: Connection authentication failure occurred. Reason: Invalid authentication..
> ij> connect 'jdbc:derby:mydb;startSlave=true;user=oystein;password=pass;slaveHost=localhost;slavePort=8001';
> ERROR XRE09: Cannot start replication slave mode for database 'mydb'. The database has already been booted.
> ij>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3549) Unable to start slave mode after
authentication failure on a previous startSlave attempt
Posted by "Jørgen Løland (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jørgen Løland updated DERBY-3549:
---------------------------------
Attachment: derby-3549-1b.stat
derby-3549-1b.diff
Thanks for reviewing the patch. Patch 1b addresses the issue that unauthorized users should not get to know if a database has been booted or not.
All tests passed. Requesting review.
> Unable to start slave mode after authentication failure on a previous startSlave attempt
> ----------------------------------------------------------------------------------------
>
> Key: DERBY-3549
> URL: https://issues.apache.org/jira/browse/DERBY-3549
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.0.0, 10.5.0.0
> Reporter: V.Narayanan
> Assignee: Jørgen Løland
> Attachments: derby-3549-1a.diff, derby-3549-1a.stat, derby-3549-1b.diff, derby-3549-1b.stat
>
>
> Trying a startSlave after an initial startSlave fails due to an authentication failure throws an error
> saying that the database has already been booted
> vn@vn-laptop:~/work/workspaces/freshworkspace/slave$ java org.apache.derby.tools.ij
> ij version 10.5
> ij> connect 'jdbc:derby:mydb;startSlave=true;slaveHost=localhost;slavePort=8001';
> ERROR 08004: Connection authentication failure occurred. Reason: Invalid authentication..
> ij> connect 'jdbc:derby:mydb;startSlave=true;user=oystein;password=pass;slaveHost=localhost;slavePort=8001';
> ERROR XRE09: Cannot start replication slave mode for database 'mydb'. The database has already been booted.
> ij>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3549) Unable to start slave mode after
authentication failure on a previous startSlave attempt
Posted by "Jørgen Løland (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jørgen Løland updated DERBY-3549:
---------------------------------
Attachment: derby-3549-1a.diff
derby-3549-1a.stat
Patch 1a shuts down the database after failing a credential check for the startSlave command. This will only happen if the database has not been booted already due to EmbedConnnection lines 277-282:
if (isStartSlaveBoot) {
if (database != null) {
throw StandardException.newException(
SQLState.CANNOT_START_SLAVE_ALREADY_BOOTED,
getTR().getDBName());
}
With the patch, the repro works as expected. All tests passed except testStartStopManagementFromApplication which also fails tinderbox. Requesting review.
> Unable to start slave mode after authentication failure on a previous startSlave attempt
> ----------------------------------------------------------------------------------------
>
> Key: DERBY-3549
> URL: https://issues.apache.org/jira/browse/DERBY-3549
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.0.0, 10.5.0.0
> Reporter: V.Narayanan
> Assignee: Jørgen Løland
> Attachments: derby-3549-1a.diff, derby-3549-1a.stat
>
>
> Trying a startSlave after an initial startSlave fails due to an authentication failure throws an error
> saying that the database has already been booted
> vn@vn-laptop:~/work/workspaces/freshworkspace/slave$ java org.apache.derby.tools.ij
> ij version 10.5
> ij> connect 'jdbc:derby:mydb;startSlave=true;slaveHost=localhost;slavePort=8001';
> ERROR 08004: Connection authentication failure occurred. Reason: Invalid authentication..
> ij> connect 'jdbc:derby:mydb;startSlave=true;user=oystein;password=pass;slaveHost=localhost;slavePort=8001';
> ERROR XRE09: Cannot start replication slave mode for database 'mydb'. The database has already been booted.
> ij>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-3549) Unable to start slave mode after
authentication failure on a previous startSlave attempt
Posted by "Øystein Grøvlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Øystein Grøvlen resolved DERBY-3549.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.4.1.0
Merged to 10.4 branch at revision 643828.
> Unable to start slave mode after authentication failure on a previous startSlave attempt
> ----------------------------------------------------------------------------------------
>
> Key: DERBY-3549
> URL: https://issues.apache.org/jira/browse/DERBY-3549
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.0.0, 10.5.0.0
> Reporter: V.Narayanan
> Assignee: Jørgen Løland
> Fix For: 10.4.1.0, 10.5.0.0
>
> Attachments: derby-3549-1a.diff, derby-3549-1a.stat, derby-3549-1b.diff, derby-3549-1b.stat
>
>
> Trying a startSlave after an initial startSlave fails due to an authentication failure throws an error
> saying that the database has already been booted
> vn@vn-laptop:~/work/workspaces/freshworkspace/slave$ java org.apache.derby.tools.ij
> ij version 10.5
> ij> connect 'jdbc:derby:mydb;startSlave=true;slaveHost=localhost;slavePort=8001';
> ERROR 08004: Connection authentication failure occurred. Reason: Invalid authentication..
> ij> connect 'jdbc:derby:mydb;startSlave=true;user=oystein;password=pass;slaveHost=localhost;slavePort=8001';
> ERROR XRE09: Cannot start replication slave mode for database 'mydb'. The database has already been booted.
> ij>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3549) Unable to start slave mode after
authentication failure on a previous startSlave attempt
Posted by "Jørgen Løland (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jørgen Løland updated DERBY-3549:
---------------------------------
Derby Info: [Patch Available]
> Unable to start slave mode after authentication failure on a previous startSlave attempt
> ----------------------------------------------------------------------------------------
>
> Key: DERBY-3549
> URL: https://issues.apache.org/jira/browse/DERBY-3549
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.0.0, 10.5.0.0
> Reporter: V.Narayanan
> Assignee: Jørgen Løland
> Attachments: derby-3549-1a.diff, derby-3549-1a.stat
>
>
> Trying a startSlave after an initial startSlave fails due to an authentication failure throws an error
> saying that the database has already been booted
> vn@vn-laptop:~/work/workspaces/freshworkspace/slave$ java org.apache.derby.tools.ij
> ij version 10.5
> ij> connect 'jdbc:derby:mydb;startSlave=true;slaveHost=localhost;slavePort=8001';
> ERROR 08004: Connection authentication failure occurred. Reason: Invalid authentication..
> ij> connect 'jdbc:derby:mydb;startSlave=true;user=oystein;password=pass;slaveHost=localhost;slavePort=8001';
> ERROR XRE09: Cannot start replication slave mode for database 'mydb'. The database has already been booted.
> ij>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.