This section lists a few common errors that you might encounter when working with the micro broker.
Performing too much work under one transaction
When receiving or handling messages through the Administrative API, you might receive an error message indicating that you are attempting too many work items under one transaction. You can resolve this problem with a couple of solutions.
You might see the following error message when handling messages through the Administrative API:
CWSOM1011E: An invalid operation was attempted on Object=DummyInternalTransaction while it was in
This error message indicates that too much work is being attempted under one transaction. The amount of work that can be done under a transaction is limited by the micro broker persistence log size.
There are two possible resolutions:
- Increase the log size through the Administrative API.
- Ensure that you regularly call the Session.commit() method on JMS client applications.
This error message can be seen as part of an FFDC, which is intended solely for service personnel.
Queue Full Exception
When the internal client code receives a QueueFullException
, it indicates that a queue has filled up.
A queue full condition is normally temporary. As a result, this exception can be treated as such. The internal client code backs out of the current transaction.
FFDCs created in diagnostics directory
The micro broker client (and the server) might generate an FFDC when it detects an unexpected error. If the user client application experiences unexpected behavior, you can check to see if the client has produced any FFDCs.
The cause of the error is detailed in the FFDC file. Even if the FFDC is not the problem that the user is experiencing, it might give an indication of underlying problems in the environment. Similarly, it is also worth looking to see if the micro broker has produced any FFDCs.
Parent topic: Troubleshooting the IBM Lotus Expeditor micro broker: XPD622