You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (JIRA)" <ji...@apache.org> on 2017/12/19 05:52:02 UTC

[jira] [Commented] (OPENMEETINGS-1789) WicketRuntimeException comes suddenly while entering the meeting with the obtained hash

    [ https://issues.apache.org/jira/browse/OPENMEETINGS-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296258#comment-16296258 ] 

Maxim Solodovnik commented on OPENMEETINGS-1789:
------------------------------------------------

What OM version are you using?
Could you check with latest release?

> WicketRuntimeException comes suddenly while entering the meeting with the obtained hash
> ---------------------------------------------------------------------------------------
>
>                 Key: OPENMEETINGS-1789
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1789
>             Project: Openmeetings
>          Issue Type: Bug
>          Components: HTML5/Room
>    Affects Versions: 3.2.1, 3.3.0, 3.3.1, 3.3.2, 4.0.0
>         Environment: ubuntu 14.04 and 16.04
>            Reporter: Sridhar S
>            Assignee: Maxim Solodovnik
>              Labels: newbie
>         Attachments: openmeetings_errorlog
>
>   Original Estimate: 128h
>  Remaining Estimate: 128h
>
> The openmeetings will be running properly for some time and entering into room and carrying out the meetings will also run without any issues, but suddenly after a day or after some time, when a user tries to join a meeting, he will get the hash, but after entering that hash to join the meeting,   he gets "internal server error" at the UI of the room and after checking the logs, there will be an exception called org.apache.wicket.WicketRuntimeException: Exception in rendering component: [HtmlHeaderItemsContainer [Component id = _header_]].
> Then, after we restart the openmeetings, It continues to work fine. 
> But, after deploying in production it not acceptable to keep restarting and also it becomes difficult to track issues.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)