on 12-04-2014 12:07 PM
Hi experts.
We have here at my company an PI 7.02 SP11 only to GRC NFe 3.10 (Brasil).
Sometimes, we go to SMQ2 queue as see a lot of entries, and it is necessary restart it manually.
We do not have performance problems and PI is runnig fine.
Have experts any idea what should we do to avoid this manually restart?
Thanks
Marcos
Dear Marcos,
As per my knowledge SMQ2 picks up LUWs from SM58 (tRFC) where all the LUWs are processed in a bunch (not in a sequence). So they are coming to SMQ2 in a bunch. So I believe if the package per queue be maintained correctly, then the queues will get processed fast. You can get the reference to this maintenance of package per queue by searching in SDN.
Regards,
Souvik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Marcos,
I usually see this problem when the PI 7.0 system or the endpoint is restarted, also when the target system is not reachable temporally, later the SMQ2 queue is stuck.
Hope this helps.
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Marcos,
You can schedule the ABAP report RSQIWKEX as a job to restart the stuck LUWs automatically.
regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Marcos,
The queue entry usually indicates the nature of error.
Please get into the queue. Select the first entry (which should be in red background), double-click on it.
If it is an XML message that is in error, you will be taken to traces of pipeline steps. See if you can find a button similar to Error Information. That should tell you why the entry failed.
regards
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.