Looks like there is some "program types" that it has trouble capturing.
Would say a flaw of WebRTC. I have the same problems with certain java
based programs. When doing the screen sharing, you will get a black
screen but if you look every now and then is will show for a brief
instance then back to black "Flickers" more so. This was when capturing
(window or Application). If you capture the screen then it can display
it without issues.
On 4/13/19 3:34 AM, R. Scholz wrote:
Hello,
when I share a program in OM5 some programs only show at the viewer a
black window.
(I told it in an email a few days ago and Maxim made some ideas to
identify the problem.)
I tried out a lot of programs and, beneath our own programmed software
I saw that the
product "SoftPerfect Network Scanner" make this black screen too.
In my own "system-tools-libary" I use the (old) free-version "4.4.5".
(Its totally enough, this free version
do exactly what I want.)
A look into the binary-code shows that it is a delphi-program.
Has anyone an idea I can try?
Best regards,
René
Am 13.04.2019 um 09:19 schrieb R. Scholz:
Hello Aaron,
I think it is the same problem I had a few weeks ago. (And I hope I
solved it.)
To your questions with the log: You find relevant logs at "/opt/logs"
e.g. "/opt/%OMDIR%/logs". The actual log is named "catalina.out".
When it is the error I think you have to edit the "mysql-persistence.xml"
You find it in the openmeeting-Directory ->
webapps/openmeetings/WEB-INF/classes/META-INF.
Here the part of my email.
My Solution:
The Parameter "serverTimezone" must in the first line of the
Driver-command (where is separated by "&").
It doesn't matter where you put it.
When I put it into the comma-separated-part it's not functionally.
Here's my line in the mysql-persistence.xml:
value="DriverClassName=com.mysql.cj.jdbc.Driver
,
Url=jdbc:mysql://localhost:3306/openmeetings?autoReconnect=true&useUnicode=true&*serverTimezone=Europe/Berlin&*createDatabaseIfNotExist=true&characterEncoding=utf-8
&connectionCollation=utf8_general_ci&cachePrepStmts=true&cacheCallableStatements=true&cacheServerConfiguration=true&useLocalSessionState=true&elideSetAutoCommits=true&alwaysSendSetIsolation=false&enableQueryTimeouts=false&prepStmtCacheSize=3000&prepStmtCacheSqlLimit=1000&useSSL=false&nullNamePatternMatchesAll=true
, maxTotal=100
, maxIdle=100
, minIdle=0
, maxWaitMillis=10000
, TestOnBorrow=true
, poolPreparedStatements=true
, Username=
, Password=" />
I hope it helps.
Best regards,
René
Am 13.04.2019 um 01:58 schrieb Aaron Hepp:
Where are the connection logs to the database located at? Just
stood up a new OM5 instance on a Ubuntu 16.04 install. went through
all the steps, but does not look like it is making a connection to
the MySQL database.
Could not create connection to database server. Attempted reconnect
3 times. Giving up.
Database is up and listening on port 3306, made sure database name,
user and password were correct, but keep getting the errors. Was
going to look at the logs but forgot where they are at to determine
what the issue was.
