One more update when I shutdown one OM -node with same configuration it is
working fine.. problem only occur when both node up with cluster
configuration.

On Tue, Jun 5, 2018 at 2:58 PM, Ritu Raj <rituraj0...@gmail.com> wrote:

> Thanks for reply. :)
>
> Yes this issue is reproducible for camera and screen-sharing both.. both
> are not woking.
>
> I have tried with LB ip as well as individual OM node ip in browser in
> both condition it is giving same error.
>
> For camera I have checked DEV console of browser there it is redirecting
> to private ip .
>
> For screen-sharing i have checked client sharing log.. which i have shared
> earlier   .
>
>
>
> On Tue, Jun 5, 2018 at 2:35 PM, Maxim Solodovnik <solomax...@gmail.com>
> wrote:
>
>> The issue is reproducible for both Camera and screen-sharing?
>> What URL do you enter in browser? URL to load balancer?
>>
>> Do you have any errors in browser DEV console?
>>
>> On Tue, Jun 5, 2018 at 3:50 PM, Ritu Raj <rituraj0...@gmail.com> wrote:
>> > Thanks for reply :) ,  I have checked application base url and changed
>> it to
>> > https://loandbalancerip/openmeetings
>> > But problem not resolved.
>> >
>> > Senario is I have Configured  openmeeting with two server and done the
>> > clustering setting as per document and binds these two app in a load
>> > balancer .. application is accessible by lb ip and working fine .. but
>> > problem is facing when we use camera and screen sharing... It is
>> redirect to
>> > https://privateip:8443/openmeetings
>> >
>> > When we removed the cluster part setting then it working fine .. and it
>> is
>> > redirected to https://floatingip:8443/openmeetings .
>> >
>> > for your reference below are screen share log :-
>> >
>> > java.net.ConnectException: Connection refused: no further information
>> > at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
>> > at sun.nio.ch.SocketChannelImpl.finishConnect(Unknown Source)
>> > at
>> > org.apache.mina.transport.socket.nio.NioSocketConnector.fini
>> shConnect(NioSocketConnector.java:223)
>> > at
>> > org.apache.mina.transport.socket.nio.NioSocketConnector.fini
>> shConnect(NioSocketConnector.java:47)
>> > at
>> > org.apache.mina.core.polling.AbstractPollingIoConnector$Conn
>> ector.processConnections(AbstractPollingIoConnector.java:571)
>> > at
>> > org.apache.mina.core.polling.AbstractPollingIoConnector$Conn
>> ector.run(AbstractPollingIoConnector.java:456)
>> > at
>> > org.apache.mina.util.NamePreservingRunnable.run(NamePreservi
>> ngRunnable.java:64)
>> > at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>> > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>> > at java.lang.Thread.run(Unknown Source)
>> > DEBUG 06-05 13:24:49.142 186 o.a.o.s.Core [NioSocketConnector-8] - host:
>> > 192.168.0.30, port: 5443, app: openmeetings/19, publish:
>> > 2fc9a380-89ea-4e19-9b42-772bd76bfd9b
>> >  INFO 06-05 13:24:49.142 281 o.r.c.n.r.BaseRTMPClientHandler
>> > [NioSocketConnector-8] - rtmps://192.168.0.30:5443/openmeetings/19
>> > ERROR 06-05 13:24:50.344 64 o.a.o.s.RTMPSScreenShare
>> [NioSocketConnector-9]
>> > - {}
>> > java.net.ConnectException: Connection refused: no further information
>> > at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
>> > at sun.nio.ch.SocketChannelImpl.finishConnect(Unknown Source)
>> > at
>> > org.apache.mina.transport.socket.nio.NioSocketConnector.fini
>> shConnect(NioSocketConnector.java:223)
>> > at
>> > org.apache.mina.transport.socket.nio.NioSocketConnector.fini
>> shConnect(NioSocketConnector.java:47)
>> > at
>> > org.apache.mina.core.polling.AbstractPollingIoConnector$Conn
>> ector.processConnections(AbstractPollingIoConnector.java:571)
>> > at
>> > org.apache.mina.core.polling.AbstractPollingIoConnector$Conn
>> ector.run(AbstractPollingIoConnector.java:456)
>> > at
>> > org.apache.mina.util.NamePreservingRunnable.run(NamePreservi
>> ngRunnable.java:64)
>> > at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>> > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>> > at java.lang.Thread.run(Unknown Source)
>> > DEBUG 06-05 13:24:50.344 186 o.a.o.s.Core [NioSocketConnector-9] - host:
>> > 192.168.0.30, port: 5443, app: openmeetings/19, publish:
>> > 2fc9a380-89ea-4e19-9b42-772bd76bfd9b
>> >  INFO 06-05 13:24:50.344 281 o.r.c.n.r.BaseRTMPClientHandler
>> > [NioSocketConnector-9] - rtmps://192.168.0.30:5443/openmeetings/19
>> >  WARN 06-05 13:24:50.359 502 o.a.o.s.g.ScreenSharerFrame
>> [AWT-EventQueue-2]
>> > - Recording action is already requested
>> > ERROR 06-05 13:24:51.498 64 o.a.o.s.RTMPSScreenShare
>> [NioSocketConnector-10]
>> > - {}
>> > java.net.ConnectException: Connection refused: no further information
>> > at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
>> > at sun.nio.ch.SocketChannelImpl.finishConnect(Unknown Source)
>> > at
>> > org.apache.mina.transport.socket.nio.NioSocketConnector.fini
>> shConnect(NioSocketConnector.java:223)
>> > at
>> > org.apache.mina.transport.socket.nio.NioSocketConnector.fini
>> shConnect(NioSocketConnector.java:47)
>> > at
>> > org.apache.mina.core.polling.AbstractPollingIoConnector$Conn
>> ector.processConnections(AbstractPollingIoConnector.java:571)
>> > at
>> > org.apache.mina.core.polling.AbstractPollingIoConnector$Conn
>> ector.run(AbstractPollingIoConnector.java:456)
>> > at
>> > org.apache.mina.util.NamePreservingRunnable.run(NamePreservi
>> ngRunnable.java:64)
>> > at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>> > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>> > at java.lang.Thread.run(Unknown Source)
>> > DEBUG 06-05 13:24:51.498 186 o.a.o.s.Core [NioSocketConnector-10] -
>> host:
>> > 192.168.0.30, port: 5443, app: openmeetings/19, publish:
>> > 2fc9a380-89ea-4e19-9b42-772bd76bfd9b
>> >  INFO 06-05 13:24:51.498 281 o.r.c.n.r.BaseRTMPClientHandler
>> > [NioSocketConnector-10] - rtmps://192.168.0.30:5443/openmeetings/19
>> > DEBUG 06-05 13:24:52.465 426 o.a.o.s.Core [AWT-EventQueue-2] -
>> ScreenShare
>> > stopStream
>> >  INFO 06-05 13:24:52.465 585 o.q.c.QuartzScheduler [AWT-EventQueue-2] -
>> > Scheduler CoreScreenShare_$_NON_CLUSTERED paused.
>> > DEBUG 06-05 13:24:52.481 610 o.a.o.s.g.ScreenSharerFrame
>> [AWT-EventQueue-2]
>> > - sharingActionRequested=false
>> > DEBUG 06-05 13:24:52.481 622 o.a.o.s.g.ScreenSharerFrame
>> [AWT-EventQueue-2]
>> > - recordingActionRequested=true
>> >  INFO 06-05 13:24:52.496 545 o.r.c.n.r.BaseRTMPClientHandler
>> > [AWT-EventQueue-2] - Connection was null
>> >
>> > Please check and suggest.
>> >
>> > On Sun 3 Jun, 2018, 6:25 PM Maxim Solodovnik, <solomax...@gmail.com>
>> wrote:
>> >>
>> >> This is it application.base.url
>> >>
>> >> On Sun, Jun 3, 2018 at 7:25 PM, Ritu Raj <rituraj0...@gmail.com>
>> wrote:
>> >> > Can you please tell me exact path of configuration ?
>> >> >
>> >> > On Sun 3 Jun, 2018, 5:11 PM Maxim Solodovnik, <solomax...@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> Maybe you set wrong base url in Admin?
>> >> >>
>> >> >> On Fri, Jun 1, 2018 at 8:11 PM, Ritu Raj <rituraj0...@gmail.com>
>> wrote:
>> >> >> >
>> >> >> >
>> >> >> >> [OPENMEETINGS-1887] Webcam image not showing - ASF JIRA
>> >> >> >>
>> >> >> >> I have configured cluster on cloud instance , which have two ip
>> one
>> >> >> >> is
>> >> >> >> floating ip and another one is private ip , port 5443 and 8443
>> are
>> >> >> >> opened
>> >> >> >> for floating ip. the thing is that we are accessing openmeeting
>> >> >> >> through
>> >> >> >> floating ip with port of 5443 as per standard but when we use the
>> >> >> >> functionality of camera and screen sharing it is redirected to
>> its
>> >> >> >> private
>> >> >> >> IP with port 8443 which should not be happen.
>> >> >> >>
>> >> >> >> When i remove the clustering part from openmeeting then it works
>> and
>> >> >> >> it
>> >> >> >> redirected to floating ip but load balancing not worked.
>> >> >> >>
>> >> >> >> openmeeting version : 4.0.2
>> >> >> >>
>> >> >> >> Please help.
>> >> >> >>
>> >> >> >> Regards,
>> >> >> >>
>> >> >> >> Ritu Raj
>> >> >> >>
>> >> >> >> +91 7977099454/8602198583
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> WBR
>> >> >> Maxim aka solomax
>> >>
>> >>
>> >>
>> >> --
>> >> WBR
>> >> Maxim aka solomax
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>

Reply via email to