Hi all,

We are using java client to test some functionality and it seems that we have a 
problem with the client cache.
We started locator and server with SSL enabled.
On the client side also add SSL parameters, create proxy region, put some 
entries and it works.

Properties props = new Properties();

props.setProperty("ssl-enabled-components", "all");

props.setProperty("ssl-keystore", keystorePath);

...

ClientCache clientCache = new 
ClientCacheFactory(props).addPoolLocator("localhost", 10334)
    .set("log-level", "info").create();

...
clientCache.close();

After that we start another test with some other properties.

As we are connecting from non-SSL-enabled client to SSL-enabled locator we 
should get an exception, but didn't.


Properties props = new Properties();

props.setProperty("log-file", "test.log");  // no ssll parameters

...

ClientCache clientCache = new 
ClientCacheFactory(props).addPoolLocator("localhost", 10334)

    .set("log-level", "info").create();

...
clientCache.close();


Despite of that we have in logs that GemFire Properties defined with api has 
only this property changed but it somehow take also the cache from the test 
before.

The same thing happened if we change order of tests execution.



Does anyone know is there a possibility that cache is saved somewhere and if 
yes how to delete it?

How to avoid this issue?


BR,

Mario

Reply via email to