Red Hat Summit Red Hat Summitサポートコンソール開発者トライアルの開始お問い合わせ

このコンテンツは選択した言語では利用できません。

Chapter 2. Getting started with transactions on Karaf (OSGi)

This section describes a Camel application that uses transactions to access an Artemis JMS broker. The information is organized as follows:

2.1. Prerequisites
リンクのコピー

Implementation of this Camel application has the following prerequisites:

  • An external AMQ 7 JMS message broker must be running.

    The following sample code runs a standalone (non-Docker) version of amq-broker-7.1.0-bin.zip. Execution creates and runs an amq7 instance: 

    $ pwd
/data/servers/amq-broker-7.1.0

$ bin/artemis create --user admin --password admin --require-login amq7
Creating ActiveMQ Artemis instance at: /data/servers/amq-broker-7.1.0/amq7

Auto tuning journal ...
done! Your system can make 27.78 writes per millisecond, your journal-buffer-timeout will be 36000

You can now start the broker by executing:

   "/data/servers/amq-broker-7.1.0/amq7/bin/artemis" run

Or you can run the broker in the background using:

   "/data/servers/amq-broker-7.1.0/amq7/bin/artemis-service" start

$ amq7/bin/artemis run
           __  __  ____    ____            _
     /\   |  \/  |/ __ \  |  _ \          | |
    /  \  | \  / | |  | | | |_) |_ __ ___ | | _____ _ __
   / /\ \ | |\/| | |  | | |  _ <| '__/ _ \| |/ / _ \ '__|
  / ____ \| |  | | |__| | | |_) | | | (_) |   <  __/ |
 /_/    \_\_|  |_|\___\_\ |____/|_|  \___/|_|\_\___|_|

 Red Hat JBoss AMQ 7.1.0.GA


018-05-02 16:37:19,294 INFO  [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server
...
    Copy to Clipboard Toggle word wrap

  • Client libraries are required. Artemis libraries are available in Maven Central or a Red Hat repository. For example, you can use:

    • mvn:org.apache.activemq/artemis-core-client/2.4.0.amq-710008-redhat-1
    • mvn:org.apache.activemq/artemis-jms-client/2.4.0.amq-710008-redhat-1

    Alternatively, Artemis/AMQ 7 client libraries can be installed as Karaf features, for example:

    • karaf@root()> feature:install artemis-jms-client artemis-core-client

  • Some supporting features that provide Karaf shell commands or dedicated Artemis support are required: 

    karaf@root()> feature:install jms pax-jms-artemis pax-jms-config
    Copy to Clipboard Toggle word wrap

  • Required Camel features are: 

    karaf@root()> feature:install camel-jms camel-blueprint
    Copy to Clipboard Toggle word wrap

2.2. Building the camel-jms project
リンクのコピー

The Fuse distribution contains the quickstarts/camel/camel-jms example, which you can build and install as an OSGi bundle. This bundle contains a Blueprint XML definition of a Camel route that sends messages to an AMQ 7 JMS queue.

In the following example, $FUSE_HOME is the location of the unzipped Fuse distribution. To build this project:

  1. Invoke Maven to build the project: 

    $ pwd
$FUSE_HOME/quickstarts

$ mvn clean install -f camel/camel-jms/
[INFO] Scanning for projects...
[INFO]
[INFO] ----------------< org.jboss.fuse.quickstarts:camel-jms >----------------
[INFO] Building Red Hat Fuse :: Quickstarts :: camel-jms 7.0.0.redhat-SNAPSHOT
[INFO] -------------------------------[ bundle ]-------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ camel-jms ---
[INFO]
[INFO] >>> maven-source-plugin:3.0.1:jar (default-cli) > generate-sources @ camel-jms >>>
[INFO]
[INFO] <<< maven-source-plugin:3.0.1:jar (default-cli) < generate-sources @ camel-jms <<<
[INFO]
[INFO]
[INFO] --- maven-source-plugin:3.0.1:jar (default-cli) @ camel-jms ---
[INFO] Building jar: $FUSE_HOME/quickstarts/camel/camel-jms/target/camel-jms-sources.jar
[INFO]
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ camel-jms ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ camel-jms ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-resources-plugin:3.0.2:testResources (default-testResources) @ camel-jms ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory $FUSE_HOME/quickstarts/camel/camel-jms/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ camel-jms ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.20.1:test (default-test) @ camel-jms ---
[INFO] Tests are skipped.
[INFO]
[INFO] --- maven-bundle-plugin:3.5.0:bundle (default-bundle) @ camel-jms ---
[INFO]
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ camel-jms ---
[INFO] Installing $FUSE_HOME/quickstarts/camel/camel-jms/target/camel-jms.jar to ~/.m2/repository/org/jboss/fuse/quickstarts/camel-jms/7.0.0.redhat-SNAPSHOT/camel-jms-7.0.0.redhat-SNAPSHOT.jar
[INFO] Installing $FUSE_HOME/quickstarts/camel/camel-jms/pom.xml to ~/.m2/repository/org/jboss/fuse/quickstarts/camel-jms/7.0.0.redhat-SNAPSHOT/camel-jms-7.0.0.redhat-SNAPSHOT.pom
[INFO] Installing $FUSE_HOME/quickstarts/camel/camel-jms/target/camel-jms-sources.jar to ~/.m2/repository/org/jboss/fuse/quickstarts/camel-jms/7.0.0.redhat-SNAPSHOT/camel-jms-7.0.0.redhat-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-bundle-plugin:3.5.0:install (default-install) @ camel-jms ---
[INFO] Local OBR update disabled (enable with -DobrRepository)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.042 s
[INFO] Finished at: 2018-05-02T16:28:57+02:00
[INFO] ------------------------------------------------------------------------
    Copy to Clipboard Toggle word wrap

  2. Create a JMS connection factory configuration so that the javax.jms.ConnectionFactory service is published in the OSGi runtime. To do this, copy $FUSE_HOME/quickstarts/camel/camel-jms/src/main/resources/etc/org.ops4j.connectionfactory-amq7.cfg into the $FUSE_HOME/etc directory. This configuration will be processed to create a working connection factory. For example: 

    $ cp camel/camel-jms/src/main/resources/etc/org.ops4j.connectionfactory-amq7.cfg ../etc/
    Copy to Clipboard Toggle word wrap

  3. Verify the published connection factory: 

    karaf@root()> service:list javax.jms.ConnectionFactory
[javax.jms.ConnectionFactory]
-----------------------------
 felix.fileinstall.filename = file:$FUSE_HOME/etc/org.ops4j.connectionfactory-amq7.cfg
 name = artemis
 osgi.jndi.service.name = artemis
 password = admin
 pax.jms.managed = true
 service.bundleid = 251
 service.factoryPid = org.ops4j.connectionfactory
 service.id = 436
 service.pid = org.ops4j.connectionfactory.d6207fcc-3fe6-4dc1-a0d8-0e76ba3b89bf
 service.scope = singleton
 type = artemis
 url = tcp://localhost:61616
 user = admin
Provided by :
 OPS4J Pax JMS Config (251)

karaf@root()> jms:info -u admin -p admin artemis
Property │ Value
─────────┼──────────────────────────
product  │ ActiveMQ
version  │ 2.4.0.amq-711002-redhat-1

karaf@root()> jms:queues -u admin -p admin artemis
JMS Queues
────────────────────────────────────
df2501d1-aa52-4439-b9e4-c0840c568df1
DLQ
ExpiryQueue
    Copy to Clipboard Toggle word wrap

  4. Install the bundle: 

    karaf@root()> install -s mvn:org.jboss.fuse.quickstarts/camel-jms/7.0.0.redhat-SNAPSHOT
Bundle ID: 256
    Copy to Clipboard Toggle word wrap

  5. Confirm that it is working: 

    karaf@root()> camel:context-list
 Context               Status              Total #       Failed #     Inflight #   Uptime
 -------               ------              -------       --------     ----------   ------
 jms-example-context   Started                   0              0              0   2 minutes
karaf@root()> camel:route-list
 Context               Route               Status              Total #       Failed #     Inflight #   Uptime
 -------               -----               ------              -------       --------     ----------   ------
 jms-example-context   file-to-jms-route   Started                   0              0              0   2 minutes
 jms-example-context   jms-cbr-route       Started                   0              0              0   2 minutes
    Copy to Clipboard Toggle word wrap
  6. As soon as the Camel routes have started, you can see a directory, work/jms/input, in your Fuse installation. Copy the files you find in this quickstart’s src/main/data directory to the newly created work/jms/input directory.

  7. Wait a few moments and you will find the same files organized by country under the work/jms/output directory:

    • order1.xml, order2.xml and order4.xml in work/jms/output/others
    • order3.xml and order5.xml in work/jms/output/us
    • order6.xml in work/jms/output/fr

  8. See the logs to check out the business logging: 

    2018-05-02 17:20:47,952 | INFO  | ile://work/jms/input | file-to-jms-route                | 58 - org.apache.camel.camel-core - 2.21.0.fuse-000077 | Receiving order order1.xml
2018-05-02 17:20:48,052 | INFO  | umer[incomingOrders] | jms-cbr-route                    | 58 - org.apache.camel.camel-core - 2.21.0.fuse-000077 | Sending order order1.xml to another country
2018-05-02 17:20:48,053 | INFO  | umer[incomingOrders] | jms-cbr-route                    | 58 - org.apache.camel.camel-core - 2.21.0.fuse-000077 | Done processing order1.xml
    Copy to Clipboard Toggle word wrap

  9. See that the queue was dynamically created: 

    karaf@root()> jms:queues -u admin -p admin artemis
JMS Queues
────────────────────────────────────
DLQ
17767323-937f-4bad-a403-07cd63311f4e
ExpiryQueue
incomingOrders
    Copy to Clipboard Toggle word wrap

  10. Check Camel route statistics: 

    karaf@root()> camel:route-info jms-example-context file-to-jms-route
Camel Route file-to-jms-route
	Camel Context: jms-example-context
	State: Started
	State: Started


Statistics
	Exchanges Total: 1
	Exchanges Completed: 1
	Exchanges Failed: 0
	Exchanges Inflight: 0
	Min Processing Time: 67 ms
	Max Processing Time: 67 ms
	Mean Processing Time: 67 ms
	Total Processing Time: 67 ms
	Last Processing Time: 67 ms
	Delta Processing Time: 67 ms
	Start Statistics Date: 2018-05-02 17:14:17
	Reset Statistics Date: 2018-05-02 17:14:17
	First Exchange Date: 2018-05-02 17:20:48
	Last Exchange Date: 2018-05-02 17:20:48
    Copy to Clipboard Toggle word wrap

2.3. Explanation of the camel-jms project
リンクのコピー

Camel routes are using the following endpoint URIs: 

<route id="file-to-jms-route">
...
    <to uri="jms:queue:incomingOrders?transacted=true" />
</route>

<route id="jms-cbr-route">
    <from uri="jms:queue:incomingOrders?transacted=true" />
...
</route>
Copy to Clipboard Toggle word wrap

The jms component is configured by using this snippet: 

<bean id="jms" class="org.apache.camel.component.jms.JmsComponent">
    <property name="connectionFactory">
        <reference interface="javax.jms.ConnectionFactory" />
    </property>
    <property name="transactionManager" ref="transactionManager"/>
</bean>
Copy to Clipboard Toggle word wrap

While the transactionManager reference is: 

<reference id="transactionManager" interface="org.springframework.transaction.PlatformTransactionManager" />
Copy to Clipboard Toggle word wrap

As you can see, both the JMS connection factory and the Spring interface of PlatformTransactionManager are only references. There is no need to define them in Blueprint XML. These services are exposed by Fuse itself.

You have already seen that javax.jms.ConnectionFactory was created by using etc/org.ops4j.connectionfactory-amq7.cfg.

The transaction manager is: 

karaf@root()> service:list org.springframework.transaction.PlatformTransactionManager
[org.springframework.transaction.PlatformTransactionManager]
------------------------------------------------------------
 service.bundleid = 21
 service.id = 527
 service.scope = singleton
Provided by :
 Red Hat Fuse :: Fuse Modules :: Transaction (21)
Used by:
 Red Hat Fuse :: Quickstarts :: camel-jms (256)
Copy to Clipboard Toggle word wrap

Check for other interfaces under which the actual transaction manager is registered: 

karaf@root()> headers 21

Red Hat Fuse :: Fuse Modules :: Transaction (21)
------------------------------------------------
...
Bundle-Name = Red Hat Fuse :: Fuse Modules :: Transaction
Bundle-SymbolicName = fuse-pax-transx-tm-narayana
Bundle-Vendor = Red Hat
...

karaf@root()> bundle:services -p 21

Red Hat Fuse :: Fuse Modules :: Transaction (21) provides:
----------------------------------------------------------
objectClass = [org.osgi.service.cm.ManagedService]
service.bundleid = 21
service.id = 519
service.pid = org.ops4j.pax.transx.tm.narayana
service.scope = singleton
 ----
objectClass = [javax.transaction.TransactionManager]
provider = narayana
service.bundleid = 21
service.id = 520
service.scope = singleton
 ----
objectClass = [javax.transaction.TransactionSynchronizationRegistry]
provider = narayana
service.bundleid = 21
service.id = 523
service.scope = singleton
 ----
objectClass = [javax.transaction.UserTransaction]
provider = narayana
service.bundleid = 21
service.id = 524
service.scope = singleton
 ----
objectClass = [org.jboss.narayana.osgi.jta.ObjStoreBrowserService]
provider = narayana
service.bundleid = 21
service.id = 525
service.scope = singleton
 ----
objectClass = [org.ops4j.pax.transx.tm.TransactionManager]
provider = narayana
service.bundleid = 21
service.id = 526
service.scope = singleton
 ----
objectClass = [org.springframework.transaction.PlatformTransactionManager]
service.bundleid = 21
service.id = 527
service.scope = singleton
Copy to Clipboard Toggle word wrap

The transaction manager is available from these interfaces:

  • javax.transaction.TransactionManager
  • javax.transaction.TransactionSynchronizationRegistry
  • javax.transaction.UserTransaction
  • org.jboss.narayana.osgi.jta.ObjStoreBrowserService
  • org.ops4j.pax.transx.tm.TransactionManager
  • org.springframework.transaction.PlatformTransactionManager

You can use any of them in any context that you need. For example camel-jms requires that the org.apache.camel.component.jms.JmsConfiguration.transactionManager field be initialized. This is why the example uses: 

<reference id="transactionManager" interface="org.springframework.transaction.PlatformTransactionManager" />
Copy to Clipboard Toggle word wrap

instead of, for example: 

<reference id="transactionManager" interface="javax.transaction.TransactionManager" />
Copy to Clipboard Toggle word wrap
トップに戻る
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2025 Red Hat