Error Generate DocumentNo TimeOut

[Aldo]

Hi everyone,

I got this Error Generate DocumentNo TimeOut (pic attached) occasionally. I don't really know the cause but that error made the users can't input any new document and only can be solved by restarting the Idempiere.

I will explain about my setup. I install the idempiere on a server and put my own scripts / services on another server. The scripts are used to get the data using Idempiere Web Services and input (or create) new orders. The Idempiere itself is still accessible for manual input.

Does anyone have any idea about the cause and how to solve it so it won't happen?

Thank you for any help you can provide.

[Carlos Antonio Ruiz Gomez]

Hi Aldo, the most common case I've seen for this error is problems in plugins not committing, or not closing properly a connection, or a prepared statement or a resultset.

Regards,

Carlos Ruiz

El 24/06/20 a las 11:33 a. m., Aldo escribió:

--

[Aldo]

Hi Carlos,

Thank you for your response. Is there any relation with the possibilty that my scripts might send new request while the previous request hasn't properly ended?

I'm planning to use message broker such as ActiveMQ to handle the queue and send the request one by one.

Is it fine to send multiple request of different types together such as input (or create) together with query data?

Or should i send only 1 request at a time?

Best Regards,

Aldo

[Alan Lescano]

Hi,

I,ve seen this error when a (slow) process called MSequence.getDocumentNoFromSeq() and did not commit the transaction before the slow/long part. That method uses "for update", which locks the selected row against concurrent updates. When another process tries to call that method, a timeout may rise.

Alan

--
You received this message because you are subscribed to the Google Groups "iDempiere" group.
To unsubscribe from this group and stop receiving emails from it, send an email to idempiere+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/idempiere/6c7f2aac-bc2e-4cf1-bd95-c81ede61d62bo%40googlegroups.com.

[Syed]

Alan is correct.

Based on my experience, better disable immediate posting of accounting processor if it is disabled so the process can complete in a short time hence you won't get this timeout error due to concurrent load.

Regards,

Syed.

To unsubscribe from this group and stop receiving emails from it, send an email to idem...@googlegroups.com.

[Aldo]

Thank you Alan and Syed for the replies.

I'm trying to disable the immediate posting and see if the problem will still occur or not.

Regards,

Aldo

[Paolo Formaro]

Hi,

I'm having similar behavior , closing the document with Immediate Posting takes long time (it doesn't timeout) but only when connected trough the NGINX proxy.

Apparently disabling Immediate Posting gives better result when using the NGINX proxy.

Accessing directly to iDempiere , without passing trough the NGINX proxy, seems to work perfectly with or without Immediate Posting activated.

I had this problem before but then it has been fixed, I think this issue re-appear when I rollback to 7.1 (previously I was working with master branch).

@Aldo any progress with your tests?

[Aldo]

Hello,

Sorry for the late reply since I have been busy.

Based on my test, it was still happened. So I changed my environment by adding message broker before sending the request to Idempiere.