[ https://issues.jboss.org/browse/TEIID-5449?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5449: ------------------------------------- [~rhn-engineering-vhalbert] As I mentioned above the Infinispan context where you registered marshaller is at global scope of all the connections in the pool, so registering a marshaller at that level will either overwrite or conflict with additional concurrent queries with the same name in the cache. This can lead to wrong results or errors in load. So, above commit is not sufficient. Either we need to * Create a new cache manager for each connection (very heavyweight, recommendation is to create one per VM) * Need to come with some way to non-conflict marshaller names based on connection * Ability to register marshallers at a different scope level in Infinispan API. The second bullet point will be my suggestion to implement. -- This message was sent by Atlassian Jira (v7.12.1#712002)