[ 
https://issues.apache.org/jira/browse/GERONIMO-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668308#action_12668308
 ] 

Jarek Gawor commented on GERONIMO-4518:
---------------------------------------

I looked at this a bit more and here's what I think is going on. The client 
connects to the address returned by InetAddress.getLocalHost() of the remote 
server. The address returned by InetAddress.getLocalHost() is really based on 
the machine's network configuration. The network configuration should be set 
properly to return the appropriate address (the public ip address or the local 
loopback address that matches the ServerHostname substitution property). 
It's the RMI code somewhere that calls InetAddress.getLocalHost() by default. 
However, we can force the RMI code to use a specific hostname by setting the 
"java.rmi.server.hostname" system property. We can set that system property to 
the ServerHostname substitution property. This should make things work better 
if ServerHostname is set to something else then 0.0.0.0. But if ServerHostname 
is set to 0.0.0.0 (which is set by default) machine's network configuration 
must still be set correctly so that InetAddress.getLocalHost() returns the 
right ip address. 


> Can't shutdown the server when host was set to 127.0.0.1 in 
> config-substitutions.properties
> -------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-4518
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4518
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: startup/shutdown
>    Affects Versions: 2.1.4, 2.2
>         Environment: Windows XP + Sun JDK 1.5
>            Reporter: Shawn Jiang
>            Assignee: Jarek Gawor
>             Fix For: 2.1.4, 2.2
>
>         Attachments: G4518_Shawn.patch
>
>
> 1, change the host in config-substitutions.properties to 127.0.0.1
> 2, start the server.
> 3, shutdown the server.
> *expected result*: the server could be shutdown.
> *actual result*: the sever can't be shutdown with exception:  
> java.net.ConnectException: Connection refused: connect
> --------------------------------------
> C:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT\bin>shutdown --host 127.0.0.1
> Using GERONIMO_HOME:   C:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT
> Using GERONIMO_TMPDIR: var\temp
> Using JRE_HOME:        D:\dev\JDKs\sun_jdk1.5.0_15\jre
> log4j:WARN No appenders could be found for logger 
> (org.apache.geronimo.kernel.basic.BasicKernel).
> log4j:WARN Please initialize the log4j system properly.
> Username: system
> Password: *******
> Locating server on 127.0.0.1:1099...
> Could not communicate with the server.  The server may not be running or the 
> port number may be inco
> rrect (Connection refused to host: 6.153.277.58; nested exception is:
>         java.net.ConnectException: Connection refused: connect)

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

Reply via email to