I'm afraid it will be impossible for me to reproduce your HW configuration :((( too powerful :) Will try to double-check locally with 20 incognito browser windows in restricted Will let you know the results
On Thu, Feb 8, 2018 at 11:53 AM, محمد تشکری <[email protected]> wrote: > -One of servers( and my single server) is DL580 HP(80 core/128 GB RAM) > -Java options for HighLOAD set in red5.sh > -Ubuntu 16.04(xenial) x86_64 > -other server (the 3 ones) Super micro(24 core/128GB Ram) > -Java options are default in red5.sh > -one Os is CentOS 7.0 and 2 others are Ubuntu 16.04 Xenial x86_64 > All setting for Java options and installations of OM’s are done step by > step from openmeetings guides are in website. > -This is limits for Java Process of OM > Limit Soft Limit Hard Limit Units > Max cpu time unlimited unlimited seconds > Max file size unlimited unlimited bytes > Max data size unlimited unlimited bytes > Max stack size 8388608 unlimited bytes > Max core file size 0 unlimited bytes > Max resident set unlimited unlimited bytes > Max processes 515530 515530 > processes > Max open files 1048576 1048576 files > Max locked memory 65536 65536 bytes > Max address space unlimited unlimited bytes > Max file locks unlimited unlimited locks > Max pending signals 515530 515530 signals > Max msgqueue size 819200 819200 bytes > Max nice priority 0 0 > Max realtime priority 0 0 > Max realtime timeout unlimited unlimited us > -No suspicious log seen. > > On Feb 8, 2018, at 07:34, Maxim Solodovnik <[email protected]> wrote: > > OK, > > What OS hardware are using for your server? > Is it possible you hit some OS limitation for amount of connections? > Is there anything suspicious in system logs? > > On Wed, Feb 7, 2018 at 8:45 PM, محمد تشکری <[email protected]> > wrote: > >> unfortunately No >> >> On Feb 7, 2018, at 15:33, Maxim Solodovnik <[email protected]> wrote: >> >> Is it reproducible on our demo? >> >> WBR, Maxim >> (from mobile, sorry for the typos) >> >> On Wed, Feb 7, 2018, 18:44 محمد تشکری <[email protected]> wrote: >> >>> -Using Default OM Configuration >>> -No https/rtmps, >>> -No proxy, >>> -20 Users from 3 servers >>> -From single server I have the same Issue >>> in single server the issue occurred after 10th user joins the meeting, >>> and >>> in hazelcast server config the issue occurred after 4th user joins the >>> meeting. >>> Network test was successful in both cases. >>> >>> On Feb 7, 2018, at 14:58, Maxim Solodovnik <[email protected]> wrote: >>> >>> I'm not sure this issue is somehow caused by the cluster config .... >>> >>> What is your OM configuration? >>> Are you using HTTPS? RTMPS? >>> Do you have frontend proxy? If yes which one? Apache? nginx? >>> >>> How many users are required to reproduce this issue? >>> Is this issue 100% reproducible? if yes, what are the steps? >>> >>> Is it reproducible for you in single server configuration? >>> On our demo server? >>> >>> On Wed, Feb 7, 2018 at 6:22 PM, محمد تشکری <[email protected]> >>> wrote: >>> >>>> I think this is critical because my audience are kicked out from >>>> meeting steady and the meeting was cancelled for this issue! >>>> What config will help you? >>>> I got the hazelcast member ship OK messages, all ports are opened and >>>> hazelcast configured to discover via tcp/ip. >>>> >>>> >>>> On Feb 7, 2018, at 14:46, Maxim Solodovnik <[email protected]> >>>> wrote: >>>> >>>> Hello, >>>> >>>> Why to you think this is critical error? Usually java.io.EOFException >>>> means client has disconnected .... >>>> Can you please provide more details on your steps and configuration? >>>> >>>> On Wed, Feb 7, 2018 at 6:14 PM, Mohammad Tashackori < >>>> [email protected]> wrote: >>>> >>>>> Hi Maxim, >>>>> I’ve encountered an error with websocket in OM 4.0.1 with Hazelcast >>>>> enabled nodes >>>>> >>>>> the following messages I’ve got in one of nodes and the other have >>>>> the same errors: >>>>> =================================== >>>>> ERROR 02-05 01:04:37.320 o.a.w.p.w.j.WicketEndpoint:86 >>>>> [0.0-5080-exec-4] - An error occurred in web socket connection with id : 2 >>>>> java.io.EOFException: null >>>>> at org.apache.tomcat.util.net.Nio >>>>> Endpoint$NioSocketWrapper.fillReadBuffer(NioEndpoint.java:1167) >>>>> at org.apache.tomcat.util.net.Nio >>>>> Endpoint$NioSocketWrapper.read(NioEndpoint.java:1107) >>>>> at org.apache.tomcat.websocket.se >>>>> rver.WsFrameServer.onDataAvailable(WsFrameServer.java:72) >>>>> at org.apache.tomcat.websocket.se >>>>> rver.WsFrameServer.doOnDataAvailable(WsFrameServer.java:171) >>>>> at org.apache.tomcat.websocket.se >>>>> rver.WsFrameServer.notifyDataAvailable(WsFrameServer.java:151) >>>>> at org.apache.tomcat.websocket.se >>>>> rver.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandl >>>>> er.java:148) >>>>> at org.apache.coyote.http11.upgra >>>>> de.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:54) >>>>> at org.apache.coyote.AbstractProc >>>>> essorLight.process(AbstractProcessorLight.java:53) >>>>> at org.apache.coyote.AbstractProtocol$ConnectionHandler. >>>>> process(AbstractProtocol.java:754) >>>>> at org.apache.tomcat.util.net.Nio >>>>> Endpoint$SocketProcessor.doRun(NioEndpoint.java:1376) >>>>> at org.apache.tomcat.util.net.Soc >>>>> ketProcessorBase.run(SocketProcessorBase.java:49) >>>>> at java.util.concurrent.ThreadPoo >>>>> lExecutor.runWorker(ThreadPoolExecutor.java:1149) >>>>> at java.util.concurrent.ThreadPoo >>>>> lExecutor$Worker.run(ThreadPoolExecutor.java:624) >>>>> at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable. >>>>> run(TaskThread.java:61) >>>>> at java.lang.Thread.run(Thread.java:748) >>>>> DEBUG 02-05 01:04:37.476 o.a.o.w.c.MainPanel:180 [0.0-5080-exec-4] - >>>>> WebSocketBehavior::closeHandler [uid: >>>>> 0cc4eea2-684a-4b3a-b940-f9e87c77affa, >>>>> session: D8CB9008B6AE8913A2A77AD7 >>>>> 69C818D6, key: org.apache.wicket.protocol.ws.api.registry.PageIdKey@0] >>>>> DEBUG 02-05 01:04:37.496 o.a.o.w.a.Application:613 [0.0-5080-exec-4] - >>>>> Removing online room client: 0cc4eea2-684a-4b3a-b940-f9e87c77affa, >>>>> room: 31 >>>>> DEBUG 02-05 01:04:37.530 o.a.o.c.r.ScopeApplicationAdapter:767 >>>>> [Thread-21] - [MessageSender] -> 'Unable to send message to NULL scope' >>>>> stopStream, java.lang.Object@7098e910 >>>>> DEBUG 02-05 01:04:37.553 o.a.o.c.u.WebSocketHelper:152 >>>>> [0.0-5080-exec-4] - Sending WebSocket message: roomExit >>>>> DEBUG 02-05 01:04:37.804 o.a.o.d.d.r.PollDao:104 [0.0-5080-exec-8] - >>>>> :: hasPoll :: 31 >>>>> DEBUG 02-05 01:04:37.824 o.a.o.d.d.r.PollDao:98 [0.0-5080-exec-8] - >>>>> :: getArchived :: 31 >>>>> DEBUG 02-05 01:04:40.926 o.a.o.d.u.AuthLevelUtil:42 [0.0-5080-exec-1] >>>>> - Level Admin :: [GRANTED] >>>>> DEBUG 02-05 01:04:41.677 o.a.o.d.d.r.PollDao:104 [0.0-5080-exec-8] - >>>>> :: hasPoll :: 31 >>>>> DEBUG 02-05 01:04:41.731 o.a.o.d.d.r.PollDao:98 [0.0-5080-exec-8] - >>>>> :: getArchived :: 31 >>>>> DEBUG 02-05 01:04:43.308 o.a.o.w.c.MainPanel:117 [.0-5080-exec-10] - >>>>> Sending WebSocket PING >>>>> DEBUG 02-05 01:04:49.542 o.a.o.d.d.l.ConferenceLogDao:54 >>>>> [0.0-5080-exec-4] - [addConferenceLog]: org.apache.openmeetings.db.ent >>>>> ity.log.ConferenceLog@723af11e >>>>> DEBUG 02-05 01:04:49.566 o.a.o.w.a.Application:411 [0.0-5080-exec-4] - >>>>> Removing online client: 0cc4eea2-684a-4b3a-b940-f9e87c77affa, roomId: >>>>> null >>>>> DEBUG 02-05 01:04:49.642 o.a.o.c.u.WebSocketHelper:225 >>>>> [0.0-5080-exec-6] - Sending WebSocket message: {"type":"wb"} >>>>> ERROR 02-05 01:04:50.017 o.a.w.DefaultExceptionMapper:170 >>>>> [0.0-5080-exec-7] - Unexpected error occurred >>>>> java.lang.NullPointerException: null >>>>> at org.apache.openmeetings.web.ap >>>>> p.Application.exitRoom(Application.java:395) >>>>> at org.apache.openmeetings.web.ro >>>>> om.menu.RoomMenuPanel.exit(RoomMenuPanel.java:377) >>>>> at org.apache.openmeetings.web.ro >>>>> om.menu.RoomMenuPanel$2.onClick(RoomMenuPanel.java:107) >>>>> at com.googlecode.wicket.jquery.u >>>>> i.widget.menu.MenuBehavior.onAjax(MenuBehavior.java:112) >>>>> at com.googlecode.wicket.jquery.c >>>>> ore.ajax.JQueryAjaxBehavior.re >>>>> <http://ore.ajax.jqueryajaxbehavior.re/>spond(JQueryAjaxBehavior.java: >>>>> 173) >>>>> at org.apache.wicket.ajax.Abstrac >>>>> tDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:598) >>>>> at org.apache.wicket.core.request >>>>> .handler.ListenerRequestHandler.internalInvoke(ListenerReque >>>>> stHandler.java:306) >>>>> at org.apache.wicket.core.request >>>>> .handler.ListenerRequestHandler.invoke(ListenerRequestHandle >>>>> r.java:280) >>>>> >>>>> ============ >>>> >>>> >>>> >>>> >>>> -- >>>> WBR >>>> Maxim aka solomax >>>> >>>> >>>> محمد تشکری >>>> مشاور راهکارهای جامع فاوا >>>> >>>> >>>> >>>> >>> >>> >>> -- >>> WBR >>> Maxim aka solomax >>> >>> >>> محمد تشکری >>> مشاور راهکارهای جامع فاوا >>> >>> >>> >>> >> محمد تشکری >> مشاور راهکارهای جامع فاوا >> >> >> >> > > > -- > WBR > Maxim aka solomax > > > محمد تشکری > مشاور راهکارهای جامع فاوا > > > > -- WBR Maxim aka solomax
