[ 
https://issues.apache.org/jira/browse/GEODE-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jinmei Liao updated GEODE-5000:
-------------------------------
    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.
{noformat}
[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){noformat}

> When initializing a client cache, we don't need to request/apply cluster 
> configuration
> --------------------------------------------------------------------------------------
>
>                 Key: GEODE-5000
>                 URL: https://issues.apache.org/jira/browse/GEODE-5000
>             Project: Geode
>          Issue Type: Bug
>          Components: configuration
>    Affects Versions: 1.4.0
>            Reporter: Jinmei Liao
>            Assignee: Jinmei Liao
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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.
> {noformat}
> [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){noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to