Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1385353143.1206621924942.JavaMail.jira@brutus>
Date: Thu, 27 Mar 2008 05:45:24 -0700 (PDT)
From: =?utf-8?Q?J=C3=B8rgen_L=C3=B8land_=28JIRA=29?= <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-3417) slave side stop in a client server
 mode results in SQLState printed without proper error message
In-Reply-To: <25294191.1202984349407.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/DERBY-3417?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1258=
2629#action_12582629 ]=20

J=C3=B8rgen L=C3=B8land commented on DERBY-3417:
--------------------------------------

I'm not sure this can be solved. AFAIK, the client normally gets the error =
message from the server using the jdbc connection. In this case, however, t=
here is no open connection, and the client is therefore unable to get the e=
rror message from the server.

> slave side stop in a client server mode results in SQLState printed witho=
ut 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.0.0
>            Reporter: V.Narayanan
>
> I tried a stopSlave on the slave side of the replication system and
> found the below
> ij> connect 'jdbc:derby://localhost:1528/replicationdb;stopSlave=3Dtrue';
> ERROR XRE41: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE41, SQLERRMC: XRE=
41
> https://issues.apache.org/jira/browse/DERBY-3205 says
> ERROR XRE41: Replication operation 'failover' or 'stopSlave' failed becau=
se the connection with the master is working. Issue the 'failover' or 'stop=
Master' operation on the master database instead.
> needs  to be printed.
> I am not sure if this is a generic case for client server replication mes=
sages.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.