[
https://issues.apache.org/jira/browse/DERBY-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-1425:
--------------------------------------
Attachment: test.diff
Attaching a patch which makes derbynet/testProtocol.java expose the hang. The
patch inserts a test case right before the one Bryan saw hanging, and that new
test case executes VALUES 1 without reading the last DSS which contains QRYDTA.
This gets DDMReader into the problematic state seen with the 10.1 version of
the protocol test, and the next test case hangs. With the suggested fix in
DDMReader's initialize() method, testProtocol completes successfully.
> testProtocol hangs with 10.1 client talking to 10.2 server
> ----------------------------------------------------------
>
> Key: DERBY-1425
> URL: https://issues.apache.org/jira/browse/DERBY-1425
> Project: Derby
> Issue Type: Bug
> Components: Network Client, Network Server
> Affects Versions: 10.2.1.6
> Reporter: Bryan Pendleton
> Assignee: Knut Anders Hatlen
> Priority: Minor
> Attachments: ddmreader_initialize.diff, test.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.
-
You can reply to this email to add a comment to the issue online.
