I see the below set of logs being printed continuously with the new
Hazelcast jar on one of the *Manager* nodes.
TID: [0] [AS] [2013-08-27 12:38:46,641] INFO
{com.hazelcast.partition.PartitionService} - [192.168.18.3]:4500
[as.qa.420.domain] Initializing cluster partition table first
Shall we try upgrading to Hazelcast 3.0?
On Sun, Aug 25, 2013 at 10:08 AM, Sameera Jayasoma same...@wso2.com wrote:
Hi Azeez,
We've seen this error time to time. We saw this error yesterday as well.
We had to restart the server to get rid of it. Please let us know if you
have a clue here.
We are testing with Hazelcast 3.0 right now. The following articles
highlight the improvements in Hazelcast 3.0.
See:
http://blog.hazelcast.com/blog/2013/06/03/whats-new-in-hazelcast3/
and
Hi Azeez,
We've seen this error time to time. We saw this error yesterday as well. We
had to restart the server to get rid of it. Please let us know if you have
a clue here.
https://wso2.org/jira/browse/CARBON-14287
Thanks,
Sameera.
--
Sameera Jayasoma,
Architect,
WSO2, Inc.
