[
https://issues.apache.org/jira/browse/OPENMEETINGS-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299891#comment-16299891
]
Maxim Solodovnik commented on OPENMEETINGS-1789:
------------------------------------------------
There shouldn't be any issues ....
Could you please test using latest nightly build?
https://builds.apache.org/view/M-R/view/OpenMeetings/job/OpenMeetings%204.0.x/
(166+)?
And provide very detailed steps how this can be reproduced if it fails at
4.0.2-SNAPSHOT?
Thanks in advance
> 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, 16.04 and windows
> 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)
