BFGJE0001 - BFGJE9999
- BFGJE0001W
- A message has been moved to the reject queue because it is not of the correct JMS message type. Rejected message: <insert_0>
- Severity
- 10 : Warning
- Explanation
- The WMQFTE JEE database logger expects all log messages to be of type TextMessage. The rejected message was not the correct type so it cannot be processed. It will be moved to the reject queue to stop any further processing.
- Response
- Examine the message to determine why it is of the wrong type. If the message is unrelated to WMQFTE, you should examine your WMQ configuration to determine why the message was delivered to the WMQFTE JEE database logger.
- BFGJE0002W
- A message has been moved to the reject queue after <insert_0> failed attempts at processing it. Rejected message: <insert_1>
- Severity
- 10 : Warning
- Explanation
- One or more attempts have previously been made by the JEE database logger to process this message but none have succeeded. The number of retry attempts has reached the configured limit as specified by the configurable _numberOfFailedAttemptsBeforeReject property, so this message has now been moved to the reject queue.
- Response
- Examine the server logs to determine why previous attempts to process the message failed.
- BFGJE0003W
- A message has been moved to the reject queue because it was not recognized by the WMQFTE JEE database logger. Reason for rejection: <insert_0>
- Severity
- 10 : Warning
- Explanation
- The WMQFTE JEE database logger could not process a message because it did not recognize the format of the message contents. The message will be moved to the reject queue to stop any further processing.
- Response
- Examine the message to determine why it could not be understood. If the message is unrelated to WMQFTE, you should examine your WMQ configuration to determine why the message was delivered to the WMQFTE JEE database logger.
- BFGJE0004E
- No EntityManager was provided to the WMQFTE JEE database logger MDB. Unable to process the supplied log message.
- Severity
- 20 : Error
- Explanation
- No EntityManager instance was provided to the WMQFTE JEE database logger MDB when it was asked to process a log message. The transaction for this message will be rolled back causing the message to be placed back on the subscription for the WMQFTE JEE database logger.
- Response
- The EntityManager is provided to the WMQFTE JEE database logger MDB by the application server container using Java resource injection. Inspect your application server logs to determine why this might have failed.
- BFGJE0005E
- An unexpected exception was caught by the WMQFTE JEE database logger while processing a log message. Exception message: <insert_0>
- Severity
- 20 : Error
- Explanation
- The WMQFTE JEE database logger caught an unexpected exception while processing a log message. Processing of the message cannot continue. The transaction for this message will be rolled back causing the message to be placed back on the subscription for the WMQFTE JEE database logger.
- Response
- Inspect the supplied exception message and any further messages in the application server logs to determine what caused the exception. If you cannot determine a reason, contact the IBM support center.
- BFGJE9997I
- <insert_0>
- Severity
- 0 : Information
- Explanation
- If this message does not give enough information, check the accompanying error messages for further information.
- Response
- For further information on resolving this error, see the problem determination information on the product Web site.
- BFGJE9998W
- <insert_0>
- Severity
- 10 : Warning
- Explanation
- If this message does not give enough information, check the accompanying error messages for further information.
- Response
- For further information on resolving this error, see the problem determination information on the product Web site.
- BFGJE9999E
- <insert_0>
- Severity
- 20 : Error
- Explanation
- If this message does not give enough information, check the accompanying error messages for further information.
- Response
- For further information on resolving this error, see the problem determination information on the product Web site.