ECONNRESET Error in Batch Server - General Discussion - Sage X3

相关文章推荐

英俊的海龟 · 火焰纹章中文版-火焰纹章中文版促销价格、火焰 ...· 2 周前 ·

大方的炒饭 · 生活情報・多言語対応インフォメーション - ...· 3 月前 ·

茫然的青椒 · 机械工程学院· 4 月前 ·

豪情万千的松鼠 · javax.validation.Unexp ...· 1 年前 ·

爱运动的打火机 · java ...· 1 年前 ·

Sage X3

Welcome to the Sage X3 Support Group on Sage City! Available 24/7, the Forums are a great place to ask and answer product questions, as well as share tips and tricks with Sage peers, partners, and pros from around the globe.

General Discussion ECONNRESET Error in Batch Server

We are on V12 Patch 22, Syracuse 12.7.6.2 and regularly (2 or 3 times per day) experiencing an error with the batch server where tasks fail with an ECONNRESET error. If this is a recurring task, we have to manually re-start the task with the 'Follow-up recur entry' menu on the Usage->Request Management screen. Otherwise the task never recurs.

The task log always looks like this:

The Syracuse log always contains the following error:

This error only occurs with the batch server. User sessions are all OK.

Any ideas?

Thanks,
Martin

Hi Simon,

You have seen a huge improvement by using additional Process Servers, in your case. As pointed out to you your sizing is a major issue for your particular customer.

Regards,

Renier

We installed V12 p23 last weekend, together with Syracuse 12.8.2.2, MongoDB 4.0.18 & runtime 93.1.17 and, so far, we haven't had the issue since the upgrade. Of course, it's only 4 days ago so too early to say for sure that the problem has gone away...

What level of Syracuse and MongoDB are you on?

Thanks for the reply. I have Mongo 4.0.18, and for Syracuse, I have 12.8.0 installer, and X3 reports 12.8.0.44-0.

I downloaded the P23 files from the KB page a while back, and didn't notice when we did the update that the runtime and adxadmin had been updated. I applied the updated versions last night which ultimately didn't help. At this moment I can't access the P23 KB article at all to see if I can get 12.8.2.2.

I did end up installing Syracuse 18.2.2 and runtime 93.1.19, but it didn't help. Our issue seemed to be more related to the total number of runtime connections; when it got above a certain number the crashes would start. I added an additional process server as well as adding some memory to the main runtime server, and thusfar the crashes have stopped.

Did you see https://support.na.sage.com/selfservice/viewdocument.do?externalId=105883 "Batch Server Tasks increasingly failing with ECONNRESET errors" ?

There is also possible issue with windows heap sizing, which I'm just about to write up, although would expect interactive users to also have ECONNRESETs in this case

Bonjour,

Il s'agit d'un véritable problème connu chez et l'information ne circule pas. Bref, la solution est la suivante, il s'agit d'une clé de registre sur le serveur de traitement qu'il faille actualiser, puis redémarrer le serveur.

Bon courage (et j'attends mon café, car je viens de vous sauver du temps déjà pas mal perdu )

"There is also possible issue with windows heap sizing, which I'm just about to write up" I did write this up and it is documented in the article: Batch Server Tasks fail with ECONNRESET errors . Sorry for not updating this thread before.

In fact, if you search the Sage Knowledge base for "ECONNRESET batch" you will find both the articles I mentioned...