Hey all,

  I was able to connect! These are the steps that I took
http://www.liferay.com/pt/web/thiago.moreira/blog/-/blogs/how-to-monitor-liferay-tomcat-remotely-through-firewalls-using-visualvm

  Thanks!

  Thiago Moreira

On Mon, Oct 24, 2011 at 1:56 PM, Thiago Moreira (timba) <
tmoreira2...@gmail.com> wrote:

>
>   Another step forward... I got jconsole print some debugging information.
> Using *jconsole -J-Djava.util.logging.config.file=logging.properties*
>
>   And found out that it is necessary add the catalina-jmx-remote.jar to
> jconsole classpath (*jconsole
> -J-Djava.util.logging.config.file=logging.properties
> -J-Djava.class.path=$JAVA_HOME/lib/jconsole.jar:$JAVA_HOME/lib/tools.jar:catalina-jmx-remote.jar
> *) now I'm getting this connection refused error. I can ping without
> problems the domain *tmoreira2020-VirtualBox.*
>
> Oct 24, 2011 1:46:33 PM RMIConnector connect
> FINER: [javax.management.remote.rmi.RMIConnector:
> jmxServiceURL=service:jmx:rmi://
> 10.226.2.187:8850/jndi/rmi://10.226.2.187:8849/jmxrmi] connecting...
> Oct 24, 2011 1:46:33 PM RMIConnector connect
> FINER: [javax.management.remote.rmi.RMIConnector:
> jmxServiceURL=service:jmx:rmi://
> 10.226.2.187:8850/jndi/rmi://10.226.2.187:8849/jmxrmi] finding stub...
> Oct 24, 2011 1:46:33 PM RMIConnector connect
> FINER: [javax.management.remote.rmi.RMIConnector:
> jmxServiceURL=service:jmx:rmi://
> 10.226.2.187:8850/jndi/rmi://10.226.2.187:8849/jmxrmi] connecting stub...
> Oct 24, 2011 1:46:33 PM RMIConnector connect
> FINER: [javax.management.remote.rmi.RMIConnector:
> jmxServiceURL=service:jmx:rmi://
> 10.226.2.187:8850/jndi/rmi://10.226.2.187:8849/jmxrmi] getting
> connection...
> Oct 24, 2011 1:46:33 PM RMIConnector connect
> FINER: [javax.management.remote.rmi.RMIConnector:
> jmxServiceURL=service:jmx:rmi://
> 10.226.2.187:8850/jndi/rmi://10.226.2.187:8849/jmxrmi] failed to connect:
> java.rmi.ConnectException: Connection refused to host:
> tmoreira2020-VirtualBox; nested exception is:
>  java.net.ConnectException: Connection refused
>
>   * *Not sure why this exception is happening.
>
>
> On Mon, Oct 24, 2011 at 11:34 AM, Thiago Moreira (timba) <
> tmoreira2...@gmail.com> wrote:
>
>>
>>   Hey Christopher,
>>
>>   All machines are running IPv4, IPv6 is disabled. And it is possible use
>> with or without space between -L and its forwarding specifiers. Today is my
>> third day fighting against this... totally frustrated! Is there a log
>> configuration that I can turn on to check if the JMX connections coming from
>> VisualVM are being served?
>>
>> On Fri, Oct 21, 2011 at 7:08 PM, Christopher Schultz <
>> ch...@christopherschultz.net> wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Thiago,
>>>
>>> On 10/21/2011 1:37 PM, Thiago Moreira (timba) wrote:
>>> > On my host machine I fired the tunneling with: ssh -v
>>> > -L10.226.2.212/8849/localhost/8849
>>> > -L10.226.2.212/8850/localhost/8850 192.168.56.101
>>>
>>> Is it possible that ssh is confused by your use of IPv6-style
>>> forwarding syntax while using IPv4 addresses? Also, -L expects a space
>>> between it and the forwarding specifier.
>>>
>>> How about this:
>>>
>>> ssh -L 10.226.2.212:8850:localhost:8850 \
>>>    -L 10.226.2.212:8850:localhost:8850
>>>
>>> - -chris
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.4.10 (MingW32)
>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>>
>>> iEYEARECAAYFAk6h31QACgkQ9CaO5/Lv0PDNjQCeMLN901blBs4zDVUeZoCGQLVh
>>> wlQAoJBV9nTl2fqRy5Bgv0YK57/Pa7m6
>>> =bAqT
>>> -----END PGP SIGNATURE-----
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>
>>>
>>
>

Reply via email to