[
https://issues.apache.org/jira/browse/OPENMEETINGS-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16308382#comment-16308382
]
Sridhar S commented on OPENMEETINGS-1789:
-----------------------------------------
Create multiple custom rooms and add extenal user with same externalID and
login in all the rooms.
After getting the rooms hashes, on of the room hash in the end will definitely
throw an error in red5.log, saying:-
Failed to close the ServletOutputStream connection cleanly
java.io.IOException: An established connection was aborted by the software in
your host machine
But, if I restart Openmeetings, the same user can be used put in another rooms.
This happens only for one user, who will be part of many rooms.
> 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)
