IBM Support

IJ26089: QVM SCHEDULED SCANS CAN FAIL TO DISPLAY WHEN THERE ARE A LARGE NUMBER OF SCAN PROFILE CRON SCHEDULES

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • QRadar Vulnerability Manager scheduled scans entries can fail
    to be displayed in the User Interface calendar view when there
    are a large number (hundreds) of scan profile cron schedules.
    When this issue is occurring, clicking in the scheduled scans
    view in the User Interface can generate an error in the QRadar
    Console's /var/log/qradar.error log when the qvmprocessor is
    deployed on a separate QRadar managed host.
    Note:  This issue is less likely to occur on systems where there
    are only a small number of scan profiles.
    Messages similar to the following might be visible in
    /var/log/qradar.error when this issue is occurring:
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]
    com.q1labs.core.ui.servlet.RemoteJavaScript: [ERROR]
    [NOT:0000003000][127.0.0.1/- -] [-/- -]An exception occurred
    while executing the remote method 'getCronScanProfiles'
    <hostname> tomcat[13976]: org.apache.cxf.interceptor.Fault:
    Could not receive Message.
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles] javax.xml.ws.WebServiceException:
    Could not receive Message.
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at
    org.apache.cxf.jaxws.JaxWsClientProxy.mapException(JaxWsClientPr
    oxy.java:183)
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at
    org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.ja
    va:145)
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at
    org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.j
    ava:56)
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at
    org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java
    :673)
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at
    org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSende
    rEndingInterceptor.handleMessage(MessageSenderInterceptor.java:6
    3)
    <hostname> tomcat[13976]: at
    org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:355)
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at
    org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInte
    rceptorChain.java:308)
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at
    org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:531)
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at
    org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:440)
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at
    org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:355)
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at
    org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at
    org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:
    96)
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at
    org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.ja
    va:140)
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    ... 67 more
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles] Caused by:
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles] java.net.SocketTimeoutException: Read
    timed out
    </fingerprint>
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at
    java.net.SocketInputStream.socketRead0(Native Method)
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at
    java.net.SocketInputStream.socketRead(SocketInputStream.java:127
    )
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at
    java.net.SocketInputStream.read(SocketInputStream.java:182)
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at
    java.net.SocketInputStream.read(SocketInputStream.java:152)
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at com.ibm.jsse2.b.a(b.java:297)
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at com.ibm.jsse2.b.a(b.java:290)
    [tomcat.tomcat] [admin@127.0.0.1(8387)
    /console/JSON-RPC/QVM.getCronScanProfiles
    QVM.getCronScanProfiles]    at com.ibm.jsse2.av.a(av.java:840)
    <hostname> tomcat[13976]: at
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
    utor.java:1160)
    <hostname> tomcat[13976]: at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
    cutor.java:635)
    <hostname> tomcat[13976]: at
    org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(T
    askThread.java:61)
    <hostname> tomcat[13976]: at
    java.lang.Thread.run(Thread.java:818)
    <hostname> tomcat[13976]: Caused by:
    <hostname> tomcat[13976]: java.net.SocketTimeoutException:
    SocketTimeoutException invoking
    https://XXXXXXXXXX:9999/scanProfileService: Read timed out
    <hostname> tomcat[13976]: at
    sun.reflect.GeneratedConstructorAccessor697.newInstance(Unknown
    Source)
    <hostname> tomcat[13976]: at
    sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Delega
    tingConstructorAccessorImpl.java:57)
    <hostname> tomcat[13976]: at
    java.lang.reflect.Constructor.newInstance(Constructor.java:437)
    <hostname> tomcat[13976]: at
    org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.ma
    pException(HTTPConduit.java:1402)
    <hostname> tomcat[13976]: at
    org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.cl
    ose(HTTPConduit.java:1386)
    <hostname> tomcat[13976]: at
    org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.j
    ava:56)
    <hostname> tomcat[13976]: at
    org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java
    :673)
    <hostname> tomcat[13976]: at
    org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSende
    rEndingInterceptor.handleMessage(MessageSenderInterceptor.java:6
    3)
    <hostname> tomcat[13976]: ... 74 more
    <hostname> tomcat[13976]: Caused by:
    <hostname> tomcat[13976]: java.net.SocketTimeoutException: Read
    timed out
    <hostname> tomcat[13976]: at
    java.net.SocketInputStream.socketRead0(Native Method)
    <hostname> tomcat[13976]: at
    java.net.SocketInputStream.socketRead(SocketInputStream.java:127
    )
    <hostname> tomcat[13976]: at
    java.net.SocketInputStream.read(SocketInputStream.java:182)
    

Local fix

  • No workaround available.
    

Problem summary

  • This issue was fixed in QRadar QRM QVM release of 7.4.2.
    

Problem conclusion

  • This issue was fixed in QRadar QRM QVM release of 7.4.2.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ26089

  • Reported component name

    QR VULNERABILIT

  • Reported component ID

    5725QVMSW

  • Reported release

    740

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-07-07

  • Closed date

    2020-11-27

  • Last modified date

    2020-11-27

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    QR VULNERABILIT

  • Fixed component ID

    5725QVMSW

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSHLPS","label":"IBM QRadar Vulnerability Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"740"}]

Document Information

Modified date:
28 November 2020