Products
Solutions
Support & Services
Company
How To Buy
Skip to main content (Press Enter).
Sign in
Skip auxiliary navigation (Press Enter).
Register
Skip main navigation (Press Enter).
Toggle navigation
Search Options
Home
Communities
All Communities
Enterprise Software
Mainframe Software
Symantec Enterprise
Blogs
All Blogs
Enterprise Software
Mainframe Software
Symantec Enterprise
Events
Enterprise Software
Mainframe Software
Symantec Enterprise
VMware
Water Cooler
Groups
Enterprise Software
Mainframe Software
Symantec Enterprise
DX Infrastructure Management
Private Community
Community Home
Threads
Library
Events
Members
Back to Library
Tech Tip: udm_inventory queue not processing data
1
Recommend
Sep 13, 2018 11:34 AM
Marco Ippati
udm_inventory queue not processing data
Document ID :
KB000112962
Last Modified Date :
06/09/2018
Issue:
The udm_inventory queue is not processing data and it is building up.
• In the discover_server.log I see:
[attach_clientsession] WARN com.nimsoft.discovery.common.queue.hub.HubQueueListener - An error occurred while handling a message for udm_inventory: (7) temporarily out of resources, null
• in the udm_manager.log I see:
[main, udm_manager] Exception establishing Datomic connection: :db.error/not-enough-memory (datomic.objectCacheMax + datomic.memoryIndexMax) exceeds 75% of JVM RAM
Environment:
UIM 8.5.1, UIM 9.0
Cause:
The errors in the log indicate that there is not enough memory allocated to the udm_manager probe
Resolution:
Please follow the below instructions to limit or eliminate this issue:
1. Deactivate discovery_server
2. Deactivate udm_manager
3. In udm_manager open Raw Configure
> open setup > datomic > double the values of the
memory_index_max
and
memory_index_threshold
> open start up > opt > double the values of the
java_mem_init
and
java_mem_max
4. Save configuration
***********************************
Example udm_manager.cfg
• Default values:
<datomic>
port = 4334
memory_index_max = 256m
memory_index_threshold = 32m
object_cache_max = 128m
heartbeat_interval_msec = 30000
</datomic>
</setup>
<startup>
<opt>
java_mem_init = -Xms96m
java_mem_max = -Xmx1024m
java_opts = -server -XX:ErrorFile=./hs_err_pid.log -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode
</opt>
• Values with memory increased:
<datomic>
port = 4334
memory_index_max = 516m
memory_index_threshold = 64m
object_cache_max = 256m
heartbeat_interval_msec = 30000
</datomic>
</setup>
<startup>
<opt>
java_mem_init = -Xms192m
java_mem_max = -Xmx2048m
java_opts = -server -XX:ErrorFile=./hs_err_pid.log -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode
</opt>
***********************************
5. Run the SQL query
DROP TABLE DATOMIC_KVS;
6. Activate the discovery_server and udm_manager probes.
(The DATOMIC_KVS table will be recreated with the activation of the probes.)
Additional Information:
Related KB Articles:
udm inventory queue builds and errors are seen in discovery server logs
Slow performance of udm_manager in Oracle environment - udm_inventory queue backed up
Statistics
0 Favorited
3 Views
0 Files
0 Shares
0 Downloads
Related Entries and Links
No Related Resource entered.
Skip Navigation Links
Footer
Copyright 2023. All rights reserved.
Powered by Higher Logic