on 08-19-2013 8:48 AM
Hi All,
We have an issue with file to IDoc interface. Interface is executed and picked the file from file server and processed to PI. In PI message landed in inbound queue(SMQ2). Below are the steps we have performed to get through.
We got to know that due to system performance queue is executing slow. One of the priority message which was also landed in the same queue and waiting for its time (its almost last entry in the queue). Now we identified a concept called message prioritization to fix the issue in future.
Our question is - as messages are executing in a sequence, do we have any possibility to execute the particular entry in the queue by excluding the current message order?
Thanks in advance...
Anusha.
Hi All,
Thanks for your valuable responses. Currently there are about 20000 messages are on top of the required message. In my case saving the top messages in LUW is may not be a suggestible approach. Even if it is acceptable selecting each and every message and saving in LUW may cause the inconsistency.
Anyway as this issue is due to system performance, customer is OK with the delay in process.
As suggested, in future we would like to incorporate queue prioritization for very high priority interfaces so as to avoid such situations.
Thanks
Anusha Penneru
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As of now you for this Queue you can save the first message which is processing longer time now to allow all other messages to flow.
To over come this issue in Future please implement the Queue Prioritization at SXMB_ADM.
You have High Priority , Low Priority and Large message Queue.
if you define all your high priority interface messages under high priority and lease priority ones under low priority and for large messages please assign large message queue to improve the performance.
Thanks
N N
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Anusha,
This is not possible. Moving the LUW to SMQ3 is used when the queue is stuck due to system error and the other messages can move. Here there is no error but system performance issues which you have already identified and taking remedial actions for.
cheers,
Ambrish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anusha,
Our question is - as messages are executing in a sequence, do we have any possibility to execute the particular entry in the queue by excluding the current message order?
AFAIK , We can't . But we can temporarily suspend / stop message processing by moving LUW to smq3 (SAVE LUW) and execute after some time.
Regards
Hari.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
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.