Thank you very much Maxim. We will test it and let you know. El 17/04/2015 07:31, "Maxim Solodovnik" <solomax...@gmail.com> escribió:
> just have tested (sorry for delay) > the following issue was reproduced and fixed: > https://issues.apache.org/jira/browse/OPENMEETINGS-1199 > could you please test latest snapshot: #137 > https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.0.x/ > > please report any further issues :) > the feature seems to be not very commonly used > > On Mon, Apr 13, 2015 at 6:49 PM, OpenAr-IT Soluciones <opena...@gmail.com> > wrote: > >> Hi Maxim, >> >> Just asking if you had a chance to test the cluster configuration. >> >> Thanks, >> >> >> On Wed, Apr 8, 2015 at 12:43 PM, Maxim Solodovnik <solomax...@gmail.com> >> wrote: >> >>> I believe there might be several issues here: >>> 0) we might broke something :( (will try to test it later) >>> 1) some configurations might be missing >>> 2) to see "cluster in action" you should access 2+ rooms >>> >>> not sure what is actually wrong >>> will try to set up cluster and double-check your results >>> >>> On Wed, Apr 8, 2015 at 8:59 PM, OpenAr-IT Soluciones <opena...@gmail.com >>> > wrote: >>> >>>> OK thanks, but the issues seems to be that the cluster is not working >>>> because when I check the connections from Administration --> Connections >>>> the field "Server Address" shows "no cluster" instead of the server's IP. >>>> >>>> [image: Inline image 1] >>>> >>>> Is it possible to debug this since the red5.sh does not show any errors? >>>> >>>> >>>> Thanks in advance. >>>> >>>> >>>> On Wed, Apr 8, 2015 at 11:48 AM, Maxim Solodovnik <solomax...@gmail.com >>>> > wrote: >>>> >>>>> Quartz scheduler should not be clustered >>>>> you just need to be able to have different rooms on the different >>>>> servers and thus be able to save bandwidth/cpu >>>>> >>>>> On Wed, Apr 8, 2015 at 8:03 PM, OpenAr-IT Soluciones < >>>>> opena...@gmail.com> wrote: >>>>> >>>>>> Hi Maxim, we hace configured the cluster based on: >>>>>> http://openmeetings.apache.org/Clustering.html page. But when we do >>>>>> the tests with 2 users logged in the Master server, we see the cluster is >>>>>> not working. The Conexions page shows the following: >>>>>> >>>>>> 12user1 >>>>>> Wed Apr 08 10:35:28 ART 20157Expulsar al usuariono cluster13Wed Apr >>>>>> 08 10:35:32 ART 20157*Expulsar al usuario*no cluster16user2 >>>>>> Wed Apr 08 10:52:34 ART 20152Expulsar al usuariono cluster17Wed Apr >>>>>> 08 10:52:39 ART 20152*Expulsar al usuario*no cluster >>>>>> And when the script red5.sh is starting it shows: >>>>>> >>>>>> org.quartz.core.QuartzScheduler - Scheduler meta-data: Quartz >>>>>> Scheduler (v2.1.7) >>>>>> 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' with >>>>>> instanceId 'NON_CLUSTERED' >>>>>> Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally. >>>>>> NOT STARTED. >>>>>> Currently in standby mode. >>>>>> Number of jobs executed: 0 >>>>>> Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 >>>>>> threads. >>>>>> Using job-store 'org.quartz.simpl.RAMJobStore' - which does not >>>>>> support persistence. and is *not clustered.* >>>>>> >>>>>> Should it say "clustered" or it is fine what is says? >>>>>> >>>>>> Do you know if there is some configuration extra that is missing on >>>>>> the Clustering page? >>>>>> >>>>>> >>>>>> Thanks in advance. >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> WBR >>>>> Maxim aka solomax >>>>> >>>> >>>> >>> >>> >>> -- >>> WBR >>> Maxim aka solomax >>> >> >> > > > -- > WBR > Maxim aka solomax >
