Hello Experts,
I’m facing the same issue in my wm9.10 IS server.
In IS servers logs I’m able to see 1000s of same errors as you got previously.
The cluster is now not operational.
2017-07-12 09:52:37 EDT [ISS.0033.0154E] Could not save session 1749b6b0751617dbbd28ffffffffd821 to the session cache. put timed out.
2017-07-12 09:52:37 EDT [ISS.0033.0154E] Could not save session 1749b6b0751617dbbd28ffffffffd821 to the session cache. put timed out.
2017-07-12 09:52:37 EDT [ISS.0033.0154E] Could not save session 6abf8440aea31c06bc90ffffffffd7f8 to the session cache. put timed out.
2017-07-12 09:52:37 EDT [ISS.0033.0154E] Could not save session 6abf8440aea31c06bc90ffffffffd7f8 to the session cache. put timed out.
2017-07-12 09:52:55 EDT [ISS.0033.0154E] Could not save session 1749b6b0751617dbbd28ffffffffd821 to the session cache. put timed out.
2017-07-12 09:52:55 EDT [ISS.0033.0154E] Could not save session 6abf8440aea31c06bc90ffffffffd7f8 to the session cache. put timed out.
2017-07-12 09:52:55 EDT [ISS.0033.0154E] Could not save session 6abf8440aea31c06bc90ffffffffd7f8 to the session cache. put timed out.
2017-07-12 09:53:28 EDT [ISS.0033.0154E] Could not save session 1749b6b0751617dbbd28ffffffffd821 to the session cache. put timed out.
Because of this issue periodically IS is going to offline as well as TSA.
Can please suggest how to resolve this issue.
Thanks in advance.
Thanks,
Ram.
#Integration-Server-and-ESB#webMethods