IBM Support

IJ44580: QRADAR APPS FAIL TO START OR STOP AFTER EDITING AN APP HOST SETTINGS TO DISABLE ENCRYPTION

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

  • Administrators with encrypted App Hosts in the deployment can
    experience an issue where the state of the app cannot be stopped
    or started with the qappmanager utility after encryption is
    disabled.
    
    This issue is caused by port mappings in the application
    framework that are not rebuilt when encryption is disbled.
    
    Attempting to stop, start, or restart an app from qappmanager
    displays the following error:
    [hostcontext.hostcontext] [pool-1-thread-2]
    com.ibm.si.api.workload.v1.ApiException:
    java.net.ConnectException: Failed to connect to
    0f5ee0e1xxxxxxxxxx.localdeployment/x.x.x.x:26001
    
    
    Full stack trace:
    [hostcontext.hostcontext] [pool-1-thread-2]
    com.ibm.si.hostcontext.app.tasks.workloads.PlatformStartAppTask:
     [ERROR] [NOT:0000003000][x.x.x.x/- -] [-/- -]An error occurred
    while attempting to start app [qapp-1751].
    [hostcontext.hostcontext] [pool-1-thread-2]
    com.ibm.si.application.platform.exception.ApplicationPlatformSer
    viceException: Unable to start application with id [qapp-1751]
    on host https://0f5ee0e1xxxxxxxx.localdeployment:26001/v1/api/,
    responseCode [0], responseBody [null]
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.ibm.si.application.workloads.WorkloadsPlatformService.proces
    sException(WorkloadsPlatformService.java:551)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.ibm.si.application.workloads.WorkloadsPlatformService.startA
    pp(WorkloadsPlatformService.java:856)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.ibm.si.hostcontext.app.tasks.workloads.PlatformStartAppTask.
    runTask(PlatformStartAppTask.java:63)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.ibm.si.frameworks.taskmanagement.Task.run(Task.java:108)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    java.util.concurrent.Executors$RunnableAdapter.call(Executors.ja
    va:522)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    java.util.concurrent.FutureTask.run(FutureTask.java:277)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
    utor.java:1160)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
    cutor.java:635)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    java.lang.Thread.run(Thread.java:822)
    [hostcontext.hostcontext] [pool-1-thread-2] Caused by:
    [hostcontext.hostcontext] [pool-1-thread-2]
    com.ibm.si.api.workload.v1.ApiException:
    java.net.ConnectException: Failed to connect to
    0f5ee0e1bf6bde89ee35.localdeployment/x.x.x.x:26001
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.ibm.si.api.workload.v1.ApiClient.execute(ApiClient.java:844)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.ibm.si.api.workload.v1.api.WorkloadsApi.showWorkloadByIdWith
    HttpInfo(WorkloadsApi.java:1036)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.ibm.si.api.workload.v1.api.WorkloadsApi.showWorkloadById(Wor
    kloadsApi.java:1022)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.ibm.si.application.workloads.WorkloadsPlatformService.getApp
    sWorkload(WorkloadsPlatformService.java:508)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.ibm.si.application.workloads.WorkloadsPlatformService.startA
    pp(WorkloadsPlatformService.java:816)
    [hostcontext.hostcontext] [pool-1-thread-2] ... 7 more
    [hostcontext.hostcontext] [pool-1-thread-2] Caused by:
    [hostcontext.hostcontext] [pool-1-thread-2]
    java.net.ConnectException: Failed to connect to
    0f5ee0e1bf6bde89ee35.localdeployment/x.x.x.x:26001
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.squareup.okhttp.internal.io.RealConnection.connectSocket(Rea
    lConnection.java:143)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.squareup.okhttp.internal.io.RealConnection.connect(RealConne
    ction.java:112)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.squareup.okhttp.internal.http.StreamAllocation.findConnectio
    n(StreamAllocation.java:184)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.squareup.okhttp.internal.http.StreamAllocation.findHealthyCo
    nnection(StreamAllocation.java:126)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.squareup.okhttp.internal.http.StreamAllocation.newStream(Str
    eamAllocation.java:95)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.squareup.okhttp.internal.http.HttpEngine.connect(HttpEngine.
    java:281)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.squareup.okhttp.Call.getResponse(Call.java:286)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.squareup.okhttp.internal.http.HttpEngine.sendRequest(HttpEng
    ine.java:224)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.squareup.okhttp.Call.getResponseWithInterceptorChain(Call.ja
    va:205)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.squareup.okhttp.Call$ApplicationInterceptorChain.proceed(Cal
    l.java:243)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.squareup.okhttp.Call.execute(Call.java:80)
    [hostcontext.hostcontext] [pool-1-thread-2] at
    com.ibm.si.api.workload.v1.ApiClient.execute(ApiClient.java:840)
    [hostcontext.hostcontext] [pool-1-thread-2] ... 11 more
    

Local fix

  • Before you complete this procedure, administrators can alert
    their users that the user interface is unavailable and all users
     are required to log back in when Tomcat is restarted. The
    user interface is unavailable until all required services are
    running as expected.
    
    1. Use SSH to log in to the Console as the root user.
    2. Type the following command:
       systemctl restart tomcat
    3. Wait until the service succesfully restarts.
    4. Type the following command:
       systemctl restart hostcontext
    
       Results
       After hostcontext restarts, the port mapping is rebuilt and
       the apps can be managed.
    

Problem summary

  • This issue has been resolved in QRadar 7.5.0 Update Package 6.
    

Problem conclusion

  • This issue has been resolved in QRadar 7.5.0 Update Package 6.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ44580

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-12-12

  • Closed date

    2023-06-26

  • Last modified date

    2023-06-26

  • 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

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

Document Information

Modified date:
26 June 2023