{"action":"opened","issue":{"url":"https://api.github.com/repos/wso2/product-apim/issues/3648","repository_url":"https://api.github.com/repos/wso2/product-apim","labels_url":"https://api.github.com/repos/wso2/product-apim/issues/3648/labels{/name}","comments_url":"https://api.github.com/repos/wso2/product-apim/issues/3648/comments","events_url":"https://api.github.com/repos/wso2/product-apim/issues/3648/events","html_url":"https://github.com/wso2/product-apim/issues/3648","id":355544937,"node_id":"MDU6SXNzdWUzNTU1NDQ5Mzc=","number":3648,"title":"WSO2 API-M error on invoking published API with large message","user":{"login":"nadastra","id":40881721,"node_id":"MDQ6VXNlcjQwODgxNzIx","avatar_url":"https://avatars0.githubusercontent.com/u/40881721?v=4","gravatar_id":"","url":"https://api.github.com/users/nadastra","html_url":"https://github.com/nadastra","followers_url":"https://api.github.com/users/nadastra/followers","following_url":"https://api.github.com/users/nadastra/following{/other_user}","gists_url":"https://api.github.com/users/nadastra/gists{/gist_id}","starred_url":"https://api.github.com/users/nadastra/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nadastra/subscriptions","organizations_url":"https://api.github.com/users/nadastra/orgs","repos_url":"https://api.github.com/users/nadastra/repos","events_url":"https://api.github.com/users/nadastra/events{/privacy}","received_events_url":"https://api.github.com/users/nadastra/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-08-30T11:34:32Z","updated_at":"2018-08-30T11:34:32Z","closed_at":null,"author_association":"NONE","body":"**Description:**\r\nWhen calling a published API with large messages (10MB+), the call returns within 1-2 seconds with no error but API-M logs the error below. This behavior is not consistent as post API-M restart, the invocation is seen to be successful.  One or two messages from a large number of invocations also goes through.\r\n\r\nInvoking the API directly with same messages is successful.\r\n\r\nAPI-M error:\r\n\r\n`[2018-08-23 17:22:56,690]  WARN -  Request message body data received while \r\nthe handler is in an inconsistent state REQUEST_DONE \r\n{org.apache.synapse.transport.passthru.SourceHandler}\r\n\r\n[2018-08-23 17:22:56,695]  WARN -  Trying to submit a response to an already \r\nclosed connection : http-incoming-366 \r\n{org.apache.synapse.transport.passthru.PassThroughHttpSender}\r\nIt appears that an erroneous state change is flagged while the input blocks are still being read.`\r\n\r\n\r\n**Suggested Labels:**\r\n\r\n**Suggested Assignees:**\r\n\r\n**Affected Product Version:** wso2am-2.5.0\r\n\r\n**OS, DB, other environment details and versions:**    \r\nRHEL 7.3\r\n\r\n**Steps to reproduce:**\r\nInvoke a published API (all API & API-M config is default) with large message (>10MB).\r\n\r\n**Related Issues:**"}}
{"actor":{"display_login":"nadastra"}}