You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-c-dev@ws.apache.org by "S.Uthaiyashankar (JIRA)" <ji...@apache.org> on 2007/10/12 12:40:50 UTC
[jira] Updated: (RAMPARTC-35) Replay detection doesn't work with
Apache web server
[ https://issues.apache.org/jira/browse/RAMPARTC-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
S.Uthaiyashankar updated RAMPARTC-35:
-------------------------------------
Attachment: replay_detection_crash.patch
while trying this issue, I found another problem. When using replay detection with apache server, second request per each thread caused the thread to crash. The reason is, the container used to hold the keys to detect replay is created in request's pool. This pool is freed after serving the request. The next request access the same container and caused the crash. Attached patch is solving this issue.
> Replay detection doesn't work with Apache web server
> ----------------------------------------------------
>
> Key: RAMPARTC-35
> URL: https://issues.apache.org/jira/browse/RAMPARTC-35
> Project: Rampart/C
> Issue Type: Bug
> Components: Rampart-core
> Affects Versions: 1.0.0
> Environment: UNIX/Win32, Apache web server
> Reporter: Malinda Kaushalye Kapuruge
> Assignee: Malinda Kaushalye Kapuruge
> Fix For: 1.1.0
>
> Attachments: replay_detection_crash.patch
>
>
> Replay detection functionality in Rampart/C has threrading problems with the Apache web server. We need to fix it before 1.1.0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.