Hi Anthony, Yes I have spring-shell in classpath. Here is the full server classpath.
C:\eclipse\workspaces\development\myapp\target\classes C:\maven\repo\org\springframework\boot\spring-boot-starter\1.5.1.RELEASE\spring-boot-starter-1.5.1.RELEASE.jar C:\maven\repo\org\springframework\boot\spring-boot\1.5.1.RELEASE\spring-boot-1.5.1.RELEASE.jar C:\maven\repo\org\springframework\spring-context\4.3.6.RELEASE\spring-context-4.3.6.RELEASE.jar C:\maven\repo\org\springframework\boot\spring-boot-autoconfigure\1.5.1.RELEASE\spring-boot-autoconfigure-1.5.1.RELEASE.jar C:\maven\repo\org\springframework\boot\spring-boot-starter-logging\1.5.1.RELEASE\spring-boot-starter-logging-1.5.1.RELEASE.jar C:\maven\repo\ch\qos\logback\logback-classic\1.1.9\logback-classic-1.1.9.jar C:\maven\repo\ch\qos\logback\logback-core\1.1.9\logback-core-1.1.9.jar C:\maven\repo\org\slf4j\jul-to-slf4j\1.7.22\jul-to-slf4j-1.7.22.jar C:\maven\repo\org\slf4j\log4j-over-slf4j\1.7.22\log4j-over-slf4j-1.7.22.jar C:\maven\repo\org\springframework\spring-core\4.3.6.RELEASE\spring-core-4.3.6.RELEASE.jar C:\maven\repo\org\yaml\snakeyaml\1.17\snakeyaml-1.17.jar C:\maven\repo\org\springframework\boot\spring-boot-starter-web\1.5.1.RELEASE\spring-boot-starter-web-1.5.1.RELEASE.jar C:\maven\repo\org\springframework\boot\spring-boot-starter-tomcat\1.5.1.RELEASE\spring-boot-starter-tomcat-1.5.1.RELEASE.jar C:\maven\repo\org\apache\tomcat\embed\tomcat-embed-core\8.5.11\tomcat-embed-core-8.5.11.jar C:\maven\repo\org\apache\tomcat\embed\tomcat-embed-el\8.5.11\tomcat-embed-el-8.5.11.jar C:\maven\repo\org\apache\tomcat\embed\tomcat-embed-websocket\8.5.11\tomcat-embed-websocket-8.5.11.jar C:\maven\repo\org\hibernate\hibernate-validator\5.3.4.Final\hibernate-validator-5.3.4.Final.jar C:\maven\repo\javax\validation\validation-api\1.1.0.Final\validation-api-1.1.0.Final.jar C:\maven\repo\org\jboss\logging\jboss-logging\3.3.0.Final\jboss-logging-3.3.0.Final.jar C:\maven\repo\com\fasterxml\classmate\1.3.3\classmate-1.3.3.jar C:\maven\repo\com\fasterxml\jackson\core\jackson-databind\2.8.6\jackson-databind-2.8.6.jar C:\maven\repo\com\fasterxml\jackson\core\jackson-core\2.8.6\jackson-core-2.8.6.jar C:\maven\repo\org\springframework\spring-web\4.3.6.RELEASE\spring-web-4.3.6.RELEASE.jar C:\maven\repo\org\springframework\spring-aop\4.3.6.RELEASE\spring-aop-4.3.6.RELEASE.jar C:\maven\repo\org\springframework\spring-beans\4.3.6.RELEASE\spring-beans-4.3.6.RELEASE.jar C:\maven\repo\org\springframework\spring-webmvc\4.3.6.RELEASE\spring-webmvc-4.3.6.RELEASE.jar C:\maven\repo\org\springframework\spring-expression\4.3.6.RELEASE\spring-expression-4.3.6.RELEASE.jar C:\maven\repo\org\springframework\boot\spring-boot-starter-actuator\1.5.1.RELEASE\spring-boot-starter-actuator-1.5.1.RELEASE.jar C:\maven\repo\org\springframework\boot\spring-boot-actuator\1.5.1.RELEASE\spring-boot-actuator-1.5.1.RELEASE.jar C:\maven\repo\org\springframework\shell\spring-shell\1.2.0.RELEASE\spring-shell-1.2.0.RELEASE.jar C:\maven\repo\com\google\guava\guava\17.0\guava-17.0.jar C:\maven\repo\jline\jline\2.12\jline-2.12.jar C:\maven\repo\org\springframework\spring-context-support\4.3.6.RELEASE\spring-context-support-4.3.6.RELEASE.jar C:\maven\repo\commons-io\commons-io\2.4\commons-io-2.4.jar C:\maven\repo\org\springframework\data\spring-data-geode\1.0.0.INCUBATING-RELEASE\spring-data-geode-1.0.0.INCUBATING-RELEASE.jar C:\maven\repo\org\springframework\spring-tx\4.3.6.RELEASE\spring-tx-4.3.6.RELEASE.jar C:\maven\repo\org\springframework\data\spring-data-commons\1.13.0.RELEASE\spring-data-commons-1.13.0.RELEASE.jar C:\maven\repo\antlr\antlr\2.7.7\antlr-2.7.7.jar C:\maven\repo\org\aspectj\aspectjweaver\1.8.9\aspectjweaver-1.8.9.jar C:\maven\repo\org\apache\shiro\shiro-spring\1.3.1\shiro-spring-1.3.1.jar C:\maven\repo\org\apache\shiro\shiro-web\1.3.1\shiro-web-1.3.1.jar C:\maven\repo\com\fasterxml\jackson\core\jackson-annotations\2.8.0\jackson-annotations-2.8.0.jar C:\maven\repo\org\slf4j\jcl-over-slf4j\1.7.22\jcl-over-slf4j-1.7.22.jar C:\maven\repo\org\slf4j\slf4j-api\1.7.22\slf4j-api-1.7.22.jar C:\maven\repo\org\apache\geode\geode-core\1.1.1\geode-core-1.1.1.jar C:\maven\repo\com\github\stephenc\findbugs\findbugs-annotations\1.3.9-1\findbugs-annotations-1.3.9-1.jar C:\maven\repo\org\jgroups\jgroups\3.6.10.Final\jgroups-3.6.10.Final.jar C:\maven\repo\commons-lang\commons-lang\2.5\commons-lang-2.5.jar C:\maven\repo\it\unimi\dsi\fastutil\7.0.2\fastutil-7.0.2.jar C:\maven\repo\javax\resource\javax.resource-api\1.7\javax.resource-api-1.7.jar C:\maven\repo\javax\transaction\javax.transaction-api\1.2\javax.transaction-api-1.2.jar C:\maven\repo\net\java\dev\jna\jna\4.2.2\jna-4.2.2.jar C:\maven\repo\net\sf\jopt-simple\jopt-simple\5.0.1\jopt-simple-5.0.1.jar C:\maven\repo\org\apache\logging\log4j\log4j-api\2.7\log4j-api-2.7.jar C:\maven\repo\org\apache\logging\log4j\log4j-core\2.7\log4j-core-2.7.jar C:\maven\repo\org\apache\shiro\shiro-core\1.3.1\shiro-core-1.3.1.jar C:\maven\repo\commons-beanutils\commons-beanutils\1.9.3\commons-beanutils-1.9.3.jar C:\maven\repo\commons-collections\commons-collections\3.2.2\commons-collections-3.2.2.jar C:\maven\repo\org\apache\geode\geode-common\1.1.1\geode-common-1.1.1.jar C:\maven\repo\org\apache\geode\geode-json\1.1.1\geode-json-1.1.1.jar C:\maven\repo\org\apache\geode\geode-cq\1.1.1\geode-cq-1.1.1.jar C:\maven\repo\org\apache\geode\geode-wan\1.1.1\geode-wan-1.1.1.jar Thanks, Dharam -----Original Message----- From: Anthony Baker [mailto:[email protected]] Sent: Wednesday, September 06, 2017 8:04 PM To: [email protected] Subject: Re: Health check URLs for cache server 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. > 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.
