| Author |
Incompatible object argument for method call
|
punna Kumar
Ranch Hand
Joined: Feb 28, 2005
Posts: 80
|
|
Hi, i am getting the following error wile running the soap client,we upgrade WAS4.0 to WAS 5.0 after upgradation i am getting this error plz help asap [Attributes={}] [faultCode=SOAP-ENV:Server.Exception:] [faultString=(class: b2b/NotificationService, method: notification signature: (Ljava/lang/String Ljava/lang/String Incompatible object argument for method call] [faultActorURI=/test/servlet/rpcrouter] [DetailEntries= [(0)=<stackTrace>java.lang.VerifyError: (class: b2b/NotificationService, method: notification signature: (Ljava/lang/String Ljava/lang/String Incompatible object argument for method call at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java(Compiled Code)) at org.apache.soap.rpc.SOAPContext.loadClass(Unknown Source) at org.apache.soap.server.http.ServerHTTPUtils.getTargetObject(Unknown Source) at org.apache.soap.providers.RPCJavaProvider.locate(Unknown Source) at org.apache.soap.server.http.RPCRouterServlet.doPost(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110) at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174) at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313) at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116) at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283) at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42) at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:974) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:555) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:200) at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:119) at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:276) at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71) at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:114) at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186) at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334) at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56) at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:618) at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:439) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593) </stackTrace>] ] [FaultEntries=] Rgds, punna
|
 |
punna Kumar
Ranch Hand
Joined: Feb 28, 2005
Posts: 80
|
|
any idea please replay asap
|
 |
Harish M
Greenhorn
Joined: Aug 13, 2005
Posts: 8
|
|
Guess so you may have a JDK compatibility issue.Try sync up JDK versions on the client side.Not sure. [ August 15, 2005: Message edited by: Harish M ]
|
 |
William Barnes
Ranch Hand
Joined: Mar 16, 2001
Posts: 984
|
|
|
There is another forum which deals with Websphere, maybe try there.
|
Please ignore post, I have no idea what I am talking about.
|
 |
 |
|
|
subject: Incompatible object argument for method call
|
|
|