User: mulder
Date: 00/09/25 03:57:50
Modified: manual developing.html managing.html
Log:
Add an example to the DB usage text.
Start the managing section.
Revision Changes Path
1.4 +15 -8 jbossweb/manual/developing.html
Index: developing.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/developing.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- developing.html 2000/09/19 14:28:36 1.3
+++ developing.html 2000/09/25 10:57:49 1.4
@@ -232,14 +232,21 @@
<p>For example, let's say you configured a data source called
<code>jdbc/OracleDB</code> in your deployment descriptor. The
bean would access it using code like the example below. Note that
- you should preform this lookup every time you require data
- access, rather than storing the DataSource or Connection in an
- instance variable (unless it's part of the state of a Stateful
- Session Bean). Also, be sure you close the connection at the
- end of the method, unless you have a very good reason not to.
- This won't really close the connection - just return it to the
- connection pool - but you want to avoid a "connection leak" at
- all costs!</p>
+ you should perform this lookup every time you require data
+ access, rather than storing the Connection in an instance variable
+ (unless it's part of the state of a Stateful Session Bean). To
+ understand why, consider an instance pool of 100 beans, each of
+ which stores a connection in a local variable. If 100 clients
+ connect at once, all those beans are instantiated and grab
+ connections from the pool. Now if all the clients leave, or go on
+ to other beans, you're left with 100 connections that are locked,
+ but not servicing any clients. And since the connections are
+ pooled, you don't get any big performance advantage by hanging on
+ to the Connection like that. Finally, be sure you close the
+ connection at the end of the method, unless you have a very good
+ reason not to. This won't really close the connection - just
+ return it to the connection pool - but you want to avoid a
+ "connection leak" at all costs!</p>
<pre>
Context ctx = new InitialContext();
Connection conn = null;
1.2 +19 -0 jbossweb/manual/managing.html
Index: managing.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/managing.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- managing.html 2000/09/14 18:28:37 1.1
+++ managing.html 2000/09/25 10:57:49 1.2
@@ -5,5 +5,24 @@
</head>
<body>
<h1 ALIGN="CENTER">jBoss 2.0: Managing a Live jBoss Server</h1>
+ <p>jBoss is built on a Java Management Extensions (JMX)
+ infrastructure, so you can use any JMX tools available to manage
+ jBoss. Since the JMX specification is so new, that doesn't give
+ you a lot of choice today, but we expect that to change in the
+ near future. This section describes the tools that are available
+ today.</p>
+
+ <h2><a NAME="web">Web Administration</a></h2>
+ <p>jBoss comes with a Web interface for managing the server. By
+ default, this listens on port 8082, though you can change that
+ if necessary (see <a HREF="adv_config.html#ports">Changing
+ Default Port Assigments</a> in the
+ <a HREF="adv_config.html">Advanced Configuration</a> section).
+ To get an idea of the options, start jBoss and point your
+ browser to the web management port (using a URL like
+ <a HREF="http://localhost:8082/">http://localhost:8082/</a>).</p>
+ <p>The main page gives you a list of services that make up the jBoss
+ server.
+
</body>
</html>
