JAX-WS proxy and WS-ReliableMessaging

Hello all,
JDeveloper 11.1.2.3
I've started the foray into looking at reliable web services as specified by WS-ReliableMessaging. I have a very simple Hello World web service deployed (it was written in C# and deployed on IIS, if you have to ask :P). In JDeveloper, I've generated a JAX-WS Style proxy and test class using the JDeveloper wizard to do so. I've specified that no Async methods be generated and that there are no client OWSM policies (none are deemed compatible with the web service anyway).
I then add a bit of code to my test class and run to test. The first time I run the class, the WS calls work successfully, although after the sequence of calls, I get an exception displayed in the console (see below). If I try to run the class again, the web service calls don't even execute and I get a different exception in the console (again, see below - at least part of this error is captured by my ReliabilityErrorListener). This sequence of events alternates ad-infinitum (odd-numbered attempts work with an exception, even-numbered attempts don't work.
I show my test code here:
      // Add your code to call the desired methods.
    WsrmClientInitFeature f = new WsrmClientInitFeature(true);
    ReliabilityErrorListener listener = new ReliabilityErrorListener()
      public void onReliabilityError(ReliabilityErrorContext context)
        // At a *minimum* do this
        System.out.println("RM sequence failure: " + context.getFaultSummaryMessage());
        // And optionally do this...
        // The context parameter tells you whether a request or the entire
        // sequence has failed. If a sequence fails, you'll get a notification
        // for each undelivered request (if any) on the sequence.
        if (context.isRequestSpecific())
          // We have a single request failure (possibly as part of a larger
          // sequence failure).
          // We can get the original request back like this:
          String operationName = context.getOperationName();
          System.out.println("Failed to deliver request for operation '" + operationName + "'. Fault summary: " +
                             context.getFaultSummaryMessage());
        else
          // The entire sequence has encountered an error.
          System.out.println("Entire sequence failed: " + context.getFaultSummaryMessage());
    f.setErrorListener(listener);
    hello = helloService.getWSHttpBindingHello(f);
    WsrmClient c = WsrmClientFactory.getWsrmClientFromPort(hello);
    System.out.println("Sequence ID is " + c.getSequenceId());
    //   c.reset();
    System.out.println(hello.getGreeting("John"));
    System.out.println(hello.getGreeting("Fred"));
    System.out.println(hello.getGreeting("Josephine"));
    System.out.println("Sequence ID is " + c.getSequenceId());
    try
      System.out.println(c.getAckRanges().first().lowerBounds);
      System.out.println(c.getAckRanges().first().upperBounds);
    catch (Exception e)
    // c.setFinalMessage();The calls that work look like this in the console:
Sequence ID is null
<05-Mar-2013 14:55:53 o'clock EAT> <Info> <Store> <BEA-280008> <Opening the persistent file store "weblogic.wsee.persistence.WseeFileStore" for recovery: directory=C:\JDeveloper\11.1.2.3\mywork\WSReliableClientPOC\Client requestedWritePolicy="Cache-Flush" fileLockingEnabled=true driver="NIO".>
<05-Mar-2013 14:55:53 o'clock EAT> <Info> <Store> <BEA-280009> <The persistent file store "weblogic.wsee.persistence.WseeFileStore" (569ea4fb-b0fd-4906-bb74-003b6885b1d5) has been opened: blockSize=512 actualWritePolicy="Cache-Flush(single-handle-non-direct)" explicitIOEnforced=false records=57.>
Hello, John. You have just communicated with me using WS-reliablemessaging
Hello, Fred. You have just communicated with me using WS-reliablemessaging
Hello, Josephine. You have just communicated with me using WS-reliablemessaging
Sequence ID is uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffd
1
3
<05-Mar-2013 14:56:03 o'clock EAT> <Error> <WseeRm> <BEA-224016> <An unexpected error occurred: weblogic.wsee.sender.api.ConversationNotFoundException: [WseeSender:221102]The conversation with the given name (uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd) could not be found.
weblogic.wsee.sender.api.ConversationNotFoundException: [WseeSender:221102]The conversation with the given name (uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd) could not be found.
     at weblogic.wsee.sender.DefaultProvider.DefaultSendingServiceProvider.getConversation(DefaultSendingServiceProvider.java:222)
     at weblogic.wsee.sender.DefaultProvider.DefaultSendingServiceProvider.stopConversation(DefaultSendingServiceProvider.java:287)
     at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:257)
     at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:30)
     at weblogic.wsee.reliability2.store.SequenceStore.removePhysicalStore(SequenceStore.java:109)
     at weblogic.wsee.persistence.LogicalStore.close(LogicalStore.java:955)
     at weblogic.wsee.persistence.LogicalStore.closeLogicalStores(LogicalStore.java:402)
     at weblogic.wsee.persistence.LogicalStore.closeStore(LogicalStore.java:384)
     at weblogic.wsee.persistence.LogicalStore.closeAllStores(LogicalStore.java:365)
     at weblogic.wsee.persistence.LogicalStore$1.run(LogicalStore.java:164)
>
<05-Mar-2013 14:56:03 o'clock EAT> <Error> <WseePersist> <BEA-221000> <An unexpected error occurred: java.lang.IllegalStateException: Attempt to remove listener from weblogic.wsee.reliability2.sequence.SourceSequence@6ac27081 - uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd when it is not the master instance
java.lang.IllegalStateException: Attempt to remove listener from weblogic.wsee.reliability2.sequence.SourceSequence@6ac27081 - uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd when it is not the master instance
     at weblogic.wsee.reliability2.sequence.Sequence.removePropertyChangeListener(Sequence.java:1250)
     at weblogic.wsee.reliability2.store.SequenceMap.shutdownSequence(SequenceMap.java:558)
     at weblogic.wsee.reliability2.store.TimedSequenceMap.shutdownSequence(TimedSequenceMap.java:182)
     at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:274)
     at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:30)
     at weblogic.wsee.reliability2.store.SequenceStore.removePhysicalStore(SequenceStore.java:109)
     at weblogic.wsee.persistence.LogicalStore.close(LogicalStore.java:955)
     at weblogic.wsee.persistence.LogicalStore.closeLogicalStores(LogicalStore.java:402)
     at weblogic.wsee.persistence.LogicalStore.closeStore(LogicalStore.java:384)
     at weblogic.wsee.persistence.LogicalStore.closeAllStores(LogicalStore.java:365)
     at weblogic.wsee.persistence.LogicalStore$1.run(LogicalStore.java:164)
>
Process exited with exit code 0.The calls that don't work look like this:
Sequence ID is null
<05-Mar-2013 14:57:49 o'clock EAT> <Info> <Store> <BEA-280008> <Opening the persistent file store "weblogic.wsee.persistence.WseeFileStore" for recovery: directory=C:\JDeveloper\11.1.2.3\mywork\WSReliableClientPOC\Client requestedWritePolicy="Cache-Flush" fileLockingEnabled=true driver="NIO".>
<05-Mar-2013 14:57:49 o'clock EAT> <Info> <Store> <BEA-280009> <The persistent file store "weblogic.wsee.persistence.WseeFileStore" (569ea4fb-b0fd-4906-bb74-003b6885b1d5) has been opened: blockSize=512 actualWritePolicy="Cache-Flush(single-handle-non-direct)" explicitIOEnforced=false records=59.>
RM sequence failure:
weblogic.wsee.sender.api.PermanentSendException: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
Failed to deliver request for operation 'GetGreeting'. Fault summary:
weblogic.wsee.sender.api.PermanentSendException: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
Exception in thread "main" java.lang.AssertionError: weblogic.wsee.sender.api.PermanentSendException: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
     at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:689)
     at com.sun.xml.ws.client.Stub.process(Stub.java:272)
     at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:153)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:115)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
     at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
     at $Proxy36.getGreeting(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
     at $Proxy35.getGreeting(Unknown Source)
     at org.tempuri.WSHttpBinding_HelloClient.main(WSHttpBinding_HelloClient.java:96)
Caused by: weblogic.wsee.sender.api.PermanentSendException: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
     at weblogic.wsee.reliability2.store.SourceSequenceSender.checkForPermanentSendFailure(SourceSequenceSender.java:549)
     at weblogic.wsee.reliability2.store.SourceSequenceSender.handleFailureForSuspendedFiber(SourceSequenceSender.java:604)
     at weblogic.wsee.reliability2.store.SourceSequenceSender.sendRequestAndHandleResponseForSuspendedFiber(SourceSequenceSender.java:452)
     at weblogic.wsee.reliability2.store.SourceSequenceSender.sendRequestAndHandleResponse(SourceSequenceSender.java:293)
     at weblogic.wsee.reliability2.store.SourceSequenceSender.send(SourceSequenceSender.java:184)
     at weblogic.wsee.sender.DefaultProvider.Conversation.sendOneRequest(Conversation.java:671)
     at weblogic.wsee.sender.DefaultProvider.Conversation.sendPendingRequests(Conversation.java:579)
     at weblogic.wsee.sender.DefaultProvider.Conversation.access$1400(Conversation.java:44)
     at weblogic.wsee.sender.DefaultProvider.Conversation$2.timerExpired(Conversation.java:476)
     at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
     at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
Caused by: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
     at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:258)
     at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:273)
     at weblogic.wsee.reliability2.store.SourceSequenceSender.sendRequestAndHandleResponseForSuspendedFiber(SourceSequenceSender.java:442)
     ... 10 more
Caused by: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
     at weblogic.wsee.reliability2.tube.WsrmTubelineDeploymentListener$WsrmClientProtocolTube.processResponse(WsrmTubelineDeploymentListener.java:222)
     at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:877)
     at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:815)
     at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:778)
     at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:680)
     at com.sun.xml.ws.client.Stub.process(Stub.java:272)
     at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:238)
     ... 12 more
<05-Mar-2013 14:57:58 o'clock EAT> <Error> <WseeRm> <BEA-224016> <An unexpected error occurred: weblogic.wsee.sender.api.ConversationNotFoundException: [WseeSender:221102]The conversation with the given name (uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd) could not be found.
weblogic.wsee.sender.api.ConversationNotFoundException: [WseeSender:221102]The conversation with the given name (uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd) could not be found.
     at weblogic.wsee.sender.DefaultProvider.DefaultSendingServiceProvider.getConversation(DefaultSendingServiceProvider.java:222)
     at weblogic.wsee.sender.DefaultProvider.DefaultSendingServiceProvider.stopConversation(DefaultSendingServiceProvider.java:287)
     at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:257)
     at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:30)
     at weblogic.wsee.reliability2.store.SequenceStore.removePhysicalStore(SequenceStore.java:109)
     at weblogic.wsee.persistence.LogicalStore.close(LogicalStore.java:955)
     at weblogic.wsee.persistence.LogicalStore.closeLogicalStores(LogicalStore.java:402)
     at weblogic.wsee.persistence.LogicalStore.closeStore(LogicalStore.java:384)
     at weblogic.wsee.persistence.LogicalStore.closeAllStores(LogicalStore.java:365)
     at weblogic.wsee.persistence.LogicalStore$1.run(LogicalStore.java:164)
>
<05-Mar-2013 14:57:58 o'clock EAT> <Error> <WseePersist> <BEA-221000> <An unexpected error occurred: java.lang.IllegalStateException: Attempt to remove listener from weblogic.wsee.reliability2.sequence.SourceSequence@79424b7b - uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd when it is not the master instance
java.lang.IllegalStateException: Attempt to remove listener from weblogic.wsee.reliability2.sequence.SourceSequence@79424b7b - uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd when it is not the master instance
     at weblogic.wsee.reliability2.sequence.Sequence.removePropertyChangeListener(Sequence.java:1250)
     at weblogic.wsee.reliability2.store.SequenceMap.shutdownSequence(SequenceMap.java:558)
     at weblogic.wsee.reliability2.store.TimedSequenceMap.shutdownSequence(TimedSequenceMap.java:182)
     at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:274)
     at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:30)
     at weblogic.wsee.reliability2.store.SequenceStore.removePhysicalStore(SequenceStore.java:109)
     at weblogic.wsee.persistence.LogicalStore.close(LogicalStore.java:955)
     at weblogic.wsee.persistence.LogicalStore.closeLogicalStores(LogicalStore.java:402)
     at weblogic.wsee.persistence.LogicalStore.closeStore(LogicalStore.java:384)
     at weblogic.wsee.persistence.LogicalStore.closeAllStores(LogicalStore.java:365)
     at weblogic.wsee.persistence.LogicalStore$1.run(LogicalStore.java:164)
>
Process exited with exit code 1.Does anyone have any insight about this behaviour?
Thanks,
John

Some additional information for the second case. Using HTTP analyzer in JDeveloper, I can see 2 HTTP POSTs going to the web service. The first one is to initiate the WS-RM sequence and shows an offered conversation identifier and the reply shows that the server has given its own identifier instead of the offered one:
request:
POST http://xgis-lel-05717.ad.xglobal.com:80/WSReliablePOC/HelloService.svc HTTP/1.1
Proxy-Authorization:
Content-type: application/soap+xml;charset="utf-8";action="http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence"
Accept: application/soap+xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
User-Agent: Oracle JAX-WS 2.1.5
Host: xgis-lel-05717.ad.xglobal.com
Proxy-Connection: Keep-Alive
Content-Length: 1620
X-HTTPAnalyzer-Rules: 1@localhost:8099
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
    <env:Header>
        <wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing" env:mustUnderstand="true">http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence</wsa:Action>
        <wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:WLS1:WseeFileStore:3f3d2d8955322f32:201221c6:13d3a75f768:-7ffb</wsa:MessageID>
        <wsa:To xmlns:wsa="http://www.w3.org/2005/08/addressing">http://xgis-lel-05717.ad.xglobal.com/WSReliablePOC/HelloService.svc</wsa:To>
        <ReplyTo xmlns="http://www.w3.org/2005/08/addressing">
            <Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
        </ReplyTo>
        <FaultTo xmlns="http://www.w3.org/2005/08/addressing">
            <Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
        </FaultTo>
    </env:Header>
    <env:Body xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
        <wsrm:CreateSequence>
            <wsrm:AcksTo xmlns:wsa="http://www.w3.org/2005/08/addressing">
                <wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address>
                <wsa:ReferenceParameters xmlns:clspi="http://www.oracle.com/wsee/jaxws/cluster/spi">
                    <clspi:PhysicalStoreName
                        xmlns:wsa="http://www.w3.org/2005/08/addressing"
                        xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility" wsa:IsReferenceParameter="true">WseeFileStore</clspi:PhysicalStoreName>
                </wsa:ReferenceParameters>
            </wsrm:AcksTo>
            <wsrm:Expires>P1D</wsrm:Expires>
            <wsrm:Offer>
                <wsrm:Identifier>uuid:WLS1:WseeFileStore:3f3d2d8955322f32:201221c6:13d3a75f768:-7ffe</wsrm:Identifier>
                <wsrm:Expires>P1D</wsrm:Expires>
            </wsrm:Offer>
        </wsrm:CreateSequence>
    </env:Body>
</env:Envelope>
reply:
HTTP/1.1 200 OK
Content-Type: application/soap+xml; charset=utf-8
Cache-Control: private
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
Content-Length: 673
Server: Microsoft-IIS/7.5
Date: Tue, 05 Mar 2013 12:10:44 GMT
X-HTTPAnalyzer-RuleName: Pass through :
<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
    <s:Header>
        <a:Action s:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequenceResponse</a:Action>
        <a:RelatesTo>uuid:WLS1:WseeFileStore:3f3d2d8955322f32:201221c6:13d3a75f768:-7ffb</a:RelatesTo>
    </s:Header>
    <s:Body>
        <CreateSequenceResponse xmlns="http://schemas.xmlsoap.org/ws/2005/02/rm">
            <Identifier>urn:uuid:b6886ed1-6cf2-40a4-99a3-f17cc5a295d7</Identifier>
            <Expires>P1D</Expires>
            <Accept>
                <AcksTo>
                    <a:Address>http://xgis-lel-05717.ad.xglobal.com/WSReliablePOC/HelloService.svc</a:Address>
                </AcksTo>
            </Accept>
        </CreateSequenceResponse>
    </s:Body>
</s:Envelope>The second POST shows the JDeveloper proxy calling the web service and sending a wsrm:Identifier value that the one originally offered by JDeveloper (see the sequence acknowledgement), not the one the server advised to use:
request:
POST http://xgis-lel-05717.ad.xglobal.com:80/WSReliablePOC/HelloService.svc HTTP/1.1
Proxy-Authorization:
Content-type: application/soap+xml;charset="utf-8";action="http://tempuri.org/Hello/GetGreeting"
Accept: application/soap+xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
User-Agent: Oracle JAX-WS 2.1.5
Host: xgis-lel-05717.ad.xglobal.com
Proxy-Connection: Keep-Alive
Content-Length: 1444
X-HTTPAnalyzer-Rules: 1@localhost:8099
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope">
    <S:Header>
        <wsa:To xmlns:wsa="http://www.w3.org/2005/08/addressing">http://xgis-lel-05717.ad.xglobal.com/WSReliablePOC/HelloService.svc</wsa:To>
        <wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing">http://tempuri.org/Hello/GetGreeting</wsa:Action>
        <ReplyTo xmlns="http://www.w3.org/2005/08/addressing">
            <Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
        </ReplyTo>
        <FaultTo xmlns="http://www.w3.org/2005/08/addressing">
            <Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
        </FaultTo>
        <wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:WLS1:WseeFileStore:3f3d2d8955322f32:201221c6:13d3a75f768:-7ffc</wsa:MessageID>
        <wsrm:SequenceAcknowledgement xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
            <wsrm:Identifier>uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-725c9c83:13d3a75543c:-7ffe</wsrm:Identifier>
            <wsrm:AcknowledgementRange Lower="1" Upper="3"/>
        </wsrm:SequenceAcknowledgement>
        <wsrm:Sequence
            xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm" S:mustUnderstand="true">
            <wsrm:Identifier>urn:uuid:b6886ed1-6cf2-40a4-99a3-f17cc5a295d7</wsrm:Identifier>
            <wsrm:MessageNumber>1</wsrm:MessageNumber>
        </wsrm:Sequence>
    </S:Header>
    <S:Body>
        <GetGreeting
            xmlns:ns2="http://schemas.microsoft.com/2003/10/Serialization/" xmlns="http://tempuri.org/">
            <name>John</name>
        </GetGreeting>
    </S:Body>
</S:Envelope>
response:
HTTP/1.1 500 Internal Server Error
Content-Type: application/soap+xml; charset=utf-8
Cache-Control: private
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
Content-Length: 710
Server: Microsoft-IIS/7.5
Date: Tue, 05 Mar 2013 12:10:52 GMT
X-HTTPAnalyzer-RuleName: Pass through :
<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
    <s:Header>
        <a:Action s:mustUnderstand="1">http://www.w3.org/2005/08/addressing/soap/fault</a:Action>
    </s:Header>
    <s:Body>
        <s:Fault>
            <s:Code>
                <s:Value>s:Sender</s:Value>
                <s:Subcode>
                    <s:Value xmlns:a="http://schemas.xmlsoap.org/ws/2005/02/rm">a:UnknownSequence</s:Value>
                </s:Subcode>
            </s:Code>
            <s:Reason>
                <s:Text xml:lang="en-GB">The value of wsrm:Identifier is not a known Sequence identifier.</s:Text>
            </s:Reason>
            <s:Detail>
                <r:Identifier xmlns:r="http://schemas.xmlsoap.org/ws/2005/02/rm">uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-725c9c83:13d3a75543c:-7ffe</r:Identifier>
            </s:Detail>
        </s:Fault>
    </s:Body>
</s:Envelope>This seems to be an issue in the JDev-generated Proxy (still need to find out why it happens "every other time" and not "every time." The time it works, JDeveloper is sending the Identifier returned by the service. The time it works, however - you can also see that the "conversation not found" exception is referring to the original "offered" identifier and not the one that was used in the conversation. I'm now starting to suspect that the proxy generation for WS-RM may be a bit buggy. Anyone else with experience in this area?
A quick look at support.oracle.com does find note 1082278.1 which although for old versions of WebLogic, that WS-RM isn't supported for JAX-WS in WLS, but is supported for JAX-RPC. Since this seems to be for publishing web services, it is not at all clear as to whether this applies to me. In any case, the JDeveloper WS proxy wizard won't let me generate a JAX-RPC proxy, instead saying that the WSDL has no SOAP 1.1 bindings (which is correct, it has SOAP 1.2 bindings).
John
John

Similar Messages

  • Connection Problem while client is behind proxy and server out side proxy

    hello
    i implemented ChatApplication in JAVA, for that i used socket connection when client and server both are in same network then it's working fine.
    but when my server is on internate and client is behind proxy and try to connect with server
    it not able to connect i get exception.
    i serch most of forum i got same answer and i try it but i was not success.
    any kind of help is appriciated.
    i attached my code(which i implement for testing ) pls reply me
    thanks in advance.
    Server.java
    import java.lang.*;
    import java.io.*;
    import java.net.*;
    class Server {
       public static void main(String args[]) {
          String data = "you are successfully connected with server.";
          try {
             ServerSocket srvs = new ServerSocket(1234);
             Socket skt = srvs.accept();
             System.out.print("Server has connected!\n");
             PrintWriter out = new PrintWriter(skt.getOutputStream(), true);
             System.out.print("Sending string: '" + data + "\n");
             out.print(data);
             out.close();
             skt.close();
             srvs.close();
          catch(Exception e) {
             System.out.print("Whoops! It didn't work!\n");
    ProxyClient.java
    import java.io.*;
    import java.net.*;
    import java.util.*;
    class ProxyClient{
       public static void main(String args[]) {
         String host="61.17.212.29";
         int port=1234;
               String line;
         Properties properties = System.getProperties();
         /*properties.put("firewallSet", "true");
         properties.put("firewallHost", "192.168.0.1");
         properties.put("firewallPort", "808");*/
         properties.put("socksProxySet","true");
         properties.put("socksProxyHost", "192.168.0.1");
         properties.put("socksProxyPort", "1080");
         System.setProperties (properties);
         try {
         /*SocketAddress addr = new InetSocketAddress("192.168.0.1", 1080);
         Proxy proxy = new Proxy(Proxy.Type.SOCKS, addr);
         Socket skt = new Socket(proxy);
         InetSocketAddress dest = new InetSocketAddress("61.17.212.29",1234);
         skt.connect(dest);*/
             System.out.println("before socket taken");
             Socket skt = new Socket(host,port);
             System.out.println("after socket taken");
             BufferedReader networkBin = new BufferedReader(new InputStreamReader(skt.getInputStream()));
             System.out.println("Received string: '");
             line = networkBin.readLine();     // Read one line
          while(true)
                 System.out.println(line);     // Output the line
                 line = networkBin.readLine(); // Read the next line, if any
          catch(Exception e) {
             System.out.print("Whoops! It didn't work!\n");
         e.printStackTrace();
    }

    Now look here. I could not care less about this
    code. I don't know anything about it, I don't
    want to know, I have already recommended you don't
    use it, and I have also given you a simpler and
    better solution. If you don't want to take my advice
    that is your privilege and your problem.ya i has understand system propertis i have setted and u can see it in the code i have tried by both system properties and also J2SE 5.0 proxy class but i got a same problem malformed Exception server refuse to connection.
    is there any problem at sever side?
    can u tell me in which way u r teling to set the propery i m looking forward for ur reply.
    ya i m sure u will give me.................reply "ejp".
    Thnx in advance.

  • Sun Web Server Reverse Proxy and Weblogic HTTP to HTTPS redirection

    Hi,
    I am currently testing reverse-proxy from SJSW 7.0 update 5 to Weblogic server but I have encountered an issue.
    I have configured a context root to be forwarded to weblogic:
    Web Server: www.server.com
    URI: /path
    Reverse Proxy URL: wlserver:9000
    When I access https://www.server.com/path, I am getting the correct page. The issue is, the weblogic server is configured to redirect HTTP access to HTTPS, i.e., when I access http://www.server.com/path, it should be redirected to https://www.server.com/path. However, that is not the case. What happens is that I am being redirected instead to https://www.server.com/.
    If I don't use reverse proxy, that is, if I use the libproxy.so from weblogic, I get the correct redirection.
    Would appreciate it very much if someone can help me troubleshoot this issue.
    Thanks in advance!
    Edited by: agent_orange on Jul 29, 2010 2:30 AM
    Edited by: agent_orange on Jul 29, 2010 2:31 AM

    I am not sure, how you have configured your reverse proxy since you didn't attach / refer your current configuration file. this is how I would do it..
    - create a new configuration (using web server 7 admin gui , within configuration wizard, disable java option if you plan to use web server 7 only for reverse proxy)
    - select this new configuration and go to reverse proxy and try to reverse proxy / to the origin server.
    that is all it should need.
    your obj.conf or <hostname>-obj.conf depending on your configuration should look like following snippet
    <Object name="default">
    AuthTrans..
    NameTrans fn=map from="/" to="/path" name="reverse-proxy-/"
    </object>
    <Object name="reverse-proxy-/">
    Route fn=....
    Service ..
    </Object>
    this is all you should need..
    However, if you wanted to add complexity to your configuration, you could do some thing like
    <Object name="default">
    Auth..
    <If defined $security>
    NameTrans fn=map from="/" to="/path" name="reverse-proxy-/"
    </If>
    </Object>
    <Object name="reverse-proxy-/">
    Route...
    </Object>

  • Problem with proxy and DNS

    Hello,
    in our company we use Internet Explorer 8... (i know...) We also have a proxy and 4 DNS servers. Last weekend we suddenly had an issue where internet pages could not be loaded. When we did some testing with Wireshark we saw that it took a long time to query
    www.google.com or www.microsoft.com. The query went from the first DNS server to the second and so on. This behaviour was shown on Windows 2008 R2 servers with Citrix and also the workstations and laptops with Windows 7.
    When we deleted the DNS servers from the network settings and set the proxy ip-adres in the browser the problem was solved. So the problem had to be in DNS.
    After that we deleted the list of Root Hints and the problem seemed to be solved. However, when we look in wireshark we still see that external addresses are queried againts our local DNS servers. In internet explorer we have a policy active where the proxy
    is set. We have two proxies and the problem exists with both of them.
    So the question is, why does IE8 still query all four DNS servers even when we have a proxy? Why is there a lot of delay there?
    Thanks!

    Hi,
    Generally, if you configure IE with an explicit proxy:
    1.User types an address
    2.The address is checked for string matches against the IE proxy exceptions list
    a. If matching a bypassed entry, DNS is used to resolve the name, and the client connects directly to the target IP address on port 80 (assumed), then sends a request like:
    GET /something.htm HTTP/1.1
    Host: fulldomainame.example.com
    b. If non matching, continue
    3.The client connects to its configured proxy and sends a request of the form:
    GET http://fulldomainname.example.com/something.htm HTTP/1.1
    (this use of the FQDN in the URL is one way you can tell that a client thinks it's talking to a proxy instead of a real web server)
    4.The proxy resolves the name, connects to the target site, etc, etc
    So what’s your configuration of proxy?
    Alex Zhao
    TechNet Community Support

  • JMS proxy and XA connection factory

    Hi all,
    I would like to ask you what is the best practice to adopt about the scenario described below.
    A JMS proxy retrieves a message and processes it.
    Any error could occurr during processing it and, in case of errors, the JMS proxy error handler publishes the message on ad hoc recovery destination D.
    (later another app will check failed messages for fixing & republishing them into ALSB).
    In that scenario we have the JMS proxy and the jms business service that, in case of errors, publishes on destination D.
    Should the JMS proxy and the business service use both a XA connection factory in order to perform all the above steps in one transaction ?
    Otherwise if the business service itself fails publishing on destination D, the message retrieved by the JMS proxy is lost and not re-delivered to the JMS proxy.
    Or XA connection factory is not needed and could I use
    Routing Options with exactly once or both are needed ?
    Thanks
    ferp

    Hi all,
    I did some tests and follow what I've achieved.
    Scenario 1.
    - Precondition
    -- A JMS proxy with XA factory + Error Destination (MyRecoveryQueue)
    -- A business service BS with XA factory that publishes into MyOutboundQueue
    -- No "exactly once" routing option used calling BS
    -- an error is forced in the pipeline
    - Flow
    -- proxy retrieves a message and try to publish it using BS
    -- an error is forced in the pipeline:
    --- transaction is rolled back, message redelivered to proxy
    --- the message is posted to the error destination after all the retries failed
    Scenario 2.
    - Precondition
    -- As 1. but no error is forced in the pipeline
    -- the MyOutboundQueue destination queue is paused
    - Flow
    -- proxy retrieves a message and try to publish it using BS
    -- BS fails to publish it on MyOutboundQueue (because it is paused)
    --- transaction is rolled back, message redelivered to proxy
    --- the message is posted to the error destination after all the retries failed
    Scenario 2A.
    - Precondition
    -- As 2. with MyOutboundQueue paused and resumed
    - Flow:
    -- proxy retrieves a message and try to publish it using BS
    -- BS fails to publish it on MyOutboundQueue (because it is paused)
    --- transaction is rolled back, message redelivered to proxy
    --- before all the retries failed the queue is resumed
    --- BS succeeds to publish the message
    Scenario 3.
    - Precondition
    -- A JMS proxy with NO XA factory + Error Destination
    -- A business service BS with NO XA factory
    -- No "exactly once" routing option used calling BS
    -- an error is forced in the pipeline
    - Flow
    -- proxy retrieves a message and try to publish it using BS
    -- an error is forced in the pipeline:
    --- transaction is NOT rolled back, message NOT redelivered to proxy
    -- so
    --- no message delivered to MyOutboundQueue2 destination
    --- no message delivered to MyRecoveryQueue2 destination
    --- message consumed from MyQueue2 and now is lost!
    To publish message into MyRecoveryQueue2 a proxy error handler has to be added and here added explicit publish to MyRecoveryQueue2.
    But naturally in that case if in the proxy error handler, the explicit publish fails or any error occurrs no message is delivered to recovery queue.
    So if I'm not using an XAFactory the message is auto-acknowledged as soon as it is read and I've to use XA factory if I want the message to be put back in the queue in case of errors and the retry to happen.
    So both my proxy service and business service use an XA factory.
    Regards
    ferp

  • Web Application Proxy and Safari

    Morning, all.
    I've installed and configured the new Windows Server 2012 R2 AD FS and Web Application Proxy, and I've run into some strange problems. I had some initial problems getting it to work, the documentation is a bit thin, but I now have Sharepoint and Webmail
    published to the Internet.
    I'm using x.509 Certificate Authentication for Extranet.
    In IE on a Windows 8.1 Surface Pro everything works. I can log in using ether a softcert or a SmartCard.
    On my OS X Mac I can log in using Chrome, but Safari won't work.
    Same thing on my iPad running iOS 7.0.4, Safari won't work. Interestingly enough, on my 7.0.4 iPhone it DOES work. Even more interestingly, I CAN Workplace Join the iPad using the URL https://<adfs fqdn>/enrollmentserver/otaprofile but
    I can't authenticate using the URL https://<adfs fqdn>/adfs/ls/IdpInitiatedSignon.aspx.
    I get to select my certificate, but after that I'm getting this error message: "Safari cannot open the page because too many redirects occurred." In the Event log on the AD FS server I'm getting this:
    Encountered error during federation passive request. 
    Additional Data 
    Protocol Name: 
    Saml 
    Relying Party: 
    http://<adfs fqdn>/adfs/services/trust 
    Exception details: 
    Microsoft.IdentityServer.Web.InvalidRequestException: MSIS7042: The same client browser session has made '6' requests in the last '0' seconds. Contact your administrator for details.
       at Microsoft.IdentityServer.Web.Protocols.PassiveProtocolHandler.UpdateLoopDetectionCookie(WrappedHttpListenerContext context)
       at Microsoft.IdentityServer.Web.Protocols.Saml.SamlProtocolHandler.SendSignInResponse(SamlContext context, MSISSignInResponse response)
       at Microsoft.IdentityServer.Web.PassiveProtocolListener.ProcessProtocolRequest(ProtocolContext protocolContext, PassiveProtocolHandler protocolHandler)
       at Microsoft.IdentityServer.Web.PassiveProtocolListener.OnGetContext(WrappedHttpListenerContext context)
    Since it does work on an iPhone running the same browser, and Workplace Join does work on the iPad even if nothing else does I'm thinking there's some UserAgent voodoo going on in parts of the Web Application Proxy. It's no big deal that Safari in OS X doesn't
    work, we can always run Chrome, but the iPad is a major problem and a total deal breaker if I can't fix it.
    I would appreciate some good advice.

    Hi,
    As both IE and Chrome work, I think it’s more a client side issue.
    Maybe you need to clear you browser cache and cookies.
    This also worth a try:
    http://stackoverflow.com/questions/2640030/adfs-v2-0-error-msis7042-the-same-client-browser-session-has-made-6-request
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    Hope this helps.

  • Web service proxy and security constraint

    I've placed a security constraint on my web service and set the login-config auth-method as BASIC. When I run the Workshop test and the (Test View) browser begins to appear I am prompted for my username and password since it is protected --- great, it's working.
    Here's my problem, when I create the Java Proxy and try to access the web service using the proxy in another application I am never prompted for my username and password and thus the request fails. Anyway to fix this so I can be promted using the proxy??
    thanks in advance,
    Steve Touw

    Hi Shay Shmeltzer,
    Thanks for the reply.
    I tried in HTTP Analyzer in JDeveloper and there also it is not working. My concern is :-
    There are many other web services deployed on the same SOA server in same partition and they are working fine in HTTP analyzer and I am able to create and use the web service proxy as well. So as per my understanding there is nothing like network issues between SOA server and jDeveloper.
    1 more thing When I am creating the proxy for this web service and requesting from the proxy's main method SOA is getting proper input (which I am providing in the main method) and SOA is returning proper output I have checked the SOA instance in em. So there is no problem in SOA side. The problem is jDeveloper is not able to get back that response which SOA is returning.
    Please Help.
    -- NavinK

  • Reverse Proxy and Load Balancer for SMP 2.3 and Agentry Application

    Hi Expert,
    I'm putting in place a mobile solution composed by SMP 2.3 SPS 4 and SAP ECC 6.0. In the SMP 2.3 I created the agentry server and I have deployed my agentry application.
    My SMP/Agentry infrastructure is composed by two servers therefore I need a load balancer for balance the load into the several servers. Furthermore I need to use a reverse proxy in my DMZ zone.
    Based on what indicated in the SAP note "1904213 - SAP Mobile Platform Server Release Information" the Apache Reverse Proxy is not supported for Agentry clients. Agentry uses nginx for Reverse Proxy.
    I also found the following document How-to-Guide for Reverse Proxy and Load Balancing in SAP Mobile Platform 3.x that explain how to set-up a reverse proxy and load balancer with nginx and apache.
    Both the SAP note and the HOW to document are refereed to SMP 3.0 and not to SMP 2.3.
    I would know if the NGINX must be used also for SMP 2.3.
    Any suggestion/information is appreciated.
    Thanks in advance
    g.

    Please see Agentry Network Landscapes

  • How do ABAP Proxy and XI adapter work?

    Hi everybody,
    I have a general question about the ABAP proxy and XI adapter.
    In order to use the ABAP proxy and XI adapter, I must configure the HTTP Destination between the R/3 system and the XI server. I must also maintain the SLD.
    After several hours configurations with our administrator, it failed. At least the HTTP Destinations on both servers don't work correctly. We got always HTTP error message. But a scenario with an ABAP Receiver proxy works! It is really strange and laughable. We're very happy about that but don't know why and what happened. Today we tested the ABAP Sender proxy, it doesn't work.
    So we decide to ask the XI experts in this forum to give us a general lessen about the ABAP proxy: how it works, why we should create the HTTP destinations, how do the destinations work and so on.
    Thanks a lot in advance!
    With best regards
    Xiang

    Hi
    Once you create the interface in XI, you generate the proxies on your R3 system.
    Client Proxies -->
    This is done for outbound interfaces. You generate the proxy and then write a report that fills in the proxy class with the data and pushes it to XI.
    Server proxies -->
    Generated for inbound interfaces. Generate the proxy and write the implementation for the exectue method that deals with the data sent from XI to the R3 system
    Abap Proxy
    ABAP Proxies in XI(Client Proxy)
    Smarter Approach for coding ABAP Proxies
    The specified item was not found.
    ABAP Proxy - XML to ABAP Transformation
    http://help.sap.com/saphelp_nw04/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm
    why we should create the HTTP destinations, how do the destinations work and so on.
    we create http destiantio because in proxies , adapter is not use so who is goin to send the message to integration server ...by creating http destinatio we create integration engine which send messg to IS . then messg is routed .and all
    error in HTTP to file scenario http to file
    hope this help's  you
    Regard's,
    Chetan Ahuja

  • How to extract attachment from ABAP proxy and store in archive link....

    Hi Experts,
    I need to consume an incoming email attachment in the ABAP Proxy program (POP Mail  --> PI --> ABAP Proxy) and then store this file in the IBM content management server through the Archvie Link connection.
    Any idea how to implement this piece of code in ABAP?
    Regards,
    Shobhit

    Hi Shobhit
    You can get the files from Sender Mail adapter. In proxy implement the method of protocol IF_WSPROTOCOL_ATTACHMENTS as said above.
    Archive Link supports HTTP, RFC etc depends on the system you are going to use for archiving. For your case you have IBM server i think you have to do HTTP synchronous. This will be like an interface again for you.
    Why are you using ERP system in middle. I think you can directly dump data to IBM server.
    Thanks
    Gaurav

  • Coding for ABAP Proxy and mapping

    Hi XI Ds
    which one need coding neither ABAP Proxy nor ABAP Mapping
    Thanks

    Hi Kushee  ,
    We need coding for both ABAP Proxy and mapping. We need to know some OO(Object Oreinted) ABAP concepts.
    We can also import JAVA CODE for certain functionality.
    Check the following websites for clarity:
    how to create a flat file out of an IDoc-XML by means of an ABAP mapping program and the J2EE File Adapter.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
    cheers!
    gyanaraj

  • Direct Connection ABAP Proxy and Java Proxy possible ????

    Hi Folks ,
    As i read as direct connection possible between 2 SAP systems only ..
    and also i read as WS Direct Connection u2013 (Java) ..
    What it means ?? is it ABAP Proxy to Java Proxy using Direct connection ??  Like Java Client Proxy and ABAP Server proxy
    I am not clear on this.. Could you please explain or help me on this . ??
    Siva..

    Hi ,
    +You can do both for java proxies as well Abap proxies.+
    As per the following points
    1. Point-to-point connection is a new capability available with SAP NW PI 7.1. It allows applications or systems to send messages using WS-RM without going through a middleware, e.g. PI, but still using a centralized tool to design and
    configure the interfaces and connection properties.
    2. SAP XI 3.0/PI 7.00 or higher releases can be licensed based on the total volume of messages in
    gigabytes (GB) that is processed per month. The size of the payload is determined in the integration
    server. The information is then aggregated according to sender and receiver system.
    Question :
    1. If Message exchange between 2 SAP applications using direct connection .. Then dont we need to consider about licencing cost for volume of messages per month ?
    2. So if i use ABAP Client Proxy to Java Server proxy  scenario.. can i use direct connection  ? Eg., SAP ECC to java application ?
    In both the cases PI Runtime is not required  .. Am i right ?
    Please clarify..
    Siva..

  • Abap proxy and java proxy

    Hi
    Could you plz tell me when should we select ABAP Proxy and when should java proxy ?? Is it like that in SAP systems we use ABAP proxy and non-sap systems we use JAVA proxy ??
    Thanks
    Kumar

    To connect to SAP system with WAS >= 6.4, ABAP proxy is used.
    <i>
    Is it like that in SAP systems we use ABAP proxy and non-sap systems we use JAVA proxy ?? </i>
    Not always. As i mentioned the limitation of ABAP proxy.
    Also, Java Proxies cannot be used for any non-SAP application. it is generally used for communication with Java Application
    Regards,
    Prateek

  • Java Proxy and ABAP Proxy

    hi,
    can any one send me some documents on Java Proxy and ABBAP Proxy
    regards,
    John

    hi,
    Proxies are nothing but a mechanism to shift the application logic from the XI server onto the sender or reciever system so as to reduce the effort on the side of XI.Depending upon where the proxies are generated ,it is differentiated as client proxy ( sender ) and server proxy ( receiver ) .In R3 system having WAS 6.2 and above its already has an inbuilt small IE so the proxy generation is favoured and possilbe,for more on this please go thru the following links
    Proxies: are interfaces which will get executed in the application system. They can be created only in the system from message interfaces using the proxy generation functions.
    The biggest advantage of the proxy is that it always by passes the Adapter Engine and will directly interact with the application system and Integration engine - so it will and should give us a better performance.
    The literal definition of a proxy is an object / process authorized to act for another; an agent or a substitute. In simpler terms, proxies in the XI context are objects used to encapsulate the creation (from a sender system) or parsing of XML (at a receiver system) as well as the communication with the relevant runtime components required to send or receive those messages. The Proxy Runtime controls these objects / processes, and can itself be controlled by the applications it communicates with.
    The Proxy currently has the following components available:
    1. ABAP Proxy – Communication using XI or Web Services
    2. Java Proxy– Communication using XI (J2EE)
    For further reference, visit the following sites,
    To test a connection - /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    Client Proxy - /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
    Server Proxy - /people/siva.maranani/blog/2005/04/03/abap-server-proxies
    Testing proxy - /people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
    JAVA Proxies:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
    ABAP Proxies:
    /people/sap.user72/blog/2005/12/13/integration-builders-through-proxy-server-part--2
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
    /people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies
    /people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
    /people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
    /people/sukumar.natarajan/blog/2007/01/07/how-to-raise-alerts-from-abap-proxy
    /people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
    ON SDN TV
    https://www.sdn.sap.com/irj/sdn/advancedsearch?query=abap%20proxy%20xi&cat=sdn_all&start=11#

  • Create a abap server proxy and consume the service with the pi WS Navigator

    hi all:
    i create a abap server proxy ,i use the t_code "sproxy"  to generate the proxy, and then write the abap code to implemente the method;    then i use the T-code (soamanager)  to define the  endpoint,  but when i click the " Open WSDL document for selected binding" to get the WSDL  file ; some error occur,the error is follow:
    ==========================================================================
    Service cannot be reached
    What has happened?
    URL http://foxxi:50000/sap/bc/srt/wsdl/bndg_000C2938EF591DEE8A9A8D3DD5CCB6AD/wsdl11/allinone/ws_policy/document call was terminated because the corresponding service is not available.
    Note
    The termination occurred in system XIF with error code 403 and for the reason Forbidden.
    The selected virtual host was 0 .
    What can I do?
    Please select a valid URL.
    If it is a valid URL, check whether service /sap/bc/srt/wsdl/bndg_000C2938EF591DEE8A9A8D3DD5CCB6AD/wsdl11/allinone/ws_policy/document is active in transaction SICF.
    If you do not yet have a user ID, contact your system administrator.
    ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:FOXXI_XIF_00-v:0-s:403-r:Forbidden
    HTTP 403 - Forbidden
    Your SAP Internet Communication Framework Team
    ==========================================================================
    when i go to the ws navigator to consume the service  i can not find the service which i define, but some system content display ,  what's the problem

    had a chance to look at this?
    /people/jitender.chauhan/blog/2009/04/20/service-enabling-in-abap

Maybe you are looking for

  • Error While Executing the Asset history report S_ALR_87011990

    Hi, I am getting the below error while executing the Asset History Report - S_ALR_87011990 No data was selected Message no. AB064 Kindly advice me

  • Getting the name of outer class in an inner class

    Hi, I have a private inner class, something like this: public class OuterClass extends AnotherClass { public OuterClass() { supre(); private class innerClass1 extends SomeotherClass { protected void someMethod() { // how to get the name of outer clas

  • Denim update lumia 930

    I have a lumia 930 ( mobile operator 000-ZA, RM-1045_1065 ) and its not even on the list on th official update availability page. will i get the denim update & if so, when?

  • BGP route selection from LAN to WAN

    Hi, I am going to implement a multihome internet connection to two different ISP. Before implementing in real network, I have prepared the same in GNS3 and testing. Subnet 10.x.5.0/24 should take R1 to outside from LAN and 10.x.6.0/24 should take R2

  • After update mac os 10.9 wifi LOST CONNECTION

    After I update the lastest operation system, my air lost connection frequently. Each time I have to manually turn off the Wi-Fi for half minute. Then turn it up and it works again. It has happen for dozens of times. Is there anyway to fix it?