Question & Answer
Question
My Liberty server running on CICS Transaction Server for z/OS (CICS TS) is talking up to ten minutes to initialize and sometimes it times out. I see the following Liberty log messages showing the delay:
09.26.51 STC39512 +CWWKE0001I: The server defaultServer has been launched.
09.40.31 STC39512 +CWWKF0011I: The server defaultServer is ready to run a smarter planet.
I tried different values for OSGI_FRAMEWORK_TIMEOUT and Dcom.ibm.cics.jvmserver.controller.timeout in the JVMprofile, however it only works with these values:
OSGI_FRAMEWORK_TIMEOUT=900 and Dcom.ibm.cics.jvmserver.controller.timeout=900000.
What could be causing the Liberty Server to initialize so slowly or timeout?
Answer
When reviewing the JVMProfile, I can see that the Liberty trace logging parameter is set as follows:
Dcom.ibm.ws.logging.trace.specification=com.ibm*=all
Setting this parameter ( *=all ) like this causes so much Liberty tracing to occur that it severely impacts the initialization of the Liberty Server. You should only set it like this when you are debugging a problem. When not debugging a problem it should be set to the default ( *=info ). It should look like this:
Dcom.ibm.ws.logging.trace.specification=com.ibm*=info
After making this change in the JVMProfile, the Liberty Server should start in seconds.
Product Synonym
CICS/TS CICSTS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
27 July 2017
UID
dwa1388507