D
dbeavon
Guest
I think the errors were because of the cruft in the opendge.properties file that still referenced the oepas1 application. I had to clean those references to "oepas1". Its too bad that wasn't cleared out for me when I undeployed the "oepas1" ABL application in the OEE management console. After I manually cleaned up the openedge.properties file , then the errors went away. You may not care about the oemanager errors at all. That would assume you are trying to use the "oemanager" webapp (or OEE). I would guess that tomcat doesn't care one way or another if that particular ABL application ("oepas1") is working or not working (or missing). Also, I should point out that I haven't had any trouble yet after removing the "oepas1" application ... but it has only been an hour. I'm not sure if that ABL application serves any real purpose or not. I did notice that it is the ABL application which is associated with the ROOT webapp ("/") so that URI path will not be available anymore (whatever purpose it might serve in the first place).
Continue reading...
Continue reading...