Has anyone encountered something similar to the following? Over the past week, the RSA-SMS service on our broker (10.6.2.0) has been randomly stopping and not starting back up. Checking through the sms.log, these are the only relevant log lines I could find. Does anyone have any additional information or context as to what these mean and how we can rectify the situation?
2017-07-30 15:29:46,577 [WrapperSimpleAppMain] WARN com.espertech.esper.timer.TimerServiceImpl - .startInternalClock Internal clock is already started, stop first before starting, operatio
n not completed
2017-07-30 15:29:43,706 [WrapperSimpleAppMain] WARN com.rsa.netwitness.carlos.i18n.MessageFactory - Can't find bundle for base name com.rsa.smc.esm.core.EsmMessages, locale en_US; fabricat
ing bundle dynamically.
2017-07-27 14:22:13,304 [WrapperSimpleAppMain] WARN com.espertech.esper.timer.TimerServiceImpl - .startInternalClock Internal clock is already started, stop first before starting, operatio
n not completed
2017-07-27 14:22:10,558 [WrapperSimpleAppMain] WARN com.rsa.netwitness.carlos.i18n.MessageFactory - Can't find bundle for base name com.rsa.smc.esm.core.EsmMessages, locale en_US; fabricat
ing bundle dynamically.
