Bugs Fixed in GemFire 6.6.3

Last updated: 06/13/2012

Ticket Created Title Description Workaround for earlier gemfire versions
#43705 07/19/11 The CPU usage for the JMX agent can be high In certain situations, the JMX Agent uses too much CPU for a sustained period of time when GFMon is connected to it. The workaround is to set the JMX Agent's refreshInterval to 60 seconds and GFMon's Refresh Interval to 60000 ms. This will cause periods of JMX Agent inactivity followed by a period of CPU usage rather than constant high CPU usage.
#44740 03/23/12 Enum serialization broken In some cases enum deserialization does not read enough data corrupting the input stream. This can cause various IOExceptions during deserialization. Set the system property -Dgemfire.serializationVersion=6.6.0
#44914 04/17/12 PDX must use the DEFAULT disk store if keys are PDX-enabled and persistent If PDX is configured with a disk store name then startup may fail with a PdxInitializationException exception. Do not specify a disk-store name. Instead just set persistent to true and use the default disk store. If you want to configure the default disk store you can by using the name "DEFAULT".
#44924 04/18/12 JMX Agent didn't read configuration in gfsecurity.properties JMX Agent now reads the SSL configuration from gfsecurity.properties Specify the ssl/security configuration as system properties while starting the JMX Agent.
#44925 04/18/12 Occasional deadlock between agent and cache servers A deadlock was observed occasionally between agent and cache servers when starting many servers simultaneously. This issue has been addressed.
#44927 04/18/12 Gfsh consumed one client license per server region In prior versions, gfsh consumed one client license per server region. It created a pool (which corresponded to a client license on the server) per region. This is a problem for customers with limited client licenses.
#44989 05/01/12 Repeatedly opening and closing a cache from xml containing a cache server caused memory leak In prior versions, repeatedly opening and closing a cache from xml containing a cache server caused memory leak of cache instances.
#44992 05/02/12 Repeatedly opening and closing a cache containing a gateway hub caused a memory leak In prior versions, repeatedly opening and closing a cache containing a gateway hub caused a memory leak of cache instances.
#44997 05/04/12 Client security artifacts are not updated when exceptions occur during client authentication When client security is enabled and the client gets an exception while processing the server's response during its authentication, the client may not have its security artifacts updated. This could result in the client getting exceptions during subsequent operations performed on that server. The fix ensures that security artifacts are updated during authentication even if the processing of the server's response returns errors.
#45005 05/08/12 Using a distributed-member-id greater than 127 will cause PDX serialization to fail If the distributed-system-id is greater than 127, then PDX serialization will be corrupted. This will cause an IllegalArgumentException during PDX deserialization. Use a distributed-system-id less than or equal to 127.