My Oracle Support Banner

Getting Time Out On Load Testing (Doc ID 2625692.1)

Last updated on JANUARY 03, 2020

Applies to:

Oracle Documaker - Version 12.6 and later
Information in this document applies to any platform.


On : 12.6 version, Enterprise Edition

Getting Time out on load testing

We are facing one peculiar issue here. On loan testing we found enormous no of timeouts in DWS Publishing service. On further investigation, we found that this issue will happen only if there a concurrent request coming to server.

To explain this better, Westpac has got documaker in a clustered environment, 2 sets of managed servers and 2 ODEE installation on those boxes. There was a load testing happening with 500 concurrent users logging to OBP and subsequently requesting doc publishing to documaker at various integration points. When the load test happens on a fully clustered environment, we are getting time outs for 30% of transactions whereas we see all the transaction processing pretty well with an average time of 5 secs when we keep one node and one ODEE instance down. So, this is definitely not a documaker upscaling\tuning issue

But curious thing is that even though we see timeout, in a clustered environment when there is a concurrent request, we can see the documents getting generated with 999 status in dashboard. This means that doc generation is completing without any issues, but somehow the receiver response queue is not delivering the response to the correct socket connection. Some mixing is happening on the queue. We use ODEE 12.6.0 here with all distributed queue.

The issue has the following business impact:
Due to this issue, users are getting time outs.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.