[
https://issues.apache.org/jira/browse/SYNAPSE-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiranya Jayathilaka resolved SYNAPSE-915.
-----------------------------------------
Resolution: Cannot Reproduce
The original issue is clearly due to the backend server not handling chunked
encoding properly. The timeout error indicates that the backend server is not
reporting the content length correctly.
Either way we need more information to debug this problem. I'd recommend you to
try this on the latest Synapse trunk where the new pass through transport is
the default. If the problem persists, reopen the issue and provide debug level
logs and wire-level message traces.
> NIO error : insufficient system resources exist to complete the requested
> service
> ---------------------------------------------------------------------------------
>
> Key: SYNAPSE-915
> URL: https://issues.apache.org/jira/browse/SYNAPSE-915
> Project: Synapse
> Issue Type: Bug
> Components: Proxy Services, Transports
> Affects Versions: 2.1
> Environment: Windows 7, IIS 6.0, soapUI 4.5.1
> Reporter: nabil
> Attachments: synapse_insufficient_system_resources_error.7z
>
>
> Hi,
> We are invoking a secured IIS web service through our Synapse proxy service,
> but we're getting an http 500 internal server error as follows (cf. attached
> files for more details on logs and config):
> <html><head><title>Error</title></head><body>Insufficient system resources
> exist to complete the requested service.</body></html>
> However, when we try the same raw request sent by the esb, via a simple http
> client, we get the expected soap response.
> It seams like the way that the esb is sending something unexpected by IIS and
> different from the case of simple http client.
> Please, can you shed some light on this issue.
> Thanks
> Nabil
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
