Engine Message Exiting: Iteration count is exceeded, exiting LSQNONNEG. log4j:WARN Please initialize the log4j system properly (Doc ID 1313844.1)

Last updated on JUNE 23, 2017

Applies to:

Oracle Demantra Demand Management - Version 7.3.0.1 and later
Information in this document applies to any platform.

Goal

Encountered these messages in Linux session when Engine is kicked off. These messages does not get into any logs ( engine2k or engineManager). But these error/warning messages continue for all the time -

log4j:WARN No appenders could be found for logger (org.apache.commons.httpclient.HttpClient).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN No appenders could be found for logger (org.apache.commons.httpclient.HttpClient).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN No appenders could be found for logger (org.apache.commons.httpclient.HttpClient).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN No appenders could be found for logger (org.apache.commons.httpclient.HttpClient).
log4j:WARN Please initialize the log4j system properly.
Exiting: Iteration count is exceeded, exiting LSQNONNEG.
Try raising the tolerance (OPTIONS.TolX).
Exiting: Iteration count is exceeded, exiting LSQNONNEG.




They also mention that they have also noticed that these messages comes in the Linux session where Engine Servlet (EngineStarter) has been started and when they close that session the Servlet aborts causing engine failure.

This was working fine, and the first time they saw these messages was when they ran the Engine in QA after applying the patch 10104087.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms