[
https://issues.apache.org/jira/browse/DERBY-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-3644:
--------------------------------------
Affects Version/s: 10.4.1.3
10.4.2.0
I think this is a regression. I've tested that NetworkServerControl from
10.4.1.3, 10.4.2.0 and 10.5.1.1 can't talk to a 10.3.3.0 (or earlier) server.
Tried runtimeinfo, ping and shutdown.
If we decide that this regression is acceptable (the workaround is simple
enough: don't use derbynet.jar>=10.4 to talk to server<10.4) we should at least
make the compatibility tests run cleanly.
> 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.
