Skip to Content
0

Agentry Error Handling - Occurs in all transaction issue

Mar 02, 2017 at 01:48 PM

182

avatar image
Former Member

Hi All,

Im facing an issue with error handling in Agentry. Though i have error handling steps in only some of the transactions, the error handling pop up is coming up for other transactions that has no error handling step added to it. This would allow the users to click "Continue" and skip that transaction which is causing an issue.

We are using the latest SMP server. Do we have any specfic configuration to restrict the error handling to come up only on the transactions that has error handling steps?

Please help as this is affecting many scenarios

Thanks in advance

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

3 Answers

avatar image
Former Member Mar 03, 2017 at 03:57 PM
1

Thanks all for the replies..

I have figured a way to do skip the error handling pop up.

Whenever there is an exception captured in the update step, in the respective java steplet i have added

this._useNewErrorHandlingMethod = false;

before the "throwExceptionToClient" method.. This would ensure that the error handling pop up is not triggered and just stops the sync in the transmit screen. So user is forced to discard the object or clear user data to avoid that pending transaction

Since "_useNewErrorHandlingMethod" static variable, if you need the error pop up for certain transactions then set

this._useNewErrorHandlingMethod = true;

along with Error handling step in the agentry to throw the pop up with user having the option to abort or continue.

-Karthik

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

Thanks for sharing - Karthik.

Regards,

Mark Pe
SAP Product Support

0
avatar image
Former Member Mar 03, 2017 at 09:33 AM
0

Hi

I did not use error handling step for transaction but i would like to ask about 'apply step' after transaction. Do you use one apply step for those two transaction as you mentined?

Share
10 |10000 characters needed characters left characters exceeded
Mark Pe
Mar 03, 2017 at 03:15 PM
0

Karthik,

Can you provide more information about how you setup your Error handling? There are two or three different techniques (General) that one can use and we wanted to know if you are using strictly the following:

a) Agentry.ini - Error handling setup.

b) Java based Error handling + Editor Transaction Error handling steps.

c) Work Manager Inbound Queue Management.

I am guessing b but just in case you are using a, that may be the issue as it applies to all and you need to focus on b.

If you are using B. please provide a snapshot of your Error handling step in the editor so we can in SAP can review.

Best Regards,

Mark Pe

SAP Product Support

Show 3 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Yes Mark, you are correct. Im using the option B.

I have configured in the Agentry.ini as follows

enableTransactionFailureHandling=True
failedTransactionFilenameFormat=%{userid} %{transaction_name} %{date} %{time}-%{count}.xml failedTransactionsQueue=FailedTransactionsQueue

In Agentry transaction steps - i have added the error handling steps for the required transactions.

The java steplet for error handling would returns true. And i have set in Agentry error handling step to "Stop" - "If steplet returns true".

I was expecting only the transactions where i have added the above Error Handling Steps to trigger the error pop up message with user option to continue/abort. But it also happens for other transaction where there is no error handling steps. Because of it user able to remove the pending transactions on clicking "Continue". Even "Even "Fatal with Message- Always Stop" - removes the pending transaction when user clicks the "Stop" button.

So in order to avoid the error handling pop up, i have done a work around as i mentioned in the other reply to this question. But if there is a better solution, it would help me to build the logic for different error handling scenarios.

capture.png (40.9 kB)
0

We will try to do an internal report with our dev team to investigate this further if we can find the root cause.

Regards,

Mark Pe

SAP Product Support

0

To Karthik and all,

As a follow up to this and based on the internal review of the code with the development team + the statement of the workaround above, the decision made by the SAP development team is not to further optimize or enhanced the older feature Fatal with message error type. With this stated, the documented workaround by Karthik will be the official workaround by SAP and any of the SAP user/customers regarding this issue. So kudos to you Karthik, for getting the workaround that we may have to follow. Expect users from different areas to reach out to you for your expertise.

Best Regards,

Mark Pe
SAP Platinum Support Engineer

0