BPM, Workflow, and Case

BPM, Workflow, and Case

Come for answers. Stay for best practices. All we’re missing is you.

 View Only

  • 1.  BAW25 dmgr not coming up

    Posted Mon July 28, 2025 12:25 PM
    Hi All,
    After making a change (com.ibm.ssl.verifyHostname = false) from websphere admin console , the BAW server is no longer starting. Although we have reverted the change in the backend security.xml files at the following paths:
    • /app/IBM/BAW/profiles/VOLTST2DMGR01/config/cells/VOLTST2CELL01
    • /app/IBM/BAW/profiles/VOLTST2BAW01/config/cells/VOLTST2CELL01
    …the DMGR still fails to start. We also attempted a VM reboot, but the issue persists.
    Change:
    A custom property was added via the WebSphere Admin Console:
    Security > SSL certificate and key management > SSL Configurations > 
    

    IHUBMQSSLSettings > Custom properties > com.ibm.ssl.verifyHostname = false
    Observations:
    Logs at the time of failure:
    CWSCF0002I: The client code is attempting to load the security configuration from the server and this operation is not allowed.
JSAS0006I: Security connection interceptor initialized.
JSAS0001I: Security configuration initialized.
JSAS0003I: Authentication mechanism: BASICAUTH
    Connection Exception:
    javax.naming.ServiceUnavailableException: A communication failure occurred while attempting to obtain an initial context with the provider URL: "corbaloc:iiop:dmgrhost:9809/WsnAdminNameService"
Root exception: java.net.ConnectException: Connection refused (127.0.0.1:9809)
    During DMGR Startup:
    ADMU3200I: Server launched. Waiting for initialization status.
ADMU3011E: Server launched but failed initialization.
    Appreciate your help!!
    Thanks,
    Venkat


    ------------------------------
    Venkat Miriyala
    ------------------------------

    Attachment(s)

    zip
    dmgr.zip   98 KB 1 version
    zip
    nodeagent.zip   63 KB 1 version


  • 2.  RE: BAW25 dmgr not coming up

    Posted Thu July 31, 2025 10:24 AM

    I also created com.ibm.ssl.verifyHostname = false after BAW 25.0.0.0. upgrade and our dmgr started without problems. I don't think it will help you much, but here are my few cents:

    • I'm not sure the property can be defined at SSL configuration level, the https://www.ibm.com/support/pages/node/7163109 states that it should be created as Global security property (Security > Global security > Custom properties)
    • it does not seem SSL handshake is the problem though, you didn't attach dmgr SystemOut.log / SystemErr.log (they might contain more information), but it seems there is some other problem
    • check your /app/IBM/BAW/java/jre/lib/security/java.security - WAS Java SDK upgrades that come with BAW overwrite it - I always check what changed after BAW upgrade and merge our old cfg to the new file if needed (java.security.bak backup is created automatically, so your old file should be there)
    • check /app/IBM/BAW/profiles/VOLTST2DMGR01/properties/ssl.client.props  - I don't know what to look for in this case, maybe some old SSL / TLS protocols etc.
    • I don't know if that can be related but your stopServer.log contains a lot of file permission errors, so maybe the problem can be something on the OS layer (again, I think dmgr SystemOut.log / SystemErr.log would be a better source of information) 
      • [7/26/25 2:03:06:934 CDT] 00000001 FfdcProvider  I   FFDC provider error
                                         java.security.PrivilegedActionException: java.io.FileNotFoundException: /app/IBM/BAW/profiles/VOLTST2DMGR01/logs/ffdc/FfdcSummary.txt (Permission denied)
      • A permission error would make sense as there is CWSCF0002I: The client code is attempting to load the security configuration from the server and this operation is not allowed 
    • I don't know this would be related and what version of WAS you upgraded from, but if you have Java2 security enabled, there was required cfg change after WAS 8.5.5.24 upgrade - see https://www.ibm.com/support/pages/node/7240227#notice


    ------------------------------
    Pavel Trka
    ------------------------------

    Original Message


  • 3.  RE: BAW25 dmgr not coming up

    Posted Fri August 01, 2025 07:32 AM

    Of course immediately after I wrote the above reply, I checked the SSL cfg doc and found that com.ibm.ssl.verifyHostname = false can be defined at SSLcfg level :) But it's not important, that seems not to be an issue here.



    ------------------------------
    Pavel Trka
    ------------------------------

    Original Message


Related Content