[GEODE-5000] When initializing a client cache, we don't need to request/apply cluster configuration

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 1.6.0
• Component/s: configuration
• Labels: pull-request-available
• Assignee: Jinmei Liao
• Reporter: Jinmei Liao
• Created: 04/Apr/18 22:23
• Updated: 14/Jun/18 17:31
• Resolved: 17/Apr/18 16:02

Description

The user running a gemfire client doesn't have write access to the local dirs in the customer environment, and they get an stack trace in their logs. This is caused by a client cache trying to request/apply cluster configuration.

[error 2018/02/12 17:52:13.899 EST <localhost-startStop-1> tid=0x12] Error when attempting to deploy JAR files on load.
java.io.IOException: Unable to write to deploy directory
at org.apache.geode.internal.JarDeployer.verifyWritableDeployDirectory(JarDeployer.java:626)
at org.apache.geode.internal.JarDeployer.loadPreviouslyDeployedJars(JarDeployer.java:74)
at org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1242)
at org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:794)
at org.apache.geode.internal.cache.GemFireCacheImpl.createClient(GemFireCacheImpl.java:767)
at org.apache.geode.cache.client.ClientCacheFactory.basicCreate(ClientCacheFactory.java:257)
at org.apache.geode.cache.client.ClientCacheFactory.create(ClientCacheFactory.java:207)

Issue Links

• links to: GitHub Pull Request #1739
• links to: GitHub Pull Request #1763