[
https://issues.apache.org/jira/browse/OPENMEETINGS-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15448250#comment-15448250
]
Uwe Tesche commented on OPENMEETINGS-1267:
------------------------------------------
Now using JDK 1.8.0_101/Hotspot 25.101 - server starts up with no logged
problems.
The screenshare-app is loaded and started with no remarkable logging too.
Using "Start" for desktopsharing and recording leads both to the follwing lines
in the log - no visual activities at the client app, the buttons remains in
state "Start".
Using the buttons again has NO further activity in the serverlog. The messages
only appears once per room-start.
<...for desktopsharing...>
2016-08-30 08:35:19,139 [NioProcessor-7] WARN o.r.s.net.rtmp.InboundHandshake
- Client digest verification failed
2016-08-30 08:35:19,140 [NioProcessor-7] WARN
o.r.server.net.rtmpe.RTMPEIoFilter - Client was rejected due to invalid
handshake
2016-08-30 08:35:19,140 [NioProcessor-7] INFO
o.r.s.net.rtmp.RTMPMinaConnection - Connection is closed: NENDMCPH2LRBG
2016-08-30 08:35:19,140 [NioProcessor-7] WARN o.r.s.net.rtmp.RTMPMinaIoHandler
- Connection was not found for NENDMCPH2LRBG
<...for recording...>
2016-08-30 08:44:10,220 [NioProcessor-10] WARN o.r.s.net.rtmp.InboundHandshake
- Client digest verification failed
2016-08-30 08:44:10,220 [NioProcessor-10] WARN
o.r.server.net.rtmpe.RTMPEIoFilter - Client was rejected due to invalid
handshake
2016-08-30 08:44:10,220 [NioProcessor-10] INFO
o.r.s.net.rtmp.RTMPMinaConnection - Connection is closed: IRWCWHVQVHH8Q
2016-08-30 08:44:10,221 [NioProcessor-10] WARN
o.r.s.net.rtmp.RTMPMinaIoHandler - Connection was not found for IRWCWHVQVHH8Q
> inproper handover of rtmphostlocal to screenshare-client
> --------------------------------------------------------
>
> Key: OPENMEETINGS-1267
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1267
> Project: Openmeetings
> Issue Type: Bug
> Components: Screen-sharing
> Affects Versions: 3.0.3, 3.0.6
> Reporter: Uwe Tesche
> Assignee: Maxim Solodovnik
> Priority: Minor
> Labels: easyfix
> Fix For: 3.1.3
>
>
> We are using https and rtmps - and due to firewall-issues, we are using port
> 443 for BOTH connections. To separate the connections otherwise, we are
> using different values for <rtmphostlocal> and <httphostlocal>.
> It works fine except the screensharing-client: one of the arguments when
> starting the client is the host-address to be used by the client.
> This address should be <rtmphostlocal>, but in fact <httphostlocal> is being
> used!
> working patch in src/WebContent/src/base/mainMethods.lzx:
> a) adding a new method:
> <method name="getRtmpHost">
> <![CDATA[
> return canvas.rtmphostlocal;
> ]]>
> </method>
> b) change in method getScreenSharingUrl:
> from ... +'rtmphostlocal=' + canvas.getHttpHost() ...
> to +'rtmphostlocal=' + canvas.getRtmpHost()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
