geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Jiang <genspr...@gmail.com>
Subject Re: [jira] Commented: (GERONIMO-4518) Can't shutdown the server when host was set to 127.0.0.1 in config-substitutions.properties
Date Fri, 27 Feb 2009 04:50:25 GMT
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) <jira@apache.org> 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

Mime
View raw message