I surprised by the fact port 8088 is required I believe this port shouldn't be in use since OM 3.0.2 or something, I suspect there is something wrong with redirecting According to your start/stop errors please try to find screensharing.log file on your client machine and check what is the error.
On Fri, Oct 2, 2015 at 5:13 PM, Dirk Hildebrand <[email protected]> wrote: > My Lame Mailclient is changing the titel every time i reply. i hate tobit > mailclient. Sorry for that. > > I have good news. I found out that Firewall was blocking Port 8088 to my > Server. i opend that port, now screensharing is loading from > https://my_external_ip/webmeeting , but > sadly i cant start the Screensharing, the startbutton doesnt switch to > "Stop" and there is no Screensharing started. > > When i connect to https://internal_IP/webmeeting screensharing is working > perfektly. Are there serveral other Ports for that? > > We found a Websocket ?Thing? wich will not load behind the mod_proxy: > wss://*internal_IP* > /webmeeting/wicket/websocket?pageId=4&wicket-ajax-baseurl=&wicket-app-name=OpenmeetingsApplication > i read about proxy_wstunnel_module, do i need that? First tests trying to > redirect webmeeting/wicket/ to wss://192.168.243.101/webmeeting/wicket/ > ends in an not working Openmeeting Website. > > Regards > > Dirk > > > > Original Message processed by David.fx12 > > *Re: Re-25: Openmeetings behind Apache mod_proxy* (02-Okt-2015 12:51) > *From:* Maxim Solodovnik <[email protected]> > *To:* > Openmeetings user-list <[email protected]> > > > OK, > > > Actually where should be 2 discussions on this. > > > 1) first one: what is wrong with HTTPS/RTMPS instructions, and these > instructions can be improved > 2) why forwarding does not work for you > > > Actually it seems to be impossible to forward HTTPS <-> HTTPS since in > this case all requests will be "double encoded" for the tomcat (used by OM > internally) > It is possible to use Apache as "securing server" for "unsecured OM" (this > is currently implemented on our demo server) > > > So first steps should be > 1) remove securing from OM > 2) set up HTTP/TRMPT proxying in secured apache > If it works (OM is fully available via HTTPS, all ports except for 22, 443 > are closed on server) > 3) try to use screen sharing > If JNLP file is successfully downloaded, check it contents, it should > contains rtmps protocol and correct port/server > In case all OK screensharing should work as expected > > > ps could you please do not change the title since currently this > conversation is impossible to follow using mail client or services like > openmeetings.markmail.org > > On Fri, Oct 2, 2015 at 11:46 AM, Dirk Hildebrand <[email protected]> > wrote: > >> I dont unserstand you at all. >> >> My 1st Setup was: >> >> Internet <- https -> (Ports 80,443,1935,8443,8080 in and out ) Apache >> with Mod_Proxy <- http -> Openmeetingsserver >> >> With this setting i was not able to have a Screensharing, because of some >> failure i dont understand. Someone here told me that my communication is >> partly encrypted so the Screensharing fails. >> >> My actual Setup: >> >> Internet <- https -> (Ports 80,443,1935,8443,8080 in and out ) Apache >> with Mod_Proxy <- https -> Openmeetingsserver >> >> Screensharing still not working. >> >> Is there a Tutorial wich explains wich relative URLs i need to forward >> and wich Ports (based on your tutorial for https/rtmps)? >> >> The tutorials i found all explain that they DONT work!? >> >> Regards >> >> Dirk >> >> >> Original Message processed by David.fx12 >> >> *Re: Re-23: Openmeetings behind Apache mod_proxy* (01-Okt-2015 18:09) >> *From:* Maxim Solodovnik <[email protected]> >> *To:* >> Openmeetings user-list <[email protected]> >> >> >> Redirecting ssl is tricky >> To avoid double encryption you need to use ssl inside om >> Or use in undecided and redirect it to site secured by Apache >> >> WBR, Maxim >> (from mobile, sorry for the typos) >> On Oct 1, 2015 13:40, "Dirk Hildebrand" <[email protected]> wrote: >> >>> Thank you for your suggestion, but i cant find how or where i could >>> enable that debug log. >>> >>> After testing around a bit i found out, that everything (almost) works >>> fine when i disable rtmps. I guess the problem is that the server name and >>> the name on the certificate are different, because openmeeting is running >>> behind a mod_proxy . The User connects to >>> https://my.external.domain/webmeeting but the openmeetingsservs >>> certificate is: "openmeeting.myinternaldomain.local". >>> >>> Is there a way to tell java or openmeeting to ignore that "error"? >>> >>> Regards >>> >>> Dirk >>> >>> Original Message processed by David.fx12 >>> >>> *Re: Re-21: Openmeetings behind Apache mod_proxy* (01-Okt-2015 10:26) >>> *From:* Maxim Solodovnik <[email protected]> >>> *To:* >>> Openmeetings user-list <[email protected]> >>> >>> >>> I would reccomend you to enable SSL debug log as described here: >>> http://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/ReadDebug.html >>> >>> You need to add *-Djavax.net.debug=all* >>> To java parameters >>> >>> WBR, Maxim >>> (from mobile, sorry for the typos) >>> On Oct 1, 2015 09:58, "Dirk Hildebrand" <[email protected]> wrote: >>> >>>> Yes, i edited public/config.xml (guess you mean that one) >>>> >>>> Thats what i changed: >>>> <rtmpsslport>8443</rtmpsslport> >>>> <useSSL>yes</useSSL> >>>> <protocol>https</protocol> >>>> <proxyType>best</proxyType> >>>> >>>> When i open a Conferenz Room i get a Handshake Error for a Second >>>> and then it says NetConnection.Connect.Failed: >>>> >>>> >>>> I cant find anything in the Logfiles, execpt those Entries i allready >>>> attached to an Email: >>>> >>>> 2015-09-30 15:20:10,200 [Launcher:/openmeetings] INFO >>>> org.quartz.core.QuartzScheduler - Scheduler >>>> org.springframework.scheduling.quartz.SchedulerFactoryBean#0_$_NON_CLUSTERED >>>> started. >>>> 2015-09-30 15:20:10,200 [Launcher:/openmeetings] INFO >>>> o.s.c.s.DefaultLifecycleProcessor - Starting beans in phase 2147483647 >>>> 2015-09-30 15:20:53,553 [NioProcessor-18] WARN >>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 1 >>>> 2015-09-30 15:20:53,553 [NioProcessor-19] WARN >>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 2 >>>> 2015-09-30 15:20:53,650 [NioProcessor-20] WARN >>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 3 >>>> >>>> I tried to connect with Google Chrome and Firefox with Flash Plugin >>>> >>>> >>>> Thanks >>>> >>>> >>>> Dirk >>>> >>>> >>>> >>>> Original Message processed by David.fx12 >>>> >>>> *Re: Re-19: Openmeetings behind Apache mod_proxy* (01-Okt-2015 9:29) >>>> *From:* Maxim Solodovnik <[email protected]> >>>> *To:* >>>> Openmeetings user-list <[email protected]> >>>> >>>> >>>> Have you modified configure.xml as described on the site? >>>> >>>> WBR, Maxim >>>> (from mobile, sorry for the typos) >>>> On Oct 1, 2015 09:11, "Dirk Hildebrand" <[email protected]> wrote: >>>> >>>>> Good morning and thank you for your patience with me. I found in the >>>>> loglife that the path to the Keystore was wrong, so i changed it and now i >>>>> have the Website up and Runnning \o/ >>>>> >>>>> But i cant enter a Meetingroom. There are Messages saying: >>>>> >>>>> try 1 >>>>> try 2 >>>>> try 3 >>>>> >>>>> and then: >>>>> >>>>> Error Missing [204] >>>>> Error Missing [556] >>>>> Error Missing [642] >>>>> >>>>> Some Threads in Openmeetings Mailinglist say that this problem ist >>>>> dedicated to some Port stuff, but i cant figure out what they did: >>>>> http://mail-archives.apache.org/mod_mbox/openmeetings-user/201302.mbox/%[email protected]%3E >>>>> >>>>> Any suggestions? >>>>> >>>>> Regards >>>>> >>>>> Dirk >>>>> >>>>> Original Message processed by David.fx12 >>>>> >>>>> *Re: Re-17: Openmeetings behind Apache mod_proxy* (30-Sep-2015 16:45) >>>>> *From:* Maxim Solodovnik <[email protected]> >>>>> *To:* >>>>> Openmeetings user-list <[email protected]> >>>>> >>>>> I can check it only next week >>>>> I don't have server to test while I'm at conference >>>>> >>>>> On Wed, Sep 30, 2015 at 8:41 PM, Dirk Hildebrand < >>>>> [email protected]> wrote: >>>>> >>>>>> Once again, i have to excuse: i call >>>>>> https://192.168.243.101:8443/webmeeting/ wich is obviously wrong. >>>>>> 8443 is rtmps port. Calling https://192.168.243.101:5443/webmeeting/ >>>>>> should >>>>>> work, but it doesnt. No Logentries in red5.log >>>>>> I get a Timeout in my Browser. Rebooting didnt help. >>>>>> >>>>>> Is it coorect that openmeeting is still available at Port 5080 after >>>>>> i configured https/rtmps? >>>>>> >>>>>> >>>>>> Original Message processed by David.fx12 >>>>>> >>>>>> *Re-16: Openmeetings behind Apache mod_proxy* (30-Sep-2015 16:30) >>>>>> *From:* Dirk Hildebrand <[email protected]> >>>>>> *To:* >>>>>> [email protected] >>>>>> >>>>>> Seems that the ports only listen on IPv6?!?! Why?! >>>>>> >>>>>> netstat -a | egrep 'Proto|LISTEN' >>>>>> Proto Recv-Q Send-Q Local Address Foreign Address >>>>>> State >>>>>> tcp 0 0 *:ssh *:* >>>>>> LISTEN >>>>>> tcp 0 0 *:ldap *:* >>>>>> LISTEN >>>>>> tcp 0 0 localhost:mysql *:* >>>>>> LISTEN >>>>>> tcp6 0 0 [::]:9998 [::]:* >>>>>> LISTEN >>>>>> tcp6 0 0 [::]:1935 [::]:* >>>>>> LISTEN >>>>>> tcp6 0 0 [::]:9999 [::]:* >>>>>> LISTEN >>>>>> tcp6 0 0 [::]:http-alt [::]:* >>>>>> LISTEN >>>>>> tcp6 0 0 [::]:tproxy [::]:* >>>>>> LISTEN >>>>>> tcp6 0 0 [::]:ssh [::]:* >>>>>> LISTEN >>>>>> tcp6 0 0 [::]:5080 [::]:* >>>>>> LISTEN >>>>>> tcp6 0 0 [::]:8443 [::]:* >>>>>> LISTEN >>>>>> tcp6 0 0 [::]:5443 [::]:* >>>>>> LISTEN >>>>>> tcp6 0 0 [::]:ldap [::]:* >>>>>> LISTEN >>>>>> >>>>>> >>>>>> Original Message processed by David.fx12 >>>>>> >>>>>> *Re: Re-14: Openmeetings behind Apache mod_proxy* (30-Sep-2015 16:22) >>>>>> *From:* Maxim Solodovnik <[email protected]> >>>>>> *To:* >>>>>> Openmeetings user-list <[email protected]> >>>>>> >>>>>> Any errors? exceptions? >>>>>> are correct ports listed by netstat? >>>>>> >>>>>> On Wed, Sep 30, 2015 at 7:59 PM, Dirk Hildebrand < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Yes, i found that i uncommented too much, now the Service starts but >>>>>>> now every time i try to open https site the Logfile says: >>>>>>> >>>>>>> 2015-09-30 15:20:10,200 [Launcher:/openmeetings] INFO >>>>>>> org.quartz.core.QuartzScheduler - Scheduler >>>>>>> org.springframework.scheduling.quartz.SchedulerFactoryBean#0_$_NON_CLUSTERED >>>>>>> started. >>>>>>> 2015-09-30 15:20:10,200 [Launcher:/openmeetings] INFO >>>>>>> o.s.c.s.DefaultLifecycleProcessor - Starting beans in phase >>>>>>> 2147483647 >>>>>>> 2015-09-30 15:20:53,553 [NioProcessor-18] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 1 >>>>>>> 2015-09-30 15:20:53,553 [NioProcessor-19] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 2 >>>>>>> 2015-09-30 15:20:53,650 [NioProcessor-20] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 3 >>>>>>> 2015-09-30 15:20:53,740 [NioProcessor-21] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 4 >>>>>>> 2015-09-30 15:20:53,836 [NioProcessor-22] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 5 >>>>>>> 2015-09-30 15:20:54,022 [NioProcessor-23] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 6 >>>>>>> 2015-09-30 15:20:54,108 [NioProcessor-24] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 7 >>>>>>> 2015-09-30 15:20:54,194 [NioProcessor-25] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 8 >>>>>>> 2015-09-30 15:20:54,277 [NioProcessor-26] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 9 >>>>>>> 2015-09-30 15:20:59,364 [NioProcessor-27] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 10 >>>>>>> 2015-09-30 15:20:59,450 [NioProcessor-28] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 11 >>>>>>> 2015-09-30 15:20:59,538 [NioProcessor-29] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 12 >>>>>>> 2015-09-30 15:20:59,624 [NioProcessor-30] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 13 >>>>>>> 2015-09-30 15:21:06,094 [NioProcessor-31] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 14 >>>>>>> 2015-09-30 15:21:06,097 [NioProcessor-32] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 15 >>>>>>> 2015-09-30 15:21:06,183 [NioProcessor-17] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 16 >>>>>>> 2015-09-30 15:21:06,267 [NioProcessor-18] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 17 >>>>>>> 2015-09-30 15:21:06,350 [NioProcessor-19] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 18 >>>>>>> 2015-09-30 15:21:09,457 [NioProcessor-20] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 19 >>>>>>> 2015-09-30 15:21:09,463 [NioProcessor-21] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 20 >>>>>>> 2015-09-30 15:21:09,542 [NioProcessor-22] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 21 >>>>>>> 2015-09-30 15:21:09,625 [NioProcessor-23] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 22 >>>>>>> 2015-09-30 15:21:09,712 [NioProcessor-24] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 23 >>>>>>> 2015-09-30 15:21:39,827 [NioProcessor-25] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 24 >>>>>>> 2015-09-30 15:21:39,910 [NioProcessor-26] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 25 >>>>>>> 2015-09-30 15:21:39,994 [NioProcessor-27] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 26 >>>>>>> 2015-09-30 15:21:40,080 [NioProcessor-28] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 27 >>>>>>> 2015-09-30 15:22:40,170 [NioProcessor-29] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 28 >>>>>>> 2015-09-30 15:22:40,252 [NioProcessor-30] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 29 >>>>>>> 2015-09-30 15:22:40,443 [NioProcessor-31] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 30 >>>>>>> 2015-09-30 15:22:40,553 [NioProcessor-32] WARN >>>>>>> o.r.s.net.rtmp.RTMPMinaIoHandler - Force close - session: 31 >>>>>>> >>>>>>> >>>>>>> Original Message processed by David.fx12 >>>>>>> >>>>>>> *Re: Re-12: Openmeetings behind Apache mod_proxy* (30-Sep-2015 >>>>>>> 15:09) >>>>>>> *From:* Maxim Solodovnik <[email protected]> >>>>>>> *To:* >>>>>>> Openmeetings user-list <[email protected]> >>>>>>> >>>>>>> Actually this errors are caused by broken XML >>>>>>> have you changed any XML file? >>>>>>> >>>>>>> On Wed, Sep 30, 2015 at 5:44 PM, Dirk Hildebrand < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Here is the red5.log, hope i have the part with the correct error: >>>>>>>> >>>>>>>> 2015-09-30 13:18:25,613 [main] INFO >>>>>>>> o.r.spring.Red5ApplicationContext - Refreshing ApplicationContext >>>>>>>> 'red5.core': startup date [Wed Sep 30 13:18:25 CEST 2015]; >>>>>>>> par ent: ApplicationContext 'red5.common' >>>>>>>> 2015-09-30 13:18:25,616 [main] INFO >>>>>>>> o.s.b.f.xml.XmlBeanDefinitionReader - Loading XML bean definitions from >>>>>>>> class path resource [red5-core.xml] >>>>>>>> 2015-09-30 13:18:25,656 [main] WARN >>>>>>>> o.s.c.s.FileSystemXmlApplicationContext - Exception encountered during >>>>>>>> context initialization - cancelling refresh attempt >>>>>>>> org.springframework.beans.factory.BeanCreationException: Error >>>>>>>> creating bean with name 'red5.core' defined in class path resource >>>>>>>> [red5.xml]: Invocation of init meth od failed; nested >>>>>>>> exception is >>>>>>>> org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: >>>>>>>> Line >>>>>>>> 238 in XML document from class path resource [red5-core.xm >>>>>>>> l] is invalid; nested exception is org.xml.sax.SAXParseException; >>>>>>>> lineNumber: 238; columnNumber: 9; cvc-complex-type.2.3: Element 'beans' >>>>>>>> cannot have character [chil dren], because the type's >>>>>>>> content type is element-only. >>>>>>>> at >>>>>>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1574) >>>>>>>> ~[spring-beans-4 .1.7.RELEASE.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:539) >>>>>>>> ~[spring-beans-4.1. 7.RELEASE.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476) >>>>>>>> ~[spring-beans-4.1.7. RELEASE.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:303) >>>>>>>> ~[spring-beans-4.1.7.RELEASE.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) >>>>>>>> ~[spring-beans-4.1.7.RELEASE.ja r:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:299) >>>>>>>> ~[spring-beans-4.1.7.RELEASE.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) >>>>>>>> ~[spring-beans-4.1.7.RELEASE.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:755) >>>>>>>> ~[spring-beans-4.1.7.RE <http://spring-beans-4.1.7.re/> >>>>>>>> LEASE.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:757) >>>>>>>> ~[spring-context-4.1.7 .RELEASE.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:480) >>>>>>>> ~[spring-context-4.1.7.RELEASE.jar:4.1.7.RELEA SE] >>>>>>>> at org.red5.server.Launcher.launch(Launcher.java:69) >>>>>>>> [red5-server.jar:na] >>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native >>>>>>>> Method) ~[na:1.8.0_60] >>>>>>>> at >>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) >>>>>>>> ~[na:1.8.0_60] >>>>>>>> at >>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>>>>>>> ~[na:1.8.0_60] >>>>>>>> at java.lang.reflect.Method.invoke(Method.java:497) >>>>>>>> ~[na:1.8.0_60] >>>>>>>> at org.red5.server.Bootstrap.bootStrap(Bootstrap.java:123) >>>>>>>> [red5-service.jar:na] >>>>>>>> at org.red5.server.Bootstrap.main(Bootstrap.java:48) >>>>>>>> [red5-service.jar:na] >>>>>>>> Caused by: >>>>>>>> org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: >>>>>>>> Line >>>>>>>> 238 in XML document from class path resource [red5-core.xml] is >>>>>>>> invalid; >>>>>>>> neste d exception is org.xml.sax.SAXParseException; >>>>>>>> lineNumber: 238; columnNumber: 9; cvc-complex-type.2.3: Element 'beans' >>>>>>>> cannot have character [children], because the t ype's >>>>>>>> content type is element-only. >>>>>>>> at >>>>>>>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399) >>>>>>>> ~[spring-beans-4.1.7.RELEASE.jar:4.1 .7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336) >>>>>>>> ~[spring-beans-4.1.7.RELEASE.jar:4.1.7 .RELEASE] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304) >>>>>>>> ~[spring-beans-4.1.7.RELEASE.jar:4.1.7 .RELEASE] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181) >>>>>>>> ~[spring-beans-4.1.7.REL EASE.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217) >>>>>>>> ~[spring-beans-4.1.7.REL EASE.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188) >>>>>>>> ~[spring-beans-4.1.7.REL EASE.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:252) >>>>>>>> ~[spring-beans-4.1.7.REL EASE.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:127) >>>>>>>> ~[spring-context-4.1.7.RELEA SE.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:93) >>>>>>>> ~[spring-context-4.1.7.RELEAS E.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:129) >>>>>>>> ~[spring-cont ext-4.1.7.RELEASE.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:537) >>>>>>>> ~[spring-context-4.1.7.RELEASE. jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:452) >>>>>>>> ~[spring-context-4.1.7.RELEASE.jar:4.1.7.RELEA SE] >>>>>>>> at >>>>>>>> org.red5.spring.Red5ApplicationContext.refresh(Red5ApplicationContext.java:36) >>>>>>>> ~[red5-server.jar:na] >>>>>>>> at >>>>>>>> org.springframework.context.support.AbstractRefreshableConfigApplicationContext.afterPropertiesSet(AbstractRefreshableConfigApplicationContext.java:151) >>>>>>>> ~ [spring-context-4.1.7.RELEASE.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.red5.spring.Red5ApplicationContext.afterPropertiesSet(Red5ApplicationContext.java:30) >>>>>>>> ~[red5-server.jar:na] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1633) >>>>>>>> ~[spring-bean s-4.1.7.RELEASE.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1570) >>>>>>>> ~[spring-beans-4 .1.7.RELEASE.jar:4.1.7.RELEASE] >>>>>>>> ... 16 common frames omitted >>>>>>>> Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.3: >>>>>>>> Element 'beans' cannot have character [children], because the type's >>>>>>>> content type is element-only. >>>>>>>> at >>>>>>>> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown >>>>>>>> Source) ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown >>>>>>>> Source) ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at >>>>>>>> org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) >>>>>>>> ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at >>>>>>>> org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) >>>>>>>> ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at >>>>>>>> org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) >>>>>>>> ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at >>>>>>>> org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown >>>>>>>> Source) ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at >>>>>>>> org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown >>>>>>>> Source) ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at >>>>>>>> org.apache.xerces.impl.xs.XMLSchemaValidator.elementLocallyValidComplexType(Unknown >>>>>>>> Source) ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at >>>>>>>> org.apache.xerces.impl.xs.XMLSchemaValidator.elementLocallyValidType(Unknown >>>>>>>> Source) ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at >>>>>>>> org.apache.xerces.impl.xs.XMLSchemaValidator.processElementContent(Unknown >>>>>>>> Source) ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at >>>>>>>> org.apache.xerces.impl.xs.XMLSchemaValidator.handleEndElement(Unknown >>>>>>>> Source) ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at >>>>>>>> org.apache.xerces.impl.xs.XMLSchemaValidator.endElement(Unknown Source) >>>>>>>> ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at >>>>>>>> org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown >>>>>>>> Source) ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at >>>>>>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown >>>>>>>> Source) ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at >>>>>>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown >>>>>>>> Source) ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at >>>>>>>> org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) >>>>>>>> ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at >>>>>>>> org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) >>>>>>>> ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at org.apache.xerces.parsers.XMLParser.parse(Unknown >>>>>>>> Source) ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at org.apache.xerces.parsers.DOMParser.parse(Unknown >>>>>>>> Source) ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown >>>>>>>> Source) ~[xercesImpl-2.9.1.jar:na] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:76) >>>>>>>> ~[spring-beans-4.1.7.RELEASE.jar:4.1.7.RELEASE] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadDocument(XmlBeanDefinitionReader.java:429) >>>>>>>> ~[spring-beans-4.1.7.RELEASE.jar:4.1.7.RELE ASE] >>>>>>>> at >>>>>>>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:391) >>>>>>>> ~[spring-beans-4.1.7.RELEASE.jar:4.1 .7.RELEASE] >>>>>>>> ... 32 common frames omitted >>>>>>>> 2015-09-30 13:18:25,657 [main] INFO >>>>>>>> o.r.spring.Red5ApplicationContext - Closing ApplicationContext >>>>>>>> 'red5.common': startup date [Wed Sep 30 13:18:25 CEST 2015]; >>>>>>>> pare nt: >>>>>>>> org.springframework.context.support.FileSystemXmlApplicationContext@617faa95 >>>>>>>> 2015-09-30 13:18:25,659 [main] INFO >>>>>>>> o.s.j.e.a.AnnotationMBeanExporter - Unregistering JMX-exposed beans on >>>>>>>> shutdown >>>>>>>> 2015-09-30 13:18:25,659 [main] INFO >>>>>>>> o.s.j.e.a.AnnotationMBeanExporter - Unregistering JMX-exposed beans >>>>>>>> 2015-09-30 13:18:25,659 [main] INFO >>>>>>>> o.s.j.s.ConnectorServerFactoryBean - Stopping JMX connector server: >>>>>>>> javax.management.remote.rmi.RMIConnectorServer@fba92d3 >>>>>>>> 2015-09-30 13:18:25,661 [main] INFO >>>>>>>> o.s.j.s.ConnectorServerFactoryBean - Unregistering JMX-exposed beans >>>>>>>> 2015-09-30 13:18:25,661 [main] INFO >>>>>>>> o.s.r.rmi.RmiRegistryFactoryBean - Unexporting RMI registry >>>>>>>> 2015-09-30 13:18:25,661 [main] INFO >>>>>>>> org.quartz.core.QuartzScheduler - Scheduler >>>>>>>> Red5_Scheduler_$_NON_CLUSTERED >>>>>>>> shutting down. >>>>>>>> 2015-09-30 13:18:25,661 [main] INFO >>>>>>>> org.quartz.core.QuartzScheduler - Scheduler >>>>>>>> Red5_Scheduler_$_NON_CLUSTERED >>>>>>>> paused. >>>>>>>> 2015-09-30 13:18:25,661 [main] INFO >>>>>>>> org.quartz.core.QuartzScheduler - Scheduler >>>>>>>> Red5_Scheduler_$_NON_CLUSTERED >>>>>>>> shutdown complete. >>>>>>>> ^C >>>>>>>> albert@WIS-RZ-OpenMeeting:~$ tail -f /opt/red5307/log/red5.log >>>>>>>> ... 32 common frames omitted >>>>>>>> 2015-09-30 13:18:25,657 [main] INFO >>>>>>>> o.r.spring.Red5ApplicationContext - Closing ApplicationContext >>>>>>>> 'red5.common': startup date [Wed Sep 30 13:18:25 CEST 2015]; parent: >>>>>>>> org.springframework.context.support.FileSystemXmlApplicationContext@617faa95 >>>>>>>> 2015-09-30 13:18:25,659 [main] INFO >>>>>>>> o.s.j.e.a.AnnotationMBeanExporter - Unregistering JMX-exposed beans on >>>>>>>> shutdown >>>>>>>> 2015-09-30 13:18:25,659 [main] INFO >>>>>>>> o.s.j.e.a.AnnotationMBeanExporter - Unregistering JMX-exposed beans >>>>>>>> 2015-09-30 13:18:25,659 [main] INFO >>>>>>>> o.s.j.s.ConnectorServerFactoryBean - Stopping JMX connector server: >>>>>>>> javax.management.remote.rmi.RMIConnectorServer@fba92d3 >>>>>>>> 2015-09-30 13:18:25,661 [main] INFO >>>>>>>> o.s.j.s.ConnectorServerFactoryBean - Unregistering JMX-exposed beans >>>>>>>> 2015-09-30 13:18:25,661 [main] INFO >>>>>>>> o.s.r.rmi.RmiRegistryFactoryBean - Unexporting RMI registry >>>>>>>> 2015-09-30 13:18:25,661 [main] INFO >>>>>>>> org.quartz.core.QuartzScheduler - Scheduler >>>>>>>> Red5_Scheduler_$_NON_CLUSTERED >>>>>>>> shutting down. >>>>>>>> 2015-09-30 13:18:25,661 [main] INFO >>>>>>>> org.quartz.core.QuartzScheduler - Scheduler >>>>>>>> Red5_Scheduler_$_NON_CLUSTERED >>>>>>>> paused. >>>>>>>> 2015-09-30 13:18:25,661 [main] INFO >>>>>>>> org.quartz.core.QuartzScheduler - Scheduler >>>>>>>> Red5_Scheduler_$_NON_CLUSTERED >>>>>>>> shutdown complete. >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> WBR >>>>>>> Maxim aka solomax >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> WBR >>>>>> Maxim aka solomax >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> WBR >>>>> Maxim aka solomax >>>>> >>>>> > > > > -- > WBR > Maxim aka solomax > > -- WBR Maxim aka solomax
