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 2012/07/18 21:56:00 UTC
[jira] [Closed] (OPENMEETINGS-169) Clean up WhiteBoardService to
use proper sync methods
[ https://issues.apache.org/jira/browse/OPENMEETINGS-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik closed OPENMEETINGS-169.
-----------------------------------------
Assignee: Maxim Solodovnik (was: SebastianWagner)
Closing all old 'Resolved' issues
> Clean up WhiteBoardService to use proper sync methods
> -----------------------------------------------------
>
> Key: OPENMEETINGS-169
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-169
> Project: Openmeetings
> Issue Type: Task
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Fix For: 2.0 Apache Incubator Release
>
>
> The whiteboard service currently syncs whiteboard events to AVClient... that makes no sense.
> Also it does not check if rcl == null (meaning: He does not check if a client currently already has disconnected while syncing)
> That results in exceptions like:
> ERROR 04-14 13:18:14.001 WhiteBoardService.java 143835 791 org.openmeetings.app.remote.WhiteBoardService [NioProcessor-5] - [removeUserFromAllLists]
> java.lang.NullPointerException: null
> at org.openmeetings.app.remote.WhiteBoardService.removeUserFromAllLists(WhiteBoardService.java:771) ~[openmeetings-2.0.0-SNAPSHOT.jar:na]
> at org.openmeetings.app.remote.red5.ScopeApplicationAdapter.roomLeaveByScope(ScopeApplicationAdapter.java:596) [openmeetings-2.0.0-SNAPSHOT.jar:na]
> at org.openmeetings.app.remote.red5.ScopeApplicationAdapter.roomLeave(ScopeApplicationAdapter.java:533) [openmeetings-2.0.0-SNAPSHOT.jar:na]
> at org.red5.server.adapter.MultiThreadedApplicationAdapter.leave(MultiThreadedApplicationAdapter.java:519) [red5.jar:na]
> The sync methods in the Whiteboard Service should use the same mechanism like the ones in the ScopeApplicationAdapter.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira