Can timeout values be read from the configuration map?

[Coooz]

Hi,

One of the channels I am implementing has a HTTP Listener source and a TCP Sender destination. A requirement is that respectively both the Receive Timeout and the Response Timeout can be configured, in seconds. Is this in any way possible?
I doubt it... but it does not hurt to put the question out of course. ;^)

[pacmano1]

10,000 ms is 10 seconds.

What do you mean?

[pacmano1]

Oh, I see. Your quesiton didn't include that fact you want to source those via the config map.

Two things - probably a questionable idea because that kind of control might be connector and client based, i.e. more granular - so i would just set them in the channel.

The receive timeout on an http listener seems to support velocity replacement, but the response time out on a TCP sender doesn't.

[Coooz]

"...to source those via the config map"
Yes, that's right, that is what I want to do. I should have been clearer on that. I'll pass your reaction to my colleagues who came up with the requirement.

One more - related - thing... I wanted to test receive timeout, so that I can have a well-founded look at velocity replacement here. I set up this http listener on server 123.456.78.90:

• Local Port: 9876
• Response: Auto-generate (Destinations completed)
• Receive Timeout: 10000

Then I executed this curl command:
curl -X POST http://123.456.78.90:9876 -d @D:\Temp\CG\26_bytes.txt --limit-rate 1

I expected to see some time out error occurring 10 seconds after the curl command, either in the logs or with the messages, but it isn't there. I also expected the Response Date of the messages to be 26 seconds after the Received Date, but it is a couple of milliseconds at most. The curl command takes 26 seconds to complete though.

Imho this is the way to test receive timeout, but the results are unexpected. How can I fix this test?

[pacmano1]

The console will show an error.

e.g. http listeneer with recieve timeoout set to ${wait} which is in $cfg

curl -X POST --limit-rate 1 --data-binary @test.txt http://192.168.66.118:9999

Results in:

org.eclipse.jetty.io.RuntimeIOException: java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 1000/1000 ms
	at org.eclipse.jetty.server.Request.extractFormParameters(Request.java:600)
	at org.eclipse.jetty.server.Request.extractContentParameters(Request.java:544)
	<truncated - note I do have wait set at 1000>

[Coooz]

I am not able to reproduce the error but that is ok now, the requirement has been dropped so I don't need to do anything with it anymore.
Thank you for contributing.