[ https://issues.apache.org/jira/browse/OPENMEETINGS-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17109360#comment-17109360 ]
Maxim Solodovnik commented on OPENMEETINGS-2358: ------------------------------------------------ Increasing this value by default might be not very good idea Due to this is the amount of memory allocated for each WS message this feature should be re-designed the safest way I can imaging: this functionality should work via REST call ... > Download as PDF with 1 image in the whiteboard crashes the application > ---------------------------------------------------------------------- > > Key: OPENMEETINGS-2358 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2358 > Project: Openmeetings > Issue Type: Bug > Components: WhiteBoard > Affects Versions: 5.0.0-M4 > Reporter: Sebastian Wagner > Priority: Major > Fix For: 5.0.0-M5 > > Attachments: StackTrace-Crash-Room.rtf, > image-2020-05-17-09-13-26-975.png > > > Steps to reproduce: > * Open any conference room > * Upload a PNG/jpeg to the library > * Put it into the whiteboard > * Go via the menu bar > Download as PDF > Results in: > {code:java} > ERROR 05-17 09:02:57.783 o.a.w.p.w.j.WicketEndpoint:100 [tp467402189-196] - > An error occurred in web socket connection with id : 4 > org.eclipse.jetty.websocket.api.MessageTooLargeException: Text message size > [90791] exceeds maximum size [65536] > at > org.eclipse.jetty.websocket.api.WebSocketPolicy.assertValidTextMessageSize(WebSocketPolicy.java:140) > at > org.eclipse.jetty.websocket.common.Parser.assertSanePayloadLength(Parser.java:131) > at org.eclipse.jetty.websocket.common.Parser.parseFrame(Parser.java:499) > at > org.eclipse.jetty.websocket.common.Parser.parseSingleFrame(Parser.java:256) > at > org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.readParse(AbstractWebSocketConnection.java:582) > at > org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:441) > at > org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:428) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) > at > org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:426) > at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:320) > at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:158) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) > at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117) > at > org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336) > at > org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313) > at > org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171) > at > org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129) > at > org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:367) > at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:782) > at > org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:918) > at java.base/java.lang.Thread.run(Thread.java:834) > {code} > > !image-2020-05-17-09-13-26-975.png|width=353,height=220! > And if you do this few times it will crash the OpenMeetings instance and you > have to restart the server. > > There is a more complete stack trace attached. Above stack trace is when the > server is basically crashed. See: [^StackTrace-Crash-Room.rtf] > -- This message was sent by Atlassian Jira (v8.3.4#803005)