WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

CSIv2 defaultOrb element issue

  • 1.  CSIv2 defaultOrb element issue

    Posted 07/18/18 05:21 PM
    I'm stuck on a very annoying problem.

    At the moment I'm using WLP 18.0.0.2 but I experienced the same problem also with past WLP versions.
    I have an EJB application with one Remote EJB published on a server joined with a collective controller.
    When I start the server I got the following error:

    [7/18/18 11:12:03:137 CEST] 00000045 AbstractCsiv2 E CWWKS9582E: The [defaultSSLConfig] sslRef attributes required by the orb element with the defaultOrb id have not been resolved within 10 seconds. As a result, the applications will not start. Ensure that you have included a keyStore element and that Secure Sockets Layer (SSL) is configured correctly. If the sslRef is defaultSSLConfig, then add a keyStore element with the id defaultKeyStore and a password.

    and the Remote EJB doesn't start.

    What I haven't understood yet is the reason for that error.
    According to the SSL part of the generated collective.xml file it seems that the defaultSSLConfig is correctly defined.

    <!-- clientAuthenticationSupported set to enable bidirectional trust -->
    <ssl id="defaultSSLConfig" keyStoreRef="defaultKeyStore" trustStoreRef="defaultTrustStore" clientAuthenticationSupported="true" />
    <!-- inbound (HTTPS) keystore -->
    <keyStore id="defaultKeyStore" password="..." location="${server.config.dir}/resources/security/key.jks" />
    <!-- inbound (HTTPS) truststore -->
    <keyStore id="defaultTrustStore" password="..." location="${server.config.dir}/resources/security/trust.jks" />

    If I try to reach a web application via the HTTPS server port, it works fine and the exposed certificate is the one present on the key.jks keystore file, so, in my opinion, the SSL feature is up and running.

    Any suggestions?

    ------------------------------
    Andrea Minuto
    Exevutive IT Specialist
    IBM
    ------------------------------