db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1425) testProtocol hangs with 10.1 client talking to 10.2 server
Date Sun, 25 Jun 2006 18:38:31 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1425?page=comments#action_12417691 ] 

Knut Anders Hatlen commented on DERBY-1425:

Hi Bryan, the patch is for the 10.2 network server. When you are running derbynetclientmats
with the configuration you have described in http://wiki.apache.org/db-derby/TestingOldClientNewServer,
testProtocol from the 10.1 derbyTesting.jar is used, but it extends the TestProto class found
in the 10.2 derbynet.jar, which again uses DDMReader/DDMWriter in the 10.2 derbynet.jar to
communicate with the server. So, in a way, you are running 10.2 network server code both on
the client side and on the server side, but the actual commands are read from 10.1 test code.
Does this make you less confused? :)

Note that I'm pretty sure this particular hang cannot occur in the network server itself.
When a new session is started, DRDAConnThread.processCommands() begins a loop reading commands
and writing responses. It always calls DDMReader.readDssHeader() before writing anything back
to the client. readDssHeader() explicitly sets the values of dssIsChainedWithSameID and dssIsChainedWithDiffID.
Since the hang was caused by those two variables having values from the previous session when
the first flush occurred, I don't see how it could happen on the server.

> 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:
>     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:
For more information on JIRA, see:

View raw message