[ http://issues.apache.org/jira/browse/DERBY-1080?page=all ]
Bryan Pendleton updated DERBY-1080:
-----------------------------------
Attachment: testSecMec_with_prints.tmp
testSecMec.DerbyNet.shutdown.std.log_with_prints
The bug reproduces with the print statements in place, which I think is good,
so we can continue to diagnose it.
I've attached the new '.tmp' file with the output of a failed test with the
print statements in place, and also, this time, I am attaching the
'shutdown.std.log' file. In the past, this file has been 0 bytes after the run,
but this time it has 4 of the print statements in it.
Please let me know what additional information I can provide.
thanks,
bryan
> Connection reset when using security mechanism=EUSRIDPWD results in protocol
> error.
> -----------------------------------------------------------------------------------
>
> Key: DERBY-1080
> URL: http://issues.apache.org/jira/browse/DERBY-1080
> Project: Derby
> Type: Bug
> Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.1.1, 10.1.1.2, 10.1.2.0,
> 10.1.2.1, 10.1.2.2
> Reporter: Sunitha Kambhampati
> Assignee: Sunitha Kambhampati
> Fix For: 10.2.0.0
> Attachments: DebugTest.diff.txt, Derby1080.diff.txt, Derby1080.stat.txt,
> derby-1080-testSecMec.tmp, derby1080.2.diff.txt, derby1080.2.stat.txt,
> derbyTesting.jar, testSecMec.DerbyNet.shutdown.std.log_with_prints,
> testSecMec_with_prints.tmp
>
> if connection is reset, the security mechanism related information for
> EUSRIDPWD is not reset correctly and this leads to a protocol error.
--
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
