Member Avatar for mydreamgirl

My source code runs fine in IBM RAD. When I tried to run it in JBuilder, I encountered an error "Incompatible object argument for function call" while running a JSP file. Any idea how to handle it? See details below:

012-06-16 10:20:48 - Ctx( ): Exception in: R( + /FileUploadAction.jsp + null) - javax.servlet.ServletException: (class: whoznextdoor/CommonsFileUploadServlet, method: UploadFile signature: (Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)V) Incompatible object argument for function call

at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:508)

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:812)

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

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:662)

Root cause:

java.lang.VerifyError: (class: whoznextdoor/CommonsFileUploadServlet, method: UploadFile signature: (Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)V) Incompatible object argument for function call

at _0002fFileUploadAction_0002ejspFileUploadAction_jsp_0._jspService(_0002fFileUploadAction_0002ejspFileUploadAction_jsp_0.java:92)

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

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

at org.apache.jasper.servlet.JspServlet$JspCountedServlet.service(JspServlet.java:130)

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

at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:282)

at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:429)

at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:500)

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:812)

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

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:662)
  • 1 Contributor
  • 1 Reply
  • 476 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by mydreamgirl

Dani AI

Generated

For : this exception is a JVM bytecode verification failure (VerifyError) that means a method call in the deployed classes does not match the types the verifier expects at runtime. That usually comes from a classloader or binary mismatch — for example, the webapp was compiled against one copy/version of servlet or library classes but the container is loading a different copy at runtime. Different IDEs (RAD vs JBuilder) often expose different classpaths or server libraries, which explains why it worked in one environment and not the other.

Actionable checklist (in order of likelihood):

  • Remove any servlet API JARs from WEB-INF/lib. The servlet classes must come from the application server/container, not the WAR.

  • Look for duplicate copies of libraries (commons-fileupload, commons-io, or any custom classes) between WEB-INF/lib and the server's lib directory. Remove duplicates so each class is loaded once.

  • Ensure the project’s compile target and the runtime JRE/JDK match (no newer bytecode level compiled against an older JVM).

  • If using a build tool, mark servlet API as provided so it is not packaged. Example (Maven):

    <dependency>
  <groupId>javax.servlet</groupId>
  <artifactId>servlet-api</artifactId>
  <version>2.5</version>
  <scope>provided</scope>
</dependency>

  • Avoid instantiating or calling servlet class methods directly from a JSP. Move upload handling into a servlet (doPost) and forward to it. Example patterns:

    <%-- forward to mapped servlet --%>
<%
  request.getRequestDispatcher("/upload").forward(request, response);
%>
    public class UploadServlet extends HttpServlet {
  protected void doPost(HttpServletRequest req, HttpServletResponse resp)
      throws ServletException, IOException {
    // handle multipart with commons-fileupload or servlet 3.0 API
  }
}

If the error persists after the above, rebuild a clean WAR and inspect it (unzip or jar tf) to verify no unwanted JARs are included, and enable verbose classloader logging or use javap on the compiled class to compare method signatures. These steps address the common root causes and usually resolve the "incompatible object argument" VerifyError seen when moving between different IDE/server setups.

Member Avatar for mydreamgirl

I tried to google this error and found some people had this kind of exception before. However, it is not clear of how to resolve this error. Please help if you can.

mydreamgirl

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.