db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3489) Error message XRE04 does not include the right port number.
Date Tue, 04 Mar 2008 03:34:50 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574829#action_12574829
] 

V.Narayanan commented on DERBY-3489:
------------------------------------

>Seems like the story is not that straight-forward as originally
>reported. It seems the problem is that theport number that is
>reported in the error message is not updated for subsequent requests. 

The issue is as simple as reported because the complicated part of the issue
that the port number is persistent is already handled by 3358.

I think,

* As a initial fix I guess the default port number value needs to be corrected.

* The code re-arrangement can be handled in a follow-up or a separate issue.

> Error message XRE04 does not include the right port number.
> -----------------------------------------------------------
>
>                 Key: DERBY-3489
>                 URL: https://issues.apache.org/jira/browse/DERBY-3489
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.0.0
>            Reporter: Øystein Grøvlen
>
> If the master is not able to connect to the slave, the error messages does not include
the right port number:
> ij> connect 'jdbc:derby:masterDB;user=oystein;password=pass;startMaster=true;slaveHost=localhost;slavePort=9901';
> ERROR XRE04: Could not establish a connection to the peer of the replicated database
'masterDB' on address 'localhost:-1'.

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


Mime
View raw message