[teiid-issues] [JBoss JIRA] (TEIID-5887) Issues with marhaller registration

[Ramesh Reddy (Jira)]

    [ https://issues.redhat.com/browse/TEIID-5887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956678#comment-13956678 ] 

Ramesh Reddy commented on TEIID-5887:
-------------------------------------

Looks good. We can make a request for Object level marshaling, but the initial one also took some time after I did above then a couple versions later they came with their own api.

> Issues with marhaller registration
> ----------------------------------
>
>                 Key: TEIID-5887
>                 URL: https://issues.redhat.com/browse/TEIID-5887
>             Project: Teiid
>          Issue Type: Bug
>          Components: Infinispan
>            Reporter: Steven Hawkins
>            Priority: Major
>             Fix For: 13.1
>
>   Original Estimate: 6 hours
>  Remaining Estimate: 6 hours
>
> Adding transactional logic to infinispan highlights several problems with marshaller registration.  The first is that all connections are working off of a shared context and each registering a marshaller for the same class type - this is not thread safe.
> The other issue specific to transactions is that some operations are delayed or redone at commit time - which is called after the connection is closed potentially in a different thread and thus the marshaller provider has been removed.  Given the interplay of threads using a thread local won't work.
> Potentially a transaction aware thread pool or the use of something like our execution context keep alive may be needed.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)