on 06-08-2018 7:35 AM
Hi,
on PO 7.5 we pick up several large files (~50MB) by a Standard file Adapter using NFS and send it via SOAP to a SAP system. When it comes to processing the files some files (3-5) get processed very quickly < 5 minutes but most of them (~10) take more than 2 hours. We have 4 Java nodes active and message prioritzation for these Messages is active. Any idea what might be the reason and how to fix it?
Best regards.
Oliver.
Hi,
the problem vanished after some time and did not happen again. Nobody knows why and of course nobody has changed anything. So hopefully it will be gone and stay away.
BR
Oliver
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Oliver,
Are you seeing long processing message? Or is adapter processing taking very long time?
Is there OOM error occurring?
Best regards,
Tom
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tom,
there is no error at all. That's what makes it hard to find the issue. The adapter is not processing too long. Once the Messages receive the adapter they get processed right away. It's somewhere before the adapter in the message processing queues.
BR.
Oliver.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Oliver,
In case of a PO system, a file(s) is picked by File sender channel, then put to messaging system (message is generated), waits for dispatch, then gets processed (pipeline, mapping, receiver channel, etc).
According to your description, I assume it's in the step "waits for dispatch" - but in this case, you'll still see some clue (e.g., delay) in message log. But of course it's not going to be an error trace.
If you are seeing the delay without seeing any message generated, it means the stuck is in sender adapter processing.
Nevertheless, you can firstly check the Adapter Engine config:
##1623356 - "To be delivered" messages in Adapter Engine
You can also check Adapter Engine Status (Queue status) according to this note.
A thread dump would also help you identify the stuck point
Best regards,
Tom
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.