Skip to Content
0

PI 7.4 Java Stack Connection error, Random Idoc stuck in SM58 in ECC

Aug 11, 2017 at 07:18 PM

53

avatar image

Hi All,

We are facing error in Idoc AAE setup in PI 7.4. Our outbound interface are built on Java stack. The connection works fine; however some idoc gets stuck in SM58 in ECC and throw error as 'Function IDOC ASYNCHRONOUS NOT FOUND'. I can see log entry in PI NWA logs as '[JRA] ReaderManaged_Application_Thread_46, onConfirmTID(), no Bean found for TID XXX' .

I have checked all configuration and related notes but couldn't find the issue. JCO RFC provider does not have any entry with default PID. This is only happening in production system and only with few idocs. If we try to reprocess it later, we are able to do so.

Please share your inputs.

Vikram

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Ryan Crosby Aug 11, 2017 at 07:22 PM
0

Hi Vikram,

We had something similar happen in our production system today - although a slightly different error but along the same lines. Somehow the logical system for our technical system in the production SLD got wiped out. We got the value placed back and then refreshed the SLD cache in the ID and updated the adapter specific identifiers for the business system. Once we made sure all of the information was restored we were able to send everything out.

Regards,

Ryan Crosby

Show 2 Share
10 |10000 characters needed characters left characters exceeded

Hi Ryan,

Thanks for the inputs. I checked our details in SLD and they are correct.

This issue is only happening with few idocs and does not result as permanent failure. We are able to resend it.

If this is configuration issue, all idocs should result as error in SM58.

Regards,

Vikram

0

Hi Vikram,

Yes, I would expect the same behavior, but my colleague mentioned that we were able to resend when triggering from SM58 before the proper updates were made in the SLD which was strange. Aside from that I think the logs in your PI system may give the most helpful information in this situation.

Regards,

Ryan Crosby

0