About the status of the JMS message in WebLogic

Today, my colleague asked me how to handle the JMS messages of receive and visible. A little bit ignorant, before the state of the message has never been concerned. In the Weblogic81, we can't see the message in destination, we can only see how many messages there are in the current destination, how many pending are there. And in 92, when we monitor the destination, we can see the specific message, and the message follows a state string. The title of the receive, VISIBLE is this state string, in fact, there are many, the common is the receive, VISIBLE. Let's look at all these state explanations in the code (MESSAGEINFO.JAVA),

Visible:indicates that's VISIBLE on the destination. Messages have been row, waiting to be consumed.

Ordered:indicates that "message" belongs to a. The message is in a unit.

Delayed:indicates that "exists on" the destination but is classified as pending because it has a scheduled deliv Ery or is delayed. The message has been row, but the message will become visible because Timetodeliver has not yet arrived until Timetodeliver. Or because of the client consumption exception, such as OnMessage in the RuntimeException, the message was recover, waiting for redelivery delay time to arrive, and then resend.

Receive:indicates that "exists on" the destination but is classified as pending because it has been received but Not acknowledged. The actual state may also include state_transaction if the receive operation is performed as part of a TRANSACTION. The message has been row , and has been deliver to some consumer, but consumer's acknowledge has not yet been received. It may be a network problem or the client is set to Client_ack mode.

Send:indicates that "exists on" the destination but is classified as pending because it was part of a send Operat Ion is in progress. The actual state may also include state_transaction if the send operation is perfromed as part of a TRANSACTION. The message has been row, but the eye The forward send operation is in process (for example, a transaction has not been committed), and the message is not available for consumer.

Transaction:indicates that "exists on" destination but is classified as pending because it's part of a send or receive operation it being performed as part of a global transaction.

Paused:indicates that "message" exists on the destination but are being held in a pending state because of a pause Operat Ion. News because pause was pending in Dest.

Redelivery_count_exceeded:indicates that's message has exceeded the Redelivery COUNT set for the destination and is no L Onger available for consumption. The message repeatedly redelivery the ceiling has arrived, such messages will not be sent back.

Depending on the state of the message, we can basically determine the location of the JMS message-related issues, so that the investigation can be targeted.