[
https://issues.apache.org/jira/browse/GEODE-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-796.
-----------------------------
Resolution: Cannot Reproduce
The description is what would happen if you failed to connect to the Jmx
Manager from GFSH. There's not enough information here to debug any further.
When I follow similar steps of what is reported, it works fine.
> Stand alone Geode Server process did not return query results in gfsh
> ---------------------------------------------------------------------
>
> Key: GEODE-796
> URL: https://issues.apache.org/jira/browse/GEODE-796
> Project: Geode
> Issue Type: Bug
> Components: gfsh
> Reporter: Luke Shannon
>
> I started a single server process with JMX enabled:
> gfsh start server \
> --name=$SERVER_NAME \
> --use-cluster-configuration=false \
> --classpath=$CLASSPATH \
> --server-port=0 \
> --dir=$SERVER_DIR_LOCATION/$SERVER_NAME \
> --J=-Xms1g \
> --J=-Xmx1g \
> --J=-Dgemfire.jmx-manager=true \
> --J=-Dgemfire.jmx-manager-start=true \
> --properties-file=$CONF_DIR/gemfire.properties \
> --spring-xml-location=file:///$CONF_DIR/spring-cache.xml
> I was able to connect to gfsh using the JMX-Manager argument for gfsh
> connect. When I tried to list the members I got a 'null' back in gfsh. For a
> query count(*) on a region, the correct right entry count was returned,
> however select * just returned a 'null'. There were no errors in the server
> logs. When I did the same config, however this time started a locator (and
> referenced it in the server start command) I was able to connect using the
> locator argument of connect. Everything worked as expected this time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
