HttpCoreNIOListener System may be unstable: IOReactor encountered a runtime exception : null

Home » Forums » Project: WSO2 Enterprise Service Bus (WSO2 ESB)
nomadmot's picture
Submitted by nomadmot on October 7, 2009 - 09:14
When I attempt to post a SOAP message to WSO2 ESB using a proprietary, internal API we developed (based on Axis 1.1 - don't ask), the ESB server sends an HTTP 400 Bad Request response and goes into a loop, displaying "HttpCoreNIOListener System may be unstable: IOReactor encountered a runtime exception : null" over and over again. I'm working on the bad client request issue separately, my question here is regarding the WSO2 server loop. Apparently the Synapse team is aware of the problem and committed a fix back in late September. When can we expect to see the fix rolled into WSO2? For obvious reasons, we can't consider WSO2 as a production solution when we have a client in the wild that crashes it.
‹ 2-way SSL connection Saving message to a folder structure ›
supun's picture

Hi, Can you check the URL

Submitted by supun on October 9, 2009 - 15:17.
Hi, Can you check the URL and see weather it has a space? Supun..
nomadmot's picture

checked URL

Submitted by nomadmot on October 12, 2009 - 09:36.
The URL doesn't have a space. I'm currently trying to get our proprietary client to work with one of the WSO2 proxy samples. I verified that it's requesting the service properly. However, I suspect that there's something in the HTTP headers that our client generates that the WSO2 server doesn't like. Frankly, I'm much more concerned about the WSO2 ESB server going into a loop when it receives one of these requests. We can't deploy this as mission-critical infrastructure while it's stability depends on well-behaved clients. Is there any fix on the works to make the WSO2 server more robust when it receives a bad request?
jay.graves.gmail.com's picture

We have the same issue.

Submitted by jay.graves.gmail.com on January 21, 2010 - 10:34.
We have the same issue. Does anyone have any update on this? Our log is filling up with "HttpCoreNIOListener - System may be unstable: IOReactor encountered a runtime exception :" Thanks in advance, Jay
ruwan's picture

Fixed for the 2.1.3/3.0.0 (planned to be out in mid April)

Submitted by ruwan on March 17, 2010 - 18:28.
Hi Thomas/Jay, This is cause by a malformed URL, anyway the ESB nhttp transport shouldn't go onto a loop and this has been fixed for the coming 3.0.0 release as well as for the 2.1.3 patched release. Extremely sorry for the late response. Thanks, Ruwan Linton Technical Lead & Product Manager - WSO2 ESB
library project main code
Popular Content
Learn Cloud
Learn
Cloud

How to deploy a web application in StratosLive using Carbon Studio
The WSO2 Application Server is a reliable application server that can host your enterprise web applications. The WSO2 Application Server as a Service is offered in StratosLive, the WSO2 Platform as a Service. This article explains how a simple web application can be developed and deployed from Carbon Studio to the WSO2 Application Server...
more>

Latest Webinar
KPI definition with Business Activity Monitor 2.0
Different groups within an organization need to monitor different Key Performance Indicators (KPIs) - An operations team will be interested in the response times of business services and loads of each service,..
Thursday, February 9th 2012, 09.00 AM (PST)
Register Now!

Thursday, February 9th 2012, 10.00 AM (GMT)
Register Now!