cancel
Showing results for 
Search instead for 
Did you mean: 

Index Out Of Bounds Exception in SAP NW BPM 7.5

former_member607993
Contributor
0 Kudos

Hello All,

I'm facing an Index out of bounds exception in NW BPM due to empty records and Process is abruptly Suspended. The error logs aren't captured as part of Boundary Events.

java.lang.IndexOutOfBoundsException: Index: 0, Size: 0

Is there any way to Capture this error log and store it as part of Data object(DO) and set a notification/alerting.

index-error.jpg

Kindly provide your Inputs.

Thanks and Stay Safe,

Rajesh PS

former_member607993
Contributor
0 Kudos

Hello Experts,

Please provide your valubale inputs.

Thankyou!

former_member607993
Contributor
0 Kudos

daniel.graversen4pettifordjocelyn.dart

former_member607993
Contributor
0 Kudos

Hello Experts,

Please provide your valubale inputs. Thankyou!

Accepted Solutions (0)

Answers (3)

Answers (3)

DG
Active Contributor
0 Kudos

I thought there was a way you could enable CBMA for your BPM engine and then poll it the same way.

former_member607993
Contributor

Hello daniel.graversen

Only Adapter engine and integration engine can be enabled for component bases alert messages. I feel this should cover up in SolMan. Some pointers on this?

l

former_member607993
Contributor
0 Kudos

Let me know your thoughts daniel.graversen4 . I'm stucked here.

Thanks.

DG
Active Contributor
0 Kudos

You can see the pattern of what is using and then find the maping.

I have seen the BPM mapping gives this kind of errors if there are empty elements in it. So add some handling for fields that can become blank.

former_member607993
Contributor

Thanks for your reply daniel.graversen

I really wanted how to capture these kind of errors and notify via emails (or) store in a Data object and send as a Error response file to concern users.

Now I intervene to monitor the messages in Manage Process so as what happened in the Pipeline and I see the process is suspended. Out of bound exceptions aren't captured as part of boundary events.Should these type of errors needs logs to be increased and capture as part of SolMan?

Please provide your inputs. Thanks!

cris_hansen
Advisor
Advisor
0 Kudos

Hi Rajesh,

Have you tried to follow the recommendation from SAP Note 1753560?

Please increase the log level and see whether you can have more details about this specific issue.

Regards,

Cris

former_member607993
Contributor
0 Kudos

Thanks for your reply cristiano.hansen

But how do we capture this error log and send to a responses file or by notification. Because currently there needs an human intervention to monitor the message in Manage Process so as what happened in the Pipeline.

cris_hansen
Advisor
Advisor

Hi Rajesh,

I thought this was an exception and you were interested in checking the cause of the issue in the first place.

Raising the log level should give you the reason behind the error and how to avoid it.

About monitoring and alerting, I am not sure how to address the scenario. Maybe the online help, suggested in the SAP Note, can give you some pointers on where to start.

Regards,

Cris

former_member607993
Contributor
0 Kudos

Thanks cristiano.hansen.I tried it searching for this but in vain I really didn't get any pointers.