Troubleshoot Java JMS Clients

This topic contains descriptions of common errors that can occur when using the Java client and provides steps on how to prevent these errors.

Before You Begin

This procedure is part of Checklist: How to Build Java JMS Clients.

Note: Learn about supported browsers, operating systems, and platform versions in the Release Notes.

What Problem Are You Having?

Kerberos challenge handler not working

Cause: Kerberos challenge handlers might not work for one or more of the following reasons:

Expected messages are not being received for a queue or durable subscriber

Cause: If expected messages are not being received for a queue or durable subscriber, then it could be because the application has received messages without acknowledging them. The Gateway will send a maximum of maximum.pending.acknowledgments messages until the client acknowledges. The maximum.pending.acknowledgments property is set to 1 for JMS providers that do not support individual message acknowledgement.

Solution: If you are using a JMS provider other than Apache ActiveMQ or TIBCO Enterprise Message Service (TIBCO EMS), you must ensure your client applications acknowledge each message received from a queue or durable subscriber.

Next Step

Display Logs for the Java JMS Client