D
dbeavon
Guest
It still seems a bit silly to me that, even in the OE 12 ESAP, there is a message which complains that the PASOE tomcat plugin cannot resolve the PASOE process ID. I assume that the generation of that error message is from code that is actually running within the context of the relevant process ID. Isn't it counter-intuitive that the code would not know its own process ID, and that it would have to go read the devlpas "logs" folder to try and find it (and then fail)? Going forward, if we are going to continue to be faced with this message in PASOE 12 log files, then perhaps we should know what it means. Could it be just an internal bug in PASOE itself? Is it a windows-specific thing or does it also appear in PASOE logs for linux? I have a few theories about the message. My theories are that it is either a windows-specific bug, or a timing-related issue where code is running prematurely, or that the error message has to do with multiple ABL applications being hosted by the same tomcat instance (a feature that seems relatively new and not totally well supported in the OEE U/I or in the PDSOE tooling.)
Continue reading...
Continue reading...