X Servlet Error: Servant is not of the expected type.: org.omg.CORBA.BAD_PARAM:
Shivani Patel
Greenhorn
Joined: Nov 01, 2001
Posts: 11
posted
0
Hi , While running the deployed application i am getting the following error. what can be the cause of problem??? org.omg.CORBA.BAD_PARAM: Servant is not of the expected type. minor code: 0 completed: No at com.ibm.rmi.corba.ClientDelegate.servant_preinvoke(ClientDelegate.java:754) at org.omg.CORBA.portable.ObjectImpl._servant_preinvoke(ObjectImpl.java:213) at com.nextgen.security._MuserHome_Stub.findByUsername(_MuserHome_Stub.java:456) at com.nextgen.security.MuserAccessBean.findByUsername(MuserAccessBean.java:64) at loginValidate_jsp_1._jspService(loginValidate_jsp_1.java:97) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:139) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.java:286) at org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:415) at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:544) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:827) at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:159) at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:286) at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:106) at com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472) at com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:1012) at com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:913) at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:499) at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:278) at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:105) at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:67) at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:123) at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67) at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:122) at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:315) at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:60) at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:313) at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:242) at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122) The flow of calling entity bean is as under: 1) loginValidate.jsp 2)com.nextgen.security.MuserAccessBean i)findByUsername 3)Entity Bean com.nextgen.security.Muser Where could be the problem here in client side or server side??? Thanks in advance.
------------------ Shivani Patel, N InfoNET Pvt. Ltd
Shivani Patel,<BR>N InfoNET Pvt. Ltd
Mazin Ghafadgi
Greenhorn
Joined: Sep 16, 2003
Posts: 1
posted
0
HI There , i have the Same Problem, i have donwload the Websphere 4.0.1 Single Advance Edition, and i have installed my EAR File, but when i run the Client to Access the EJB , i have the Same Exception Above. i have Fixed this problem by Installing the Fix Pack 4.0.3 . so i recommnded that you insatll the Fix Pack for your Websphere Version. and you problem will be Solved Completley. Have Fun Mazin Ghafadgi