[
https://issues.apache.org/jira/browse/OPENMEETINGS-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364527#comment-15364527
]
Maxim Solodovnik commented on OPENMEETINGS-1425:
------------------------------------------------
clustering was fixed in 3.1.2 (for ex. OPENMEETINGS-1350)
Could you please check latest SNAPSHOT:
https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.1.x/
> DatabaseStore java.lang.NullPointerException in addClientListItem
> -----------------------------------------------------------------
>
> Key: OPENMEETINGS-1425
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1425
> Project: Openmeetings
> Issue Type: Bug
> Components: Cluster
> Affects Versions: 3.1.1
> Environment: Debian 8, bd mysql connector 5.1.9
> XenServer VM 4 cores and 8Gb RAM
> Reporter: Arturo Durán Domínguez
> Assignee: Maxim Solodovnik
>
> Previously, we've installed OM 3.1.1 succesfully in three nodes and we've
> tested isolated so we're sure are correctly installed.
> We're following the instructions in
> http://openmeetings.apache.org/Clustering.html.
> We configure the DatabaseStore like SessionManager, restart red5 service and
> when the client start the session in the room we get this error in
> openmeetings.log:
> ERROR 06-24 13:35:46.313 o.a.o.c.s.SessionManager:105
> [RTMPConnectionExecutor-1] - [addClientListItem]
> java.lang.NullPointerException: null
> at
> org.apache.openmeetings.core.session.store.DatabaseStore.put(DatabaseStore.java:45)
> ~[openmeetings-core-3.1.1.jar:3.1.1]
> at
> org.apache.openmeetings.core.session.SessionManager$1.addClientListItem(SessionManager.java:101)
> ~[openmeetings-core-3.1.1.jar:3.1.1]
> at
> org.apache.openmeetings.core.session.SessionManager.addClientListItem(SessionManager.java:324)
> [openmeetings-core-3.1.1.jar:3.1.1]
> at
> org.apache.openmeetings.core.remote.red5.ScopeApplicationAdapter.roomConnect(ScopeApplicationAdapter.java:173)
> [openmeetings-core-3.1.1.jar:3.1.1]
> at
> org.red5.server.adapter.MultiThreadedApplicationAdapter.connect(MultiThreadedApplicationAdapter.java:315)
> [red5-server.jar:1.0.6-RELEASE]
> at
> org.red5.server.adapter.ApplicationAdapter.connect(ApplicationAdapter.java:42)
> [red5-server.jar:1.0.6-RELEASE]
> at org.red5.server.scope.Scope.connect(Scope.java:255)
> [red5-server-common-1.0.6-RELEASE.jar:na]
> at org.red5.server.BaseConnection.connect(BaseConnection.java:354)
> [red5-server-common-1.0.6-RELEASE.jar:na]
> at
> org.red5.server.net.rtmp.RTMPConnection.connect(RTMPConnection.java:405)
> [red5-server-common-1.0.6-RELEASE.jar:1.0.6-RELEASE]
> at
> org.red5.server.net.rtmp.RTMPMinaConnection.connect(RTMPMinaConnection.java:87)
> [red5-server-common-1.0.6-RELEASE.jar:1.0.6-RELEASE]
> at
> org.red5.server.net.rtmp.RTMPHandler.onCommand(RTMPHandler.java:347)
> [red5-server-common-1.0.6-RELEASE.jar:1.0.6-RELEASE]
> at
> org.red5.server.net.rtmp.BaseRTMPHandler.messageReceived(BaseRTMPHandler.java:105)
> [red5-server-common-1.0.6-RELEASE.jar:1.0.6-RELEASE]
> at
> org.red5.server.net.rtmp.ReceivedMessageTask.call(ReceivedMessageTask.java:63)
> [red5-server-common-1.0.6-RELEASE.jar:1.0.6-RELEASE]
> at
> org.red5.server.net.rtmp.ReceivedMessageTask.call(ReceivedMessageTask.java:14)
> [red5-server-common-1.0.6-RELEASE.jar:1.0.6-RELEASE]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> [na:1.7.0_101]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> [na:1.7.0_101]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> [na:1.7.0_101]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [na:1.7.0_101]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [na:1.7.0_101]
> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_101]
> WARN 06-24 13:35:46.314 o.a.o.c.r.r.ScopeApplicationAdapter:177
> [RTMPConnectionExecutor-1] - Failed to create Client on room connect
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
