[ http://issues.apache.org/jira/browse/DERBY-1425?page=comments#action_12417731 ]
Knut Anders Hatlen commented on DERBY-1425: ------------------------------------------- Yes, the test still fails, but I don't think a separate issue is needed since the test should fail in a mixed environment. It does not test whether the client works, but whether the server responds exactly the way a 10.1 server would. One might even argue that derbynetmats/derbynetclientmats is not the correct suite for this test since it neither uses the client driver nor JCC. > testProtocol hangs with 10.1 client talking to 10.2 server > ---------------------------------------------------------- > > Key: DERBY-1425 > URL: http://issues.apache.org/jira/browse/DERBY-1425 > Project: Derby > Type: Bug > Components: Network Server, Network Client > Versions: 10.2.0.0 > Reporter: Bryan Pendleton > Priority: Minor > Attachments: ddmreader_initialize.diff > > I was trying to verify that the changes in DERBY-920 hadn't > introduced any new compatibility problems (they shouldn't, because > we were changing an internal class, but I wanted to make sure). > So I was trying to follow some old tips about how to run tests with > an old client against a new server, as documented in: > http://wiki.apache.org/db-derby/TestingOldClientNewServer > However, when I did this, the test "testProtocol" did not terminate. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
