openmeetings-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Hill (JIRA)" <>
Subject [jira] [Commented] (OPENMEETINGS-500) Unable to ssl connect to openmeetings
Date Thu, 10 Jan 2013 03:08:13 GMT


Brian Hill commented on OPENMEETINGS-500:

Let's take a second look at the original message, more specifically at item (b). I logged
this message to find out if anyone had overcome the issue related to 'long handshake'. 
It would be great if we could address this point specifically.  An example would be (change

> Unable to ssl connect to openmeetings
> -------------------------------------
>                 Key: OPENMEETINGS-500
>                 URL:
>             Project: Openmeetings
>          Issue Type: Bug
>            Reporter: Brian Hill
>            Assignee: Maxim Solodovnik
>             Fix For: 2.0 Apache Incubator Release
> I've been trying to secure my installation of Openmeetings2.
> After a couple of attempts based on instructions on the Openmeetings site (
official site, I noticed the following errors:
>     a) - Exception caught SSL handshake
>     b) [Red5_Scheduler_Worker-2] - Closing RTMPMinaConnection
from 192.168.X.X #### to null with id # due to long handshake
>    Subsequently, I noticed that the instructions references version 1.9 of Openmeetings
rather than Version 2.0 (which is what I installed). Specifically, this bug which is listed
in openmeetings' changelog (for version 2 that I installed) :
>       [OPENMEETINGS-234] - Video and Screen sharing not working with HTTPS and RTMPS
- Java Application starts but doesnt connect - java trace logs shows "[WARN] [NioProcessor-2] - Exception caught Keystore or password are null"
>    Some question is:
>     * Is there a way to secure openmeetings 2.0 or should I unsinstall this version and
install 1.9 instead to achieve this  goal?
>     * Is the right RTMPS URL to connect as follows:
>       If not, please advise.
>       Thanks.
>     Thanks.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message