[
https://issues.apache.org/jira/browse/DERBY-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen reassigned DERBY-1425:
-----------------------------------------
Assignee: Knut Anders Hatlen
There has been no activity on this bug for four years, but there's a patch
attached. I think we should either see if we could get the patch committed or
close the bug as Won't Fix. I'll have a look. Intuitively, clearing the two
flags on reinitialization sounds correct, so my intention is to commit it if
the tests still pass.
> 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
>
>
> 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.
