You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Laurent CHARTIER (JIRA)" <ji...@apache.org> on 2008/06/20 16:31:45 UTC
[jira] Created: (SYNAPSE-370) Proxy timeout
Proxy timeout
-------------
Key: SYNAPSE-370
URL: https://issues.apache.org/jira/browse/SYNAPSE-370
Project: Synapse
Issue Type: Bug
Affects Versions: 1.1.1
Environment: Os: AIX 5.3 TL5 SP1
Reporter: Laurent CHARTIER
Priority: Blocker
Attachments: synapse.xml
As discussed on the mailing list with subject [Synapse 1.1.1] - Proxy timeout (vendredi 13 juin 2008 17:42 Paris):
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.
Previously, it took 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....
The Synapse job is to transform the reveived message into an XMLMessage called AGORAMessage.
Then, this message is sent to an endpoint (stj2ee).
The response of this endpoint is then transformed again from AGORAMessage into a SOAP message.
This SOAP message should be returned to the client. (Line 74 in the synapse.xml)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-370) Proxy timeout
Posted by "Laurent CHARTIER (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laurent CHARTIER updated SYNAPSE-370:
-------------------------------------
Attachment: simpleTestSynpase.xml
> Proxy timeout
> -------------
>
> Key: SYNAPSE-370
> URL: https://issues.apache.org/jira/browse/SYNAPSE-370
> Project: Synapse
> Issue Type: Bug
> Affects Versions: 1.1.1
> Environment: Os: AIX 5.3 TL5 SP1
> Reporter: Laurent CHARTIER
> Priority: Blocker
> Attachments: simpleTestLog.txt, simpleTestSynpase.xml, synapse.xml
>
>
> As discussed on the mailing list with subject [Synapse 1.1.1] - Proxy timeout (vendredi 13 juin 2008 17:42 Paris):
> 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.
> Previously, it took 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....
> The Synapse job is to transform the reveived message into an XMLMessage called AGORAMessage.
> Then, this message is sent to an endpoint (stj2ee).
> The response of this endpoint is then transformed again from AGORAMessage into a SOAP message.
> This SOAP message should be returned to the client. (Line 74 in the synapse.xml)
> N.B.: The client invoking Synapse is SOAPUI (2.0.2) with socket timeout configured with 650000ms ans running on Windows XP Pro SP2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-370) Proxy timeout
Posted by "Laurent CHARTIER (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laurent CHARTIER updated SYNAPSE-370:
-------------------------------------
Attachment: synapse.xml
Synapse configuration file.
> Proxy timeout
> -------------
>
> Key: SYNAPSE-370
> URL: https://issues.apache.org/jira/browse/SYNAPSE-370
> Project: Synapse
> Issue Type: Bug
> Affects Versions: 1.1.1
> Environment: Os: AIX 5.3 TL5 SP1
> Reporter: Laurent CHARTIER
> Priority: Blocker
> Attachments: synapse.xml
>
>
> As discussed on the mailing list with subject [Synapse 1.1.1] - Proxy timeout (vendredi 13 juin 2008 17:42 Paris):
> 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.
> Previously, it took 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....
> The Synapse job is to transform the reveived message into an XMLMessage called AGORAMessage.
> Then, this message is sent to an endpoint (stj2ee).
> The response of this endpoint is then transformed again from AGORAMessage into a SOAP message.
> This SOAP message should be returned to the client. (Line 74 in the synapse.xml)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-370) Proxy timeout
Posted by "Dinuka Roshan Arseculeratne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626911#action_12626911 ]
Dinuka Roshan Arseculeratne commented on SYNAPSE-370:
-----------------------------------------------------
Hi Laurent,
Looking at your synapse.xml file i see that within your validate element you have not removed the 'To' Header before sending the fault message. This could be the potential problem that the client never receives a response. So can you add '<header name="To" action="remove" />' after setting the RESPONSE to true?
Thanks
Dinuka
> Proxy timeout
> -------------
>
> Key: SYNAPSE-370
> URL: https://issues.apache.org/jira/browse/SYNAPSE-370
> Project: Synapse
> Issue Type: Bug
> Affects Versions: 1.1.1
> Environment: Os: AIX 5.3 TL5 SP1
> Reporter: Laurent CHARTIER
> Priority: Blocker
> Attachments: simpleTestLog.txt, simpleTestSynpase.xml, synapse.xml
>
>
> As discussed on the mailing list with subject [Synapse 1.1.1] - Proxy timeout (vendredi 13 juin 2008 17:42 Paris):
> 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.
> Previously, it took 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....
> The Synapse job is to transform the reveived message into an XMLMessage called AGORAMessage.
> Then, this message is sent to an endpoint (stj2ee).
> The response of this endpoint is then transformed again from AGORAMessage into a SOAP message.
> This SOAP message should be returned to the client. (Line 74 in the synapse.xml)
> N.B.: The client invoking Synapse is SOAPUI (2.0.2) with socket timeout configured with 650000ms ans running on Windows XP Pro SP2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-370) Proxy timeout
Posted by "Laurent CHARTIER (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606796#action_12606796 ]
Laurent CHARTIER commented on SYNAPSE-370:
------------------------------------------
I've got a similar problem with a very simple test.
Synapse is configured to "forward" the request to an endpoint.
This endpoint is a mock, so it responds always the same message.
Then the client should receive, as a response from Synapse, the response of the mock.
But here again, there's a lock.
See simpleTestSynapse.xml & simpleTestLog.txt
> Proxy timeout
> -------------
>
> Key: SYNAPSE-370
> URL: https://issues.apache.org/jira/browse/SYNAPSE-370
> Project: Synapse
> Issue Type: Bug
> Affects Versions: 1.1.1
> Environment: Os: AIX 5.3 TL5 SP1
> Reporter: Laurent CHARTIER
> Priority: Blocker
> Attachments: synapse.xml
>
>
> As discussed on the mailing list with subject [Synapse 1.1.1] - Proxy timeout (vendredi 13 juin 2008 17:42 Paris):
> 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.
> Previously, it took 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....
> The Synapse job is to transform the reveived message into an XMLMessage called AGORAMessage.
> Then, this message is sent to an endpoint (stj2ee).
> The response of this endpoint is then transformed again from AGORAMessage into a SOAP message.
> This SOAP message should be returned to the client. (Line 74 in the synapse.xml)
> N.B.: The client invoking Synapse is SOAPUI (2.0.2) with socket timeout configured with 650000ms ans running on Windows XP Pro SP2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-370) Proxy timeout
Posted by "Laurent CHARTIER (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laurent CHARTIER updated SYNAPSE-370:
-------------------------------------
Comment: was deleted
> Proxy timeout
> -------------
>
> Key: SYNAPSE-370
> URL: https://issues.apache.org/jira/browse/SYNAPSE-370
> Project: Synapse
> Issue Type: Bug
> Affects Versions: 1.1.1
> Environment: Os: AIX 5.3 TL5 SP1
> Reporter: Laurent CHARTIER
> Priority: Blocker
> Attachments: synapse.xml
>
>
> As discussed on the mailing list with subject [Synapse 1.1.1] - Proxy timeout (vendredi 13 juin 2008 17:42 Paris):
> 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.
> Previously, it took 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....
> The Synapse job is to transform the reveived message into an XMLMessage called AGORAMessage.
> Then, this message is sent to an endpoint (stj2ee).
> The response of this endpoint is then transformed again from AGORAMessage into a SOAP message.
> This SOAP message should be returned to the client. (Line 74 in the synapse.xml)
> N.B.: The client invoking Synapse is SOAPUI (2.0.2) with socket timeout configured with 650000ms ans running on Windows XP Pro SP2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-370) Proxy timeout
Posted by "Laurent CHARTIER (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laurent CHARTIER updated SYNAPSE-370:
-------------------------------------
Description:
As discussed on the mailing list with subject [Synapse 1.1.1] - Proxy timeout (vendredi 13 juin 2008 17:42 Paris):
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.
Previously, it took 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....
The Synapse job is to transform the reveived message into an XMLMessage called AGORAMessage.
Then, this message is sent to an endpoint (stj2ee).
The response of this endpoint is then transformed again from AGORAMessage into a SOAP message.
This SOAP message should be returned to the client. (Line 74 in the synapse.xml)
N.B.: The client invoking Synapse is SOAPUI (2.0.2) with socket timeout configured with 650000ms ans running on Windows XP Pro SP2
was:
As discussed on the mailing list with subject [Synapse 1.1.1] - Proxy timeout (vendredi 13 juin 2008 17:42 Paris):
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.
Previously, it took 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....
The Synapse job is to transform the reveived message into an XMLMessage called AGORAMessage.
Then, this message is sent to an endpoint (stj2ee).
The response of this endpoint is then transformed again from AGORAMessage into a SOAP message.
This SOAP message should be returned to the client. (Line 74 in the synapse.xml)
N.B.: The client invoking Synapse is SOAPUI (2.0.2) with socket timeout configured with 650000ms
> Proxy timeout
> -------------
>
> Key: SYNAPSE-370
> URL: https://issues.apache.org/jira/browse/SYNAPSE-370
> Project: Synapse
> Issue Type: Bug
> Affects Versions: 1.1.1
> Environment: Os: AIX 5.3 TL5 SP1
> Reporter: Laurent CHARTIER
> Priority: Blocker
> Attachments: synapse.xml
>
>
> As discussed on the mailing list with subject [Synapse 1.1.1] - Proxy timeout (vendredi 13 juin 2008 17:42 Paris):
> 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.
> Previously, it took 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....
> The Synapse job is to transform the reveived message into an XMLMessage called AGORAMessage.
> Then, this message is sent to an endpoint (stj2ee).
> The response of this endpoint is then transformed again from AGORAMessage into a SOAP message.
> This SOAP message should be returned to the client. (Line 74 in the synapse.xml)
> N.B.: The client invoking Synapse is SOAPUI (2.0.2) with socket timeout configured with 650000ms ans running on Windows XP Pro SP2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-370) Proxy timeout
Posted by "Laurent CHARTIER (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626994#action_12626994 ]
Laurent CHARTIER commented on SYNAPSE-370:
------------------------------------------
I'm really sorry...
I haven't any AIX environnement to make the test....
We choose to switch to Linux (RedHat) and the problem disappear...
> Proxy timeout
> -------------
>
> Key: SYNAPSE-370
> URL: https://issues.apache.org/jira/browse/SYNAPSE-370
> Project: Synapse
> Issue Type: Bug
> Affects Versions: 1.1.1
> Environment: Os: AIX 5.3 TL5 SP1
> Reporter: Laurent CHARTIER
> Priority: Blocker
> Attachments: simpleTestLog.txt, simpleTestSynpase.xml, synapse.xml
>
>
> As discussed on the mailing list with subject [Synapse 1.1.1] - Proxy timeout (vendredi 13 juin 2008 17:42 Paris):
> 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.
> Previously, it took 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....
> The Synapse job is to transform the reveived message into an XMLMessage called AGORAMessage.
> Then, this message is sent to an endpoint (stj2ee).
> The response of this endpoint is then transformed again from AGORAMessage into a SOAP message.
> This SOAP message should be returned to the client. (Line 74 in the synapse.xml)
> N.B.: The client invoking Synapse is SOAPUI (2.0.2) with socket timeout configured with 650000ms ans running on Windows XP Pro SP2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-370) Proxy timeout
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asankha C. Perera resolved SYNAPSE-370.
---------------------------------------
Resolution: Won't Fix
Assignee: Asankha C. Perera
This is a bug on AIX, which is most probably caused by the use of the IBM JDK and/or OS differences. Similar issues have been seen on IBM mainframes, SunOS etc. A patch for the IBM JDK is/will be fully available to address this in future.
Closing this issue on the last comment from the user
> Proxy timeout
> -------------
>
> Key: SYNAPSE-370
> URL: https://issues.apache.org/jira/browse/SYNAPSE-370
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 1.1.1
> Environment: Os: AIX 5.3 TL5 SP1
> Reporter: Laurent CHARTIER
> Assignee: Asankha C. Perera
> Priority: Blocker
> Attachments: simpleTestLog.txt, simpleTestSynpase.xml, synapse.xml
>
>
> As discussed on the mailing list with subject [Synapse 1.1.1] - Proxy timeout (vendredi 13 juin 2008 17:42 Paris):
> 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.
> Previously, it took 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....
> The Synapse job is to transform the reveived message into an XMLMessage called AGORAMessage.
> Then, this message is sent to an endpoint (stj2ee).
> The response of this endpoint is then transformed again from AGORAMessage into a SOAP message.
> This SOAP message should be returned to the client. (Line 74 in the synapse.xml)
> N.B.: The client invoking Synapse is SOAPUI (2.0.2) with socket timeout configured with 650000ms ans running on Windows XP Pro SP2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-370) Proxy timeout
Posted by "Laurent CHARTIER (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laurent CHARTIER updated SYNAPSE-370:
-------------------------------------
Description:
As discussed on the mailing list with subject [Synapse 1.1.1] - Proxy timeout (vendredi 13 juin 2008 17:42 Paris):
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.
Previously, it took 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....
The Synapse job is to transform the reveived message into an XMLMessage called AGORAMessage.
Then, this message is sent to an endpoint (stj2ee).
The response of this endpoint is then transformed again from AGORAMessage into a SOAP message.
This SOAP message should be returned to the client. (Line 74 in the synapse.xml)
N.B.: The client invoking Synapse is SOAPUI (2.0.2) with socket timeout configured with 650000ms
was:
As discussed on the mailing list with subject [Synapse 1.1.1] - Proxy timeout (vendredi 13 juin 2008 17:42 Paris):
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.
Previously, it took 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....
The Synapse job is to transform the reveived message into an XMLMessage called AGORAMessage.
Then, this message is sent to an endpoint (stj2ee).
The response of this endpoint is then transformed again from AGORAMessage into a SOAP message.
This SOAP message should be returned to the client. (Line 74 in the synapse.xml)
> Proxy timeout
> -------------
>
> Key: SYNAPSE-370
> URL: https://issues.apache.org/jira/browse/SYNAPSE-370
> Project: Synapse
> Issue Type: Bug
> Affects Versions: 1.1.1
> Environment: Os: AIX 5.3 TL5 SP1
> Reporter: Laurent CHARTIER
> Priority: Blocker
> Attachments: synapse.xml
>
>
> As discussed on the mailing list with subject [Synapse 1.1.1] - Proxy timeout (vendredi 13 juin 2008 17:42 Paris):
> 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.
> Previously, it took 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....
> The Synapse job is to transform the reveived message into an XMLMessage called AGORAMessage.
> Then, this message is sent to an endpoint (stj2ee).
> The response of this endpoint is then transformed again from AGORAMessage into a SOAP message.
> This SOAP message should be returned to the client. (Line 74 in the synapse.xml)
> N.B.: The client invoking Synapse is SOAPUI (2.0.2) with socket timeout configured with 650000ms
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-370) Proxy timeout
Posted by "Laurent CHARTIER (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laurent CHARTIER updated SYNAPSE-370:
-------------------------------------
Attachment: simpleTestLog.txt
> Proxy timeout
> -------------
>
> Key: SYNAPSE-370
> URL: https://issues.apache.org/jira/browse/SYNAPSE-370
> Project: Synapse
> Issue Type: Bug
> Affects Versions: 1.1.1
> Environment: Os: AIX 5.3 TL5 SP1
> Reporter: Laurent CHARTIER
> Priority: Blocker
> Attachments: simpleTestLog.txt, simpleTestSynpase.xml, synapse.xml
>
>
> As discussed on the mailing list with subject [Synapse 1.1.1] - Proxy timeout (vendredi 13 juin 2008 17:42 Paris):
> 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.
> Previously, it took 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....
> The Synapse job is to transform the reveived message into an XMLMessage called AGORAMessage.
> Then, this message is sent to an endpoint (stj2ee).
> The response of this endpoint is then transformed again from AGORAMessage into a SOAP message.
> This SOAP message should be returned to the client. (Line 74 in the synapse.xml)
> N.B.: The client invoking Synapse is SOAPUI (2.0.2) with socket timeout configured with 650000ms ans running on Windows XP Pro SP2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-370) Proxy timeout
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated SYNAPSE-370:
------------------------------------
Component/s: Transports
> Proxy timeout
> -------------
>
> Key: SYNAPSE-370
> URL: https://issues.apache.org/jira/browse/SYNAPSE-370
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 1.1.1
> Environment: Os: AIX 5.3 TL5 SP1
> Reporter: Laurent CHARTIER
> Priority: Blocker
> Attachments: simpleTestLog.txt, simpleTestSynpase.xml, synapse.xml
>
>
> As discussed on the mailing list with subject [Synapse 1.1.1] - Proxy timeout (vendredi 13 juin 2008 17:42 Paris):
> 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.
> Previously, it took 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....
> The Synapse job is to transform the reveived message into an XMLMessage called AGORAMessage.
> Then, this message is sent to an endpoint (stj2ee).
> The response of this endpoint is then transformed again from AGORAMessage into a SOAP message.
> This SOAP message should be returned to the client. (Line 74 in the synapse.xml)
> N.B.: The client invoking Synapse is SOAPUI (2.0.2) with socket timeout configured with 650000ms ans running on Windows XP Pro SP2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org