Socket transport has a hardcoded 10 seconds transaction timeout. This should be modifiable

[GoogleCodeExporter]

The CICS transaction servicing a socket request will not wait more than 10 
seconds for an incoming request. After that, all modifications since the last 
commit are backed out.

Sometimes we may want to set this to a shorter time. Therefore we should have 
an additional transactionTimeout parameter in the host endpoint to allow 
clients to change that 10 seconds value.

Original issue reported on code.google.com by fady.mou...@gmail.com on 2 Oct 2011 at 7:55

[GoogleCodeExporter]

This has been alleviated by the pooledMaxIdleTime parameter on the host 
connection. The problem affected mainly pooled connections which remain open 
for longer than a single request/response lifetime. Such long connections are 
killed after 10 seconds. By setting pooledMaxIdleTime to less than 10 seconds, 
the connection can be closed earlier.
Observe that this is not a complete solution as it does not allow the idle 
connection to stay alive for longer than 10 seconds but then, in a CICS 
environment, 10 seconds is already a long time for a transaction to remain 
active.

Original comment by fady.mou...@gmail.com on 4 Jun 2012 at 8:03

• Added labels: Priority-Low
• Removed labels: Priority-Medium