It's correct link to the related thread http://apache-ignite-users.70518.x6.nabble.com/CacheStore-being-serialized-to-client-td1931.html
On Mon, Dec 11, 2017 at 7:31 PM, Nikolai Tikhonov <ntikho...@apache.org> wrote: > Hello! > > Apache Ignite requires that CacheStore classes should be in classpath on > client nodes. Look at thread with the same question: > http://apache-ignite-users.70518.x6.nabble.com/Cache- > store-class-not-found-exception-td18842.html > > > > > On Mon, Dec 11, 2017 at 6:28 PM, Naveen Kumar <naveen.band...@gmail.com> > wrote: > >> Please make sure >> >> class is on the server Ignite's CLASSPATH. OR You can just deploy the >> JAR to $IGNITE_HOME/libs/user direcgtory >> >> This should resolve >> >> On Mon, Dec 11, 2017 at 8:52 PM, Mikael <mikael-arons...@telia.com> >> wrote: >> > Hi! >> > >> > I have a cache in a server node that is using a custom cache store for a >> > JDBC database, when I connect a client node (running inside a >> > Payara/Glassfish web application) to that server node I get a: >> > >> > class org.apache.ignite.IgniteCheckedException: Failed to find class >> with >> > given class loader for unmarshalling (make sure same versions of all >> classes >> > are available on all nodes or enable peer-class-loading) >> > [clsLdr=WebappClassLoader (delegate=true; repositories=WEB-INF/classes/) >> , >> > cls=my_cache_store_class] >> > >> > And sure, that class is not there, but it's a client so the cache >> should not >> > be there either and the cache store will not work in the client because >> > there is no database there, so the question is if I am doing something >> wrong >> > or should it be like that ? do I need to put the class in the client ? >> it >> > will have references to other classes that are not there either so if it >> > tries to unmarshal the cache store in the client it will not be a good >> idea. >> > >> > >> >> >> >> -- >> Thanks & Regards, >> Naveen Bandaru >> > >