Error List

Error List for the ‘Java’ Category

Ant runs into an infinite loop/throws an OutOufMemoryError

Applies to:
Ant, Mac OS X

Description:
Occurs while compiling project under Mac OS X

Cause:
Apple’s Java VMs reside in /System/Library/Frameworks/JavaVM.framework/Versions/X.Y.Z and JAVA_HOME will usually be something like /System/Library/Frameworks/JavaVM.framework/Versions/X.Y.Z/Home.
Inside this home directory there is a symbolic link named shared_bundle that links three levels up, i.e. to /System/Library/Frameworks/JavaVM.framework.

If your build file contains a fileset like

Ant is going to follow the shared_bundle symlink and ends up recursing into all your installed VMs. Even worse, it will enter /System/Library/Frameworks/JavaVM.framework/Versions/X.Y.Z/Home and will once again follow the same symlink.
Ant versions after Ant 1.7.1 will detect the infinite loop they are in, but the resulting fileset may still be too big to deal with, in particular if you have many different VM versions installed. The problem is amplified by the fact that each installed version has a shared_bundle symlink in it.

JAVA-Tools , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

java.lang.VerifyError: llegal use of nonvirtual function call

Applies to:
Linux

Description:
Occurs while trying to run program on Linux

Cause:
You have tried to run program on Linux and got a very strange error message and the program failed.

JAVA-Mail , , , , ,

Problem while using Velocity in JBoss

Applies to:
JBoss, Velocity

Description:
Occurs while using Velocity in JBoss

Cause:
Velocity deploys their servlet as a singleton.

JAVA-JBoss ,

org.jboss.portal.portlet.InvokerUnavailableException: Problem getting service description

Applies to:
JBoss Portal

Description:
Occurs while starting JBoss using the -b option, and WSRP is now complaining with the following stack trace
Caused by: org.jboss.portal.portlet.InvokerUnavailableException: Problem getting service description for producer self at org.jboss.portal.wsrp.consumer.WSRPConsumerImpl.getPortlets(WSRPConsumerImpl.java:157) at org.jboss.portal.portlet.federation.impl.FederatedPortletInvokerService.getPortlets(FederatedPortletInvokerService.java:90) at org.jboss.portal.core.management.PortletDiscoveryService.processPortletDiscovery(PortletDiscoveryService.java:89)

Cause:
Invalid WSRP configuration.

JAVA-JBoss , , , , , ,

UnsupportedDataTypeException when sending new message

Applies to:
NA

Description:
Occurs while sending a message with unsupported content

Cause:
You probably set some content for your message using the setContent(Object o, String type) method.

JAVA-Mail , , ,

java.lang.IllegalAccessError: tried to access field org.apache.xpath.compiler.FunctionTable.m_functions from class org.apache.xml.security.Init at org.apache.xml.security.Init.init(Init.java:233)

Applies to:
JBoss 4.0.0, Java version 1.4.2_05

Description:
Occurs while launching JBoss from the IDE

Cause:
Ever since Java version 1.4.2_05, Java has included an out-of-date version of Xalan. The JBoss 4.0.0 startup scripts fix this by overriding the version of Xalan by setting the java.endorsed.dirs property. The JBoss IDE launcher does not do this.

JAVA-JBoss , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Data type not recognized

Applies to:
DBUnit

Description:
By default, DbUnit only supports standard JDBC data types. This error will occur while using vendor-specific data types

Cause:
You are getting this warning message if you are using vendor-specific data types.

JAVA-DBUnit , , ,

You must install a Solaris patch to run the native threads version of the Java runtime. The green threads version will work without this patch. Please check the native threads release notes for more information. If you are embedding the VM in a native application, please make sure that the native application is linked with libthread.so (-lthread)." Exiting.

EL Or JSTL Not Working As Expected

Applies to:
NA

Description:
Occurs while using EL or JSTL in JSP.

Cause:
Configuration mismatch between the version of JSP that you are using, the version of the JSTL that you employ, and how you have declared your web application in the deployment descriptor (web.xml).

JAVA-JSP , , , , , , , , , , , ,

causes other tasks to hang or leads to strange behaviour of tasks

Applies to:
Ant

Description:
Occurs while using Apache Ant.

Cause:
You have used which caused strange behaviour of tasks.

JAVA-Tools