Infinispan cache between different war files: unmarshalling error "ModuleNotFoundException"

[olegchir]

I have two servers with two completely different deployments. The only common thing is a single class, that exists on both servers (and both deployed wars)

So I set up jgroups, infinispan over TCP, etc, and everything works, but unmarshalling fails:

ERROR [org.infinispan.transaction.TransactionCoordinator] (default task-2) ISPN000097: Error while processing a prepare in a single-phase transaction: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from server1/ws-container, see cause for remote stack trace

Caused by: org.infinispan.commons.CacheException: Problems invoking command.

Caused by: java.io.InvalidClassException: com.my.shared.classes.MyClass; Module load failed

Caused by: org.jboss.modules.ModuleNotFoundException: deployment.server2.war:main

(server1, server2 - hostnames of servers

server1.war, server2.war - different applications deployed on this servers

ws-container - cache container name, the same on both servers

com.my.shared.classes.MyClass - shared class, the same on both servers)

How can we fix this?

I read about Hibernate regions, but still can't understand how apply this knowledge to bare pojos, not JPA entities.

Also I read about custom marshallers and unmarshallers and digging this direction now. Maybe we can just replace standard marshaller with Gson...

[ctomc]

move shared class into jar that is in static jboss module, not in deployment.

than add dependency to it in your deployment.

do that on both servers, this way class will be in same module on both servers so infinispan will be able to find it.

[olegchir]

Is there any way to keep that class in the original war file?

For example, to keep this "static jboss module" inside this war file?

It's not important how ugly this way may be

For moving into external module, I think that our information security division just reject this way of deployment, because wildfly (and other system things) have to be sacred and untouchable.

We can slightly change standalone.xml, like modifying TCPPING section, but nothing more.

Eg, we have our own web service stack, serialization stack, etc inside the war file, and not using anything provided by wildfly, because we can't tune base platform as we like.

[pferraro]

Why not bundle your WAR files and a JAR containing com.my.shared.classes.MyClass within an EAR?