[ http://issues.apache.org/jira/browse/DERBY-1080?page=all ]
Sunitha Kambhampati updated DERBY-1080:
---------------------------------------
Attachment: DebugTest.diff.txt
derbyTesting.jar
I am attaching a DebugTest.diff.txt which adds some println statements to
testSecMec to see if the intermittent problem with the test is an issue with
the closing of System.out and System.err streams. I built the insane version
of derbyTesting.jar with this change in test. Bryan- if possible, can you run
this test with this change or using this derbyTesting.jar and see if it
reproduces. Thanks much.
Main logic for switching of System.out and System.err streams was added as
part of derby273 and then got merged with changes for derby 928. I'll study
that more and see if I can find something.
I ran the test separately with jdk141/win2k several times and the test passed
ok. I tried to run it about 15 times on a linux machine (2.6 kernel, redhat)
with sun 1.4.1 and the test passes.
java version "1.4.1_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_07-b02)
Java HotSpot(TM) Client VM (build 1.4.1_07-b02, mixed mode)
OS name: Linux
OS architecture: i386
OS version: 2.6.9-22.0.1.ELsmp
> 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
>
> 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
