[
https://issues.apache.org/jira/browse/KITTY-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057146#comment-13057146
]
Alessandro Novarini commented on KITTY-29:
------------------------------------------
Actually the problem is not related to the host, but to its port.
In fact, the code doesn't take the correct port passed as parameter, but it
keeps using the default one (1099).
Here's attached a patch, without tests at the moment; I'll provide them as soon
as I can though.
> Connection refused to host: localhost
> -------------------------------------
>
> Key: KITTY-29
> URL: https://issues.apache.org/jira/browse/KITTY-29
> Project: Kitty
> Issue Type: Bug
> Reporter: Alessandro Novarini
> Attachments: kitty-29.patch
>
>
> I am working off of trunk and I am trying to connect to a local Tomcat
> server. I can connect using jconsole remote but for some reason I get the
> following exception with kitty, can anyone reproduce?
> kitty> connect localhost 9000
> connect localhost 9000
> ERROR! Failed to retrieve RMIServer stub:
> javax.naming.ServiceUnavailableException [Root exception is
> java.rmi.ConnectException: Connection refused to host: localhost; nested
> exception is:
> java.net.ConnectException: Connection refused]
> Connection attempt was unsuccessful
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
