IBM Security QRadar SOAR

 View Only

  • 1.  Inbound mail

    Posted Mon October 19, 2020 03:48 AM


    Hi team,

    After rebooting resilient (for increasing ram) , inbound mail didn't work with this error. Any advice / document wold be appreciated.

    Best

    07:38:16.039 [Camel (camel-1) thread #16 - JmsConsumer[email-service.save-email-data]] ERROR o.a.c.c.j.DefaultJmsMessageListenerContainer - Could not refresh JMS Connection for destination 'email-service.save-email-data' - retrying using FixedBackOff{interval=5000, currentAttempts=67, maxAttempts=unlimited}. Cause: Could not connect to broker URL: ssl://127.0.0.1:65000?socket.verifyHostName=false&socket.enabledProtocols=TLSv1.2&socket.enabledCipherSuites=SSL_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384%2CSSL_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384%2CSSL_ECDHE_ECDSA_WITH_AES_256_CBC_SHA%2CSSL_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256%2CSSL_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256%2CSSL_ECDHE_ECDSA_WITH_AES_128_CBC_SHA%2CSSL_ECDHE_RSA_WITH_AES_256_GCM_SHA384%2CSSL_ECDHE_RSA_WITH_AES_256_CBC_SHA384%2CSSL_ECDHE_RSA_WITH_AES_256_CBC_SHA%2CSSL_ECDHE_RSA_WITH_AES_128_GCM_SHA256%2CSSL_ECDHE_RSA_WITH_AES_128_CBC_SHA256%2CSSL_ECDHE_RSA_WITH_AES_128_CBC_SHA%2CTLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256%2CTLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256%2CTLS_ECDH_RSA_WITH_AES_128_CBC_SHA256%2CTLS_ECDH_RSA_WITH_AES_128_GCM_SHA256%2CTLS_RSA_WITH_AES_128_CBC_SHA%2CTLS_RSA_WITH_AES_128_CBC_SHA256%2CTLS_RSA_WITH_AES_256_CBC_SHA%2CTLS_RSA_WITH_AES_256_CBC_SHA256%2CTLS_RSA_WITH_AES_128_GCM_SHA256. Reason: java.net.SocketException: Socket closed 07:38:23.796 [Camel (camel-1)

    ------------------------------
    Jasmine
    ------------------------------


  • 2.  RE: Inbound mail

    Posted Mon October 19, 2020 04:55 AM
    I have solved this issue. Seems that you have to restart resilient messaging service after reboot.

    ------------------------------
    Jasmine
    ------------------------------

    Original Message


  • 3.  RE: Inbound mail

    Posted Tue October 20, 2020 09:05 AM
    It shouldn't be necessary to manually restart the messaging service after reboot. If you are finding that to be the case I would open a support ticket so a bug can be created.

    Ben

    ------------------------------
    Ben Lurie
    ------------------------------

    Original Message