Error List

Error List for the ‘Java’ Category

Headers do not reflect the message changes

Applies to:
NA

Description:
Occurs when modifying a message

Cause:
You have modified a message, but the headers do not reflect the changes.

JAVA-Mail

java.net.ConnectException: Connection timed out: connect

Applies to:
JBoss

Description:
Occurs when trying to connect to the JBoss server

Cause:
You got an error like this when you tried to connect to the JBoss server:

javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 10.10.34.77; nested exception is:
java.net.ConnectException: Connection timed out: connect]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:707)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
at javax.naming.InitialContext.lookup(InitialContext.java:351)

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

AmbiguousTableNameException

Applies to:
DBUnit

Description:
This error occurs when no schema is specified and that DbUnit detect that it is getting columns information from multiple tables having the same name and located in different schemas

Cause:
a. No schema is specified.
B. Your database contains two tables whose names only differ by case, e.g. “userlist” and “UserList”. DBUnit handles table names case-insensitively and gets confused. This can happen on database systems that are case-sensitive for identifiers, e.g. MySQL and (possibly) Microsoft SQL Server.

JAVA-DBUnit , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

libthread loaded into green threads

Applies to:
Solaris, JNI

Description:
This error is produced if you
a. are running the green threads VM
b. did a System.loadLibrary(“foo”), and
c. libfoo.so was linked -lthread.

Cause:
Green threads and native threads don’t mix well and hence the check in the VM.

JAVA-JNI , , , , , , , , ,

Java Bean not found

Applies to:
NA

Description:
A common problem which occurs when the class loader cannot find beans that the pages reference.That usually results in an error message like “Class xxx cannot be resolved to a type”

Cause:
The class loader could not find beans that the pages referenced.

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

Resulting jar does not work in my application server

Applies to:
Ant

Description:
Occurs while using Apache Ant.

Cause:
You have used the Ant jar or manifest related tasks, long lines in Your manifest were wrapped at 70 characters and the resulting jar did not work in Your application server

JAVA-Tools , , ,

@Lob annotation fails

Applies to:
Hibernate

Description:
Occurs at application startup.

Cause:
Annotation @Serialized was working for You, and now You used @Lob but it failed.

JAVA-Hibernate ,

Cannot play "xyz.mov" or "abc.wav"

Applies to:
JSF 2.1.1

Description:
Occurs when You tried to play unsupported file type

Cause:
Although JMF might support a certain media content type such as QuickTime and MPEG, it may not support the specific compression (CODEC) used for the data inside that file. For example, a QuickTime file with Cinepak video will play in JMF, but a QuickTime file with Sorensen video will not play.

JAVA-JMF , , , ,

org.jboss.mq.SpyJMSException: Cannot authenticate user

Applies to:
JBossMQ

Description:
Occurs while using JBoss

Cause:
You may be confused if you see this:

org.jboss.mq.SpyJMSException: Cannot authenticate user; – nested throwable: (java.net.SocketException: Socket closed)

when a JMS client is trying to connect.
Authentication is attempted when a connection is first established. When a connection is accepted, JBoss attempts to authenticate the client. If the socket is closed, then this exception is generated. The underlying cause is found within the parenthesis: java.net.SocketException: Socket closed.
Connection difficulties may be due to network firewall issues, outages, or OS problems, such as not enough free sockets or files on the server. Or, an unreliable client may be connecting but soon dropping due to issues on the client side.
This might also happen if you start jboss server on a multihomed system and jboss bind’s to the “wrong” ip address.

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

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 , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,