Previous Contents Index Next |
Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Error Messages Reference

> ## Chapter 20
> Message Driven Bean Container

> This chapter lists error messages that originate from the message driven bean container.

> ##

> MDB

> Message-driven beans are persistent objects that are likely to call a full range of JDBC interfaces, much like entity beans. However, message-driven beans have no local or remote interfaces as do other EJB components, and they differ from entity beans in how they are accessed.

> A message-driven bean is a message listener that can reliably consume messages from a queue or a durable subscription. The messages may be sent by any J2EE component—from an application client, another EJB component, or a Web component—or from an application or a system that does not use J2EE technology.

> ##### MDB0002

> Severity | SEVERE
> Description | Could not get server session. The message-driven bean’s, ejbCreate method may have failed.
> Action | Check the stack trace following this error message for reason.

> ##### MDB0004

> Severity | SEVERE
> Description | The getSession() call failed while the session was still in use. It is likely that the JMS provider re-used the old ServerSession object instead of getting one from the ServerSessionPool.
> Action | Lower the server's log level to get more information about the error and try again. If the problem persists, Analyze the System, as described on (more...) .

> ##### MDB0005

> Severity | SEVERE
> Description | The getSession() call failed after the session was destroyed. It is likely that the JMS provider re-used an old ServerSession object that was destroyed instead of getting one from the ServerSessionPool.
> Action | Lower the server's log level to get more information about the error and try again. If the problem persists, Analyze the System, as described on (more...) .

> ##### MDB0006

> Severity | SEVERE
> Description | The Get session failed. There are several reasons for this failure. For example, creation of JMS Session or the message-driven bean ejbCreate method may have failed.
> Action | Check the stack trace following this error message for reason or check the other error messages in the server log.

> ##### MDB0008

> Severity | SEVERE
> Description | An exception occurred in Session.run().
> Action | Check the server log for more information and check any runtime errors with the message-driven bean's onMessage method.

> ##### MDB00010

> Severity | SEVERE
> Description | An exception occurred while cleaning up ServerSession. The message-driven bean's ejbRemove method may have failed.
> Action | Check the stack trace following this error message and other error messages in the server log for more information.

> ##### MDB00012

> Severity | SEVERE
> Description | ServerSession.getSession() must be called first before calling ServerSession.start(). It is likely that the JMS provider called the ServerSession methods in an incorrect sequence.
> Action | Lower the server's log level to get more information about the error and try again. If the problem persists, Analyze the System, as described on (more...) .

> ##### MDB00013

> Severity | SEVERE
> Description | An error occurred while creating ServerSession.
> Action | Check the stack trace following this error message and other error messages in the server log.

> ##### MDB00015

> Severity | SEVERE
> Description | Message-driven bean’s destination name not found.
> Action | Check the stack trace following this error message for information on why this exception occurred.

> ##### MDB00017

> Severity | SEVERE
> Description | An exception occurred while creating message-driven bean container.
> Action | See the stack trace following this error message for information on why this exception occurred.

> ##### MDB00020

> Severity | SEVERE
> Description | An exception occurred while closing message-driven bean container.
> Action | See the exception in the error message. Lower the server's log level to get more information about the error and try again. If the problem persists, Analyze the System, as described on (more...) .

> ##### MDB00021

> Severity | SEVERE
> Description | Message-driven bean container’s destination has a type mismatch.
> Action | See the error message for details. Check the message-driven bean's deployment descriptors and the type of the JMS destination that the message-driven bean listens and correct the type mismatch.

> ##### MDB00023

> Severity | WARNING
> Description | The message-driven bean’s deployment descriptor element, jms-max-messages-load has an invalid value.
> Action | Correct the invalid jms-max-messages-load value in the message-driven bean's deployment descriptor element.

> ##### MDB00024

> Severity | SEVERE
> Description | Message-driven bean container’s connection factory not found.
> Action | Check the JMS connection factory resource configuration for the message-driven bean container. Check the stack trace information following this error message for information on why the error occurred.

> ##### MDB00025

> Severity | SEVERE
> Description | Message-driven bean container’s connection factory has a type mismatch.
> Action | See the error message for detail. Check the message-driven bean's deployment descriptors and the type of the JMS connection factory for the message-driven bean container and correct the type mismatch.

> ##### MDB00026

> Severity | SEVERE
> Description | Unable to start the message-driven bean container connection.
> Action | See the error message for reason. Check the stack trace following this error message.

> ##### MDB00027

> Severity | SEVERE
> Description | A connection exception event occurred.
> Action | See the error message for details. The message-driven bean container's connection to the JMS provider is broken. Check the stack trace following this error message. Check if the JMS provider's message server is still running.

> ##### MDB00029

> Severity | SEVERE
> Description | An error occurred while registering the bean-pool monitor for a message-driven bean.
> Action | See the error message for reason. Lower the server's log level to get more information about the error and try again. If the problem persists, Analyze the System, as described on (more...) .

> ##### MDB00030

> Severity | SEVERE
> Description | An exception occurred while setting up the message-driven bean container.
> Action | See the error message and other error messages in the server log for reason.

> ##### MDB00031

> Severity | WARNING
> Description | Message-driven bean container's connection factory not found. The default connection factory which connects to the built-in Sun Java System Message Queue server will be used instead.
> Action | Check the configuration of the JMS connection factory resource for the message-driven bean container.

> ##### MDB00032

> Severity | WARNING
> Description | Message-driven bean container's connection factory not found. The default connection factory which connects to the built-in Sun Java System Message Queue server will be used instead.
> Action | If you are using the default JMS connection factory, and it is not intended for the message-driven bean, add the mdb-connection-factory to the message-driven bean deployment descriptor and redeploy the application.

> ##### MDB00035

> Severity | SEVERE
> Description | An exception occurred after closing the message-driven bean pool.
> Action | See the error message and the stack trace following this error message for reason.

> ##### MDB00036

> Severity | SEVERE
> Description | Pre-invocation of message-driven bean failed.
> Action | See the stack trace following this error message and other error messages in the server log for more information.

> ##### MDB00037

> Severity | SEVERE
> Description | An exception occurred during message-driven bean invocation.
> Action | The message-driven bean container pre-invocation failed. See the error message for reason. Check the stack trace following this error message and other error messages in the server log for more information.

> ##### MDB00038

> Severity | SEVERE
> Description | No message-driven bean context in message listener.
> Action | Analyze the System, as described on (more...) .

> ##### MDB00039

> Severity | SEVERE
> Description | Message sent to a destroyed message-driven bean.
> Action | Analyze the System, as described on (more...) .

> ##### MDB00041

> Severity | SEVERE
> Description | An exception occurred in the message-driven bean's onMessage method.
> Action | See the error message for reason. Lower the server's log level to get more information about the error and try again. If the problem persists, Analyze the System, as described on (more...) .

> ##### MDB00042

> Severity | SEVERE
> Description | No invocation for message.
> Action | See other error messages in the server log for more information.

> ##### MDB00043

> Severity | WARNING
> Description | An exception occurred while reading the mdb-container configuration.
> Action | See the error message for reason. Check valid values in the mdb-container element in server.xml.

> ##### MDB00046

> Severity | SEVERE
> Description | The message-driven bean's onMessage method threw a run time exception.
> Action | Check the message-driven bean’s onMessage method for abnormal runtime behavior. Lowering the server's log level may give more information.

> ##### MDB00047

> Severity | SEVERE
> Description | Some application or unchecked exception occurred.
> Action | See the error message and other error messages in the server log for more information.

> ##### MDB00048

> Severity | SEVERE
> Description | An exception occurred in the message-driven bean’s pre-invocation.
> Action | See the error message for reason. Check other error messages and stack traces in the server log for more information.

> ##### MDB00049

> Severity | SEVERE
> Description | An exception occurred in the message-driven bean’s post-invocation.
> Action | See the error message for reason. Check the stack trace following this error message and other error messages in the server log for more information.

> ##### MDB00050

> Severity | SEVERE
> Description | An exception occurred while creating message-driven bean.
> Action | See the error message and the stack trace following this error message for reason.

> ##### MDB00051

> Severity | SEVERE
> Description | The message-driven bean container pre-invocation of ejbRemove method or ejbRemove method may have failed.
> Action | Check the error message and the stack trace following this error message for more information.

> ##### MDB00052

> Severity | SEVERE
> Description | Start message delivery for the message-driven bean container failed.
> Action | See the error message and the stack trace following this error message for information.

> ##### MDB00053

> Severity | SEVERE
> Description | Message-driven bean container has a cleanup exception.
> Action | See the error message and the stack trace following this error message for more information.

> ##### MDB00054

> Severity | SEVERE
> Description | An exception occurred while setting message-driven bean context.
> Action | See the error message and the stack trace following this error message for reason.

> ##### MDB00055

> Severity | SEVERE
> Description | An exception occurred while closing message-driven bean container’s ConnectionConsumer.
> Action | See the error message and the stack trace following this error message for reason.

> ##### MDB00058

> Severity | SEVERE
> Description | The message-driven bean container’s JMS connection threw an exception during server shutdown.
> Action | See the error message for the connection exception.

> ##### MDB00060

> Severity | SEVERE
> Description | An invalid or inconsistent attribute value was found in the mdb-container element in server.xml value.
> Action | Check valid values in mdb-container element in server.xml.

> Previous Contents Index Next

> Copyright 2004 Sun Microsystems, Inc. All rights reserved.