http://git-wip-us.apache.org/repos/asf/activemq-web/blob/7a7d976c/integrating-apache-activemq-with-jboss.xml ---------------------------------------------------------------------- diff --git a/integrating-apache-activemq-with-jboss.xml b/integrating-apache-activemq-with-jboss.xml index 4a5a397..53905a3 100644 --- a/integrating-apache-activemq-with-jboss.xml +++ b/integrating-apache-activemq-with-jboss.xml @@ -1,48 +1,43 @@ -<div class="wiki-content maincontent"><h1 id="IntegratingApacheActiveMQwithJBoss-IntegratingApacheActiveMQwithJBoss">Integrating Apache ActiveMQ with JBoss</h1> +<div class="wiki-content maincontent"><h1>Integrating Apache ActiveMQ with JBoss</h1> -<p>Integration with application servers is a common scenario in the enterprise Java world, especially when it comes to messaging. <a shape="rect" class="external-link" href="http://activemq.org/"; rel="nofollow">ActiveMQ</a> is a JMS 1.1 compliant, open source, Apache Licensed, message oriented middleware (MOM) with <a shape="rect" class="external-link" href="http://activemq.org/site/changes-in-40.html"; rel="nofollow">many</a>, <a shape="rect" class="external-link" href="http://activemq.org/site/new-features-in-41.html"; rel="nofollow">many</a> features far beyond the JMS specification. ActiveMQ offers many different <a shape="rect" class="external-link" href="http://activemq.org/site/connectivity.html"; rel="nofollow">points of connectivity</a>, many <a shape="rect" class="external-link" href="http://activemq.org/site/cross-language-clients.html"; rel="nofollow">cross language clients</a> and many <a shape="rect" class="external-link" href="http://activemq.org/site/protocols.html"; rel= "nofollow">pluggable transport protocols</a> including integration with any J2EE 1.4 application server.</p> +<p>Integration with application servers is a common scenario in the enterprise Java world, especially when it comes to messaging. <a shape="rect" href="http://activemq.org/";>ActiveMQ</a> is a JMS 1.1 compliant, open source, Apache Licensed, message oriented middleware (MOM) with <a shape="rect" href="http://activemq.org/site/changes-in-40.html";>many</a>, <a shape="rect" href="http://activemq.org/site/new-features-in-41.html";>many</a> features far beyond the JMS specification. ActiveMQ offers many different <a shape="rect" href="http://activemq.org/site/connectivity.html";>points of connectivity</a>, many <a shape="rect" href="http://activemq.org/site/cross-language-clients.html";>cross language clients</a> and many <a shape="rect" href="http://activemq.org/site/protocols.html";>pluggable transport protocols</a> including integration with any J2EE 1.4 application server.</p> -<p>One of the application servers in the open source world is JBoss. A very common requirement is to configure ActiveMQ as the messaging infrastructure within JBoss. Although there is <a shape="rect" class="external-link" href="http://www.activemq.org/site/jboss-integration.html"; rel="nofollow">a bit of documentation</a> on this integration, this article seeks to provide much more detail and explanation. So if you have a need to integrate ActiveMQ with JBoss, this article is for you.</p> +<p>One of the application servers in the open source world is JBoss. A very common requirement is to configure ActiveMQ as the messaging infrastructure within JBoss. Although there is <a shape="rect" href="http://www.activemq.org/site/jboss-integration.html";>a bit of documentation</a> on this integration, this article seeks to provide much more detail and explanation. So if you have a need to integrate ActiveMQ with JBoss, this article is for you.</p> <p>This article explains how to configure JBoss to start up ActiveMQ as part of its lifecycle and how to configure the ActiveMQ resource adapter to handle the messaging and transactionality between ActiveMQ and JBoss.</p> -<h2 id="IntegratingApacheActiveMQwithJBoss-Requirements">Requirements</h2> +<h2>Requirements</h2> <p>Below are the software requirements for this article with links to download each:</p> -<ul><li><a shape="rect" class="external-link" href="http://activemq.org/site/download.html"; rel="nofollow">Apache ActiveMQ 4.0.1+</a></li><li><a shape="rect" class="external-link" href="http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=416591"; rel="nofollow">JBoss 4.0.4+</a></li><li><a shape="rect" class="external-link" href="http://www.java.com/en/download/index.jsp"; rel="nofollow">Sun Java 1.5+</a></li><li><a shape="rect" class="external-link" href="http://ant.apache.org/bindownload.cgi";>Apache Ant 1.6+</a></li></ul> +<ul><li><a shape="rect" href="http://activemq.org/site/download.html";>Apache ActiveMQ 4.0.1+</a></li><li><a shape="rect" href="http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=416591";>JBoss 4.0.4+</a></li><li><a shape="rect" href="http://www.java.com/en/download/index.jsp";>Sun Java 1.5+</a></li><li><a shape="rect" href="http://ant.apache.org/bindownload.cgi";>Apache Ant 1.6+</a></li></ul> <p>Though this article is using Unix, the installation and integration will work on any platform running Sun Java. It is recommended that each piece of software be downloaded before working through the steps is this article. Once each piece of software has been downloaded, proceed to the first step.</p> -<h2 id="IntegratingApacheActiveMQwithJBoss-InstalltheJ2SE1.5">Install the J2SE 1.5</h2> +<h2>Install the J2SE 1.5</h2> <p>The first step in this process is to install Java 1.5 and verify that it runs correctly. Using the link above, find, download and install the correct version of Java for your platform. Once Java is installed and in the PATH, test it to see that it runs correctly using the following command:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="9bc24ef3-40ca-44c4-8184-3dc2558516dc" ac:name="code" ac:schema-version="1"><plain-text-body> $ java -version -java version "1.5.0_06" +java version "1.5.0_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-112) Java HotSpot(TM) Client VM (build 1.5.0_06-64, mixed mode, sharing) -]]></script> -</div></div> +</plain-text-body></structured-macro> <p>Depending upon your platform and the exact build number of Java 1.5, your output may vary slightly. As long as it's Java 1.5 and the version information is output, you should be ready to proceed to the next step.</p> -<h2 id="IntegratingApacheActiveMQwithJBoss-InstallApacheAnt">Install Apache Ant</h2> +<h2>Install Apache Ant</h2> <p>The second step is to install Apache Ant. Simply download it using the link above, expand somewhere on your hard drive and place the <code>bin</code> directory in the PATH. This will allow you to test it quickly using the commands below:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="0b584001-7c6f-4418-a373-2baeaa6b5c3b" ac:name="code" ac:schema-version="1"><plain-text-body> $ ant -version Apache Ant version 1.6.2 compiled on July 16 2004 -]]></script> -</div></div> +</plain-text-body></structured-macro> <p>As long as you see the version output above, Ant should be usable. If you did not see the version output or received an error, consult the Ant documentation or mailing list archives to work out the issue. Please note that Ant is not used until the end of this whole exercise to test the integration.</p> -<h2 id="IntegratingApacheActiveMQwithJBoss-InstalltheJBossApplicationServer">Install the JBoss Application Server</h2> +<h2>Install the JBoss Application Server</h2> <p>The third step in this process is to install JBoss and make sure it runs correctly before installing and configuring ActiveMQ. Upon downloading JBoss-4.0.4, expand it in a place where it can create a directory. Next, run the server using the following commands:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="ecdb3355-5bad-42a4-a5ee-0ba25b1d0b45" ac:name="code" ac:schema-version="1"><plain-text-body> $ cd jboss-4.0.4.GA $ ./bin/run.sh -c default ========================================================================= @@ -74,19 +69,17 @@ $ ./bin/run.sh -c default ... 15:35:17,360 INFO [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)] Started in 22s:238ms -]]></script> -</div></div> -<p>The first few lines of output from the JBoss startup indicates the configuration being used but the last line is the most important one. It tells you that JBoss has been started successfully on your system. For an extra measure of assurance, visit <a shape="rect" class="external-link" href="http://localhost:8080/web-console/"; rel="nofollow">http://localhost:8080/web-console/</a> in a web browser to make sure you are able to see the JBoss web console. If you can see this console, everything should be ready to go.</p> +</plain-text-body></structured-macro> +<p>The first few lines of output from the JBoss startup indicates the configuration being used but the last line is the most important one. It tells you that JBoss has been started successfully on your system. For an extra measure of assurance, visit <a shape="rect" href="http://localhost:8080/web-console/";>http://localhost:8080/web-console/</a> in a web browser to make sure you are able to see the JBoss web console. If you can see this console, everything should be ready to go.</p> -<p>As a side note, the left-hand side of the web-console requires that the <a shape="rect" class="external-link" href="http://java.sun.com/products/plugin/"; rel="nofollow">Java plugin</a> be properly installed. This is supposed to take place when installing the J2SE, so if it did not work correctly for you, I suggest that you consult some documentation about any errors you may be seeing. The Java plugin is not required for JBoss or ActiveMQ to function properly, it is simply for the JBoss web-console.</p> +<p>As a side note, the left-hand side of the web-console requires that the <a shape="rect" href="http://java.sun.com/products/plugin/";>Java plugin</a> be properly installed. This is supposed to take place when installing the J2SE, so if it did not work correctly for you, I suggest that you consult some documentation about any errors you may be seeing. The Java plugin is not required for JBoss or ActiveMQ to function properly, it is simply for the JBoss web-console.</p> <p>Once JBoss is installed properly, shut it down using either the shutdown script or by simply typing ctrl-c to activate the shutdown hook. Once it is shut down, proceed to the next step.</p> -<h2 id="IntegratingApacheActiveMQwithJBoss-PrepareforIntegratingApacheActiveMQwiththeJBossApplicationServer">Prepare for Integrating Apache ActiveMQ with the JBoss Application Server</h2> +<h2>Prepare for Integrating Apache ActiveMQ with the JBoss Application Server</h2> <p>The fourth step is to prepare your environment for integrating ActiveMQ with JBoss. If you haven't done so already, download Apache ActiveMQ using the link above. As of the writing of this article, the latest released version is 4.0.2-RC4. Upon downloading this archive, expand it in a place where it can create a directory, preferably in the same location where JBoss was expanded. Verify that the ActiveMQ RAR file is included using the following commands:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="3a69cbcd-8308-4e16-806b-e40caeb29677" ac:name="code" ac:schema-version="1"><plain-text-body> $ cd ./incubator-activemq-4.0.2.tar.gz $ jar tvf /opt/incubator-activemq-4.0.2/lib/optional/activemq-ra-4.0.2.rar 0 Mon Sep 25 19:00:50 MDT 2006 META-INF/ @@ -107,25 +100,20 @@ $ jar tvf /opt/incubator-activemq-4.0.2/lib/optional/activemq-ra-4.0.2.rar 358085 Tue Aug 01 12:23:26 MDT 2006 log4j-1.2.12.jar 523 Mon Sep 25 19:00:50 MDT 2006 META-INF/DISCLAIMER.txt 11359 Mon Sep 25 19:00:50 MDT 2006 META-INF/LICENSE.txt -]]></script> -</div></div> +</plain-text-body></structured-macro> <p>This is simply a table of contents of the RAR file. There should only be one reason that this will fail - an incomplete download of the ActiveMQ tarball or zip file. Beyond that, depending on the version you download, some of the library versions may be slightly different.</p> <p>Now go back to the JBoss installation and create a directory for ActiveMQ in the JBoss deploy directory for the default JBoss context. Below are the commands to achieve this task:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="dfbdd1ea-39da-4687-ad6a-a42d8947ab30" ac:name="code" ac:schema-version="1"><plain-text-body> $ mkdir /opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar $ cd /opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar $ pwd /opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar -]]></script> -</div></div> -<div class="panel" style="background-color: #ccccff;border-width: 1px;"><div class="panelContent" style="background-color: #ccccff;"> -<p><strong><em>NOTE:</em></strong> The creation of a directory is not required but is the easiest way to set up the ActiveMQ RAR when you're just getting started. This is due to the flexibility it affords during the development phase for the configuration to be changed very easily. The alternative is to JAR up the directory as a RAR file once the configuration is solid enough that it no longer needs to be changed. But leaving everything in a directory during development is the easiest path.</p> -</div></div> +</plain-text-body></structured-macro> +<structured-macro ac:macro-id="8b393505-f091-411a-ae01-7fa559ed289b" ac:name="panel" ac:schema-version="1"><parameter ac:name="bgColor">#ccccff</parameter><rich-text-body> +<p><strong><em>NOTE:</em></strong> The creation of a directory is not required but is the easiest way to set up the ActiveMQ RAR when you're just getting started. This is due to the flexibility it affords during the development phase for the configuration to be changed very easily. The alternative is to JAR up the directory as a RAR file once the configuration is solid enough that it no longer needs to be changed. But leaving everything in a directory during development is the easiest path.</p></rich-text-body></structured-macro> <p>Now expand the activemq-ra-4.0.2.rar into the current working directory:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="b59168c6-1886-46c9-8b3b-c33ae6953b52" ac:name="code" ac:schema-version="1"><plain-text-body> jar xvf /opt/incubator-activemq-4.0.2/lib/optional/activemq-ra-4.0.2.rar created: META-INF/ inflated: META-INF/MANIFEST.MF @@ -145,11 +133,9 @@ jar xvf /opt/incubator-activemq-4.0.2/lib/optional/activemq-ra-4.0.2.rar inflated: log4j-1.2.12.jar inflated: META-INF/DISCLAIMER.txt inflated: META-INF/LICENSE.txt -]]></script> -</div></div> +</plain-text-body></structured-macro> <p>Below is a quick listing of the contents of that directory:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="cd5b60d0-b463-4799-862a-2e6bef89f317" ac:name="code" ac:schema-version="1"><plain-text-body> $ ls -l total 12848 drwxr-xr-x 6 bsnyder bsnyder 204 Oct 16 16:27 META-INF @@ -164,21 +150,18 @@ drwxr-xr-x 6 bsnyder bsnyder 204 Oct 16 16:27 META-INF -rw-r--r-- 1 bsnyder bsnyder 358085 Oct 16 16:27 log4j-1.2.12.jar -rw-r--r-- 1 bsnyder bsnyder 1901653 Oct 16 16:27 spring-1.2.6.jar -rw-r--r-- 1 bsnyder bsnyder 94713 Oct 16 16:27 xbean-spring-2.2.jar -]]></script> -</div></div> +</plain-text-body></structured-macro> <p>Now it's time to configure ActiveMQ.</p> -<h2 id="IntegratingApacheActiveMQwithJBoss-ConfiguringApacheActiveMQ">Configuring Apache ActiveMQ</h2> +<h2>Configuring Apache ActiveMQ</h2> <p>The fifth step is to actually configure ActiveMQ for integration with JBoss. Remember that you should be sitting in the following directory:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="ec3c4d38-41bf-40f1-9deb-3767135411c9" ac:name="code" ac:schema-version="1"><plain-text-body> /opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar -]]></script> -</div></div> +</plain-text-body></structured-macro> <p>You may or may not have installed JBoss in <code>/opt</code>, that doesn't particularly matter. What does matter is that you're sitting in the directory that was created above to hold the contents of the expanded ActiveMQ RAR file.</p> -<div class="panel" style="background-color: #ccccff;border-width: 1px;"><div class="panelContent" style="background-color: #ccccff;"> -<p><strong><em>NOTE:</em></strong> A RAR file is a Resource adapter ARchive (RAR). Resource adapters are a concept from the <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/connector/"; rel="nofollow">J2EE Connector Architecture (JCA)</a> and are used to interface with Enterprise Information Systems (EIS), i.e., systems external to the application server (e.g., relational databases, mainframes, MOMs, accounting systems, etc.). Resource adapters are often referred to as J2EE connectors and are very similar to the concept of a device driver for, say, a printer in that they contain information specific to connecting to a particular system. The difference with JCA is that that connection has been formalized in specification for Java. So the overall concepts of JCA is for connection to any EIS, but what does that mean? JCA 1.5 provides connectivity and more via the following contracts:</p> +<structured-macro ac:macro-id="c0800a73-554e-4dc9-9f81-d0fe7bd1cdfc" ac:name="panel" ac:schema-version="1"><parameter ac:name="bgColor">#ccccff</parameter><rich-text-body> +<p><strong><em>NOTE:</em></strong> A RAR file is a Resource adapter ARchive (RAR). Resource adapters are a concept from the <a shape="rect" href="http://java.sun.com/j2ee/connector/";>J2EE Connector Architecture (JCA)</a> and are used to interface with Enterprise Information Systems (EIS), i.e., systems external to the application server (e.g., relational databases, mainframes, MOMs, accounting systems, etc.). Resource adapters are often referred to as J2EE connectors and are very similar to the concept of a device driver for, say, a printer in that they contain information specific to connecting to a particular system. The difference with JCA is that that connection has been formalized in specification for Java. So the overall concepts of JCA is for connection to any EIS, but what does that mean? JCA 1.5 provides connectivity and more via the following contracts:</p> <p>Version 1.0 Contracts</p> @@ -192,45 +175,39 @@ drwxr-xr-x 6 bsnyder bsnyder 204 Oct 16 16:27 META-INF <ul><li>Lifecycle Management Contract: Lets the application server manage the lifecycle – that is, the startup and shutdown functionality – of the resource adapter.</li><li>Work Management Contract: Allows the resource adapter to do work by submitting it to an application server for execution. Since the application server does the work for the resource adapter, the resource adapter needn't worry about thread management. Instead, the application server manages this aspect efficiently and can use thread pooling if necessary. Although the work management contract is not required (the resource adapter can choose to manage its own thread for work), it is definitely recommended.</li><li>Transaction Inflow Contract: Allows a resource adapter to propagate an imported transaction to an application server, as well as flow-in transaction completion and crash recovery initiated by an EIS.</li><li>Message Inflow Contract: Allows the resource adapter to synchronously or asynchronously deliver messages to endpoints in the application server, irrespective of message style, semantics, and infrastructure.</li></ul> -<p><sub>Quoted from</sub> <sub><a shape="rect" class="external-link" href="http://java.sun.com/developer/technicalArticles/J2EE/connectorarch1_5/"; rel="nofollow"><sub>What's New in the J2EE Connector Architecture 1.5</sub></a></sub></p> +<p><sub>Quoted from</sub> <sub><a shape="rect" href="http://java.sun.com/developer/technicalArticles/J2EE/connectorarch1_5/";><sub>What's New in the J2EE Connector Architecture 1.5</sub></a></sub></p> -<p>For more information about JCA, please consult the <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/connector/index.jsp"; rel="nofollow">J2EE Connector Architecture documentation</a>.</p> -</div></div> +<p>For more information about JCA, please consult the <a shape="rect" href="http://java.sun.com/j2ee/connector/index.jsp";>J2EE Connector Architecture documentation</a>.</p></rich-text-body></structured-macro> <p>Open the <code>META-INF/ra.xml</code> file and look for the following section:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>META-INF/ra.xml</b></div><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="60f6b9af-051c-4c7d-9266-2ceb2c9a4bbd" ac:name="code" ac:schema-version="1"><parameter ac:name="title">META-INF/ra.xml</parameter><plain-text-body> <config-property> <description> The URL to the ActiveMQ server that you want this connection to connect to. If using - an embedded broker, this value should be 'vm://localhost'. + an embedded broker, this value should be 'vm://localhost'. </description> <config-property-name>ServerUrl</config-property-name> <config-property-type>java.lang.String</config-property-type> <config-property-value>tcp://localhost:61616</config-property-value> <!-- <config-property-value>vm://localhost</config-property-value> --> </config-property> -]]></script> -</div></div> +</plain-text-body></structured-macro> <p>The section above is used to tell the ActiveMQ RAR where ActiveMQ is located. By default, the in-VM protocol is commented out in favor of the tcp protocol. This will find ActiveMQ running on any interface on the localhost on port 61616. It's ok to just leave this alone if you don't mind the inefficiency of communicating within the JVM via TCP. However, it is recommended that <code>vm://</code> transport be used for an embedded broker, so comment out the <code>tcp://</code> transport and uncomment the <code>vm://</code> transport. Below is an example of this:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>META-INF/ra.xml</b></div><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="fdda2ef7-5c59-424b-bb81-8fe635e3e14f" ac:name="code" ac:schema-version="1"><parameter ac:name="title">META-INF/ra.xml</parameter><plain-text-body> <config-property> <description> The URL to the ActiveMQ server that you want this connection to connect to. If using - an embedded broker, this value should be 'vm://localhost'. + an embedded broker, this value should be 'vm://localhost'. </description> <config-property-name>ServerUrl</config-property-name> <config-property-type>java.lang.String</config-property-type> <!-- <config-property-value>tcp://localhost:61616</config-property-value> --> <config-property-value>vm://localhost</config-property-value> </config-property> -]]></script> -</div></div> +</plain-text-body></structured-macro> <p>Because we're embedding ActiveMQ inside of JBoss, it is more efficient to use the <code>vm://</code> transport, rather than to perform messaging over the <code>tcp://</code> transport.</p> <p>Now look further down the <code>META-INF/ra.xml</code> file and locate the following section:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>META-INF/ra.xml</b></div><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="b727474f-93c3-4537-8228-296b250ffc14" ac:name="code" ac:schema-version="1"><parameter ac:name="title">META-INF/ra.xml</parameter><plain-text-body> <config-property> <description> Sets the XML configuration file used to configure the embedded ActiveMQ broker via @@ -248,11 +225,9 @@ drwxr-xr-x 6 bsnyder bsnyder 204 Oct 16 16:27 META-INF <config-property-value>xbean:broker-config.xml</config-property-value> --> </config-property> -]]></script> -</div></div> +</plain-text-body></structured-macro> <p>The section above needs to be changed to uncomment the second to last line and remove/replace the empty element that is above it. Below is an example of how this should be changed:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>META-INF/ra.xml</b></div><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="cc4ec3ed-0668-4861-b33c-d5be8a95225c" ac:name="code" ac:schema-version="1"><parameter ac:name="title">META-INF/ra.xml</parameter><plain-text-body> <config-property> <description> Sets the XML configuration file used to configure the embedded ActiveMQ broker via @@ -267,80 +242,67 @@ drwxr-xr-x 6 bsnyder bsnyder 204 Oct 16 16:27 META-INF <config-property-type>java.lang.String</config-property-type> <config-property-value>xbean:broker-config.xml</config-property-value> </config-property> -]]></script> -</div></div> +</plain-text-body></structured-macro> <p>This change tells the ActiveMQ RAR to read a configuration file named <code>broker-config.xml</code> (the <code>xbean:</code> that proceeds the filename is simply a hint to class doing the reading of the configuration file) which is located on the CLASSPATH. In this case, the <code>broker-config.xml</code> file is located in the <code>activemq-ra.rar</code> directory. Save the changes to that file and then open the <code>broker-config.xml</code> file.</p> <p>The <code>broker-config.xml</code> file <em>is</em> the ActiveMQ configuration file. This is the file used to configure ActiveMQ. The default contents of this file are usable, but should be customized to suit your environment. There are several items of note about this configuration. The most prominent sections to note in this file are the <code><persistenceAdapter></code> element and the <code><transportConnectors></code> and <code><networkConnectors></code> elements as seen below:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>broker-config.xml</b></div><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ -<beans xmlns="http://activemq.org/config/1.0"> +<structured-macro ac:macro-id="af48af35-393f-417b-906d-f17f34eabda8" ac:name="code" ac:schema-version="1"><parameter ac:name="title">broker-config.xml</parameter><plain-text-body> +<beans xmlns="http://activemq.org/config/1.0"> - <broker useJmx="true"> + <broker useJmx="true"> ... <persistenceAdapter> - <journaledJDBC journalLogFiles="5" dataDirectory="activemq-data"/> + <journaledJDBC journalLogFiles="5" dataDirectory="activemq-data"/> <!-- To use a different datasource, use th following syntax : --> <!-- - <journaledJDBC journalLogFiles="5" dataDirectory="../data" dataSource="#postgres-ds"/> + <journaledJDBC journalLogFiles="5" dataDirectory="../data" dataSource="#postgres-ds"/> --> </persistenceAdapter> <transportConnectors> <!-- prefixing a connector with discovery: causes the connector to be advertiesed over rendezvous --> - <transportConnector uri="tcp://localhost:61616" discoveryUri="multicast://default"/> + <transportConnector uri="tcp://localhost:61616" discoveryUri="multicast://default"/> </transportConnectors> <networkConnectors> <!-- by default just auto discover the other brokers --> - <networkConnector uri="multicast://default"/> + <networkConnector uri="multicast://default"/> <!-- - <networkConnector uri="static://(tcp://host1:61616,tcp://host2:61616)"/> + <networkConnector uri="static://(tcp://host1:61616,tcp://host2:61616)"/> --> </networkConnectors> </broker> </beans> -]]></script> -</div></div> +</plain-text-body></structured-macro> <p>The first change to this file is to add the brokerName attribute to the broker element and provide a name:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ -<broker useJmx="true" brokerName="bruce.broker1"> -]]></script> -</div></div> +<structured-macro ac:macro-id="03cf582d-73c3-45a2-bd0d-9b0ea96e191a" ac:name="code" ac:schema-version="1"><plain-text-body> +<broker useJmx="true" brokerName="bruce.broker1"> +</plain-text-body></structured-macro> <p>In addition, this same name is used further down the configuration to provide a name for the <code><transportConnector></code> element:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ -<transportConnector name="bruce.broker1" uri="tcp://localhost:61616" discoveryUri="multicast://default"/> -]]></script> -</div></div> +<structured-macro ac:macro-id="34a54822-38c1-464d-9596-05153a1be414" ac:name="code" ac:schema-version="1"><plain-text-body> +<transportConnector name="bruce.broker1" uri="tcp://localhost:61616" discoveryUri="multicast://default"/> +</plain-text-body></structured-macro> <p>Now we'll tell ActiveMQ not to initialize JMX because we'll use the existing one that JBoss has:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="6722ef5d-9c32-4fba-89a9-405bf8678a2c" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <!-- put the following as the first child of the broker tag --> -<managementContext><!-- we'll use an existing one (JBoss) instead of creating one --> - <managementContext createConnector="false"/> +<managementContext><!-- we'll use an existing one (JBoss) instead of creating one --> + <managementContext createConnector="false"/> </managementContext> -]]></script> -</div></div> +</plain-text-body></structured-macro> <p>The <code><persistenceAdapter></code> element should be reconfigured to store its data in an appropriate place. On JBoss, that's most likely within the "data" directory of the server configuration you're using. We're going to set this dynamically using an XBean and Spring feature that allows us to inject system properties values into the configuration. First this needs to be enabled:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="808a9522-c308-4270-9e82-4374dd0ecebb" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <!-- put the following as the first child of the beans element --> -<bean xmlns="" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/> -]]></script> -</div></div> +<bean xmlns="" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/> +</plain-text-body></structured-macro> <p>Now, modify the <code>dataDirectory</code> attribute of the <code>journaledJDBC</code> element to be the following: <code>${jboss.server.data.dir}/activemq</code>.</p> -<p>The <code><transportConnectors></code> element is used to advertise the ActiveMQ broker for client-to-broker communications and the <code><networkConnectors></code> element advertises the ActiveMQ broker for broker-to-broker communications. The default configuration is to use the ActiveMQ <a shape="rect" class="external-link" href="http://www.activemq.org/site/multicast-transport-reference.html"; rel="nofollow">multicast transport</a> for both. This is simply an easy configuration under which to get ActiveMQ up and running, so we'll just leave it at that for the time being.</p> -<div class="panel" style="background-color: #ccccff;border-width: 1px;"><div class="panelContent" style="background-color: #ccccff;"> -<p><strong><em>NOTE:</em></strong> There are far more configuration options available for ActiveMQ than are noted here. The configuration above is only enough to just get ActiveMQ up and running, nothing more. For more information on the ActiveMQ configuration, see the <a shape="rect" class="external-link" href="http://www.activemq.org/site/xbean-xml-reference-41.html"; rel="nofollow">ActiveMQ 4.1 XML Reference</a>.</p> -</div></div> +<p>The <code><transportConnectors></code> element is used to advertise the ActiveMQ broker for client-to-broker communications and the <code><networkConnectors></code> element advertises the ActiveMQ broker for broker-to-broker communications. The default configuration is to use the ActiveMQ <a shape="rect" href="http://www.activemq.org/site/multicast-transport-reference.html";>multicast transport</a> for both. This is simply an easy configuration under which to get ActiveMQ up and running, so we'll just leave it at that for the time being.</p> +<structured-macro ac:macro-id="b2fd7dca-0195-45f9-beaa-a35e3502a0e4" ac:name="panel" ac:schema-version="1"><parameter ac:name="bgColor">#ccccff</parameter><rich-text-body> +<p><strong><em>NOTE:</em></strong> There are far more configuration options available for ActiveMQ than are noted here. The configuration above is only enough to just get ActiveMQ up and running, nothing more. For more information on the ActiveMQ configuration, see the <a shape="rect" href="http://www.activemq.org/site/xbean-xml-reference-41.html";>ActiveMQ 4.1 XML Reference</a>.</p></rich-text-body></structured-macro> <p>Now we just need to start up JBoss to assure that it comes up correctly without error using the same commands we used previously to start JBoss:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="99275948-d5a3-4e82-9827-5827c1f58ed4" ac:name="code" ac:schema-version="1"><plain-text-body> $ cd jboss-4.0.4.GA $ ./bin/run.sh -c default ========================================================================= @@ -372,20 +334,18 @@ $ ./bin/run.sh -c default ... 15:35:17,360 INFO [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)] Started in 28s:576ms -]]></script> -</div></div> +</plain-text-body></structured-macro> <p>As long as JBoss comes up without error, you're ready to move on to the next step.</p> -<h2 id="IntegratingApacheActiveMQwithJBoss-ConfiguringJBoss">Configuring JBoss</h2> +<h2>Configuring JBoss</h2> -<p>The sixth step is to configure JBoss to initialize and start ActiveMQ whenever JBoss starts up. This is accomplished using an XML file that abides by the <a shape="rect" class="external-link" href="http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd"; rel="nofollow">JBoss JCA DTD</a> for data sources. Like most other Java application servers on the market, the JBoss architecture uses the J2EE Connector Architecture to manage connections of any kind including JDBC, JMS, etc. and the JBoss JCA DTD denotes the allowed contents for creating an XML data source instance to configure JBoss JCA. Below is an example XML data source instance for use with JBoss:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>activemq-jms-ds.xml</b></div><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ -<?xml version="1.0" encoding="UTF-8"?> +<p>The sixth step is to configure JBoss to initialize and start ActiveMQ whenever JBoss starts up. This is accomplished using an XML file that abides by the <a shape="rect" href="http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd";>JBoss JCA DTD</a> for data sources. Like most other Java application servers on the market, the JBoss architecture uses the J2EE Connector Architecture to manage connections of any kind including JDBC, JMS, etc. and the JBoss JCA DTD denotes the allowed contents for creating an XML data source instance to configure JBoss JCA. Below is an example XML data source instance for use with JBoss:</p> +<structured-macro ac:macro-id="71943892-d21f-4db7-bcaf-463eb91e23d2" ac:name="code" ac:schema-version="1"><parameter ac:name="title">activemq-jms-ds.xml</parameter><plain-text-body> +<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE connection-factories - PUBLIC "-//JBoss//DTD JBOSS JCA Config 1.5//EN" - "http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd"> + PUBLIC "-//JBoss//DTD JBOSS JCA Config 1.5//EN" + "http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd"> <connection-factories> @@ -423,26 +383,24 @@ Started in 28s:576ms <idle-timeout-minutes>3</idle-timeout-minutes> </tx-connection-factory> - <mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.queue:name=outboundQueue"> - <attribute name="JNDIName">activemq/queue/outbound</attribute> - <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-ra.rar'</depends> - <attribute name="Type">javax.jms.Queue</attribute> - <attribute name="Properties">PhysicalName=queue.outbound</attribute> + <mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.queue:name=outboundQueue"> + <attribute name="JNDIName">activemq/queue/outbound</attribute> + <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-ra.rar'</depends> + <attribute name="Type">javax.jms.Queue</attribute> + <attribute name="Properties">PhysicalName=queue.outbound</attribute> </mbean> - <mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.topic:name=inboundTopic"> - <attribute name="JNDIName">activemq/topic/inbound</attribute> - <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-ra.rar'</depends> - <attribute name="Type">javax.jms.Topic</attribute> - <attribute name="Properties">PhysicalName=topic.inbound</attribute> + <mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.topic:name=inboundTopic"> + <attribute name="JNDIName">activemq/topic/inbound</attribute> + <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-ra.rar'</depends> + <attribute name="Type">javax.jms.Topic</attribute> + <attribute name="Properties">PhysicalName=topic.inbound</attribute> </mbean> </connection-factories> -]]></script> -</div></div> +</plain-text-body></structured-macro> <p>This XML instance configures a JMS <code>QueueConnectionFactory</code> and a JMS <code>TopicConnectionFactory</code> and makes them available via JNDI. Also defined in this file are some {{AdminObject}}s which are used to specify a topic and a queue. This file should be dropped into the JBoss deploy directory. Its name (*-ds.xml) will cause it to be picked up by the JBoss deployer upon startup. Speaking of which, once this file is in place, a quick smoke test can be performed by simply starting up the JBoss server. Below is an example of the output that should be seen:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="4a3ffbcf-5e58-42dd-8c5f-1d77b501c805" ac:name="code" ac:schema-version="1"><plain-text-body> ========================================================================= JBoss Bootstrap Environment @@ -470,7 +428,7 @@ Started in 28s:576ms 22:55:48,704 INFO [Server] Server Temp Dir: /opt/jboss-4.0.4.GA/server/default/tmp 22:55:48,706 INFO [Server] Root Deployment Filename: jboss-service.xml 22:55:49,092 INFO [ServerInfo] Java version: 1.5.0_06,Apple Computer, Inc. -22:55:49,101 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_06-64,"Apple Computer, Inc." +22:55:49,101 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_06-64,"Apple Computer, Inc." 22:55:49,102 INFO [ServerInfo] OS-System: Mac OS X 10.4.8,i386 22:55:49,803 INFO [Server] Core system initialized 22:55:53,379 INFO [WebService] Using RMI server codebase: http://rattlesnake:8083/ @@ -511,10 +469,10 @@ beans [org.apache.activemq.xbean.XBeanBrokerService]; root of BeanFactory hierar [org.apache.xbean.spring.context.ClassPathXmlApplicationContext;hashCode=13887543] 22:56:07,773 INFO [CollectionFactory] JDK 1.4+ collections available 22:56:07,778 INFO [ClassPathXmlApplicationContext] Unable to locate MessageSource with name -'messageSource': using default +'messageSource': using default [org.springframework.context.support.DelegatingMessageSource@5fee96] 22:56:07,781 INFO [ClassPathXmlApplicationContext] Unable to locate ApplicationEventMulticaster -with name 'applicationEventMulticaster': using default +with name 'applicationEventMulticaster': using default [org.springframework.context.event.SimpleApplicationEventMulticaster@78c714] 22:56:07,783 INFO [DefaultListableBeanFactory] Pre-instantiating singletons in factory [org.springframework.beans.factory.support.DefaultListableBeanFactory @@ -546,17 +504,17 @@ using 5 x 20.0 Megs at: /opt/jboss-4.0.4.GA/activemq-data/journal 22:56:11,847 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar 22:56:12,251 INFO [ConnectionFactoryBindingService] Bound ConnectionManager -'jboss.jca:service=ConnectionFactoryBinding,name=activemq/QueueConnectionFactory' to -JNDI name 'java:activemq/QueueConnectionFactory' +'jboss.jca:service=ConnectionFactoryBinding,name=activemq/QueueConnectionFactory' to +JNDI name 'java:activemq/QueueConnectionFactory' 22:56:12,258 INFO [ConnectionFactoryBindingService] Bound ConnectionManager -'jboss.jca:service=ConnectionFactoryBinding,name=activemq/TopicConnectionFactory' to -JNDI name 'java:activemq/TopicConnectionFactory' -22:56:12,265 INFO [AdminObject] Bound admin object 'org.apache.activemq.command.ActiveMQQueue' -at 'activemq/queue/outbound' -22:56:12,330 INFO [AdminObject] Bound admin object 'org.apache.activemq.command.ActiveMQTopic' -at 'activemq/topic/inbound' +'jboss.jca:service=ConnectionFactoryBinding,name=activemq/TopicConnectionFactory' to +JNDI name 'java:activemq/TopicConnectionFactory' +22:56:12,265 INFO [AdminObject] Bound admin object 'org.apache.activemq.command.ActiveMQQueue' +at 'activemq/queue/outbound' +22:56:12,330 INFO [AdminObject] Bound admin object 'org.apache.activemq.command.ActiveMQTopic' +at 'activemq/topic/inbound' 22:56:13,246 INFO [ConnectionFactoryBindingService] Bound ConnectionManager -'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS' +'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS' 22:56:13,842 INFO [A] Bound to JNDI name: queue/A 22:56:13,845 INFO [B] Bound to JNDI name: queue/B 22:56:13,846 INFO [C] Bound to JNDI name: queue/C @@ -569,24 +527,22 @@ at 'activemq/topic/inbound' 22:56:13,994 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093 22:56:14,055 INFO [DLQ] Bound to JNDI name: queue/DLQ 22:56:14,375 INFO [ConnectionFactoryBindingService] Bound ConnectionManager -'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA' +'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA' 22:56:14,525 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/ 22:56:14,991 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080 22:56:15,071 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009 22:56:15,082 INFO [JkMain] Jk running ID=0 time=0/25 config=null 22:56:15,108 INFO [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)] Started in 26s:398ms -]]></script> -</div></div> +</plain-text-body></structured-macro> <p>Note the startup messages from both ActiveMQ and from the <code>AdminObject}}s creating an {{ActiveMQQueue</code> and an <code>ActiveMQTopic</code>. These are good indications that the configuration is correct, but needs to be verified a bit further. This is covered in the next section.</p> -<h2 id="IntegratingApacheActiveMQwithJBoss-TestingtheIntegration">Testing the Integration</h2> +<h2>Testing the Integration</h2> <p>The seventh and final step is to perform a slightly more comprehensive smoke test of the integration. This can be accomplished using Apache Ant via the examples that come with the ActiveMQ binary distribution. An Ant build.xml file is included which provides easy access to a simple consumer and a simple producer. The producer will be used to send messages that are received by the consumer. To proceed with this testing, just follow the steps below:</p> <ol><li>In the first terminal, start up JBoss. The same startup script can be used here as was used above.</li><li>In the second terminal, use the commands below to run the ActiveMQ consumer: -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ -$ cd /opt/incubator-activemq-4.0.2/examples #note in activemq v5 the directory is just "example" not "examples" +<structured-macro ac:macro-id="83da24fc-8569-41f8-98e1-80cd0847b639" ac:name="code" ac:schema-version="1"><plain-text-body> +$ cd /opt/incubator-activemq-4.0.2/examples #note in activemq v5 the directory is just "example" not "examples" $ ant consumer Buildfile: build.xml @@ -603,10 +559,8 @@ consumer: [java] Consuming queue: TEST.FOO [java] Using non-durable subscription [java] We are about to wait until we consume: 10 message(s) then we will shutdown -]]></script> -</div></div></li><li>In the third terminal, use the commands below to run the ActiveMQ producer: -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +</plain-text-body></structured-macro></li><li>In the third terminal, use the commands below to run the ActiveMQ producer: +<structured-macro ac:macro-id="b1fdb2dd-302a-4340-9223-be539c22f866" ac:name="code" ac:schema-version="1"><plain-text-body> $ cd /opt/incubator-activemq-4.0.2/examples $ ant producer Buildfile: build.xml @@ -680,8 +634,7 @@ description: Time spent by a message before being delivered } [java] } [java] } [java] } -]]></script> -</div></div></li></ol> +</plain-text-body></structured-macro></li></ol> <p>Step 1 above just starts up JBoss. Step 2 above starts up a simple message consumer that comes with ActiveMQ. Step 3 above starts up a simple message producer that comes with ActiveMQ. Though the message consumer and message producer are simple utilities, the each one accepts many parameters making them extremely useful for testing ActiveMQ configurations.</p> @@ -690,123 +643,12 @@ description: Time spent by a message before being delivered } <p>After setting up one broker within one instance of JBoss, setting up another is made much easier, but requires another machine or operating system instance. But that's a whole separate article and something to address another day.</p> -<h2 id="IntegratingApacheActiveMQwithJBoss-Conclusion">Conclusion</h2> +<h2>Conclusion</h2> -<p>What has been demonstrated here is the integration of ActiveMQ with the JBoss application server. This integration is quite common and performed by many enterprises. I hope that this was helpful to people interested in the integration of ActiveMQ with JBoss application server. If you have any questions or are interested in consulting services surrounding ActiveMQ, please <a shape="rect" class="external-link" href="http://www.logicblaze.com/contact.jsp"; rel="nofollow">contact us</a> for more information.</p> +<p>What has been demonstrated here is the integration of ActiveMQ with the JBoss application server. This integration is quite common and performed by many enterprises. I hope that this was helpful to people interested in the integration of ActiveMQ with JBoss application server. If you have any questions or are interested in consulting services surrounding ActiveMQ, please <a shape="rect" href="http://www.logicblaze.com/contact.jsp";>contact us</a> for more information.</p> -<h3 id="IntegratingApacheActiveMQwithJBoss-Resources">Resources</h3> +<h3>Resources</h3> <p>Below are the configurations for use with both Spring 1.x and Spring 2.x:</p> - - - - -<div class="plugin_attachments_container"> - <div class="plugin_attachments_table_container"> - <fieldset class="hidden"> - <input type="hidden" class="plugin_attachments_macro_render_param" name="pageId" value="67786"> - <input type="hidden" name="deleteConfirmMessage" value="Are you sure you want to send the attached file " _0="_0" to="to" the="the" trash="trash" only="only" a="a" space="space" administrator="administrator" can="can" undo="undo" this="this" action.="action."> - <input type="hidden" name="outputType" value="display"> - </fieldset> - - - - - - - - - - - -<table class="attachments aui"><thead><tr><th colspan="1" rowspan="1" class="expand-column attachment-summary-toggle"> </th><th colspan="1" rowspan="1" class="filename-column"> <a shape="rect" href="integrating-apache-activemq-with-jboss.xml?sortBy=name&sortOrder=ascending">File</a> - </th><th colspan="1" rowspan="1" class="modified-column"> <span class="propersortedby $sortOrder"><a shape="rect" href="integrating-apache-activemq-with-jboss.xml?sortBy=date&sortOrder=descending">Modified</a></span> - </th></tr></thead><tbody><tr class="attachment-row" id="attachment-59670763" data-attachment-id="59670763" data-attachment-idx="1"><td colspan="1" rowspan="1" class="attachment-summary-toggle"> - <span class="icon icon-section-closed" title="Show more info"></span> - </td><td colspan="1" rowspan="1" class="filename-column"> - - - - - -<span class="icon icon-file-unknown" title="File">File</span> <a shape="rect" class="filename" href="integrating-apache-activemq-with-jboss.data/amq-spring-1.2.6.tgz?api=v2" title="Download" data-filename="amq-spring-1.2.6.tgz" data-type="application/x-tar" data-linked-resource-container-id="67786"> - amq-spring-1.2.6.tgz - </a> - </td><td colspan="1" rowspan="1" class="attachment-created modified-column"> - <span>Oct 03, 2007</span> - <span>by</span> - <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~bsnyder";>Bruce Snyder</a> </td></tr><tr class="attachment-summary attachment-summary-59670763 hidden" data-attachment-id="59670763" data-attachment-filename="amq-spring-1.2.6.tgz"><td colspan="1" rowspan="1" class="attachment-summary-toggle"></td><td colspan="2" rowspan="1" class="attachment-details-wrapper"> - - - <p class="attachment-labels">Labels</p> - -<div class="labels-section-content content-column" entityid="59670763" entitytype="attachment"> - <div class="labels-content"> - - <ul class="label-list has-pen"><li class="no-labels-message"> - No labels - </li><li class="labels-edit-container"> - <a shape="rect" class="show-labels-editor" href="#" title="Edit Labels"> - <span class="aui-icon aui-icon-small aui-iconfont-edit-small">Edit Labels</span> - </a> - </li></ul> - - </div> -</div> - - <div class="attachment-history-wrapper"></div> - - <div class="attachment-buttons"> - <a shape="rect" class="aui-button previewAttachmentLink" data-filename="amq-spring-1.2.6.tgz" data-file-src="/confluence/download/attachments/67786/amq-spring-1.2.6.tgz?api=v2" data-linked-resource-default-alias="amq-spring-1.2.6.tgz" data-mime-type="application/x-tar" data-linked-resource-container-id="67786" data-linked-resource-id="59670763">Preview</a> - - </div> - </td></tr><tr class="attachment-row" id="attachment-59670764" data-attachment-id="59670764" data-attachment-idx="2"><td colspan="1" rowspan="1" class="attachment-summary-toggle"> - <span class="icon icon-section-closed" title="Show more info"></span> - </td><td colspan="1" rowspan="1" class="filename-column"> - - - - - -<span class="icon icon-file-unknown" title="File">File</span> <a shape="rect" class="filename" href="integrating-apache-activemq-with-jboss.data/amq-spring-2.0.tgz?api=v2" title="Download" data-filename="amq-spring-2.0.tgz" data-type="application/x-tar" data-linked-resource-container-id="67786"> - amq-spring-2.0.tgz - </a> - </td><td colspan="1" rowspan="1" class="attachment-created modified-column"> - <span>Oct 03, 2007</span> - <span>by</span> - <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~bsnyder";>Bruce Snyder</a> </td></tr><tr class="attachment-summary attachment-summary-59670764 hidden" data-attachment-id="59670764" data-attachment-filename="amq-spring-2.0.tgz"><td colspan="1" rowspan="1" class="attachment-summary-toggle"></td><td colspan="2" rowspan="1" class="attachment-details-wrapper"> - - - <p class="attachment-labels">Labels</p> - -<div class="labels-section-content content-column" entityid="59670764" entitytype="attachment"> - <div class="labels-content"> - - <ul class="label-list has-pen"><li class="no-labels-message"> - No labels - </li><li class="labels-edit-container"> - <a shape="rect" class="show-labels-editor" href="#" title="Edit Labels"> - <span class="aui-icon aui-icon-small aui-iconfont-edit-small">Edit Labels</span> - </a> - </li></ul> - - </div> -</div> - - <div class="attachment-history-wrapper"></div> - - <div class="attachment-buttons"> - <a shape="rect" class="aui-button previewAttachmentLink" data-filename="amq-spring-2.0.tgz" data-file-src="/confluence/download/attachments/67786/amq-spring-2.0.tgz?api=v2" data-linked-resource-default-alias="amq-spring-2.0.tgz" data-mime-type="application/x-tar" data-linked-resource-container-id="67786" data-linked-resource-id="59670764">Preview</a> - - </div> - </td></tr></tbody></table> - </div> - <div class="plugin_attachments_upload_container"> - </div> - - <div> - <a shape="rect" class="download-all-link" href="/confluence/pages/downloadallattachments.action?pageId=67786" title="Download all the latest versions of attachments on this page as single zip file.">Download All</a> - </div> -</div> -</div> +<structured-macro ac:macro-id="eda15643-f616-42ea-bd14-d9b2d1397323" ac:name="attachments" ac:schema-version="1"></structured-macro></div>
http://git-wip-us.apache.org/repos/asf/activemq-web/blob/7a7d976c/integration-tests.xml ---------------------------------------------------------------------- diff --git a/integration-tests.xml b/integration-tests.xml index 987a85a..152901e 100644 --- a/integration-tests.xml +++ b/integration-tests.xml @@ -1,73 +1,63 @@ <div class="wiki-content maincontent"> <p>The Integration Tests validate that ActiveMQ Resource Adapter operate correctly when deployed with a J2EE application running in an Application Server such as Apache Geronimo.</p> -<h2 id="IntegrationTests-GettingReady">Getting Ready</h2> +<h2>Getting Ready</h2> <p>The instructions on this page reference a few directories that you will need to substitute appropriate values for:</p> <ul><li><em>activemq-core</em> is where your ActiveMQ source code is located.</li><li><em>geronimo-home</em> is where your Geronimo home directory is located.</li></ul> -<h2 id="IntegrationTests-BuildingtheActiveMQResourceAdapter">Building the ActiveMQ Resource Adapter</h2> +<h2>Building the ActiveMQ Resource Adapter</h2> <p>The ActiveMQ Resource Adapter allows a J2EE Application Server to provide transaction management, connection pooling and security to ActiveMQ connection when used by EJBs. The Resource Adapter is deployed in the client EAR that will be using the ActiveMQ.</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="ee6afd83-8b33-4daa-b68f-e794c0025e20" ac:name="code" ac:schema-version="1"><plain-text-body> cd activemq-ra maven rar:install-snapshot -]]></script> -</div></div> +</plain-text-body></structured-macro> <p> </p> <p> </p> -<h2 id="IntegrationTests-BuildingtheIntegrationTestEJBmodule">Building the Integration Test EJB module</h2> +<h2>Building the Integration Test EJB module</h2> <p>The Integration Test EJB module provides a set of EJBs that the tests are run against.</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="d638161b-414d-4cf3-9e0d-dd21bc6c9245" ac:name="code" ac:schema-version="1"><plain-text-body> cd systest/itests/ejb maven -]]></script> -</div></div> +</plain-text-body></structured-macro> <p> </p> <p> </p> -<h2 id="IntegrationTests-BuildingandDeployingtheIntegrationTestEARmodule">Building and Deploying the Integration Test EAR module</h2> +<h2>Building and Deploying the Integration Test EAR module</h2> <p>The EAR module packages up the Resource Adapter and the Integration Tests EJBs into a deployable EAR.</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="c636a44d-9d69-4691-8e51-4cefff3a8559" ac:name="code" ac:schema-version="1"><plain-text-body> cd systest/itests/ear maven -Dgeronimo.home=geronimo-home -]]></script> -</div></div> +</plain-text-body></structured-macro> <p> </p> <p> </p> -<h2 id="IntegrationTests-StartingGeronimowiththeIntegrationTestEARconfiguration.">Starting Geronimo with the Integration Test EAR configuration.</h2> +<h2>Starting Geronimo with the Integration Test EAR configuration.</h2> <p>In a seperate console, issue the following commands</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="2151b074-3e72-4b45-a729-2b872e261a7e" ac:name="code" ac:schema-version="1"><plain-text-body> cd geronimo-home java -jar bin/server.jar org/activemq/ear/itest -]]></script> -</div></div> +</plain-text-body></structured-macro> <p> </p> <p> </p> -<h2 id="IntegrationTests-BuildingandrunningtheIntegrationTests.">Building and running the Integration Tests.</h2> +<h2>Building and running the Integration Tests.</h2> <p>The following builds and runs the integration tests:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="84c9c914-c765-4b10-83c9-008b0f80a189" ac:name="code" ac:schema-version="1"><plain-text-body> cd systest/itests/client maven -]]></script> -</div></div> +</plain-text-body></structured-macro> <p> </p> <p> </p></div> http://git-wip-us.apache.org/repos/asf/activemq-web/blob/7a7d976c/interceptors.xml ---------------------------------------------------------------------- diff --git a/interceptors.xml b/interceptors.xml index fcd09d6..81b867c 100644 --- a/interceptors.xml +++ b/interceptors.xml @@ -1,27 +1,26 @@ -<div class="wiki-content maincontent"><p>ActiveMQ has a sophisticated <em>interceptor stack</em> so that you can attach whatever functionality you require into the broker in an easy way without complicating all of the other broker code. This has really helped us keep the code clean and modular while offering powerful extension points.</p><p>For an example of the kinds of things you can do with interceptors see the following pages</p><ul><li><a shape="rect" href="logging-interceptor.xml">Logging Interceptor</a></li><li><a shape="rect" href="security.xml">Security</a></li><li><a shape="rect" href="visualisation.xml">Visualisation</a></li><li><a shape="rect" href="timestampplugin.xml">TimeStamp on the Broker</a></li><li><a shape="rect" href="statisticsplugin.xml">Get Statistics via Messages</a></li><li><a shape="rect" href="destinations-plugin.xml">Destinations Plugin</a></li></ul><h3 id="Interceptors-Howpluginswork">How plugins work</h3><p>A plugin is an instance of the interface <a s hape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/BrokerPlugin.html";>BrokerPlugin</a> which allows a plugin to add itself into the broker interceptor chain, typically using the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/BrokerFilter.html";>BrokerFilter</a> as a base class to allow only certain operations to be customized.</p><p>The object that implements the BrokerPlugin interface is called out as a plugin in the message broker's XML configuration file (see example below). Your plugin can then optionally reference other beans that are defined in the XML file.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans xmlns="http://www.springframework.org/schema/beans" xmlns:amq="http://activemq.org/config/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans +<div class="wiki-content maincontent"><p>ActiveMQ has a sophisticated <em>interceptor stack</em> so that you can attach whatever functionality you require into the broker in an easy way without complicating all of the other broker code. This has really helped us keep the code clean and modular while offering powerful extension points.</p><p>For an example of the kinds of things you can do with interceptors see the following pages</p><ul><li><link><page ri:content-title="Logging Interceptor"></page></link></li><li><link><page ri:content-title="Security"></page></link></li><li><link><page ri:content-title="Visualisation"></page></link></li><li><link><page ri:content-title="TimeStampPlugin"></page><plain-text-link-body>TimeStamp on the Broker</plain-text-link-body></link></li><li><link><page ri:content-title="StatisticsPlugin"></page><plain-text-link-body>Get Statistics via Messages</plain-text-link-body></link></li><li><link><page ri:content-title="Destinations Plugin"></page></link>< /li></ul><h3>How plugins work</h3><p>A plugin is an instance of the interface <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/BrokerPlugin.html";>BrokerPlugin</a> which allows a plugin to add itself into the broker interceptor chain, typically using the <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/BrokerFilter.html";>BrokerFilter</a> as a base class to allow only certain operations to be customized.</p><p>The object that implements the BrokerPlugin interface is called out as a plugin in the message broker's XML configuration file (see example below). Your plugin can then optionally reference other beans that are defined in the XML file.</p><structured-macro ac:macro-id="656129f8-6ff6-4792-be1a-034e4eb4bfa9" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><beans xmlns="http://www.springframework.org/schema/beans"; xmlns:amq="http://activemq.org/config/1.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd http://activemq.org/config/1.0 -http://activemq.apache.org/schema/activemq-core.xsd http://activemq.apache.org/camel/schema/spring http://activemq.apache.org/camel/schema/spring/camel-spring.xsd"> +http://activemq.apache.org/schema/activemq-core.xsd http://activemq.apache.org/camel/schema/spring http://activemq.apache.org/camel/schema/spring/camel-spring.xsd"> <!-- Allows us to use system properties as variables in this configuration file --> -<bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer" /> +<bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer" /> - <broker xmlns="http://activemq.org/config/1.0" brokerName="localhost" dataDirectory="${activemq.base}/data" plugins="#myPlugin"> + <broker xmlns="http://activemq.org/config/1.0"; brokerName="localhost" dataDirectory="${activemq.base}/data" plugins="#myPlugin"> <!-- The transport connectors ActiveMQ will listen to --> <transportConnectors> - <transportConnector name="openwire" uri="tcp://localhost:61616" /> + <transportConnector name="openwire" uri="tcp://localhost:61616" /> </transportConnectors> </broker> - <bean id="myPlugin" class="org.myorg.MyPlugin"> + <bean id="myPlugin" class="org.myorg.MyPlugin"> <!-- You can reference one or more Spring beans in this file --> - <property name="myMgr" ref="myManager"/> + <property name="myMgr" ref="myManager"/> </bean> - <bean id="myManager" class="org.myorg.MyManager"> - <property name="fooList"> + <bean id="myManager" class="org.myorg.MyManager"> + <property name="fooList"> <list> <value>foo</value> <value>foo2</value> @@ -31,35 +30,31 @@ http://activemq.apache.org/schema/activemq-core.xsd http://activemq.apache.org/c </beans> -]]></script> -</div></div><p>You can also define plugins from within the <plugin> element as this example illustrates.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans xmlns="http://www.springframework.org/schema/beans" xmlns:amq="http://activemq.org/config/1.0" -xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans +</plain-text-body></structured-macro><p>You can also define plugins from within the <plugin> element as this example illustrates.</p><structured-macro ac:macro-id="4c7bdd02-d993-4579-9dd9-0f0aa25d6464" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><beans xmlns="http://www.springframework.org/schema/beans"; xmlns:amq="http://activemq.org/config/1.0"; +xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd http://activemq.org/config/1.0 http://activemq.apache.org/schema/activemq-core.xsd http://activemq.apache.org/camel/schema/spring -http://activemq.apache.org/camel/schema/spring/camel-spring.xsd"> +http://activemq.apache.org/camel/schema/spring/camel-spring.xsd"> <!-- Allows us to use system properties as variables in this configuration file --> - <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer" /> + <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer" /> - <broker xmlns="http://activemq.org/config/1.0" brokerName="localhost" dataDirectory="${activemq.base}/data"> + <broker xmlns="http://activemq.org/config/1.0"; brokerName="localhost" dataDirectory="${activemq.base}/data"> <!-- The transport connectors ActiveMQ will listen to --> <transportConnectors> - <transportConnector name="openwire" uri="tcp://localhost:61616" /> + <transportConnector name="openwire" uri="tcp://localhost:61616" /> </transportConnectors> <plugins> - <bean xmlns="http://www.springframework.org/schema/beans" id="myPlugin" class="org.myorg.MyPlugin"/> + <bean xmlns="http://www.springframework.org/schema/beans"; id="myPlugin" class="org.myorg.MyPlugin"/> </plugins> </broker> </beans> -]]></script> -</div></div><p>At startup, the main or core broker calls your plugin's installPlugin() method. This method creates and returns an object that typically extends <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/BrokerFilter.html";>BrokerFilter</a>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[import org.apache.activemq.broker.Broker; +</plain-text-body></structured-macro><p>At startup, the main or core broker calls your plugin's installPlugin() method. This method creates and returns an object that typically extends <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/BrokerFilter.html";>BrokerFilter</a>.</p><structured-macro ac:macro-id="cf46422e-34b5-4b0a-9df2-52d5b5d113c6" ac:name="code" ac:schema-version="1"><plain-text-body>import org.apache.activemq.broker.Broker; import org.apache.activemq.broker.BrokerPlugin; public class MyPlugin implements BrokerPlugin { @@ -69,9 +64,7 @@ public class MyPlugin implements BrokerPlugin { } } -]]></script> -</div></div><p>The BrokerFilter class is a convenience class that implements the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/Broker.html";>Broker</a> interface. This interface defines all the main operations (e.g., addConnection, addSession, etc.) that your implementation can intercept. The class that extends BrokerFilter overrides any of the methods that are defined in the Broker interface so that it can intercept the corresponding core engine's operations. Here's an example of a class that extends BrokerFilter and intercepts/overrides the addConnection() and addSession() Broker methods/operations.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[import org.apache.activemq.broker.Broker; +</plain-text-body></structured-macro><p>The BrokerFilter class is a convenience class that implements the <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/Broker.html";>Broker</a> interface. This interface defines all the main operations (e.g., addConnection, addSession, etc.) that your implementation can intercept. The class that extends BrokerFilter overrides any of the methods that are defined in the Broker interface so that it can intercept the corresponding core engine's operations. Here's an example of a class that extends BrokerFilter and intercepts/overrides the addConnection() and addSession() Broker methods/operations.</p><structured-macro ac:macro-id="f56ae2b6-9bb1-4c36-8e6a-521868d81a33" ac:name="code" ac:schema-version="1"><plain-text-body>import org.apache.activemq.broker.Broker; import org.apache.activemq.broker.BrokerFilter; import org.apache.activemq.broker.ConnectionContext; import org.apache.activemq.command.ConnectionInfo; @@ -103,6 +96,5 @@ public class MyBroker extends BrokerFilter { -]]></script> -</div></div><p>For more details see <a shape="rect" href="developing-plugins.xml">Developing Plugins</a></p></div> +</plain-text-body></structured-macro><p>For more details see <link><page ri:content-title="Developing Plugins"></page></link></p></div> http://git-wip-us.apache.org/repos/asf/activemq-web/blob/7a7d976c/ioexception-could-not-find-class-for-resource.xml ---------------------------------------------------------------------- diff --git a/ioexception-could-not-find-class-for-resource.xml b/ioexception-could-not-find-class-for-resource.xml index ec41fd4..c7e2e9c 100644 --- a/ioexception-could-not-find-class-for-resource.xml +++ b/ioexception-could-not-find-class-for-resource.xml @@ -1,22 +1,20 @@ <div class="wiki-content maincontent"><p>If you get an exception looking like this</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> -<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ +<structured-macro ac:macro-id="5c09a37c-461c-400a-8682-4acaa5c967c4" ac:name="code" ac:schema-version="1"><plain-text-body> Reason: java.io.exception : could not find class for resource: META-INF/services/org/apache/activemq/transport/tcp -]]></script> -</div></div> +</plain-text-body></structured-macro> <p> </p> -<h3 id="IOException-couldnotfindclassforresource-Cause">Cause</h3> +<h3>Cause</h3> <p>You are probably using the ActiveMQ source code without using the resources</p> -<h3 id="IOException-couldnotfindclassforresource-Quickfix">Quick fix</h3> +<h3>Quick fix</h3> <p>Try one of these</p> <ul><li>use one of the distribution jars for ActiveMQ</li><li>use Maven to run your program</li><li>try adding activemq/src/conf to your classpath</li></ul> -<h3 id="IOException-couldnotfindclassforresource-Background">Background</h3> +<h3>Background</h3> <p>Then it means that the files in META-INF/services could not be found on the classpath. These files are used to support loose coupling on ActiveMQ with the transport protocols (e.g. to avoid a classpath dependency on JXTA) and to allow dynamic protocol enhancement without a change to the core.</p> http://git-wip-us.apache.org/repos/asf/activemq-web/blob/7a7d976c/irc.xml ---------------------------------------------------------------------- diff --git a/irc.xml b/irc.xml index 2ff5a8e..9ed2f2f 100644 --- a/irc.xml +++ b/irc.xml @@ -1,2 +1,2 @@ -<div class="wiki-content maincontent"><p>Committers and contributors can often be found hanging out in IRC. <span style="line-height: 1.4285715;">Below is the information about the channel that we use: </span></p><p><strong>Server:</strong> irc.freenode.net</p><p><strong>Channel:</strong> #apache-activemq</p><p>There are many <a shape="rect" class="external-link" href="https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients"; rel="nofollow">IRC clients</a> available out there depending on the operating system you are using. </p><p> </p><p>Note the IRC channel on codehaus is deprecated as of April 2015; please refrain from using that room.  Likewise, be aware there is a channel named #activemq on the freenode server - please avoid it as well.</p></div> +<div class="wiki-content maincontent"><p>Committers and contributors can often be found hanging out in IRC. <span style="line-height: 1.4285715;">Below is the information about the channel that we use: </span></p><p><strong>Server:</strong> irc.freenode.net</p><p><strong>Channel:</strong> #apache-activemq</p><p>There are many <a shape="rect" href="https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients";>IRC clients</a> available out there depending on the operating system you are using. </p><p> </p><p>Note the IRC channel on codehaus is deprecated as of April 2015; please refrain from using that room.  Likewise, be aware there is a channel named #activemq on the freenode server - please avoid it as well.</p></div> http://git-wip-us.apache.org/repos/asf/activemq-web/blob/7a7d976c/j2ee.xml ---------------------------------------------------------------------- diff --git a/j2ee.xml b/j2ee.xml index b96734c..9869e48 100644 --- a/j2ee.xml +++ b/j2ee.xml @@ -1,5 +1,5 @@ <div class="wiki-content maincontent"> -<p>In J2EE 1.4 or later the standard way to integrate with a JMS provider is via JCA 1.5 and a <a shape="rect" href="resource-adapter.xml">Resource Adapter</a>.</p> +<p>In J2EE 1.4 or later the standard way to integrate with a JMS provider is via JCA 1.5 and a <link><page ri:content-title="Resource Adapter"></page></link>.</p> -<h2 id="J2EE-Introduction">Introduction</h2><p>ActiveMQ includes a Java Connector Architecture (JCA) 1.5 Resource Adapter. JCA 1.5 defines the contract between an J2EE application server and external resources such as databases and messaging middleware. It allows the application server to efficiently pool connections, control transactions and manage security. The Resource Adapter allows ActiveMQ to be used from any J2EE 1.4 application server. We have tested that the Resource Adapter works in the following J2EE 1.4 containers</p><ul><li><a shape="rect" class="external-link" href="http://tomee.apache.org/tomcat-jms.html";>TomEE</a> 1</li><li>Geronimo 1</li><li>GlassFish</li><li>JBoss 4</li><li>WebLogic 9</li><li>WebSphere 6</li></ul><h2 id="J2EE-Features">Features</h2><ul><li>Inbound connection delivers messages to MDBs via XA or local transactions.</li><li>Outbound connections support standard container pooling or can reuse the inbound connection/session to avoid XA.</li><li>JTA supp ort: Can be enlisted in XA and local transactions.</li><li>XA transaction recovery via XAResource.recover() supported.</li><li>When used outside a JTA transaction, session transaction settings retain normal JMS semantics so that it be used by your web-app tier.</li><li>Can configure and start up embedded broker.</li><li>Can connect to external ActiveMQ broker or embedded broker.</li><li>Inbound message delivery supports fine grain control of concurrency and prefetching.</li><li>Batching so that multiple messages can be delivered within the same transaction for optimal performances.</li></ul><h2 id="J2EE-DownloadingtheRAR">Downloading the RAR</h2><p>The RAR is available via <a shape="rect" class="external-link" href="http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22activemq-rar%22"; rel="nofollow">maven central</a></p><p><span style="color: rgb(102,0,51);font-size: 20.0px;line-height: 1.5;">Deployment Guides</span></p><ul><li><a shape="rect" href="tomee.xml">TomEE</a></li><li><a shap e="rect" href="geronimo.xml">Geronimo</a></li><li><a shape="rect" href="integrating-apache-activemq-with-glassfish.xml">Integrating Apache ActiveMQ with Glassfish</a></li><li><a shape="rect" href="jboss-integration.xml">JBoss Integration</a></li></ul><h2 id="J2EE-TheuseofanEmbeddedBroker">The use of an Embedded Broker</h2><p>The ActiveMQ Resource Adapter can connect to a remote broker using any of the available transports, or it can start up an embedded broker. As described in the <a shape="rect" href="resource-adapter-properties.xml">Resource Adapter Properties</a>, you can enable an embedded broker using the <strong>BrokerXmlConfig</strong> property.</p><h2 id="J2EE-ConfigurationReference">Configuration Reference</h2><ul><li><a shape="rect" href="resource-adapter-properties.xml">Resource Adapter Properties</a></li><li><a shape="rect" href="connection-factory-properties.xml">Connection Factory Properties</a></li><li><a shape="rect" href="activation-spec-properties.xml">Activation S pec Properties</a></li></ul></div> +<structured-macro ac:macro-id="bb1a6e8d-0586-4002-8125-6273eff4fed3" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Resource Adapter"></page></link></parameter></structured-macro></div>
