[
https://issues.apache.org/jira/browse/GERONIMO-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay D. McHugh resolved GERONIMO-2567.
-
Resolution: Invalid
Assignee: Jay D. McHugh
Kevan,
You are correct - It was an IPv6 issue (I hadn't realized that I had IPv6
enabled locally).
So, taking that into account (specifying the remote server address using the
IPv4 version
surrounded by "[ ]") and setting the remoteDeployAddress in the server's
config.xml
(server address in IPv4 surrounded by "[ ]" with the port set to ) allowed
me to connect
and list my modules.
Rather than a bug, this looks like it would be better addressed in the
documentation.
> Remote admin of server using deployer.jar fails to connect
> --
>
> Key: GERONIMO-2567
> URL: https://issues.apache.org/jira/browse/GERONIMO-2567
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
>Affects Versions: 1.2, 2.0, 2.0.x
> Environment: Linux
> Java 1.5
>Reporter: Jay D. McHugh
>Assignee: Jay D. McHugh
> Fix For: Verification Required
>
>
> Trying to remote deploy a WAR file resulted in a failed connection.
> This happened regardless of whether the port was specified.
> $ java -jar deployer.jar --user system --password manager --host 172.16.1.41
> redeploy ~/PaLM.war
> Error: Unable to connect to server at
> deployer:geronimo:jmx://172.16.1.41 -- Connection refused to host:
> 127.0.0.1; nested exception is:
> java.net.ConnectException: Connection refused
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
