db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-1425) testProtocol hangs with 10.1 client talking to 10.2 server
Date Wed, 07 Jul 2010 07:41:49 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Knut Anders Hatlen resolved DERBY-1425.

    Fix Version/s:
       Resolution: Fixed

All the regression tests ran cleanly. Committed revision 961271.

I'm not planning to back-port the fix. It's most likely harmless, but since the analysis so
far suggests that this is not a problem that will be seen when using the client driver to
talk to the server, it's probably not worth the effort to back-port it.

> 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:
>            Reporter: Bryan Pendleton
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For:
>         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.

View raw message