geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-3038) A server process shuts down quietly when path to cache.xml is incorrect
Date Wed, 02 Aug 2017 14:41:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111032#comment-16111032
] 

ASF GitHub Bot commented on GEODE-3038:
---------------------------------------

GitHub user anton-mironenko opened a pull request:

    https://github.com/apache/geode/pull/677

    GEODE-3038: A server process shuts down quietly when path to cache.xml is incorrect

    [GEODE-3038](https://issues.apache.org/jira/browse/GEODE-3038)
    The error 
    "Declarative Cache XML file/resource \[path-to-cache-xml\] does not exist"
    is trying to be written into the log in GemFireCacheImpl.basicCreate(), after method GemFireCacheImpl.close()
is called, so that writing into the log is already not available.
    
    Thank you for submitting a contribution to Apache Geode.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
    
    - [ ] Has your PR been rebased against the latest commit within the target branch (typically
`develop`)?
    
    - [x] Is your initial contribution a single, squashed commit?
    
    - [x] Does `gradlew build` run cleanly?
    
    - [ ] Have you written or updated unit tests to verify your changes?
    
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way
that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and
    submit an update to your PR as soon as possible. If you need help, please send an
    email to dev@geode.apache.org.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/anton-mironenko/geode develop

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/geode/pull/677.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #677
    
----
commit f119fb381d4212e8714d26f2388860206daa3d8a
Author: Anton Mironenko <anton.mironenko@gmail.com>
Date:   2017-08-01T12:18:12Z

    write cachexml-not-found exception into the log in a proper place

commit bf0b059035751b3d7cba82a145546edb7efce824
Author: Anton Mironenko <anton.mironenko@gmail.com>
Date:   2017-08-01T12:52:14Z

    Merge remote-tracking branch 'upstream/develop' into GEODE-3038

----


> A server process shuts down quietly when path to cache.xml is incorrect
> -----------------------------------------------------------------------
>
>                 Key: GEODE-3038
>                 URL: https://issues.apache.org/jira/browse/GEODE-3038
>             Project: Geode
>          Issue Type: Bug
>          Components: configuration
>            Reporter: Anton Mironenko
>            Assignee: Kirk Lund
>            Priority: Minor
>
> Geode version: 1.1.1, 1.3.0 (latest develop snapshot)
> If I start a server with incorrect path to Server.xml, it shuts down quietly without
any message in the log. 
> An expected behavior would be the error message "Server.xml not found in the path [...],
shutting down"
> Here are the steps to reproduce, please use GEODE-3003 for zip files.
> Test preparation:
> ---------------------
> Here are two attached zip files - "geode-host1.zip" and "geode-host2.zip"
> 1) unzip "geode-host1.zip" into some folder on your first host
> 2) in start-locator.sh change the IPs of locators to the values of your host1 and host2
> "--locators=10.50.3.38[20236],10.50.3.14[20236]"
> 3) in start-server.sh
> "locators=10.50.3.38[20236],10.50.3.14[20236]" change the IPs of locators to the values
of your host1 and host2
> 4) do the bullets 1)-4) for host2, the folder where you unzip the file should be the
same as on the first host
> Test running:
> ---------------
> 0) change start-server.sh so that the path to Server.xml is wrong
> cache-xml-file=$SERVERXML_DIR/Server.xml
> ->
> cache-xml-file=$SERVERXML_DIR/Server_.xml
> 1) run ./start-locator.sh on host1
> 2) after some pause run ./start-server
> 3) observe the server started and immediately stopped,
> 4) observe in the server logs, server1/cacheserver.log:
> [info 2017/06/06 18:32:05.141 MSK host1-server-1 <main> tid=0x1] Received cluster
configuration from the locator
> [info 2017/06/06 18:32:05.141 MSK host1-server-1 <main> tid=0x1] 
>   ***************************************************************
>   Configuration for  'cluster'
>   
>   Jar files to deployed
> [info 2017/06/06 18:32:05.141 MSK host1-server-1 <main> tid=0x1] Requesting cluster
configuration
> [info 2017/06/06 18:32:05.143 MSK host1-server-1 <main> tid=0x1] Got response with
jars: 
> [info 2017/06/06 18:32:05.209 MSK host1-server-1 <main> tid=0x1] Initializing region
_monitoringRegion_10.50.3.38<v1>1025
> [info 2017/06/06 18:32:05.222 MSK host1-server-1 <main> tid=0x1] Region _monitoringRegion_10.50.3.38<v1>1025
requesting initial image from 10.50.3.38(host1-locator-0-20236:27511:locator)<ec><v0>:1024
> [info 2017/06/06 18:32:05.227 MSK host1-server-1 <main> tid=0x1] _monitoringRegion_10.50.3.38<v1>1025
is done getting image from 10.50.3.38(host1-locator-0-20236:27511:locator)<ec><v0>:1024.
isDeltaGII is false
> [info 2017/06/06 18:32:05.228 MSK host1-server-1 <main> tid=0x1] Initialization
of region _monitoringRegion_10.50.3.38<v1>1025 completed
> [info 2017/06/06 18:32:05.812 MSK host1-server-1 <main> tid=0x1] GemFireCache[id
= 2117642238; isClosing = true; isShutDownAll = false; created = Tue Jun 06 18:32:05 MSK 2017;
server = false; copyOnRead = false; lockLease = 120; lockTimeout = 60]: Now closing.
> [info 2017/06/06 18:32:05.855 MSK host1-server-1 <main> tid=0x1] Shutting down
DistributionManager 10.50.3.38(host1-server-1:27773)<v1>:1025. 
> [info 2017/06/06 18:32:05.961 MSK host1-server-1 <main> tid=0x1] Now closing distribution
for 10.50.3.38(host1-server-1:27773)<v1>:1025
> [info 2017/06/06 18:32:05.962 MSK host1-server-1 <main> tid=0x1] Stopping membership
services
> [info 2017/06/06 18:32:05.964 MSK host1-server-1 <Geode Failure Detection Server thread
0> tid=0x1d] GMSHealthMonitor server thread exiting
> [info 2017/06/06 18:32:05.964 MSK host1-server-1 <main> tid=0x1] GMSHealthMonitor
server socket is closed in stopServices().
> [info 2017/06/06 18:32:05.968 MSK host1-server-1 <main> tid=0x1] GMSHealthMonitor
serverSocketExecutor is terminated
> [info 2017/06/06 18:32:05.974 MSK host1-server-1 <main> tid=0x1] DistributionManager
stopped in 119ms.
> [info 2017/06/06 18:32:05.974 MSK host1-server-1 <main> tid=0x1] Marking DistributionManager
10.50.3.38(host1-server-1:27773)<v1>:1025 as closed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message