geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emily Yeh (JIRA)" <>
Subject [jira] [Created] (GEODE-3033) NPE when jarFileNames is null in ClusterConfigurationLoader
Date Mon, 05 Jun 2017 21:17:04 GMT
Emily Yeh created GEODE-3033:

             Summary: NPE when jarFileNames is null in ClusterConfigurationLoader
                 Key: GEODE-3033
             Project: Geode
          Issue Type: Bug
          Components: gfsh
            Reporter: Emily Yeh

(Copied from original email by Barry Oglesby)

I got this NPE attempting to roll from 9.0.4 to develop (starting a develop server using a
9.0.4 locator):

Exception in thread "main" java.lang.NullPointerException
	at org.apache.geode.internal.cache.ClusterConfigurationLoader.deployJarsReceivedFromClusterConfiguration(
	at org.apache.geode.internal.cache.GemFireCacheImpl.deployJarsReceivedFromClusterConfiguration(
	at org.apache.geode.internal.cache.GemFireCacheImpl.initialize(
	at org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(
	at org.apache.geode.internal.cache.GemFireCacheImpl.create(
	at org.apache.geode.cache.CacheFactory.create(
In this case, jarFileNames is null, so this line fails:"Got response with jars: {}", Stream.of(jarFileNames).collect(joining(",")));

Moving the logger message inside the null checks fixes the issue:

if (jarFileNames != null && jarBytes != null) {"Got response with jars: {}", Stream.of(jarFileNames).collect(joining(",")));

This message was sent by Atlassian JIRA

View raw message