Task #4101
Story #3882: Refactor hzNodes out of CN Node Registry
Hazelcast Client should use the ConfigBuilder of hazelcast
Start date:
2013-10-17
Due date:
% Done:
0%
Milestone:
CCI-1.4
Product Version:
*
Story Points:
Sprint:
Description
To make the client more robust, use the properties file to populate ConfigBuilder.
Also apply more logic to handle when the client is not longer active. Restart does not work, so a new client with the old config will need to be created.
Need to make certain the same approach will work in ReserveIdentifier Service as the Rest Service and d1 processing
History
#1 Updated by Robert Waltz over 10 years ago
- Milestone changed from None to CCI-1.2
- Product Version changed from * to 1.2.0
#2 Updated by Robert Waltz over 10 years ago
- Category set to d1_cn_common
#3 Updated by Robert Waltz over 10 years ago
- Target version changed from 2013.33-Block.4.4 to 2013.46-Block.6.2
#4 Updated by Chris Jones over 10 years ago
- Target version changed from 2013.46-Block.6.2 to 2014.8-Block.1.4
#5 Updated by Robert Waltz over 10 years ago
- Target version changed from 2014.8-Block.1.4 to 2014.6-Block.1.3
#6 Updated by Robert Waltz over 10 years ago
- Target version changed from 2014.6-Block.1.3 to 2014.14-Block.2.3
#7 Updated by Robert Waltz about 10 years ago
- Target version changed from 2014.14-Block.2.3 to 2014.28-Block.4.2
#8 Updated by Robert Waltz almost 10 years ago
- Target version deleted (
2014.28-Block.4.2)
#9 Updated by Robert Waltz almost 10 years ago
- Product Version changed from 1.2.0 to *
- Milestone changed from CCI-1.2 to CCI-1.4
#10 Updated by Robert Waltz over 9 years ago
- Target version set to Maintenance Backlog
#11 Updated by Robert Waltz over 9 years ago
- Target version changed from Maintenance Backlog to Release Backlog
#12 Updated by Robert Waltz over 9 years ago
- Target version changed from Release Backlog to CCI-2.1.0
#13 Updated by Robert Waltz over 8 years ago
- translation missing: en.field_remaining_hours set to 0.0
- Status changed from New to Rejected
