User: oleg
Date: 00/10/17 08:41:06
Modified: manual adv_config.html
Log:
Now it is possible to have many FileLogging entries in jboss.conf with different
source filters
Revision Changes Path
1.11 +34 -30 jbossweb/manual/adv_config.html
Index: adv_config.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/adv_config.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- adv_config.html 2000/10/11 23:42:08 1.10
+++ adv_config.html 2000/10/17 15:41:06 1.11
@@ -223,7 +223,7 @@
If set to <strong>false</strong>, then the pool will return
null immediately (and the client may retry).<br>
<i>Note: If you set blocking to false, your client must be
- prepared to handle null results!</i></td>
+ prepared to handle null results!</i></td>
<td>true</td>
</tr>
<tr>
@@ -242,10 +242,10 @@
suddenly without closing database connections gracefully,
or queries that take an unexpectedly long time to run. This
is not generally useful in an EJB environment, though it may
- be for stateful session beans that keep a DB connection as
- part of their state. This is in contrast to the idle
- timeout, which closes connection that have been idle in the
- pool.</td>
+ be for stateful session beans that keep a DB connection as
+ part of their state. This is in contrast to the idle
+ timeout, which closes connection that have been idle in the
+ pool.</td>
<td>false</td>
</tr>
<tr>
@@ -266,37 +266,37 @@
<td>Whether the pool should close idle connections. This
prevents the pool from keeping a large number of connections
open indefinitely after a spike in activity. Any connection
- that has been unused in the pool for longer than this amount
- of time will be closed. If you do not want the pool to
- shrink so rapidly, you can set the MaxIdleTimeoutPercent
- and then some connections will be recreated to replace the
- closed ones. This is in contrast to garbage collection,
- which returns connections to the pool that have been checked
- out of the pool but not returned for a long period of
- time.</td>
+ that has been unused in the pool for longer than this amount
+ of time will be closed. If you do not want the pool to
+ shrink so rapidly, you can set the MaxIdleTimeoutPercent
+ and then some connections will be recreated to replace the
+ closed ones. This is in contrast to garbage collection,
+ which returns connections to the pool that have been checked
+ out of the pool but not returned for a long period of
+ time.</td>
<td>false</td>
</tr>
<tr>
<td>MaxIdleTimeoutPercent</td>
<td>Sets the idle timeout percent as a fraction between 0 and 1.
- If a number of connections are determined to be idle, they
- will all be closed and removed from the pool. However, if the
- ratio of objects released to objects in the pool is greater
- than this fraction, some new objects will be created to
- replace the closed objects. This prevents the pool size from
- decreasing too rapidly. Set to 0 to decrease the pool size by
- a maximum of 1 object per test, or 1 to never replace objects
- that have exceeded the idle timeout. The pool will always
- replace enough closed connections to stay at the minimum
- size.</td>
+ If a number of connections are determined to be idle, they
+ will all be closed and removed from the pool. However, if the
+ ratio of objects released to objects in the pool is greater
+ than this fraction, some new objects will be created to
+ replace the closed objects. This prevents the pool size from
+ decreasing too rapidly. Set to 0 to decrease the pool size by
+ a maximum of 1 object per test, or 1 to never replace objects
+ that have exceeded the idle timeout. The pool will always
+ replace enough closed connections to stay at the minimum
+ size.</td>
<td>1.0</td>
</tr>
<tr>
<td>IdleTimeout</td>
<td>Set the idle timeout for unused connections. If a
- connection has been unused in the pool for this amount of
- time, it will be released the next time garbage collection
- and shrinking are run (see GCInterval).</td>
+ connection has been unused in the pool for this amount of
+ time, it will be released the next time garbage collection
+ and shrinking are run (see GCInterval).</td>
<td>1800000 (30m)</td>
</tr>
<tr>
@@ -456,8 +456,8 @@
</li>
<li>jboss.jcml
<p>Note: You must include a user name and password. They can be
- bogus if your PostgreSQL installation is configured to "trust"
- the machine you're coming from, but you can't leave them out.</p>
+ bogus if your PostgreSQL installation is configured to "trust"
+ the machine you're coming from, but you can't leave them out.</p>
<pre>
<mbean name="DefaultDomain:service=XADataSource,name=<b>PostgresDB</b>">
<attribute
name="URL">jdbc:postgresql://<b>host.domain.com</b>/<b>database</b></attribute>
@@ -552,13 +552,17 @@
<MLET CODE = "org.jboss.logging.FileLogging" ARCHIVE="jboss.jar"
CODEBASE="../lib/ext/">
<ARG TYPE="java.lang.String" VALUE="Information,Debug,Warning,Error">
<ARG TYPE="java.lang.String" VALUE="<b>{0,date,yyyy-MM-dd}
{0,time,hh:mm:ss}</b> [{2}] {4}">
- <ARG TYPE="java.lang.String" VALUE="">
+ <ARG TYPE="java.lang.String" VALUE="<b>myBeanName1;myBeanName2</b>">
<ARG TYPE="java.lang.String" VALUE="FileName">
<ARG TYPE="java.lang.Boolean" VALUE="<b>true</b>">
</MLET>
</pre>
<p>In the second argument line above you can see an example
- of setting date and time formats for the log file.</p>
+ of setting date and time formats for the log file.
+ The third parameter may be used for filtering the log messages by their
+ source. You can have multiple FileLogging entries with different
+ source filters.
+ </p>
<h4><a NAME="gui">Configuring GUI Logging</a></h4>
<p>For GUI logging, add an entry to jboss.conf that looks like
