Troubleshooting

The onMessage Method Is Not Being Called

My onMessage method is not being called by the container.

Make sure that the JMS destination for which the message-driven bean is a consumer is set up. Each vendor might have a unique way of setting up the JMS destinations. Also check that the destination type and name that are declared in the deployment descriptors match what are actually configured.

Security Identity for a Message-Driven Bean

How do I set up a security identity for a message-driven bean?

Because a message-driven bean can't be seen directly by a client, the client's security principal can't be propagated to the container. However, you can configure a message-driven bean to assume a security identity so that it can be propagated to other EJBs during the onMessage processing.