[
https://issues.apache.org/jira/browse/OPENMEETINGS-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197848#comment-15197848
]
Bruno Rubio commented on OPENMEETINGS-1350:
-------------------------------------------
I made 2 diferent tests but any of them worked.
Test 1: single instalation (no clustering)
when I launch jnlp file, I get this error (screenshot1.png it is in spanish,
but I think you will understand)
I found a solution by changing the "application.base.url" parameter to
"http://192.168.96.222:5080/openmeetings/"; (avoid using localhost)
Test 2: clustering instalation (2 nodes)
I cant access the room (screenshot2.png)
You can find relevant lines on log files attached to this issue.
> rtmpT connection problem
> ------------------------
>
> Key: OPENMEETINGS-1350
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1350
> Project: Openmeetings
> Issue Type: Bug
> Components: Cluster, Screen-sharing
> Affects Versions: 3.0.7
> Environment: CentOS 7, OpenMeetings 3.0.7, clustering mode, rtmpT
> Reporter: Bruno Rubio
> Assignee: Maxim Solodovnik
> Attachments: openmeetings(node_1).log, openmeetings(node_2).log,
> red5(node_1).log, red5(node_2).log, screenshot1.png, screenshot2.png
>
>
> Hello,
> I have an clustered OpenMeetings instalation in an intranet forcing the rtmpT
> connection (port 5080) closing port 1935 at iptables
> when I try I cant share the screen, sometimes it is not possible because it
> attempts to connect the port 1935, and sometimes it connects but is too slow
> and connection closes unexpectedly
> Someone else with same problem?
> Regards.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
