Thankyou it could be that !

We have internal ips mapped on the public ethernet for the load balancer 
to connect to also. But im trying to RMI in on the public address. Could 
that be it ? It used to work at some stage, why is it I may have to 
connect like

service:jmx:rmi://mypublichost.com:9998/jndi/rmi://mypublichost.com: 
9999/red5

?


Andreas Folkesson wrote:
> I had the same problem but found a solution. The problem is that JMX  
> opens up a second "data" port which is not possible to specify in  
> red5. You can modify red5 in the class JMXAgent where the  
> JMXServiceURL is created and replace the line with something like  
> this (around line 306):
>
>       JMXServiceURL url = new JMXServiceURL("service:jmx:rmi://localhost:"  
> + (Integer.parseInt(rmiAdapterPort) - 1) +"/jndi/rmi://localhost:" +  
> rmiAdapterPort + "/red5");
>
> In this case if the specified rmi port is 9999 then the data port  
> will be 9998. So, you now need to open up this port in the firewall.
>
> You should now be able to connect to the JMX instance using JConsole  
> with this url:
>
>       service:jmx:rmi://mypublichost.com:9998/jndi/rmi://mypublichost.com: 
> 9999/red5
>
> If you still receives errors then it might be because the server  
> returns the wrong ip (the local) for the JMX client (JConsole) to  
> use.  You might need to specify the following jvm options when you  
> start your red5 server:
>
>       -Djava.rmi.server.hostname=mypublichost.com - 
> Djava.rmi.server.useLocalHostname=true
>
> I hope this helps and let's hope someone from the red5 team could  
> give us the possibility to change the data port without patching the  
> source in the future.
>
> /Andreas
>
>
>
>
> On Jun 27, 2007, at 4:20 AM, Dan Rossi wrote:
>
>   
>> Hi for some strange reason our server is impossible to connect to  
>> either
>> via non-ssl or ssl connections. I am able to connect via localhost but
>> when trying to access remotely jconsole wont connect. Is there any way
>> to debug this on the server it doesnt really tell me much.
>>
>> _______________________________________________
>> Red5 mailing list
>> [email protected]
>> http://osflash.org/mailman/listinfo/red5_osflash.org
>>
>>     
>
>
> _______________________________________________
> Red5 mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/red5_osflash.org
>
>   


_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org

Reply via email to