-
Bug
-
Resolution: Done
-
Major
-
3.4.5.Final, 3.5.0.Beta6
-
None
In WorkerThread#openTcpStreamConnection() and WorkerThread#acceptTcpStreamConnection(), when new NioSocketStreamConnection is created, READ_TIMEOUT and WRITE_TIMEOUT options should be set, if they are defined in optionMap parameter.
I think this is a root cause for JBEAP-10038 and JBEAP-10259.
- causes
-
JBEAP-10038 [GSS](7.2.0) EJB client gets stuck in awaitResponse or AbstractHandleableCloseable when server is disconnected from network
- Closed
-
JBEAP-10259 [GSS](7.0.z) XNIO-296 - READ_TIMEOUT and WRITE_TIMEOUT options not set when opening new channel
- Closed
-
JBEAP-12670 [GSS](7.1.z) EJB client gets stuck in awaitResponse or AbstractHandleableCloseable when server is disconnected from network
- Closed