Article Number
000032019
Applies To
RSA Product Set: Security Analytics
RSA Product/Service Type: Security Analytics UI, Security Analytics Server
RSA Version/Condition: 10.5.0.x, 10.5.1
Platform: CentOS
Platform (Other): MongoDB
O/S Version: EL6
Issue
When viewing Job Results that are large, the Security Analytics user interface decreases in performance.
Cause
This issue occurs because when Job Results are viewed in the Security Analytics UI, the Security Analytics server fetched the entire result from the MongoDB database before presenting the first page in the user interface.
When the results are large enough, the server will run out of memory and may result in a Loading screen that never completes and the user interface slowing down.
When the server runs out of memory, an error message similar to the example below can be found in the logs.
Caused by: java.lang.OutOfMemoryError: Java heap space
at java.util.HashMap.resize(HashMap.java:703)
at java.util.HashMap.putVal(HashMap.java:628)
at java.util.HashMap.put(HashMap.java:611)
at org.bson.BasicBSONObject.put(BasicBSONObject.java:281)
at org.bson.BasicBSONCallback._put(BasicBSONCallback.java:174)
at org.bson.BasicBSONCallback.gotString(BasicBSONCallback.java:133)
at org.bson.BasicBSONDecoder.decodeElement(BasicBSONDecoder.java:155)
at org.bson.BasicBSONDecoder.decodeElement(BasicBSONDecoder.java:206)
at org.bson.BasicBSONDecoder.decodeElement(BasicBSONDecoder.java:196)
at org.bson.BasicBSONDecoder.decodeElement(BasicBSONDecoder.java:206)
at org.bson.BasicBSONDecoder.decodeElement(BasicBSONDecoder.java:196)
at org.bson.BasicBSONDecoder._decode(BasicBSONDecoder.java:79)
at org.bson.BasicBSONDecoder.decode(BasicBSONDecoder.java:57)
at com.mongodb.DefaultDBDecoder.decode(DefaultDBDecoder.java:56)
at com.mongodb.Response.<init>(Response.java:83)
at com.mongodb.DBPort.go(DBPort.java:124)
at com.mongodb.DBPort.call(DBPort.java:74)
at com.mongodb.DBTCPConnector.innerCall(DBTCPConnector.java:286)
at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:257)
at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:225)
at com.mongodb.DBApiLayer$Result._advance(DBApiLayer.java:452)
at com.mongodb.DBApiLayer$Result.hasNext(DBApiLayer.java:421)
at com.mongodb.DBCursor._hasNext(DBCursor.java:464)
at com.mongodb.DBCursor.hasNext(DBCursor.java:484)
at org.springframework.data.mongodb.core.MongoTemplate.executeFindMultiInternal(MongoTemplate.java:1669)
at org.springframework.data.mongodb.core.MongoTemplate.doFind(MongoTemplate.java:1496)
at org.springframework.data.mongodb.core.MongoTemplate.doFind(MongoTemplate.java:1480)
at org.springframework.data.mongodb.core.MongoTemplate.find(MongoTemplate.java:527)
at org.springframework.data.mongodb.core.MongoTemplate.find(MongoTemplate.java:518)
at com.rsa.smc.sa.datascience.service.impl.DataScienceViewServiceImpl.getDomainsResult(DataScienceViewServiceImpl.java:365)
at com.rsa.smc.sa.content.datascience.web.controller.DataScienceViewController.getDomainGridResults(DataScienceViewController.java:70)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Resolution
This issue has been resolved in Security Analytics 10.5.1.1.