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] Commented: (DERBY-1080) Connection reset when using security mechanism=EUSRIDPWD results in protocol error.
Date Tue, 14 Mar 2006 18:21:11 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1080?page=comments#action_12370382 ] 

Bryan Pendleton commented on DERBY-1080:

Sunitha, can you help me understand the purpose of the Thread.sleep(5000) line in testSecMec.java?
If I change that line from (5000) to (100), the problem becomes *much* more reproducible.

Is there a possibility that, on my machine, some action is sometimes taking longer than 5
seconds to perform, and so the problem is related to that sleep() call returning "too soon"?

In your environment, what happens if you change the Thread.sleep() call?



> 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: DebugTest.diff.txt, Derby1080.diff.txt, Derby1080.stat.txt, derby-1080-testSecMec.tmp,
derby1080.2.diff.txt, derby1080.2.stat.txt, derbyTesting.jar, premature_shutdown_derby.log,
premature_shutdown_sysinfo.out, 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:
For more information on JIRA, see:

View raw message