Skip to main content

License limit messages in console.log

  • January 18, 2016
  • 0 replies
  • 0 views

Problem:

 We are seeing the following messages in our console.log files:

CASKC1001W Warning: Allocated license limit exceeded 0000000015 times
CASKC1002I ES allocated license limit: 0000000025 units, peak usage: 0000000040 units

JCLCM0180I JOB01990 BATCHPAA Job ready for execution.
CASKC1001W Warning: Allocated license limit exceeded 0000000011 times

CASKC1001W Warning: Allocated license limit exceeded 0000000002 times
CASKC1002I ES allocated license limit: 0000000025 units, peak usage: 0000000036 units

CASKC1001W Warning: Allocated license limit exceeded 0000000011 times
CASKC1002I ES allocated license limit: 0000000025 units, peak usage: 0000000040 units

CASXO0003S Resource Manager for resource ILV Transaction start failed: reason -00003
CASKC1001W Warning: Allocated license limit exceeded 0000000001 times
CASXO0003S Resource Manager for resource ILV Transaction start failed: reason -00003
CASKC1002I ES allocated license limit: 0000000030 units, peak usage: 0000000031 units

What 'license limit' are these messages referring to? We also get a DB error '08S02' from the application program. The problem is fixed by manually restarting the program that fails.

 

Resolution:

 Our Help lists the messages cited but there is not very much information in their description:
 
Micro Focus Enterprise Developer 2.3 for Eclipse > Micro Focus Enterprise Developer 2.3 for Eclipse > Deployment > Configuration and Administration > Enterprise Server Reference > Error Messages > Enterprise Server Error Messages > CASKC Error Messages, CASKC1000 - CASKC1003
 
CASKC1000I
 During startup the maximum number of concurrent requests is logged.
CASKC1001W
 The number of active client requests exceeded the licensed maximum client-count times.
CASKC1002I
 During shutdown the maximum number of concurrent requests is logged against the actual
CASKC1003I
 A request for a license of the referenced type was made to the license server. No license was available. Please contact your Micro Focus sales representative
 
 When one configures a server, one needs to allocate a number of licenses for the server in the Requested Licenses field under Enterprise Server Admin page Server > Properties > General Tab > Startup Options area > Requested Licenses. When the server is started, these licenses are instantly allocated to the server from the main pool of licenses and if there are not enough licenses left in the pool to satisfy the requested number of licenses, the server will not be able to be started.
 
 For example if there are 10 licenses installed and one allocates 4 licenses to each of 3 servers, only 2 servers will be able to be started. When a third server is attempted to be started, it will not start because 4 licenses were requested but only 2 were available.
 
 Once a server is started, the requested licenses form another pool set aside just for this server. This is the number of concurrent processes that each server can run and can be anything happening on the system that requires a SEP. So this will include running batch jobs, servicing web service requests, active CICS or IMS sessions and administrators using ES Monitor and control screens. If we have two users accessing ESMAC we will need two licenses in addition to the licenses needed to run batch jobs.

 The messages in the console are just warnings that the pools of licenses for the active server were exhausted. The server will continue to run those jobs that were already started, but if one tries to start more processes than available licenses on a machine, then the case may be encountered where no more new jobs will be allowed to be activated until a license is made available. If one runs more than the allocated limit, these messages can be issued:
 
  CASKC1001W Warning: Allocated license limit exceeded 0000000002 times
  CASKC1002I ES allocated license limit: 0000000004 units, peak usage: 0000000005 units
 
The messages mean that the server did not have enough allocated licenses to cope with the peak demand. And these messages will only appear as processes are started. In order to prevent these messages one needs to request more licenses in the server configuration. For the cases cited, we are seeing 25 and 30 licenses are in use but we had peak of 40 and 31. So using a value of 40 will mean fewer messages will be issued as long as 40 are always available.

 These messages do not refer to real 'licenses' - not in the sense that one must ask Sales for them and pay for them. They are indicators of how busy the system is. For example, we had one instance of 20 paid licenses and when their servers were set to 20 we saw these messages. After setting the value to 60, no more messages were logged in the console log. So it seems this might be more historical than actual and our code has changed to track processes more than actual licenses.

 From the information provided to us, we saw these settings:

Mode          Server Name     SEPs    Requested Licenses
-------       --------------  ------  -----------------
Production    PRODBLV          10      30

Non-Prod      DEV1             10      25
              UNTSTLV          10      25
              UAT              10      25
 
Our recommendation is to increase your values from 25 and 30 to 50 and 60. If you see the need to have a more detailed system analysis, then we can refer you to our technical services team who will examine your system's performance and give suggestions.


#EnterpriseDeveloper
#MFDS

0 replies

Be the first to reply!