Re: [jira] Commented: (GERONIMO-4518) Can't shutdown the server when host was set to 127.0.0.1 in config-substitutions.properties
I don't think this is a application specific problem. I did some test and found the reproduce steps and the root cause here: Reproduce steps: 1, Change NamingPort=3099 from 1099 in var/config-substitutions.properties. 2, Use GShell command "geronimo/start-server“ to start the server. 3, Use Use GShell command "geronimo/stop-server -p 3099“ to stop the server. Expected result: the server could be shutdown and return to the GShell command line mode. Actually result: The server can't be shutdown, can't return to the GShell command line. Root Cause: You have to use "geronimo/start-server -p 3099" to start server if you want use "geronimo/stop-server -p 3099“ to stop the server. I believe there should not a -p args for geronimo/start-server command. Instead, geronimo/start-server should read NamingPort=3099 in config.substitutions.properties to avoid the problem. I've created a JIRA to track this problem: https://issues.apache.org/jira/browse/GSHELL-162 On Thu, Feb 26, 2009 at 4:33 AM, Jeff Lu (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/GERONIMO-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676766#action_12676766 > ] > > Jeff Lu commented on GERONIMO-4518: > --- > > Jarek, > > I found the problem that is within our apps when shutdown is issued, one of > the threads was in a forever wait state causing shutdown to hang. Problem > solved. > > Thank you > >> 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. > > -- Shawn
[jira] Commented: (GERONIMO-4518) Can't shutdown the server when host was set to 127.0.0.1 in config-substitutions.properties
[ https://issues.apache.org/jira/browse/GERONIMO-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676766#action_12676766 ] Jeff Lu commented on GERONIMO-4518: --- Jarek, I found the problem that is within our apps when shutdown is issued, one of the threads was in a forever wait state causing shutdown to hang. Problem solved. Thank you > 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.
Re: [jira] Commented: (GERONIMO-4518) Can't shutdown the server when host was set to 127.0.0.1 in config-substitutions.properties
Confirmed, this should be a gshell start/shutdown problem because the server could be started/shutdown successfully with startup.bat/sh and shutdown.bat/sh. On Tue, Feb 24, 2009 at 5:26 AM, Jeff Lu (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/GERONIMO-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676071#action_12676071 > ] > > Jeff Lu commented on GERONIMO-4518: > --- > > Jarek, > > I just pulled down the latest build of 2.1.4 snapshot. I made the changes to > all references of localhost and 0.0.0.0 to 127.0.0.1in > config-substitutions.properties as mentioned above. > > When ran stop-server > C:\Geronimo2.1.4\bin>stop-server -p 3999 > Connecting to Geronimo server: localhost:3999 > Username: system > Password: *** > Connection established > Stopping Geronimo server... > > The command never returns and the server never stops > > Thank you > > > >> 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. > > -- Shawn
[jira] Commented: (GERONIMO-4518) Can't shutdown the server when host was set to 127.0.0.1 in config-substitutions.properties
[ https://issues.apache.org/jira/browse/GERONIMO-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676071#action_12676071 ] Jeff Lu commented on GERONIMO-4518: --- Jarek, I just pulled down the latest build of 2.1.4 snapshot. I made the changes to all references of localhost and 0.0.0.0 to 127.0.0.1in config-substitutions.properties as mentioned above. When ran stop-server C:\Geronimo2.1.4\bin>stop-server -p 3999 Connecting to Geronimo server: localhost:3999 Username: system Password: *** Connection established Stopping Geronimo server... The command never returns and the server never stops Thank you > 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.
[jira] Commented: (GERONIMO-4518) Can't shutdown the server when host was set to 127.0.0.1 in config-substitutions.properties
[ https://issues.apache.org/jira/browse/GERONIMO-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669872#action_12669872 ] Shawn Jiang commented on GERONIMO-4518: --- I just verified that this is fixed in the latest 2.2 snapshot and 2.1.4 snapshot. Thank Jarek ! > 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.
[jira] Commented: (GERONIMO-4518) Can't shutdown the server when host was set to 127.0.0.1 in config-substitutions.properties
[ 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.
[jira] Commented: (GERONIMO-4518) Can't shutdown the server when host was set to 127.0.0.1 in config-substitutions.properties
[ https://issues.apache.org/jira/browse/GERONIMO-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665757#action_12665757 ] Shawn Jiang commented on GERONIMO-4518: --- I've verified that this defect was fixed in latest 2.1.4 snapshot build. Thanks. > 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: Donald Woods >Priority: Blocker > 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.
[jira] Commented: (GERONIMO-4518) Can't shutdown the server when host was set to 127.0.0.1 in config-substitutions.properties
[ https://issues.apache.org/jira/browse/GERONIMO-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664451#action_12664451 ] Shawn Jiang commented on GERONIMO-4518: --- I guess this is a regression of https://issues.apache.org/jira/browse/GERONIMO-4442 The org.apache.geronimo.deployment.cli.StopServer will always try to connect the real IP instead of the "127.0.0.1" passed in. I'm trying to use a customized GeronimoRMIClientSocketFactory to limit the the connection to the host passed in. > 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.2 > Environment: Windows XP + Sun JDK 1.5 >Reporter: Shawn Jiang > > 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.
