A very simple error message appears against a stalled livecycle process which runs upon a flex form submission. You'd think that the connection to the server was lost.This custom process ("completion") is attempting to write out to the backend database at that time.
However,the "read" process to prepopulate the form already correctly uses the same JNDI connection. And that works. Every time.
The solution was to go into the "completion" process and move around the individual nodes, re-save and deploy again
Why is this - seems to be more problems in ES2 than we bargained for perhaps.