[
https://issues.apache.org/jira/browse/DERBY-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701088#action_12701088
]
Knut Anders Hatlen commented on DERBY-3417:
-------------------------------------------
Making those exceptions session severity sounds like a good idea to me.
Since an exception thrown by getConnection() will always prevent the connection
from being established, perhaps it would be more robust if we made the server
pre-format all exceptions from getConnection() regardless of the stated
severity? Anyways, increasing the severity would be enough for the messages
found here, and it sounds like the right thing to do.
> slave side stop in a client server mode results in SQLState printed without
> proper error message
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-3417
> URL: https://issues.apache.org/jira/browse/DERBY-3417
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.1.3
> Reporter: V.Narayanan
> Assignee: Dag H. Wanvik
>
> I tried a stopSlave on the slave side of the replication system and
> found the below
> ij> connect 'jdbc:derby://localhost:1528/replicationdb;stopSlave=true';
> ERROR XRE41: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE41, SQLERRMC: XRE41
> https://issues.apache.org/jira/browse/DERBY-3205 says
> ERROR XRE41: Replication operation 'failover' or 'stopSlave' failed because
> the connection with the master is working. Issue the 'failover' or
> 'stopMaster' operation on the master database instead.
> needs to be printed.
> I am not sure if this is a generic case for client server replication
> messages.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
