[ 
https://issues.apache.org/jira/browse/OPENMEETINGS-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277881#comment-13277881
 ] 

Stephen Cottham commented on OPENMEETINGS-277:
----------------------------------------------

Thanks Maxim, removing that line resolved the issue, I'll hold off testing 
until you have finished the changes no probs.

Best Regards

                
> Latest build fails to start using RTMPS
> ---------------------------------------
>
>                 Key: OPENMEETINGS-277
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-277
>             Project: Openmeetings
>          Issue Type: Bug
>          Components: Audio/Video
>    Affects Versions: 2.0 Apache Incubator Release
>         Environment: Debian64 
>            Reporter: Stephen Cottham
>            Assignee: Maxim Solodovnik
>             Fix For: 2.0 Apache Incubator Release
>
>
> Starting Red5 throws the following when using RTMPS:
> Exception org.springframework.beans.factory.BeanCreationException: Error 
> creating bean with name 'red5.core' defined in class path resource 
> [red5.xml]: Instantiation of bean failed; nested exception is 
> org.springframework.beans.BeanInstantiationException: Could not instantiate 
> bean class 
> [org.springframework.context.support.FileSystemXmlApplicationContext]: 
> Constructor threw exception; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 'rtmpsTransport' defined in class path resource [red5-core.xml]: 
> Error setting property values; nested exception is 
> org.springframework.beans.NotWritablePropertyException: Invalid property 
> 'jmxPollInterval' of bean class [org.red5.server.net.rtmp.RTMPMinaTransport]: 
> Bean property 'jmxPollInterval' is not writable or has an invalid setter 
> method. Does the parameter type of the setter match the return type of the 
> getter?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to