Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Error while accessing Odata webservice in Hybrid application

Hi Experts,

We are facing the below errors in our SMP logs. The application is working fine, and all relevant data is coming as expected. Although these errors are recurring, and server logs are building up. Note that if we enable logger plugin to upload the logs, the same errors(especially 1. below) are uploaded, and creating unnecessary traffic as well.

  1. 2015 07 06 16:24:57#+0300#ERROR#com.sap.mobile.platform.server.online.filter.correlatedlogging.SMPCorrelatedLoggingHandler##anonymous#http-bio-8081-exec-7####2a053b97-3f00-41ec-bd92-ddc13837688b#<<app-id here>>#null#error#Other#nosec_identity#null#d3fd66c1-0781-4b17-a50d-4968064b0cfb#null#1436178297795#null#com.sap.mobile.platform.server.online.filter.correlatedlogging.SMPCorrelatedLoggingHandler:doFilter#Exception occurred :::  while trying to invoke the method java.io.PrintWriter.write(java.lang.String) of a null object loaded from local variable 'outWriter'java.lang.NullPointerException: while trying to invoke the method java.io.PrintWriter.write(java.lang.String) of a null object loaded from local variable 'outWriter' com.sap.mobile.platform.server.online.filter.application.SMPInternalConnectionRedirectFilter.rewriteResponseUrls(SMPInternalConnectionRedirectFilter.java:124) com.sap.mobile.platform.server.online.filter.application.SMPInternalConnectionRedirectFilter.doFilter(SMPInternalConnectionRedirectFilter.java:107) sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:606) org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319) org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56) org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60) ..........

  2. 2015 07 05 13:58:53#+0300#ERROR#com.sap.mobile.platform.server.online.filter.application.SMPOnPremiseApplicationSettingsHandler##anonymous#http-bio-8080-exec-17####9cd5d2bf-6fef-42ed-bcac-214ac4f87f84#<<app-id here>>#null#error#Other#null#null#5469d27f-be68-442d-b47e-3d18f5443f8d#null#1436083133668#null#com.sap.mobile.platform.server.online.filter.application.AbstractSMPApplicationSettingsHandler:doFilter#Unauthorized#null#786#ApplicationSettings#1436093933590000#401 |
    Note that this does not affect the data read on the device. We have followed the default logic of pointing to sap(No Authentication Filter) namespace while publishing the web-service and marked the web-service as Internal in the settings. We are using SMP SP07 PL02, and this still requires the SMP admin user credentials to access this webservice(over browser that is. In our application we are passing the username and password from the registration application context in the header.)

  3. 2015 07 05 14:53:08#+0300#WARN#com.sybase.security.ldap.LDAPLoginModule##anonymous#http-bio-8080-exec-64###Attempt to set maxActive configuration option of the LDAP connection pool ignored. A maximum of one attempt to set this option with a non-default value is allowed during the lifetime of the pool. |

    2015 07 05 14:53:08#+0300#WARN#com.sybase.security.ldap.LDAPQueryHelper##anonymous#http-bio-8080-exec-64###[LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1 ] javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1 ]
    at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3087)
    at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033)
    at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2835)
    at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749)
    at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:316)
    at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193) ...

    These are warning, although these keep building up in the logs, and aking up lot of space. Kindly adivce what could be the root cause. We are using LDAP Authentication in our application.

Thank you in advance.

Cheers,

Vigil

Tags:
Former Member
Not what you were looking for? View more on this topic or Ask a question