Warning message, "Outstanding requests" shown in ActiveSpaces Cluster logs.
Article ID: KB0093578
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveSpaces | - |
| Not Applicable | - |
Description
Description:
========================
Warning message, "Outstanding requests" shown in ActiveSpaces Cluster logs.
Sample log messages.
===================
In the as-agent log files the following messages are seen.
[2015-08-28T12:58:32.155][5093][47960557119808][WARNING][ST01.$listeners][EntryManager.cpp:4429][scanForOutstandingReqs]
Outstanding requests found, total=1
[2015-08-28T12:58:32.156][5093][47960557119808][WARNING][ST01.$listeners][EntryManager.cpp:4439][scanForOutstandingReqs]
resending outstanding request=PutReq, age=198900 with route=
<Route>
c79c-55d502d7-1e4 0
c79f-55d5031e-10c 1
c79f-55d50372-bd 2
c7b4-55dcea16-29f -1
c79e-55d50349-5f 4
c79e-55d502d7-1e4 5
c79c-55d50349-5f 6
</Route>
========================
Issue/Introduction
Warning message, "Outstanding requests" shown in ActiveSpaces Cluster logs.
Resolution
AS operations will complete within write-timeout (default 60 seconds) amount of time. If an operation does not complete, this warning prints and operations will be reissued.
There are couple of reasons for an operation to timeout.
There are couple of reasons for an operation to timeout.
- A node is killed and member timeout applies.
- Seeder Joining and leaving.
- Memory is low and swapping slows down execution.
- CPU is maxed out, operations cannot complete.
- Shared All persistence is used, and the database is slow.
- Network slowness or I/O wait is on high side.
Additional Information
Feedback
Yes
No
Powered by
