such errors usually happens when you use incompatible
applicationContext.xml file (i.e. copy it from previous version)

in this upcoming version you shouldn't edit applicationContext.xml
all *basic* tuning should be done in openmeetings.properties




On Tue, 27 Oct 2020 at 14:45, dww <[email protected]> wrote:

> On my Linode I had upgraded from 5.0.0 to the snapshot. I have been
> getting 404 errors when doing the intial navigation )[my domain
> name].com:5443/openmeetings
>
> In Catalina.out I am seeing the error
>
> Caused by: org.springframework.beans.NotWritablePropertyException: Invalid
> property 'checkTimeout' of bean class
> [org.apache.openmeetings.core.remote.KurentoHandler]: Bean property
> 'checkTimeout' is not writable or has an invalid setter method. Does the
> parameter type of the setter match the return type of the getter?
> at
> org.springframework.beans.BeanWrapperImpl.createNotWritablePropertyException(BeanWrapperImpl.java:243)
> at
> org.springframework.beans.AbstractNestablePropertyAccessor.processLocalProperty(AbstractNestablePropertyAccessor.java:426)
> at
> org.springframework.beans.AbstractNestablePropertyAccessor.setPropertyValue(AbstractNestablePropertyAccessor.java:278)
> at
> org.springframework.beans.AbstractNestablePropertyAccessor.setPropertyValue(AbstractNestablePropertyAccessor.java:266)
> at
> org.springframework.beans.AbstractPropertyAccessor.setPropertyValues(AbstractPropertyAccessor.java:97)
> at
> org.springframework.beans.AbstractPropertyAccessor.setPropertyValues(AbstractPropertyAccessor.java:77)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1730)
>
> checkTimeout is one of the properties for the kurento Handler bean config
> in /opt/open500/webapps/openmeetings/WEB-INF/classes/applicationContext.xml
> mentioned in step 7 of the Creating Let's Encrypt SSL Certificates and
> Installing Coturn on Debian 10
> for OpenMeetings 5.0.0 tutorial. any idea what is the issue?
>
> Dennis
>
> On Tue, 2020-10-27 at 12:54 +0700, Maxim Solodovnik wrote:
>
> Well
> at least the situation is not getting worst :(
>
> I'll wait for reports from others
> can't test such multiuser scenario right now
> my laptop is not powerful enough :(
>
> On Tue, 27 Oct 2020 at 10:49, dww <[email protected]> wrote:
>
> I tried your bash script based on the demo server. As before it seemed
> stable up to 4 guest users, started to deteriorate at 5 and rapidly
> deteriorated beyond that.
>
> Dennis
>
> On Mon, 2020-10-26 at 12:46 +0700, Maxim Solodovnik wrote:
>
>
>
> On Mon, 26 Oct 2020 at 10:45, dww <[email protected]> wrote:
>
> On Mon, 2020-10-26 at 10:24 +0700, Maxim Solodovnik wrote:
>
>
>
> On Mon, 26 Oct 2020 at 10:19, dww <[email protected]> wrote:
>
> Just verified with both laptops using Firefox. This is definitely
> different than 5.0.0.
>
>
> you just verified with what steps? (please be very detailed)
>
>
> 1. From one of my laptops I go to the the demo server,
> https://om.alteametasoft.com:8443 using Firefox and log in.
> 2. I enter the Public Video and Whiteboard Room.
> 3. I select the Allow for video and microphone for WebRTC. The pod for
> this laptop appears with video and audio.
> 4.I send an invitation to my email address to joint.
> 5. On my other laptop (off of the same cable modem) I navigate in Firefox
> to the url in the invitation.
> 6. I select the Allow for video and microphone for WebRTC and change the
> first name from "Guest" to "1DWTest" The pod for this laptop appears along
> side the one for the first laptop and both appear on the first machine Both
> have video and audio.
> 7. I add another tab in Firefox on the second laptop and navigate again
> with the url from the invitation.
>
>
> so you are trying to open 2 *different* invitations in same browser
> This will not work this way (and shouldn't)
>
> browser tabs are sharing same cookies
>
> you need different browsers
> OR
> _maybe_ incognito windows can help
> OR
> you can use *new* chrome/chromium with modified `user-data-dir` this way
> cookies will NOT be shared
> `chromium-browser --user-data-dir=UNIQUE_FOLDER_PATH_HERE
> --disable-infobars --no-default-browser-check --allow-insecure-localhost`
>
>
> 8. Immediately the pod for the first tab on the second laptop and first
> laptop disappear and the 1DWTest user is gone from the users list on both
> laptops.
> 9. I select the Allow for video and microphone for WebRTC and change the
> first name from "Guest" to "2DWTest" The pod for this laptop appears along
> side the one for the first laptop and both appear on the first machine Both
> have video and audio.
> 10 If I go back to the first tab on the second laptop, the user 1DWTest is
> still in the users list along with the user of the first laptop, however
> the pod associated with user 1DWTest is gone, the pod frame for the first
> laptop is present but not video and the first laptop user is in the users
> list.
>
>
>
>
>
>

-- 
Best regards,
Maxim

Reply via email to