Hi Mateusz,
1. It seems that distributed cache is still *not* available in
PRIVATE/ISOLATED modes. Is this correct?
Right, it hasn't been fixed yet. I've just followed up the related
discussion on the dev list. Please follow it to see the most up-to-date
information
http://apache-ignite-developers.2346864.n4.nabble.com/Fwd-Distributed-queue-problem-with-peerClassLoading-enabled-tp4521p6440.html
2. When I run my simple test code in the default SHARED mode (the same as
specified in https://issues.apache.org/jira/browse/IGNITE-1823 jira issue),
I still get an error. However the cause exception seems to be different.
Please see attached server log.
The reason is that there is an attempt to deserialize a binary object
stored on a server node and the server node doesn't have object's class
definition in its class path.
I've opened a ticket
https://issues.apache.org/jira/browse/IGNITE-2339
As a workaround you can put a class definition on server's class path
and the problem will disappear.
Regards,
Denis
On 1/7/2016 1:30 PM, mjjp wrote:
Hello,
I have just downloaded 1.5.0-final to check if my problem has been resolved.
Either I'm doing something wrong, or version 1.5 has the same behavior in
this context:
1. It seems that distributed cache is still *not* available in
PRIVATE/ISOLATED modes. Is this correct?
2. When I run my simple test code in the default SHARED mode (the same as
specified in https://issues.apache.org/jira/browse/IGNITE-1823 jira issue),
I still get an error. However the cause exception seems to be different.
Please see attached server log.
Would you be able to check the attached log to verify if this is an expected
behavior in 1.5?
Cheers,
-Mateusz
ignite-fd14d572.log
<http://apache-ignite-users.70518.x6.nabble.com/file/n2416/ignite-fd14d572.log>
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-queue-problem-with-peerClassLoading-enabled-tp1762p2416.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
