JDriver on WebSphere 6.0 generates a stackOverFlow exception
Welcome to "KB Articles"
JDriver on WebSphere 6.0 generates a stackOverFlow exception
book
Article ID: KB0091509
calendar_today
Updated On: 01-14-2017
Products
Versions
TIBCO DataSynapse GridServer
-
Not Applicable
-
Description
Resolution: Running JDriver from a WebSphere 6.0 servlet generates a stackOverFlow exception:
com.livecluster.util.logging.logger.forName(name) keeps appending '_' to "ServiceFileFilter" until stack overflows.
The overflow is due to a WebSphere bug. If a logger doesn't exist, LogManager.getLogger(name) in WS LogManager() returns a new logger rather than a null. See http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg1PK35603.
To work around this problem:
1. Make sure your WebSphere Server has the correct fix pack installed. For details, see http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg1PK35603. 2. After the correct fix pack is installed, set com.ibm.ws.bootstrap.logmanager.createNewLogger=false. To set this system property, navigate through Servers > Application servers > server_name > Java and Process Management > Process Definition > Java Virtual Machine > Customer Properties.
Issue/Introduction
JDriver on WebSphere 6.0 generates a stackOverFlow exception