[OLINGO-976] Problem with JTA transactions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: V2 2.0.7
• Fix Version/s: V2 2.0.7
• Component/s: odata2-jpa
• Environment: neo-javaee6-wp-sdk (SAP HANA cloud)
• Assignee: mibo
• Reporter: Alex Key
• Created: 28/Jun/16 13:20
• Updated: 11/Sep/16 17:57
• Resolved: 17/Aug/16 11:55

Description

There are still problems with JTA transaction after fixing OLINGO-882.

At the moment IllegalStateException is thrown by ODataJPATransactionLocalDefault constructor, which has em.getTransaction() call.
Here's stacktrace:

java.lang.IllegalStateException: A JTA EntityManager can not use the EntityTransaction API.  See JPA 1.0 section 5.5
	at org.apache.openejb.persistence.JtaEntityManager.getTransaction(JtaEntityManager.java:349)
	at org.apache.olingo.odata2.jpa.processor.core.ODataJPATransactionLocalDefault.<init>(ODataJPATransactionLocalDefault.java:31)
	at org.apache.olingo.odata2.jpa.processor.core.ODataJPAContextImpl.getODataJPATransaction(ODataJPAContextImpl.java:178)
	at org.apache.olingo.odata2.jpa.processor.core.access.data.JPAProcessorImpl.setTransaction(JPAProcessorImpl.java:451)
	at org.apache.olingo.odata2.jpa.processor.core.access.data.JPAProcessorImpl.processCreate(JPAProcessorImpl.java:335)
	at org.apache.olingo.odata2.jpa.processor.core.access.data.JPAProcessorImpl.process(JPAProcessorImpl.java:223)
	at org.apache.olingo.odata2.jpa.processor.core.ODataJPAProcessorDefault.createEntity(ODataJPAProcessorDefault.java:122)
	at org.apache.olingo.odata2.core.Dispatcher.dispatch(Dispatcher.java:79)
	at org.apache.olingo.odata2.core.ODataRequestHandler.handle(ODataRequestHandler.java:130)
	at org.apache.olingo.odata2.core.rest.ODataSubLocator.handle(ODataSubLocator.java:164)
	at org.apache.olingo.odata2.core.rest.ODataSubLocator.handlePost(ODataSubLocator.java:86)

Issue Links

• is related to: OLINGO-971 Issue with Container Managed Persistence in Olingo library V2.0
• is related to: OLINGO-882 Olingo closes EntityManager which is managed by the application server