Skip to Content

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

Problems while running xMAM within NWDS

Hello,

I figured out a strange problem with my NWDS (7.0) and xMAM30:

Running the application directly over my MI client works fine.

Starting the application from within my IDE (NWDS 7.0) results in the following error message:

java.lang.NullPointerException

at com.sap.mbs.mam.bo.impl.Mam090ManagerImpl.getMam090s(Mam090ManagerImpl.java:110)

at com.sap.mbs.mam.cstm.process.impl.UserCustomCache.getUserCustomizing(UserCustomCache.java:60)

at com.sap.mbs.mam.cstm.process.impl.UserCustomProcessImpl.getUserCustomizing(UserCustomProcessImpl.java:64)

at com.sap.mbs.mam.cstm.process.impl.GenericCustomCache.getMamScenario(GenericCustomCache.java:72)

at com.sap.mbs.mam.cstm.process.impl.GenericCustomCache.getDeviceSettingsProfile(GenericCustomCache.java:115)

at com.sap.mbs.mam.cstm.util.DateTimeUtils.getDeviceSettingsProfile(DateTimeUtils.java:184)

at com.sap.mbs.mam.cstm.util.DateTimeUtils.getDateFormat(DateTimeUtils.java:84)

at de.dataone.infracor.werkstattbuch.MyFrontServlet.init(MyFrontServlet.java:103)

at javax.servlet.GenericServlet.init(GenericServlet.java:258)

at org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317)

at org.apache.tomcat.core.Handler.init(Handler.java:215)

at org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:296)

at org.apache.tomcat.core.Handler.service(Handler.java:254)

at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)

at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:806)

at org.apache.tomcat.core.ContextManager.service(ContextManager.java:752)

at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:213)

at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)

at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)

at java.lang.Thread.run(Thread.java:534)

I debugged it and figured out that the SyncBoDescriptor for MAM30_090 is null.

I think this behaviour is really strange, because the application works fine when starting it directly over the Mi client, as mentioned above.

I am using

MOBILEENGINE_JSP Version 70150

DB2E912

XMAM30 Version 3.0500 with Patch 01

Any suggestions?

Best Regards,

Anika

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