[ 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? 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, 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
