[
https://issues.apache.org/jira/browse/DERBY-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904238#action_12904238
]
Mamta A. Satoor commented on DERBY-3644:
----------------------------------------
Just commited a change into trunk with revision 990841 which has reverted back
the prtocol level back to 1. I will create another jira for shutdown issue and
look into that.
the commit comments were as follows
DERBY-3644 and DERBY-2109
As part of DERBY-2109, shutdown command started accepting optional user name
and password. Bacause of this change in command, the protcol level was bumped
up to 2. But this caused all the network server commands from clients with
DERBY-2109 changes to break against a server without the DERBY-2109 changes.
That is because the server checks the protocol level of the client commands and
if they do match with server protocol version, then server will simply throw an
exception about mistmatch of protocol levels and thus causing all the client
commands from post DERBY-2109 clients to break against server with
pre-DERBY-2109 changes.
Will create another jira to handle the shutdown command's optional user name
and password parameters.
> NetworkServerControl.ping() on trunk against 10.3.2.1 and older servers give
> 'DRDA_InvalidReplyHeader2.S:Invalid reply header from network server: Invalid
> string . Plaintext connection attempt to an SSL enabled server?'
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3644
> URL: https://issues.apache.org/jira/browse/DERBY-3644
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.4.1.3, 10.4.2.0, 10.5.1.1
> Environment: All
> Reporter: Ole Solberg
>
> Since 2008-02-29 r632502(DERBY-2109) the compatibility tests run on trunk has
> reported
> 'DRDA_InvalidReplyHeader2.S:Invalid reply header from network server: Invalid
> string . Plaintext connection attempt to an SSL enabled server?'
> when doing NetworkServerControl.ping() on trunk against 10.3.2.1 and older
> servers.
> Is this a regression or according to spec?
> The compatibility test itself, i.e. the client-server testing is OK.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
