[jira] Updated: (SANTUARIO-245) IdResolver Java API extension

["Colm O hEigeartaigh (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SANTUARIO-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh updated SANTUARIO-245:
------------------------------------------

    Fix Version/s: Java 1.4.4
         Assignee:     (was: XML Security Developers Mailing List)

> IdResolver Java API extension
> -----------------------------
>
>                 Key: SANTUARIO-245
>                 URL: https://issues.apache.org/jira/browse/SANTUARIO-245
>             Project: Santuario
>          Issue Type: Bug
>          Components: Java
>    Affects Versions: Java 1.4.2
>         Environment: Operating System: All
> Platform: PC
>            Reporter: Stefan Vladov
>             Fix For: Java 1.4.4
>
>         Attachments: xmlsec_IdReslover.txt
>
>
> Created an attachment (id=26110)
> Proposed patch.
> I would like to suggest an extension to the xmlsec java API, namely to add a static method like unregisterDocument to org.apache.xml.security.utils.IdResolver to remove adocument from the static "docMap" WeakHashMap. Under long running high load test after some time we are experiencing a hangup with all the worker threads in the following state:
> "HTTP Handler 10.20.32.55" Id=185 in RUNNABLE
>  at java.util.WeakHashMap.get(WeakHashMap.java:355)
>  at org.apache.xml.security.utils.IdResolver.registerElementById(Unknown Source)
>  at org.apache.xml.security.signature.XMLSignature.setId(Unknown Source)
>  at org.apache.ws.security.message.WSSecSignature.prepare(WSSecSignature.java:360)
>  at org.apache.rampart.builder.BindingBuilder.getSignatureBuider(BindingBuilder.java:387)
>  at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignature(AsymmetricBindingBuilder.java:716)
>  at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:433)
>  at org.apache.rampart.builder.AsymmetricBindingBuilder.build(AsymmetricBindingBuilder.java:95)
>  at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:147)
>  at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:79)
>  at org.apache.axis2.engine.Phase.invoke(Phase.java:325)
>  at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264)
>  at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:429)
> With manual cleanup of the weak has map this situation is avoided.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.