PE 5.3 m110 and Dynamic Link Manager and FOSI changes not getting picked up

[naglists]

Hi,
Am working on an 5.3 m110 environment. I am noticing different PE behavior
regarding FOSI changes.

I used to be able to make changes to FOSI (in 5.1 and 5.2 environments) and
subsequent composition requests picked up the new file. This is not
happening in 5.3 m110. I've tried running the "Reload Subprocesses" or
f=init URL but that actually kills the PE session. Subsequent composition
requests return 500 server errors. A Tomcat restart restores normal behavior
if (I'm not 100% sure about this "if" part yet) if I also stop/start Editor.
If I don't close/open Editor, I think the PE session is re-killed by
something in the Editor / PE conversation.

Anyone else experiencing this? Figured a way around it?

We are using DLM if that matters ...

--
Paul Nagai

[ptc-953926]

We've been using PE 5.3 for a long time and we've always had to stop and restart Tomcat to get FOSI changes recognized. PE seems to keep loaded the last however many FOSIs it's used and isn't cognizant of changes.

Dave

[naglists]

Hi Dave,
Funny thing ... I think we've talked about it here before ... Do you have
any success with the f=init subprocesses reload?

[ptc-953926]

Paul,

Unfortunately, I'm not the one who set up the PE server and maintains it. I just maintain the FOSIs. I'll ask him and get back to you.

Dave