Author: mmcallis
Date: 2008-02-06 02:55:21 -0500 (Wed, 06 Feb 2008)
New Revision: 9797
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml
Log:
minor corrections to my revision:
3.6. Disabling Dynamic Proxy Un-wrapping
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml
===================================================================
---
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-02-06
07:04:41 UTC (rev 9796)
+++
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-02-06
07:55:21 UTC (rev 9797)
@@ -262,19 +262,23 @@
</sect1>
<sect1>
<title>Disabling Dynamic Proxy Un-wrapping</title>
- <para>JBoss Portal uses the JBoss Microkernel for the service
infrastructure. The JBoss Microkernel provides injection of services into other services,
also known as wiring. It is only possible to inject
- dynamic proxies that talk to the MBeanServer, due to the Microkernel being JMX
based. The overhead
- at runtime is minimal since the Microkernel implementation is highly optimized;
however, when it is used
- with Java 5, a noticeable bottleneck appears due to the fact that the
implementation
- of the JMX API classes, <emphasis>javax.management.*</emphasis>,
provided by the Java Platform, performs synchronization. This does not occur under JDK 1.4
since those classes are implemented by JBoss MX.
+ <para>JBoss Portal uses the JBoss Microkernel for the service infrastructure.
The JBoss Microkernel provides injection of services into other services, otherwise known
as wiring. Due to the Microkernel being JMX based, tt is only possible to inject dynamic
proxies that talk to the MBeanServer. The overhead at runtime is minimal since the
Microkernel implementation is highly optimized; however, when it is used with Java 5, a
noticeable bottleneck appears due to the fact that the implementation of the JMX API
classes, <emphasis>javax.management.*</emphasis>, provided by the Java
Platform, performs synchronization. This does not occur under JDK 1.4 since those classes
are implemented by JBoss MX.
</para>
<para>
- JBoss Portal services use a special kind of Model MBean called
<emphasis>JBossServiceModelMBean</emphasis>, which allows the un-wrapping of
injected dynamic proxies, and replaces them with real plain old java object (POJO)
services. This allows the removal of the bottleneck with Java 5, and also provides a
performance boost on JDK 1.4. By default this feature is enabled, but it is possible to
disabled is using the following command:
+ JBoss Portal services use a special kind of Model MBean called
<emphasis>JBossServiceModelMBean</emphasis>, which allows the un-wrapping of
injected dynamic proxies, and replaces them with real plain old java object (POJO)
services. This allows the removal of the bottleneck with Java 5, and also provides a
performance boost on JDK 1.4. By default this feature is enabled, but it is possible to
disable. To do this on Linux systems, change into the
<filename>$JBOSS_HOME/bin/</filename> directory and run the following
command:
</para>
<para>
-<screen><![CDATA[
-./run.sh -Dportal.kernel.no_proxies=false]]>
+<screen>
+./run.sh -Dportal.kernel.no_proxies=false
</screen>
</para>
+<para>
+ On Microsoft Windows systems, run the following command:
+</para>
+<para>
+<screen>
+run.bat -Dportal.kernel.no_proxies=false
+</screen>
+</para>
</sect1>
</chapter>