Hi Dharam,

Thanks for researching this further.  Can you share the log snippet from the 
server where it prints the classpath?  I’m curious if spring-shell is on the 
classpath of the server.

Anthony

> On Sep 6, 2017, at 3:13 AM, Thacker, Dharam <[email protected]> 
> wrote:
> 
> Let me be specific here after some more testing!
> 
>>> It works fine for both (Locator & Server) started via GFSH
> 
>>> It only fails for Server started via spring boot container bootstrapped 
>>> using spring-data-geode api
> 
> Regards,
> Dharam
> 
> -----Original Message-----
> From: Thacker, Dharam
> Sent: Wednesday, September 06, 2017 11:31 AM
> To: '[email protected]'
> Subject: RE: Health check URLs for cache server
> 
> Thanks for the reply Gregory!
> 
> I am still getting member name without host specification for me.  I have 
> shown my locator properties as well below, My current version: Apache Geode 
> 1.1.1
> 
> Monitor and Manage Apache Geode
> gfsh>connect --locator=localhost[10334]
> Connecting to Locator at [host=localhost, port=10334] ..
> Connecting to Manager at [host=Host1XX, port=1099] ..
> user: admin
> password: *******
> Successfully connected to: [host=Host1XX, port=1099]
> 
> gfsh>list members
>         Name          | Id
> ---------------------- | 
> --------------------------------------------------------
> Locator2          | Host2XX(Locator2:14775:locator)<ec><v0>:1024
> Locator1          | Host1XX(Locator1:25952:locator)<ec><v7>:1024
> Server2            | Host2XX (Server2:15034)<ec><v2>:1025
> Server1           | Host1XX(Server1:26711)<ec><v3>:1025
> 
> gfsh>status server --name=Server1
> An error occurred while attempting to determine the status of Geode Cache 
> server: null
> 
> 
> My Geode Locator Properties,
> 
> locators=Host1XX[10334],Host2XX[10334]
> mcast-port=0
> jmx-manager=true
> jmx-manager-start=true
> jmx-manager-port=1099
> jmx-manager-ssl-enabled=false
> jmx-manager-ssl-require-authentication=false
> jmx-manager-bind-address=Host1XX
> enable-network-partition-detection=false
> http-service-port=9201
> http-service-bind-address=Host1XX
> log-file=/apps/geode/members/Locator1/logs/Locator1-Host1XX.log
> log-file-size-limit=10
> log-level=config
> log-disk-space-limit=100
> security-manager=com.x.x.x.ClusterSecurityManager
> security-post-processor=com.x.x.ClusterPostProcessor
> 
> Thanks,
> Dharam
> 
> -----Original Message-----
> From: Gregory Vortman [mailto:[email protected]]
> Sent: Wednesday, September 06, 2017 11:21 AM
> To: [email protected]
> Subject: RE: Health check URLs for cache server
> 
> Hi Dharam,
> The command you specified is correct.
> However the Member Name specification in your grid doesn't contain host 
> specification.  May be it leads to ambiguity.
> This how it looks in my grid:
> 
> gfsh>list members
>       Name         | Id
> ------------------- | 
> ---------------------------------------------------------
> myhost2203-locator   | 
> 10.236.xx.yy(myhost2203-locator:3103:locator)<ec><v0>:1024
> myhost2203-server1   | 10.236.xx.yy(myhost2203-server1:5411)<v1>:1025
> 
> gfsh>status server --name= myhost2203-server1
> Server in /spotuser/spot/envs/vmwrk5/GEODE/Server/servers/server1 on 
> myhost2203.corp.amdocs.com[19418] as myhost2203-server1 is currently online.
> Process ID: 5411
> Uptime: 1 day 15 hours 40 minutes 35 seconds Geode Version: 
> 1.2.0-amdocs-230817151200 Java Version: 1.8.0_102 Log File: 
> /spotuser/spot/envs/vmwrk5/GEODE/Server/servers/server1/myhost2203-server1.log
> JVM Arguments: .....
> Class-Path: .....
> 
> Regards
> 
> -----Original Message-----
> From: Thacker, Dharam [mailto:[email protected]]
> Sent: Wednesday, September 06, 2017 8:25 AM
> To: [email protected]
> Subject: RE: Health check URLs for cache server
> 
> Hello Team,
> 
> Could someone help me on this? It does not show me status for a running 
> server to me with GFSH.
> Is that a right command?
> 
> Thanks,
> Dharam
> 
> -----Original Message-----
> From: Thacker, Dharam
> Sent: Thursday, August 31, 2017 9:44 AM
> To: '[email protected]'
> Subject: RE: Health check URLs for cache server
> 
> Hi Jacob,
> 
> Thanks for the reply! But looks like some bug in "gfsh status server" 
> command. Could you verify your side?
> 
> Version: Apache Geode 1.1.1
> 
> gfsh>list members
>         Name          | Id
> ---------------------- | 
> ----------------------------------------------------------
> Locator1          | Host1XX(Locator1:32053:locator)<ec><v110>:1024
> Locator2          | Host2XX(Locator2:8642:locator)<ec><v123>:1024
> Server1           | Host1XX(Server1:1666)<ec><v111>:1025
> Server2           | Host2XX(Server2:10954)<ec><v124>:1025
> 
> gfsh>status server --name=Server2
> An error occurred while attempting to determine the status of Geode Cache 
> server: null
> 
> Thanks,
> Dharam
> 
> -----Original Message-----
> From: Jacob Barrett [mailto:[email protected]]
> Sent: Monday, August 21, 2017 1:46 AM
> To: [email protected]
> Subject: Re: Health check URLs for cache server
> 
> 
> 
>> On Aug 20, 2017, at 11:37 AM, Dharam Thacker <[email protected]> 
>> wrote:
>> 
>> Hi Team,
>> 
>> 1) Is there any health check URL which can tell me if server started fully?
>> 
> 
> No HTTP based URL but you could use the JMX capabilities of the locator to 
> figure out the server states.
> 
> 
> This message is confidential and subject to terms at: 
> http://www.jpmorgan.com/emaildisclaimer including on confidentiality, legal 
> privilege, viruses and monitoring of electronic messages. If you are not the 
> intended recipient, please delete this message and notify the sender 
> immediately. Any unauthorized use is strictly prohibited.
> 
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer 
> <https://www.amdocs.com/about/email-disclaimer>
> 
> 
> This message is confidential and subject to terms at: 
> http://www.jpmorgan.com/emaildisclaimer including on confidentiality, legal 
> privilege, viruses and monitoring of electronic messages. If you are not the 
> intended recipient, please delete this message and notify the sender 
> immediately. Any unauthorized use is strictly prohibited.
> 

Reply via email to