-
Notifications
You must be signed in to change notification settings - Fork 38.8k
Description
Alejandro opened SPR-16586 and commented
When executing the command to stop the instances (stopServer.sh) or using the web console to stop the instances of websphere aplication server with normal or immediate stop, these instances do not stop, the stop fails.
[1/20/18 16:06:26:268 CET] 00000097 TimeoutManage I WTRN0006W: Transaction 0000016114196D9400000001489CCCB44A7B13B1A40632B2663ED0D9BFD85F902942FE0D 0000016114196D9400000001489CCCB44A7B13B1A40632B2663ED0D9BFD85F902942FE0D 00000001 has timed out after 120 seconds. [1/20/18 16:06:26:268 CET] 00000097 TimeoutManage I WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[org.springframework.jms.listener. DefaultMessageListenerContainer#0-774,5,]. The stack trace of this thread when the timeout occurred was:
the transactions do not end and the server does not stop having to kill it and delete the transaction log every time
IBM support gave us this bug as a possible cause:
#16409
The jira defect says affected versions are 4.0.3, 4.2.4 and is fixed in versions 4.2.5, 4.3 RC1 .
We have verified that the installed version of spring is 4.1.0.
The query is:
The version of Spring 4.1.0 Is affected by the bug?
Thanks in advance.
Reference URL: #16409
Issue Links:
- DefaultMessageListenerContainer hangs on shutdown [SPR-11787] #16409 DefaultMessageListenerContainer hangs on shutdown
- DefaultMessageListenerContainer should interrupt worker threads when not returning on shutdown [SPR-16536] #21079 DefaultMessageListenerContainer should interrupt worker threads when not returning on shutdown