Dear OpenMeetings Developers,
We have performed some tests with OM 3.1.0. We would appreciate your
insights when two instances (two Red5 servers) are running on the SAME
server. One of the instances does not shut down.
Environment:
OM 3.1.0
Server 1: CentOS 6.5, MySQL
Server 2: CentOS 7, MariaDB
Java 7 patch 76
Red5.properties has:
JMX…
jmx.rmi.port=9999
jmx.rmi.sport=9998
Use cases:
1)When there is only one instance running on a server, OM starts, runs
smoothly and gracefully shuts down in the above environment. All OM
features are also working fine.
2)When we have two instances with different ports (in red5.properties
and config.xml) and different databases, OM starts and runs smoothly,
with all features working fine in both instances.
JMX…
#jmx.rmi.port=9999
jmx.rmi.port=9995
#jmx.rmi.sport=9998
jmx.rmi.sport=9994
However, it does not gracefully shut down (not using kill) saying
Attempting to connect to RMI [::]:9999
This dual configuration for JMX was working fine in OM 3.0.7. Is there
any change in OM 3.1.0 that affects JMX configuration?
Is there any other way of gracefully shutting down with JMX ports other
than 9999.
Attached are the logs.
Thank you.
Sincerely,
Susheel Jalali
Coscend Communications Solutions
www.Coscend.com
----------------------------------------------------------------
CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail
Messages from Coscend Communications Solutions' posted at:
http://www.Coscend.com/Terms_and_Conditions.html
