geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim McConnell (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMODEVTOOLS-537) Remote server deployment fails with connection exception
Date Tue, 02 Dec 2008 00:05:44 GMT

     [ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tim McConnell closed GERONIMODEVTOOLS-537.
------------------------------------------

    Resolution: Invalid

Here are the correct sequence of steps to facilitate deployment to a remote server using the
GEP:

1. First define a local server and make sure it starts within Eclipse. If it starts okay,
in the Servers view of the Java EE perspective in Eclipse double-click on the server and update
the hostname from "localhost" to the remote server's hostname or IP.

2. Similarly, on the remote system update the RemoteDeployHostname value in config-substitutions.properties
 to listen on something besides localhost (i.e., use remote server's hostname or IP as above).

3. Leave Eclipse up and then start the server on the remote system. Even though you can't
use Eclipse to start/stop the server on the remote system Eclipse should still synchronize
with the remote server. If it does synchronize you will see the status of the server in Eclipse
change from "Stopped" to *Started" (again in the Servers view). This make take a few seconds
to synchronize, but then you should be able to deploy to that Server.

4. Ensure the server on the remote system is still running and then try to deploy via Eclipse.

> Remote server deployment fails with connection exception
> --------------------------------------------------------
>
>                 Key: GERONIMODEVTOOLS-537
>                 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-537
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>          Components: eclipse-plugin
>    Affects Versions: 2.2.0, 2.1.4
>            Reporter: Tim McConnell
>            Assignee: Tim McConnell
>
> Distribution of module failed.  See log for details.
>   Connection refused: connect
>   java.net.ConnectException: Connection refused: connect
>   	at java.net.PlainSocketImpl.socketConnect(Native Method)
>   	at java.net.PlainSocketImpl.doConnect(Unknown Source)
>   	at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
>   	at java.net.PlainSocketImpl.connect(Unknown Source)
>   	at java.net.Socket.connect(Unknown Source)
>   	at java.net.Socket.connect(Unknown Source)
>   	at sun.net.NetworkClient.doConnect(Unknown Source)
>   	at sun.net.www.http.HttpClient.openServer(Unknown Source)
>   	at sun.net.www.http.HttpClient.openServer(Unknown Source)
>   	at sun.net.www.http.HttpClient.<init>(Unknown Source)
>   	at sun.net.www.http.HttpClient.New(Unknown Source)
>   	at sun.net.www.http.HttpClient.New(Unknown Source)
>   	at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
>   	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
>   	at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
>   	at org.apache.geronimo.deployment.plugin.remote.FileUploadServletClient.connectToServer(FileUploadServletClient.java:266)
>   	at org.apache.geronimo.deployment.plugin.remote.FileUploadServletClient.uploadFilesToServer(FileUploadServletClient.java:115)
>   	at org.apache.geronimo.deployment.plugin.remote.RemoteDeployUtil.uploadFilesToServer(RemoteDeployUtil.java:33)
>   	at org.apache.geronimo.deployment.plugin.remote.DistributeCommand.massageFileNames(DistributeCommand.java:43)
>   	at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:114)
>   	at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)
>   	at org.apache.geronimo.deployment.plugin.remote.DistributeCommand.run(DistributeCommand.java:50)
>   	at java.lang.Thread.run(Unknown Source)

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


Mime
View raw message