[jboss-cvs] JBoss Messaging SVN: r7014 - in trunk: src/bin and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue May 26 07:02:22 EDT 2009
Author: timfox
Date: 2009-05-26 07:02:22 -0400 (Tue, 26 May 2009)
New Revision: 7014
Modified:
trunk/docs/user-manual/en/jar-dependencies.xml
trunk/docs/user-manual/en/persistence.xml
trunk/docs/user-manual/en/using-server.xml
trunk/src/bin/run.sh
Log:
LD_LIBRARY_PATH
Modified: trunk/docs/user-manual/en/jar-dependencies.xml
===================================================================
--- trunk/docs/user-manual/en/jar-dependencies.xml 2009-05-26 10:14:12 UTC (rev 7013)
+++ trunk/docs/user-manual/en/jar-dependencies.xml 2009-05-26 11:02:22 UTC (rev 7014)
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="jar-dependencies">
- <title>Jar Dependencies</title>
+ <title>Jar Dependencies and Client Classpath</title>
<para>JBoss Messaging was designed to have as few dependencies on external jars as possible. In
fact, JBoss Messaging core has zero dependencies on any jars other than the standard JDK
classes!</para>
@@ -168,4 +168,26 @@
</tgroup>
</table>
</section>
+ <section>
+ <title>Client Classpath</title>
+ <para>In this section we explain what jars you need on the client classpath, this depends on
+ how you're using JBoss Messaging</para>
+ <para>!!!!!!!!!!! TODO - clebert please complete this</para>
+ <itemizedlist>
+ <listitem>
+ <para>Core. If you're just using the JBoss Messaging core client API, you just need
+ xyz</para>
+ </listitem>
+ <listitem>
+ <para>JMS. If you're using JMS, you need XYZ. If you're using JNDI with JMS you need
+ XYZ</para>
+ </listitem>
+ <listitem>
+ <para>If you're using netty you need XYZ</para>
+ </listitem>
+ <listitem>
+ <para>etc</para>
+ </listitem>
+ </itemizedlist>
+ </section>
</chapter>
Modified: trunk/docs/user-manual/en/persistence.xml
===================================================================
--- trunk/docs/user-manual/en/persistence.xml 2009-05-26 10:14:12 UTC (rev 7013)
+++ trunk/docs/user-manual/en/persistence.xml 2009-05-26 11:02:22 UTC (rev 7014)
@@ -40,7 +40,7 @@
JDK.</para>
</listitem>
<listitem>
- <para>Linux Asynchronous IO (<ulink url="http://lse.sourceforge.net/io/aio.html"
+ <para id="aio-journal">Linux Asynchronous IO (<ulink url="http://lse.sourceforge.net/io/aio.html"
>AIO</ulink>).</para>
<para>The second implementation uses a thin native code wrapper to talk to the Linux
asynchronous IO library (AIO). In a highly concurrent environment, AIO can provide
Modified: trunk/docs/user-manual/en/using-server.xml
===================================================================
--- trunk/docs/user-manual/en/using-server.xml 2009-05-26 10:14:12 UTC (rev 7013)
+++ trunk/docs/user-manual/en/using-server.xml 2009-05-26 11:02:22 UTC (rev 7014)
@@ -40,7 +40,7 @@
are the place to do it.</para>
</section>
<section>
- <title>Server runtime</title>
+ <title>Server classpath</title>
<para>JBoss Messaging looks for its configuration files on the Java classpath.</para>
<para>The scripts <literal>run.sh</literal> and <literal>run.bat</literal> specify the
classpath when calling Java to run the server.</para>
@@ -70,13 +70,22 @@
when starting up.</para>
</section>
<section>
+ <title>LD_LIBRARY_PATH</title>
+ <para>If you're using the <xref linkend="aio-journal">Asynchronous IO Journal</xref> on
+ Linux, then the environment variable <literal>LD_LIBRARY_PATH</literal> needs to be set
+ to the path that contains the shared library file that contains the native code for the
+ AIO abstraction layer. This is done automatically in the <literal>run.sh</literal>
+ script.</para>
+ </section>
+ <section>
<title>System properties</title>
<para>JBoss Messaging also takes a couple of Java system properties on the command line for
configuring logging properties</para>
<para>JBoss Messaging uses JDK logging to minimise dependencies on other logging systems.
JDK logging can then be configured to delegate to some other framework, e.g. log4j if
that's what you prefer.</para>
- <para>For more information on configuring logging, please see <xref linkend="logging" />.</para>
+ <para>For more information on configuring logging, please see <xref linkend="logging"
+ />.</para>
</section>
<section id="using-server.configuration">
<title>Configuration files</title>
@@ -90,13 +99,13 @@
dependencies to enforce between them. Remember that JBoss Messaging is just a
set of POJOs. In the stand-alone server, it's the JBoss Microcontainer which
instantiates these POJOs and enforces dependencies between them and other beans.
- Please see <xref linkend="usingserver.mainconfig"/> for more
- information on this file.</para>
+ Please see <xref linkend="usingserver.mainconfig"/> for more information on this
+ file.</para>
</listitem>
<listitem>
<para><literal>jbm-configuration.xml</literal>. This is the main JBoss Messaging
configuration file. All the parameters in this file are described in <xref
- linkend="configuration-index" />.</para>
+ linkend="configuration-index"/>.</para>
</listitem>
<listitem>
<para><literal>jbm-queues.xml</literal>. This file contains pre-defined queues,
@@ -121,8 +130,8 @@
server side JMS service which mainly deploys JMS Queues, Topics and
ConnectionFactorys from this file into JNDI. If you're not using JMS, or you
don't need to deploy JMS objects on the server side, then you don't need this
- file. For more information on using JMS, please see <xref
- linkend="using-jms" />.</para>
+ file. For more information on using JMS, please see <xref linkend="using-jms"
+ />.</para>
</listitem>
<listitem>
<para><literal>logging.properties</literal> This is used to configure the logging
@@ -139,9 +148,9 @@
>jbm-configuration.xml</literal> configuration when set to false mans that the
other configuration files are not loaded. This is true by default.</para>
</note>
- <para>It is also possible to use system property substitution in all the configuration files. by
- replacing a value with the name of a system property. Here is an example of this with a
- connector configuration:</para>
+ <para>It is also possible to use system property substitution in all the configuration
+ files. by replacing a value with the name of a system property. Here is an example of
+ this with a connector configuration:</para>
<programlisting><connector name="netty">
<factory-class>org.jboss.messaging.integration.transports.netty.NettyConnectorFactory</factory-class>
<param key="jbm.remoting.netty.host" value="${jbm.remoting.netty.host:localhost}" type="String"/>
@@ -174,19 +183,19 @@
<!-- JNDI server. Disable this if you don't want JNDI -->
<bean name="JNDIServer" class="org.jnp.server.Main">
-<property name="namingInfo">
-<inject bean="Naming"/>
-</property>
-<property name="port">1099</property>
-<property name="bindAddress">localhost</property>
-<property name="rmiPort">1098</property>
-<property name="rmiBindAddress">localhost</property>
+ <property name="namingInfo">
+ <inject bean="Naming"/>
+ </property>
+ <property name="port">1099</property>
+ <property name="bindAddress">localhost</property>
+ <property name="rmiPort">1098</property>
+ <property name="rmiBindAddress">localhost</property>
</bean>
<!-- MBean server -->
<bean name="MBeanServer" class="javax.management.MBeanServer">
-<constructor factoryClass="java.lang.management.ManagementFactory"
-factoryMethod="getPlatformMBeanServer"/>
+ <constructor factoryClass="java.lang.management.ManagementFactory"
+ factoryMethod="getPlatformMBeanServer"/>
</bean>
<!-- The core configuration -->
@@ -196,35 +205,35 @@
<!-- The security manager -->
<bean name="JBMSecurityManager"
class="org.jboss.messaging.core.security.impl.JBMSecurityManagerImpl">
-<start ignored="true"/>
-<stop ignored="true"/>
+ <start ignored="true"/>
+ <stop ignored="true"/>
</bean>
<!-- The core server -->
<bean name="MessagingServer" class="org.jboss.messaging.core.server.impl.MessagingServerImpl">
-<start ignored="true"/>
-<stop ignored="true"/>
-<constructor>
-<parameter>
-<inject bean="Configuration"/>
-</parameter>
-<parameter>
-<inject bean="MBeanServer"/>
-</parameter>
-<parameter>
-<inject bean="JBMSecurityManager"/>
-</parameter>
-</constructor>
+ <start ignored="true"/>
+ <stop ignored="true"/>
+ <constructor>
+ <parameter>
+ <inject bean="Configuration"/>
+ </parameter>
+ <parameter>
+ <inject bean="MBeanServer"/>
+ </parameter>
+ <parameter>
+ <inject bean="JBMSecurityManager"/>
+ </parameter>
+ </constructor>
</bean>
<!-- The JMS server -->
<bean name="JMSServerManager"
class="org.jboss.messaging.jms.server.impl.JMSServerManagerImpl">
-<constructor>
-<parameter>
-<inject bean="MessagingServer"/>
-</parameter>
-</constructor>
+ <constructor>
+ <parameter>
+ <inject bean="MessagingServer"/>
+ </parameter>
+ </constructor>
</bean>
</deployment></programlisting>
@@ -259,7 +268,8 @@
<literal>jbm-users.xml</literal> file on disk. However it can be replaced by
a JAAS security manager, or when running inside JBoss Application Server it can
be configured to use the JBoss AS security manager for tight integration with
- JBoss AS security.</para>
+ JBoss AS security. If you've disabled security altogether you can remove this
+ too.</para>
</listitem>
<listitem>
<para>MessagingServer</para>
@@ -271,8 +281,8 @@
instances from <literal>jbm-jms.xml</literal> files on the disk. It also
provides a simple management API for manipulating JMS Objects. On the whole it
just translates and delegates its work to the core server. If you don't need to
- deploy JMS Queues, Topics and ConnectionFactorys from server side configuration and
- don't require the JMS management interface this can be disabled.</para>
+ deploy JMS Queues, Topics and ConnectionFactorys from server side configuration
+ and don't require the JMS management interface this can be disabled.</para>
</listitem>
</itemizedlist>
</section>
Modified: trunk/src/bin/run.sh
===================================================================
--- trunk/src/bin/run.sh 2009-05-26 10:14:12 UTC (rev 7013)
+++ trunk/src/bin/run.sh 2009-05-26 11:02:22 UTC (rev 7014)
@@ -5,6 +5,7 @@
if [ a"$1" = a ]; then CONFIG_DIR=$JBM_HOME/config/stand-alone/non-clustered; else CONFIG_DIR="$1"; fi
if [ a"$2" = a ]; then FILENAME=jbm-jboss-beans.xml; else FILENAME="$2"; fi
+export LD_LIBRARY_PATH=$JBM_HOME/bin
export CLASSPATH=$CONFIG_DIR:$JBM_HOME/schemas/
export JVM_ARGS="-XX:+UseParallelGC -XX:+AggressiveOpts -XX:+UseFastAccessorMethods -Xms512M -Xmx1024M -Djava.util.logging.config.file=$CONFIG_DIR/logging.properties -Dorg.jboss.logging.Logger.pluginClass=org.jboss.messaging.integration.logging.JBMLoggerPlugin -Djava.library.path=."
#export JVM_ARGS="-Xmx512M -Djava.util.logging.config.file=$CONFIG_DIR/logging.properties -Dorg.jboss.logging.Logger.pluginClass=org.jboss.messaging.integration.logging.JBMLoggerPlugin -Djava.library.path=. -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"
More information about the jboss-cvs-commits
mailing list