[IDEA] Allow specifying a timeout for a javascript reader/writer

[mgaffigan]

Is your feature request related to a problem? Please describe.
I just found out an interface stopped polling 30+ days ago. It's unclear why, but it was stuck in "Reading", so I assume it was mid-execution of the javascript reader. Restarting the channel restarted message flow.

Describe your use case
When a javascript reader gets "hung", I want an error, not a silent failure.

Describe the solution you'd like
An option for timeout in milliseconds on the source/destination for js. When the timeout is hit, the read/write is aborted.

Describe alternatives you've considered
External monitoring can only detect message flow. On high volume channels, the "Reading" state is typical, and thus not indicative of an issue.

[gibson9583]

I have run into similar situations. A configurable timeout would be wonderful.