ats

The easist way to make it working is to patch webpack.config.js generated by Angular CLI.

Create web3-patch.js file in root folder of your app.

The problem seems to be with root-logger and level DEBUG, I just take back that level to INFO and this problems fade away.

The real problem seems to be something related with hibernate log, but no idea what is exactly.

This is a workaraound but I could also use DEBUG level.

standalone.xml

The @Transactional interceptor priority is defined by specification to be Priority.PLATFORM_BEFORE+200. The fault tolerance interceptor priority is defined by specification to be Priority.PLATFORM_AFTER+10. So if the @Transactional interceptor fails after its InvocationContext.proceed(), which is the case when the error happens during commit, then the fault tolerance interceptor is long gone and no retry can possibly happen.

The fault tolerance interceptor priority can be changed by defining a configuration property mp.fault.tolerance.interceptor.priority, if there's a need. But by default, what you observe is the intended behavior, as far as I can tell.

primary is a reserved SQL keywork, see SQL Key Words

You should use a different column name, you can use @Column(name="primary_color") for this.

When you are indexing the child document, the name for the field for the join data type is written wrong. It should be "join_field" and not "join_filed"

Update your child document as shown below

Create an attachment and set the PR_ATTACH_CONTENT_ID property (DASL name "http://schemas.microsoft.com/mapi/proptag/0x3712001F") using Attachment.PropertyAccessor.SetProperty.

Your HTML body (MailItem.HTMLBody property) would then need to reference that image attachment through the cid:

In the PERFOM UNTIL... loop, you are reading BASEBALL-FILE-OUT, instead of the sorted BASEBALL-FILE-SORTED.

ARE-THERE-MORE-RECORDS = 'NO' is still true from its use in the input procedure. At the beginning of the output procedure, insert MOVE 'YES' TO ARE-THERE-MORE-RECORDS. You also need to replace the READ BASEBALL-FILE-IN with RETURN SORT-FILE, add some fields to SORT-RECORD, and use those fields for the report.

Why do you have BASEBALL-FILE-UNSORTED-IN? It doesn't have any of the fields you need to move to SORT-RECORD.

If you want to use BASEBALL-FILE-UNSORTED-IN, then don't use an input procedure. Instead change the SORT statement from INPUT PROCEDURE 120-SORT-INPUT-PROCEDURE to USING BASEBALL-FILE-UNSORTED-IN. Do not OPEN or CLOSE the file. That will be done by the runtime. Remove the 120- and 130- paragraphs.

Comment everything associated with BASEBALL-FILE-IN, except 01 BASEBALL-RECORD-IN and its data items. That effectively allows the BASEBALL-RECORD-IN data definition to be used as a replacement for SORT-RECORD. That reduces the number of changes that are needed.

SORT is not being used correctly. The report is being printed in 120-SORT-INPUT-PROCEDURE using the fields from BASEBALL-RECORD-IN. It should be printed in 130-SORT-OUTPUT-PROCEDURE using the fields from SORT-RECORD.

Furthermore, no records are sorted because there is no RELEASE statement in the input procedure. To access records after the sort, a RETURN statement is used in the same manner as a READ statement for a sequential file.

The input procedure should be used to move the data from selected records to the sort record, after which the record is released to sort.

The output procedure may then used to produce a report from the sorted data by returning and printing each record until the there are no more sorted records.