Error Message Successful when restarted from SXMB_MONI

[kesavadas_thekkillath]

Hi Experts,

My scenario is as follows:

Few inbound message(s) reaches our system with PGP encrypted content( in time span of 5 seconds around 3 messages are reached ), Once its in, the message is decrypted by an UNIX external command( program logic ) which triggers the PGP encryption/decryption, after decryption the XML tags are decoded and the business logic is performed.

All the test scenario's worked fine in Development landscape. In Quality landscape few messages are stuck in Error status then and there indicating that the decryption failed( Reason: external command execution, cannot be decrypted ), when we restart those manually, it gets processed without any issues. Why is it happening like this ?

Please help me with some hints. I am basically not from PI background. 🙂

Regards

Kesav

[former_member184720]

Not sure how/where you are executing the UNIX command in your interface

However as it failed in the sxmb_moni transaction,

open the message -> on the left hand side, you should be able to see inbound message -> expand soap header -> Trace

Open that and search for the text "Error"

You should notice the error message which should explain why the message failed.

[kesavadas_thekkillath]

Hi Hareesh,

Thanks for your response

The Unix command is executed inside a badi and it is working well in stand alone from SM49 and also when I manually test it from SPROXY.

I did the same thing you have suggested already, the message indicated is "cannot decrypt........failed".

Suppose there are 3 messages with the same error reason and when I restart it manually then there are no errors.

Would it be due to resource handling or queuing or getting processed in parallel or system parameters or PGP multiple threads ? Me thinking ... Why it works when we reprocess it manually

Kesav

[former_member184720]

>>>Would it be due to resource handling or queuing or getting processed in parallel or system parameters

It could be. May be try changing the Quality of service to EOIO and see if that helps.

Are you restarting one after the other or all at one go??

[kesavadas_thekkillath]

That's a good hint 🙂

I'll trouble shoot it and update here ... Thanks by the way

Kesav

[kesavadas_thekkillath]

Hi,

The root cause was identified and the problem is solved now ( issue was not related to PI 😉 )

There were 2 instances available in quality landscape running in the HEC environment( whereas only one in DEV ), The business logic relies on few directory paths created in application server ( the paths were only existing in one server instance ), the incoming entry from PI was choosing the instance based on load balancing and the entry was being executed in the instance where the paths were not existing, the standard code was raising a message which was very deceiving and generic, this resulted in such effort for identifying the root cause. There will be an OSS note released in due course for exact error message capturing.

Thanks for your effort.

BR

Kesav