Soa rest adapter error

RS69

i have error in my composite , when i try connection api .

Exception [EclipseLink-4011] (Eclipse Persistence Services - 2.6.4.v20160829-44060b6): org.eclipse.persistence.exceptions.DatabaseException

Exception Description: Error preallocating sequence numbers.  The sequence table information is not complete.

Global retry rollback fault thrown.

The current JTA transaction is aborting due to an user rollback fault being thrown. The upstream component should retry in a new JTA transaction upon catching this fault.

This exception was caused by a global retry fault being thrown from downstream component. The user had directed the BPEL engine to roll back the current JTA transaction and retry within new JTA transactions for the specified number of times and retry interval.

There is no action recommended.

Martien van den Akker

Hi,

Since you get "Exception [EclipseLink-4011] (Eclipse Persistence Services - 2.6.4.v20160829-44060b6): org.eclipse.persistence.exceptions.DatabaseException

Exception Description: Error preallocating sequence numbers.  The sequence table information is not complete.", I have the suspicion that it's not the REST adapter but a problem in the API. I think the API is using JPA to do DML to the database, but has a problem because of the sequence table. It might not be populated probably. If I google on the exception I get several cases with this error. For instance: http://eclipse.1072660.n5.nabble.com/ECLIPSELINK-4011-Any-more-information-td1396.html which suggests (in that case) that the sequence table is't properly populated.

But all cases suggest that the API is not properly deployed and/or configured, or has a bug. It hasn't got anything to do with the REST adapter itself.

Kind regards,
Martien

RS69

Hello , Matrien
my composite turned to this api during the day and everything worked, the next day it started to give an error above, but through postman/arc I can still contact and send my data to api

Martien van den Akker

Hi,

It could be that something changed in the mapping. Please check if the message send to the API from the composite is the same as send from Postman.

Compare it thoroughly.

What I'm suggesting is that to me it seems that the error is originating from the API.

By the way,  it's quite  common in the IT area that overnight things seem to stop working. But there should be something that is changed. Sometimes it is that it is changed but only gets effective after a restart.  I mention this not to offend, but seriously to help investigating your problem.

Kind regards,

Martien

RS69

we know about how  works it(no) and often we laugh (weep) ourselves from this, but the problem is not unique, all connections through the rest adapter do not work, but if you use spring, then everything works

RS69

Hi Martien.

Maybe someone was interested or found out where soa writes all the transactions that are created when the composites work, because there should be system tables with such information ???

Martien van den Akker

Hi,

You could take a look here: https://easyteam.fr/oracle-soa-12c-principles-soa-dehydration-stores-useful-sql-queries/  and https://soaarchitecture.wordpress.com/2018/04/02/soa-infra-usefull-everyday-queries-12c/ (see the list of links at the bottom of the first link).

And https://blog.darwin-it.nl/2020/02/get-xml-document-from-soa-infra-table.html  for reading messages from the database.

But the actual BPEL flows are stored in a sort of binary way. So you won't be able to interpret them properly. That is: it would be quite and unsupported.

Kind regards,
Martien