Skip to Content
0

Work Manager 6.2 - Push - Error

Jan 24, 2017 at 03:01 PM

99

avatar image

Hi All

We have an issue in the Push scenario in Work Manager 6.2. Below is the error we are facing:

2017 01 23 10:29:32#0-700#INFO#System.out###Agentry SAPWMEG1_08_22 Worker Thread#########throwExceptionToClient::com.syclo.sap.component.ZWM.steplet.ZWM_WorkorderPushSteplet::throwExceptionToClient::1011::ZWM_WorkorderPushSteplet - while trying to invoke the method java.lang.Object.hashCode() of a null object loaded from local variable 'key' | 2017 01 23 10:29:32#0-700#ERROR#System.err###Agentry SAPWMEG1_08_22 Worker Thread#########java.lang.NullPointerException: while trying to invoke the method java.lang.Object.hashCode() of a null object loaded from local variable 'key' | 2017 01 23 10:29:32#0-700#ERROR#System.err###Agentry SAPWMEG1_08_22 Worker Thread#########at java.util.Hashtable.put(Hashtable.java:464) | 2017 01 23 10:29:32#0-700#ERROR#System.err###Agentry SAPWMEG1_08_22 Worker Thread#########at com.syclo.sap.PushStepHandler.getUserGUIDs(PushStepHandler.java:313) | 2017 01 23 10:29:32#0-700#ERROR#System.err###Agentry SAPWMEG1_08_22 Worker Thread#########at com.syclo.sap.PushStepHandler.pollPush(PushStepHandler.java:195) | 2017 01 23 10:29:32#0-700#ERROR#System.err###Agentry SAPWMEG1_08_22 Worker Thread#########at com.syclo.sap.component.ZWM.steplet.ZWM_WorkorderPushSteplet.execute(ZWM_WorkorderPushSteplet.java:26) | 2017 01 23 10:29:32#0-700#ERROR#System.err###Agentry SAPWMEG1_08_22 Worker Thread#########at com.syclo.sap.Steplet.doSteplet(Steplet.java:172) | 2017 01 23 10:29:32#0-700#ERROR#System.err###Agentry SAPWMEG1_08_22 Worker Thread#########at com.syclo.sap.steplet.PushSteplet.doSteplet(PushSteplet.java:82) | 2017 01 23 10:29:32#0-700#ERROR#com.sap.mobile.platform.server.agentry.console###Agentry SAPWMEG1_08_22 Worker Thread#########Exception: 10:29:32 01/23/2017 : 20 (Agentry3), JavaBackEndError (ZWM_WorkorderPushSteplet: steplet execution failed), |

We think this is happening because of this:

getClientDeviceLanguage::Property: <<user.client.Language>> not found, returning empty string |

This method, in the user class, is called during push processing and not able to return the client language and thus Push fails.

Please help.

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

2 Answers

Bill Froelich
Jan 24, 2017 at 07:40 PM
0

The error about user.client.Language not being found would not impact your push. That error occurs with my instances as well and I have had push working still. Since you are using a custom class I would start with debugging your custom class and determine where the and exactly what the problem is. The error seems to reference a missing hash entry for key.

--Bill

Share
10 |10000 characters needed characters left characters exceeded
Mark Pe
Jan 27, 2017 at 04:03 PM
0

Ankur,

When we had this same issue with some customers, we found that <<user.client.Language>> is shown for both working and none working Pushes. But it is also seen that on working Pushes this <<user.client.Language>> was not present.

In short:

Successful Pushes: <<user.client.Language>> being blank both exist and not exist for users.

Unsuccessful Pushes: <<users.client.Language>> being blank always exist.

We have an action to the customer to check if there is something different between the devices to make user.client.Language null or blank as this is a key parameter to invoke certain conversions of calculation in the backend. But again this normally is shown randomly and this is why this issue may be a little hard.

The key when null will significantly impact your push but to determine the root cause is going to be non-trivial.

We are going to share some of our findings:

1) Overloading the system with multiple connection and violating the thread can contribute to more lost pushes as users are going to be unconnected.

2) Some of the missed pushes could be from users just not connected (check log with netmsg).

3) It may also be seen when once a Push steplet fails, the order of successful pushes (may be tied to the backend queue) may fail for all users. In short, once the failure occurs, all users may see it.

4) At this point, the findings we have on the field are inconclusive to find the root cause and we may need people who goes live onsite to determine more.

This is what I need to share and I hope it helps the team to find the root cause.

Regards,

Mark Pe
SAP Platinum Support Engineer

Share
10 |10000 characters needed characters left characters exceeded