[
https://issues.apache.org/jira/browse/SANDESHA2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745856#action_12745856
]
Dave Parsons commented on SANDESHA2-197:
----------------------------------------
Hi Patrice,
In fact you could use the JIRA you raised that started this discussion
thread. It's probably worth changing the abstract to say that you are
using Axis2 1.4 with Sandesha2 1.3 and that in this specific scenario (RM
1.1 with MakeConn) you are seeing the issue whereby the MakeConn anonymous
address isn't being registered with Axis2 as an anonymous address so the
createSeqResponse cannot be sent back to the client.
Did you try the same scenario and get any success with Axis 1.3 or even
Axis 1.5?
Regards,
Dave
Dave Parsons
Web Services Development
INTERNAL: David Parsons1/UK/i...@ibmgb :: DE3F20 :: 246930
EXTERNAL: parso...@uk.ibm.com :: (01962) 816930
Mail Point 211, IBM Hursley Park, Winchester. SO21 2JN
From:
"patrice aubry (JIRA)" <j...@apache.org>
To:
sandesha-dev@ws.apache.org
Date:
21/08/2009 09:24
Subject:
[jira] Commented: (SANDESHA2-197) CreateSequence response is actually sent
to the anonymous makeconnection url (i.e. http//:docs.oasis-open.org/.....
???
[
https://issues.apache.org/jira/browse/SANDESHA2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745836#action_12745836
]
patrice aubry commented on SANDESHA2-197:
-----------------------------------------
Hello Dave,
Should I create a new issue stating that Sandesha2 does not work with
Axis2 1.4 ?
Thanks,
Patrice
--- On Thu, 8/20/09, Dave Parsons (JIRA) <j...@apache.org> wrote:
From: Dave Parsons (JIRA) <j...@apache.org>
Subject: [jira] Commented: (SANDESHA2-197) CreateSequence response is
actually sent to the anonymous makeconnection url (i.e.
http//:docs.oasis-open.org/..... ???
To: pnau...@yahoo.com
Date: Thursday, August 20, 2009, 5:23 PM
[
https://issues.apache.org/jira/browse/SANDESHA2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745457#action_12745457
]
Dave Parsons commented on SANDESHA2-197:
----------------------------------------
Hi Patrice,
Apologies I thought you were running Axis2 1.3 with Sandesha 1.3.
Nevertheless I thought Sandesha 1.3 would work with Axis2 1.4, maybe it
doesn't for the RM 1.1 scenario you are trying. You could try moving back
to Axis 1.3.
Regards
Dave
Dave Parsons
Web Services Development
INTERNAL: David Parsons1/UK/i...@ibmgb :: DE3F20 :: 246930
EXTERNAL: parso...@uk.ibm.com :: (01962) 816930
Mail Point 211, IBM Hursley Park, Winchester. SO21 2JN
From:
"patrice aubry (JIRA)" <j...@apache.org>
To:
sandesha-dev@ws.apache.org
Date:
19/08/2009 17:43
Subject:
[jira] Commented: (SANDESHA2-197) CreateSequence response is actually sent
to the anonymous makeconnection url (i.e. http//:docs.oasis-open.org/.....
???
[
https://issues.apache.org/jira/browse/SANDESHA2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745115#action_12745115
]
patrice aubry commented on SANDESHA2-197:
-----------------------------------------
Hi Dave,
The axis2.log I sent you was generated in debug mode. I don't know how to
give you more than that. If you do, please let me know.
Please answer the following question: Do you have a simple service/client
pair that runs under V1_1 with Axis2 1.4 ?
I have suspicion that Sandesha2 does not work well (or at all) in V1_1
mode, at least with Axis2 1.4
Cheers,
Patrice
--- On Wed, 8/19/09, Dave Parsons (JIRA) <j...@apache.org> wrote:
From: Dave Parsons (JIRA) <j...@apache.org>
Subject: [jira] Commented: (SANDESHA2-197) CreateSequence response is
actually sent to the anonymous makeconnection url (i.e.
http//:docs.oasis-open.org/..... ???
To: pnau...@yahoo.com
Date: Wednesday, August 19, 2009, 3:00 PM
[
https://issues.apache.org/jira/browse/SANDESHA2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745040#action_12745040
]
Dave Parsons commented on SANDESHA2-197:
----------------------------------------
Hi Patrice,
My mistake, it is set by default. It all looks like your module.xml is
correct. I think we need to get Axis2 & Sandesha trace so that we can see
what's going on. I'd expect to see Axis2 register the MC annon EndPoint
so that it sees it as an anonymous EndPoint. This obviously isn't
happening and i'm not sure why as your setup seems sound.
Could you collect this trace. I'd be happy to take a look.
Dave
Dave Parsons
Web Services Development
INTERNAL: David Parsons1/UK/i...@ibmgb :: DE3F20 :: 246930
EXTERNAL: parso...@uk.ibm.com :: (01962) 816930
Mail Point 211, IBM Hursley Park, Winchester. SO21 2JN
From:
"patrice aubry (JIRA)" <j...@apache.org>
To:
sandesha-dev@ws.apache.org
Date:
19/08/2009 08:41
Subject:
[jira] Commented: (SANDESHA2-197) CreateSequence response is actually sent
to the anonymous makeconnection url (i.e. http//:docs.oasis-open.org/.....
???
[
https://issues.apache.org/jira/browse/SANDESHA2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744941#action_12744941
]
patrice aubry commented on SANDESHA2-197:
-----------------------------------------
Hi Dave,
Here's my module.xml pulled straight out of the sandesha2-1.3.mar and it
has 1.1 enabled :
======================================
<module name="sandesha2" class="org.apache.sandesha2.SandeshaModule">
<Description>
This module implements WS-ReliableMessaging for Axis2. This implements
both the WSRM submitted spec and up to the version CD4 of the new WSRM 1.1
spec.
</Description>
<InFlow>
<handler name="SandeshaGlobalInHandler"
class="org.apache.sandesha2.handlers.SandeshaGlobalInHandler">
<!-- Global In handler should come before addressing dispatching -->
<order phase="Dispatch" phaseFirst="true"/>
</handler>
<handler name="MessageContextCorrectionHandler"
class="org.apache.sandesha2.handlers.MessageContextCorrectionHandler">
<!-- A handler which handle the duplicate messages -->
<order phase="Transport"/>
</handler>
<handler name="SequenceIDDispatcher"
class="org.apache.sandesha2.handlers.SequenceIDDispatcher">
<order phase="Addressing" before="AddressingBasedDispatcher" />
</handler>
<handler name="SandeshaInHandler"
class="org.apache.sandesha2.handlers.SandeshaInHandler">
<order phase="RMPhase"/>
</handler>
</InFlow>
<OutFlow>
<handler name="SandeshaOutHandler"
class="org.apache.sandesha2.handlers.SandeshaOutHandler">
<order phase="RMPhase"/>
</handler>
</OutFlow>
<InFaultFlow>
<handler name="SandeshaGlobalInHandler"
class="org.apache.sandesha2.handlers.SandeshaGlobalInHandler">
<!-- Global In handler should come before instance dispatching -->
<order phase="Dispatch" before="InstanceDispatcher" />
</handler>
<handler name="SandeshaInHandler"
class="org.apache.sandesha2.handlers.SandeshaInHandler">
<order phase="RMPhase"/>
</handler>
</InFaultFlow>
<OutFaultFlow>
<handler name="SandeshaOutHandler"
class="org.apache.sandesha2.handlers.SandeshaOutHandler">
<order phase="RMPhase"/>
</handler>
</OutFaultFlow>
<operation name="Sandesha2OperationInOnly" mep="
http://www.w3.org/2006/01/wsdl/in-only";>
<messageReceiver
class="org.apache.sandesha2.msgreceivers.RMMessageReceiver"/>
<!-- namespaces for the 2005-02 spec -->
<actionMapping>
http://schemas.xmlsoap.org/ws/2005/02/rm/SequenceAcknowledgement
</actionMapping>
<!-- For interopability purposes. Some WSRM implementations tend to send
this as the LastMessage -->
<actionMapping>http://schemas.xmlsoap.org/ws/2005/02/rm/LastMessage
</actionMapping>
<!-- namespaces for the 2007-02 spec -->
<actionMapping>
http://docs.oasis-open.org/ws-rx/wsrm/200702/SequenceAcknowledgement
</actionMapping>
<actionMapping>http://docs.oasis-open.org/ws-rx/wsrm/200702/fault
</actionMapping>
<actionMapping>http://docs.oasis-open.org/ws-rx/wsrm/200702/AckRequested
</actionMapping>
<actionMapping>http://schemas.xmlsoap.org/ws/2005/02/rm/TerminateSequence
</actionMapping>
</operation>
<operation name="Sandesha2OperationInOut" mep="
http://www.w3.org/2006/01/wsdl/in-out";>
<messageReceiver
class="org.apache.sandesha2.msgreceivers.RMMessageReceiver"/>
<!-- namespaces for the 2005-02 spec -->
<actionMapping>http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence
</actionMapping>
<actionMapping>http://schemas.xmlsoap.org/ws/2005/02/rm/AckRequested
</actionMapping>
<!-- namespaces for the 2007-02 spec -->
<actionMapping>http://docs.oasis-open.org/ws-rx/wsrm/200702/CreateSequence
</actionMapping>
<actionMapping>http://docs.oasis-open.org/ws-rx/wsrm/200702/CloseSequence
</actionMapping>
<actionMapping>
http://docs.oasis-open.org/ws-rx/wsrm/200702/TerminateSequence
</actionMapping>
<actionMapping>http://docs.oasis-open.org/ws-rx/wsmc/200702/MakeConnection
</actionMapping>
</operation>
<operation name="Sandesha2OperationOutOnly" mep="
http://www.w3.org/2006/01/wsdl/out-only";>
<messageReceiver
class="org.apache.sandesha2.msgreceivers.RMMessageReceiver"/>
</operation>
<operation name="Sandesha2OperationOutIn" mep="
http://www.w3.org/2006/01/wsdl/out-in";>
<messageReceiver
class="org.apache.sandesha2.msgreceivers.RMMessageReceiver"/>
</operation>
<operation name="Sandesha2OperationDuplicateInOnly" mep="
http://www.w3.org/2006/01/wsdl/in-only";>
<messageReceiver
class="org.apache.sandesha2.msgreceivers.RMMessageReceiver"/>
</operation>
<operation name="Sandesha2OperationDuplicateInOut" mep="
http://www.w3.org/2006/01/wsdl/in-out";>
<messageReceiver
class="org.apache.sandesha2.msgreceivers.RMMessageReceiver"/>
</operation>
<supported-policy-namespaces namespaces="
http://ws.apache.org/sandesha2/policy"; />
<wsp:Policy xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";
xmlns:wsu="
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
"
xmlns:sandesha2="http://ws.apache.org/sandesha2/policy"; wsu:Id="RMPolicy">
<sandesha2:RMAssertion>
<wsp:Policy>
<sandesha2:AcknowledgementInterval>3000</sandesha2:AcknowledgementInterval>
<sandesha2:RetransmissionInterval>6000</sandesha2:RetransmissionInterval>
<!-- '-1' conveys that there is no limit to the max. number of
retransmissions.-->
<sandesha2:MaximumRetransmissionCount>10</sandesha2:MaximumRetransmissionCount>
<sandesha2:ExponentialBackoff>false</sandesha2:ExponentialBackoff>
<sandesha2:InactivityTimeout>60</sandesha2:InactivityTimeout>
<sandesha2:InactivityTimeoutMeasure>seconds</sandesha2:InactivityTimeoutMeasure>
<!-- Once a sequence has been marked as deleted, or timed out, this is the
length of time that the
sequence will remain before all sequence state is totally removed -->
<sandesha2:SequenceRemovalTimeout>600</sandesha2:SequenceRemovalTimeout>
<sandesha2:SequenceRemovalTimeoutMeasure>seconds</sandesha2:SequenceRemovalTimeoutMeasure>
<sandesha2:InvokeInOrder>true</sandesha2:InvokeInOrder>
<!-- These will not be overriden by service level policies -->
<sandesha2:MessageTypesToDrop>none</sandesha2:MessageTypesToDrop>
<!-- This will not be overriden by service level policies -->
<sandesha2:StorageManagers>
<sandesha2:InMemoryStorageManager>
org.apache.sandesha2.storage.inmemory.InMemoryStorageManager
</sandesha2:InMemoryStorageManager>
<sandesha2:PermanentStorageManager>
org.apache.sandesha2.storage.inmemory.InMemoryStorageManager
</sandesha2:PermanentStorageManager>
</sandesha2:StorageManagers>
<!-- This will not be overriden by service level policies -->
<sandesha2:SecurityManager>org.apache.sandesha2.security.dummy.DummySecurityManager</sandesha2:SecurityManager>
<sandesha2:ContextManager>org.apache.sandesha2.context.DummyContextManager</sandesha2:ContextManager>
<sandesha2:MakeConnection>
<sandesha2:Enabled>true</sandesha2:Enabled>
<sandesha2:UseRMAnonURI>true</sandesha2:UseRMAnonURI>
</sandesha2:MakeConnection>
<!--
<sandesha2:UseMessageSerialization>true</sandesha2:UseMessageSerialization>
-->
<sandesha2:EnforceRM>false</sandesha2:EnforceRM>
</wsp:Policy>
</sandesha2:RMAssertion>
</wsp:Policy>
<!-- Parameters that will be copied when creating related MessageContexts
-->
<parameter name="propertiesToCopyFromReferenceMessage"
locked="false">TransportURL,WSAddressingVersion,disableAddressingForOutMessages,rampartPolicy,RECV_RESULTS,PROXY</parameter>
<parameter name="propertiesToCopyFromReferenceRequestMessage"
locked="false">WSAddressingVersion,RECV_RESULTS,rampartPolicy</parameter>
</module>
======================================================
Thanks,
Patrice
--- On Tue, 8/18/09, Dave Parsons (JIRA) <j...@apache.org> wrote:
From: Dave Parsons (JIRA) <j...@apache.org>
Subject: [jira] Commented: (SANDESHA2-197) CreateSequence response is
actually sent to the anonymous makeconnection url (i.e.
http//:docs.oasis-open.org/..... ???
To: pnau...@yahoo.com
Date: Tuesday, August 18, 2009, 6:11 PM
[
https://issues.apache.org/jira/browse/SANDESHA2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744580#action_12744580
]
Dave Parsons commented on SANDESHA2-197:
----------------------------------------
Hi,
The default sandesha2-1.3.mar doesn't have the following:
<sandesha2:MakeConnection>
<sandesha2:Enabled>true</sandesha2:Enabled>
<sandesha2:UseRMAnonURI>true</sandesha2:UseRMAnonURI>
</sandesha2:MakeConnection>
as part of it's module.xml. These have to be set as part of your config.
The Sandesha module has been deployed correctly as I can see that it
processes the createSeq and tries to send a createSeqResponse.
Regards,
Dave
Dave Parsons
Web Services Development
INTERNAL: David Parsons1/UK/i...@ibmgb :: DE3F20 :: 246930
EXTERNAL: parso...@uk.ibm.com :: (01962) 816930
Mail Point 211, IBM Hursley Park, Winchester. SO21 2JN
From:
"patrice aubry (JIRA)" <j...@apache.org>
To:
sandesha-dev@ws.apache.org
Date:
18/08/2009 16:08
Subject:
[jira] Commented: (SANDESHA2-197) CreateSequence response is actually sent
to the anonymous makeconnection url (i.e. http//:docs.oasis-open.org/.....
???
[
https://issues.apache.org/jira/browse/SANDESHA2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744539#action_12744539
]
patrice aubry commented on SANDESHA2-197:
-----------------------------------------
Hello Dave,
The trace I sent you shows that MakeConn is enabled (see axis2.log). I am
using the default modules.xml in the sandesha.mar, which enables MakeConn.
As to the services.xml, uncommenting the MakeConn policies has no effect;
this is coherent since the modules.xml enables these.
By the way, is RMPhase correctly positionned in the axis2 conf in the late
documentation ?
Can you run the client and the service as I sent them to you successfuly ?
Or better yet, can you send me a simple service and client that runs
successfullly under WS-RM 1.1 with Axis2 1.4 or 1.5 ?
Thanks in advance,
Patrice
--- On Tue, 8/18/09, Dave Parsons (JIRA) <j...@apache.org> wrote:
From: Dave Parsons (JIRA) <j...@apache.org>
Subject: [jira] Commented: (SANDESHA2-197) CreateSequence response is
actually sent to the anonymous makeconnection url (i.e.
http//:docs.oasis-open.org/..... ???
To: pnau...@yahoo.com
Date: Tuesday, August 18, 2009, 11:32 AM
[
https://issues.apache.org/jira/browse/SANDESHA2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744432#action_12744432
]
Dave Parsons commented on SANDESHA2-197:
----------------------------------------
Hi,
Your services.xml shows the makeConn enablement commented out, you should
try uncommenting this. I haven't seen your module.xml so can't comment on
that. If you can collect sandesha trace for your service I can get a
better idea of what's going on. It's only an assumption that
MakeConnection isn't enabled on your service and that's why you are seeing
the behaviour you are.
Regards,
Dave
Dave Parsons
Web Services Development
INTERNAL: David Parsons1/UK/i...@ibmgb :: DE3F20 :: 246930
EXTERNAL: parso...@uk.ibm.com :: (01962) 816930
Mail Point 211, IBM Hursley Park, Winchester. SO21 2JN
From:
"patrice aubry (JIRA)" <j...@apache.org>
To:
sandesha-dev@ws.apache.org
Date:
18/08/2009 08:39
Subject:
[jira] Commented: (SANDESHA2-197) CreateSequence response is actually sent
to the anonymous makeconnection url (i.e. http//:docs.oasis-open.org/.....
???
[
https://issues.apache.org/jira/browse/SANDESHA2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744399#action_12744399
]
patrice aubry commented on SANDESHA2-197:
-----------------------------------------
Hello Dave,
I'll try again, but the commented out code showed me that MakeConn is
enabled, as specified in the module.xml policies.
Do the client and service taht I sent work for you ?
Thanks in advance,
Patrice
--- On Mon, 8/17/09, Dave Parsons (JIRA) <j...@apache.org> wrote:
From: Dave Parsons (JIRA) <j...@apache.org>
Subject: [jira] Commented: (SANDESHA2-197) CreateSequence response is
actually sent to the anonymous makeconnection url (i.e.
http//:docs.oasis-open.org/..... ???
To: pnau...@yahoo.com
Date: Monday, August 17, 2009, 6:44 PM
[
https://issues.apache.org/jira/browse/SANDESHA2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744128#action_12744128
]
Dave Parsons commented on SANDESHA2-197:
----------------------------------------
Hi Patrice,
The init method of your service is commented out. This says that it is
used to disable MakeConn but currently the commented out code is setting
it to true. Try enabling this so that when it is called MakeConn will be
enabled. I think your seeing problems because MakeConn isn't enabled on
your service.
Regards,
Dave
Dave Parsons
Web Services Development
INTERNAL: David Parsons1/UK/i...@ibmgb :: DE3F20 :: 246930
EXTERNAL: parso...@uk.ibm.com :: (01962) 816930
Mail Point 211, IBM Hursley Park, Winchester. SO21 2JN
From:
"patrice aubry (JIRA)" <j...@apache.org>
To:
sandesha-dev@ws.apache.org
Date:
15/08/2009 09:12
Subject:
[jira] Updated: (SANDESHA2-197) CreateSequence response is actually sent
to the anonymous makeconnection url (i.e. http//:docs.oasis-open.org/.....
???
[
https://issues.apache.org/jira/browse/SANDESHA2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
patrice aubry updated SANDESHA2-197:
------------------------------------
Attachment: sandesha-issue.zip
Hello Dave,
The answer is yes to your questions.
To check that v1.1 is engaged on the server side, I just checked the
SandshaBean that MakeConnection was enabled and that UseRMAnonURI is true.
I've attached a ZIP file containing the axis2 log, the service and client
, as well as the CreateSequence message (sent from the client) captured on
TcpMon.
I know that there is an issue with policy loading in Sandesha, but the
MakeConnection policy seem to be loaded correctly.
Thank you very much in advance,
Patrice
--- On Fri, 8/14/09, Dave Parsons (JIRA) <j...@apache.org> wrote:
From: Dave Parsons (JIRA) <j...@apache.org>
Subject: [jira] Commented: (SANDESHA2-197) CreateSequence response is
actually sent to the anonymous makeconnection url (i.e.
http//:docs.oasis-open.org/..... ???
To: pnau...@yahoo.com
Date: Friday, August 14, 2009, 11:48 AM
[
https://issues.apache.org/jira/browse/SANDESHA2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743154#action_12743154
]
Dave Parsons commented on SANDESHA2-197:
----------------------------------------
Hi Patrice,
Are you saying that the CreateSequenceResponse message is being sent
asynchronously to the MC Anonymous address that is set in the replyTo &
AcksTo of the createSequence message? Also just to confirm is your client
and server both using Sandesha for RM and are they both set at the same
version level of 1.1?
If you want to send over the trace I can take a look and see if I can see
anything out of the ordinary.
Regards,
Dave
Dave Parsons
Web Services Development
INTERNAL: David Parsons1/UK/i...@ibmgb :: DE3F20 :: 246930
EXTERNAL: parso...@uk.ibm.com :: (01962) 816930
Mail Point 211, IBM Hursley Park, Winchester. SO21 2JN
From:
"patrice aubry (JIRA)" <j...@apache.org>
To:
sandesha-dev@ws.apache.org
Date:
13/08/2009 16:29
Subject:
[jira] Created: (SANDESHA2-197) CreateSequence response is actually sent
to the anonymous makeconnection url (i.e. http//:docs.oasis-open.org/.....
???
CreateSequence response is actually sent to the anonymous makeconnection
url (i.e. http//:docs.oasis-open.org/..... ???
-----------------------------------------------------------------------------------------------------------------------
Key: SANDESHA2-197
URL: https://issues.apache.org/jira/browse/SANDESHA2-197
Project: Sandesha2
Issue Type: Bug
Affects Versions: 1.3
Environment: Windows XP, Java 1.6, Axis 1.4, Tomcat 6
Reporter: patrice aubry
Priority: Blocker
This may not be a bug.
I am testing the samples provided. The syncpingclient works fine (after a
few updates) in W-RM 1.0 but not for WS-RM 1.1.
When using WS-RM 1.1, the anonymous replyTo is not understood as such and
is treated as an actual URL.
When a CreateSequence message is sent, the response is of course never
received, with an UnknownHostException.
The debug log looks fine, in that the correct processing seems to take
place.
What am I missing ?
Your help will be greatly appreciated.
Thanks in advance,
--
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-unsubscr...@ws.apache.org
For additional commands, e-mail: sandesha-dev-h...@ws.apache.org
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
url (i.e. http//:docs.oasis-open.org/..... ???
-----------------------------------------------------------------------------------------------------------------------
a few updates) in W-RM 1.0 but not for WS-RM 1.1.
and is treated as an actual URL.
received, with an UnknownHostException.
place.
--
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-unsubscr...@ws.apache.org
For additional commands, e-mail: sandesha-dev-h...@ws.apache.org
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
url (i.e. http//:docs.oasis-open.org/..... ???
-----------------------------------------------------------------------------------------------------------------------
a few updates) in W-RM 1.0 but not for WS-RM 1.1.
and is treated as an actual URL.
received, with an UnknownHostException.
place.
--
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-unsubscr...@ws.apache.org
For additional commands, e-mail: sandesha-dev-h...@ws.apache.org
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
url (i.e. http//:docs.oasis-open.org/..... ???
-----------------------------------------------------------------------------------------------------------------------
a few updates) in W-RM 1.0 but not for WS-RM 1.1.
and is treated as an actual URL.
received, with an UnknownHostException.
place.
--
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-unsubscr...@ws.apache.org
For additional commands, e-mail: sandesha-dev-h...@ws.apache.org
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
url (i.e. http//:docs.oasis-open.org/..... ???
-----------------------------------------------------------------------------------------------------------------------
a few updates) in W-RM 1.0 but not for WS-RM 1.1.
and is treated as an actual URL.
received, with an UnknownHostException.
place.
--
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-unsubscr...@ws.apache.org
For additional commands, e-mail: sandesha-dev-h...@ws.apache.org
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
url (i.e. http//:docs.oasis-open.org/..... ???
-----------------------------------------------------------------------------------------------------------------------
a few updates) in W-RM 1.0 but not for WS-RM 1.1.
and is treated as an actual URL.
received, with an UnknownHostException.
place.
--
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-unsubscr...@ws.apache.org
For additional commands, e-mail: sandesha-dev-h...@ws.apache.org
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
url (i.e. http//:docs.oasis-open.org/..... ???
-----------------------------------------------------------------------------------------------------------------------
a few updates) in W-RM 1.0 but not for WS-RM 1.1.
and is treated as an actual URL.
received, with an UnknownHostException.
place.
--
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-unsubscr...@ws.apache.org
For additional commands, e-mail: sandesha-dev-h...@ws.apache.org
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
> CreateSequence response is actually sent to the anonymous makeconnection url
> (i.e. http//:docs.oasis-open.org/..... ???
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: SANDESHA2-197
> URL: https://issues.apache.org/jira/browse/SANDESHA2-197
> Project: Sandesha2
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: Windows XP, Java 1.6, Axis 1.4, Tomcat 6
> Reporter: patrice aubry
> Priority: Blocker
> Attachments: sandesha-issue.zip
>
>
> This may not be a bug.
> I am testing the samples provided. The syncpingclient works fine (after a few
> updates) in W-RM 1.0 but not for WS-RM 1.1.
> When using WS-RM 1.1, the anonymous replyTo is not understood as such and is
> treated as an actual URL.
> When a CreateSequence message is sent, the response is of course never
> received, with an UnknownHostException.
> The debug log looks fine, in that the correct processing seems to take place.
> What am I missing ?
> Your help will be greatly appreciated.
> Thanks in advance,
--
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-unsubscr...@ws.apache.org
For additional commands, e-mail: sandesha-dev-h...@ws.apache.org
