weblogic jms訊息狀態message
今天同事問我說,如何處理RECEIVE、VISIBLE的JMS訊息?有點懵,之前從沒有關注過訊息的狀態。Weblogic81中,我們是不能看到destination中的訊息的,只能看到當前destination中,有多少message, 有多少pending的message。而92中,我們監控destination的時候,可以看到具體的message,而且message後面會跟一個state string。標題中說的RECEIVE、VISIBLE就是這個state string,其實state有很多,常見的也就是RECEIVE、VISIBLE。下面我們看看所有這些STATE在程式碼(MessageInfo.java)中的解釋,
VISIBLE:Indicates that the message is visible on the destination.訊息已經入列,等待被消費。
ORDERED:Indicates that the message belongs to a Unit of Order. 訊息處於某個unit中。
DELAYED:Indicates that the message exists on the destination but is classified as pending because it has a scheduled delivery time or is delayed. 訊息已經入列,但因為TimeToDeliver還沒有到,直到TimeToDeliver,該訊息才會變成VISIBLE。
RECEIVE:Indicates that the message 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 was performed as part of a transaction.訊息已經入列,且已經被DELIVER到某個CONSUMER,但CONSUMER的ACKNOWLEDGE還沒有收到。可能是網路問題或客戶端設為CLIENT_ACK模式。
SEND:Indicates that the message exists on the destination but is classified as pending because it is part of a send operation that is in progress. The actual state may also include STATE_TRANSACTION if the send operation was perfromed as part of a transaction.訊息已經入列,且正在被DELIVER到CONSUMER端。
TRANSACTION:Indicates that the message exists on the destination but is classified as pending because it is part of a send or receive operation that is being performed as part of a global transaction.
PAUSED:Indicates that the message exists on the destination but is being held in a pending state because of a pause operation. 訊息因為PAUSE被PENDING在DEST中。
REDELIVERY_COUNT_EXCEEDED:Indicates that the message has exceeded the redelivery count set for the destination and is no longer available for consumption. 訊息反覆REDELIVERY的上限已經到達,這樣的訊息不會被重發。
根據訊息的狀態,我們基本可以斷定JMS訊息相關問題的位置,從而調查可以做到有的放矢。[@more@]
VISIBLE:Indicates that the message is visible on the destination.訊息已經入列,等待被消費。
ORDERED:Indicates that the message belongs to a Unit of Order. 訊息處於某個unit中。
DELAYED:Indicates that the message exists on the destination but is classified as pending because it has a scheduled delivery time or is delayed. 訊息已經入列,但因為TimeToDeliver還沒有到,直到TimeToDeliver,該訊息才會變成VISIBLE。
RECEIVE:Indicates that the message 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 was performed as part of a transaction.訊息已經入列,且已經被DELIVER到某個CONSUMER,但CONSUMER的ACKNOWLEDGE還沒有收到。可能是網路問題或客戶端設為CLIENT_ACK模式。
SEND:Indicates that the message exists on the destination but is classified as pending because it is part of a send operation that is in progress. The actual state may also include STATE_TRANSACTION if the send operation was perfromed as part of a transaction.訊息已經入列,且正在被DELIVER到CONSUMER端。
TRANSACTION:Indicates that the message exists on the destination but is classified as pending because it is part of a send or receive operation that is being performed as part of a global transaction.
PAUSED:Indicates that the message exists on the destination but is being held in a pending state because of a pause operation. 訊息因為PAUSE被PENDING在DEST中。
REDELIVERY_COUNT_EXCEEDED:Indicates that the message has exceeded the redelivery count set for the destination and is no longer available for consumption. 訊息反覆REDELIVERY的上限已經到達,這樣的訊息不會被重發。
根據訊息的狀態,我們基本可以斷定JMS訊息相關問題的位置,從而調查可以做到有的放矢。[@more@]
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/21645448/viewspace-1022396/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- JMS java 訊息機制Java
- Android訊息機制Message訊息池Android
- 實戰JBuilder7+WebLogic7(四)續JMS+Message-Driven Bean (轉)UIWebBean
- 訊息中介軟體與JMS標準
- 歡迎使用ilink message server:國內第一個獨立的JMS訊息中介軟體Server
- 訊息佇列之JMS和AMQP對比佇列MQ
- MQTT 遺囑訊息(Will Message)的使用MQQT
- unity 3種message訊息管理使用Unity
- Python PyQt顯示臨時狀態訊息PythonQT
- JMS pub/sub執行正常但訊息沒有
- 訊息佇列(Message Queue)基本概念佇列
- ActiveMQ 中的訊息遊標(Message cursors)MQ
- 使用Spring JMS簡化非同步訊息處理Spring非同步
- weblogic NodeManager狀態不可用Web
- 部署Weblogic的jms的問題Web
- weblogic中 JMS 的配置問題Web
- Android 安全加密:訊息摘要Message DigestAndroid加密
- Android安全加密:訊息摘要Message DigestAndroid加密
- Android 訊息處理機制:Handler|MessageAndroid
- Spring 系列,第 4 部分: Spring JMS 訊息處理Spring
- RocketMQ的事務訊息處理【half-message】MQ
- Weblogic JMS佇列阻塞問題處理Web佇列
- WebSphere Message Broker 中使用者出口跟蹤訊息Web
- 訊息資料庫Message DB:PostgreSQL的事件儲存和訊息儲存 - Eventide Blog資料庫SQL事件IDE
- RocketMQ原始碼解析之訊息消費者(consume Message)MQ原始碼
- Protobuf_動態訊息-反射反射
- Android訊息處理機制(Handler、Looper、MessageQueue與Message)AndroidOOP
- WCF技術剖析之十八:訊息契約(Message Contract)和基於訊息契約的序列化
- 遠端呼叫服務(RPC)和基於訊息的通訊(Message Queue)對比RPC
- WID/WPS 中開發、配置 JMS 作為訊息中介軟體的應用
- SOA Suite中weblogic的managed server 啟動是ADMIN狀態UIWebServer
- Chrome瀏覽器擴充套件開發系列之十三:訊息傳遞MessageChrome瀏覽器套件
- JMS訊息在消費者處於叢集環境下如何過濾重複資料
- RocketMQ 訊息整合:多型別業務訊息-普通訊息MQ多型型別
- 同步和非同步關注的是訊息通訊機制,阻塞和非阻塞關注的是程式在等待呼叫結果(訊息,返回值)時的狀態非同步
- RocketMQ 訊息整合:多型別業務訊息——定時訊息MQ多型型別
- 訊息機制篇——初識訊息與訊息佇列佇列
- 解析 RocketMQ 業務訊息——“事務訊息”MQ