[teiid-issues] [JBoss JIRA] (TEIIDSB-155) Infinispan configuration should support a transactional cache

[Steven Hawkins (Jira)]

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

Steven Hawkins commented on TEIIDSB-155:
----------------------------------------

Running these changes against an infinispan cluster in openshift results in:

{code}
org.infinispan.client.hotrod.exceptions.HotRodClientException: java.lang.SecurityException: ISPN006017: Unauthorized 'PREPARE_TX_2' operation
	at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:337) ~[infinispan-client-hotrod-10.0.1.Final.jar:10.0.1.Final]
	at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:176) ~[infinispan-client-hotrod-10.0.1.Final.jar:10.0.1.Final]
{code}

During the pre-check before creating the remote transactional cache.  This is an infinispan DataGrid created by their operator using either their generated developer or operator accounts.

I'll poke around in the infinispan code before raising an issue on their side.

> Infinispan configuration should support a transactional cache
> -------------------------------------------------------------
>
>                 Key: TEIIDSB-155
>                 URL: https://issues.redhat.com/browse/TEIIDSB-155
>             Project: Teiid Spring Boot
>          Issue Type: Enhancement
>          Components: datasource
>            Reporter: Steven Hawkins
>            Priority: Major
>             Fix For: 1.3.1
>
>
> The configuration should allow for single phase commit and non-recoverable xa.  This will need to change the transaction support on the translator, set the transaction config, and register a transactionManager lookup that can find the configured transaction manager.
> The infinispan operator does not provide a way to configure the transaction support of the cache, so this may not fully work yet - I'll test to see what happens both with the default cache and with trying to create one on demand.



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