axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepal Jayasinghe (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (AXIS2-866) Axis Client not threadsafe when signing/timestamp enabled
Date Thu, 06 Jul 2006 11:45:31 GMT
     [ http://issues.apache.org/jira/browse/AXIS2-866?page=all ]

Deepal Jayasinghe reassigned AXIS2-866:
---------------------------------------

    Assign To: Ruchith Udayanga Fernando

> Axis Client not threadsafe when signing/timestamp enabled
> ---------------------------------------------------------
>
>          Key: AXIS2-866
>          URL: http://issues.apache.org/jira/browse/AXIS2-866
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug

>   Components: client-api
>     Versions: 1.0
>  Environment: Windows 2000
> java version "1.4.2_04"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
> Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)
>     Reporter: Halvard Martinsen
>     Assignee: Ruchith Udayanga Fernando
>     Priority: Blocker

>
> Starts simulations threads invoking a service that requires signing/timestamp (Client
code generate with xmlbeans binding)
> Creates ConfigurationContext and stub as static variables in a synchronized block used
by both threads
> Received the following stacktraces (depending on the order of the threads that starts)
> org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR: A node is used in a different document
than the one that created it.
> 	at org.apache.axiom.om.impl.dom.ParentNode.insertBefore(ParentNode.java:160)
> 	at org.apache.ws.security.util.WSSecurityUtil.prependChildElement(WSSecurityUtil.java:588)
> 	at org.apache.ws.security.message.WSSecSignature.prependToHeader(WSSecSignature.java:561)
> 	at org.apache.ws.security.message.WSSecSignature.build(WSSecSignature.java:658)
> 	at org.apache.ws.security.action.SignatureAction.execute(SignatureAction.java:54)
> 	at org.apache.ws.security.handler.WSHandler.doSenderAction(WSHandler.java:191)
> 	at org.apache.axis2.security.WSDoAllSender.processMessage(WSDoAllSender.java:181)
> 	at org.apache.axis2.security.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:82)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:473)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:572)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:328)
> 	at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:279)
>  
> or 
> java.lang.NullPointerException
> 	at org.apache.axis2.security.WSDoAllSender.processMessage(WSDoAllSender.java:197)
> 	at org.apache.axis2.security.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:82)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:473)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:572)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:328)
> 	at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:279)
> Changing the requirements for Security, that is, no signing or timestamp at the service
and consumer side, makes my client handles threads perfectly.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message