Camel doesn't return error while invoking jbi endpoint which doesn't exist, setting up a infinite loop on retry
Issue
- Camel doesn't return error while invoking jbi endpoint which doesn't exist, setting up an infinite loop on retry
The following Came route was used in this example:
from("jbi:endpoint:https://my.namespace.com/OTA_PingCamel/my?mep=in-optional-out")
.process(logStart(Level.INFO, "com.my.camel", "OTA_PingCamel route processing has started"))
.to("direct:goToNotExistingJBIEndpoint")
.process(logEnd(Level.INFO, "com.my.camel", "OTA_PingCamel route processing has ended"));
The following will be seen in the log:
15:21:53,062 | INFO | rovider-thread-5 | camel | 119 - com.myproject.camel-endpoints - 1.0.0.SNAPSHOT | OTA_PingCamel route processing has started
15:21:53,062 | INFO | rovider-thread-4 | camel | 119 - com.myproject.camel-endpoints - 1.0.0.SNAPSHOT | OTA_PingCamel route processing has started
15:21:53,062 | INFO | rovider-thread-6 | camel | 119 - com.myproject.camel-endpoints - 1.0.0.SNAPSHOT | OTA_PingCamel route processing has started
15:21:53,063 | INFO | rovider-thread-7 | camel | 119 - com.myproject.camel-endpoints - 1.0.0.SNAPSHOT | OTA_PingCamel route processing has started
...
Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: GC overhead limit exceeded
This occurs if the route is invoked via JBI.
Environment
- Fuse ESB 7.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
