You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Hubert, Eric" <Er...@foxmobile.com> on 2009/04/17 02:58:17 UTC
Endless recursion in FaultHandler.handleFault()
Hi all,
Has someone ever seen something like that? It happened while local testing with Synapse trunk.
[...]
at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:107)
at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:107)
at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:181)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
at org.apache.synapse.transport.nhttp.ServerWorker.processPost(ServerWorker.java:287)
at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:194)
at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
[HttpServerWorker-1] WARN FaultHandler - ERROR_CODE : 0 ERROR_MESSAGE : Unexpected error during sending message out
[HttpServerWorker-1] DEBUG AxisService - Get operation for anonOutInOp
[HttpServerWorker-1] DEBUG AxisService - Found axis operation: org.apache.synapse.core.axis2.DynamicAxisOperation@2f06b6
[HttpServerWorker-1] DEBUG ConfigurationContext - registerOperationContext (false): org.apache.axis2.context.OperationContext@cbbdf3 with key: urn:uuid:9FBF099295ABAFDCF71239925998622
[HttpServerWorker-1] DEBUG SandeshaModule$1 - Unsetting USE_ASYNC_OPERATIONS and DISABLE_RESPONSE_ACK for unreliable message
[HttpServerWorker-1] DEBUG SandeshaModule$1 - Entry: SandeshaModule::resolveTarget
[HttpServerWorker-1] DEBUG SandeshaUtil - Entry: SandeshaUtil::isMessageUnreliable
[HttpServerWorker-1] DEBUG SandeshaUtil - Exit: SandeshaUtil::isMessageUnreliable, false
[HttpServerWorker-1] DEBUG SandeshaModule$1 - Exit: SandeshaModule::resolveTarget
[HttpServerWorker-1] DEBUG ProjectResourceBundle - org.apache.axis2.i18n.resource::handleGetObject(cannotInferTransport)
[HttpServerWorker-1] ERROR ClientUtils - The system cannot infer the transport information from the /services/cmretrieval-game URL.
[HttpServerWorker-1] DEBUG ProjectResourceBundle - org.apache.axis2.i18n.resource::handleGetObject(cannotInferTransport)
[HttpServerWorker-1] ERROR Axis2Sender - Unexpected error during sending message out
org.apache.axis2.AxisFault: The system cannot infer the transport information from the /services/myservice URL.
at org.apache.axis2.description.ClientUtils.inferOutTransport(ClientUtils.java:82)
at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:123)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:317)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:56)
at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:191)
at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:194)
at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:61)
at org.apache.synapse.endpoints.IndirectEndpoint.send(IndirectEndpoint.java:54)
at org.apache.synapse.endpoints.LoadbalanceEndpoint.send(LoadbalanceEndpoint.java:84)
at org.apache.synapse.endpoints.LoadbalanceEndpoint.onChildEndpointFail(LoadbalanceEndpoint.java:122)
at org.apache.synapse.endpoints.AbstractEndpoint.invokeNextFaultHandler(AbstractEndpoint.java:401)
at org.apache.synapse.endpoints.AbstractEndpoint.onFault(AbstractEndpoint.java:286)
at org.apache.synapse.endpoints.AddressEndpoint.onFault(AddressEndpoint.java:45)
at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:101)
at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:107)
at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:107)
at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:107)
[...]
at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:107)
at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:107)
at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:107) […]
at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:181)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
at org.apache.synapse.transport.nhttp.ServerWorker.processPost(ServerWorker.java:287)
at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:194)
at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
[HttpServerWorker-1] WARN FaultHandler - ERROR_CODE : 0 ERROR_MESSAGE : Unexpected error during sending message out
[HttpServerWorker-1] DEBUG AxisService - Get operation for anonOutInOp
[HttpServerWorker-1] DEBUG AxisService - Found axis operation: org.apache.synapse.core.axis2.DynamicAxisOperation@2f06b6
[HttpServerWorker-1] DEBUG ConfigurationContext - registerOperationContext (false): org.apache.axis2.context.OperationContext@15cb20e with key: urn:uuid:9FBF099295ABAFDCF71239925998622
[HttpServerWorker-1] DEBUG SandeshaModule$1 - Unsetting USE_ASYNC_OPERATIONS and DISABLE_RESPONSE_ACK for unreliable message
[HttpServerWorker-1] DEBUG SandeshaModule$1 - Entry: SandeshaModule::resolveTarget
[HttpServerWorker-1] DEBUG SandeshaUtil - Entry: SandeshaUtil::isMessageUnreliable
[HttpServerWorker-1] DEBUG SandeshaUtil - Exit: SandeshaUtil::isMessageUnreliable, false
[HttpServerWorker-1] DEBUG SandeshaModule$1 - Exit: SandeshaModule::resolveTarget
[HttpServerWorker-1] DEBUG ProjectResourceBundle - org.apache.axis2.i18n.resource::handleGetObject(cannotInferTransport)
[HttpServerWorker-1] ERROR ClientUtils - The system cannot infer the transport information from the /services/cmretrieval-game URL.
[HttpServerWorker-1] DEBUG ProjectResourceBundle - org.apache.axis2.i18n.resource::handleGetObject(cannotInferTransport)
Regards,
Eric
Re: Endless recursion in FaultHandler.handleFault()
Posted by Ruwan Linton <ru...@gmail.com>.
I am just going through some samples again, it is just the setTo which
causes this issue, indeed options like FaultTo and other addressing stuff
has to be copied, but not sure.
Thanks,
Ruwan
On Mon, Apr 20, 2009 at 12:12 PM, Hubert, Eric <Er...@foxmobile.com>wrote:
> Hi Ruwan,
>
>
>
> no problem. I can confirm your fix is solving the issue I had. Looking at
> your change one may consider renaming the cloneOptions() in the
> MessageHelper(), or? Now it is neither a deep copy nor a complete flat copy,
> or? You simply skip cloning all the addressing options. I think this should
> be at least reflected in the JavaDoc, although it might be better to change
> the method name as well.
>
>
>
> Regards,
>
> Eric
> ------------------------------
>
> *From:* Ruwan Linton [mailto:ruwan.linton@gmail.com]
> *Sent:* Monday, April 20, 2009 7:25 AM
> *To:* dev@synapse.apache.org
> *Subject:* Re: Endless recursion in FaultHandler.handleFault()
>
>
>
> Eric I properly fixed this.... you may verify this, sorry for the trouble.
>
> Thanks,
> Ruwan
>
> On Sat, Apr 18, 2009 at 10:35 PM, Hubert, Eric <Er...@foxmobile.com>
> wrote:
>
> Hi Andreas,
>
> thanks for quickly fixing this! I was working on a couple of small
> improvements and was very confused as this suddenly happened. I was not sure
> whether it was related to my changes or the svn up. ;-)
>
> Regards,
> Eric
>
> > See SYNAPSE-525.
> >
> > Andreas
>
>
>
>
> --
> Ruwan Linton
> Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>
--
Ruwan Linton
Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com
RE: Endless recursion in FaultHandler.handleFault()
Posted by "Hubert, Eric" <Er...@foxmobile.com>.
Hi Ruwan,
no problem. I can confirm your fix is solving the issue I had. Looking at your change one may consider renaming the cloneOptions() in the MessageHelper(), or? Now it is neither a deep copy nor a complete flat copy, or? You simply skip cloning all the addressing options. I think this should be at least reflected in the JavaDoc, although it might be better to change the method name as well.
Regards,
Eric
________________________________
From: Ruwan Linton [mailto:ruwan.linton@gmail.com]
Sent: Monday, April 20, 2009 7:25 AM
To: dev@synapse.apache.org
Subject: Re: Endless recursion in FaultHandler.handleFault()
Eric I properly fixed this.... you may verify this, sorry for the trouble.
Thanks,
Ruwan
On Sat, Apr 18, 2009 at 10:35 PM, Hubert, Eric <Er...@foxmobile.com> wrote:
Hi Andreas,
thanks for quickly fixing this! I was working on a couple of small improvements and was very confused as this suddenly happened. I was not sure whether it was related to my changes or the svn up. ;-)
Regards,
Eric
> See SYNAPSE-525.
>
> Andreas
--
Ruwan Linton
Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com
Re: Endless recursion in FaultHandler.handleFault()
Posted by Ruwan Linton <ru...@gmail.com>.
Eric I properly fixed this.... you may verify this, sorry for the trouble.
Thanks,
Ruwan
On Sat, Apr 18, 2009 at 10:35 PM, Hubert, Eric <Er...@foxmobile.com>wrote:
> Hi Andreas,
>
> thanks for quickly fixing this! I was working on a couple of small
> improvements and was very confused as this suddenly happened. I was not sure
> whether it was related to my changes or the svn up. ;-)
>
> Regards,
> Eric
>
> > See SYNAPSE-525.
> >
> > Andreas
>
--
Ruwan Linton
Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com
Re: Endless recursion in FaultHandler.handleFault()
Posted by Ruwan Linton <ru...@gmail.com>.
Seems like a missing case, in the Indika's commit he is considering either
an LB or FO group child as endpoint where as, this case also is a valid root
level endpoint.
I will have a further look at this.
Thanks,
Ruwan
On Sun, Apr 19, 2009 at 5:09 PM, Hubert, Eric <Er...@foxmobile.com>wrote:
> Hi all,
>
>
>
> As no one beat me to it, I tracked down this issue to the following change
> to the onFault() method of AddressEndpoint:
>
>
>
> /**
>
> * This class represents an actual endpoint to send the message. It is
> responsible for sending the
>
> @@ -35,22 +31,32 @@
>
>
>
> public void onFault(MessageContext synCtx) {
>
>
>
> - // is this really a fault or a timeout/connection close etc?
>
> - if (isTimeout(synCtx)) {
>
> - getContext().onTimeout();
>
> - } else if (isSuspendFault(synCtx)) {
>
> - getContext().onFault();
>
> + // is this an actual leaf endpoint
>
> + if (getParentEndpoint() != null) {
>
> + // is this really a fault or a timeout/connection close etc?
>
> + if (isTimeout(synCtx)) {
>
> + getContext().onTimeout();
>
> + } else if (isSuspendFault(synCtx)) {
>
> + getContext().onFault();
>
> + }
>
> }
>
>
>
> The added null-check of the parent endpoint causes this trouble. The parent
> endpoint of my address endpoint is always null, thus the
> EndpointContext.onFault() gets never executed and we run endless circles.
>
>
>
> Removing this check, resolves the issue for me, but according to the commit
> message this seems to be done on purpose to fix another issue…
>
>
>
> Here are the details of the change:
>
>
>
> Revision: 727648
>
> Author: indika
>
> Date: 06:38:32, Thursday, 18. Dec 2008
>
> Message:
>
> Fixed an issue - JMX switch off doesn’t work due to a leaf level endpoint
> (wsdl / address) become root endpoint too (when there are only address or
> wsdl endpoint - no LB or FO endpoint with address endpoints as children).
>
>
>
> ----
>
> Modified :
> /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/SynapseConstants.java
>
> Modified :
> /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/endpoints/AbstractEndpoint.java
>
> Modified :
> /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/endpoints/AddressEndpoint.java
>
> Modified :
> /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/endpoints/EndpointContext.java
>
> Modified :
> /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/endpoints/WSDLEndpoint.java
>
>
>
>
>
> Regards,
>
> Eric
>
>
>
>
> ------------------------------
>
> *From:* Hubert, Eric [mailto:Eric.Hubert@foxmobile.com]
> *Sent:* Saturday, April 18, 2009 7:20 PM
> *To:* dev@synapse.apache.org
> *Subject:* RE: Endless recursion in FaultHandler.handleFault()
>
>
>
> Hi all,
>
>
>
> I'm still facing an issue which looks like a recursion (not the same), if
> the endpoint url is a non existing one resulting in a connection refused.
>
>
>
> Here is my endpoint config:
>
> <syn:endpoint name="servicename#1.0#lbgroupname#A1###myhost">
>
> <syn:address uri="some_non_existing_url" statistics="false">
>
> <syn:timeout>
>
> <syn:duration>120000</syn:duration>
>
> <syn:action>fault</syn:action>
>
> </syn:timeout>
>
> <syn:markForSuspension>
>
> <syn:retriesBeforeSuspend>3</syn:retriesBeforeSuspend>
>
> <syn:retryDelay>500</syn:retryDelay>
>
> </syn:markForSuspension>
>
> <syn:suspendOnFailure>
>
> <syn:initialDuration>100</syn:initialDuration>
>
> <syn:progressionFactor>3</syn:progressionFactor>
>
> <syn:maximumDuration>300000</syn:maximumDuration>
>
> </syn:suspendOnFailure>
>
> </syn:address>
>
> </syn:endpoint>
>
>
>
> [...]
>
> [HttpClientWorker-7] WARN FaultHandler - ERROR_CODE : 101503 ERROR_MESSAGE
> : Connection refused or failed for : myhost:6003
>
> [HttpClientWorker-7] DEBUG AxisService - Get operation for anonOutInOp
>
> [HttpClientWorker-7] DEBUG AxisService - Found axis operation:
> org.apache.synapse.core.axis2.DynamicAxisOperation@2720f6
>
> [HttpClientWorker-7] DEBUG ConfigurationContext - registerOperationContext
> (false): org.apache.axis2.context.OperationContext@16a9d0a with key:
> urn:uuid:EEC7CAA6BBD62D98F91240074657255
>
> [HttpClientWorker-7] DEBUG SandeshaModule$1 - Unsetting
> USE_ASYNC_OPERATIONS and DISABLE_RESPONSE_ACK for unreliable message
>
> [HttpClientWorker-7] DEBUG SandeshaModule$1 - Entry:
> SandeshaModule::resolveTarget
>
> [HttpClientWorker-7] DEBUG SandeshaUtil - Entry:
> SandeshaUtil::isMessageUnreliable
>
> [HttpClientWorker-7] DEBUG SandeshaUtil - Exit:
> SandeshaUtil::isMessageUnreliable, false
>
> [HttpClientWorker-7] DEBUG SandeshaModule$1 - Exit:
> SandeshaModule::resolveTarget
>
> [HttpClientWorker-7] DEBUG ConfigurationContext - registerOperationContext
> (false): org.apache.axis2.context.OperationContext@16a9d0a with key:
> urn:uuid:EEC7CAA6BBD62D98F91240074657255
>
> [HttpClientWorker-7] DEBUG ConfigurationContext - msgContext:
> [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] action:
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for
> Phase "soapmonitorPhase"
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase
> "soapmonitorPhase"
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for
> phase "soapmonitorPhase"
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for
> Phase "OperationOutPhase"
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase
> "OperationOutPhase"
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for
> phase "OperationOutPhase"
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for
> Phase "RMPhase"
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase "RMPhase"
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for
> phase "RMPhase"
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for
> Phase "PolicyDetermination"
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase
> "PolicyDetermination"
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for
> phase "PolicyDetermination"
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for
> Phase "MessageOut"
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase "MessageOut"
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking Handler
> 'AddressingOutHandler' in Phase 'MessageOut'
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for
> phase "MessageOut"
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for
> Phase "Security"
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase "Security"
>
> [HttpClientWorker-7] DEBUG Phase - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for
> phase "Security"
>
> [HttpClientWorker-7] DEBUG AddressingHelper - [MessageContext:
> logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] isReplyRedirected: ReplyTo
> is null. Returning false
>
> [HttpClientWorker-10] DEBUG SandeshaModule$1 - Unsetting
> USE_ASYNC_OPERATIONS and DISABLE_RESPONSE_ACK for unreliable message
>
> [HttpClientWorker-10] DEBUG SandeshaModule$1 - Entry:
> SandeshaModule::resolveTarget
>
> [HttpClientWorker-10] DEBUG SandeshaUtil - Entry:
> SandeshaUtil::isMessageUnreliable
>
> [HttpClientWorker-10] DEBUG SandeshaUtil - Exit:
> SandeshaUtil::isMessageUnreliable, false
>
> [HttpClientWorker-10] DEBUG SandeshaModule$1 - Exit:
> SandeshaModule::resolveTarget
>
> [HttpClientWorker-10] DEBUG OMNodeImpl - Builder is already complete.
>
> [HttpClientWorker-10] WARN FaultHandler - ERROR_CODE : 101503
> ERROR_MESSAGE : Connection refused or failed for :
> pls-svc-2.uat.jamba.net:6003
>
> [HttpClientWorker-10] DEBUG AxisService - Get operation for anonOutInOp
>
> [...]
>
>
>
> Any ideas? Otherwise I will try to dig into this if I find the time.
>
>
>
> Regards,
>
> Eric
>
--
Ruwan Linton
Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com
RE: Endless recursion in FaultHandler.handleFault()
Posted by "Hubert, Eric" <Er...@foxmobile.com>.
Hi all,
As no one beat me to it, I tracked down this issue to the following change to the onFault() method of AddressEndpoint:
/**
* This class represents an actual endpoint to send the message. It is responsible for sending the
@@ -35,22 +31,32 @@
public void onFault(MessageContext synCtx) {
- // is this really a fault or a timeout/connection close etc?
- if (isTimeout(synCtx)) {
- getContext().onTimeout();
- } else if (isSuspendFault(synCtx)) {
- getContext().onFault();
+ // is this an actual leaf endpoint
+ if (getParentEndpoint() != null) {
+ // is this really a fault or a timeout/connection close etc?
+ if (isTimeout(synCtx)) {
+ getContext().onTimeout();
+ } else if (isSuspendFault(synCtx)) {
+ getContext().onFault();
+ }
}
The added null-check of the parent endpoint causes this trouble. The parent endpoint of my address endpoint is always null, thus the EndpointContext.onFault() gets never executed and we run endless circles.
Removing this check, resolves the issue for me, but according to the commit message this seems to be done on purpose to fix another issue…
Here are the details of the change:
Revision: 727648
Author: indika
Date: 06:38:32, Thursday, 18. Dec 2008
Message:
Fixed an issue - JMX switch off doesn’t work due to a leaf level endpoint (wsdl / address) become root endpoint too (when there are only address or wsdl endpoint - no LB or FO endpoint with address endpoints as children).
----
Modified : /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/SynapseConstants.java
Modified : /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/endpoints/AbstractEndpoint.java
Modified : /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/endpoints/AddressEndpoint.java
Modified : /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/endpoints/EndpointContext.java
Modified : /synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/endpoints/WSDLEndpoint.java
Regards,
Eric
________________________________
From: Hubert, Eric [mailto:Eric.Hubert@foxmobile.com]
Sent: Saturday, April 18, 2009 7:20 PM
To: dev@synapse.apache.org
Subject: RE: Endless recursion in FaultHandler.handleFault()
Hi all,
I'm still facing an issue which looks like a recursion (not the same), if the endpoint url is a non existing one resulting in a connection refused.
Here is my endpoint config:
<syn:endpoint name="servicename#1.0#lbgroupname#A1###myhost">
<syn:address uri="some_non_existing_url" statistics="false">
<syn:timeout>
<syn:duration>120000</syn:duration>
<syn:action>fault</syn:action>
</syn:timeout>
<syn:markForSuspension>
<syn:retriesBeforeSuspend>3</syn:retriesBeforeSuspend>
<syn:retryDelay>500</syn:retryDelay>
</syn:markForSuspension>
<syn:suspendOnFailure>
<syn:initialDuration>100</syn:initialDuration>
<syn:progressionFactor>3</syn:progressionFactor>
<syn:maximumDuration>300000</syn:maximumDuration>
</syn:suspendOnFailure>
</syn:address>
</syn:endpoint>
[...]
[HttpClientWorker-7] WARN FaultHandler - ERROR_CODE : 101503 ERROR_MESSAGE : Connection refused or failed for : myhost:6003
[HttpClientWorker-7] DEBUG AxisService - Get operation for anonOutInOp
[HttpClientWorker-7] DEBUG AxisService - Found axis operation: org.apache.synapse.core.axis2.DynamicAxisOperation@2720f6
[HttpClientWorker-7] DEBUG ConfigurationContext - registerOperationContext (false): org.apache.axis2.context.OperationContext@16a9d0a with key: urn:uuid:EEC7CAA6BBD62D98F91240074657255
[HttpClientWorker-7] DEBUG SandeshaModule$1 - Unsetting USE_ASYNC_OPERATIONS and DISABLE_RESPONSE_ACK for unreliable message
[HttpClientWorker-7] DEBUG SandeshaModule$1 - Entry: SandeshaModule::resolveTarget
[HttpClientWorker-7] DEBUG SandeshaUtil - Entry: SandeshaUtil::isMessageUnreliable
[HttpClientWorker-7] DEBUG SandeshaUtil - Exit: SandeshaUtil::isMessageUnreliable, false
[HttpClientWorker-7] DEBUG SandeshaModule$1 - Exit: SandeshaModule::resolveTarget
[HttpClientWorker-7] DEBUG ConfigurationContext - registerOperationContext (false): org.apache.axis2.context.OperationContext@16a9d0a with key: urn:uuid:EEC7CAA6BBD62D98F91240074657255
[HttpClientWorker-7] DEBUG ConfigurationContext - msgContext: [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] action:
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for Phase "soapmonitorPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase "soapmonitorPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for phase "soapmonitorPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for Phase "OperationOutPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase "OperationOutPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for phase "OperationOutPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for Phase "RMPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase "RMPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for phase "RMPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for Phase "PolicyDetermination"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase "PolicyDetermination"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for phase "PolicyDetermination"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for Phase "MessageOut"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase "MessageOut"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking Handler 'AddressingOutHandler' in Phase 'MessageOut'
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for phase "MessageOut"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for Phase "Security"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase "Security"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for phase "Security"
[HttpClientWorker-7] DEBUG AddressingHelper - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] isReplyRedirected: ReplyTo is null. Returning false
[HttpClientWorker-10] DEBUG SandeshaModule$1 - Unsetting USE_ASYNC_OPERATIONS and DISABLE_RESPONSE_ACK for unreliable message
[HttpClientWorker-10] DEBUG SandeshaModule$1 - Entry: SandeshaModule::resolveTarget
[HttpClientWorker-10] DEBUG SandeshaUtil - Entry: SandeshaUtil::isMessageUnreliable
[HttpClientWorker-10] DEBUG SandeshaUtil - Exit: SandeshaUtil::isMessageUnreliable, false
[HttpClientWorker-10] DEBUG SandeshaModule$1 - Exit: SandeshaModule::resolveTarget
[HttpClientWorker-10] DEBUG OMNodeImpl - Builder is already complete.
[HttpClientWorker-10] WARN FaultHandler - ERROR_CODE : 101503 ERROR_MESSAGE : Connection refused or failed for : pls-svc-2.uat.jamba.net:6003
[HttpClientWorker-10] DEBUG AxisService - Get operation for anonOutInOp
[...]
Any ideas? Otherwise I will try to dig into this if I find the time.
Regards,
Eric
RE: Endless recursion in FaultHandler.handleFault()
Posted by "Hubert, Eric" <Er...@foxmobile.com>.
Hi all,
I'm still facing an issue which looks like a recursion (not the same), if the endpoint url is a non existing one resulting in a connection refused.
Here is my endpoint config:
<syn:endpoint name="servicename#1.0#lbgroupname#A1###myhost">
<syn:address uri="some_non_existing_url" statistics="false">
<syn:timeout>
<syn:duration>120000</syn:duration>
<syn:action>fault</syn:action>
</syn:timeout>
<syn:markForSuspension>
<syn:retriesBeforeSuspend>3</syn:retriesBeforeSuspend>
<syn:retryDelay>500</syn:retryDelay>
</syn:markForSuspension>
<syn:suspendOnFailure>
<syn:initialDuration>100</syn:initialDuration>
<syn:progressionFactor>3</syn:progressionFactor>
<syn:maximumDuration>300000</syn:maximumDuration>
</syn:suspendOnFailure>
</syn:address>
</syn:endpoint>
[...]
[HttpClientWorker-7] WARN FaultHandler - ERROR_CODE : 101503 ERROR_MESSAGE : Connection refused or failed for : myhost:6003
[HttpClientWorker-7] DEBUG AxisService - Get operation for anonOutInOp
[HttpClientWorker-7] DEBUG AxisService - Found axis operation: org.apache.synapse.core.axis2.DynamicAxisOperation@2720f6
[HttpClientWorker-7] DEBUG ConfigurationContext - registerOperationContext (false): org.apache.axis2.context.OperationContext@16a9d0a with key: urn:uuid:EEC7CAA6BBD62D98F91240074657255
[HttpClientWorker-7] DEBUG SandeshaModule$1 - Unsetting USE_ASYNC_OPERATIONS and DISABLE_RESPONSE_ACK for unreliable message
[HttpClientWorker-7] DEBUG SandeshaModule$1 - Entry: SandeshaModule::resolveTarget
[HttpClientWorker-7] DEBUG SandeshaUtil - Entry: SandeshaUtil::isMessageUnreliable
[HttpClientWorker-7] DEBUG SandeshaUtil - Exit: SandeshaUtil::isMessageUnreliable, false
[HttpClientWorker-7] DEBUG SandeshaModule$1 - Exit: SandeshaModule::resolveTarget
[HttpClientWorker-7] DEBUG ConfigurationContext - registerOperationContext (false): org.apache.axis2.context.OperationContext@16a9d0a with key: urn:uuid:EEC7CAA6BBD62D98F91240074657255
[HttpClientWorker-7] DEBUG ConfigurationContext - msgContext: [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] action:
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for Phase "soapmonitorPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase "soapmonitorPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for phase "soapmonitorPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for Phase "OperationOutPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase "OperationOutPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for phase "OperationOutPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for Phase "RMPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase "RMPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for phase "RMPhase"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for Phase "PolicyDetermination"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase "PolicyDetermination"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for phase "PolicyDetermination"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for Phase "MessageOut"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase "MessageOut"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking Handler 'AddressingOutHandler' in Phase 'MessageOut'
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for phase "MessageOut"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking pre-condition for Phase "Security"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Invoking phase "Security"
[HttpClientWorker-7] DEBUG Phase - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] Checking post-conditions for phase "Security"
[HttpClientWorker-7] DEBUG AddressingHelper - [MessageContext: logID=urn:uuid:EEC7CAA6BBD62D98F91240074679600] isReplyRedirected: ReplyTo is null. Returning false
[HttpClientWorker-10] DEBUG SandeshaModule$1 - Unsetting USE_ASYNC_OPERATIONS and DISABLE_RESPONSE_ACK for unreliable message
[HttpClientWorker-10] DEBUG SandeshaModule$1 - Entry: SandeshaModule::resolveTarget
[HttpClientWorker-10] DEBUG SandeshaUtil - Entry: SandeshaUtil::isMessageUnreliable
[HttpClientWorker-10] DEBUG SandeshaUtil - Exit: SandeshaUtil::isMessageUnreliable, false
[HttpClientWorker-10] DEBUG SandeshaModule$1 - Exit: SandeshaModule::resolveTarget
[HttpClientWorker-10] DEBUG OMNodeImpl - Builder is already complete.
[HttpClientWorker-10] WARN FaultHandler - ERROR_CODE : 101503 ERROR_MESSAGE : Connection refused or failed for : pls-svc-2.uat.jamba.net:6003
[HttpClientWorker-10] DEBUG AxisService - Get operation for anonOutInOp
[...]
Any ideas? Otherwise I will try to dig into this if I find the time.
Regards,
Eric
RE: Endless recursion in FaultHandler.handleFault()
Posted by "Hubert, Eric" <Er...@foxmobile.com>.
Hi Andreas,
thanks for quickly fixing this! I was working on a couple of small improvements and was very confused as this suddenly happened. I was not sure whether it was related to my changes or the svn up. ;-)
Regards,
Eric
> See SYNAPSE-525.
>
> Andreas
Re: Endless recursion in FaultHandler.handleFault()
Posted by Andreas Veithen <an...@gmail.com>.
See SYNAPSE-525.
Andreas
On Fri, Apr 17, 2009 at 02:58, Hubert, Eric <Er...@foxmobile.com> wrote:
> Hi all,
>
>
>
> Has someone ever seen something like that? It happened while local testing
> with Synapse trunk.
>
>
>
> [...]
>
> at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:107)
>
> at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:107)
>
> at
> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:181)
>
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
>
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
>
> at
> org.apache.synapse.transport.nhttp.ServerWorker.processPost(ServerWorker.java:287)
>
> at
> org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:194)
>
> at
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>
> at java.lang.Thread.run(Thread.java:619)
>
> [HttpServerWorker-1] WARN FaultHandler - ERROR_CODE : 0 ERROR_MESSAGE :
> Unexpected error during sending message out
>
> [HttpServerWorker-1] DEBUG AxisService - Get operation for anonOutInOp
>
> [HttpServerWorker-1] DEBUG AxisService - Found axis operation:
> org.apache.synapse.core.axis2.DynamicAxisOperation@2f06b6
>
> [HttpServerWorker-1] DEBUG ConfigurationContext - registerOperationContext
> (false): org.apache.axis2.context.OperationContext@cbbdf3 with key:
> urn:uuid:9FBF099295ABAFDCF71239925998622
>
> [HttpServerWorker-1] DEBUG SandeshaModule$1 - Unsetting USE_ASYNC_OPERATIONS
> and DISABLE_RESPONSE_ACK for unreliable message
>
> [HttpServerWorker-1] DEBUG SandeshaModule$1 - Entry:
> SandeshaModule::resolveTarget
>
> [HttpServerWorker-1] DEBUG SandeshaUtil - Entry:
> SandeshaUtil::isMessageUnreliable
>
> [HttpServerWorker-1] DEBUG SandeshaUtil - Exit:
> SandeshaUtil::isMessageUnreliable, false
>
> [HttpServerWorker-1] DEBUG SandeshaModule$1 - Exit:
> SandeshaModule::resolveTarget
>
> [HttpServerWorker-1] DEBUG ProjectResourceBundle -
> org.apache.axis2.i18n.resource::handleGetObject(cannotInferTransport)
>
> [HttpServerWorker-1] ERROR ClientUtils - The system cannot infer the
> transport information from the /services/cmretrieval-game URL.
>
> [HttpServerWorker-1] DEBUG ProjectResourceBundle -
> org.apache.axis2.i18n.resource::handleGetObject(cannotInferTransport)
>
> [HttpServerWorker-1] ERROR Axis2Sender - Unexpected error during sending
> message out
>
> org.apache.axis2.AxisFault: The system cannot infer the transport
> information from the /services/myservice URL.
>
> at
> org.apache.axis2.description.ClientUtils.inferOutTransport(ClientUtils.java:82)
>
> at
> org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:123)
>
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
>
> at
> org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:317)
>
> at
> org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:56)
>
> at
> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:191)
>
> at
> org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:194)
>
> at
> org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:61)
>
> at
> org.apache.synapse.endpoints.IndirectEndpoint.send(IndirectEndpoint.java:54)
>
> at
> org.apache.synapse.endpoints.LoadbalanceEndpoint.send(LoadbalanceEndpoint.java:84)
>
> at
> org.apache.synapse.endpoints.LoadbalanceEndpoint.onChildEndpointFail(LoadbalanceEndpoint.java:122)
>
> at
> org.apache.synapse.endpoints.AbstractEndpoint.invokeNextFaultHandler(AbstractEndpoint.java:401)
>
> at
> org.apache.synapse.endpoints.AbstractEndpoint.onFault(AbstractEndpoint.java:286)
>
> at
> org.apache.synapse.endpoints.AddressEndpoint.onFault(AddressEndpoint.java:45)
>
> at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:101)
>
> at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:107)
>
> at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:107)
>
> at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:107)
>
> [...]
>
> at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:107)
>
> at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:107)
>
> at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:107)
> […]
>
> at
> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:181)
>
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
>
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
>
> at
> org.apache.synapse.transport.nhttp.ServerWorker.processPost(ServerWorker.java:287)
>
> at
> org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:194)
>
> at
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>
> at java.lang.Thread.run(Thread.java:619)
>
> [HttpServerWorker-1] WARN FaultHandler - ERROR_CODE : 0 ERROR_MESSAGE :
> Unexpected error during sending message out
>
> [HttpServerWorker-1] DEBUG AxisService - Get operation for anonOutInOp
>
> [HttpServerWorker-1] DEBUG AxisService - Found axis operation:
> org.apache.synapse.core.axis2.DynamicAxisOperation@2f06b6
>
> [HttpServerWorker-1] DEBUG ConfigurationContext - registerOperationContext
> (false): org.apache.axis2.context.OperationContext@15cb20e with key:
> urn:uuid:9FBF099295ABAFDCF71239925998622
>
> [HttpServerWorker-1] DEBUG SandeshaModule$1 - Unsetting USE_ASYNC_OPERATIONS
> and DISABLE_RESPONSE_ACK for unreliable message
>
> [HttpServerWorker-1] DEBUG SandeshaModule$1 - Entry:
> SandeshaModule::resolveTarget
>
> [HttpServerWorker-1] DEBUG SandeshaUtil - Entry:
> SandeshaUtil::isMessageUnreliable
>
> [HttpServerWorker-1] DEBUG SandeshaUtil - Exit:
> SandeshaUtil::isMessageUnreliable, false
>
> [HttpServerWorker-1] DEBUG SandeshaModule$1 - Exit:
> SandeshaModule::resolveTarget
>
> [HttpServerWorker-1] DEBUG ProjectResourceBundle -
> org.apache.axis2.i18n.resource::handleGetObject(cannotInferTransport)
>
> [HttpServerWorker-1] ERROR ClientUtils - The system cannot infer the
> transport information from the /services/cmretrieval-game URL.
>
> [HttpServerWorker-1] DEBUG ProjectResourceBundle -
> org.apache.axis2.i18n.resource::handleGetObject(cannotInferTransport)
>
>
>
> Regards,
>
> Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org