Dear Maxim, Your prompt responses from across the world allows us to productively find and implement solutions that could benefit a cause beyond ourselves over time. Summarized below is the 1. Problem of continuous disconnections of OpenMeetings sessions, 2. cause of these disconnections and 3. solution to enable persistent OpenMeetings session. For greater adoption of OpenMeetings in enterprises and other users, perhaps we should share this solution in the "configuration" section on OpenMeetings Web site. If so, we would be happy to provide greater detail.
------------ Problem ------------ The sessions, both dashboard and conference rooms, ask all users to reload their browser every 30-50 seconds, still persisting with their session IDs. ------------ Cause ------------ 3.2.x extensively uses WebSockets to establish a dashboard session, create a room session and persist with it. Using WebSockets is a positive evolution, but enterprise infrastructure (hosting, server and browser) are still catching up because this new protocol was ratified in 2011 only and is still being implemented as a full-duplex RTP. 3.1.x used WebSockets for chat, and hence, the issue did not crop up unless someone used chat messaging service rigorously. ------------ Solution ------------ OpenMeetings is accessed through load balancers, proxy servers and caching servers at enterprises and Small offices that use business-grade ISP. This is not the case with home office users. Special configuration is required in load balancers, proxy servers and caching servers to persist with pings sent by OpenMeetings (MainPanel.java). Implementation: OpenMeetings by default, uses: 1. HTTP: for the WebSocket setup 2. TCP: WebSocket data exchange Different load balancers need different configurations to make OpenMeetings sessions persist beyond 50 seconds. Also, browsers may behave differently based on their versions. We have successfully tested this configuration with: 1. Apache HTTPD, 2. Nginx and 3. HAProxy. We would be happy to provide the detailed information for others' use, if needed. Thank you. Sincerely, Hemant K. Sabat Coscend Communications Solutions Web site: www.Coscend.com ------------------------------------------------------------------ Real-time, Interactive Video Collaboration, Tele-healthcare, Tele-education, Telepresence Services, on the fly… ------------------------------------------------------------------ CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail Messages from Coscend Communications Solutions' posted at: http://www.Coscend.com/Terms_and_Conditions.html -----Original Message----- From: Maxim Solodovnik [mailto:solomax...@gmail.com] Sent: Thursday, March 16, 2017 12:12 AM To: dev <dev@openmeetings.apache.org>; om.insig...@coscend.com Subject: Re: 3.2.x Disconnect Error, Menu Click Twice Error Actually 3.1.x uses WebSockets for chat messages only 3.2.x heavily uses WebSockets in room On Thu, Mar 16, 2017 at 12:08 PM, Coscend@OM <om.insig...@coscend.com> wrote: > Hello Maxim, > > Finding: We have been able to identify the possible cause of the issue. > This issue is going to affect installation of OpenMeetings 3.2.x which is > within an enterprise inside production-grade servers. > > Solution: We have successfully found and tested the solution of this issue. > Before we post it assertively for others' use, we would like to validate the > following to fool-proof our solution. > > 1. Did 3.1.x use Web sockets for creation and persistence of: > (i) dashboard session > (ii) conference room session > > 2. If 3.1.x used it, how is 3.2.x using Web sockets DIFFERENTLY for creation > and persistence of: > (i) dashboard session > (ii) conference room session > File: MainPanel.java > > protected void onTimer(AjaxRequestTarget target) { > log.debug("Sending WebSocket PING"); > WebSocketHelper.sendClient(client, new byte[1]); > } > > > Thank you. > > Sincerely, > > Hemant K. Sabat > > Coscend Communications Solutions > Web site: www.Coscend.com > ------------------------------------------------------------------ > Real-time, Interactive Video Collaboration, Tele-healthcare, > Tele-education, Telepresence Services, on the fly… > ------------------------------------------------------------------ > CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail > Messages from Coscend Communications Solutions' posted at: > http://www.Coscend.com/Terms_and_Conditions.html > > > > > -----Original Message----- > From: Coscend@OM [mailto:om.insig...@coscend.com] > Sent: Wednesday, March 15, 2017 2:12 AM > To: dev@openmeetings.apache.org > Subject: RE: 3.2.x Disconnect Error, Menu Click Twice Error > > Dear Maxim, > > To identify the cause of session disconnection, we are testing 3.2.x (no > customization) with alternative configurations: > 1. Different servers > 2. Different reverse proxy servers and 3. Different SSL settings. > > We will share the result in a day or so. Thank you. > > Sincerely, > > Hemant K. Sabat > > Coscend Communications Solutions > Web site: www.Coscend.com > ------------------------------------------------------------------ > Real-time, Interactive Video Collaboration, Tele-healthcare, > Tele-education, Telepresence Services, on the fly… > ------------------------------------------------------------------ > CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail > Messages from Coscend Communications Solutions' posted at: > http://www.Coscend.com/Terms_and_Conditions.html > -----Original Message----- > From: Maxim Solodovnik [mailto:solomax...@gmail.com] > Sent: Wednesday, March 15, 2017 12:35 AM > To: dev <dev@openmeetings.apache.org>; om.insig...@coscend.com > Subject: Re: 3.2.x Disconnect Error, Menu Click Twice Error > > Hello Hemant, > > I don't see these issues locally > What is you configuration? > Are you using apache/nginx and proxy server? > > can you reproduce these issues on our demo server? > https://om.alteametasoft.com:8443/next/ > > On Wed, Mar 15, 2017 at 11:20 AM, Coscend@OM <om.insig...@coscend.com> wrote: >> Dear OpenMeetings Developers and Testers, >> >> >> >> We are seeing three errors in the 3.2.1 RC2. These errors were not >> there in >> 3.1.5 while using the same database. Since, 3.2.1 is still under >> review for bug fixing and UAT, we are posting this to development forum. >> >> Environment: CentOS 7.2, Chrome browser >> >> >> >> 1. The service disconnects every 1-2 minutes. >> >> 2. The items in menu dropdown in Dashboard needs two clicks before it >> displays the page. >> >> 3. The Administration panel does not offer a scroll down option at the >> right end in the first instance. However, when we refresh / reload >> the page, the scroll down bar appears. >> >> >> >> What are the causes of >> >> 1. disconnection? >> >> 2. Need for multiple clicks >> >> 3. Need to reload? >> >> >> >> ============= >> >> DETAILED LOG >> >> ============= >> >> ERROR 03-14 22:40:35.832 WicketEndpoint.java 915655 86 >> org.apache.wicket.protocol.ws.javax.WicketEndpoint >> [http-nio-<IP-Port>-exec-1] - An error occurred in web socket >> connection with id : 8 >> >> java.io.IOException: Connection reset by peer >> >> at sun.nio.ch.FileDispatcherImpl.read0(Native Method) >> >> . >> >> DEBUG 03-14 22:40:35.834 MainPanel.java 915657 263 >> org.apache.openmeetings.web.common.MainPanel >> [http-nio-<IP-Port>-exec-1] - WebSocketBehavior::closeHandler [uid: >> 171f76b1-bfd5-49eb-b028-2a0f9dc0ccad, >> session: 649794A7B2803BEC0225FAD85CEAEA87, key: >> org.apache.wicket.protocol.ws.api.registry.PageIdKey@a] >> >> DEBUG 03-14 22:40:35.834 Application.java 915657 411 >> org.apache.openmeetings.web.app.Application >> [http-nio-<IP-Port>-exec-1] - Removing online room client: >> 171f76b1-bfd5-49eb-b028-2a0f9dc0ccad, room: 29 >> >> DEBUG 03-14 22:40:35.834 ScopeApplicationAdapter.java 915657 580 >> org.apache.openmeetings.core.remote.red5.ScopeApplicationAdapter >> [http-nio-<IP-Port>-exec-1] - [roomLeaveByScope] >> 171f76b1-bfd5-49eb-b028-2a0f9dc0ccad 29 Client [streamid=5, >> publicSID=171f76b1-bfd5-49eb-b028-2a0f9dc0ccad, isScreenClient=false, >> isMobile = false, roomId=29, broadCastID=5, userId=1, avsettings=av, >> isRecording=false, recordingId=null, recordingMetaDataId=null, >> screenPublishStarted=false, interviewPodId=null, server=null] Scope >> [name=29, path=/default/OpenMeetings, type=ROOM, autoStart=true, >> creationTime=1489549185019, depth=2, enabled=true, running=true] >> >> DEBUG 03-14 22:40:35.834 ScopeApplicationAdapter.java 915657 598 >> org.apache.openmeetings.core.remote.red5.ScopeApplicationAdapter >> [http-nio-<IP-Port>-exec-1] - [roomLeaveByScope] currentClient Client >> [streamid=5, publicSID=171f76b1-bfd5-49eb-b028-2a0f9dc0ccad, >> isScreenClient=false, isMobile = false, roomId=29, broadCastID=5, >> userId=1, avsettings=av, isRecording=false, recordingId=null, >> recordingMetaDataId=null, screenPublishStarted=false, >> interviewPodId=null, server=null] >> >> DEBUG 03-14 22:40:35.835 WhiteBoardService.java 915658 462 >> org.apache.openmeetings.core.remote.WhiteBoardService >> [http-nio-<IP-Port>-exec-1] - removeUserFromAllLists >> this.whiteBoardObjectListManager: >> org.apache.openmeetings.core.data.whiteboard.WhiteBoardObjectSyncMana >> g >> er@799 >> 5651d >> >> DEBUG 03-14 22:40:35.835 WhiteBoardService.java 915658 463 >> org.apache.openmeetings.core.remote.WhiteBoardService >> [http-nio-<IP-Port>-exec-1] - removeUserFromAllLists roomId: 29 >> >> DEBUG 03-14 22:40:35.835 WhiteBoardService.java 915658 477 >> org.apache.openmeetings.core.remote.WhiteBoardService >> [http-nio-<IP-Port>-exec-1] - scope Scope [name=29, >> path=/default/OpenMeetings, type=ROOM, autoStart=true, >> creationTime=1489549185019, depth=2, enabled=true, running=true] >> >> DEBUG 03-14 22:40:35.836 ScopeApplicationAdapter.java 915659 611 >> org.apache.openmeetings.core.remote.red5.ScopeApplicationAdapter >> [http-nio-<IP-Port>-exec-1] - removing Username Firstname.Lastname >> Tue Mar >> 14 22:39:45 CDT 2017 streamid: 5 >> >> DEBUG 03-14 22:40:35.836 RecordingService.java 915659 407 >> org.apache.openmeetings.core.remote.RecordingService >> [http-nio-<IP-Port>-exec-1] - ### stopRecordingShowForClient: Client >> [streamid=5, publicSID=171f76b1-bfd5-49eb-b028-2a0f9dc0ccad, >> isScreenClient=false, isMobile = false, roomId=29, broadCastID=5, >> userId=1, avsettings=av, isRecording=false, recordingId=null, >> recordingMetaDataId=null, screenPublishStarted=false, >> interviewPodId=null, server=null] >> >> ERROR 03-14 22:40:35.837 RecordingService.java 915660 256 >> org.apache.openmeetings.core.remote.RecordingService >> [http-nio-<IP-Port>-exec-1] - recordingMetaDataId is null >> >> >> >> Thank you. >> >> >> >> Sincerely, >> >> >> >> Hemant K. Sabat >> >> >> >> Coscend Communications Solutions >> >> Web site: <http://www.coscend.com/> www.Coscend.com >> >> ------------------------------------------------------------------ >> >> Real-time, Interactive Video Collaboration, Tele-healthcare, >> Tele-education, Telepresence Services, on the fly. >> >> ------------------------------------------------------------------ >> >> CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail >> Messages from Coscend Communications Solutions' posted at: >> <http://www.coscend.com/Terms_and_Conditions.html> >> http://www.Coscend.com/Terms_and_Conditions.html >> >> >> >> >> >> >> > > > > -- > WBR > Maxim aka solomax > > > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2016.0.8007 / Virus Database: 4756/14117 - Release Date: > 03/14/17 > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2016.0.8007 / Virus Database: 4756/14117 - Release Date: > 03/14/17 > > > > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2016.0.8007 / Virus Database: 4756/14117 - Release Date: > 03/14/17 > > -- WBR Maxim aka solomax ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2016.0.8007 / Virus Database: 4756/14122 - Release Date: 03/15/17 ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2016.0.8007 / Virus Database: 4756/14120 - Release Date: 03/15/17
