[
https://issues.apache.org/jira/browse/DERBY-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903094#action_12903094
]
Kathey Marsden commented on DERBY-3644:
---------------------------------------
Thank you Mamta for looking at this issue. It would seem the PROTOCOL_VERSION
is not very helpful with a newer client because there is no handshake in the
protocol to negotiate down. I guess in retrospect it would have been better to
just have a new COMMAND_SHUTDOWN_USER_PASS command for DERBY-2109 and leave the
old one alone, but I think to fix this issue maybe the following approach might
work.
1) Send protocol version 1 for all the unchanged commands.
2) For shutdown, If no user/password are specified, first do a ping which
will get a reply header from the server so we can see its protocol version.
Then send version 1 (no user/pass) or version 2 (user/pass) as appropriate.
3) If user/password are specified, just send version 2 format.
4) Change COMMAND_SHUTDOWN parsing to do the right thing for protocol version
1 vs 2.
Shutdown will have an extra round trip, but I think all the commands should
work.
> 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.
