geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jay D. McHugh (JIRA)" <>
Subject [jira] Resolved: (GERONIMO-2567) Remote admin of server using deployer.jar fails to connect
Date Tue, 21 Aug 2007 16:02:31 GMT


Jay D. McHugh resolved GERONIMO-2567.

    Resolution: Invalid
      Assignee: Jay D. McHugh


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 9999) 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:
>             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 redeploy
>     Error: Unable to connect to server at
>     deployer:geronimo:jmx:// -- Connection refused to host:
>; nested exception is:
> Connection refused

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message