WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Resolving problems when developing Message Broker API applications
Use the advice given here to help you to resolve problems that can arise when developing Message Broker API (also known as the CMP API) applications.
Your CMP application hangs if the broker is not available
You set a property of an object and query its value, but the value has not changed
- Scenario: You have set a property of an object, then queried its value; the value has not changed.
- Explanation: Methods that change properties of broker objects are not processed immediately. If you call a property change method on a CMP object, the CMP API sends a message that requests the specified change to the broker. The broker processes the request asynchronously, and notifies all AdministeredObjectListeners of the affected object when the change has been attempted.
- Solution: Methods that change state typically return to the calling program as soon as the request has been put to the queue manager of the broker, or, following a call to BrokerProxy.beginUpdates(), as soon as the request has been added to the current batch. If the property has still not been updated after the action's response to the request has been returned to the application, consult the response message for more details.