JBoss hornetq SVN: r9346 - trunk/docs/user-manual/en.
by do-not-reply＠jboss.org
Author: ataylor
Date: 2010-06-18 11:07:16 -0400 (Fri, 18 Jun 2010)
New Revision: 9346
Modified:
trunk/docs/user-manual/en/appserver-integration.xml
Log:
HORNETQ-401 - update Resource Adaptor docs adding dependencies needed
Modified: trunk/docs/user-manual/en/appserver-integration.xml
===================================================================
--- trunk/docs/user-manual/en/appserver-integration.xml 2010-06-17 17:08:48 UTC (rev 9345)
+++ trunk/docs/user-manual/en/appserver-integration.xml 2010-06-18 15:07:16 UTC (rev 9346)
@@ -28,6 +28,10 @@
outflow of messages sent from other JEE components, e.g. EJBs and Servlets.</para>
<para>This section explains the basics behind configuring the different JEE components in the
AS.</para>
+ <section>
+ <title>Dependencies for Application Server Integration</title>
+ <para></para>
+ </section>
<section>
<title>Configuring Message-Driven Beans</title>
<para>The delivery of messages to an MDB using HornetQ is configured on the JCA Adapter via
@@ -828,46 +832,143 @@
</section>
<section>
<title>Configuring the adapter to use a standalone HornetQ Server</title>
- <para>Sometime you may want your messaging server on a different machine or separate from the application server.</para>
- <para>To do this you will need to configure both the incoming and outgoing adapter.</para>
- <para>To configure MDB's to consume messages from a remote HornetQ server you need to configure the ra.xml file
- which can be found under <literal>deploy/hornet-ra.rar/META-INF</literal>. Simply configure the transport to
- use a netty connector (instead of the invm connector) and configure its transport params. Heres an example of
- what this would look like:</para>
- <programlisting>
- <resourceadapter-class>org.hornetq.ra.HornetQResourceAdapter</resourceadapter-class>
- <config-property>
- <description>The transport type</description>
- <config-property-name>ConnectorClassName</config-property-name>
- <config-property-type>java.lang.String</config-property-type>
- <config-property-value>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</config-property-value>
- </config-property>
- <config-property>
- <description>The transport configuration. These values must be in the form of key=val;key=val;</description>
- <config-property-name>ConnectionParameters</config-property-name>
- <config-property-type>java.lang.String</config-property-type>
- <config-property-value>host=127.0.0.1;port=5446</config-property-value>
- </config-property>
- </programlisting>
- <para>This configures the resource adapter to connect to a server running on localhost listening on port 5446</para>
- <para>You will also need to configure any outbound connections to also connect to this server. This can be done
- by either configuring the jms-ds.xml file found under <literal>deploy/hornetq.sar</literal> or creating a
- new configuration file and making sure the filename ends in -ds.xml</para>
- <para>The following example shows a sample configuration</para>
- <programlisting>
- <tx-connection-factory>
- <jndi-name>RemoteJmsXA</jndi-name>
- <xa-transaction/>
- <rar-name>hornetq-ra.rar</rar-name>
- <connection-definition>org.hornetq.ra.HornetQRAConnectionFactory</connection-definition>
- <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
- <config-property name="ConnectorClassName" type="java.lang.String">org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</config-property>
- <config-property name="ConnectionParameters" type="java.lang.String">host=127.0.0.1;port=5446</config-property>
- <max-pool-size>20</max-pool-size>
- </tx-connection-factory>
- </programlisting>
- <para>Again this will connect to the HornetQ server running on localhost and listening on port 5446. JEE components
- can access this by using JNDI and looking up <literal>java:/RemoteJmsXA</literal></para>
+ <para>Sometime you may want your messaging server on a different machine or separate from the application server.
+ If this is the case you will only need the hornetq client libs installed. This section explains what config to create
+ and what jar dependencies are needed.</para>
+ <section>
+ <para>There are two configuration files needed to do this, one for the incoming adapter used for MDB's
+ and one for outgoing connections managed by the JCA managed connection pool used by outgoing JEE components
+ wanting outgoing connections.</para>
+ <section>
+ <title>Configuring the Incoming Adaptor</title>
+ <para>Firstly you will need to create directory under the
+ <literal>deploy</literal>
+ directory ending in
+ <literal>.rar.
+ For this example we will name the directory <literal>hornetq-ra.rar</literal>. This detail is
+ important as
+ the name of directory is referred to by the MDB's and the outgoing configuration.
+ </literal>
+ </para>
+ <note>
+ <para>The jboss default for this is <literal>jms-ra.rar</literal>, If you don't want to have to
+ configure your
+ MDB's you can use this but you may need to remove the generic adaptor that uses this.
+ </para>
+ </note>
+ <para>Under the
+ <literal>hornetq-ra.rar</literal>
+ directory you will need to create a
+ <literal>META-INF</literal>
+ directory into which you should create an
+ <literal>ra.xml</literal>
+ configuration file. You can find a template
+ for the
+ <literal>ra.xml</literal>
+ under the config directory of the HornetQ distribution.
+ </para>
+ <para>To configure MDB's to consume messages from a remote HornetQ server you need to edit the
+ <literal>ra.xml</literal>
+ file under
+ <literal>deploy/hornet-ra.rar/META-INF</literal>
+ and change the transport type to
+ use a netty connector (instead of the invm connector that is defined) and configure its transport
+ params.
+ Heres an example of what this would look like:
+ </para>
+ <programlisting>
+ <resourceadapter-class>org.hornetq.ra.HornetQResourceAdapter</resourceadapter-class>
+ <config-property>
+ <description>The transport type</description>
+ <config-property-name>ConnectorClassName</config-property-name>
+ <config-property-type>java.lang.String</config-property-type>
+ <config-property-value>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</config-property-value>
+ </config-property>
+ <config-property>
+ <description>The transport configuration. These values must be in the form of key=val;key=val;</description>
+ <config-property-name>ConnectionParameters</config-property-name>
+ <config-property-type>java.lang.String</config-property-type>
+ <config-property-value>host=127.0.0.1;port=5446</config-property-value>
+ </config-property>
+ </programlisting>
+ <para>This configures the resource adapter to connect to a server running on localhost listening on port
+ 5446
+ </para>
+ </section>
+
+ <section>
+ <title>Configuring the outgoing adaptor</title>
+ <para>You will also need to configure the outbound connection by creating a <literal>hornetq-ds.xml</literal>
+ and placing it under any directory that will be deployed under the <literal>deploy</literal> directory.
+ In a standard HornetQ jboss configuration this would be under <literal>horneq</literal> or <literal>hornetq.sar</literal>
+ but you can place it where ever you like. Actually as long as it ends in <literal>-ds.xml</literal> you can
+ call it anything you like. You can again find a template for this file under the config directory of the
+ HornetQ distribution but called <literal>jms-ds.xml</literal> which is the jboss default.
+ </para>
+ <para>The following example shows a sample configuration</para>
+ <programlisting>
+ <tx-connection-factory>
+ <jndi-name>RemoteJmsXA</jndi-name>
+ <xa-transaction/>
+ <rar-name>hornetq-ra.rar</rar-name>
+ <connection-definition>org.hornetq.ra.HornetQRAConnectionFactory</connection-definition>
+ <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
+ <config-property name="ConnectorClassName" type="java.lang.String">org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</config-property>
+ <config-property name="ConnectionParameters" type="java.lang.String">host=127.0.0.1;port=5446</config-property>
+ <max-pool-size>20</max-pool-size>
+ </tx-connection-factory>
+ </programlisting>
+ <para>Again you will see that this uses the netty connector type and will connect to the HornetQ server
+ running on localhost and listening on port 5446. JEE components can access this by using JNDI and looking
+ up the connection factory using JNDI using <literal>java:/RemoteJmsXA</literal>, you can see that this
+ is defined under the<literal>jndi-name</literal> attribute. You will also note that the outgoing connection
+ will be created by the resource adaptor configured under the directory <literal>hornetq-ra.rar</literal> as explained in the last section.
+ </para>
+ </section>
+
+ <section>
+ <title>Jar dependencies</title>
+ <para>This is a list of the HornetQ and third party jars needed</para>
+ <table frame="topbot" border="2">
+ <title>Jar Dependencies</title>
+ <tgroup cols="3">
+ <colspec colname="c1" colnum="1"/>
+ <colspec colname="c2" colnum="2"/>
+ <colspec colname="c3" colnum="3"/>
+ <thead>
+ <row>
+ <entry>Jar Name</entry>
+ <entry>Description</entry>
+ <entry>Location</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>hornetq-ra.jar</entry>
+ <entry>The HornetQ resource adaptor classes</entry>
+ <entry>deploy/hornetq-ra.rar or equivelant</entry>
+ </row>
+ <row>
+ <entry>hornetq-core-client.jar</entry>
+ <entry>The HornetQ core client classes</entry>
+ <entry>either in the config lib, i.e. default/lib or the common lib dir, i.e. $JBOSS_HOME/common lib </entry>
+ </row>
+ <row>
+ <entry>hornetq-jms-client.jar</entry>
+ <entry>The HornetQ JMS classes</entry>
+ <entry>as above</entry>
+ </row>
+ <row>
+ <entry>netty.jar</entry>
+ <entry>The Netty transport classes</entry>
+ <entry>as above</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+
+ </section>
</section>
</section>
<section>
13 years, 10 months
JBoss hornetq SVN: r9345 - trunk/tests/config.
by do-not-reply＠jboss.org
Author: clebert.suconic(a)jboss.com
Date: 2010-06-17 13:08:48 -0400 (Thu, 17 Jun 2010)
New Revision: 9345
Modified:
trunk/tests/config/hornetq-jms-for-JMSServerDeployerTest.xml
trunk/tests/config/hornetq-jms-for-JMSServerDeployerTest2.xml
Log:
https://jira.jboss.org/browse/HORNETQ-400 - fixing tests accordingly to Andy's change
Modified: trunk/tests/config/hornetq-jms-for-JMSServerDeployerTest.xml
===================================================================
--- trunk/tests/config/hornetq-jms-for-JMSServerDeployerTest.xml 2010-06-17 09:21:31 UTC (rev 9344)
+++ trunk/tests/config/hornetq-jms-for-JMSServerDeployerTest.xml 2010-06-17 17:08:48 UTC (rev 9345)
@@ -26,7 +26,7 @@
<block-on-acknowledge>true</block-on-acknowledge>
<block-on-non-durable-send>false</block-on-non-durable-send>
<block-on-durable-send>true</block-on-durable-send>
- <auto-group-id>false</auto-group-id>
+ <auto-group>false</auto-group>
<pre-acknowledge>true</pre-acknowledge>
<connection-ttl>2345</connection-ttl>
<discovery-initial-wait-timeout>678</discovery-initial-wait-timeout>
Modified: trunk/tests/config/hornetq-jms-for-JMSServerDeployerTest2.xml
===================================================================
--- trunk/tests/config/hornetq-jms-for-JMSServerDeployerTest2.xml 2010-06-17 09:21:31 UTC (rev 9344)
+++ trunk/tests/config/hornetq-jms-for-JMSServerDeployerTest2.xml 2010-06-17 17:08:48 UTC (rev 9345)
@@ -27,7 +27,7 @@
<block-on-acknowledge>true</block-on-acknowledge>
<block-on-non-durable-send>false</block-on-non-durable-send>
<block-on-durable-send>true</block-on-durable-send>
- <auto-group-id>false</auto-group-id>
+ <auto-group>false</auto-group>
<pre-acknowledge>true</pre-acknowledge>
<connection-ttl>2345</connection-ttl>
<discovery-initial-wait-timeout>5464</discovery-initial-wait-timeout>
13 years, 10 months
JBoss hornetq SVN: r9344 - trunk/src/config/common/schema.
by do-not-reply＠jboss.org
Author: ataylor
Date: 2010-06-17 05:21:31 -0400 (Thu, 17 Jun 2010)
New Revision: 9344
Modified:
trunk/src/config/common/schema/hornetq-jms.xsd
Log:
HORNETQ-400 - In Message Grouping, I cannot set autogroup by hornetq-jms.xml
Modified: trunk/src/config/common/schema/hornetq-jms.xsd
===================================================================
--- trunk/src/config/common/schema/hornetq-jms.xsd 2010-06-17 08:14:13 UTC (rev 9343)
+++ trunk/src/config/common/schema/hornetq-jms.xsd 2010-06-17 09:21:31 UTC (rev 9344)
@@ -94,7 +94,7 @@
<xsd:element name="block-on-durable-send" type="xsd:boolean"
maxOccurs="1" minOccurs="0">
</xsd:element>
- <xsd:element name="auto-group-id" type="xsd:boolean"
+ <xsd:element name="auto-group" type="xsd:boolean"
maxOccurs="1" minOccurs="0">
</xsd:element>
<xsd:element name="pre-acknowledge" type="xsd:boolean"
13 years, 10 months
JBoss hornetq SVN: r9343 - in trunk: tests/src/org/hornetq/tests/integration/management and 1 other directory.
by do-not-reply＠jboss.org
Author: jmesnil
Date: 2010-06-17 04:14:13 -0400 (Thu, 17 Jun 2010)
New Revision: 9343
Modified:
trunk/src/main/org/hornetq/core/server/management/impl/ManagementServiceImpl.java
trunk/tests/src/org/hornetq/tests/integration/management/ManagementServiceImplTest.java
Log:
https://jira.jboss.org/browse/HORNETQ-420: HDR_OPERATION_SUCCEEDED not set to true when retrieving an attribute value
* set the header on the reply message after successfully retrieving the attribute value
Modified: trunk/src/main/org/hornetq/core/server/management/impl/ManagementServiceImpl.java
===================================================================
--- trunk/src/main/org/hornetq/core/server/management/impl/ManagementServiceImpl.java 2010-06-16 14:03:30 UTC (rev 9342)
+++ trunk/src/main/org/hornetq/core/server/management/impl/ManagementServiceImpl.java 2010-06-17 08:14:13 UTC (rev 9343)
@@ -462,6 +462,8 @@
Object result = getAttribute(resourceName, attribute);
ManagementHelper.storeResult(reply, result);
+
+ reply.putBooleanProperty(ManagementHelper.HDR_OPERATION_SUCCEEDED, true);
}
catch (Exception e)
{
Modified: trunk/tests/src/org/hornetq/tests/integration/management/ManagementServiceImplTest.java
===================================================================
--- trunk/tests/src/org/hornetq/tests/integration/management/ManagementServiceImplTest.java 2010-06-16 14:03:30 UTC (rev 9342)
+++ trunk/tests/src/org/hornetq/tests/integration/management/ManagementServiceImplTest.java 2010-06-17 08:14:13 UTC (rev 9343)
@@ -114,7 +114,7 @@
server.stop();
}
- public void testHandleManagementMessageWithUnknowAttribute() throws Exception
+ public void testHandleManagementMessageWithUnknownAttribute() throws Exception
{
Configuration conf = new ConfigurationImpl();
conf.setJMXManagementEnabled(false);
@@ -125,6 +125,26 @@
// invoke attribute and operation on the server
ServerMessage message = new ServerMessageImpl(1, 100);
+ ManagementHelper.putAttribute(message, ResourceNames.CORE_SERVER, "started");
+
+ ServerMessage reply = server.getManagementService().handleMessage(message);
+
+ Assert.assertTrue(ManagementHelper.hasOperationSucceeded(reply));
+ Assert.assertTrue((Boolean)ManagementHelper.getResult(reply));
+ server.stop();
+ }
+
+ public void testHandleManagementMessageWithKnownAttribute() throws Exception
+ {
+ Configuration conf = new ConfigurationImpl();
+ conf.setJMXManagementEnabled(false);
+
+ HornetQServer server = HornetQServers.newHornetQServer(conf, false);
+ server.start();
+
+ // invoke attribute and operation on the server
+ ServerMessage message = new ServerMessageImpl(1, 100);
+
ManagementHelper.putAttribute(message, ResourceNames.CORE_SERVER, "attribute.Does.Not.Exist");
ServerMessage reply = server.getManagementService().handleMessage(message);
13 years, 10 months
JBoss hornetq SVN: r9342 - trunk.
by do-not-reply＠jboss.org
Author: clebert.suconic(a)jboss.com
Date: 2010-06-16 10:03:30 -0400 (Wed, 16 Jun 2010)
New Revision: 9342
Modified:
trunk/pom.xml
Log:
Tweak only, this is not used on the releaes
Modified: trunk/pom.xml
===================================================================
--- trunk/pom.xml 2010-06-16 07:56:21 UTC (rev 9341)
+++ trunk/pom.xml 2010-06-16 14:03:30 UTC (rev 9342)
@@ -19,7 +19,7 @@
<groupId>org.hornetq</groupId>
<artifactId>messaging</artifactId>
<packaging>pom</packaging>
- <version>2.1.0.Final</version>
+ <version>2.1.1.Final</version>
<name>HornetQ</name>
<url>http://hornetq.org</url>
13 years, 10 months
JBoss hornetq SVN: r9341 - projects/jopr-plugin/tags.
by do-not-reply＠jboss.org
Author: ataylor
Date: 2010-06-16 03:56:21 -0400 (Wed, 16 Jun 2010)
New Revision: 9341
Added:
projects/jopr-plugin/tags/HornetQ-jopr-plugin_1_0_0_CR2/
Log:
HornetQ jopr plugin 1.0.0.CR2 tag
Copied: projects/jopr-plugin/tags/HornetQ-jopr-plugin_1_0_0_CR2 (from rev 9340, projects/jopr-plugin/trunk)
13 years, 10 months
JBoss hornetq SVN: r9339 - projects/jopr-plugin/trunk.
by do-not-reply＠jboss.org
Author: ataylor
Date: 2010-06-16 03:55:29 -0400 (Wed, 16 Jun 2010)
New Revision: 9339
Modified:
projects/jopr-plugin/trunk/pom.xml
Log:
updated version
Modified: projects/jopr-plugin/trunk/pom.xml
===================================================================
--- projects/jopr-plugin/trunk/pom.xml 2010-06-16 07:54:34 UTC (rev 9338)
+++ projects/jopr-plugin/trunk/pom.xml 2010-06-16 07:55:29 UTC (rev 9339)
@@ -5,7 +5,7 @@
<groupId>org.hornetq</groupId>
<artifactId>hornetq-jopr-plugin</artifactId>
<packaging>jar</packaging>
- <version>1.0.0.CR1</version>
+ <version>1.0.0.CR2</version>
<name>JBoss Application Server JOPR plugin</name>
<url>http://hornetq.org</url>
<description>HornetQ JOPR plugin</description>
13 years, 10 months
JBoss hornetq SVN: r9338 - projects/jopr-plugin/tags.
by do-not-reply＠jboss.org
Author: ataylor
Date: 2010-06-16 03:54:34 -0400 (Wed, 16 Jun 2010)
New Revision: 9338
Added:
projects/jopr-plugin/tags/HornetQ-jopr-plugin_1_0_0_CR2/
Log:
HornetQ jopr plugin 1.0.0.CR2 tag
Copied: projects/jopr-plugin/tags/HornetQ-jopr-plugin_1_0_0_CR2 (from rev 9337, projects/jopr-plugin/trunk)
13 years, 10 months
JBoss hornetq SVN: r9337 - tags.
by do-not-reply＠jboss.org
Author: clebert.suconic(a)jboss.com
Date: 2010-06-15 22:43:25 -0400 (Tue, 15 Jun 2010)
New Revision: 9337
Added:
tags/Hornetq_2_1_1_Final/
Log:
2.1.1 release
Copied: tags/Hornetq_2_1_1_Final (from rev 9336, trunk)
13 years, 10 months