The latest updates about IBM Security QRadar SIEM. It has been identified that after patching to QRadar 7.3.2, that opening the Offense page in the QRadar User Interface can. IJ16002: THE OFFENSE PAGE IN THE QRADAR USER INTERFACE CAN BE SLOW TO OPEN AFTER PATCHING TO QRADAR 7.3.2.
Posted by2 months ago
QRadar 7.3.2 Interim Fix 01 is Released
Hey all,
Just a quick note that QRadar 7.3.2 Interim Fix 01 has been posted to IBM Fix Central. This update includes a single APAR/fix for a UI responsiveness issue when large API calls are occurring as Tomcat can start running out of file handles as listed in APAR IJ14947.
Links:
- APARs lookup page - This item is listed under '7.3.2 Interim Fix 01'
- Direct APAR link to IJ14947
NOTE: The APAR for this update is not live yet, but I put a description and the error message from the logs on the APARs lookup page. Administrators who make heavy use of the QRadar API should consider applying this update to their 7.3.2 QRadar Console appliance.
Why is this APAR listed as Transitioning to Closed on the APARs page?
We use Transitioning to Closed to indicate that this fix is going to be available in another software update. In this specific example, this resolution/code is also going to be part of future QRadar 7.3.2 Patch, when that update is available. Users on QRadar 7.3.2 should not wait for the QRadar 7.3.1 Patch 1 if you use the API or leverage apps that make use of the QRadar API, like UBA, Watson Advisor, etc. Since this APAR is listed in association with another release, we tag these fixes 'Transitioning to Closed' because closing APARs can be slightly misleading when there is a port happening to fix the issue on another version.
If you have any questions, let me know.
- Jonathan
- Jonathan
100% Upvoted