Before You Begin
Note: Learn about supported browsers, operating systems, and platform versions in the Release Notes.
What Problem Are You Having?
- Error When Using textMessage()
- Expected Messages Are Not Being Received for a Queue or Durable Subscriber
- 400 Bad Request Error During Authentication Using Internet Explorer
Cause: This message usually means that you are using Connection.start(), Connection.close(), Connection.create(), Transaction.commit(), Transaction.rollback(), or Producer.send() and the interface is not fully completing its function before initializing the "future" handler. For example, when using Connection.start(), all message processing must start properly before calling connectionFuture.
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.
Cause: Internet Explorer caches credentials by default. For example, if a client in Internet Explorer performs Negotiate authentication to obtain a token and then attempts to use Basic Authentication for a username and password, the client in Internet Explorer responds by sending a Negotiate scheme instead of the Basic scheme, resulting in a 400 Bad Request.