The problem is in file limit on our server, try smaller mp4 file :)))
We will increase the limit to be at least 20M

On Fri, Jan 20, 2017 at 4:02 PM, Maxim Solodovnik <solomax...@gmail.com>
wrote:

> MP4 files are supported and works as expected locally
> I'll double-check what can be wrong
> Will write results to the list
>
> On Fri, Jan 20, 2017 at 2:53 PM, Yakovlev N. <yakovlev...@krvostok.ru>
> wrote:
>
>> Hi Maxim,
>>
>> FLV,AVI-files are OK.
>>
>> MP4 ones are not uploaded. Is MP4-format supported ?
>>
>>
>>
>> Nik
>>
>>
>>
>> *From:* Maxim Solodovnik [mailto:solomax...@gmail.com]
>> *Sent:* Thursday, January 19, 2017 6:20 PM
>> *To:* dev; Openmeetings user-list
>> *Subject:* Re: [DISCUSSION] 3.2.0 release
>>
>>
>>
>> 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 <solomax...@gmail.com>
>> wrote:
>>
>> Stupid idea ....
>>
>> Maybe JS is disabled in your Chrome?
>>
>>
>>
>> On Thu, Jan 19, 2017 at 8:18 PM, Peter Dähn <da...@vcrp.de> 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:8443/next/ using your Chrome?
>>
>> On Thu, Jan 19, 2017 at 6:06 PM, Peter Dähn <da...@vcrp.de> wrote:
>>
>> 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, login=XXX, pictureuri=null,
>> deleted=false, languageId=2, address=Address [id=X, country=DE,
>> street=null, town=null, zip=null, deleted=false, email=XXX@XXX,
>> phone=null], externalId=null, externalType=null, type=user]]]
>> DEBUG 01-19 12:04:40.079 AuthLevelUtil.java 10909276 39
>> org.apache.openmeetings.db.util.AuthLevelUtil
>> [http-nio-0.0.0.0-5080-exec-5] - Level Admin :: [DENIED]
>> DEBUG 01-19 12:04:40.089 AuthLevelUtil.java 10909286 39
>> org.apache.openmeetings.db.util.AuthLevelUtil
>> [http-nio-0.0.0.0-5080-exec-4] - Level Admin :: [DENIED]
>> DEBUG 01-19 12:04:40.090 AuthLevelUtil.java 10909287 39
>> org.apache.openmeetings.db.util.AuthLevelUtil
>> [http-nio-0.0.0.0-5080-exec-4] - Level GroupAdmin :: [DENIED]
>> DEBUG 01-19 12:04:40.124 AuthLevelUtil.java 10909321 39
>> org.apache.openmeetings.db.util.AuthLevelUtil
>> [http-nio-0.0.0.0-5080-exec-4] - Level Admin :: [DENIED]
>> Jan 19, 2017 12:04:40 PM org.apache.coyote.AbstractProt
>> ocol$ConnectionHandler
>> process
>> SCHWERWIEGEND: Error reading request, ignored
>> java.lang.NullPointerException
>>      at org.apache.wicket.protocol.ws.api.AbstractWebSocketProcessor
>> .<init>(AbstractWebSocketProcessor.java:104)
>>      at org.apache.wicket.protocol.ws.javax.JavaxWebSocketProcessor.
>> <init>(JavaxWebSocketProcessor.java:46)
>>      at org.apache.wicket.protocol.ws.javax.WicketEndpoint.onOpen(Wi
>> cketEndpoint.java:64)
>>      at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.init
>> (WsHttpUpgradeHandler.java:133)
>>      at org.apache.coyote.AbstractProtocol$ConnectionHandler.
>> process(AbstractProtocol.java:831)
>>      at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
>> (NioEndpoint.java:1437)
>>      at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketPro
>> cessorBase.java:49)
>>      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>>      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:617)
>>      at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.
>> run(TaskThread.java:61)
>>      at java.lang.Thread.run(Thread.java:745)
>>
>> [ERROR] [http-nio-0.0.0.0-5080-exec-9] org.apache.coyote.http11.Http1
>> 1NioProtocol
>> - Error reading request, ignored
>> java.lang.NullPointerException: null
>>      at org.apache.wicket.protocol.ws.api.AbstractWebSocketProcessor
>> .<init>(AbstractWebSocketProcessor.java:104)
>>      at org.apache.wicket.protocol.ws.javax.JavaxWebSocketProcessor.
>> <init>(JavaxWebSocketProcessor.java:46)
>>      at org.apache.wicket.protocol.ws.javax.WicketEndpoint.onOpen(Wi
>> cketEndpoint.java:64)
>>      at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.init
>> (WsHttpUpgradeHandler.java:133)
>>      at org.apache.coyote.AbstractProtocol$ConnectionHandler.
>> process(AbstractProtocol.java:831)
>>      at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
>> (NioEndpoint.java:1437)
>>      at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketPro
>> cessorBase.java:49)
>>      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>>      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:617)
>>      at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.
>>
>> run(TaskThread.java:61)
>>      at java.lang.Thread.run(Thread.java:745)
>>
>>
>>
>> Am 19.01.2017 um 11:33 schrieb 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" <da...@vcrp.de> wrote:
>>
>> 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.2743.82 (64-bit)
>>
>> Is it my system or a general problem?
>>
>> 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
>> https://issues.apache.org/jira/browse/OPENMEETINGS-1527 and would like
>> to
>> pack RC1
>>
>> Please let me know if there are any critical issues.
>> (you can use our demo for tests: https://om.alteametasoft.com:8443/next
>> )
>>
>> And IMHO we need to switch main stable development branch to 3.2.x
>> 3.1.5 can be released in a week or so with some critical REST/SOAP fixes
>>
>> WDYT?
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> WBR
>> Maxim aka solomax
>>
>>
>>
>>
>>
>> --
>>
>> WBR
>> Maxim aka solomax
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
WBR
Maxim aka solomax

Reply via email to