You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jay D. McHugh (JIRA)" <ji...@apache.org> on 2007/09/07 01:16:29 UTC
[jira] Closed: (GERONIMO-2567) Remote admin of server using
deployer.jar fails to connect
[ https://issues.apache.org/jira/browse/GERONIMO-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jay D. McHugh closed GERONIMO-2567.
-----------------------------------
Fixed in Revision: 568302
Linux notes:
The hostname of the server needs to appear in the /etc/hosts file (on the server) with its external ip address.
And the <geronimo-home>/var/config/config.xml file needs to have the gbean-deployer module
updated to point to the external address (of the server).
ie:
<module name="org.apache.geronimo.configs/geronimo-gbean-deployer/2.1-SNAPSHOT/car">
<gbean name="Deployer">
<attribute name="remoteDeployAddress">http://172.16.1.2:${HTTPPortPrimary + PortOffset}</attribute>
</gbean>
</module>
> 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: Kevan Miller
> Fix For: 2.0.x, 2.1
>
>
> 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.