Connectivity > Protocols > REST ActiveMQ Classic implements a RESTful API to messaging which allows any web capable device to publish or consume messages using a regular HTTP POST or GET. If you are interested in messaging directly from web browsers you might wanna check out our Ajax or WebSockets support or try running the REST examples Mapping of REST to JMS To publish a message use a HTTP POST.
Features > Destination Features > Delete Inactive Destinations Inactive Destination An ‘inactive’ destination is one that has had no messages pending and no consumers connected for some configured period of time. By default the broker does not check for inactive destinations. This as governed by the default values for the following options: schedulePeriodForDestinationPurge="0" and gcInactiveDesti
For the last two weeks I’ve been working on some interesting use cases for the good ol’ failover transport. I finally have some time at my hands, so here’s a brief recap of what’s coming in 5.6 release in this area. First there’s a new feature, called Priority Backup. It’s described in details here, but in a nutshell it provides you with the mechanism of prioritizing your failover urls and keep yo
Networks of message brokers in ActiveMQ work quite differently to more familiar models such as that of physical networks. They are not any harder to understand or reason about but we need to have an appreciation as to what exactly each of the pieces in the puzzle do by themselves in order to understand them in them large. I will try to explain each component piece progressively moving up in comple
ActiveMQとは ActiveMQとは、Java Message Serviceを実装したメッセージ関連のミドルウェアです。ActiveMQをインストールすることで、アプリケーションは非同期型のメッセージキューイングを行うことができます。メッセージを非同期にやり取りするため、一時的にシステムがダウンしても影響を受けずに処理を再開させることが可能です。以下のような感じです。 ActiveMQのインストール ActiveMQはソースコードで提供されていますが、RPMの作成も可能です。ここではいったんRPMを作成してインストールする手順を解説します。 $ sudo yum install -y rpm_build $ mkdir -p ~/rpm/{BUILD,RPMS,SOURCES,SPECS,SRPMS} $ echo "%_topdir ~/rpm" > ~/.rpmmacros $
Features > Clustering > Networks of Brokers To provide massive scalability of a large messaging fabric you typically want to allow many brokers to be connected together into a network so that you can have as many clients as you wish all logically connected together - and running as many message brokers as you need based on your number of clients and network topology. If you are using client/server
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
ActiveMQ: JDBC Master Slave with MySQL
ActiveMQ - Network of Brokers Explained - Part 2
ActiveMQ - Network of Brokers Explained