このコンテンツは選択した言語では利用できません。
Chapter 3. Resolved Issues
The following issues have been resolved in JBoss Data Grid 6.0.1.
- BZ#810155 - Default configuration may not be optimal for a 2-node cluster
- A sample configuration is now included in the JBoss Data Grid Server distribution called docs/examples/configs/standalone-two-nodes.xml, which provides better performance when using clusters formed by only two nodes. This configuration changes the default JGroups configuration to use the UNICAST protocol instead of the UNICAST2 and RSVP combination of protocols. For larger clusters the UNICAST2 and RSVP combination is recommended.
- BZ#841887 - Transactional listeners method order problem
- In JBoss Data Grid 6.0.0 listeners on remote nodes would be invoked in a different order compared the originator node. This has now been resolved and remote nodes will invoke listeners in the same, correct order as on the originator nodes.
- BZ#841888 - Make connection refused exceptions TRACE
- In JBoss Data Grid 6.0.0 the HotRod connection pooling check for idle connections would log spurious WARN messages about not being able to create a connection. These messages are now logged at the TRACE level since they are harmless and can safely be ignored.
- BZ#841890 - Duplicate counts for some stats
- In JBoss Data Grid 6.0.0 some statistics were counted twice. This has now been corrected and all statistics are counted once as expected.
- BZ#841892 - ping_on_startup ignored
- In JBoss Data Grid 6.0.0 the HotRod client option infinispan.client.hotrod.ping_on_startup was ignored and the client pinged the servers on start up. This is now resolved and the client's behavior is in accordance with the infinispan.client.hotrod.ping_on_startup option.
- BZ#841893 - Ping should try all servers in server list.
- In JBoss Data Grid 6.0.0 HotRod clients attempting to retrieve topology information using the protocol's PING message from a non-functional server would fail immediately without retrying. This issue has been resolved and the clients will retry the failed PING operation.
- BZ#841896 - JDBC cache store should quote generated table name
- In JBoss Data Grid 6.0.0 the JDBC cache store would not enclose generated table names within quotes, which caused problems when attempting to use special characters. This has now been resolved, and table names are quoted.
- BZ#846729 - Some DefaultCacheManager constructors still performing legacy configuration adaptation
- In JBoss Data Grid 6.0.0 some of the org.infinispan.manager.DefaultCacheManager constructors using the org.infinispan.configuration API would invoke the adapter to convert configuration to the legacy org.infinispan.config API. This would cause some properties, such as a user-specified classloader, to be lost. This has now been resolved and the legacy adapter is no longer invoked in these situations.
- BZ#846731 - AtomicHashMapProxy calls Cache.getCacheConfiguration() triggering legacy config adaptation.
- In JBoss Data Grid 6.0.0 the AtomicHashMapProxy class would trigger an invocation to the legacy configuration adapter causing performance degradation and a spurious INFO log message. This is now resolved.
- BZ#847711 - Cache view installation takes too long
- When the coordinator shuts down, it tries to install a new cache view that does not include itself. Because there are multiple nodes shutting down at the same time, two or more nodes can see themselves as the coordinator and will try to install conflicting views, failing and repeating the process for a very long time. This is now resolved by automatically rejecting outside cache views installation requests on the current JGroups coordinator. This way each one of the "coordinators" can shut down without interfering with the others.
- BZ#854662 - Upgrade to JGroups 3.0.13.Final
- The version of JGroups bundled with JBoss Data Grid 6.0.1 is upgraded to 3.0.13.Final which provides bug fixes and performance improvements.
