File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
Win a copy of Clojure in Action this week in the Clojure forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

java.lang.VerifyError: Incompatible object argument for function calify

 
Dushyant Agarwal
Ranch Hand
Posts: 75
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I am developing a JSF+EJB3.0 application using Jdeveloper 10.1.3.3 and JBoss4.2.1. JDK 1.5 is being used with JBoss as well as JDev.

On Deploying my jar file into the server/default/deploy I get the following exception.
java.lang.VerifyError: Incompatible object argument for function call

What might have been the reason for this???

I also came to know that this is an unremoved bug in the JDK 1.5 & that it can be by-passed by passing the -noverify parameter to the JVM.
IF so how can we pass a parameter to the JVM while deploying the .jar file???
 
Jaikiran Pai
Marshal
Pie
Posts: 10444
227
IntelliJ IDE Ubuntu
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Please post the entire exception stacktrace.

I also came to know that this is an unremoved bug in the JDK 1.5 & that it can be by-passed by passing the -noverify parameter to the JVM.


Any reference for this? JVM parameters can be set in the run.bat file. Look at the line where JAVA_OPTS are being set in that bat file.
[ November 18, 2007: Message edited by: Jaikiran Pai ]
 
Dushyant Agarwal
Ranch Hand
Posts: 75
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
The Details of this bug can be found at
http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=eb3fcd8f72ab4713f96e378a7575?bug_id=6614974

Till now I have only been able to bypass it by giving the following command in the command prompt :-

java -noverify -jar run.jar

to start the JBoss server.

But I want to implememnt giving this argument (-noverify) to the server at application level.

Also I have not been able to figure out a way to cofigure TopLink in JBoss.
 
Jaikiran Pai
Marshal
Pie
Posts: 10444
227
IntelliJ IDE Ubuntu
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
But I want to implememnt giving this argument (-noverify) to the server at application level.


That parameter is a JVM level parameter and since the JVM represents the entire server, you cannot set this parameter at application level. This will have to be system-wide.
 
Jaikiran Pai
Marshal
Pie
Posts: 10444
227
IntelliJ IDE Ubuntu
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Dushyant Agarwal:

The Details of this bug can be found at
http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=eb3fcd8f72ab4713f96e378a7575?bug_id=6614974



That bug is for JDK 1.6. You are using JDK 1.5. You shouldn't be seeing this error, unless you are using Java6. Can you post the contents of the server.log file?
 
Jayesh Vora
Greenhorn
Posts: 2
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
With JBoss 5, JDK 1.5.0_10, we were facing similar issue with our EAR application. While calling a Remote API from a Portal application, it throws following Error:
java.lang.VerifyError: (class: <some class name>,
method: doResume signature: ()V) Incompatible argument to function

This error was observed only when we enable separate classloader for the EAR application, by using following jboss-app.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<jboss-app>
<loader-repository>
com.savvion:loader=myapp.ear
</loader-repository>
</jboss-app>

We found that there were two issues involved:
1. One particular class (our own class) was present in System classpath as well as within the EAR file. Once we removed this class from EAR file and just kept one copy of it with System classpath, things worked fine.
2. The default class loading behaviour with JBoss is parent-last, which is good for Web applications but not for EAR applications. Thus for our EAR application, we changed jboss-app.xml as follows:
<jboss-app>
<loader-repository>
com.savvion:loader=myapp.ear
<loader-repository-config>
java2ParentDelegation=true
</loader-repository-config>
</loader-repository>
</jboss-app>

With these two changes, now it works fine.
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic