db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1080) Connection reset when using security mechanism=EUSRIDPWD results in protocol error.
Date Mon, 13 Mar 2006 22:27:39 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1080?page=all ]

Bryan Pendleton updated DERBY-1080:

    Attachment: derby-1080-testSecMec.tmp

Sunitha, I had a strange failure in testSecMec in the DerbyNet framework.

This is on Linux, using Sun JDK 1.4, when I ran all of derbyall.

I have attached the testSecMec.tmp file. Basically, the output just ceased at line 28, with
no other error messages that I can find.

I re-ran the test 5 or 6 times as a single test (-Dframework=DerbyNet derbynet/testSecMec.java)
and I reran the derbynetmats suite with the DerbyNet framework.

During the various re-runs, the test failed again the same way exactly once.

So, there seems to be some sort of a very intermittent failure, but I cannot reproduce it.

Does this make sense to you? Can you look at the attached testSecMec.tmp and tell me whether
you have a theory for why I might have seen this very intermittent failure? Is there something
that might be causing the test program to quit without flushing its output buffer?



> 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:,,,,,,,
>     Reporter: Sunitha Kambhampati
>     Assignee: Sunitha Kambhampati
>      Fix For:
>  Attachments: Derby1080.diff.txt, Derby1080.stat.txt, derby-1080-testSecMec.tmp, derby1080.2.diff.txt,
> 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:
For more information on JIRA, see:

View raw message