[chrisplough]

Jeff,

I've experienced the same issue on BPEL PM 10.1.2.0.2 and EBS 11.5.10.2.

I found that I had to restart the BPEL server regularly when committing changes to the packages in EBS, in order to allow it to re-create the DB connection and obtain the latest package information.

To the root of your question, though -- no, I'm not aware of a way to force BPEL / Fusion to read the data automatically each time and fully avoid these restarts. I was sometimes able to avoid them if I removed the package spec and body, then re-loaded them, instead of just updating; however, it was still somewhat inconsistent.

Later, as you move into environment testing, you'll also find that you'll need to restart BPEL / Fusion each time EBS is restarted in order to re-instantiate the DB connection between BPEL and EBS, since it doesn't appear to re-create automatically.

Thanks,
Chris