From jboss-remoting-commits at lists.jboss.org Fri May 6 00:56:10 2011
Content-Type: multipart/mixed; boundary="===============1948004562427653271=="
MIME-Version: 1.0
From: jboss-remoting-commits at lists.jboss.org
To: jboss-remoting-commits at lists.jboss.org
Subject: [jboss-remoting-commits] JBoss Remoting SVN: r6365 -
remoting2/branches/2.x/docs/userguide/en.
Date: Fri, 06 May 2011 00:56:10 -0400
Message-ID: <201105060456.p464uArR021426@svn01.web.mwc.hst.phx2.redhat.com>
--===============1948004562427653271==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: ron.sigal(a)jboss.com
Date: 2011-05-06 00:56:09 -0400 (Fri, 06 May 2011)
New Revision: 6365
Modified:
remoting2/branches/2.x/docs/userguide/en/chap7.xml
Log:
JBREM-1283: Added discusssion of configurable parameters.
Modified: remoting2/branches/2.x/docs/userguide/en/chap7.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- remoting2/branches/2.x/docs/userguide/en/chap7.xml 2011-05-06 03:20:46 =
UTC (rev 6364)
+++ remoting2/branches/2.x/docs/userguide/en/chap7.xml 2011-05-06 04:56:09 =
UTC (rev 6365)
@@ -35,9 +35,8 @@
javax.net.ssl.SSLSockets and javax.ne=
t.ssl.SSLServerSockets
instead of Sockets and ServerSocket=
classname>s.
+
=
-
-
servlet and sslservlet transports
@@ -82,10 +81,95 @@
=
</web-app>
+
=
+
+ Server side parameters: http and https transports
+ =
+ In general, parameters passed to a CoyoteInvoker are
+ passed to the underlying Tomcat implementation. For example, the Tomcat=
attribute "maxThreads"
+ can be used to set the maximum number of threads to be used to accept i=
ncoming http requests.
+ However, the Remoting attributes "serverBindAddress" and "serverBindPor=
t" should be used instead
+ of the Tomcat attributes "address" and "port". For more information on =
the configuration attributes
+ available for the Tomcat connectors, please refer to http:/=
/tomcat.apache.org/tomcat-6.0-doc/config/http.html.
+
+ =
+ CoyoteInvoker can also configure an instan=
ce of
+ org.apache.catalina.Executor, an interface which=
extends
+ java.util.concurrent.Executor. If the parameter=
"executor" is
+ associated with a comma separated list of key=3Dvalue pairs, CoyoteInvoker
+ will parse the list, use the resulting Map to co=
nfigure an instance of
+ org.apache.catalina.core.StandardThreadExecutor,=
and inject it into the
+ underlying Tomcat implementation. For example, JBoss Messaging's =
remoting-http-service.xml
+ configuration file could contain
+ =
+ <attribute name=3D"executor">minSpareThreads=3D20=
,maxThreads=3D100</attribute> =
+ =
+ Note that if an executor is injected, the other threadpool related
+ attributes such as "maxThreads", which would otherwise be applied to a =
threadpool created by Tomcat, are ignored.
+ The configurable attributes of the StandardThreadExecutor are described in ht=
tp://tomcat.apache.org/tomcat-6.0-doc/config/executor.html. =
+
+ =
+ =
+
+ Server side parameters: servlet and sslservlet transports
+ =
+ The following parameter may be used to configure
+ an instance of ServletServerInvoker:
+ =
+ unwrapSingletonArrays - key in=
dicating if, when
+ javax.servlet.http.HttpServletRequest.getParameterMap() returns a
+ map containing pairs of the form (key, value) where value has the form
+ java.lang.String[] with length 1, the pair shoul=
d be replaced with a =
+ pair (key, ((String[] value)[0]). The default value is "false".
+ =
+
+ Client side parameters: http, https, servlet, sslservlet transpo=
rts
+ =
+ The following parameters may be used to configure
+ an instance of org.jboss.remoting.transport.http.HTTPClientI=
nvoker:
+ =
+ disconnectAfterUse - key indic=
ating if the
+ java.net.HttpURLConnection should be disconnecte=
d after the invocation.
+ The default value is "false".
+ =
+ ignoreErrorResponseMessage - k=
ey indicating
+ if HTTPClientInvoker
+ should try to get a response message and response code in the event of =
an exception.
+ The default value is "false".
+ =
+ numberOfCallAttempts - This p=
arameter is relevant only on the
+ client side, where it determines the maximum number of attempts that
+ will be made to complete an invocation. The default value is 1.
=
+ unmarshalNullStream - key indi=
cating if
+ HTTPClientInvoker
+ should make the call to UnMarshaller.read() wh=
en
+ the InputStream is null. The default value is "t=
rue".
+
+
+ Client side parameters: https and sslservlet transports
+ =
+ The following parameters may be used to configure
+ an instance of HTTPSClientInvoker:
+
+ org.jboss.security.ignoreHttpsHost - key indicating if =
+ HTTPSClientInvoker should ignore host name
+ verification, i.e., it will not check for a mismatch between the URL's =
hostname and the server's
+ hostname during handshaking. By default, standard hostname
+ verification will be performed.
+
+ hostnameVerifier - key indicat=
ing the hostname verifier that should be
+ used by HTTPSClientInvoker. The value should be =
the fully qualified
+ classname of a class that implements javax.net.ssl.HostnameV=
erifier and has
+ a void constructor.
+
+
+
JBoss Messaging, http transports, and callbacks
=
Unlike the bisocket transport, which was designed especially to a=
llow push callbacks without
--===============1948004562427653271==--