Return-Path: X-Original-To: apmail-activemq-commits-archive@www.apache.org Delivered-To: apmail-activemq-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4E51917553 for ; Mon, 10 Nov 2014 16:32:17 +0000 (UTC) Received: (qmail 50395 invoked by uid 500); 10 Nov 2014 16:32:15 -0000 Delivered-To: apmail-activemq-commits-archive@activemq.apache.org Received: (qmail 50301 invoked by uid 500); 10 Nov 2014 16:32:15 -0000 Mailing-List: contact commits-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list commits@activemq.apache.org Received: (qmail 48331 invoked by uid 99); 10 Nov 2014 16:32:13 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Nov 2014 16:32:13 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id BD00D8C15AE; Mon, 10 Nov 2014 16:32:13 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: jbertram@apache.org To: commits@activemq.apache.org Date: Mon, 10 Nov 2014 16:32:57 -0000 Message-Id: <6dbea88bb77744ac9d44e1acdbe97d9b@git.apache.org> In-Reply-To: <8b738e60a5d74a9c9614de4f578bb10f@git.apache.org> References: <8b738e60a5d74a9c9614de4f578bb10f@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [46/51] [partial] activemq-6 git commit: ACTIVEMQ6-1 - Initial HornetQ Donation Commit http://git-wip-us.apache.org/repos/asf/activemq-6/blob/8ecd255f/docs/quickstart-guide/en/examples.xml ---------------------------------------------------------------------- diff --git a/docs/quickstart-guide/en/examples.xml b/docs/quickstart-guide/en/examples.xml new file mode 100644 index 0000000..8dcccea --- /dev/null +++ b/docs/quickstart-guide/en/examples.xml @@ -0,0 +1,330 @@ + + + + + + + + + + + + + + + + + + + + +%BOOK_ENTITIES; +]> + + Running the Examples + In the directory examples there are 2 sets of examples, these are + + + JMS Examples - these demonstrate functionality while sending and consumng JMS + messages. + + + Java EE Examples - these demonstrate application server integration, e.g. MDBs, EJBs, + Servlets, etc. + + +
+ The JMS examples + The JMS Examples all follow the same format. Each examples is contained in its own + directory which contains the following. + + + pom.xml + This is the Maven build file used to run the example + + + src directory + This contains the source code for the example + + + resources/hornetq/server0 configuration directory + This contains the configuration files needed to run the server for the example. + There may be multiple configuration directories server0, server1 etc for clustered examples etc. + + + Each example will start one or more stand-alone servers and stop them after the example + has completed. + As a quick start we'll run the queue example. For all other examples refer to the main + user manual. + Firstly open a Shell or a Command prompt and navigate to the examples/jms/queue directory. + Type the command mvn verify and you should see the following output: + + +[INFO] Scanning for projects... +[INFO] +[INFO] ------------------------------------------------------------------------ +[INFO] Building HornetQ JMS Queue Example 2.3.0.BETA-SNAPSHOT +[INFO] ------------------------------------------------------------------------ +[INFO] +[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ hornetq-jms-queue-example --- +[INFO] Using 'UTF-8' encoding to copy filtered resources. +[INFO] Copying 3 resources +[INFO] +[INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ hornetq-jms-queue-example --- +[INFO] Nothing to compile - all classes are up to date +[INFO] +[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ hornetq-jms-queue-example --- +[INFO] Using 'UTF-8' encoding to copy filtered resources. +[INFO] skip non existing resourceDirectory /home/andy/projects/hornetq-master/examples/jms/queue/src/test/resources +[INFO] +[INFO] --- maven-compiler-plugin:3.0:testCompile (default-testCompile) @ hornetq-jms-queue-example --- +[INFO] No sources to compile +[INFO] +[INFO] --- maven-surefire-plugin:2.13:test (default-test) @ hornetq-jms-queue-example --- +[INFO] +[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ hornetq-jms-queue-example --- +[INFO] Building jar: /home/andy/projects/hornetq-master/examples/jms/queue/target/hornetq-jms-queue-example-2.3.0.BETA-SNAPSHOT.jar +[INFO] +[INFO] >>> maven-source-plugin:2.2.1:jar (attach-sources) @ hornetq-jms-queue-example >>> +[INFO] +[INFO] <<< maven-source-plugin:2.2.1:jar (attach-sources) @ hornetq-jms-queue-example <<< +[INFO] +[INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @ hornetq-jms-queue-example --- +[INFO] Building jar: /home/andy/projects/hornetq-master/examples/jms/queue/target/hornetq-jms-queue-example-2.3.0.BETA-SNAPSHOT-sources.jar +[INFO] +[INFO] >>> maven-source-plugin:2.2.1:jar (default) @ hornetq-jms-queue-example >>> +[INFO] +[INFO] <<< maven-source-plugin:2.2.1:jar (default) @ hornetq-jms-queue-example <<< +[INFO] +[INFO] --- maven-source-plugin:2.2.1:jar (default) @ hornetq-jms-queue-example --- +[WARNING] Artifact org.hornetq.examples.jms:hornetq-jms-queue-example:java-source:sources:2.3.0.BETA-SNAPSHOT already attached to project, ignoring duplicate +[INFO] +[INFO] --- hornetq-maven-plugin:1.1.1-SNAPSHOT:start (start) @ hornetq-jms-queue-example --- +[file:/home/andy/projects/hornetq-master/examples/jms/queue/target/classes/hornetq/server0/] +Apr 17, 2013 10:51:01 AM org.hornetq.core.deployers.impl.FileConfigurationParser parseMainConfig +WARN: HQ222018: AIO was not located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal +Apr 17, 2013 10:51:01 AM org.hornetq.core.server.impl.HornetQServerImpl start +INFO: HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/andy/projects/hornetq-master/examples/jms/queue/target//server0/data/messaging/journal,bindingsDirectory=/home/andy/projects/hornetq-master/examples/jms/queue/target//server0/data/messaging/bindings,largeMessagesDirectory=/home/andy/projects/hornetq-master/examples/jms/queue/target//server0/data/messaging/largemessages,pagingDirectory=/home/andy/projects/hornetq-master/examples/jms/queue/target//server0/data/messaging/paging) +Apr 17, 2013 10:51:01 AM org.hornetq.core.server.impl.HornetQServerImpl$SharedStoreLiveActivation run +INFO: HQ221006: Waiting to obtain live lock +Apr 17, 2013 10:51:01 AM org.hornetq.core.persistence.impl.journal.JournalStorageManager <init> +INFO: HQ221013: Using NIO Journal +Apr 17, 2013 10:51:01 AM org.hornetq.core.server.impl.HornetQServerImpl initialisePart1 +WARN: HQ222007: Security risk! HornetQ is running with the default cluster admin user and default password. Please see the HornetQ user guide, cluster chapter, for instructions on how to change this. +Apr 17, 2013 10:51:01 AM org.hornetq.core.server.impl.FileLockNodeManager startLiveNode +INFO: HQ221034: Waiting to obtain live lock +Apr 17, 2013 10:51:01 AM org.hornetq.core.server.impl.FileLockNodeManager startLiveNode +INFO: HQ221035: Live Server Obtained live lock +Apr 17, 2013 10:51:02 AM org.hornetq.core.server.impl.HornetQServerImpl deployQueue +INFO: HQ221003: trying to deploy queue jms.queue.exampleQueue +Apr 17, 2013 10:51:02 AM org.hornetq.core.remoting.impl.netty.NettyAcceptor start +INFO: HQ221020: Started Netty Acceptor version 3.6.2.Final-c0d783c localhost:5445 for CORE protocol +Apr 17, 2013 10:51:02 AM org.hornetq.core.server.impl.HornetQServerImpl$SharedStoreLiveActivation run +INFO: HQ221007: Server is now live +Apr 17, 2013 10:51:02 AM org.hornetq.core.server.impl.HornetQServerImpl start +INFO: HQ221001: HornetQ Server version 2.3.0.SNAPSHOT (black'n'yellow, 123) [a57893ff-7783-11e2-9787-07ca142fc9f7] +[INFO] +[INFO] --- hornetq-maven-plugin:1.1.1-SNAPSHOT:runClient (runClient) @ hornetq-jms-queue-example --- +Apr 17, 2013 10:51:02 AM org.hornetq.common.example.HornetQExample getContext +INFO: using jnp://localhost:1099 for jndi +Sent message: This is a text message +Received message: This is a text message +example complete + +##################### +### SUCCESS! ### +##################### +[INFO] +[INFO] --- hornetq-maven-plugin:1.1.1-SNAPSHOT:stop (stop) @ hornetq-jms-queue-example --- +Apr 17, 2013 10:51:03 AM org.hornetq.core.server.management.impl.ManagementServiceImpl stop +WARN: HQ222113: On ManagementService stop, there are 1 unexpected registered MBeans: [core.acceptor.netty-acceptor] +Apr 17, 2013 10:51:03 AM org.hornetq.core.server.impl.HornetQServerImpl stop +INFO: HQ221002: HornetQ Server version 2.3.0.SNAPSHOT (black'n'yellow, 123) [a57893ff-7783-11e2-9787-07ca142fc9f7] stopped +[INFO] ------------------------------------------------------------------------ +[INFO] BUILD SUCCESS +[INFO] ------------------------------------------------------------------------ +[INFO] Total time: 4.428s +[INFO] Finished at: Wed Apr 17 10:51:03 BST 2013 +[INFO] Final Memory: 11M/456M +[INFO] ------------------------------------------------------------------------ + + + Congratulations! You have successfully run your first HornetQ example. Try some of the + others. +
+
+ The Java EE Examples + The Java EE Examples are examples that require a JEE application server to run. They + include MDB, Servlet, EJB examples etc. For this you will need the JBoss Application Server 7.1.x + installed and uses Arquillian to run the example. How to do this is explained in the previous chapters. + We'll use the MDB example for the purposes of this guide. For the other examples refer + to the user guide. Before going any further ensure that the JBoss Application Server is + running. + The first thing we need to do is set the JBOSS_HOME environment property to the location of the JBoss + Application Server, in a Linux shell this would be something like: + export JBOSS_HOME=/home/jbossas7.1/build/output/jboss-7.1.0 + Yoy can then run the example via maven by running mvn test + In the shell window you should see something like the following output: + +[INFO] Scanning for projects... +[INFO] +[INFO] ------------------------------------------------------------------------ +[INFO] Building HornetQ JEE MDB Example 2.3.0.BETA-SNAPSHOT +[INFO] ------------------------------------------------------------------------ +[INFO] +[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ hornetq-jee-mdb-bmt-example --- +[INFO] Using 'UTF-8' encoding to copy filtered resources. +[INFO] skip non existing resourceDirectory /home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/src/main/resources +[INFO] +[INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ hornetq-jee-mdb-bmt-example --- +[INFO] Nothing to compile - all classes are up to date +[INFO] +[INFO] --- maven-resources-plugin:2.6:copy-resources (as-node-0) @ hornetq-jee-mdb-bmt-example --- +[INFO] Using 'UTF-8' encoding to copy filtered resources. +[INFO] Copying 1112 resources +[INFO] Copying 5 resources +[INFO] +[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ hornetq-jee-mdb-bmt-example --- +[INFO] Using 'UTF-8' encoding to copy filtered resources. +[INFO] Copying 1 resource +[INFO] +[INFO] --- maven-compiler-plugin:3.0:testCompile (default-testCompile) @ hornetq-jee-mdb-bmt-example --- +[INFO] Changes detected - recompiling the module! +[INFO] Compiling 1 source file to /home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/test-classes +[INFO] +[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ hornetq-jee-mdb-bmt-example --- +[INFO] Surefire report directory: /home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/surefire-reports + +------------------------------------------------------- + T E S T S +------------------------------------------------------- +Running org.hornetq.javaee.example.server.ExampleRunnerTest +log4j:WARN No appenders could be found for logger (org.jboss.logging). +log4j:WARN Please initialize the log4j system properly. +log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. +Apr 17, 2013 10:58:04 AM org.jboss.arquillian.container.impl.MapObject populate +WARNING: Configuration contain properties not supported by the backing object org.jboss.as.arquillian.container.managed.ManagedContainerConfiguration +Unused property entries: {waitForPortsTimeoutInSeconds=8, waitForPorts=8787 9999} +Supported property names: [jbossHome, outputToConsole, enableAssertions, password, managementPort, javaHome, javaVmArguments, username, serverConfig, allowConnectingToRunningServer, managementAddress, startupTimeoutInSeconds, modulePath] +Apr 17, 2013 10:58:04 AM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal +INFO: Starting container with: [/home/andy/devtools/jdk1.6.0_25//bin/java, -Djboss.inst=/home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0, -ea, -Djboss.home.dir=/home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0, -Dorg.jboss.boot.log.file=/home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0/standalone/log/boot.log, -Dlogging.configuration=file:/home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0/standalone/configuration/logging.properties, -Djboss.modules.dir=/home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0/modules, -Djboss.bundles.dir=/home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0/bundles, -jar, /home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0/jboss-modules.jar, -mp, /home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0/modules, -jaxpmodule, javax.xml. jaxp-provider, org.jboss.as.standalone, -server-config, standalone-example.xml] +10:58:04,525 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA +10:58:04,664 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA +10:58:04,703 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting +10:58:05,492 INFO [org.xnio] XNIO Version 3.0.3.GA +10:58:05,494 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http) +10:58:05,502 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA +10:58:05,509 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA +10:58:05,527 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers +10:58:05,530 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 32) JBAS016200: Activating ConfigAdmin Subsystem +10:58:05,560 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 37) JBAS010280: Activating Infinispan subsystem. +10:58:05,562 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) +10:58:05,573 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 38) JBAS016300: Activating JacORB Subsystem +10:58:05,595 INFO [org.jboss.as.connector] (MSC service thread 1-12) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final) +10:58:05,612 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 48) JBAS011800: Activating Naming Subsystem +10:58:05,625 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 49) JBAS011940: Activating OSGi Subsystem +10:58:05,649 INFO [org.jboss.as.security] (ServerService Thread Pool -- 54) JBAS013101: Activating Security Subsystem +10:58:05,657 INFO [org.jboss.as.naming] (MSC service thread 1-8) JBAS011802: Starting Naming Service +10:58:05,663 INFO [org.jboss.as.mail.extension] (MSC service thread 1-16) JBAS015400: Bound mail session [java:jboss/mail/Default] +10:58:05,675 INFO [org.jboss.as.security] (MSC service thread 1-14) JBAS013100: Current PicketBox version=4.0.7.Final +10:58:05,683 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 58) JBAS015537: Activating WebServices Extension +10:58:05,705 INFO [org.jboss.jaxr] (MSC service thread 1-8) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory +10:58:05,831 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-4) JBoss Web Services - Stack CXF Server 4.0.2.GA +10:58:05,943 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-6) Starting Coyote HTTP/1.1 on http-localhost.localdomain-127.0.0.1-8080 +10:58:05,966 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB Service started +10:58:05,988 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-11) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0/standalone/data/messagingjournal,bindingsDirectory=/home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0/standalone/data/messagingbindings,largeMessagesDirectory=/home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0/standalone/data/messaginglargemessages,pagingDirectory=/home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0/standalone/data/messagingpaging) +10:58:05,996 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-11) Waiting to obtain live lock +10:58:06,037 INFO [org.hornetq.core.persistence.impl.journal.JournalStorageManager] (MSC service thread 1-11) Using AIO Journal +10:58:06,122 INFO [org.jboss.as.jacorb] (MSC service thread 1-14) JBAS016328: CORBA Naming Service started +10:58:06,184 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] +10:58:06,204 INFO [org.hornetq.core.server.impl.AIOFileLockNodeManager] (MSC service thread 1-11) Waiting to obtain live lock +10:58:06,205 INFO [org.hornetq.core.server.impl.AIOFileLockNodeManager] (MSC service thread 1-11) Live Server Obtained live lock +10:58:06,434 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on localhost.localdomain/127.0.0.1:4447 +10:58:06,434 INFO [org.jboss.as.remoting] (MSC service thread 1-15) JBAS017100: Listening on /127.0.0.1:9999 +10:58:06,436 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-16) JBAS015012: Started FileSystemDeploymentService for directory /home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0/standalone/deployments +10:58:08,790 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-11) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost.localdomain:5445 for CORE protocol +10:58:08,793 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-11) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost.localdomain:5455 for CORE protocol +10:58:08,795 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-11) Server is now live +10:58:08,797 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-11) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [5c499e88-9c63-11e2-bfa3-fe5400591699]) started +10:58:08,822 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory +10:58:08,824 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory +10:58:08,825 INFO [org.jboss.as.messaging] (MSC service thread 1-10) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory +10:58:08,830 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) trying to deploy queue jms.queue.testQueue +10:58:08,836 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/queue/test +10:58:08,840 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queues/testQueue +10:58:08,859 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-9) JBAS010406: Registered connection factory java:/JmsXA +10:58:08,866 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-9) HornetQ resource adaptor started +10:58:08,867 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-9) IJ020002: Deployed: file://RaActivatorhornetq-ra +10:58:08,870 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-5) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] +10:58:08,898 INFO [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015876: Starting deployment of "ONT001-1.0.war" +10:58:09,146 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-1) Add Service + id=com.hpm.webservices.BasicWSImpl + address=http://localhost:8080/hpm/BasicWService + implementor=com.hpm.webservices.BasicWSImpl + invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker + serviceName={http://ont001-hpm.rhcloud.com/BasicWS}BasicWService + portName={http://ont001-hpm.rhcloud.com/BasicWS}BasicWS + wsdlLocation=null + mtomEnabled=false +10:58:09,361 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://ont001-hpm.rhcloud.com/BasicWS}BasicWService from WSDL: WEB-INF/wsdl/BasicWService.wsdl +10:58:09,517 INFO [org.jboss.wsf.stack.cxf.transport.AddressRewritingEndpointInfo] (MSC service thread 1-1) Setting new service endpoint address in wsdl: http://ONT001-HPM.rhcloud.com:80/BasicWService +10:58:09,656 INFO [org.jboss.wsf.stack.cxf.transport.AddressRewritingEndpointInfo] (MSC service thread 1-1) Setting new service endpoint address in wsdl: http://localhost:8080/hpm/BasicWService +10:58:09,688 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/hpm/BasicWService +10:58:09,729 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-1) WSDL published to: file:/home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0/standalone/data/wsdl/ONT001-1.0.war/BasicWService.wsdl +10:58:09,735 INFO [org.jboss.as.webservices] (MSC service thread 1-11) JBAS015539: Starting service jboss.ws.port-component-link +10:58:09,748 INFO [org.jboss.as.webservices] (MSC service thread 1-10) JBAS015539: Starting service jboss.ws.endpoint."ONT001-1.0.war"."com.hpm.webservices.BasicWSImpl" +10:58:09,753 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-10) register: jboss.ws:context=hpm,endpoint=com.hpm.webservices.BasicWSImpl +10:58:09,829 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /hpm +10:58:09,834 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015951: Admin console listening on http://127.0.0.1:9990 +10:58:09,835 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 5506ms - Started 216 of 296 services (79 services are passive or on-demand) +10:58:09,979 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "ONT001-1.0.war" +mdb.jar: +/org/ +/org/hornetq/ +/org/hornetq/javaee/ +/org/hornetq/javaee/example/ +/org/hornetq/javaee/example/server/ +/org/hornetq/javaee/example/server/MDB_BMTExample.class +10:58:11,612 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0/standalone/data/content/f0/e2d589ab9490193e109c8bc833f725c87defae/content +10:58:11,620 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "arquillian-service" +10:58:11,811 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.arquillian-service" is using a private module ("org.jboss.as.jmx:main") which may be changed or removed in future versions without notice. +10:58:11,812 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.arquillian-service" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice. +10:58:11,813 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.arquillian-service" is using a private module ("org.jboss.as.osgi:main") which may be changed or removed in future versions without notice. +10:58:11,815 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.arquillian-service" is using a private module ("org.jboss.jandex:main") which may be changed or removed in future versions without notice. +10:58:11,817 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.arquillian-service" is using a private module ("org.jboss.osgi.framework:main") which may be changed or removed in future versions without notice. +10:58:11,953 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "arquillian-service" +10:58:12,328 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014900: Content added at location /home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0/standalone/data/content/59/7dcdb0f420ed57aea638b2599f7a86eecf6c85/content +10:58:12,333 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "mdb.jar" +10:58:12,401 INFO [org.jboss.as.arquillian] (MSC service thread 1-14) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."mdb.jar",unit=mdb.jar,tests=[org.hornetq.javaee.example.server.ExampleRunnerTest]] +10:58:12,418 INFO [org.jboss.as.ejb3] (MSC service thread 1-15) JBAS014142: Started message driven bean 'MDB_BMTExample' with 'hornetq-ra' resource adapter +10:58:12,562 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018559: Deployed "mdb.jar" +Sent message: This is a text message +10:58:13,229 INFO [org.jboss.as.naming] (Remoting "localhost" task-3) JBAS011806: Channel end notification received, closing channel Channel ID 57be4578 (inbound) of Remoting connection 3ac552d5 to /127.0.0.1:58571 +10:58:13,255 INFO [stdout] (Thread-0 (HornetQ-client-global-threads-1402019528)) message This is a text message received +10:58:13,257 INFO [stdout] (Thread-0 (HornetQ-client-global-threads-1402019528)) we're in the middle of a transaction: org.jboss.tm.usertx.client.ServerVMClientUserTransaction@6b04d3c8 +10:58:14,292 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment mdb.jar in 33ms +10:58:14,413 INFO [org.jboss.as.repository] (management-handler-thread - 1) JBAS014901: Content removed from location /home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0/standalone/data/content/59/7dcdb0f420ed57aea638b2599f7a86eecf6c85/content +10:58:14,415 INFO [org.jboss.as.server] (management-handler-thread - 1) JBAS018558: Undeployed "mdb.jar" +Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.609 sec +10:58:14,436 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment arquillian-service in 6ms +10:58:14,530 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014901: Content removed from location /home/andy/projects/hornetq-master/examples/javaee/mdb-bmt/target/jbossas-node0/standalone/data/content/f0/e2d589ab9490193e109c8bc833f725c87defae/content +10:58:14,532 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018558: Undeployed "arquillian-service" + +Results : + +Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 + +[INFO] ------------------------------------------------------------------------ +[INFO] BUILD SUCCESS +[INFO] ------------------------------------------------------------------------ +[INFO] Total time: 23.441s +[INFO] Finished at: Wed Apr 17 10:58:16 BST 2013 +[INFO] Final Memory: 19M/361M +[INFO] ------------------------------------------------------------------------ + +Congratulations! you have successfully deployed and run a Java EE example. +
+
http://git-wip-us.apache.org/repos/asf/activemq-6/blob/8ecd255f/docs/quickstart-guide/en/images/hornetQ_logo_600px.png ---------------------------------------------------------------------- diff --git a/docs/quickstart-guide/en/images/hornetQ_logo_600px.png b/docs/quickstart-guide/en/images/hornetQ_logo_600px.png new file mode 100644 index 0000000..b71f4ba Binary files /dev/null and b/docs/quickstart-guide/en/images/hornetQ_logo_600px.png differ http://git-wip-us.apache.org/repos/asf/activemq-6/blob/8ecd255f/docs/quickstart-guide/en/installation.xml ---------------------------------------------------------------------- diff --git a/docs/quickstart-guide/en/installation.xml b/docs/quickstart-guide/en/installation.xml new file mode 100644 index 0000000..80d4844 --- /dev/null +++ b/docs/quickstart-guide/en/installation.xml @@ -0,0 +1,102 @@ + + + + + + + + + + + + + + + + + + + + +%BOOK_ENTITIES; +]> + + Installation + This section describes how to install HornetQ. +
+ Prerequisites + + HornetQ only runs on Java 7 or later. + + By default, HornetQ server runs with 1GiB of memory. If your computer has less memory, + or you want to run it with more available RAM, modify the value in bin/run.sh accordingly. + For persistence, HornetQ uses its own fast journal, which you can configure to use + libaio (which is the default when running on Linux) or Java NIO. In order to use the libaio + module on Linux, you'll need to install libaio, if it's not already installed. + If you're not running on Linux then you don't need to worry about this. + You can install libaio using the following steps as the root user: + Using yum, (e.g. on Fedora or Red Hat Enterprise Linux): + yum install libaio + Using aptitude, (e.g. on Ubuntu or Debian system): + apt-get install libaio +
+
+ Stand-alone HornetQ Server + After downloading the distribution, unzip it into your chosen directory. At this point + it should be possible to run straight out of the + box, the following describes the directory structure: + + |___ bin + | + |___ config + | |___ jboss-as-4 + | |___ jboss-as-5 + | |___ stand-alone + | + |___ docs + | |___ api + | |___ quickstart-guide + | |___ user-manual + | + |___ examples + | |___ core + | |___ javaee + | |___ jms + | + |___ lib + | + |___ licenses + | + |___ schemas + + + + bin -- binaries and scripts needed to run HornetQ. + + + config -- configuration files needed to configure HornetQ. This + contains configurations to run HornetQ either in stand-alone or inside JBoss AS 4 and 5. + Please refer to the reference guide for details on configuration. + + + docs -- guides and javadocs for HornetQ + + + examples -- JMS and Java EE examples. Please refer to the + 'running examples' chapter for details on how to run them. + + + lib -- jars and libraries needed to run HornetQ + + + licenses -- licenses for HornetQ + + + schemas -- XML Schemas used to validate HornetQ configuration + files + + +
+
http://git-wip-us.apache.org/repos/asf/activemq-6/blob/8ecd255f/docs/quickstart-guide/en/introduction.xml ---------------------------------------------------------------------- diff --git a/docs/quickstart-guide/en/introduction.xml b/docs/quickstart-guide/en/introduction.xml new file mode 100644 index 0000000..faded49 --- /dev/null +++ b/docs/quickstart-guide/en/introduction.xml @@ -0,0 +1,33 @@ + + + + + + + + + + + + + + + + + + + + +%BOOK_ENTITIES; +]> + + Getting Started + This short guide explains how to download, install and quickly get started with + HornetQ. + After downloading and installing we highly recommend you run the examples to get + acquainted with HornetQ. We ship with over 70 examples demonstrating most of the + features. + This guide is not intended to be a replacement for the user manual. The user manual goes + into much more depth, so please consult that for further information. + http://git-wip-us.apache.org/repos/asf/activemq-6/blob/8ecd255f/docs/quickstart-guide/en/master.xml ---------------------------------------------------------------------- diff --git a/docs/quickstart-guide/en/master.xml b/docs/quickstart-guide/en/master.xml new file mode 100644 index 0000000..e69de29 http://git-wip-us.apache.org/repos/asf/activemq-6/blob/8ecd255f/docs/quickstart-guide/en/notice.xml ---------------------------------------------------------------------- diff --git a/docs/quickstart-guide/en/notice.xml b/docs/quickstart-guide/en/notice.xml new file mode 100644 index 0000000..f5c5f05 --- /dev/null +++ b/docs/quickstart-guide/en/notice.xml @@ -0,0 +1,37 @@ + + + + + + + + + + + + + + + + + + + +%BOOK_ENTITIES; +]> + + + Legal Notice + + Copyright © 2010 Red Hat, Inc. and others. + The text of and illustrations in this document are licensed by Red Hat under + a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). + An explanation of CC-BY-SA is available at + http://creativecommons.org/licenses/by-sa/3.0/. + In accordance with CC-BY-SA, if you distribute this document or an adaptation + of it, you must provide the URL for the original version. + Red Hat, as the licensor of this document, waives the right to enforce, + and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent + permitted by applicable law. + \ No newline at end of file http://git-wip-us.apache.org/repos/asf/activemq-6/blob/8ecd255f/docs/quickstart-guide/en/running.xml ---------------------------------------------------------------------- diff --git a/docs/quickstart-guide/en/running.xml b/docs/quickstart-guide/en/running.xml new file mode 100644 index 0000000..39f8797 --- /dev/null +++ b/docs/quickstart-guide/en/running.xml @@ -0,0 +1,125 @@ + + + + + + + + + + + + + + + + + + + + +%BOOK_ENTITIES; +]> + + Starting The Server +
+ Standalone HornetQ + To run a stand-alone server, open up a shell or command prompt and navigate into the + bin directory. Then execute ./run.sh (or run.bat on Windows) and you should see the following output + + bin$ ./run.sh + + 15:05:54,108 INFO @main [HornetQBootstrapServer] Starting HornetQ server + ... + 15:06:02,566 INFO @main [HornetQServerImpl] HornetQ Server version + 2.0.0.CR3 (yellowjacket, 111) started + + HornetQ is now running. + Both the run and the stop scripts use the config under config/stand-alone/non-clustered by default. The configuration can be changed + by running ./run.sh ../config/stand-alone/clustered or another config of + your choosing. This is the same for the stop script and the windows bat files. +
+
+ HornetQ In Wildfly + HornetQ is the Default Messaging Provider in the Wildfly Application Server + To run the server you need to run the standalone-full.xml configuration by running the command './standalone.sh -c standalone-full.xml'. + You will see something like:/ + + bin$ ./standalone.sh -c standalone-full.xml + ========================================================================= + + JBoss Bootstrap Environment + + JBOSS_HOME: /home/andy/projects/wildfly/build/target/wildfly-8.0.0.Beta1-SNAPSHOT + + JAVA: java + + JAVA_OPTS: -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true + + ========================================================================= + + 14:47:33,642 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final + 14:47:34,780 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.0.Beta2 + 14:47:34,875 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: WildFly 8.0.0.Beta1-SNAPSHOT "WildFly" starting + 14:47:40,382 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) + 14:47:40,383 INFO [org.xnio] (MSC service thread 1-15) XNIO version 3.1.0.CR7 + 14:47:40,402 INFO [org.xnio.nio] (MSC service thread 1-15) XNIO NIO Implementation Version 3.1.0.CR7 + 14:47:40,488 INFO [org.jboss.remoting] (MSC service thread 1-15) JBoss Remoting version 4.0.0.Beta1 + 14:47:40,547 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 36) JBAS010280: Activating Infinispan subsystem. + 14:47:40,560 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 47) JBAS011800: Activating Naming Subsystem + 14:47:40,560 INFO [org.jboss.as.security] (ServerService Thread Pool -- 52) JBAS013171: Activating Security Subsystem + 14:47:40,567 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 37) JBAS016300: Activating JacORB Subsystem + 14:47:40,571 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 43) JBAS012605: Activated the following JSF Implementations: [main] + 14:47:40,574 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) JBAS015537: Activating WebServices Extension + 14:47:40,721 INFO [org.jboss.as.connector.logging] (MSC service thread 1-6) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.0.Final) + 14:47:41,321 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service + 14:47:41,323 INFO [org.jboss.as.mail.extension] (MSC service thread 1-11) JBAS015400: Bound mail session [java:jboss/mail/Default] + 14:47:41,552 INFO [org.wildfly.extension.undertow] (MSC service thread 1-10) JBAS017502: Undertow 1.0.0.Beta16 starting + 14:47:41,552 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) JBAS017502: Undertow 1.0.0.Beta16 starting + 14:47:41,573 INFO [org.jboss.as.security] (MSC service thread 1-6) JBAS013170: Current PicketBox version=4.0.17.SP1 + 14:47:41,775 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) + 14:47:41,777 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-16) JBAS010417: Started Driver service with driver-name = h2 + 14:47:42,085 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) JBAS017527: Creating file handler for path /home/andy/projects/wildfly/build/target/wildfly-8.0.0.Beta1-SNAPSHOT/welcome-content + 14:47:42,086 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017525: Started server default-server. + 14:47:42,088 INFO [org.wildfly.extension.undertow] (MSC service thread 1-13) JBAS017531: Host default-host starting + 14:47:42,471 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080 + 14:47:42,823 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-10) JBAS015012: Started FileSystemDeploymentService for directory /home/andy/projects/wildfly/build/target/wildfly-8.0.0.Beta1-SNAPSHOT/standalone/deployments + 14:47:42,882 INFO [org.jboss.as.remoting] (MSC service thread 1-16) JBAS017100: Listening on 127.0.0.1:9999 + 14:47:43,037 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/andy/projects/wildfly/build/target/wildfly-8.0.0.Beta1-SNAPSHOT/standalone/data/messagingjournal,bindingsDirectory=/home/andy/projects/wildfly/build/target/wildfly-8.0.0.Beta1-SNAPSHOT/standalone/data/messagingbindings,largeMessagesDirectory=/home/andy/projects/wildfly/build/target/wildfly-8.0.0.Beta1-SNAPSHOT/standalone/data/messaginglargemessages,pagingDirectory=/home/andy/projects/wildfly/build/target/wildfly-8.0.0.Beta1-SNAPSHOT/standalone/data/messagingpaging) + 14:47:43,062 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221006: Waiting to obtain live lock + 14:47:43,103 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221012: Using AIO Journal + 14:47:43,313 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ224067: Adding protocol support CORE + 14:47:43,426 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.1.Final + 14:47:43,448 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ224067: Adding protocol support AMQP + 14:47:43,451 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ224067: Adding protocol support STOMP + 14:47:43,453 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ224067: Adding protocol support STOMP_WS + 14:47:43,567 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221034: Waiting to obtain live lock + 14:47:43,567 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221035: Live Server Obtained live lock + 14:47:43,777 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] + 14:47:43,781 INFO [org.jboss.as.jacorb] (MSC service thread 1-1) JBAS016330: CORBA ORB Service started + 14:47:44,115 INFO [org.jboss.as.jacorb] (MSC service thread 1-13) JBAS016328: CORBA Naming Service started + 14:47:44,345 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS018210: Register web context: /hornetq-server + 14:47:44,361 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221020: Started Netty Acceptor version 3.6.6.Final-90e1eb2 127.0.0.1:5455 for CORE protocol + 14:47:44,362 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221020: Started Netty Acceptor version 3.6.6.Final-90e1eb2 127.0.0.1:5445 for CORE protocol + 14:47:44,364 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221020: Started Netty Acceptor version 3.6.6.Final-90e1eb2 org.hornetq.default.servlet:5445 for CORE protocol + 14:47:44,366 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221007: Server is now live + 14:47:44,366 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221001: HornetQ Server version 2.4.0.Beta2 (Andromedian Flyer, 123) [bcc1cd10-2bfb-11e3-ad5f-9f88840f9e1a] + 14:47:44,435 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory + 14:47:44,437 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/ServletConnectionFactory + 14:47:44,439 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory + 14:47:44,462 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) JBAS010406: Registered connection factory java:/JmsXA + 14:47:44,531 INFO [org.hornetq.ra] (MSC service thread 1-3) HornetQ resource adaptor started + 14:47:44,532 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatorhornetq-ra + 14:47:44,535 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-12) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] + 14:47:44,536 INFO [org.jboss.as.messaging] (MSC service thread 1-15) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory + 14:47:44,719 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management + 14:47:44,720 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 + 14:47:44,721 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.Beta1-SNAPSHOT "WildFly" started in 12184ms - Started 213 of 249 services (73 services are lazy, passive or on-demand) + + +
+
http://git-wip-us.apache.org/repos/asf/activemq-6/blob/8ecd255f/docs/quickstart-guide/pom.xml ---------------------------------------------------------------------- diff --git a/docs/quickstart-guide/pom.xml b/docs/quickstart-guide/pom.xml new file mode 100644 index 0000000..d2e1d02 --- /dev/null +++ b/docs/quickstart-guide/pom.xml @@ -0,0 +1,300 @@ + + + + 4.0.0 + + + org.hornetq.docs + hornetq-docs + 2.5.0-SNAPSHOT + + + org.hornetq.docs + quickstart-guide + 1.0 + jdocbook + quickstart-guide + + + en + HornetQ_QuickStart_Guide + HornetQ QuickStart Guide + + + + + jboss-public-repository-group + JBoss Public Maven Repository Group + https://repository.jboss.org/nexus/content/groups/public/ + default + + true + never + + + true + never + + + + + + jboss-public-repository-group + JBoss Public Maven Repository Group + https://repository.jboss.org/nexus/content/groups/public/ + default + + true + + + true + + + + + + + + + + all + + true + + + + + org.jboss.maven.plugins + maven-jdocbook-plugin + 2.3.5 + true + + + + pdf + classpath:/xslt/org/jboss/pdf.xsl + ${docname}.pdf + + + html + classpath:/xslt/org/jboss/xhtml.xsl + index.html + + + html_single + classpath:/xslt/org/jboss/xhtml-single.xsl + index.html + + + + + + + + + + + html + + false + + + + + org.jboss.maven.plugins + maven-jdocbook-plugin + 2.2.1 + true + + + + html + classpath:/xslt/org/jboss/xhtml.xsl + index.html + + + + + + + + + + + html-single + + false + + + + + org.jboss.maven.plugins + maven-jdocbook-plugin + 2.2.1 + true + + + + + + + + pdf + + false + + + + + org.jboss.maven.plugins + maven-jdocbook-plugin + 2.2.1 + true + + + + pdf + classpath:/xslt/org/jboss/pdf.xsl + ${docname}.pdf + + + + + + + + + + + + + + org.jboss.maven.plugins + maven-jdocbook-plugin + 2.2.1 + true + + + org.jboss.pressgang + pressgang-xslt + 2.0.2 + + + org.jboss + jbossorg-jdocbook-style + 1.1.1 + jdocbook-style + + + + ${project.basedir} + ${docname}.xml + en + + ${project.basedir}/en + + images/*.png + + + + + pdf + classpath:/xslt/org/jboss/pdf.xsl + ${pdf.name} + + + html + classpath:/xslt/org/jboss/xhtml.xsl + index.html + + + html_single + classpath:/xslt/org/jboss/xhtml-single.xsl + index.html + + + + true + saxon + 1.72.0 + - + false + + + javax.xml.parsers.DocumentBuilderFactory + org.apache.xerces.jaxp.DocumentBuilderFactoryImpl + + + javax.xml.parsers.SAXParserFactory + org.apache.xerces.jaxp.SAXParserFactoryImpl + + + + + + + + + + + http://git-wip-us.apache.org/repos/asf/activemq-6/blob/8ecd255f/docs/quickstart-guide/quickstart-guide.xpr ---------------------------------------------------------------------- diff --git a/docs/quickstart-guide/quickstart-guide.xpr b/docs/quickstart-guide/quickstart-guide.xpr new file mode 100644 index 0000000..24c5847 --- /dev/null +++ b/docs/quickstart-guide/quickstart-guide.xpr @@ -0,0 +1,21 @@ + + + + + + + + + + + + + + + + + + + + http://git-wip-us.apache.org/repos/asf/activemq-6/blob/8ecd255f/docs/quickstart-guide/zh/about.xml ---------------------------------------------------------------------- diff --git a/docs/quickstart-guide/zh/about.xml b/docs/quickstart-guide/zh/about.xml new file mode 100644 index 0000000..393d60b --- /dev/null +++ b/docs/quickstart-guide/zh/about.xml @@ -0,0 +1,67 @@ + + + + + + + + + + + + + + + + + + + + + + 关于HornetQ + 什么是HornetQ? + + + HornetQ是一个开源项目。它的目标是一个多协议、可嵌入、高性能、可集群的异步的消息系统。 + + + 有关HornetQ是什么及不是什么的更多的问题,请访问 + FAQs wiki + 页 + + + 为什么要使用HornetQ? 以下给出了几个理由: + + + HornetQ是100%的开源软件。 HornetQ 采用 Apache v 2.0开源协议,对用户的限制最小。 + + + HornetQ的设计强调可用性。 + + + 采用Java语言编写。可以在任何Java 6+ 的平台上运行。这几乎包括了从Windows到IBM mainframes的每个平台。 + + + 性能出众。不但对非持久化消息的处理性能达到了非常高的性能。独特高效的日志(journal)使持久消息处理接近非持久消息的性能。 + + + 功能全面。不仅拥有其它成熟消息产品所具有的全部功能,而且还有很多独特的功能。 + + + HornetQ的设计遵从了简约的原则。对第三方软件的依赖极少。根据不同的需要, + HornetQ可以单独运行,也可以运行于JEE应用服务器中。它还可以嵌入到你自己的应用程序中。 + + + 完美的可获得性。HornetQ提供自动客户端失效备援(automatic client failover)功能,能保证在服务器故障时没有消息丢失或消息重复。 + + + 超级灵活的集群方案。可以控制集群进行消息负载均衡的方式。分布在不同地理位置的各个集群间可以通过非可靠的网络连接形成一个全球网络。 + 还可以非常灵活地配置消息路由。 + + + 请访问 wiki来全面了解HornetQ的所有功能介绍。 + + + http://git-wip-us.apache.org/repos/asf/activemq-6/blob/8ecd255f/docs/quickstart-guide/zh/download.xml ---------------------------------------------------------------------- diff --git a/docs/quickstart-guide/zh/download.xml b/docs/quickstart-guide/zh/download.xml new file mode 100644 index 0000000..a15a51a --- /dev/null +++ b/docs/quickstart-guide/zh/download.xml @@ -0,0 +1,70 @@ + + + + + + + + + + + + + + + + + + + + 下载 + HornetQ项目的官方地址是 http://hornetq.org/ +
+ 软件下载 + HornetQ的下载地址是http://hornetq.org/downloads.html +
+
+ 项目信息 + + + + HornetQ的 wiki + + + 如果在使用HornetQ中发生任何问题,可以去我们的 用户论坛 + + + + 如果你有开发方面的问题与想法,请访问我们的 开发论坛 + + + 请加入我们的IRC频道与我们的核心开发工程师交流。 + + + 我们项目有自己的 博客 + + + 还可以跟踪我们的twitter + + + HornetQ的Git代码库地址 https://github.com/hornetq/hornetq + + + 每次发布的版本标签都在https://github.com/hornetq/hornetq/tags下能找到。 + + + +
+
http://git-wip-us.apache.org/repos/asf/activemq-6/blob/8ecd255f/docs/quickstart-guide/zh/examples.xml ---------------------------------------------------------------------- diff --git a/docs/quickstart-guide/zh/examples.xml b/docs/quickstart-guide/zh/examples.xml new file mode 100644 index 0000000..dab594a --- /dev/null +++ b/docs/quickstart-guide/zh/examples.xml @@ -0,0 +1,216 @@ + + + + + + + + + + + + + + + + + + + + 运行HornetQ例子 + 在HornetQ的examples目录下有两组例子,它们是: + + + JMS例子 - 这些例子展示的是使用JMS发送与接收消息的功能。 + + + Java EE 例子 - 这些例子展示的是与应用服务器的集成,例如MDB,EJB,Servlet等。 + + +
+ JMS例子 + 所有JMS都有统一的格式。每个例子都有自己的目录,它的内容包括: + + + build.xml + ant的build文件,用来运行例子。 + + + src 目录 + 例子的代码。 + + + server0配置目录 + 它包含了运行服务器所需要的配置文件。有的集群的例子可能有多个这样的目录,如server0, + server1等。 + + + 在运行每个例子时,都要先启动一个或多个单独的服务器。当例子运行完毕,再将它们停止。 + 做为演示我们这里运行queue例子。其它的例子可以参见用户手册。 + 首先打开一个命令行窗口(shell),进入到HornetQ的 examples/jms/queue目录。 + 敲入命令./build.sh (或者在Windows上build.bat),你 + 将看到如下的输出: + Buildfile: build.xml + +run: + +init: + +compile: + [echo] src.example.dir=/home/andy/projects/hornetq/trunk/examples/jms/queue/src + [javac] Compiling 5 source files to /home/andy/projects/hornetq/trunk/examples/jms/queue +/build/classes + +runExample: + [java] 10:41:04,149 INFO @main [JMSExample] hornetq.example.runServer is true + [java] 10:41:04,149 INFO @main [JMSExample] starting server with config 'server0' + logServerOutput true + [java] 10:41:04,149 INFO @main [JMSExample] and vm args: -Xms512M,-Xmx512M,-XX:+U +seParallelGC,-XX:+AggressiveOpts,-XX:+UseFastAccessorMethods,-Djava.util.logging.config. +file=/home/andy/projects/hornetq/trunk/examples/jms/common/../../../src/config/stand-alone/no +n-clustered/logging.properties + [java] org.hornetq.jms.example.SpawnedJMSServer out:10:41:08,437 INFO @main [Journal +StorageManager] AIO journal selected + [java] org.hornetq.jms.example.SpawnedJMSServer out:10:41:08,437 WARN @main [Journal +StorageManager] AIO wasn't located on this platform, it will fall back to using pure Jav +a NIO. If your platform is Linux, install LibAIO to enable the AIO journal + [java] org.hornetq.jms.example.SpawnedJMSServer out:10:41:08,437 WARN @main [Securit +yStoreImpl] It has been detected that the cluster admin password which is used to replic +ate management operation from one node to the other has not had its password changed fro +m the installation default. Please see the HornetQ user guide for instructions o +n how to do this. + [java] org.hornetq.jms.example.SpawnedJMSServer out:10:41:10,941 INFO @main [HornetQCo +nnectionFactory] read only is false + [java] org.hornetq.jms.example.SpawnedJMSServer out:10:41:10,941 INFO @main [HornetQCo +nnectionFactory] read only is false + [java] org.hornetq.jms.example.SpawnedJMSServer out:10:41:10,941 INFO @main [HornetQCo +nnectionFactory] read only is false + [java] org.hornetq.jms.example.SpawnedJMSServer out:10:41:10,991 WARN @main [JMSServ +erManagerImpl] Binding for java:/ConnectionFactory already exists + [java] org.hornetq.jms.example.SpawnedJMSServer out:10:41:10,991 WARN @main [JMSServ +erManagerImpl] Binding for java:/XAConnectionFactory already exists + [java] org.hornetq.jms.example.SpawnedJMSServer out:10:41:11,241 INFO @main [Messagi +ngServerImpl] HornetQ Server version 2.0.0.BETA5 (buzz-buzz, 107) started + [java] org.hornetq.jms.example.SpawnedJMSServer out:10:41:11,241 INFO @main [HornetQBoot +strapServer] HornetQ server started + [java] org.hornetq.jms.example.SpawnedJMSServer out:STARTED:: + [java] 10:41:11,276 INFO @main [JMSExample] using server0/client-jndi.properties f +or jndi + [java] Sent message: This is a text message + [java] Received message: This is a text message + [java] + [java] ##################### + [java] ### SUCCESS! ### + [java] ##################### + +BUILD SUCCESSFUL +Total time: 13 seconds + + 恭喜!你已经成功地运行了你的第一个HornetQ例子。试着运行其它的例子。 +
+
+ Java EE例子 + Java EE的例子需要首先运行一个JEE应用服务器。这些例子包括MDB,Servlet,EJB等等。你首先要安装JBoss应用服务 + 器。参见前面的章节进行安装。 + 这里我们将用MDB例子来说明。有关其它例子的详细信息参见用户手册。首先确认JBoss应用服务器已经启动。 + 如同其它Java EE例子一样,MDB需要部署到应用服务器。第一,将JBOSS_HOME环境变量 + 指向你的应用服务器安装目录。如在Linux下: + export JBOSS_HOME=/home/jbossas5.1/build/output/jboss-5.1.0.GA + 然后就可以进行部署了。在examples/javaee/mdb目录下运行: + ./build.sh deploy + 它将创建一个“messaging"的AS配置,并用它来启动AS服务器。 + 在命令行窗口你会看到如下的输出: + Buildfile: build.xml + +validate-jboss: + +deploy: + +deploy-resources: + [copy] Copying 1 file to /home/andy/projects/jbossas5.1/build/output/jboss-5.1.0.GA + /server/default-with-hornetq/deploy/hornetq.sar + [copy] Copying 1 file to /home/andy/projects/jbossas5.1/build/output/jboss-5.1.0.GA + /server/default-with-hornetq/deploy/hornetq.sar + +init: + +compile: + +jar: + [jar] Building jar: /home/andy/projects/hornetq/trunk/examples/javaee/mdb/build/mdb-exa + mple.jar + +ear: + [jar] Building jar: /home/andy/projects/hornetq/trunk/examples/javaee/mdb/build/mdb-exa + mple.ear + +deploy-ear: + [copy] Copying 1 file to /home/andy/projects/jbossas5.1/build/output/jboss-5.1.0.GA + + ....... + + + [exec] 16:01:04,607 INFO [JBossASKernel] Class:javax.jms.MessageListener + [exec] 16:01:04,607 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=mdb-example.ear, + jar=mdb-example.jar,name=MessageMDBExample,service=EJB3) to KernelDeployment of: + mdb-example.jar + [exec] 16:01:04,702 INFO [EJBContainer] STARTED EJB: org.hornetq.javaee.example.server + .MDBExample ejbName: MessageMDBExample + [exec] 16:01:09,496 INFO [TomcatDeployment] deploy, ctxPath=/mdb-example + [exec] 16:01:09,812 WARNING [config] Unable to process deployment descriptor for cont + ext '/mdb-example' + [exec] 16:01:09,812 INFO [config] Initializing Mojarra (1.2_12-b01-FCS) for context + '/mdb-example' + [exec] 16:01:09,958 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1- + 8080 + [exec] 16:01:09,990 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 + [exec] 16:01:10,001 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag + =JBoss_5_1_0_GA date=200905151005)] Started in 6m:21s:797ms + + + 现在我们可以运行例子了。在mdb目录下运行下列命令: + ./build.sh + 你将看到如下输出: + Buildfile: build.xml + +run: + +init: + +compile: + +runExample: + [java] Sent message: This is a text message + +BUILD SUCCESSFUL +Total time: 7 seconds + 在JBoss应用服务器端你还会看到如下的输出: + 16:27:54,703 INFO [STDOUT] message This is a text message received + 然后在mdb目录下运行下面的命令可以将这个例子卸载。 + ./build.sh undeploy + 你将会看到如下的输出: + Buildfile: build.xml + +validate-jboss: + +undeploy: + +undeploy-misc: + [delete] Deleting: /home/andy/projects/jbossas5.1/build/output/jboss-5.1.0.GA + /server/default-with-hornetq/deploy/mdb-example.ear + [delete] Deleting: /home/andy/projects/jbossas5.1/build/output/jboss-5.1.0.GA + /server/default-with-hornetq/deploy/hornetq.sar/hornetq-queues.xml + [delete] Deleting: /home/andy/projects/jbossas5.1/build/output/jboss-5.1.0.GA + /server/default-with-hornetq/deploy/hornetq.sar/hornetq-jms.xml + +BUILD SUCCESSFUL +Total time: 1 second + + 你还会在窗口输出中看到MDB的应用最終被删除了,如: + 16:36:45,277 INFO [EJBContainer] STOPPED EJB: org.jboss.javaee.example.server.MDBExample + ejbName: MessageMDBExample + + 恭喜!你已经成功地部署并运行了一个Java EE的例子。 +
+
http://git-wip-us.apache.org/repos/asf/activemq-6/blob/8ecd255f/docs/quickstart-guide/zh/images/hornetQ_logo_600px.png ---------------------------------------------------------------------- diff --git a/docs/quickstart-guide/zh/images/hornetQ_logo_600px.png b/docs/quickstart-guide/zh/images/hornetQ_logo_600px.png new file mode 100644 index 0000000..b71f4ba Binary files /dev/null and b/docs/quickstart-guide/zh/images/hornetQ_logo_600px.png differ