Fixes are available
APAR status
Closed as program error.
Error description
When many agents connect directly to the server, the servers ActiveMQ memory might max out. The default max is 64MB for ActiveMQ.xml systemUsage/systemUsage/memoryUsage/limit property. You will see: - There are not database locks - There is normal CPU usage - 'Waiting to start' in the deployment screen
Local fix
Uncomment the 'systemUsage' section inside of the ActiveMQ.xml file on the server. Change memoryUsage limit="20 mb" to memoryUsage limit="256 mb".
Problem summary
**************************************************************** * USERS AFFECTED: * * Administrators * **************************************************************** * PROBLEM DESCRIPTION: * * DEPLOYMENTS DO NOT START WHEN 2K+ AGENTS ARE CONNECTED * * DIRECTLY * * TO SERVER * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
A fix is available in IBM UrbanCode Deploy 6.2.1.1
Temporary fix
Comments
APAR Information
APAR number
PI55333
Reported component name
UDEPLOY
Reported component ID
5725M7700
Reported release
500
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-01-13
Closed date
2016-05-26
Last modified date
2016-05-26
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
UDEPLOY
Fixed component ID
5725M7700
Applicable component levels
R500 PSN
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4JV8","label":"IBM uDeploy"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"500","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
13 October 2021