[wsf-c-dev] [jira] Commented: (WSFRUBY-34) RC3: signing_client sample fail due to server cache issue

[Ruwan Janapriya (JIRA)]

    [ https://wso2.org/jira/browse/WSFRUBY-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416#action_16416 ] 

Ruwan Janapriya commented on WSFRUBY-34:
----------------------------------------

In the current implementation the above bug, could not be simulated. It seems like the above bug is automatically fixed while resolving another issue. So this will be marked as INVALID.

> RC3: signing_client sample fail due to server cache issue
> ---------------------------------------------------------
>
>                 Key: WSFRUBY-34
>                 URL: https://wso2.org/jira/browse/WSFRUBY-34
>             Project: WSO2 WSF/Ruby
>          Issue Type: Bug
>         Environment: Ubuntu 7.10
>            Reporter: Krishantha Samaraweera
>            Assignee: Ruwan Janapriya
>
> signing_client_file.rb sample failed with fault reason "Timestamp token required. Cannot find in the security header". This happens after running the timestamp samples and try to invoke signing samples. once I restart the ruby server signing_client works fine.
> step to recreate:
> 1. start ruby server
> 2. run timestamp samples
> 3. then run signing samples.( sample will fail)
> 4. now restart ruby server
> 5. again run signing samples (sample will pass)
> this seems to be common issue for other samples as well.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira