ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vkulichenko <valentin.kuliche...@gmail.com>
Subject Re: Cache put operation blocked in cluster
Date Fri, 14 Aug 2015 01:26:53 GMT
Yes, this is a known issue. This is happening because when listener is
registered on a stable topology, it's marshalled with OptimizedMarshaller.
If its requireSerializable flag is false and peer-deployment is switched on,
ActiveMQ entities will not cause any exception. When a new node joins, on
the other hand, the same listener is sent as a part of discovery message.
Discovery uses plain JDK marshalling, which always requires Serializable
interface and can't peer-deploy classes.

I would recommend to do the following:
- Make all required classes available on all nodes.
- Set requireSerializable to true (unless it's really required). This will
give you more control on what is serialized in your application.
- Make ActiveMQ entities transient and initialize them lazily (as Dmitry
suggested).

Hope this helps.

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cache-put-operation-blocked-in-cluster-tp955p974.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message