You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@synapse.apache.org by Laurent CHARTIER <ex...@agora.msa.fr> on 2008/06/13 17:40:51 UTC
RE : [Synapse 1.1.1] - Proxy timeout
It takes 60 seconds to have a timeout.
I tried to increase the timeout with nhttp.properties.
But... It seems that my Synapse locks between the moment it prepare the
connection (I see HTTP connection [/170.217.170.36:3520]: HTTP/1.1 200 OK)
and the moment it sends the response data.
2008-06-13 17:33:49,887 [HttpClientWorker-2] DEBUG SOAPMessageFormatter -
contentType from the OMOutputFormat =text/xml
2008-06-13 17:33:49,887 [HttpClientWorker-2] DEBUG SOAPMessageFormatter -
contentType returned =text/xml; charset=UTF-8
2008-06-13 17:33:49,888 [HttpClientWorker-2] DEBUG
LoggingNHttpServerConnection - HTTP connection [/170.217.170.36:3529]:
HTTP/1.1 200 OK
2008-06-13 17:33:49,889 [HttpClientWorker-2] DEBUG LoggingIOSession - I/O
session 3 [interested ops: [r]; ready ops: [r]]: Set event [w]
2008-06-13 17:36:45,045 [I/O dispatcher 4] DEBUG LoggingNHttpServiceHandler
- HTTP connection [/170.217.170.36:3529]: Timeout
2008-06-13 17:36:45,046 [I/O dispatcher 4] DEBUG ServerHandler - Connection
Timeout for request to : /soap/R5WSService Probably the keepalive connection
was closed
2008-06-13 17:36:45,046 [I/O dispatcher 4] DEBUG LoggingIOSession - I/O
session 3 [interested ops: [r]; ready ops: [r]]: Shutdown
2008-06-13 17:36:45,046 [I/O dispatcher 4] DEBUG LoggingNHttpServiceHandler
- HTTP connection [closed]: Closed
2008-06-13 17:36:45,046 [I/O dispatcher 4] DEBUG ServerHandler - Connection
closed
After this, it seems that Synapse is locked. "CTRL+C" can't close the
instance....
-----Message d'origine-----
De : Asankha C. Perera [mailto:asankha@wso2.com]
Envoyé : vendredi 13 juin 2008 13:07
À : user@synapse.apache.org
Objet : Re: [Synapse 1.1.1] - Proxy timeout
Hi Laurent
> I encounter some timeout problems with a Synapse installation. My
> client(170.217.170.36) invokes Synapse(170.243.1.100:8210), then
> Synapse do its job. But before it can respond to my client, it says "
> HTTP connection [/170.217.170.36:2115]: Timeout". My client never
> receives the response.
>
> Can somebody help me with that problem? Can I parameter the proxy
> (synapse.xml) in order to increase this timeout?
>
How long does it take for Synapse to respond back to the client? Is it
around 30 secs or 60?.. also how have you implemented your client? Is it
a Java client, Axis2 client or .Net client etc? Basically you need to
increase the socket timeout, but from Synapse side its already set to 60
or 120 secs as I remember, so probably your client is terminating the
connection. I will need full logs to confirm this
asankha
Ce message est protégé par les règles relatives au secret des correspondances. Il est donc établi à destination exclusive de son destinataire. Celui-ci peut donc contenir des informations confidentielles. La divulgation de ces informations est à ce titre rigoureusement interdite. Si vous avez reçu ce message par erreur, merci de le renvoyer à l'expéditeur dont l'adresse e-mail figure ci-dessus et de détruire le message ainsi que toute pièce jointe.
This message is protected by the secrecy of correspondence rules. Therefore, this message is intended solely for the attention of the addressee. This message may contain privileged or confidential information, as such the disclosure of these informations is strictly forbidden. If, by mistake, you have received this message, please return this message to the addressser whose e-mail address is written above and destroy this message and all files attached.
RE : RE : RE : [Synapse 1.1.1] - Proxy timeout
Posted by Laurent CHARTIER <ex...@agora.msa.fr>.
JIRA updated
Laurent.
-----Message d'origine-----
De : Asankha C. Perera [mailto:asankha@wso2.com]
Envoyé : vendredi 20 juin 2008 16:42
À : user@synapse.apache.org
Objet : Re: RE : RE : [Synapse 1.1.1] - Proxy timeout
Laurent
> JIRA done: https://issues.apache.org/jira/browse/SYNAPSE-370
>
Can you also tell me how your client is implemented? is it an Axis2 web
service client? is it SOAP UI ? etc.. and also what is the OS hosting
this client? Is it Windows/Linux etc
Is there any sample you can post, that could help me re-create this issue?
asankha
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com
Ce message est protégé par les règles relatives au secret des correspondances. Il est donc établi à destination exclusive de son destinataire. Celui-ci peut donc contenir des informations confidentielles. La divulgation de ces informations est à ce titre rigoureusement interdite. Si vous avez reçu ce message par erreur, merci de le renvoyer à l'expéditeur dont l'adresse e-mail figure ci-dessus et de détruire le message ainsi que toute pièce jointe.
This message is protected by the secrecy of correspondence rules. Therefore, this message is intended solely for the attention of the addressee. This message may contain privileged or confidential information, as such the disclosure of these informations is strictly forbidden. If, by mistake, you have received this message, please return this message to the addressser whose e-mail address is written above and destroy this message and all files attached.
Re: RE : RE : [Synapse 1.1.1] - Proxy timeout
Posted by "Asankha C. Perera" <as...@wso2.com>.
Laurent
> JIRA done: https://issues.apache.org/jira/browse/SYNAPSE-370
>
Can you also tell me how your client is implemented? is it an Axis2 web
service client? is it SOAP UI ? etc.. and also what is the OS hosting
this client? Is it Windows/Linux etc
Is there any sample you can post, that could help me re-create this issue?
asankha
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com
RE : RE : [Synapse 1.1.1] - Proxy timeout
Posted by Laurent CHARTIER <ex...@agora.msa.fr>.
JIRA done: https://issues.apache.org/jira/browse/SYNAPSE-370
Laurent.
-----Message d'origine-----
De : Asankha C. Perera [mailto:asankha@wso2.com]
Envoyé : vendredi 13 juin 2008 18:41
À : user@synapse.apache.org
Objet : Re: RE : [Synapse 1.1.1] - Proxy timeout
Laurent
> It takes 60 seconds to have a timeout. I tried to increase the timeout
> with nhttp.properties.
>
You need to still tell me about your client as well, since thats the
party terminating the connection :-) !
> But... It seems that my Synapse locks between the moment it prepare
> the connection (I see HTTP connection [/170.217.170.36:3520]: HTTP/1.1
> 200 OK) and the moment it sends the response data.
>
> 2008-06-13 17:33:49,887 [HttpClientWorker-2] DEBUG
> SOAPMessageFormatter - contentType from the OMOutputFormat =text/xml
> 2008-06-13 17:33:49,887 [HttpClientWorker-2] DEBUG
> SOAPMessageFormatter - contentType returned =text/xml; charset=UTF-8
> 2008-06-13 17:33:49,888 [HttpClientWorker-2] DEBUG
> LoggingNHttpServerConnection - HTTP connection [/170.217.170.36:3529]:
> HTTP/1.1 200 OK 2008-06-13 17:33:49,889 [HttpClientWorker-2] DEBUG
> LoggingIOSession - I/O session 3 [interested ops: [r]; ready ops:
> [r]]: Set event [w] 2008-06-13 17:36:45,045 [I/O dispatcher 4] DEBUG
> LoggingNHttpServiceHandler
> - HTTP connection [/170.217.170.36:3529]: Timeout
> 2008-06-13 17:36:45,046 [I/O dispatcher 4] DEBUG ServerHandler -
> Connection Timeout for request to : /soap/R5WSService Probably the
> keepalive connection was closed 2008-06-13 17:36:45,046 [I/O
> dispatcher 4] DEBUG LoggingIOSession - I/O session 3 [interested ops:
> [r]; ready ops: [r]]: Shutdown 2008-06-13 17:36:45,046 [I/O dispatcher
> 4] DEBUG LoggingNHttpServiceHandler
> - HTTP connection [closed]: Closed
> 2008-06-13 17:36:45,046 [I/O dispatcher 4] DEBUG ServerHandler -
> Connection closed
>
> After this, it seems that Synapse is locked. "CTRL+C" can't close the
>
Can you share your synapse.xml and any other information to reproduce
this consistently? A JIRA would be great too, so that I can take a
closer look
asankha
Ce message est protégé par les règles relatives au secret des correspondances. Il est donc établi à destination exclusive de son destinataire. Celui-ci peut donc contenir des informations confidentielles. La divulgation de ces informations est à ce titre rigoureusement interdite. Si vous avez reçu ce message par erreur, merci de le renvoyer à l'expéditeur dont l'adresse e-mail figure ci-dessus et de détruire le message ainsi que toute pièce jointe.
This message is protected by the secrecy of correspondence rules. Therefore, this message is intended solely for the attention of the addressee. This message may contain privileged or confidential information, as such the disclosure of these informations is strictly forbidden. If, by mistake, you have received this message, please return this message to the addressser whose e-mail address is written above and destroy this message and all files attached.
Re: RE : [Synapse 1.1.1] - Proxy timeout
Posted by "Asankha C. Perera" <as...@wso2.com>.
Laurent
> It takes 60 seconds to have a timeout. I tried to increase the timeout with nhttp.properties.
>
You need to still tell me about your client as well, since thats the
party terminating the connection :-) !
> But... It seems that my Synapse locks between the moment it prepare the
> connection (I see HTTP connection [/170.217.170.36:3520]: HTTP/1.1 200 OK)
> and the moment it sends the response data.
>
> 2008-06-13 17:33:49,887 [HttpClientWorker-2] DEBUG SOAPMessageFormatter -
> contentType from the OMOutputFormat =text/xml
> 2008-06-13 17:33:49,887 [HttpClientWorker-2] DEBUG SOAPMessageFormatter -
> contentType returned =text/xml; charset=UTF-8
> 2008-06-13 17:33:49,888 [HttpClientWorker-2] DEBUG
> LoggingNHttpServerConnection - HTTP connection [/170.217.170.36:3529]:
> HTTP/1.1 200 OK
> 2008-06-13 17:33:49,889 [HttpClientWorker-2] DEBUG LoggingIOSession - I/O
> session 3 [interested ops: [r]; ready ops: [r]]: Set event [w]
> 2008-06-13 17:36:45,045 [I/O dispatcher 4] DEBUG LoggingNHttpServiceHandler
> - HTTP connection [/170.217.170.36:3529]: Timeout
> 2008-06-13 17:36:45,046 [I/O dispatcher 4] DEBUG ServerHandler - Connection
> Timeout for request to : /soap/R5WSService Probably the keepalive connection
> was closed
> 2008-06-13 17:36:45,046 [I/O dispatcher 4] DEBUG LoggingIOSession - I/O
> session 3 [interested ops: [r]; ready ops: [r]]: Shutdown
> 2008-06-13 17:36:45,046 [I/O dispatcher 4] DEBUG LoggingNHttpServiceHandler
> - HTTP connection [closed]: Closed
> 2008-06-13 17:36:45,046 [I/O dispatcher 4] DEBUG ServerHandler - Connection
> closed
>
> After this, it seems that Synapse is locked. "CTRL+C" can't close the
>
Can you share your synapse.xml and any other information to reproduce
this consistently? A JIRA would be great too, so that I can take a
closer look
asankha