dendi-wang/thingsboard
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

removed try-catch for checkSessionsTimeout because for actor all messages are processed sequentially

Browse Source
This commit is contained in:
Sergey Matvienko 2022-01-14 11:52:59 +02:00
parent 1507ac69ab
commit 3a00a792c3
1 changed files with 6 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
application/src/main/java/org/thingsboard/server/actors/device/DeviceActorMessageProcessor.java
View File

@ -966,7 +966,6 @@ class DeviceActorMessageProcessor extends AbstractContextAwareMsgProcessor {
final long expTime = System.currentTimeMillis() - systemContext.getSessionInactivityTimeout();
List<UUID> expiredIds = null;
try {
for (Map.Entry<UUID, SessionInfoMetaData> kv : sessions.entrySet()) { //entry set are cached for stable sessions
if (kv.getValue().getLastActivityTime() < expTime) {
final UUID id = kv.getKey();
@ -974,14 +973,8 @@ class DeviceActorMessageProcessor extends AbstractContextAwareMsgProcessor {
expiredIds = new ArrayList<>(1); //most of the expired sessions is a single event
}
expiredIds.add(id);
}
}
} catch (ConcurrentModificationException ignored) {
//Sessions are not thread safe and possible exceptions
//It is an extremely rare event
//Complete session check will perform on the next check
}
if (expiredIds != null) {
int removed = 0;