Error List

Error List for the ‘Java’ Category

is broken

Applies to:
Ant 1.5.2

Description:
Occurs while using Apache Ant.

Cause:
Ant creates archives that a partially unreadable by WinZIP. Luckily jar deals with the archives and so the generated jars/wars/ears will most likely work for You anyway.

JAVA-Tools ,

Fetch out of sequence error

Applies to:
NA

Description:
Occurs when fetching values for columns more than once.

Cause:
This type of error happens because your JDBC driver only supports fetching values for columns once AND in the order that they appear in your ResultSet. For example:
while (rs.next()){
rs.getString(1);
rs.getString(3);
rs.getString(3);// error happens here
rs.getString(2);// error would also happen here
}

JAVA-JDBC , , , , ,

OutOfMemoryException after redeploying application several times

Applies to:
JBoss

Description:
Occurs when redeploying an application several times

Cause:
There is a BUG related to class unloading http://jira.jboss.com/jira/browse/JBAS-1319.
The web container (Tomcat) was still holding references to the ClassLoaders (required condition to unload the class).
Sun’s Java virtual machine creates a so called Permanent Generation in their memory heap where they store reflective data about the current runtime. In practice this usually means instances of java.lang.Class and java.lang.reflect. classes. These classes are only unloaded if all the references to the classLoaders are gone plus there is no more instances of the class. This will happen during Full GC operations.

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

Could not create table with SQL

Applies to:
JBoss Portal

Description:
Occurs at startup: You can see DEBUG level messages that include a SQLException stack trace similar to the following:
DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager]
Could not create table with SQL: CREATE CACHED TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL,
DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB OBJECT,
PRIMARY KEY (MESSAGEID, DESTINATION) )
java.sql.SQLException: Table already exists: JMS_MESSAGES in statement [CREATE CACHED TABLE JMS_MESSAGES]



Cause:
These messages sometimes causes concern for users. However, most of the time, this message is normal and expected (hence, the DEBUG logging level instead of, say, ERROR or WARN.)

By default, the server attempts to create the tables that support message persistence. If the tables already exist, a java.sql.SQLException will be thrown. This normally indicates that the tables already exist and do not need to be created. Of course, if the tables do not already exist they will be created, and administrators are not required to create the tables required by JMS as a separate task.
While the stack trace is usually the feature of the log message that causes concern, it is needed in the DEBUG message. There is no standard SQL exception or message thrown for a “table already exists” type of failure. This means that there is not a general way to report the exception only when the failure is caused by some other problem. Thus, the stack trace is included to facilitate debugging when there is some other failure when creating the tables.

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

does not exist or no valid version error

Applies to:
Maven

Description:
Occurs while using Maven.

Cause:
This error indicates that Maven is either unable to access the required plug-in from your local repository, or unable to access the official or ‘central’ Maven2 plug-in repository.

JAVA-Tools ,

UnsupportedDataTypeException when invoking getContent() on a bodypart

Applies to:
NA

Description:
Occurs when invoking getContent() method on a bodypart.

Cause:
You have tried to invoke getContent() method on a bodypart.

JAVA-Mail , , ,

Invalid invocation

Applies to:
JBoss, EJB

Description:
Indicates that there is an inconsistent type system between the caller of the ejb and the ejb container.

Cause:
An exception like the following:
javax.ejb.EJBException: Invalid invocation, check your deployment packaging, method=public abstract SomeInterface SomeClass

JAVA-JBoss , , , ,

Error retrieving artifact' error during bootstrap/-all

Ant creates WAR/JAR files with a lower-case

Applies to:
Ant

Description:
Occurs while using Apache Ant.

Cause:
Ant created WAR files with a lower-case web-inf or JAR files with a lower-case meta-inf directory.

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

Unknown entity exception

Applies to:
Hibernate

Description:
Occurs when using @org.hibernate.annotations.Entity

Cause:
You have used @org.hibernate.annotations.Entity

JAVA-Hibernate ,