How to handle error entries during Startup of asg-engine?
book
Article ID: KB0080500
calendar_today
Updated On:
Description
Here are some sample entries seen during startup of the engine:
------------------------
2018 Aug 10 09:55:22:727 GMT +1 ASG_CORE_6683 Error [CatalinaHttpServer_5680-startStop-1] - [root] Aug 10, 2018 9:55:22 AM org.apache.catalina.tribes.membership.McastServiceImpl waitForMembers
INFO: Done sleeping, membership established, start level:4
2018 Aug 10 09:55:22:735 GMT +1 ASG_CORE_6683 Error [CatalinaHttpServer_5680-startStop-1] - [root] Aug 10, 2018 9:55:22 AM org.apache.catalina.tribes.membership.McastServiceImpl waitForMembers
INFO: Sleeping for 1000 milliseconds to establish cluster membership, start level:8
2018 Aug 10 09:55:23:738 GMT +1 ASG_CORE_6683 Error [CatalinaHttpServer_5680-startStop-1] - [root] Aug 10, 2018 9:55:23 AM org.apache.catalina.tribes.membership.McastServiceImpl waitForMembers
INFO: Done sleeping, membership established, start level:8
2018 Aug 10 09:55:24:429 GMT +1 ASG_CORE_6683 Error [localhost-startStop-1] - [root] Aug 10, 2018 9:55:24 AM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
----------------------------------
Issue/Introduction
This articles provides inputs on the error-level entries seen during the startup of the engine.
Environment
All Supported Platforms
Resolution
They are benign(low level console entries produced by BE) and can be ignored.
- Configuration should be validated and all errors resolved.
- Engine startup can be checked using some keywords. Please refer to Article#000022786.
- Sample ping or other requests can be sent and a successful response verified.
- Listener on port(s) or JMS Queue(s) can be checked.
Feedback
thumb_up
Yes
thumb_down
No