MI Client overview_syncbonames.jsp Error

[Former Member]

Hi,

I had created a MI Client application ZCON6 with meRep.xml. Generated the war file and uploaded it to the Web Console. Assigned it to the my device id and lastly synchronized it. Everytime i restart the MI client, when i click on the ZCON6 application, the error as below will be shown. But if i export and run the ZCON6 application from the NWDS, the application can be run smoothly in the MI Client. What is wrong with my setting? Any help would be highly appreciated. Thanks.

Error: 500

Location: /ZCON6/jsp/overview_syncbonames.jsp

Internal Servlet Error:

javax.servlet.ServletException

at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:461)

at jsp.overview_0005fsyncbonames._jspService(overview_0005fsyncbonames.java:168)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)

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

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

at org.apache.tomcat.facade.RequestDispatcherImpl.doForward(RequestDispatcherImpl.java:222)

at org.apache.tomcat.facade.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:162)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.dispatchRequest(AbstractMEHttpServlet.java:907)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGetNotThreadSafe(AbstractMEHttpServlet.java:348)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGet(AbstractMEHttpServlet.java:689)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.service(AbstractMEHttpServlet.java:313)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)

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

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)

Root cause:

java.lang.ClassCastException

at jsp.overview_0005fsyncbonames._jspService(overview_0005fsyncbonames.java:66)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)

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

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

at org.apache.tomcat.facade.RequestDispatcherImpl.doForward(RequestDispatcherImpl.java:222)

at org.apache.tomcat.facade.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:162)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.dispatchRequest(AbstractMEHttpServlet.java:907)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGetNotThreadSafe(AbstractMEHttpServlet.java:348)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGet(AbstractMEHttpServlet.java:689)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.service(AbstractMEHttpServlet.java:313)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)

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

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)

- julius

[Former Member · Accepted solution]

Hi julius,

Check these things:

1. Is your client having more than one application (mostly one client will not work with more than one application)

2. Which jdk using your MI client (mostly works with jdk1.4)

Regards,

Murthy.

[konchada_saikrishna · Accepted solution]

Hi Murthy,

Are you sure...? only one application will work on a client. bcos in our projects we are having more than two applications.

No of applications doesn't matter, it matters with system memory & stuff. and the client is just an tomcat server.

you can use j2sdk-1_4_2_06-windows-i586-p I am using this, it worksa on PDA, Desktops, Tablet PCs.

Regards,

Sai K

[Former Member · Accepted solution]

Hi Murthy,

1. Yes, I have more than 2 applications in the MI client. Among them, there are 2 applications with the different name, but calling the almost same functions.

2. I have jdk 1.5 and jdk1.4.x in my laptop. Jdk1.4.x is use for my NWDS. How do i check that which version of JDK the MI client is using?

- julius

[rajan_venkatachalam · Accepted solution]

Hi Julius,

If you have two application in the MI client which has been generated automatically from the MDK plugin by giving the meRepMeta.xml as an input then the two application might have the same jsp names which will lead to this classcastexception.

Thanks and Regards,

Rajan

[Former Member · Accepted solution]

Hi julius,

As Rajan said if you have two application that causes an exception while firing that event.

You can check your JDK version SAP Mobile Infrastructure\startup.bat file. Edit this file and check your JDK version.

Regards,

Murthy

[Former Member · Accepted solution]

Hi Sai,

In my system if I deploy two applications even with diff. name, my client has giving the same exception. But when I delete any of the application, that was working.

Obviously PDA has less memory and more than one application will not run on PDA.

Regards,

Murthy

[Former Member]

Hi Julius,

your problem seems to be, that you have two apps using a syncBo with the same name. IF this is the case, then you really will end up in a problem. At one time you can only have one application on a device calling that BO. If you have a second one, you will end up with an exception. It is not a problem to have more then one App in MI, as longas these are using different BOs.

Create the syncBOs for the second app again with a different name. They could use the same Backend handlers, but give them just a different name, then it should not be a problem.

Regards,

Oliver