Remsy

this seems to be something else.. can you raise an issue on the JIRA and attach this log and the configuration used and the scenario tested, for someone to take a detailed look as to what went wrong?

asankha

Schmilinsky, Remsy wrote:
Forgot to include this:

2008-09-23 09:10:14,183 [127.0.1.1-ubuntu] [HttpClientWorker-1] ERROR 
AnonymousServiceFactory Error retrieving anonymous service for QoS : __NONE__
org.apache.axis2.AxisFault: The system is attempting to access an inactive 
service: __NONE__
        at 
org.apache.axis2.engine.AxisConfiguration.getService(AxisConfiguration.java:755)
        at 
org.apache.synapse.core.axis2.AnonymousServiceFactory.getAnonymousService(AnonymousServiceFactory.java:85)
        at 
org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:213)
        at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:57)
        at 
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:222)
        at 
org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:195)
        at 
org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:157)
        at 
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:58)
        at 
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:125)
        at 
org.apache.synapse.mediators.MediatorFaultHandler.onFault(MediatorFaultHandler.java:79)
        at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:94)
        at 
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:188)
        at 
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:131)
        at 
org.apache.synapse.transport.nhttp.ClientHandler$1.run(ClientHandler.java:298)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
        at java.lang.Thread.run(Thread.java:595)
2008-09-23 09:10:14,183 [127.0.1.1-ubuntu] [HttpClientWorker-1] ERROR 
Axis2Sender Unexpected error during sending message out
org.apache.synapse.SynapseException: Error retrieving anonymous service for QoS 
: __NONE__
        at 
org.apache.synapse.core.axis2.AnonymousServiceFactory.handleException(AnonymousServiceFactory.java:122)
        at 
org.apache.synapse.core.axis2.AnonymousServiceFactory.getAnonymousService(AnonymousServiceFactory.java:115)
        at 
org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:213)
        at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:57)
        at 
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:222)
        at 
org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:195)
        at 
org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:157)
        at 
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:58)
        at 
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:125)
        at 
org.apache.synapse.mediators.MediatorFaultHandler.onFault(MediatorFaultHandler.java:79)
        at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:94)
        at 
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:188)
        at 
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:131)
        at 
org.apache.synapse.transport.nhttp.ClientHandler$1.run(ClientHandler.java:298)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
        at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.axis2.AxisFault: The system is attempting to access an 
inactive service: __NONE__
        at 
org.apache.axis2.engine.AxisConfiguration.getService(AxisConfiguration.java:755)
        at 
org.apache.synapse.core.axis2.AnonymousServiceFactory.getAnonymousService(AnonymousServiceFactory.java:85)
        ... 15 more

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Schmilinsky, Remsy
Sent: September 23, 2008 9:16 AM
To: [email protected]
Subject: Re: [esb-java-user] abnormal connection close


Hi Asankha. This the log info:

2008-09-23 09:00:06,792 [127.0.1.1-ubuntu] [HttpServerWorker-13]  INFO 
LogMediator To: http://localhost:8280/soap/Transformer,MessageID: 
urn:uuid:1CA76505829CE3EE4A1222174807357,Direction: request
2008-09-23 09:00:07,812 [127.0.1.1-ubuntu] [HttpClientWorker-1]  INFO LogMediator To: , MessageID: 
urn:uuid:1EB40901883271FB4D1222174746812073009-1951864453, Direction: request, MESSAGE = Executing default "fault" sequence, ERROR_CODE = 
00000, ERROR_MESSAGE = Connection timeout, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope 
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";><soapenv:Body><ax:text 
xmlns:ax="http://ws.apache.org/commons/ns/payload";>SAMPLE MESSAGE</ax:text></soapenv:Body></soapenv:Envelope>

So the connection from the mediator to the proxy service is timiming out. is 
there a way to fix this ?

remsy   

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Asankha C. Perera
Sent: September 23, 2008 9:03 AM
To: [email protected]
Subject: Re: [esb-java-user] abnormal connection close


Remsy

An abnormal connection close is usually initiated by the remote party, after expiration of its TCP socket timeout. A snippet from the error log/stack trace would help better analyse exact cause. This can happen for example if you send a request to server X, which takes 45 secs to respond, but server X uses a default socket timeout of 30secs, in which case the ESB that spoke to Server X would see the connection closing.

asankha

Schmilinsky, Remsy wrote:
Sometimes I am getting soap faults indicating "Abnormal connection close", and 
the original message is then returned as an error. Do you know under what conditions this 
is usual ? Of course, I am using colinux, maybe is not the ideal environment for this.

thanks

Remsy

_______________________________________________
Esb-java-user mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user


_______________________________________________
Esb-java-user mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user

_______________________________________________
Esb-java-user mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user

_______________________________________________
Esb-java-user mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user

_______________________________________________
Esb-java-user mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Reply via email to