Re: [DISCUSSION] 3.2.0 release

2017-01-30 Thread Maxim Solodovnik
dentiality Notice Regarding E-mail Messages > from Coscend Communications Solutions' posted at: > http://www.Coscend.com/Terms_and_Conditions.html > > > > > -Original Message- > From: Maxim Solodovnik [mailto:solomax...@gmail.com] > Sent: Friday, January 27, 20

RE: [DISCUSSION] 3.2.0 release

2017-01-29 Thread Coscend@OM
list ; dev Subject: Re: [DISCUSSION] 3.2.0 release Hello All, I'm almost ready to start 3.2.0 release process, Any "last minute" issues? :))) Another question: Is it OK to drop 3.1.x support? i.e. 3.1.5 will be the last 3.1.x release On Tue, Jan 24, 2017 at 1:08 PM, Maxim Solodovnik

Re: [DISCUSSION] 3.2.0 release

2017-01-28 Thread Maxim Solodovnik
I'm going to start 3.2.0 release :)) On Sat, Jan 28, 2017 at 11:44 AM, Maxim Solodovnik wrote: > Hello All, > > I'm almost ready to start 3.2.0 release process, Any "last minute" issues? > :))) > > Another question: Is it OK to drop 3.1.x support? i.e. 3.1.5 will be the > last 3.1.x release > > O

Re: [DISCUSSION] 3.2.0 release

2017-01-27 Thread Maxim Solodovnik
Hello All, I'm almost ready to start 3.2.0 release process, Any "last minute" issues? :))) Another question: Is it OK to drop 3.1.x support? i.e. 3.1.5 will be the last 3.1.x release On Tue, Jan 24, 2017 at 1:08 PM, Maxim Solodovnik wrote: > Thanks for the report Sebastian! > I was able to rep

Re: [DISCUSSION] 3.2.0 release

2017-01-20 Thread Maxim Solodovnik
Hello Peter, Can you please create JIRA issue? (better with steps in English how to configure browser) I wasn't aware of this behavior and need some time to investigate it. Weird thing is: OM 3.1.x and 3.2.x both using same code for the admin/calendar/dashboard, I wonder why you see such behavior

Re: [DISCUSSION] 3.2.0 release

2017-01-20 Thread Peter Dähn
and my installation doesn't show the chatpanel because it is not activated fot dashboard... so both acted in the same way... but anyway I'm not sure if om should act like this... Greetings Peter Am 20.01.2017 um 09:44 schrieb Peter Dähn: ok.. I got it... I used in cookies settings to block

Re: [DISCUSSION] 3.2.0 release

2017-01-20 Thread Peter Dähn
ok.. I got it... I used in cookies settings to block cookies per default, and handle cookies via exceptions, this seems to work for other sites but not for OM... Change settings to the first option and OM dashboard is shown... Am 20.01.2017 um 09:37 schrieb Peter Dähn: well... no error in

Re: [DISCUSSION] 3.2.0 release

2017-01-20 Thread Peter Dähn
well... no error in console but now I have a difference between testserver and my installation... testserver gives me at least the chat-panel, my installation still the whitescreen but pages are not empty, I got a lot of divs with display:none property... Am 19.01.2017 um 16:39 schrieb Max

Re: [DISCUSSION] 3.2.0 release

2017-01-19 Thread Maxim Solodovnik
Anything in dev console? (displayed on F12 in Chrome) On Thu, Jan 19, 2017 at 10:37 PM, Peter Dähn wrote: > no ist isn't... > > > > Am 19.01.2017 um 15:55 schrieb Maxim Solodovnik: > > Stupid idea > Maybe JS is disabled in your Chrome? > > On Thu, Jan 19, 2017 at 8:18 PM, Peter Dähn > wr

Re: [DISCUSSION] 3.2.0 release

2017-01-19 Thread Peter Dähn
no ist isn't... Am 19.01.2017 um 15:55 schrieb Maxim Solodovnik: Stupid idea Maybe JS is disabled in your Chrome? On Thu, Jan 19, 2017 at 8:18 PM, Peter Dähn wrote: same result... white screen... Am 19.01.2017 um 13:40 schrieb Maxim Solodovnik: Dashboard should work even if websoc

Re: [DISCUSSION] 3.2.0 release

2017-01-19 Thread Maxim Solodovnik
Video upload and file deletion in room are fixed Please let me know if any other issues blocks the release :) On Thu, Jan 19, 2017 at 9:55 PM, Maxim Solodovnik wrote: > Stupid idea > Maybe JS is disabled in your Chrome? > > On Thu, Jan 19, 2017 at 8:18 PM, Peter Dähn wrote: > >> same resul

Re: [DISCUSSION] 3.2.0 release

2017-01-19 Thread Maxim Solodovnik
Stupid idea Maybe JS is disabled in your Chrome? On Thu, Jan 19, 2017 at 8:18 PM, Peter Dähn wrote: > same result... white screen... > > > Am 19.01.2017 um 13:40 schrieb Maxim Solodovnik: > >> Dashboard should work even if websockets are broken >> Can you access https://om.alteametasoft.com

Re: [DISCUSSION] 3.2.0 release

2017-01-19 Thread Peter Dähn
same result... white screen... Am 19.01.2017 um 13:40 schrieb Maxim Solodovnik: Dashboard should work even if websockets are broken Can you access https://om.alteametasoft.com:8443/next/ using your Chrome? On Thu, Jan 19, 2017 at 6:06 PM, Peter Dähn wrote: Hi Maxim, console log: DEBUG 01-1

Re: [DISCUSSION] 3.2.0 release

2017-01-19 Thread Maxim Solodovnik
Dashboard should work even if websockets are broken Can you access https://om.alteametasoft.com:8443/next/ using your Chrome? On Thu, Jan 19, 2017 at 6:06 PM, Peter Dähn wrote: > Hi Maxim, > > console log: > > DEBUG 01-19 12:04:40.062 UserDao.java 10909259 643 > org.apache.openmeetings.db.dao.us

Re: [DISCUSSION] 3.2.0 release

2017-01-19 Thread Peter Dähn
Hi Maxim, console log: DEBUG 01-19 12:04:40.062 UserDao.java 10909259 643 org.apache.openmeetings.db.dao.user.UserDao [http-nio-0.0.0.0-5080-exec-5] - loginUser [GroupUser [id=X, moderator=false, group=Group [id=1, name=XXX, deleted=false], user=User [id=X, firstname=Peter, lastname=XXX, log

Re: [DISCUSSION] 3.2.0 release

2017-01-19 Thread Maxim Solodovnik
Hello Peter, Works for me, Ubuntu x64 Any errors in the logs? WBR, Maxim (from mobile, sorry for the typos) On Jan 19, 2017 17:31, "Peter Dähn" wrote: > 1st impressions: > > - build and restore backup works so far > - login, dash, admin panel, rooms seem to work (FF) > > Try out using google c

Re: [DISCUSSION] 3.2.0 release

2017-01-19 Thread Peter Dähn
1st impressions: - build and restore backup works so far - login, dash, admin panel, rooms seem to work (FF) Try out using google chrome - after login I just see a white page instead the dash - network test works so flash works in chrome Environment: Linux Mint 18 Google Chrome Version 52.0.2

Re: [DISCUSSION] 3.2.0 release

2017-01-19 Thread Alvaro
Hello, OM 3.2 #395 * In Conference room upload and play any video file like flvRecording_1.avi, and office files correctly. * In a Calendar meeting, upload any video file but don't play it any one. Upload office files correctly. Alvaro .. On jue, 2017-01-19 at 12:42 +0700, Ma

Re: [DISCUSSION] 3.2.0 release

2017-01-19 Thread Peter Dähn
ok... thanks for your answer and you are right... VERY jvm/server specific... ;-) Am 19.01.2017 um 09:08 schrieb Maxim Solodovnik: Hello Peter, *-highperf.* was removed from red5, you can get it from 3.1.3 version (or from 3.0.7) Java performance tuning is very JVM/server dependant, so I belie

Re: [DISCUSSION] 3.2.0 release

2017-01-19 Thread Maxim Solodovnik
Hello Peter, *-highperf.* was removed from red5, you can get it from 3.1.3 version (or from 3.0.7) Java performance tuning is very JVM/server dependant, so I believe, removing it was correct decision On Thu, Jan 19, 2017 at 2:57 PM, Peter Dähn wrote: > Hi together, > > going to build and test..

Re: [DISCUSSION] 3.2.0 release

2017-01-18 Thread Peter Dähn
Hi together, going to build and test... 1st: I miss red5-highperf.sh after build (seems to be the same in 3.1.4) report later/tomorrow about my impression Greetings Peter Am 19.01.2017 um 06:42 schrieb Maxim Solodovnik: Hello All, I believe 3.2.0 should be released, I'm going to implement h