Error with thehive for "The service was not able to process your request"

Questions
1

Describe the issue/error/question

when run many workflow at same time, especially for the same case, will always meet the error as follow. Sometimes run 1 workflow for 1 case, will also see the error at the node of “CloseAlert”.

What is the error message (if any)?

ERROR: The service was not able to process your request

(JE 18.3.12) Lock expired. Locker 2088676684 86142955_application-akka.actor.default-dispatcher-13_Txn: waited for lock on database=edgestore LockAddr:749646804 LSN=0x440/0x3fc7d4 type=WRITE grant=WAIT_NEW timeoutMillis=500 startTime=1663140418237 endTime=1663140421443 Owners: [] Waiters: []

Please share the workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 0.184.0
  • Database you’re using (default: SQLite): default
  • Running n8n with the execution process [own(default), main]: default
  • **Running n8n via [Docker, npm, n8n.cloud, desktop app]:**Docker
2

Hey @teshcgv,

That looks like an internal issue with another application, If you are seeing that on the output from The Hive node it would be worth checking there to see if it is a known issue. Looking at the wording of the error it could be that the database is not responding quick enough to the requests coming in.

1 Like
3

@Jon Hi bro, this is the details of error:

{
"message": "500 - {"type":"com.sleepycat.je.LockTimeoutException","message":"(JE 18.3.12) Lock expired. Locker 2088676684 86142955_application-akka.actor.default-dispatcher-13_Txn: waited for lock on database=edgestore LockAddr:749646804 LSN=0x440/0x3fc7d4 type=WRITE grant=WAIT_NEW timeoutMillis=500 startTime=1663140418237 endTime=1663140421443\nOwners: [<LockInfo locker=\"713046019 86142902_application-akka.actor.default-dispatcher-18_Txn\" type=\"READ\"/>]\nWaiters: [<LockInfo locker=\"2088676684 86142955_application-akka.actor.default-dispatcher-13_Txn\" type=\"WRITE\"/>]\n"}",
"name": "Error",
"stack": "Error: Request failed with status code 500 at createError (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/createError.js:16:15) at settle (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:17:12) at IncomingMessage.handleStreamEnd (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:269:11) at IncomingMessage.emit (node:events:539:35) at IncomingMessage.emit (node:domain:475:12) at endReadableNT (node:internal/streams/readable:1345:12) at processTicksAndRejections (node:internal/process/task_queues:83:21)"
}

and last part

NodeApiError: The service was not able to process your request
    at Object.theHiveApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/TheHive/GenericFunctions.js:35:15)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/TheHive/TheHive.node.js:427:40)
    at async Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/src/Workflow.js:594:28)
    at async /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/src/WorkflowExecute.js:537:49

from error, think should be the hive issue.

4

Hey @teshcgv,

You got it, So it might not be The Hive directly and could be that the database it is using needs tweaking.

5

Hi @Jon , what should I do to avoid the error, could you give any suggestions?

Thanks

6

Hey @teshcgv,

If it was me I would be looking into why The Hive is returning that and fix the underlying issue, As a work around from the n8n side if you are sending a lot of requests you could try adding in a split in batches node and add a wait of maybe 1 second and do it in a loop to see if that helps.

1 Like
7

got it, thanks bro

1 Like