Release Notes - shoal - Version milestone 1 - HTML format

Bug

  • [SHOAL-1] - Possible to request same group for different server IDs in same JVM
  • [SHOAL-2] - New module create for existing group depending on module creation order
  • [SHOAL-4] - GMS SPI does not expose Send to more than one member
  • [SHOAL-6] - GroupHandle needs to expose API to sendMessage to more than one member
  • [SHOAL-7] - DistributedStateCacheImpl should not send messages to members individually
  • [SHOAL-10] - stack trace during appserver shutdown
  • [SHOAL-11] - GMS doesn't see nodes via GroupHandle that have been started later
  • [SHOAL-12] - Startup time needs improvement
  • [SHOAL-13] - MasterNode not notifying add event to own listeners when responding with MasterNodeResponse
  • [SHOAL-14] - MasterNode treats both master announcement and master response with the same message type
  • [SHOAL-15] - MasterNode sends unnecessary ADD_EVENT notifs to its listeners
  • [SHOAL-16] - Fix FindBugs issues raised in HealthMessage and NetworkManager
  • [SHOAL-17] - Shoal Does not provide ability to set configuration properties
  • [SHOAL-18] - Request from JOnAS : Make app messages visible to senders
  • [SHOAL-21] - When MasterNode is killed, then other surviving member does not assume master role
  • [SHOAL-23] - Occassional NPE see in DistribuedStateCache sync()
  • [SHOAL-24] - Incorrect handling of Master Change Events in ViewWindow
  • [SHOAL-25] - NPE from net.jxta.impl.pipe.BlockingWireOutputPipe.checkMessenger
  • [SHOAL-26] - Threads don't shutdown
  • [SHOAL-27] - java.lang.IllegalStateException is thrown with default config
  • [SHOAL-30] - Health Monitor's getState returns state of members as DEAD if health messages have not yet started
  • [SHOAL-31] - Health Monitor's reportJoinedAndReadyState doesnt send local cluster view event in master node
  • [SHOAL-34] - Join notif states different for master and other members
  • [SHOAL-36] - messages received not in same order as when sent
  • [SHOAL-38] - HealthMonitoring support for hardware/network failures avoiding TCP timeouts
  • [SHOAL-40] - (User Feedback) : provide ability to choose network interface on which to have group communication
  • [SHOAL-42] - masterNode.getRouteControl().isConnected returns false intermittently or all the time
  • [SHOAL-43] - unable to create messenger exception from JXTA
  • [SHOAL-45] - MessageWindow NullPointerException handling GMSMessage
  • [SHOAL-46] - .shoal directory size increases dangerously
  • [SHOAL-47] - Gracefully shutdown does not work, but also creates sideeffects
  • [SHOAL-48] - Gracefully shutdown does not work, but also creates sideeffects
  • [SHOAL-51] - signal.getMemberDetails().get(WAITTIMEBEFORESTARTINGRECOVERY))) returns null
  • [SHOAL-52] - NPE in LWRMulticast.pipeMsgEvent
  • [SHOAL-53] - MSG LOSS: MISSING Failure Events in GMS/glassfish
  • [SHOAL-54] - gms.getGroupHandle().getGroupLeader() throws NullPointerException
  • [SHOAL-55] - more reliable failure notification
  • [SHOAL-58] - One instance was killed, other instances were not properly notified about that event.
  • [SHOAL-59] - when the node fails, the node details don't get removed from DSC.
  • [SHOAL-60] - when new member joins existing group, this member can't receive join notifications of others that already joined
  • [SHOAL-61] - when members join the group concurrently, join notifications of some members are often duplicated or missed
  • [SHOAL-62] - sometimes, sending messages to a member failed though the member is still alive.
  • [SHOAL-63] - When I invoke GMSFactory.startGMSModule(...), some NPEs are occurred
  • [SHOAL-66] - Join Notification Signals of own join is not notified
  • [SHOAL-67] - NPE seen in ClusterManager Line 161 while executing Shoal Sample

Improvement

  • [SHOAL-3] - GMS SPI does not expose receive capability
  • [SHOAL-5] - GMS SPI should use more that a String to identify members
  • [SHOAL-8] - Add a client API to expose Group's leader
  • [SHOAL-9] - Need Shoal User Guide
  • [SHOAL-37] - expose API to determine if group is shutting down
  • [SHOAL-39] - HealthMonitor should report if the Network Interface of the local peer is down
  • [SHOAL-41] - Add support in Shoal for passing in cert stores
  • [SHOAL-44] - accessing JXTA's System ADV information or equivalent
  • [SHOAL-49] - Provide a converse to JoinedAndReady when consuming app did not get ready
  • [SHOAL-50] - Expose MASTER_CHANGE_EVENT
  • [SHOAL-56] - Document Configuration Settings Available to users

New Feature

  • [SHOAL-28] - Add support for multicluster support
  • [SHOAL-29] - API to Signal to group that each member's application is ready to start operations
  • [SHOAL-57] - Provide a JMX MBean to list and configure configuration settings

Task

  • [SHOAL-19] - Publish JavaDoc of the APIs
  • [SHOAL-20] - Document ".shoal" directory
  • [SHOAL-22] - HealthMonitor refactoring to improve node state maintenance and detection
  • [SHOAL-32] - test for getCurrentAliveOrReadyMembers
  • [SHOAL-33] - test for DSCMessage
  • [SHOAL-35] - member state shld not returned as DEAD for a member not in view
  • [SHOAL-64] - add AtomicBoolean for controlling the started variable
  • [SHOAL-65] - add cluster name to HealthMonitor thread descriptions and log messages

Edit/Copy Release Notes

The text area below allows the project release notes to be edited and copied to another document.