[infinispan-issues] [JBoss JIRA] (ISPN-8814) Remote server tasks still expect GenericJBossMarshaller

[ https://issues.jboss.org/browse/ISPN-8814?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8814: ----------------------------------- Description: When executing tasks, parameters and return types are expected to be marshalled with GenericJBossMarshaller. If not, you get all exceptions such as: {code} Exception in thread "main" org.infinispan.client.hotrod.exceptions.HotRodClientException: Request for messageId=3 returned server error (status=0x85): java.io.IOException: Unsupported protocol version 100 {code} Example can be found [here|https://gist.github.com/galderz/68302021bd9e957fb0164c1bdd362c3f]. was: When executing tasks, parameters and return types are expected to be marshalled with GenericJBossMarshaller. If not, you get all exceptions such as: {code} Exception in thread "main" org.infinispan.client.hotrod.exceptions.HotRodClientException: Request for messageId=3 returned server error (status=0x85): java.io.IOException: Unsupported protocol version 100 {code} Example can be found [here|https://gist.github.com/galderz/68302021bd9e957fb0164c1bdd362c3f]. A workaround is to have separate RemoteCache instances, built with different configuration used for data versus task execution, [example|https://gist.github.com/galderz/d1cc02d520352a6af036ed0fc677e208]. Workaround Description: Have separate RemoteCache instances, built with different configuration used for data versus task execution, [example|https://gist.github.com/galderz/d1cc02d520352a6af036ed0fc677e208]. This is clunky though. Workaround: Workaround Exists -- This message was sent by Atlassian JIRA (v7.5.0#75005)