App Engines are only supposed to issue commits after a step or later. I'm currently writing single step peoplecode programs that use CI's.
The way it was programmed, when an error occurred, a rollback was issued.
Well errors were happening but rows were still being saved off to some of the tables.
The culprit was a CI calling an App Engine and that App Engine was completing steps (and therefore calling DB commits).
Just something to look out for.
Subscribe to:
Post Comments (Atom)
Integration broker message going to done with no action
If IB messages are just going straight to done without running the handler, it can be corrected by regenerating the routings on the service ...
-
This annoying message text can be removed by using: error msggettext(&validMessageSet,&validMessageNum,"alt error text"...
-
After creating a brand new App Engine in a dev environment and getting it running successfully in the dev environment, I received the follow...
-
The problem: automatically incrementing a numeric field. The Row ID should show up for each new row as it is created. Peoplesoft likes to us...
No comments:
Post a Comment