Every time a request is made to MuleReceiverServlet the endpoint bound to the receiver gets re-wrapped. Over time this causes a stack overflow. You should to reproduce on the sample webapp with this script: for ((i=0;i<100000;i++)); do curl -d "payload=foo" http://c18-rb-dev40-app1:7006/mule-examples/rest?endpoint=greeter; done > /dev/null 2>&1 Here's an excerpt of mine from the mailing list describing the details of the problem: To follow up on this I've found the bug in the Mule code, but I'm not sure what the correct fix is. The MuleReceiverServlet has this line that gets executed on every request at line 315: receiver.setEndpoint(new DynamicURIInboundEndpoint(receiver.getEndpoint(), new MuleEndpointURI( getRequestUrl(httpServletRequest)))); The receiver has the same lifecycle as the servlet, so it gets re-used for each request. The problem is that for each request, the receivers endpoint basically gets wrapped one more time. In our tests after about 20K requests we get a stack overflow exception, because there are 20K DynamicURIInboundEndpoints wrapping each other. It can be changed to only wrap the endpoint if it's not already an instance of DynamicURIInboundEndpoint, but I don't know if that would meet intent of the author of this code. Can anyone with knowledge of this code point out what the proper fix is? This bug will cause Mule to constistantly crash. ----- Original Message ---- From: Bill Graham <emailbillgraham@yahoo.com> To: Mule users <user@mule.codehaus.org> Sent: Friday, September 12, 2008 10:37:11 AM Subject: [mule-user] Infinite exception loop at DynamicURIInboundEndpoint Hi, This morning I found an exception that was in the logs that was caught in an infinite loop. Is this a known issue, or has anyone seen this? Unfortunately it's not entirely clear what request triggered this, nor how to reproduce, but we're investigating that. This is was in the logs: [2008-09-11 19:13:40.353] at java.util.AbstractList.iterator(AbstractList.java:337) [2008-09-11 19:13:40.353] at java.util.AbstractList.hashCode(AbstractList.java:627) [2008-09-11 19:13:40.353] at java.util.Collections$UnmodifiableList.hashCode(Collections.java:1153) [2008-09-11 19:13:40.353] at org.mule.util.ClassUtils.hash(ClassUtils.java:788) [2008-09-11 19:13:40.353] at org.mule.endpoint.AbstractEndpoint.hashCode(AbstractEndpoint.java:315) [2008-09-11 19:13:40.353] at org.mule.endpoint.DynamicURIInboundEndpoint.hashCode(DynamicURIInboundEndpoint.java:170) [2008-09-11 19:13:40.353] at org.mule.endpoint.DynamicURIInboundEndpoint.hashCode(DynamicURIInboundEndpoint.java:170) [2008-09-11 19:13:40.353] at org.mule.endpoint.DynamicURIInboundEndpoint.hashCode(DynamicURIInboundEndpoint.java:170) [2008-09-11 19:13:40.353] at org.mule.endpoint.DynamicURIInboundEndpoint.hashCode(DynamicURIInboundEndpoint.java:170) [[ repeats indefinitely ]] Looking at the code (Mule 2.0.2) DynamicURIInboundEndpoint wraps another endpoint, and hashCode traverses through calling each. In my case it seems the DynamicURIInboundEndpoint is wrapping itself. Any ideas how that could happen? Here's the code from DynamicURIInboundEndpoint with line 170 pointed out: public int hashCode() { final int prime = 31; int result = 1; result = prime * result + ((dynamicEndpointURI == null) ? 0 : dynamicEndpointURI.hashCode()); result = prime * result + ((endpoint == null) ? 0 : endpoint.hashCode()); <<---- line 170 return result; } thanks, Bill