Urgent - Unprocessed messages kill performance and J2EE.

[Former Member]

Dear experts,

We have a live XI system with which we have the following issue. During go-live a great number of messages have been sent through XI. A lot of them did not compute well. Some were missing essential data, etc.

After a while the inbound queues were emtpy and all looked well. However, every so many hours user BACKGRJOBS then suddenly puts thousands of files in the inbound queue and let's it run. These are messages from days ago. Many of them have status "Manual restart". After this, J2EE is struggling to work. File adapters stop working, etc.

And afterwards, the inbound queue is empty again.

Where are these messages stored? As they do not seem to appear in the inbound queue, but then suddenly are put in by the BACKGRUSER.

And how can I stop it from killing J2EE?

Kind regards.

[Former Member · Accepted solution]

Hi,

The performance of your J2ee engine is degrading due to large volume of data you are trying to reprocess at the same time.

These data are persisted in the database and the background job is trying to reprocess it.

You can do following things :-

1) wait for some time if the messages are reprocessing

2) If the server performance is poor then you will have to restart the J2EE side.

3)Schedule the job so that it can pick lesser number of files.

4)You can also cancel the failed messages from SXMB_MONI and resend the files.

Regards

Amitanshu