IBM Support

IJ29851: WINCOLLECT 7.3.0 P1 AGENTS FAIL TO UPDATE OR GET CONFIGURATION UPDATES IN NAT'D ENVIRONMENTS

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

  • WinCollect 7.3.0 P1 Agents can fail to receive configuration
    updates or are unable to be updated due to connection timeouts
    occuring in NAT'd environments.
    Messages similar to the following might be visible when this
    issue occurs:
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24]
    com.q1labs.sem.semsources.wincollectconfigserver.requestprocesso
    rs.ConnectionEstablishmentVersion2Processor: [ERROR]
    [NOT:0000003000][<IP>/- -] [-/- -]Agent XXXXXXX2069(127.0.0.1)
    caught exception
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24]
    java.net.ConnectException: Connection timed out (Connection
    timed out)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainS
    ocketImpl.java:236)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl
    .java:218)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    java.net.SocksSocketImpl.connect(SocksSocketImpl.java:374)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    java.net.Socket.connect(Socket.java:682)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    com.ibm.jsse2.av.connect(av.java:453)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    com.ibm.jsse2.au.connect(au.java:98)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    sun.net.NetworkClient.doConnect(NetworkClient.java:192)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    sun.net.www.http.HttpClient.openServer(HttpClient.java:494)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    sun.net.www.http.HttpClient.openServer(HttpClient.java:589)
    : [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24]
    at com.ibm.net.ssl.www2.protocol.https.c.<init>(c.java:56)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    com.ibm.net.ssl.www2.protocol.https.c.a(c.java:222)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    com.ibm.net.ssl.www2.protocol.https.d.getNewHttpClient(d.java:25
    )
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpUR
    LConnection.java:1206)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURL
    Connection.java:1068)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    com.ibm.net.ssl.www2.protocol.https.d.connect(d.java:78)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Http
    URLConnection.java:1582)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpU
    RLConnection.java:1510)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    java.net.HttpURLConnection.getResponseCode(HttpURLConnection.jav
    a:491)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    com.ibm.net.ssl.www2.protocol.https.b.getResponseCode(b.java:40)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    com.q1labs.sem.semsources.wincollectconfigserver.requestprocesso
    rs.ConnectionEstablishmentVersion2Processor.onReceiveConnectionE
    stablishmentRequest(ConnectionEstablishmentVersion2Processor.jav
    a:235)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    com.q1labs.sem.semsources.wincollectconfigserver.WinCollectConfi
    gHandler.run(WinCollectConfigHandler.java:121)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
    utor.java:1160)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
    cutor.java:635)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    java.lang.Thread.run(Thread.java:818)
    

Local fix

  • Contact Support for a possible workaround that might address
    this issue in some instances.
    

Problem summary

  • WinCollect 7.3.0 P1 Agents can fail to receive configuration
    updates or are unable to be updated due to connection timeouts
    occuring in NAT'd environments.
    Messages similar to the following might be visible when this
    issue occurs:
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24]
    com.q1labs.sem.semsources.wincollectconfigserver.requestprocesso
    rs.ConnectionEstablishmentVersion2Processor: [ERROR]
    [NOT:0000003000][<IP>/- -] [-/- -]Agent XXXXXXX2069(127.0.0.1)
    caught exception
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24]
    java.net.ConnectException: Connection timed out (Connection
    timed out)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainS
    ocketImpl.java:236)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl
    .java:218)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    java.net.SocksSocketImpl.connect(SocksSocketImpl.java:374)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    java.net.Socket.connect(Socket.java:682)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    com.ibm.jsse2.av.connect(av.java:453)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    com.ibm.jsse2.au.connect(au.java:98)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    sun.net.NetworkClient.doConnect(NetworkClient.java:192)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    sun.net.www.http.HttpClient.openServer(HttpClient.java:494)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    sun.net.www.http.HttpClient.openServer(HttpClient.java:589)
    : [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24]
    at com.ibm.net.ssl.www2.protocol.https.c.<init>(c.java:56)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    com.ibm.net.ssl.www2.protocol.https.c.a(c.java:222)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    com.ibm.net.ssl.www2.protocol.https.d.getNewHttpClient(d.java:25
    )
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpUR
    LConnection.java:1206)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURL
    Connection.java:1068)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    com.ibm.net.ssl.www2.protocol.https.d.connect(d.java:78)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Http
    URLConnection.java:1582)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpU
    RLConnection.java:1510)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    java.net.HttpURLConnection.getResponseCode(HttpURLConnection.jav
    a:491)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    com.ibm.net.ssl.www2.protocol.https.b.getResponseCode(b.java:40)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    com.q1labs.sem.semsources.wincollectconfigserver.requestprocesso
    rs.ConnectionEstablishmentVersion2Processor.onReceiveConnectionE
    stablishmentRequest(ConnectionEstablishmentVersion2Processor.jav
    a:235)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    com.q1labs.sem.semsources.wincollectconfigserver.WinCollectConfi
    gHandler.run(WinCollectConfigHandler.java:121)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
    utor.java:1160)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
    cutor.java:635)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_24] at
    java.lang.Thread.run(Thread.java:818)
    

Problem conclusion

  • This APAR has been fixed in WinCollect version 7.3.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ29851

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    730

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-12-10

  • Closed date

    2021-05-04

  • Last modified date

    2021-05-04

  • 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

    QRADAR SOFTWARE

  • Fixed component ID

    5725QRDSW

Applicable component levels

[{"Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"730"}]

Document Information

Modified date:
05 May 2021