Error List

Error List for the ‘JAVA-JBoss’ Category

IOException ping timeout

Applies to:
JBossMQ

Description:
Each connection pings the server once every PingPeriod. This is configured on the ConnectionFactory (e.g. jms/deploy/uil2-service.xml) and defaults to 60 seconds.
Its purpose is for the client to be able detect that the connection with the server has been broken.

The mechanism is as follows:
1. Client sends a ping to the server and rests for the PingPeriod
2. After the PingPeriod has expired it checks that it got a Pong from the server
3. Repeat from 1

Cause:
1. The connection is broken, use Connection.setExceptionListener() to handle broken connections (usually by closing the old connection and reconnecting)
2. Something horrible is going on, e.g. very long garbage collections or massive amounts of paging means the ping/pong doesn’t get enough cpu to process in time i.e. either the client or server is failing big time to keep up with requests
3. You send a large message that takes more than PingPeriod to send over the connection, the ping or pong waits behind the message for its turn to be processed UIL2 has a ChunkSize that simulates a Pong when that many bytes are sent over the network to avoid this problem.
4. Some other problem like a deadlock see READTHISFIRST for how to debug this.

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

ClassCastExceptions when hot deploying ears

Applies to:
JBoss

Description:
You have A.ear and B.ear, and B.ear relies upon an EJB that is packaged in A.ear. You update some code inside A.ear and redeploy it, and when you go to test the updated code using a method contained in B.ear, you get a ClassCastException.

Cause:
First off, this is not a bug with the JBoss classloader, this is normal expected behavior. What is happenning is when A.ear is redeployed any references that B.ear may have to classes contained inside A.ear are no longer valid.

JAVA-JBoss , , , , , , , ,

LoadContexts fail-safe cleanup

Applies to:
JBoss Portal, JBoss AS 4.2.1.GA

Description:
Occurs while using JBoss Portal:
WARN LoadContexts fail-safe cleanup (collections)… org.hibernate.engine.loading.CollectionLoadContext@cd7045

Cause:
Nothing’s wrong, it’s a small issue that will be resolved in future versions of Hibernate.

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

StreamCorruptedException

Applies to:
JBoss

Description:
Occurs while using JBoss

Cause:
The most common cause of this error is due to missing a class on the client classpath that is unmarshalling a serialized object. This can happen in JNDI lookups, ejb calls, etc.



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

Socket write error

Could not activate; failed to restore state

Applies to:
JBoss

Description:
Occurs when EJB passivates

Cause:
This happened due to an EJB instance being passivated to a file (.ser) and then later that file being removed by a clean up service. When the EJB instance was then called on to be activated, it’s serialized form on file was not there.

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

ERROR MyfacesConfig Both MyFaces and the RI are on your classpath. Please make sure to use only one of the two JSF-implementations

Applies to:
JBoss Portal

Description:
Occurs at startup

Cause:
It depends, JBoss Portlets core portlets will run jet fine with that error, nothing to worry about. If you are embedding MyFaces libs, make sure to understand the classloading rules.

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

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

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

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 ,