This is happening immediately upon the region starting up. 

We can see in the logs that it finishes creating all the SEPs, and 10 seconds after all the SEPs abend with the message "CASCD0154S SEP 00001 for ES PROD abended by signal 4294967295". Our clients are using 10 SEPs, and they all abend the same way. See part of the log file below. The rest of the log file looks normal.

The most recent clients are in versions "ED6.0/20230530_PU25" and "ED6.0/20230630_PU26".

Has anyone had this reported?

Thanks.

231023 05010373 5544 PROD CASCS5100I Communications Process instance 01 is ready to accept requests 05:01:03
231023 05010389 CASCD0127I SEP 00001 created for ES PROD, process-id = 2448 05:01:03
231023 05010392 CASCD0127I SEP 00002 created for ES PROD, process-id = 6484 05:01:03
231023 05010392 CASCD0127I SEP 00003 created for ES PROD, process-id = 3096 05:01:03
231023 05010407 CASCD0127I SEP 00004 created for ES PROD, process-id = 6768 05:01:04
231023 05010408 CASCD0127I SEP 00005 created for ES PROD, process-id = 2956 05:01:04
231023 05010429 CASCD0127I SEP 00006 created for ES PROD, process-id = 3696 05:01:04
231023 05010445 CASCD0127I SEP 00007 created for ES PROD, process-id = 4600 05:01:04
231023 05010460 CASCD0127I SEP 00008 created for ES PROD, process-id = 5000 05:01:04
231023 05010469 CASCD0154S SEP 00002 for ES PROD abended by signal 4294967295 05:01:04
231023 05010471 CASCD0127I SEP 00009 created for ES PROD, process-id = 1704 05:01:04
231023 05010473 CASCD0127I SEP 00010 created for ES PROD, process-id = 536 05:01:04
231023 05010484 CASCD0154S SEP 00006 for ES PROD abended by signal 4294967295 05:01:04
231023 05010485 CASCD0154S SEP 00005 for ES PROD abended by signal 4294967295 05:01:04
231023 05010511 CASCD0154S SEP 00004 for ES PROD abended by signal 4294967295 05:01:05
231023 05010512 CASCD0154S SEP 00001 for ES PROD abended by signal 4294967295 05:01:05
231023 05010520 CASCD0154S SEP 00010 for ES PROD abended by signal 4294967295 05:01:05
231023 05010538 CASCD0154S SEP 00008 for ES PROD abended by signal 4294967295 05:01:05
231023 05010544 CASCD0154S SEP 00007 for ES PROD abended by signal 4294967295 05:01:05
231023 05010568 CASCD0154S SEP 00003 for ES PROD abended by signal 4294967295 05:01:05
231023 05010598 CASCD0154S SEP 00009 for ES PROD abended by signal 4294967295 05:01:05
231023 05010599 CASCD1071I Administration SEP created for Server PROD, process-id = 5880 05:01:05
231023 05010625 CASCD1074S Administration SEP for Server PROD abended by signal 4294967295 05:01:06

Hi

-Is this a new issue, or was this working then something changed and now you see the issue? What changed?
-Is there any error/events previous to what you shared from the console.log, in case that is causing the issue.

-This may require further in depth investigation, therefore I recommend you to consider raising a support case, please consider to gather/include the following traces:
-Enable Auxiliary trace for the affected region,
-Generate core files,
-Generate MFESDIAGS diagnostics collection just after the issue occurred, share the .zip,
-Generate runtime CTF (consolidated trace file) traces,
Please advise if you require any information regarding how to enable the above traces.

Regards,
Kim

Thanks Kim.

This suddenly started happening and the clients are not aware of any changes in the server. It does not happen every day, it's about once a week.

We have more than one client with the same issue.

We do have a ticket opened with MF support team and have provided all the tracing information listed above, but they haven't been able to help.

This is why I am trying in the community, hoping for better outcome 🙂

Thanks again.