You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/07/28 09:10:00 UTC
[jira] [Commented] (OPENMEETINGS-1677) Clustering seems to be
broken
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16104696#comment-16104696 ]
ASF subversion and git services commented on OPENMEETINGS-1677:
---------------------------------------------------------------
Commit 2c0468f35486c8f96dfd79786027fec74036791b in openmeetings's branch refs/heads/3.3.x from [~solomax]
[ https://git-wip-us.apache.org/repos/asf?p=openmeetings.git;h=2c0468f ]
[OPENMEETINGS-1677] documentation update, dependencies update
> 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) red5 quartz settings
> 3) OM room
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)