Troubleshooting
Problem
DQM connection gives error when testing Data Source connection: "DPR-ERR-2002 Unable to execute the request because there were no connection to the process available within the configured time limit"
Symptom
Testing of DQM based data sourfce connection fails and Application Server OS process manager (Windows Task Manager) does not show 'java.exe' process for DQM, only 'java.exe' belonging to dispatcher is running.
Cause
JVM Garbage Collection Nursery heap size setting was set to same value as initial/max DQM memory heap and Query Service failed to start as per error.
Environment
Cognos 10.2.1 BI
Diagnosing The Problem
Logfile has following entries:
"-Dorg.dom4j.DocumentFactory.singleton.strategy=org.dom4j.util.PerThreadSingleton, com.cognos.xqebifw.cubingservices.DQServer] with console output: JVMJ9GC019E
-Xmns too large for -Xmx JVMJ9VM015W Initialization error for library j9gc26(2): Failed to initialize Error:
Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit."
"External Report Server process External Process cannot be startedAccept timed out java.net.SocketTimeoutException: Accept timed out at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method) at java.net.DualStackPlainSocketImpl.socketAccept"
Resolving The Problem
By default JAVA Garbage Collection memory is set for value '0' and in most cases memory allocation should get determined automatically based on demand.
To fix the problem, adjust JVM Nursery Nursery heap size under "Cognos Administration > System > Disp > Query Service > Properties", use default '0' or set it based on available total JVM memory for Query Service. For example half of total: 2048Mb for JAVA heap / 1024Mb for GC.
Related Information
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21883901