Symptom
- The Diagnostic Agent stay with the status "Starting apps" on the Agent Admin. Checking the latest SMDSystem.X.log, it is possible to see the Agent restarting without any reason:
[Thread[Thread-200,5,main] ] Info [SMDAgent.shutdown] SMDAgent is shut down.
[Thread[SMDAgentShutdownHook,5,main] ] Info [ShutdownHook.run] hook received ...
- Checking the Default Trace from Solution Manager Java (/usr/sap/<SID>/J<instance>/j2ee/cluster/server0/log/defaultTrace.*.trc), it is possible to see this error happening multiples times per second:
#BC-JAS-COR-CSH#kernel.sda#C0008DAD369D0094001BC1020142003A###com.sap.engine.core.cache.impl.CacheManagerImpl#Guest#0##A12DA793B9DF11E9C68800000021355E#a12da793b9df11e9c68800000021355e##0#Thread[CML Monitoring,5,main]#Plain##
No more available Shared Momory Slots. Increase shared memory in JStartup configuration. Or decrease number of used regions. Failed region: BIWEBAPPS:odocResourcesUSER.CORP_LDAP.XXXXXXXX, caused by: com.sap.bc.proj.jstartup.sadm.ShmNoMemoryException: Cannot alloc cache 'BIWEBAPPS:odocResourcesUSER.CORP_LDAP.XXXXXXXX' (rc = 2 out of memory).#
Read more...
Environment
SAP Solution Manager 7.2
Product
SAP Solution Manager 7.2
Keywords
scalability, connection, smd, sma, agent, daaadm, smda, /smd/AgentAdmin , KBA , SV-SMG-DIA-SRV-AGT , Agent Framework , BC-JAS-COR-CSH , Common Cache Management , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.