D
dbeavon
Guest
I'd love to clean up my logs in PASOE. Whenever I look at them to troubleshoot a problem, I see errors that shouldn't be there, and are misleading because they are not real errors (based on my experience). 13:44:52.255/25 [localhost-startStop-1] WARN c.p.a.s.s.OESpringPropertySource - Could not resolve openedge.properties ABL application name for web application: oepas1 13:44:52.448/218 [localhost-startStop-1] WARN c.p.a.s.security.OEMetadataSource - restOEMetadataSource: Resolving intercept-url source file using a CATALINA_BASE/webapps file path 13:44:52.450/220 [localhost-startStop-1] WARN c.p.a.s.security.OEMetadataSource - webOEMetadataSource: Resolving intercept-url source file using a CATALINA_BASE/webapps file path 13:44:52.452/222 [localhost-startStop-1] WARN c.p.a.s.security.OEMetadataSource - apsvOEMetadataSource: Resolving intercept-url source file using a CATALINA_BASE/webapps file path 13:44:52.453/223 [localhost-startStop-1] WARN c.p.a.s.security.OEMetadataSource - soapOEMetadataSource: Resolving intercept-url source file using a CATALINA_BASE/webapps file path 13:44:52.454/224 [localhost-startStop-1] WARN c.p.a.s.security.OEMetadataSource - defaultOEMetadataSource: Resolving intercept-url source file using a CATALINA_BASE/webapps file path 13:44:52.524/294 [localhost-startStop-1] ERROR c.p.a.s.s.OESTSUserDetailsImpl - Error opening/reading CATALINA_PID file: java.io.FileNotFoundException: C:\OpenEdge\WRK\oepas1\logs\catalina-oepas1.pid (The process cannot access the file because it is being used by another process) 13:44:52.527/5860 [localhost-startStop-1] WARN c.p.appserv.adapters.rest.Management - Property file C:\OpenEdge\WRK\oepas1\webapps\myappserver/WEB-INF/adapters/rest/_oepingService/runtime.props not found - Using default properties 13:44:52.529/299 [localhost-startStop-1] WARN com.progress.caf.logging.CafLogging - Unable to create InputStream for resource "caflogging.properties". 13:44:52.638/5971 [localhost-startStop-1] WARN o.a.c.m.DefaultManagementLifecycleStrategy - This CamelContext(camel) will be registered using the name: camel-4 due to clash with an existing name already registered in MBeanServer. 13:44:52.686/6019 [localhost-startStop-1] WARN com.progress.appserv.Prop - Development Server is limited to 1 agent 13:44:52.686/6019 [localhost-startStop-1] WARN com.progress.appserv.Prop - Development Server is limited to 5 concurrent requests 13:44:52.686/6019 [localhost-startStop-1] WARN c.p.appserv.IdleResourceWatchdog - Idle resource watchdog enabled - idleResourceTimeout= 10000 ms I suppose I should be ignoring most of this, since it is WARN messages. Let me know if any of the WARN messages are significant. The one that I'd especially like to clean up is this : Error opening/reading CATALINA_PID file: java.io.FileNotFoundException: C:\OpenEdge\WRK\oepas1\logs\catalina-oepas1.pid (The process cannot access the file because it is being used by another process) The error makes it sound like another instance of tomcat is running. That is not the case, since oepas1 is the only instance, and it was not previously running. I get the same error message in the session manager log file of every ABL application that is hosted within oepas1. The instance is set up to run as a Windows service and I get the error whether I start from the service controller (eg. net start) or via OEE ("start as windows service" button). I'm running OE 11.7.2 on Windows. Any tips would be appreciated.
Continue reading...
Continue reading...