SAP Knowledge Base Article - Preview

2486517 - SMP Server throwing 500 error with cause "Exception occurred ::: java.lang.AssertionError: null

Symptom

  • We are seeing quite a few query failures across all entity sets in SMP 3.0 server logs with the following error message.
    This causes the offline store refresh to fail on the client side, appears to be occurring randomly on all our client devices.
    The error only shows up one of the application servers

  • SMP Server Log Shows:
    2017 06 07 10:24:21#0-400#ERROR#System.err###Thread-166######### Error caused by: [-100029] Retrieve feed
    "http://xxxxx.xxxxxxxx.com:8000/com.xxxxxxxx.xxxxxx/xxxxxxx?$filter=Location%20eq%20'0530'%20and%20Route%20eq%20'86'"
    failed because the OData server returned HTTP code, 500, with message: null |

    2017 06 07 10:24:21#0-400#ERROR#System.err###Thread-166#########Caused by: [-100029] Retrieve feed
    "http://xxxxx.xxxxxxxx.com:8000/com.xxxxxxxx.xxxxxx/xxxxxxx?$filter=Location%20eq%20'0530'%20and%20Route%20eq%20'86'"
    " failed because the OData server returned HTTP code, 500, with message: null |
    2017 06 07 10:24:21#0-400#ERROR#com.sap.odata.offline.util.NativeLogger###Thread-166####f0ec8af6-4b49-11e7-8000-8eddfb307a24#####<301687>
    [-10118] Caught Java exception with type: com.sap.odata.offline.util.MODataException. |

    2017 06 07 10:24:21#0-400#ERROR#com.sap.odata.offline.util.NativeLogger###Thread-166####f0ec8af6-4b49-11e7-8000-8eddfb307a24#####<301687>
    [-10118]  Exception message: [-100027] An error occurred while processing request "oneTimeChargeStagingSet"
    (http://xxxxx.xxxxxxxx.com:8000/com.xxxxxxxx.xxxxxx/xxxxxxx?$filter=Location%20eq%20'0530'%20and%20Route%20eq%20'86'") |

    2017 06 07 10:24:21#0-400#ERROR#com.sap.odata.offline.util.NativeLogger###Thread-166####f0ec8af6-4b49-11e7-8000-8eddfb307a24#####<301687>
    [-10118]   Error caused by: [-100029] Retrieve feed
    "http://xxxxx.xxxxxxxx.com:8000/com.xxxxxxxx.xxxxxx/xxxxxxx?$filter=Location%20eq%20'0530'%20and%20Route%20eq%20'86'"
    " failed because the OData server returned HTTP code, 500, with message: null |

    2017 06 12 13:55:55#0-400#ERROR#com.sap.mobile.platform.server.online.filter.correlatedlogging.SMPCorrelatedLoggingHandler##c1243601#Thread-268##614a148b-f41a-4723-b18f-db7a9ba09142#com.xxxx.xxxxx#558c9af0-4f55-11e7-8000-ea28ef51f1c4#RequestResponse#200#{SMPARCH-5015-otp-two-factor-authentication=false, SMPSRVRUN3-841-SAML-IdP-proxy=true, SMPARCH-4846-odp-cookie-store=true}##Exception occurred ::: java.lang.AssertionError: null
    at com.google.common.collect.CustomConcurrentHashMap$Segment.evictEntry(CustomConcurrentHashMap.java:1906)

 


Read more...

Environment

  • Android 5.x app
  • SMP SDK 3.0 SP13 PL07
  • SMP Server 3.0 SP10 PL07

Product

SAP Mobile Platform 3.0

Keywords

SMP HTTP 500  system.err , KBA , MOB-ONP-OOD , SAP Mobile On Premise Offline OData Server , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.