[ http://issues.apache.org/jira/browse/DERBY-1425?page=comments#action_12416631 ]
Bryan Pendleton commented on DERBY-1425:
----------------------------------------
Comment from Knut Anders on derby-dev:
It seems like the hang is in fact caused by a bug in
DDMReader. dssIsChainedWithDiffID and dssIsChainedWithSameID are not
reset in initialize(), so values from a previous session might be
used. In this particular case, the old values made
DDMReader.getCurrChainState() return an incorrect value, which again
made calls to DDMWriter.finalizeChain() a no-op. The protocol test
therefore never sent the DRDA commands it thought it had sent, and
both sides ended up waiting for data from the other one.
It is not clear to me whether this bug actually can be triggered
outside the protocol test since the client driver doesn't use
DDMReader/DDMWriter. The way DRDAConnThread uses those classes should
be safe, as the server always reads a command before responding and
the fields seem to be set to reasonable values at each read.
Anyway, setting those two fields to false in DDMReader.initialize()
made the hang go away, and derbynetclientmats runs cleanly with that
change.
> 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
>
> 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