Atomic Transaction Between Web Services (WS-AT and WS-COOR) Fails On GlassFish Server 3.1.2
Last updated on APRIL 04, 2017
Applies to:Oracle GlassFish Server - Version 3.1.2 and later
Information in this document applies to any platform.
When using the transactionality feature between Web Services (ws-at and ws-coor protocols) published in Glassfish, it works in GlassFish version 2.1.1, but it does not work in version 3.1.2.
• A client application (Java servlet), that creates a global transaction and invokes a web service that creates a register in an Oracle database and returns the id just created for the client application.
• After that the same client application invokes a second web service in the same transactional context using the id of the record created in the first web service to make a query of that record.
In the GlassFish Server version 2.1.1, the Web Service finds the record, but in GlassFish Server 3.1.2 it doesn't find it.
The web services were developed with:
• Java 1.7
• Session EJB Stateless with a CMT EntityManager with Hibernate 4, to make the query and to persist the record.
• The session EJB was published like a Web Service using the annotations for implementing the ws-at.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms