qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rgodf...@apache.org
Subject svn commit: r1227030 [6/8] - in /qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book: html-single/ html/ html/css/ pdf/
Date Wed, 04 Jan 2012 02:22:59 GMT
Added: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-FAQ.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-FAQ.html?rev=1227030&view=auto
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-FAQ.html (added)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-FAQ.html Wed Jan  4 02:22:58 2012
@@ -0,0 +1,827 @@
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.2.  Qpid Java FAQ</title><link rel="stylesheet" href="css/style.css" type="text/css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in Java)"><link rel="up" href="Java-General-User-Guides.html" title="Chapter 1. General User Guides"><link rel="prev" href="Java-General-User-Guides.html" title="Chapter 1. General User Guides"><link rel="next" href="Java-Environment-Variables.html" title="1.3.  Java Environment Variables"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.2. 
+      Qpid Java FAQ
+    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Java-General-User-Guides.html">Prev</a> </td><th width="60%" align="center">Chapter 1. General User Guides</th><td width="20%" align="right"> <a accesskey="n" href="Java-Environment-Variables.html">Next</a></td></tr></table><hr></div><div class="section" title="1.2.  Qpid Java FAQ"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="Qpid-Java-FAQ"></a>1.2. 
+      Qpid Java FAQ
+    </h2></div></div></div>
+
+    <div class="section" title="1.2.1. Purpose"><div class="titlepage"><div><div><h3 class="title"><a name="QpidJavaFAQ-Purpose"></a>1.2.1. Purpose</h3></div></div></div>
+      
+	  <p>
+            Here are a list of commonly asked questions and answers. Click on
+            the the bolded questions for the answer to unfold. If you have
+            any questions which are not on this list, please email our
+            qpid-user list.
+          </p>
+
+	  <div class="section" title="1.2.1.1.  What is Qpid ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-WhatisQpid-3F"></a>1.2.1.1. 
+            What is Qpid ?
+          </h4></div></div></div>
+
+	  <p>
+            The java implementation of Qpid is a pure Java message broker
+            that implements the AMQP protocol. Essentially, Qpid is a robust,
+            performant middleware component that can handle your messaging
+            traffic.
+          </p><p>
+            It currently supports the following features:
+          </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>High performance header-based routing for messages
+            </p></li><li class="listitem"><p>All features required by the JMS 1.1 specification. Qpid
+            passes all tests in the Sun JMS compliance test suite
+            </p></li><li class="listitem"><p>Transaction support
+            </p></li><li class="listitem"><p>Persistence using the high performance Berkeley DB Java
+            Edition. The persistence layer is also pluggable should an
+            alternative implementation be required. The BDB store is
+            available from the <a class="xref" href="">???</a> page
+            </p></li><li class="listitem"><p>Pluggable security using SASL. Any Java SASL provider can be
+            used
+            </p></li><li class="listitem"><p>Management using JMX and a custom management console built
+            using Eclipse RCP
+            </p></li><li class="listitem"><p>Naturally, interoperability with other clients including the
+            Qpid .NET, Python, Ruby and C++ implementations
+            </p></li></ul></div>
+	  </div>
+
+	  <div class="section" title="1.2.1.2.  Why am I getting a ConfigurationException at broker startup ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-WhyamIgettingaConfigurationExceptionatbrokerstartup-3F"></a>1.2.1.2. 
+            Why am I getting a ConfigurationException at broker startup ?
+          </h4></div></div></div>
+
+	  <div class="section" title="InvocationTargetException"><div class="titlepage"><div><div><h5 class="title"><a name="QpidJavaFAQ-InvocationTargetException"></a>
+            InvocationTargetException
+          </h5></div></div></div>
+	  <p>
+            If you get a java.lang.reflect.InvocationTargetException on
+            startup, wrapped as ConfigurationException like this:
+          </p>
+            <pre class="programlisting">
+Error configuring message broker: org.apache.commons.configuration.ConfigurationException: java.lang.reflect.InvocationTargetException 
+2008-09-26 15:14:56,529 ERROR [main] server.Main (Main.java:206) - Error configuring message broker: org.apache.commons.configuration.ConfigurationException: java.lang.reflect.InvocationTargetException 
+org.apache.commons.configuration.ConfigurationException: java.lang.reflect.InvocationTargetException 
+at org.apache.qpid.server.security.auth.database.ConfigurationFilePrincipalDatabaseManager.initialisePrincipalDatabase(ConfigurationFilePrincipalDatabaseManager.java:158) 
+at org.apache.qpid.server.security.auth.database.ConfigurationFilePrincipalDatabaseManager.initialisePrincipalDatabases(ConfigurationFilePrincipalDatabaseManager.java:87) 
+at org.apache.qpid.server.security.auth.database.ConfigurationFilePrincipalDatabaseManager.&lt;init&gt;(ConfigurationFilePrincipalDatabaseManager.java:56) 
+at org.apache.qpid.server.registry.ConfigurationFileApplicationRegistry.initialise(ConfigurationFileApplicationRegistry.java:117) 
+at org.apache.qpid.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:79) 
+at org.apache.qpid.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:67) 
+at org.apache.qpid.server.Main.startup(Main.java:260) 
+at org.apache.qpid.server.Main.execute(Main.java:196) 
+at org.apache.qpid.server.Main.&lt;init&gt;(Main.java:96) 
+at org.apache.qpid.server.Main.main(Main.java:454) 
+at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
+at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
+at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
+at java.lang.reflect.Method.invoke(Method.java:597) 
+at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) 
+Caused by: java.lang.reflect.InvocationTargetException 
+at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
+at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
+at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
+at java.lang.reflect.Method.invoke(Method.java:597) 
+at org.apache.qpid.server.security.auth.database.ConfigurationFilePrincipalDatabaseManager.initialisePrincipalDatabase(ConfigurationFilePrincipalDatabaseManager.java:148) 
+</pre>
+          <p>
+            .. then it means you have a missing password file.
+          </p><p>
+            You need to create a password file for your deployment and update
+            your config.xml to reflect the location of the password file for
+            your instance.
+          </p><p>
+            The config.xml can be a little confusing in terms of element
+            names and file names for passwords.
+          </p><p>
+            To do this, you need to edit the passwordDir element for the
+            broker, which may have a comment to that effect:
+          </p>
+            <pre class="programlisting">
+&lt;passwordDir&gt;&lt;!-- Change to the location --&gt;&lt;/passwordDir&gt;
+</pre>
+          <p>
+            The file should be named passwd by default but if you want to you
+            can change this by editing this element:
+          </p>
+            <pre class="programlisting">
+&lt;value&gt;${passwordDir}/passwd&lt;/value&gt;
+</pre>
+	  </div>
+
+
+	  <div class="section" title="Cannot locate configuration source null/virtualhosts.xml"><div class="titlepage"><div><div><h5 class="title"><a name="QpidJavaFAQ-Cannotlocateconfigurationsourcenull-2Fvirtualhosts.xml"></a>
+            Cannot locate configuration source null/virtualhosts.xml
+          </h5></div></div></div>
+
+	  <p>
+            If you get this message, wrapped inside a ConfigurationException
+            then you've come across a known issue, see JIRA <a class="xref" href="">???</a>
+          </p><p>
+            The work around is to use a qualified path as the parameter value
+            for your -c option, rather than (as you migth be) starting the
+            broker from your installed etc directory. Even going up one level
+            and using a path relative to your £QPID_HOME directory
+            would sort this e.g qpid-server -c ./etc/myconfig.xml
+          </p>
+</div>
+</div>
+
+	  <div class="section" title="1.2.1.3.  How do I run the Qpid broker ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-HowdoIruntheQpidbroker-3F"></a>1.2.1.3. 
+            How do I run
+            the Qpid broker ?
+          </h4></div></div></div>
+
+	  <p>
+            The broker comes with a script for unix/linux/cygwin called
+            qpid-server, which can be found in the bin directory of the
+            installed package. This command can be executed without any
+            paramters and will then use the default configuration file
+            provided on install.
+          </p><p>
+            For the Windows OS, please use qpid-server.bat.
+          </p><p>
+            There's no need to set your classpath for QPID as the scripts
+            take care of that by adding jar's with classpath defining
+            manifest files to your classpath.
+          </p><p>
+            For more information on running the broker please see our
+            <a class="xref" href="">???</a> page.
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.4.  How can I create a connection using a URL ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-HowcanIcreateaconnectionusingaURL-3F"></a>1.2.1.4. 
+            How can I
+            create a connection using a URL ?
+          </h4></div></div></div>
+
+	  <p>
+            Please see the <a class="xref" href="">???</a> documentation.
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.5.  How do I represent a JMS Destination string with QPID ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-HowdoIrepresentaJMSDestinationstringwithQPID-3F"></a>1.2.1.5. 
+            How
+            do I represent a JMS Destination string with QPID ?
+          </h4></div></div></div>
+
+	  <div class="section" title="Queues"><div class="titlepage"><div><div><h5 class="title"><a name="QpidJavaFAQ-Queues"></a>
+            Queues
+          </h5></div></div></div>
+
+	  <p>
+            A queue can be created in QPID using the following URL format.
+          </p><p>
+            direct://amq.direct/&lt;Destination&gt;/&lt;Queue
+            Name&gt;
+          </p><p>
+            For example:
+            direct://amq.direct/&lt;Destination&gt;/simpleQueue
+          </p><p>
+            Queue names may consist of any mixture of digits, letters, and
+            underscores.
+          </p><p>
+            The <a class="xref" href="">???</a> is described in more
+            detail on it's own page.
+          </p>
+</div>
+
+	  <div class="section" title="Topics"><div class="titlepage"><div><div><h5 class="title"><a name="QpidJavaFAQ-Topics"></a>
+            Topics
+          </h5></div></div></div>
+
+	  <p>
+            A topic can be created in QPID using the following URL format.
+          </p><p>
+            topic://amq.topic/&lt;Topic Subscription&gt;/
+          </p><p>
+            The topic subscription may only contain the letters A-Z and a-z
+            and digits 0-9.
+          </p><p>
+            The topic subscription is formed from a series of words that may
+            only contain the letters A-Z and a-z and digits 0-9.
+            The words are delimited by dots. Each dot represents a new level.
+          </p><p>
+            For example: stocks.nyse.ibm
+          </p><p>
+            Wildcards can be used on subscription with the following meaning.
+          </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>match a single level
+              # match zero or more levels
+            </p></li></ul></div><p>
+            For example:
+            With two clients
+            1 - stocks.*.ibm
+            2 - stocks.#.ibm
+          </p><p>
+            Publishing stocks.nyse.ibm will be received by both
+            clients but stocks.ibm and stocks.world.us.ibm
+            will only be received by client 2.
+          </p><p>
+            The topic currently does not support wild cards.
+          </p>
+</div>
+</div>
+
+	  <div class="section" title="1.2.1.6.  How do I connect to the broker using JNDI ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-HowdoIconnecttothebrokerusingJNDI-3F"></a>1.2.1.6. 
+            How do I
+            connect to the broker using JNDI ?
+          </h4></div></div></div>
+
+	  <p>
+            see <a class="xref" href="">???</a>
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.7.  I'm using Spring and Weblogic - can you help me with the configuration for moving over to Qpid ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-I-27musingSpringandWeblogiccanyouhelpmewiththeconfigurationformovingovertoQpid-3F"></a>1.2.1.7. 
+            I'm using Spring and Weblogic - can you help me with the
+            configuration for moving over to Qpid ?
+          </h4></div></div></div>
+
+	  <p>
+            Here is a donated Spring configuration file <a class="ulink" href="http://qpid.apache.org/qpid-java-faq.data/appContext.zip" target="_top">appContext.zip</a>
+            which shows the config for Qpid side by side with
+            Weblogic. HtH !
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.8.  How do I configure the logging level for Qpid ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-HowdoIconfigurethelogginglevelforQpid-3F"></a>1.2.1.8. 
+            How do
+            I configure the logging level for Qpid ?
+          </h4></div></div></div>
+
+	  <p>
+            The system property
+          </p>
+            <pre class="programlisting">
+amqj.logging.level
+</pre>
+          <p>
+            can be used to configure the logging level.
+            For the broker, you can use the environment variable
+            AMQJ_LOGGING_LEVEL which is picked up by the qpid-run script
+            (called by qpid-server to start the broker) at runtime.
+          </p><p>
+            For client code that you've written, simply pass in a system
+            property to your command line to set it to the level you'd like
+            i.e.
+          </p>
+            <pre class="programlisting">
+-Damqj.logging.level=INFO
+</pre>
+          <p>
+            The log level for the broker defaults to INFO if the env variable
+            is not set, but you may find that your log4j properties affect
+            this. Setting the property noted above should address this.
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.9.  How can I configure my application to use Qpid client logging?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-HowcanIconfiguremyapplicationtouseQpidclientlogging-3F"></a>1.2.1.9. 
+            How can I configure my application to use Qpid client
+            logging?
+          </h4></div></div></div>
+
+	  <p>
+            If you don't already have a logging implementation in your
+            classpath you should add slf4-log4j12-1.4.0.jar and
+            log4j-1.2.12.jar.
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.10.  How can I configure the broker ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-HowcanIconfigurethebroker-3F"></a>1.2.1.10. 
+            How can I
+            configure the broker ?
+          </h4></div></div></div>
+
+	  <p>
+            The broker configuration is contained in the
+            &lt;installed-dir&gt;/etc/config.xml file. You can copy and edit
+            this file and then specify your own configuration file as a
+            parameter to the startup script using the -c flag i.e.
+            qpid-server -c &lt;your_config_file's_path&gt;
+          </p><p>
+            For more detailed information on configuration, please see
+            <a class="xref" href="">???</a>
+          </p><p>
+            
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.11.  What ports does the broker use?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-Whatportsdoesthebrokeruse"></a>1.2.1.11. 
+            What ports
+            does the broker use?
+          </h4></div></div></div>
+
+	  <p>
+            The broker defaults to use port 5672 at startup for AMQP
+            traffic.
+            If the management interface is enabled it starts on port 8999 by
+            default.
+          </p><p>
+            The JMX management interface actually requires 2 ports to
+            operate, the second of which is indicated to the client
+            application during connection initiation to the main (default:
+            8999) port. Previously this second port has been chosen at random
+            during broker startup, however since Qpid 0.5 this has been fixed
+            to a port 100 higher than the main port(ie Default:9099) in order
+            to ease firewall navigation.
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.12.  How can I change the port the broker uses at runtime ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-HowcanIchangetheportthebrokerusesatruntime-3F"></a>1.2.1.12. 
+            How
+            can I change the port the broker uses at runtime ?
+          </h4></div></div></div>
+
+	  <p>
+            The broker defaults to use port 5672 at startup for AMQP
+            traffic.
+            The broker also uses port 8999 for the JMX Management interface.
+          </p><p>
+            To change the AMQP traffic port use the -p flag at startup. To
+            change the management port use -m
+            i.e. qpid-server -p &lt;port_number_to_use&gt; -m
+            &lt;port_number_to_use&gt;
+          </p><p>
+            Use this to get round any issues on your host server with port
+            5672/8999 being in use/unavailable.
+          </p><p>
+            For additional details on what ports the broker uses see <a class="xref" href="Qpid-Java-FAQ.html#QpidJavaFAQ-Whatportsdoesthebrokeruse" title="1.2.1.11.  What ports does the broker use?">Section 1.2.1.11, &#8220;
+            What ports
+            does the broker use?
+          &#8221;</a> FAQ
+            entry.
+            For more detailed information on configuration, please see
+            <a class="xref" href="">???</a>
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.13.  What command line options can I pass into the qpid-server script ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-WhatcommandlineoptionscanIpassintotheqpidserverscript-3F"></a>1.2.1.13. 
+            What command line options can I pass into the qpid-server
+            script ?
+          </h4></div></div></div>
+
+	  <p>
+            The following command line options are available:
+          </p>
+
+	  <p>
+            The following options are available:
+          </p><div class="table"><a name="id1325846"></a><p class="title"><b>Table 1.1. 
+            Command Line Options
+          </b></p><div class="table-contents">
+	  
+
+	  <table summary="
+            Command Line Options
+          " border="1"><colgroup><col><col><col></colgroup><tbody><tr><td>
+                  Option
+                </td><td>
+                  Long Option
+                </td><td>
+                  Description
+                </td></tr><tr><td>
+                  b
+                </td><td>
+                  bind
+                </td><td>
+                  Bind to the specified address overriding any value in the
+                  config file
+                </td></tr><tr><td>
+                  c
+                </td><td>
+                  config
+                </td><td>
+                  Use the given configuration file
+                </td></tr><tr><td>
+                  h
+                </td><td>
+                  help
+                </td><td>
+                  Prints list of options
+                </td></tr><tr><td>
+                  l
+                </td><td>
+                  logconfig
+                </td><td>
+                  Use the specified log4j.xml file rather than that in the
+                  etc directory
+                </td></tr><tr><td>
+                  m
+                </td><td>
+                  mport
+                </td><td>
+                  Specify port to listen on for the JMX Management. Overrides
+                  value in config file
+                </td></tr><tr><td>
+                  p
+                </td><td>
+                  port
+                </td><td>
+                  Specify port to listen on. Overrides value in config file
+                </td></tr><tr><td>
+                  v
+                </td><td>
+                  version
+                </td><td>
+                  Print version information and exit
+                </td></tr><tr><td>
+                  w
+                </td><td>
+                  logwatch
+                </td><td>
+                  Specify interval for checking for logging config changes.
+                  Zero means no checking
+                </td></tr></tbody></table></div></div><br class="table-break">
+	  </div>
+
+	  <div class="section" title="1.2.1.14.  How do I authenticate with the broker ? What user id &amp; password should I use ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-HowdoIauthenticatewiththebroker-3FWhatuserid-26passwordshouldIuse-3F"></a>1.2.1.14. 
+            How do I authenticate with the broker ? What user id &amp;
+            password should I use ?
+          </h4></div></div></div>
+
+	  <p>
+            You should login as user guest with password guest
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.15.  How do I create queues that will always be instantiated at broker startup ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-HowdoIcreatequeuesthatwillalwaysbeinstantiatedatbrokerstartup-3F"></a>1.2.1.15. 
+            How do I create queues that will always be instantiated at
+            broker startup ?
+          </h4></div></div></div>
+
+	  <p>
+            You can configure queues which will be created at broker startup
+            by tailoring a copy of the virtualhosts.xml file provided in the
+            installed qpid-version/etc directory.
+          </p><p>
+            So, if you're using a queue called 'devqueue' you can ensure that
+            it is created at startup by using an entry something like this:
+          </p>
+            <pre class="programlisting">
+&lt;virtualhosts&gt;
+  &lt;default&gt;test&lt;/default&gt;
+  &lt;virtualhost&gt;
+   &lt;name&gt;test&lt;/name&gt;
+   &lt;test&gt;
+   &lt;queue&gt;
+      &lt;name&gt;devqueue&lt;/name&gt;
+      &lt;devqueue&gt;
+        &lt;exchange&gt;amq.direct&lt;/exchange&gt;
+        &lt;maximumQueueDepth&gt;4235264&lt;/maximumQueueDepth&gt;  &lt;!-- 4Mb --&gt;
+        &lt;maximumMessageSize&gt;2117632&lt;/maximumMessageSize&gt; &lt;!-- 2Mb --&gt;
+        &lt;maximumMessageAge&gt;600000&lt;/maximumMessageAge&gt;  &lt;!-- 10 mins --&gt;
+      &lt;/devqueue&gt;
+   &lt;/queue&gt;
+   &lt;/test&gt;
+  &lt;/virtualhost&gt;
+&lt;/virtualhosts&gt;
+</pre>
+          <p>
+            Note that the name (in thie example above the name is 'test')
+            element should match the virtualhost that you're using to create
+            connections to the broker. This is effectively a namespace used
+            to prevent queue name clashes etc. You can also see that we've
+            set the 'test' virtual host to be the default for any connections
+            which do not specify a virtual host (in the &lt;default&gt; tag).
+          </p><p>
+            You can amend the config.xml to point at a different
+            virtualhosts.xml file by editing the &lt;virtualhosts/&gt;
+            element.
+          </p><p>
+            So, for example, you could tell the broker to use a file in your
+            home directory by creating a new config.xml file with the
+            following entry:
+          </p><p>
+            &lt;virtualhosts&gt;/home/myhomedir/virtualhosts.xml&lt;/virtualhosts&gt;
+          </p><p>
+            You can then pass this amended config.xml into the broker at
+            startup using the -c flag i.e.
+            qpid-server -c &lt;path&gt;/config.xml
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.16.  How do I create queues at runtime?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-HowdoIcreatequeuesatruntime-3F"></a>1.2.1.16. 
+            How do I
+            create queues at runtime?
+          </h4></div></div></div>
+
+	  <p>
+            Queues can be dynamically created at runtime by creating a
+            consumer for them. After they have been created and bound (which
+            happens automatically when a JMS Consumer is created) a publisher
+            can send messages to them.
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.17.  How do I tune the broker?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-HowdoItunethebroker-3F"></a>1.2.1.17. 
+            How do I tune
+            the broker?
+          </h4></div></div></div>
+
+	  <p>
+            There are a number of tuning options available, please see the
+            <a class="xref" href="How-to-Tune-M3-Java-Broker-Performance.html" title="2.8.  How to Tune M3 Java Broker Performance">Section 2.8, &#8220;
+      How to Tune M3 Java Broker Performance
+    &#8221;</a> page for more information.
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.18.  Where do undeliverable messages end up ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-Wheredoundeliverablemessagesendup-3F"></a>1.2.1.18. 
+            Where do
+            undeliverable messages end up ?
+          </h4></div></div></div>
+
+	  <p>
+            At present, messages with an invalid routing key will be returned
+            to the sender. If you register an exception listener for your
+            publisher (easiest to do by making your publisher implement the
+            ExceptionListener interface and coding the onException method)
+            you'll see that you end up in onException in this case. You can
+            expect to be catching a subclass of
+            org.apache.qpid.AMQUndeliveredException.
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.19.  Can I configure the name of the Qpid broker log file at runtime ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-CanIconfigurethenameoftheQpidbrokerlogfileatruntime-3F"></a>1.2.1.19. 
+            Can I configure the name of the Qpid broker log file at
+            runtime ?
+          </h4></div></div></div>
+
+	  <p>
+            If you simply start the Qpid broker using the default
+            configuration, then the log file is written to
+            $QPID_WORK/log/qpid.log
+          </p><p>
+            This is not ideal if you want to run several instances from one
+            install, or acrhive logs to a shared drive from several hosts.
+          </p><p>
+            To make life easier, there are two optional ways to configure the
+            naming convention used for the broker log.
+          </p>
+
+	  <div class="section" title="Setting a prefix or suffix"><div class="titlepage"><div><div><h5 class="title"><a name="QpidJavaFAQ-Settingaprefixorsuffix"></a>
+            Setting a prefix
+            or suffix
+          </h5></div></div></div>
+
+	  <p>
+            Users should set the following environment variables before
+            running qpid-server:
+          </p><p>
+            QPID_LOG_PREFIX - will prefix the log file name with the
+            specified value e.g. if you set this value to be the name of your
+            host (for example) it could look something like host123qpid.log
+          </p><p>
+            QPID_LOG_SUFFIX - will suffix the file name with the specified
+            value e.g. if you set this value to be the name of your
+            application (for example) if could look something like
+            qpidMyApp.log
+          </p>
+</div>
+
+	  <div class="section" title="Including the PID"><div class="titlepage"><div><div><h5 class="title"><a name="QpidJavaFAQ-IncludingthePID"></a>
+            Including the PID
+          </h5></div></div></div>
+
+	  <p>
+            Setting either of these variables to the special value PID will
+            introduce the process id of the java process into the file name
+            as a prefix or suffix as specified**
+          </p>
+</div>
+</div>          
+
+	  <div class="section" title="1.2.1.20.  My client application appears to have hung?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-Myclientapplicationappearstohavehung-3F"></a>1.2.1.20. 
+            My
+            client application appears to have hung?
+          </h4></div></div></div>
+
+	  <p>
+            The client code currently has various timeouts scattered
+            throughout the code. These can cause your client to appear like
+            it has hung when it is actually waiting for the timeout ot
+            compelete. One example is when the broker becomes non-responsive,
+            the client code has a hard coded 2 minute timeout that it will
+            wait when closing a connection. These timeouts need to be
+            consolidated and exposed. see <a class="xref" href="">???</a>
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.21.  How do I contact the Qpid team ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-HowdoIcontacttheQpidteam-3F"></a>1.2.1.21. 
+            How do I
+            contact the Qpid team ?
+          </h4></div></div></div>
+
+	  <p>
+            For general questions, please subscribe to the
+            <a class="ulink" href="mailto:users@qpid.apache.org" target="_top">users@qpid.apache.org</a> mailing list.
+          </p><p>
+            For development questions, please subscribe to the
+            <a class="ulink" href="mailto:dev@qpid.apache.org" target="_top">dev@qpid.apache.org</a> mailing list.
+          </p><p>
+            More details on these lists are available on our <a class="xref" href="">???</a>
+            page.
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.22.  How can I change a user's password while the broker is up ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-HowcanIchangeauser-27spasswordwhilethebrokerisup-3F"></a>1.2.1.22. 
+            How can I change a user's password while the broker is up ?
+          </h4></div></div></div>
+
+	  <p>
+            You can do this via the <a class="xref" href="">???</a>. To
+            do this simply log in to the management console as an admin user
+            (you need to have created an admin account in the
+            jmxremote.access file first) and then select the 'UserManagement'
+            mbean. Select the user in the table and click the Set Password
+            button. Alternatively, update the password file and use the
+            management console to reload the file with the button at the
+            bottom of the 'UserManagement' view. In both cases, this will
+            take effect when the user next logs in i.e. will not cause them
+            to be disconnected if they are already connected.
+          </p><p>
+            For more information on the Management Console please see our
+            <a class="xref" href="Qpid-JMX-Management-Console.html#Qpid-JMX-Management-Console-User-Guide" title="3.1.1.5.  Qpid JMX Management Console User Guide">Section 3.1.1.5, &#8220;
+      Qpid JMX Management Console User Guide
+    &#8221;</a>
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.23.  How do I know if there is a consumer for a message I am going to send?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-HowdoIknowifthereisaconsumerforamessageIamgoingtosend-3F"></a>1.2.1.23. 
+            How do I know if there is a consumer for a message I am going
+            to send?
+          </h4></div></div></div>
+
+	  <p>
+            Knowing that there is a consumer for a message is quite tricky.
+            That said using the qpid.jms.Session#createProducer with
+            immediate and mandatory set to true will get you part of the way
+            there.
+          </p><p>
+            If you are publishing to a well known queue then immediate will
+            let you know if there is any consumer able to pre-fetch that
+            message at the time you send it. If not it will be returned to
+            you on your connection listener.
+          </p><p>
+            If you are sending to a queue that the consumer creates then the
+            mandatory flag will let you know if they have not yet created
+            that queue.
+          </p><p>
+            These flags will not be able to tell you if the consuming
+            application has received the message and is able to process it.
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.24.  How can I inspect the contents of my MessageStore?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-HowcanIinspectthecontentsofmyMessageStore-3F"></a>1.2.1.24. 
+            How
+            can I inspect the contents of my MessageStore?
+          </h4></div></div></div>
+
+	  <p>
+            There are two possibilities here:
+          </p><p>
+            1) The management console can be used to interogate an active
+            broker and browse the contents of a queue.See the <a class="xref" href="">???</a>
+            page for further details.
+          </p><p>
+            2) The <a class="xref" href="">???</a> can be used to inspect
+            the contents of a persistent message store. Note: this can
+            currently only be used when the broker is offline.
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.25.  Why are my transient messages being so slow?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-Whyaremytransientmessagesbeingsoslow-3F"></a>1.2.1.25. 
+            Why are
+            my transient messages being so slow?
+          </h4></div></div></div>
+
+	  <p>
+            You should check that you aren't sending persistent messages,
+            this is the default. If you want to send transient messages you
+            must explicitly set this option when instantiating your
+            MessageProducer or on the send() method.
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.26.  Why does my producer fill up the broker with messages?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-Whydoesmyproducerfillupthebrokerwithmessages-3F"></a>1.2.1.26. 
+            Why
+            does my producer fill up the broker with messages?
+          </h4></div></div></div>
+
+	  <p>
+            The Java broker does not currently implement producer flow
+            control. Publishes are currently asynchronous, so there is no
+            ability to rate limit this automatically. While this is something
+            which will be addressed in the future, it is currently up to
+            applications to ensure that they do not publish faster than the
+            messages are being consumed for signifcant periods of time.
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.27.  The broker keeps throwing an OutOfMemory exception?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-ThebrokerkeepsthrowinganOutOfMemoryexception-3F"></a>1.2.1.27. 
+            The
+            broker keeps throwing an OutOfMemory exception?
+          </h4></div></div></div>
+
+	  <p>
+            The broker can no longer store any more messages in memory. This
+            is particular evident if you are using the MemoryMessageStore. To
+            alleviate this issue you should ensure that your clients are
+            consuming all the messages from the broker.
+          </p><p>
+            You may also want to increase the memory allowance to the broker
+            though this will only delay the exception if you are publishing
+            messages faster than you are consuming. See <a class="xref" href="">???</a> for
+            details of changing the memory settings.
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.28.  Why am I getting a broker side exception when I try to publish to a queue or a topic ?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-WhyamIgettingabrokersideexceptionwhenItrytopublishtoaqueueoratopic-3F"></a>1.2.1.28. 
+            Why am I getting a broker side exception when I try to
+            publish to a queue or a topic ?
+          </h4></div></div></div>
+
+	  <p>
+            If you get a stack trace like this when you try to publish, then
+            you may have typo'd the exchange type in your queue or topic
+            declaration. Open your virtualhosts.xml and check that the
+          </p>
+            <pre class="programlisting">
+&lt;exchange&gt;amq.direct&lt;/exchange&gt;
+</pre>
+          
+            <pre class="programlisting">
+2009-01-12 15:26:27,957 ERROR [pool-11-thread-2] protocol.AMQMinaProtocolSession (AMQMinaProtocolSession.java:365) - Unexpected exception while processing frame. Closing connection. 
+java.lang.NullPointerException 
+        at org.apache.qpid.server.security.access.PrincipalPermissions.authorise(PrincipalPermissions.java:398) 
+        at org.apache.qpid.server.security.access.plugins.SimpleXML.authorise(SimpleXML.java:302) 
+        at org.apache.qpid.server.handler.QueueBindHandler.methodReceived(QueueBindHandler.java:111) 
+        at org.apache.qpid.server.handler.ServerMethodDispatcherImpl.dispatchQueueBind(ServerMethodDispatcherImpl.java:498) 
+        at org.apache.qpid.framing.amqp_8_0.QueueBindBodyImpl.execute(QueueBindBodyImpl.java:167) 
+        at org.apache.qpid.server.state.AMQStateManager.methodReceived(AMQStateManager.java:204) 
+        at org.apache.qpid.server.protocol.AMQMinaProtocolSession.methodFrameReceived(AMQMinaProtocolSession.java:295) 
+        at org.apache.qpid.framing.AMQMethodBodyImpl.handle(AMQMethodBodyImpl.java:93) 
+        at org.apache.qpid.server.protocol.AMQMinaProtocolSession.frameReceived(AMQMinaProtocolSession.java:235) 
+        at org.apache.qpid.server.protocol.AMQMinaProtocolSession.dataBlockReceived(AMQMinaProtocolSession.java:191) 
+        at org.apache.qpid.server.protocol.AMQPFastProtocolHandler.messageReceived(AMQPFastProtocolHandler.java:244) 
+        at org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.messageReceived(AbstractIoFilterChain.java:703) 
+        at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:362) 
+        at org.apache.mina.common.support.AbstractIoFilterChain.access$1200(AbstractIoFilterChain.java:54) 
+        at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:800) 
+        at org.apache.qpid.pool.PoolingFilter.messageReceived(PoolingFilter.java:371) 
+        at org.apache.mina.filter.ReferenceCountingIoFilter.messageReceived(ReferenceCountingIoFilter.java:96) 
+        at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:362) 
+        at org.apache.mina.common.support.AbstractIoFilterChain.access$1200(AbstractIoFilterChain.java:54) 
+        at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:800) 
+        at org.apache.mina.filter.codec.support.SimpleProtocolDecoderOutput.flush(SimpleProtocolDecoderOutput.java:60) 
+        at org.apache.mina.filter.codec.QpidProtocolCodecFilter.messageReceived(QpidProtocolCodecFilter.java:174) 
+        at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:362) 
+        at org.apache.mina.common.support.AbstractIoFilterChain.access$1200(AbstractIoFilterChain.java:54) 
+        at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:800) 
+        at org.apache.qpid.pool.Event$ReceivedEvent.process(Event.java:86) 
+        at org.apache.qpid.pool.Job.processAll(Job.java:110) 
+        at org.apache.qpid.pool.Job.run(Job.java:149) 
+        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) 
+        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) 
+        at java.lang.Thread.run(Thread.java:619) 
+</pre>
+</div>
+
+	  <div class="section" title="1.2.1.29.  Why is there a lot of AnonymousIoService threads"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-WhyistherealotofAnonymousIoServicethreads"></a>1.2.1.29. 
+            Why
+            is there a lot of AnonymousIoService threads
+          </h4></div></div></div>
+
+	  <p>
+            These threads are part of the thread pool used by Mina to process
+            the socket. In the future we may provide tuning guidelines but at
+            this point we have seen no performance implications from the
+            current configuration. As the threads are part of a pool they
+            should remain inactive until required.
+          </p>
+</div>
+
+	  <div class="section" title='1.2.1.30.  "unable to certify the provided SSL certificate using the current SSL trust store" when connecting the Management Console to the broker.'><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ--22unabletocertifytheprovidedSSLcertificateusingthecurrentSSLtruststore-22whenconnectingtheManagementConsoletothebroker."></a>1.2.1.30. 
+            "unable to certify the provided SSL certificate using the
+            current SSL trust store" when connecting the Management Console
+            to the broker.
+          </h4></div></div></div>
+
+	  <p>
+            You have not configured the console's SSL trust store properly,
+            see <a class="xref" href="">???</a> for
+            more details.
+          </p>
+</div>
+
+	  <div class="section" title="1.2.1.31.  Can a use TCP_KEEPALIVE or AMQP heartbeating to keep my connection open?"><div class="titlepage"><div><div><h4 class="title"><a name="QpidJavaFAQ-CanauseTCPKEEPALIVEorAMQPheartbeatingtokeepmyconnectionopen-3F"></a>1.2.1.31. 
+            Can a use TCP_KEEPALIVE or AMQP heartbeating to keep my
+            connection open?
+          </h4></div></div></div>
+
+	  <p>
+            See <a class="xref" href="">???</a>
+          </p>
+
+</div>            
+</div>
+
+	            
+
+</div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Java-General-User-Guides.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Java-General-User-Guides.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Java-Environment-Variables.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 1. General User Guides </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.3. 
+      Java Environment Variables
+    </td></tr></table></div></body></html>

Added: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-Log4j.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-Log4j.html?rev=1227030&view=auto
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-Log4j.html (added)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-Log4j.html Wed Jan  4 02:22:58 2012
@@ -0,0 +1,130 @@
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.4.  Configure Log4j CompositeRolling Appender</title><link rel="stylesheet" href="css/style.css" type="text/css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in Java)"><link rel="up" href="Qpid-Java-Broker-HowTos.html" title="Chapter 2. How Tos"><link rel="prev" href="Qpid-Java-SSL.html" title="2.3.  Configure Java Qpid to use a SSL connection."><link rel="next" href="Qpid-Java-Broker-Config-File.html" title="2.5.  Configure the Broker via config.xml"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.4. 
+      Configure Log4j CompositeRolling Appender
+    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Qpid-Java-SSL.html">Prev</a> </td><th width="60%" align="center">Chapter 2. How Tos</th><td width="20%" align="right"> <a accesskey="n" href="Qpid-Java-Broker-Config-File.html">Next</a></td></tr></table><hr></div><div class="section" title="2.4.  Configure Log4j CompositeRolling Appender"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="Qpid-Java-Log4j"></a>2.4. 
+      Configure Log4j CompositeRolling Appender
+    </h2></div></div></div>
+    <div class="section" title="2.4.1.  How to configure the CompositeRolling log4j Appender"><div class="titlepage"><div><div><h3 class="title"><a name="ConfigureLog4jCompositeRollingAppender-HowtoconfiguretheCompositeRollinglog4jAppender"></a>2.4.1. 
+            How to configure the CompositeRolling log4j Appender
+          </h3></div></div></div>
+	  <p>
+            There are several sections of our default log4j file that will
+            need your attention if you wish to fully use this Appender.
+          </p>
+
+	  <div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
+	  <p>Enable the Appender</p>
+	  <p>
+            The default log4j.xml file uses the FileAppender, swap this for
+            the ArchivingFileAppender as follows:
+          </p>
+            <pre class="programlisting">
+    &lt;!-- Log all info events to file --&gt;
+    &lt;root&gt;
+        &lt;priority value="info"/&gt;
+
+        &lt;appender-ref ref="ArchivingFileAppender"/&gt;
+    &lt;/root&gt;
+</pre>
+	    </li><li class="listitem">
+          <p>
+            Configure the Appender
+          </p>
+
+	  <p>
+            The Appender has a number of parameters that can be adjusted
+            depending on what you are trying to achieve. For clarity lets
+            take a quick look at the complete default appender:
+          </p>
+            <pre class="programlisting">
+  &lt;appender name="ArchivingFileAppender" class="org.apache.log4j.QpidCompositeRollingAppender"&gt;
+        &lt;!-- Ensure that logs allways have the dateFormat set--&gt;
+        &lt;param name="StaticLogFileName" value="false"/&gt;
+        &lt;param name="File" value="${QPID_WORK}/log/${logprefix}qpid${logsuffix}.log"/&gt;
+        &lt;param name="Append" value="false"/&gt;
+        &lt;!-- Change the direction so newer files have bigger numbers --&gt;
+        &lt;!-- So log.1 is written then log.2 etc This prevents a lot of file renames at log rollover --&gt;
+        &lt;param name="CountDirection" value="1"/&gt;
+        &lt;!-- Use default 10MB --&gt;
+        &lt;!--param name="MaxFileSize" value="100000"/--&gt;
+        &lt;param name="DatePattern" value="'.'yyyy-MM-dd-HH-mm"/&gt;
+        &lt;!-- Unlimited number of backups --&gt;
+        &lt;param name="MaxSizeRollBackups" value="-1"/&gt;
+        &lt;!-- Compress(gzip) the backup files--&gt;
+        &lt;param name="CompressBackupFiles" value="true"/&gt;
+        &lt;!-- Compress the backup files using a second thread --&gt;
+        &lt;param name="CompressAsync" value="true"/&gt;
+        &lt;!-- Start at zero numbered files--&gt;
+        &lt;param name="ZeroBased" value="true"/&gt;
+        &lt;!-- Backup Location --&gt;
+        &lt;param name="backupFilesToPath" value="${QPID_WORK}/backup/log"/&gt;
+
+        &lt;layout class="org.apache.log4j.PatternLayout"&gt;
+            &lt;param name="ConversionPattern" value="%d %-5p [%t] %C{2} (%F:%L) - %m%n"/&gt;
+        &lt;/layout&gt;
+    &lt;/appender&gt;
+</pre>
+          <p>
+            The appender configuration has three groups of parameter
+            configuration.
+          </p><p>
+            The first group is for configuration of the file name. The
+            default is to write a log file to QPID_WORK/log/qpid.log
+            (Remembering you can use the logprefix and logsuffix values to
+            modify the file name, see Property Config).
+          </p>
+            <pre class="programlisting">
+        &lt;!-- Ensure that logs always have the dateFormat set--&gt;
+        &lt;param name="StaticLogFileName" value="false"/&gt;
+        &lt;param name="File" value="${QPID_WORK}/log/${logprefix}qpid${logsuffix}.log"/&gt;
+        &lt;param name="Append" value="false"/&gt;
+</pre>
+          <p>
+            The second section allows the specification of a Maximum File
+            Size and a DatePattern that will be used to move on to the next
+            file.
+          </p><p>
+            When MaxFileSize is reached a new log file will be created
+            The DataPattern is used to decide when to create a new log file,
+            so here a new file will be created for every minute and every
+            10Meg of data. So if 15MB of data is made every minute then there
+            will be two log files created each minute. One at the start of
+            the minute and a second when the file hit 10MB. When the next
+            minute arrives a new file will be made even though it only has
+            5MB of content. For a production system it would be expected to
+            be changed to something like 'yyyy-MM-dd' which would make a new
+            log file each day and keep the files to a max of 10MB.
+          </p><p>
+            The final MaxSizeRollBackups allows you to limit the amount of
+            disk you are using by only keeping the last n backups.
+          </p>
+            <pre class="programlisting">
+        &lt;!-- Change the direction so newer files have bigger numbers --&gt;
+        &lt;!-- So log.1 is written then log.2 etc This prevents a lot of file renames at log rollover --&gt;
+        &lt;param name="CountDirection" value="1"/&gt;
+        &lt;!-- Use default 10MB --&gt;
+        &lt;!--param name="MaxFileSize" value="100000"/--&gt;
+        &lt;param name="DatePattern" value="'.'yyyy-MM-dd-HH-mm"/&gt;
+        &lt;!-- Unlimited number of backups --&gt;
+        &lt;param name="MaxSizeRollBackups" value="-1"/&gt;
+</pre>
+          <p>
+            The final section allows the old log files to be compressed and
+            copied to a new location.
+          </p>
+            <pre class="programlisting">
+        &lt;!-- Compress(gzip) the backup files--&gt;
+        &lt;param name="CompressBackupFiles" value="true"/&gt;
+        &lt;!-- Compress the backup files using a second thread --&gt;
+        &lt;param name="CompressAsync" value="true"/&gt;
+        &lt;!-- Start at zero numbered files--&gt;
+        &lt;param name="ZeroBased" value="true"/&gt;
+        &lt;!-- Backup Location --&gt;
+        &lt;param name="backupFilesToPath" value="${QPID_WORK}/backup/log"/&gt;
+</pre>
+</li></ol></div>
+</div>
+</div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Qpid-Java-SSL.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Qpid-Java-Broker-HowTos.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Qpid-Java-Broker-Config-File.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.3. 
+      Configure Java Qpid to use a SSL connection.
+     </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.5. 
+      Configure the Broker via config.xml
+    </td></tr></table></div></body></html>

Added: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-SSL.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-SSL.html?rev=1227030&view=auto
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-SSL.html (added)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-SSL.html Wed Jan  4 02:22:58 2012
@@ -0,0 +1,67 @@
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.3.  Configure Java Qpid to use a SSL connection.</title><link rel="stylesheet" href="css/style.css" type="text/css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in Java)"><link rel="up" href="Qpid-Java-Broker-HowTos.html" title="Chapter 2. How Tos"><link rel="prev" href="Configuring-ACLS.html" title="2.2.  Configuring ACLs"><link rel="next" href="Qpid-Java-Log4j.html" title="2.4.  Configure Log4j CompositeRolling Appender"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.3. 
+      Configure Java Qpid to use a SSL connection.
+    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Configuring-ACLS.html">Prev</a> </td><th width="60%" align="center">Chapter 2. How Tos</th><td width="20%" align="right"> <a accesskey="n" href="Qpid-Java-Log4j.html">Next</a></td></tr></table><hr></div><div class="section" title="2.3.  Configure Java Qpid to use a SSL connection."><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="Qpid-Java-SSL"></a>2.3. 
+      Configure Java Qpid to use a SSL connection.
+    </h2></div></div></div>
+
+    <div class="section" title="2.3.1.  Using SSL connection with Qpid Java."><div class="titlepage"><div><div><h3 class="title"><a name="ConfigureJavaQpidtouseaSSLconnection.-UsingSSLconnectionwithQpidJava."></a>2.3.1. 
+            Using SSL connection with Qpid Java.
+          </h3></div></div></div>
+	  <p>
+            This section will show how to use SSL to enable secure
+            connections between a Java client and broker.
+          </p>
+</div>
+    <div class="section" title="2.3.2.  Setup"><div class="titlepage"><div><div><h3 class="title"><a name="ConfigureJavaQpidtouseaSSLconnection.-Setup"></a>2.3.2. 
+            Setup
+          </h3></div></div></div>
+    <div class="section" title="2.3.2.1.  Broker Setup"><div class="titlepage"><div><div><h4 class="title"><a name="ConfigureJavaQpidtouseaSSLconnection.-BrokerSetup"></a>2.3.2.1. 
+            Broker
+            Setup
+          </h4></div></div></div>
+	  <p>
+            The broker configuration file (config.xml) needs to be updated to
+            include the SSL keystore location details.
+          </p>
+                        
+<pre class="programlisting">
+&lt;!-- Additions required to Connector Section --&gt;
+
+&lt;ssl&gt;
+    &lt;enabled&gt;true&lt;/enabled&gt;
+    &lt;sslOnly&gt;true&lt;/sslOnly&gt;
+    &lt;keyStorePath&gt;/path/to/keystore.ks&lt;/keyStorePath&gt;
+    &lt;keyStorePassword&gt;keystorepass&lt;/keyStorePassword&gt;
+&lt;/ssl&gt;
+</pre>
+            
+          <p>
+            The sslOnly option is included here for completeness however this
+            will disable the unencrypted port and leave only the SSL port
+            listening for connections.
+          </p>
+</div>
+    <div class="section" title="2.3.2.2.  Client Setup"><div class="titlepage"><div><div><h4 class="title"><a name="ConfigureJavaQpidtouseaSSLconnection.-ClientSetup"></a>2.3.2.2. 
+            Client
+            Setup
+          </h4></div></div></div>
+	  <p>
+            The best place to start looking is class
+            <span class="emphasis"><em>SSLConfiguration</em></span> this is provided to the connection
+            during creation however there is currently no example that
+            demonstrates its use.
+          </p>
+</div>
+</div>
+
+    <div class="section" title="2.3.3.  Performing the connection."><div class="titlepage"><div><div><h3 class="title"><a name="ConfigureJavaQpidtouseaSSLconnection.-Performingtheconnection."></a>2.3.3. 
+            Performing
+            the connection.
+          </h3></div></div></div>
+	  <p></p>
+    </div>
+</div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Configuring-ACLS.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Qpid-Java-Broker-HowTos.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Qpid-Java-Log4j.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.2. 
+      Configuring ACLs
+   </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.4. 
+      Configure Log4j CompositeRolling Appender
+    </td></tr></table></div></body></html>

Added: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Troubleshooting-Guide.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Troubleshooting-Guide.html?rev=1227030&view=auto
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Troubleshooting-Guide.html (added)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Troubleshooting-Guide.html Wed Jan  4 02:22:58 2012
@@ -0,0 +1,138 @@
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.4.  Qpid Troubleshooting Guide</title><link rel="stylesheet" href="css/style.css" type="text/css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in Java)"><link rel="up" href="Java-General-User-Guides.html" title="Chapter 1. General User Guides"><link rel="prev" href="Java-Environment-Variables.html" title="1.3.  Java Environment Variables"><link rel="next" href="Java-Broker-Configuration-Guide.html" title="1.5. Broker Configuration Guide"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.4. 
+      Qpid Troubleshooting Guide
+    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Java-Environment-Variables.html">Prev</a> </td><th width="60%" align="center">Chapter 1. General User Guides</th><td width="20%" align="right"> <a accesskey="n" href="Java-Broker-Configuration-Guide.html">Next</a></td></tr></table><hr></div><div class="section" title="1.4.  Qpid Troubleshooting Guide"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="Qpid-Troubleshooting-Guide"></a>1.4. 
+      Qpid Troubleshooting Guide
+    </h2></div></div></div>
+
+  
+
+          <div class="section" title="1.4.1.  I'm getting a java.lang.UnsupportedClassVersionError when I try to start the broker. What does this mean ?"><div class="titlepage"><div><div><h3 class="title"><a name="QpidTroubleshootingGuide-I-27mgettingajava.lang.UnsupportedClassVersionErrorwhenItrytostartthebroker.Whatdoesthismean-3F"></a>1.4.1. 
+            I'm getting a java.lang.UnsupportedClassVersionError when I
+            try to start the broker. What does this mean ?
+          </h3></div></div></div>
+
+	  <p>
+            The QPID broker requires JDK 1.5 or later. If you're seeing this
+            exception you don't have that version in your path. Set JAVA_HOME
+            to the correct version and ensure the bin directory is on your
+            path.
+          </p><p>
+            java.lang.UnsupportedClassVersionError:
+            org/apache/qpid/server/Main (Unsupported major.minor version
+            49.0)
+            at
+            java.lang.ClassLoader.defineClass(Ljava.lang.String;[BIILjava.security.ProtectionDomain;)Ljava.lang.Class;(Unknown
+            Source)
+            at
+            java.security.SecureClassLoader.defineClass(Ljava.lang.String;[BIILjava.security.CodeSource;)Ljava.lang.Class;(SecureClassLoader.java:123)
+
+            at
+            java.net.URLClassLoader.defineClass(Ljava.lang.String;Lsun.misc.Resource;)Ljava.lang.Class;(URLClassLoader.java:251)
+
+            at
+            java.net.URLClassLoader.access$100(Ljava.net.URLClassLoader;Ljava.lang.String;Lsun.misc.Resource;)Ljava.lang.Class;(URLClassLoader.java:55)
+
+            at java.net.URLClassLoader$1.run()Ljava.lang.Object;
+            (URLClassLoader.java:194)
+            at
+            jrockit.vm.AccessController.do_privileged_exc(Ljava.security.PrivilegedExceptionAction;Ljava.security.AccessControlContext;I)Ljava.lang.Object;(Unknown
+            Source)
+            at
+            jrockit.vm.AccessController.doPrivileged(Ljava.security.PrivilegedExceptionAction;Ljava.security.AccessControlContext;)Ljava.lang.Object;(Unknown
+            Source)
+            at
+            java.net.URLClassLoader.findClass(Ljava.lang.String;)Ljava.lang.Class;(URLClassLoader.java:187)
+
+            at
+            java.lang.ClassLoader.loadClass(Ljava.lang.String;Z)Ljava.lang.Class;
+            (Unknown Source)
+            at
+            sun.misc.Launcher$AppClassLoader.loadClass(Ljava.lang.String;Z)Ljava.lang.Class;(Launcher.java:274)
+
+            at
+            java.lang.ClassLoader.loadClass(Ljava.lang.String;)Ljava.lang.Class;
+
+            (Unknown Source)
+            at
+            java.lang.ClassLoader.loadClassFromNative(II)Ljava.lang.Class;
+
+            (Unknown Source)
+          </p>
+
+</div>
+
+	  <div class="section" title="1.4.2.  I'm having a problem binding to the required host:port at broker startup ?"><div class="titlepage"><div><div><h3 class="title"><a name="QpidTroubleshootingGuide-I-27mhavingaproblembindingtotherequiredhost-3Aportatbrokerstartup-3F"></a>1.4.2. 
+            I'm having a problem binding to the required host:port at
+            broker startup ?
+          </h3></div></div></div>
+	  <p>
+            This error probably indicates that another process is using the
+            port you the broker is trying to listen on. If you haven't
+            amended the default configuration this will be 5672. To check
+            what process is using the port you can use 'netstat -an |grep
+            5672'.
+          </p><p>
+            To change the port your broker uses, either edit the config.xml
+            you are using. You can specify an alternative config.xml from the
+            one provided in /etc by using the -c flag i.e. qpid-server -c
+            &lt;my config file path&gt;.
+          </p><p>
+            You can also amend the port more simply using the -p option to
+            qpid-server i.e. qpid-server -p &lt;my port number'
+          </p>
+</div>
+
+	  <div class="section" title="1.4.3.  I'm having problems with my classpath. How can I ensure that my classpath is ok ?"><div class="titlepage"><div><div><h3 class="title"><a name="QpidTroubleshootingGuide-I-27mhavingproblemswithmyclasspath.HowcanIensurethatmyclasspathisok-3F"></a>1.4.3. 
+            I'm having problems with my classpath. How can I ensure that
+            my classpath is ok ?
+          </h3></div></div></div>
+	  <p>
+            When you are running the broker the classpath is taken care of
+            for you, via the manifest entries in the launch jars that the
+            qpid-server configuration file adds to the classpath.
+          </p><p>
+            However, if you are running your own client code and experiencing
+            classspath errors you need to ensure that the client-launch.jar
+            from the installed Qpid lib directory is on your classpath. The
+            manifest for this jar includes the common-launch.jar, and thus
+            all the code you need to run a client application.
+          </p>
+	  </div>
+
+	  <div class="section" title="1.4.4.  I can't get the broker to start. How can I diagnose the problem ?"><div class="titlepage"><div><div><h3 class="title"><a name="QpidTroubleshootingGuide-Ican-27tgetthebrokertostart.HowcanIdiagnosetheproblem-3F"></a>1.4.4. 
+            I can't get the broker to start. How can I diagnose the
+            problem ?
+          </h3></div></div></div>
+	  <p>
+            Firstly have a look at the broker log file - either on stdout or
+            in $QPID_WORK/log/qpid.log or in $HOME/log/qpid.log if you
+            haven't set QPID_WORK.
+          </p><p>
+            You should see the problem logged in here via log4j and a stack
+            trace. Have a look at the other entries on this page for common
+            problems. If the log file includes a line like:
+          </p><p>
+            "2006-10-13 09:58:14,672 INFO [main] server.Main (Main.java:343)
+            - Qpid.AMQP listening on non-SSL address 0.0.0.0/0.0.0.0:5672"
+          </p><p>
+            ... then you know the broker started up. If not, then it didn't.
+          </p>
+</div>
+
+	  <div class="section" title="1.4.5.  When I try to send messages to a queue I'm getting a error as the queue does not exist. What can I do ?"><div class="titlepage"><div><div><h3 class="title"><a name="QpidTroubleshootingGuide-WhenItrytosendmessagestoaqueueI-27mgettingaerrorasthequeuedoesnotexist.WhatcanIdo-3F"></a>1.4.5. 
+            When I try to send messages to a queue I'm getting a error as
+            the queue does not exist. What can I do ?
+          </h3></div></div></div>
+	  <p>
+            In Qpid queues need a consumer before they really exist, unless
+            you have used the virtualhosts.xml file to specify queues which
+            should always be created at broker startup. If you don't want to
+            use this config, then simply ensure that you consume first from
+            queue before staring to publish to it. See the entry on our
+            <a class="xref" href="">???</a> for more details of using the virtualhosts.xml route.
+          </p>
+</div>
+
+</div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Java-Environment-Variables.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Java-General-User-Guides.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Java-Broker-Configuration-Guide.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.3. 
+      Java Environment Variables
+     </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.5. Broker Configuration Guide </td></tr></table></div></body></html>

Added: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/QpidJavaBroker-ManagementTools.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/QpidJavaBroker-ManagementTools.html?rev=1227030&view=auto
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/QpidJavaBroker-ManagementTools.html (added)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/QpidJavaBroker-ManagementTools.html Wed Jan  4 02:22:58 2012
@@ -0,0 +1,141 @@
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 4. Management Tools</title><link rel="stylesheet" href="css/style.css" type="text/css"><meta name="generator" content="DocBook XSL-NS Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in Java)"><link rel="up" href="index.html" title="AMQP Messaging Broker (Implemented in Java)"><link rel="prev" href="Qpid-JMX-Management-Console.html" title="Chapter 3.  Qpid JMX Management Console"><link rel="next" href="Qpid-Java-Broker-Management-CLI.html" title="4.2.  Qpid Java Broker Management CLI"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 4. Management Tools</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Qpid-JMX-Management-Console.html">Prev</a> </td><th wid
 th="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="Qpid-Java-Broker-Management-CLI.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 4. Management Tools"><div class="titlepage"><div><div><h2 class="title"><a name="QpidJavaBroker-ManagementTools"></a>Chapter 4. Management Tools</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="QpidJavaBroker-ManagementTools.html#id1333341">4.1. 
+      MessageStore Tool
+    </a></span></dt><dd><dl><dt><span class="section"><a href="QpidJavaBroker-ManagementTools.html#MessageStoreTool-MessageStoreTool">4.1.1. 
+            MessageStore Tool
+          </a></span></dt></dl></dd><dt><span class="section"><a href="Qpid-Java-Broker-Management-CLI.html">4.2. 
+      Qpid Java Broker Management CLI
+    </a></span></dt><dd><dl><dt><span class="section"><a href="Qpid-Java-Broker-Management-CLI.html#QpidJavaBrokerManagementCLI-HowtobuildApacheQpidCLI">4.2.1. 
+            How to
+            build Apache Qpid CLI
+          </a></span></dt></dl></dd></dl></div>
+
+        <div class="section" title="4.1.  MessageStore Tool"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1333341"></a>4.1. 
+      MessageStore Tool
+    </h2></div></div></div><div class="section" title="4.1.1.  MessageStore Tool"><div class="titlepage"><div><div><h3 class="title"><a name="MessageStoreTool-MessageStoreTool"></a>4.1.1. 
+            MessageStore Tool
+          </h3></div></div></div>
+
+	 <p>
+            We have a number of implementations of the Qpid MessageStore
+            interface. This tool allows the interrogation of these stores
+            while the broker is offline.
+          </p>
+
+	  <div class="section" title="4.1.1.1.  MessageStore Implementations"><div class="titlepage"><div><div><h4 class="title"><a name="MessageStoreTool-MessageStoreImplementations"></a>4.1.1.1. 
+            MessageStore
+            Implementations
+          </h4></div></div></div>
+
+	 <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
+              <a class="xref" href="">???</a>
+            </p></li><li class="listitem"><p>
+              <a class="xref" href="">???</a>
+            </p></li><li class="listitem"><p>
+              <a class="xref" href="">???</a>
+            </p></li></ul></div>
+</div>
+
+	  <div class="section" title="4.1.1.2.  Introduction"><div class="titlepage"><div><div><h4 class="title"><a name="MessageStoreTool-Introduction"></a>4.1.1.2. 
+            Introduction
+          </h4></div></div></div>
+
+	 <p>
+            Each of the MessageStore implementations provide different back
+            end storage for their messages and so would need a different tool
+            to be able to interrogate their contents at the back end.
+          </p><p>
+            What this tool does is to utilise the Java broker code base to
+            access the contents of the storage providing the user with a
+            consistent means to inspect the storage contents in broker
+            memory. The tool allows the current messages in the store to be
+            inspected and copied/moved between queues. The tool uses the
+            message instance in memory for all its access paths, but changes
+            made will be reflected in the physical store (if one exists).
+          </p>
+</div>
+
+	  <div class="section" title="4.1.1.3.  Usage"><div class="titlepage"><div><div><h4 class="title"><a name="MessageStoreTool-Usage"></a>4.1.1.3. 
+            Usage
+          </h4></div></div></div>
+
+	 <p>
+            The tools-distribution currently includes a unix shell command
+            'msTool.sh' this script will launch the java tool.
+          </p><p>
+            The tool loads $QPID_HOME/etc/config.xml by default. If an
+            alternative broker configuration is required this should be
+            provided on the command line as would be done for the broker.
+          </p>
+            <pre class="programlisting">
+msTool.sh -c &lt;path to different config.xml&gt;
+</pre>
+          <p>
+            On startup the user is present with a command prompt
+          </p>
+            <pre class="programlisting">
+$ msTool.sh
+MessageStoreTool - for examining Persistent Qpid Broker MessageStore instances
+bdb$ 
+</pre>
+</div>
+
+          <div class="section" title="4.1.1.4.  Available Commands"><div class="titlepage"><div><div><h4 class="title"><a name="MessageStoreTool-AvailableCommands"></a>4.1.1.4. 
+            Available
+            Commands
+          </h4></div></div></div>
+
+	 <p>
+            The available commands in the tool can be seen through the use of
+            the 'help' command.
+          </p>
+            <pre class="programlisting">
+bdb$ help
++----------------------------------------------------------------+
+|                       Available Commands                       |
++----------------------------------------------------------------+
+| Command | Description                                          |
++----------------------------------------------------------------+
+| quit    | Quit the tool.                                       |
+| list    | list available items.                                |
+| dump    | Dump selected message content. Default: show=content |
+| load    | Loads specified broker configuration file.           |
+| clear   | Clears any selection.                                |
+| show    | Shows the messages headers.                          |
+| select  | Perform a selection.                                 |
+| help    | Provides detailed help on commands.                  |
++----------------------------------------------------------------+
+bdb$
+</pre>
+          <p>
+            A brief description is displayed and further usage information is
+            shown with 'help &lt;command&gt;'
+          </p>
+            <pre class="programlisting">
+bdb$ help list
+list availble items.
+Usage:list queues [&lt;exchange&gt;] | exchanges | bindings [&lt;exchange&gt;] | all
+bdb$
+</pre>
+</div>
+
+
+          <div class="section" title="4.1.1.5.  Future Work"><div class="titlepage"><div><div><h4 class="title"><a name="MessageStoreTool-FutureWork"></a>4.1.1.5. 
+            Future Work
+          </h4></div></div></div>
+
+	 <p>
+            Currently the tool only works whilst the broker is offline i.e.
+            it is up, but not accepting AMQP connections. This requires a
+            stop/start of the broker. If this functionality was incorporated
+            into the broker then a telnet functionality could be provided
+            allowing online management.
+          </p>
+</div>
+</div>
+</div>
+        
+</div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Qpid-JMX-Management-Console.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="Qpid-Java-Broker-Management-CLI.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 3. 
+    Qpid JMX Management Console
+   </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4.2. 
+      Qpid Java Broker Management CLI
+    </td></tr></table></div></body></html>

Added: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/css/style.css
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/css/style.css?rev=1227030&view=auto
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/css/style.css (added)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/css/style.css Wed Jan  4 02:22:58 2012
@@ -0,0 +1,129 @@
+/*
+ *
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ * 
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ * 
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ *
+ */
+ul {
+    list-style-type:square;
+}
+
+th { 
+    font-weight: bold;
+}
+
+.navfooter td { 
+    font-size:10pt;
+}
+
+.navheader td { 
+    font-size:10pt;
+}
+
+body {
+    width:950px;
+    margin-left:100px;
+    margin-top:40px;
+
+    background:#FFFFFF;
+    font-family:"Verdana", sans-serif;
+    font-size:10pt;
+}
+
+body a {
+    color:#000000;
+}
+
+
+div.book {
+    margin-left:10pt;
+    margin-right:10pt;
+}
+
+div.preface {
+    margin-left:10pt;
+    margin-right:10pt;
+}
+
+div.chapter {
+    margin-left:10pt;
+    margin-right:10pt;
+}
+
+div.section {
+    margin-left:10pt;
+    margin-right:10pt;
+}
+
+div.titlepage {
+    margin-left:-10pt;
+    margin-right:-10pt;
+}
+
+.calloutlist td {
+    font-size:10pt;
+}
+
+.table-contents table {
+    border-spacing: 0px;
+}
+
+.table-contents td {
+    font-size:10pt;
+    padding-left:6px;
+    padding-right:6px;
+}
+
+.chapter h2.title {
+    font-size:20pt;
+    color:#0c3b82;
+}
+
+.chapter .section h2.title {
+    font-size:18pt;
+    color:#0c3b82;
+}
+
+.section h2.title {
+    font-size:16pt;
+    color:#0c3b82;
+}
+
+.section h3.title {
+    font-size:14pt;
+    color:#0c3b82;
+}
+
+.section h4.title {
+    font-size:12pt;
+    color:#0c3b82;
+}
+
+.section h5.title {
+    font-size:12pt;
+    color:#0c3b82;
+}
+
+.section h6.title {
+    font-size:12pt;
+    color:#0c3b82;
+}
+
+.toc a {
+    font-size:9pt;
+}
+



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:commits-subscribe@qpid.apache.org


Mime
View raw message