Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Resolved Issues

 

The following are the resolved issues addressed in the JSA 7.3.3 Fix Pack 1 (Patch 1):

  • OFFENSE API DOES NOT RETURN EXPECTED OFFENSES WHEN USING “ID” AND “INACTIVE” FIELD IF OFFENSE ACTIVE_CODE IS ‘DORMANT’.

  • JSA APPS CAN GO OUT OF MEMORY DUE TO A RHEL KERNEL BUG WITH DENTRY SLAB CACHE.

  • JSA PATCH AND OR REPLICATION PROCESS CAN FAIL WHEN MULTIPLE DUPLICATED ASSET.ASSETVIEW DATA EXISTS.

  • LDAP LOGINS CAN FAIL IF PAGINATION IS DISABLED FOR BIND USERS.

  • DATA BACKUPS CAN FAIL (TIME OUT) WHEN A BACKEND “PS” COMMAND HANGS.

  • EVENT COLLECTORS CAN EXPERIENCE PIPLELINE PERFORMANCE ISSUES DUE TO NOT HAVING AN APPLIANCE CAPABILITY CONFIGURED.

  • REGEXMONITOR FEATURE CAN SOMETIMES DISABLE CUSTOM PROPERTIES WITHOUT ANY SYSTEM NOTIFICATION.

  • JSA USER INTERFACE CAN BECOME INACCESSIBLE DUE TO TOMCAT TXSENTRY WHEN USING ‘TOP CATEGORY TYPES’ DASHBOARD ITEM.

  • DEPLOY FUNCTION TIMEOUT CAUSED BY INCORRECT DEPLOYMENT.XML COMPONENT DATA AFTER A FLOW PROCESSOR SOURCE IS REMOVED.

  • DIFFERENCES IN HOW DSM EDITOR PARSES VERSUS HOW THE PIPELINE PARSES CAN PREVENT PROPER DSM EDITOR REGEX WRITING/TESTING.

  • SOME FORWARDED EVENTS CAN FAIL TO FORWARD SUCCESSFULLY WHEN A CONNECTION DROP OCCURS TO THE EVENT FORWARDING RECEIVER.

  • TOMCAT OUT OF MEMORY CAN OCCUR WHEN PERFORMING AN ENABLE OR DISABLE OF A LOG SOURCE.

  • JSA USER INTERFACE BECOMES UNRESPONSIVE DURING BULK CHANGES MADE TO A LARGE NUMBER OF LOG SOURCES USING THE API.

  • OFFENSE SOURCE SUMMARY INFORMATION THAT IS PULLING ASSET DATA IS NOT DOMAIN AWARE FOR SOME INDEXED OFFENSES.

  • OFFENSES CAN FAIL TO GENERATE AND OR UPDATE WHEN USERNAME OR HOSTNAME IN ASSET EXCEEDS 255 CHARACTERS.

  • THE OFFENSE PAGE IN THE JSA USER INTERFACE CAN BE SLOW TO OPEN AFTER PATCHING TO JSA 7.3.2.

  • CUSTOM AQL EVENT/FLOW PROPERTIES WHILE USING OFFLINE FORWARDER WITH JSON FORWARDED DESTINATIONS CAN CAUSE PERFORMANCE ISSUES.

  • HTTP 504 ERROR IN JSA USER INTERFACE WHEN SELECTING CUSTOM RULES OR WHEN OPENING RULES IN THE RULE WIZARD.

  • ‘SAR SENTINEL: THRESHOLD CROSSED FOR DRBD0’ SYSTEM NOTIFICATIONS.

  • ‘THE APPLIANCE EXCEEDED THE EPS OR FPM ALLOCATION WITHIN THE LAST HOUR’ MESSAGES CAN BE CAUSED BY HEALTH METRICS EVENTS.

  • ECS-EP PROCESS FAILS TO START AFTER PATCHING TO JSA 7.3.2 (OR LATER) WHEN CUSTOM SNMP TRAP EVENTS WERE CONFIGURED.

  • WINCOLLECT AGENTS ARE DOWNGRADED TO VERSION 7.2.3 AFTER A CONFIGURATION RESTORE ON THE JSA CONSOLE.