You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Sandip Ghayal (JIRA)" <de...@geronimo.apache.org> on 2005/01/27 15:25:17 UTC
[jira] Created: (GERONIMO-553) Security Timeout Test failures
Security Timeout Test failures
------------------------------
Key: GERONIMO-553
URL: http://issues.apache.org/jira/browse/GERONIMO-553
Project: Apache Geronimo
Type: Improvement
Components: security
Environment: Windows XP
Reporter: Sandip Ghayal
Priority: Minor
Attachments: security_Timout_fix.patch
When during Geronimo Build I found the Security test failures for Timeout Test.
During investigation what I found was my login context was being dropped during running of the test. When investigating further I found that the timeout was set to one second. Where as the next request came after 1.2 secs (though the sleep in the test was for 300 ms).
I think that the time out values and machine speed is too critical for this test to work with such precisions. So I propose to increase the timeout value to 10 secs and increase the sleep times within the test to 3 secs and 17 secs. (just multiplied all times by 10).
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-553) Security Timeout Test failures
Posted by "Alan Cabrera (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-553?page=comments#action_58168 ]
Alan Cabrera commented on GERONIMO-553:
---------------------------------------
50ms timeout scan? Yikes, that means that slower computers will be doing nothing but scanning. Can you revert the parameters for the test back and set the timeout scan to 100ms and see if it passes?
> Security Timeout Test failures
> ------------------------------
>
> Key: GERONIMO-553
> URL: http://issues.apache.org/jira/browse/GERONIMO-553
> Project: Apache Geronimo
> Type: Improvement
> Components: security
> Environment: Windows XP
> Reporter: Sandip Ghayal
> Priority: Minor
> Attachments: security_Timout_fix.patch, security_Timout_fix.patch
>
> When during Geronimo Build I found the Security test failures for Timeout Test.
> During investigation what I found was my login context was being dropped during running of the test. When investigating further I found that the timeout was set to one second. Where as the next request came after 1.2 secs (though the sleep in the test was for 300 ms).
> I think that the time out values and machine speed is too critical for this test to work with such precisions. So I propose to increase the timeout value to 10 secs and increase the sleep times within the test to 3 secs and 17 secs. (just multiplied all times by 10).
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-553) Security Timeout Test failures
Posted by "Sandip Ghayal (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-553?page=history ]
Sandip Ghayal updated GERONIMO-553:
-----------------------------------
Attachment: security_Timout_fix.patch
To reduce the test times I have reduced the timeout and sleep values in the test
New Context Timeout value = 5 secs
New Sleep 1 value = 3 secs
New Sleep 2 value = 7 secs
We can also modify login timeout scan intervals (which is currently at 50ms. But it should not afect the time take to run the tests.
> Security Timeout Test failures
> ------------------------------
>
> Key: GERONIMO-553
> URL: http://issues.apache.org/jira/browse/GERONIMO-553
> Project: Apache Geronimo
> Type: Improvement
> Components: security
> Environment: Windows XP
> Reporter: Sandip Ghayal
> Priority: Minor
> Attachments: security_Timout_fix.patch, security_Timout_fix.patch
>
> When during Geronimo Build I found the Security test failures for Timeout Test.
> During investigation what I found was my login context was being dropped during running of the test. When investigating further I found that the timeout was set to one second. Where as the next request came after 1.2 secs (though the sleep in the test was for 300 ms).
> I think that the time out values and machine speed is too critical for this test to work with such precisions. So I propose to increase the timeout value to 10 secs and increase the sleep times within the test to 3 secs and 17 secs. (just multiplied all times by 10).
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-553) Security Timeout Test failures
Posted by "Gianny DAMOUR (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-553?page=comments#action_60704 ]
Gianny DAMOUR commented on GERONIMO-553:
----------------------------------------
Quick follow up.
Sandip, could you please tell us what is the current status for this issue?
Alan suggested:
"
50ms timeout scan? Yikes, that means that slower computers will be doing nothing but scanning. Can you revert the parameters for the test back and set the timeout scan to 100ms and see if it passes?
"
Thanks.
> Security Timeout Test failures
> ------------------------------
>
> Key: GERONIMO-553
> URL: http://issues.apache.org/jira/browse/GERONIMO-553
> Project: Geronimo
> Type: Improvement
> Components: security
> Environment: Windows XP
> Reporter: Sandip Ghayal
> Priority: Minor
> Attachments: security_Timout_fix.patch, security_Timout_fix.patch
>
> When during Geronimo Build I found the Security test failures for Timeout Test.
> During investigation what I found was my login context was being dropped during running of the test. When investigating further I found that the timeout was set to one second. Where as the next request came after 1.2 secs (though the sleep in the test was for 300 ms).
> I think that the time out values and machine speed is too critical for this test to work with such precisions. So I propose to increase the timeout value to 10 secs and increase the sleep times within the test to 3 secs and 17 secs. (just multiplied all times by 10).
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-553) Security Timeout Test failures
Posted by "Sandip Ghayal (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-553?page=history ]
Sandip Ghayal updated GERONIMO-553:
-----------------------------------
Attachment: security_Timout_fix.patch
I have created patch for this and tested it to be working. Please find attached file for the fix
> Security Timeout Test failures
> ------------------------------
>
> Key: GERONIMO-553
> URL: http://issues.apache.org/jira/browse/GERONIMO-553
> Project: Apache Geronimo
> Type: Improvement
> Components: security
> Environment: Windows XP
> Reporter: Sandip Ghayal
> Priority: Minor
> Attachments: security_Timout_fix.patch
>
> When during Geronimo Build I found the Security test failures for Timeout Test.
> During investigation what I found was my login context was being dropped during running of the test. When investigating further I found that the timeout was set to one second. Where as the next request came after 1.2 secs (though the sleep in the test was for 300 ms).
> I think that the time out values and machine speed is too critical for this test to work with such precisions. So I propose to increase the timeout value to 10 secs and increase the sleep times within the test to 3 secs and 17 secs. (just multiplied all times by 10).
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-553) Security Timeout Test failures
Posted by "Alan Cabrera (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-553?page=history ]
Alan Cabrera closed GERONIMO-553:
---------------------------------
Resolution: Fixed
Thanks Sandip.
> Security Timeout Test failures
> ------------------------------
>
> Key: GERONIMO-553
> URL: http://issues.apache.org/jira/browse/GERONIMO-553
> Project: Geronimo
> Type: Improvement
> Components: security
> Environment: Windows XP
> Reporter: Sandip Ghayal
> Priority: Minor
> Attachments: security_Timout_fix.patch, security_Timout_fix.patch
>
> When during Geronimo Build I found the Security test failures for Timeout Test.
> During investigation what I found was my login context was being dropped during running of the test. When investigating further I found that the timeout was set to one second. Where as the next request came after 1.2 secs (though the sleep in the test was for 300 ms).
> I think that the time out values and machine speed is too critical for this test to work with such precisions. So I propose to increase the timeout value to 10 secs and increase the sleep times within the test to 3 secs and 17 secs. (just multiplied all times by 10).
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira