You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (JIRA)" <ji...@apache.org> on 2017/08/02 03:45:00 UTC

[jira] [Updated] (OPENMEETINGS-1677) Clustering seems to be broken

     [ https://issues.apache.org/jira/browse/OPENMEETINGS-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Solodovnik updated OPENMEETINGS-1677:
-------------------------------------------
    Description: 
Client UIDs are currently being stored in static Map in Wicket Application
This is not cluster aware

Following components need to be checked
-1) Documentation
2) DB
3) Application wide caches
4) WebSocket messages-
5*) HTML5 WB

  was:
Client UIDs are currently being stored in static Map in Wicket Application
This is not cluster aware

Following components need to be checked
1) Documentation
2) red5 quartz settings
3) OM room


> Clustering seems to be broken
> -----------------------------
>
>                 Key: OPENMEETINGS-1677
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1677
>             Project: Openmeetings
>          Issue Type: Bug
>          Components: Cluster
>    Affects Versions: 3.2.0
>            Reporter: Maxim Solodovnik
>            Assignee: Maxim Solodovnik
>            Priority: Blocker
>             Fix For: 3.3.1, 4.0.0
>
>
> Client UIDs are currently being stored in static Map in Wicket Application
> This is not cluster aware
> Following components need to be checked
> -1) Documentation
> 2) DB
> 3) Application wide caches
> 4) WebSocket messages-
> 5*) HTML5 WB



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)