You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by "Pierre TON-THAT (JIRA)" <ji...@apache.org> on 2007/06/27 12:36:26 UTC
[jira] Issue Comment Edited: (SANDESHA2-90) Rampart 1.2 with
Sandesha2 1.2
[ https://issues.apache.org/jira/browse/SANDESHA2-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508499 ]
Pierre TON-THAT edited comment on SANDESHA2-90 at 6/27/07 3:36 AM:
-------------------------------------------------------------------
Running something like the sample policy 03 of Rampart package, with Axis2 1.2 + Rampart 1.2 + Sandesha2 1.2 (win32, Tomcat 5, JDK 1.4) with same final axisFault : "Sandesha2 could not send the message on sequence Sandesha2InternalSequence : [url of service] as the sequence has timed out."
With Rampart OR Sandesha2, engaged individually : it's working.
But I have other errors before that... (on the first run, not after a second test, in Eclipse console) :
GRAVE: Sandesha2 got an exception when sending a message: java.util.NoSuchElementException.
java.util.NoSuchElementException
at java.util.LinkedList.remove(Unknown Source)
at java.util.LinkedList.removeFirst(Unknown Source)
at org.apache.axis2.context.MessageContext.removeFirstOutboundExecutedPhase(MessageContext.java:669)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:218)
at org.apache.axis2.engine.AxisEngine.resumeSend(AxisEngine.java:318)
at org.apache.sandesha2.workers.SenderWorker.run(SenderWorker.java:258)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Unknown Source)
And I have something in the SOAPMonitor : the client seems to loop about 10 times with a new <wsrm:CreateSequence/> (and the service returns a <wsrm:CreateSequenceResponse/>, though the <wsrm:Identifier/> is not the same (should be it ?)), then Sandesha2 tells the sequence has timeout.
was:
Running something like the sample policy 03 of Rampart package, with Axis2 1.2 + Rampart 1.2 + Sandesha2 1.2 (win32, Tomcat 5, JDK 1.4) with same final axisFault : "Sandesha2 could not send the message on sequence Sandesha2InternalSequence : [url of service] as the sequence has timed out."
With Rampart OR Sandesha2, engaged individually : it's working.
But I have other errors before that... (on the first run, not after a second test, in Eclipse console) :
GRAVE: Sandesha2 got an exception when sending a message: java.util.NoSuchElementException.
java.util.NoSuchElementException
at java.util.LinkedList.remove(Unknown Source)
at java.util.LinkedList.removeFirst(Unknown Source)
at org.apache.axis2.context.MessageContext.removeFirstOutboundExecutedPhase(MessageContext.java:669)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:218)
at org.apache.axis2.engine.AxisEngine.resumeSend(AxisEngine.java:318)
at org.apache.sandesha2.workers.SenderWorker.run(SenderWorker.java:258)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Unknown Source)
And I have something in the SOAPMonitor : the client seems to loop about 10 times with a new <wsrm:CreateSequence/> (and the service returns a <wsrm:CreateSequenceResponse/>), then Sandesha2 tells the sequence has timeout.
> Rampart 1.2 with Sandesha2 1.2
> -------------------------------
>
> Key: SANDESHA2-90
> URL: https://issues.apache.org/jira/browse/SANDESHA2-90
> Project: Sandesha2
> Issue Type: Bug
> Environment: Windows XP, Tomcat 5.5
> Reporter: Ted Jones
> Attachments: 2806.zip, stacktrace.txt
>
>
> When engaging Rampart 1.2 with Sandesha2 1.2 in Axis 1.2, my client never returns and I see no messages in TCPMon. When these modules are engaged individually, they work as expected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org