You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2013/12/12 14:21:07 UTC
[jira] [Updated] (WSS-487) Certain action combinations causes WSS4J
to hang
[ https://issues.apache.org/jira/browse/WSS-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh updated WSS-487:
------------------------------------
Description:
Certain action combinations causes WSS4J to hang. For example, 2x Signatures or 2x Encrypt. See the following @Ignore'd tests to reproduce:
svn.apache.org/viewvc/webservices/wss4j/trunk/ws-security-stax/src/test/java/org/apache/wss4j/stax/test/MultipleActionTest.java?view=log
The corresponding jstack stacktraces are as follows:
"main" prio=10 tid=0x00007f2798007800 nid=0x25e9 runnable [0x00007f279f130000]
java.lang.Thread.State: RUNNABLE
at org.apache.xml.security.stax.ext.AbstractOutputProcessor.processNextEvent(AbstractOutputProcessor.java:130)
at org.apache.xml.security.stax.impl.OutputProcessorChainImpl.processEvent(OutputProcessorChainImpl.java:217)
at org.apache.xml.security.stax.ext.AbstractBufferingOutputProcessor.flushBufferAndCallbackAfterHeader(AbstractBufferingOutputProcessor.java:74)
at org.apache.wss4j.stax.impl.processor.output.WSSSignatureEndingOutputProcessor.flushBufferAndCallbackAfterHeader(WSSSignatureEndingOutputProcessor.java:272)
at org.apache.xml.security.stax.ext.AbstractBufferingOutputProcessor.doFinal(AbstractBufferingOutputProcessor.java:54)
"main" prio=10 tid=0x00007febd8007800 nid=0x2778 runnable [0x00007febde611000]
java.lang.Thread.State: RUNNABLE
at org.apache.xml.security.stax.impl.OutputProcessorChainImpl.processEvent(OutputProcessorChainImpl.java:200)
at org.apache.xml.security.stax.ext.AbstractBufferingOutputProcessor.flushBufferAndCallbackAfterHeader(AbstractBufferingOutputProcessor.java:74)
at org.apache.wss4j.stax.impl.processor.output.EncryptEndingOutputProcessor.flushBufferAndCallbackAfterHeader(EncryptEndingOutputProcessor.java:104)
at org.apache.xml.security.stax.ext.AbstractBufferingOutputProcessor.doFinal(AbstractBufferingOutputProcessor.java:54)
was:
Certain action combinations causes WSS4J to hang. For example, 2x Signatures or 2x Encrypt. See the following @Ignore'd tests to reproduce:
The corresponding jstack stacktraces are as follows:
"main" prio=10 tid=0x00007f2798007800 nid=0x25e9 runnable [0x00007f279f130000]
java.lang.Thread.State: RUNNABLE
at org.apache.xml.security.stax.ext.AbstractOutputProcessor.processNextEvent(AbstractOutputProcessor.java:130)
at org.apache.xml.security.stax.impl.OutputProcessorChainImpl.processEvent(OutputProcessorChainImpl.java:217)
at org.apache.xml.security.stax.ext.AbstractBufferingOutputProcessor.flushBufferAndCallbackAfterHeader(AbstractBufferingOutputProcessor.java:74)
at org.apache.wss4j.stax.impl.processor.output.WSSSignatureEndingOutputProcessor.flushBufferAndCallbackAfterHeader(WSSSignatureEndingOutputProcessor.java:272)
at org.apache.xml.security.stax.ext.AbstractBufferingOutputProcessor.doFinal(AbstractBufferingOutputProcessor.java:54)
"main" prio=10 tid=0x00007febd8007800 nid=0x2778 runnable [0x00007febde611000]
java.lang.Thread.State: RUNNABLE
at org.apache.xml.security.stax.impl.OutputProcessorChainImpl.processEvent(OutputProcessorChainImpl.java:200)
at org.apache.xml.security.stax.ext.AbstractBufferingOutputProcessor.flushBufferAndCallbackAfterHeader(AbstractBufferingOutputProcessor.java:74)
at org.apache.wss4j.stax.impl.processor.output.EncryptEndingOutputProcessor.flushBufferAndCallbackAfterHeader(EncryptEndingOutputProcessor.java:104)
at org.apache.xml.security.stax.ext.AbstractBufferingOutputProcessor.doFinal(AbstractBufferingOutputProcessor.java:54)
> Certain action combinations causes WSS4J to hang
> ------------------------------------------------
>
> Key: WSS-487
> URL: https://issues.apache.org/jira/browse/WSS-487
> Project: WSS4J
> Issue Type: Bug
> Reporter: Colm O hEigeartaigh
> Assignee: Marc Giger
> Fix For: 2.0
>
>
> Certain action combinations causes WSS4J to hang. For example, 2x Signatures or 2x Encrypt. See the following @Ignore'd tests to reproduce:
> svn.apache.org/viewvc/webservices/wss4j/trunk/ws-security-stax/src/test/java/org/apache/wss4j/stax/test/MultipleActionTest.java?view=log
> The corresponding jstack stacktraces are as follows:
> "main" prio=10 tid=0x00007f2798007800 nid=0x25e9 runnable [0x00007f279f130000]
> java.lang.Thread.State: RUNNABLE
> at org.apache.xml.security.stax.ext.AbstractOutputProcessor.processNextEvent(AbstractOutputProcessor.java:130)
> at org.apache.xml.security.stax.impl.OutputProcessorChainImpl.processEvent(OutputProcessorChainImpl.java:217)
> at org.apache.xml.security.stax.ext.AbstractBufferingOutputProcessor.flushBufferAndCallbackAfterHeader(AbstractBufferingOutputProcessor.java:74)
> at org.apache.wss4j.stax.impl.processor.output.WSSSignatureEndingOutputProcessor.flushBufferAndCallbackAfterHeader(WSSSignatureEndingOutputProcessor.java:272)
> at org.apache.xml.security.stax.ext.AbstractBufferingOutputProcessor.doFinal(AbstractBufferingOutputProcessor.java:54)
> "main" prio=10 tid=0x00007febd8007800 nid=0x2778 runnable [0x00007febde611000]
> java.lang.Thread.State: RUNNABLE
> at org.apache.xml.security.stax.impl.OutputProcessorChainImpl.processEvent(OutputProcessorChainImpl.java:200)
> at org.apache.xml.security.stax.ext.AbstractBufferingOutputProcessor.flushBufferAndCallbackAfterHeader(AbstractBufferingOutputProcessor.java:74)
> at org.apache.wss4j.stax.impl.processor.output.EncryptEndingOutputProcessor.flushBufferAndCallbackAfterHeader(EncryptEndingOutputProcessor.java:104)
> at org.apache.xml.security.stax.ext.AbstractBufferingOutputProcessor.doFinal(AbstractBufferingOutputProcessor.java:54)
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org