Hi everyone, I'm using the camel-restlet component and get issues when there are too many connections. I have an HTTP client that creates multiple threads to send HTTP requests. However, I can't put more than 7 threads without getting problems. If I try with more than 7 threads, my camel app logs give this :
I tryed many settings, such as : However nothing changes, I can't get more than 7 requests simultaneously. So this may be the physical limit, but the component does nothing with the others requests ! It should send a 500 error or something, so that the client sends them again later. However, the client doesn't get anything and ends throwing an java.io.EOFException. How can I change this behaviour ? I have another problem : I have a camel route involving multiple components, like : from Restlet to JDBC to APNS However, the restlet component sends an answer to the client only at the end of the route. I would like to trigger an answer after, for example, the JDBC processing. I didn't find anything about this in the camel-restlet documentation, then I looked at the camel documentation. I thought I found the solution by putting the ExchangePattern <http://camel.apache.org/exchange-pattern.html> to "inOnly" at the point where I wanted my answer to be sent, but it doesn't work. The REST answer is always sent back after the last component. Any ideas ? Thanks ! -- View this message in context: http://camel.465427.n5.nabble.com/Camel-restlet-multithreading-issues-can-t-trigger-answer-tp5753708.html Sent from the Camel - Users mailing list archive at Nabble.com.
