Hi,
I have deleted the logs for I want to do more test to make sure whether it's
a issue.
I run Ignite ver. 1.5.0-b1 with modified configuration , and now it have
run smoothly for about one month.
So I think it should be the TcpDiscoverySpi configuration problem.
The current configuration is :
<property name="discoverySpi">
<bean
class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
<property name="joinTimeout" value="0"/>
<property name="ackTimeout" value="1000"/>
<property name="socketTimeout" value="2000"/>
<property name="networkTimeout" value="30000"/>
<property name="reconnectCount" value="500"/>
<property name="heartbeatFrequency" value="2000"/>
<property name="maxMissedHeartbeats" value="5"/>
<property name="ipFinder">
<bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
<property name="addresses">
<list>
<value>10.1.XXXX:47500</value>
<value>10.1.YYYY:47500</value>
<value>10.1.ZZZZ:47500</value>
</list>
</property>
</bean>
</property>
</bean>
</property>
Do you have any suggestions for best practices?
Thanks a lot.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Grid-stopped-with-IgniteCheckedException-Failed-to-deserialize-object-with-given-class-loader-sun-mir-tp2123p2369.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
