[jboss-cvs] JBossAS SVN: r80700 - trunk/server/src/etc/deploy.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Nov 7 20:27:53 EST 2008
Author: ron_sigal
Date: 2008-11-07 20:27:53 -0500 (Fri, 07 Nov 2008)
New Revision: 80700
Added:
trunk/server/src/etc/deploy/remoting-jboss-beans.xml
Modified:
trunk/server/src/etc/deploy/remoting-service.xml
Log:
JBAS-3926: Moved all Remoting related configuration from deploy/remoting-service.xml to deploy/remoting-jboss-beans.xml.
Added: trunk/server/src/etc/deploy/remoting-jboss-beans.xml
===================================================================
--- trunk/server/src/etc/deploy/remoting-jboss-beans.xml (rev 0)
+++ trunk/server/src/etc/deploy/remoting-jboss-beans.xml 2008-11-08 01:27:53 UTC (rev 80700)
@@ -0,0 +1,112 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<deployment xmlns="urn:jboss:bean-deployer:2.0">
+
+
+ <!-- ==================================================================== -->
+ <!-- Remoting services -->
+ <!-- ==================================================================== -->
+
+ <!-- For detailed description of all these configuration attributes, please see the -->
+ <!-- JBoss Remoting User's Guide (http://www.jboss.org/jbossremoting/docs/index.html) or -->
+ <!-- the Remoting wiki (http://www.jboss.org/community/docs/DOC-11782). -->
+
+ <!-- Unified invoker. Registers itself as an invocation handler with UnifiedInvokerConnector. -->
+ <!-- Can find more details on unified invoker configuration at -->
+ <!-- http://docs.jboss.org/jbossas/unified_invoker/UnifiedInvoker_guide.html. -->
+ <bean name="UnifiedInvoker" class="org.jboss.invocation.unified.server.UnifiedInvoker">
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=invoker,type=unified",exposedInterface=org.jboss.invocation.unified.server.UnifiedInvokerMBean.class,registerDirectly=true)</annotation>
+ <property name="connector"><inject bean="UnifiedInvokerConnector"/></property>
+ <depends>TransactionManager</depends>
+ </bean>
+
+
+ <!-- The Connector is the core component of the remoting server service. -->
+ <!-- It binds the remoting invoker (transport protocol, callback configuration, -->
+ <!-- data marshalling, etc.) with the invocation handlers. -->
+ <bean name="UnifiedInvokerConnector" class="org.jboss.remoting.transport.Connector">
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.remoting:service=Connector,transport=socket",exposedInterface=org.jboss.remoting.transport.ConnectorMBean.class,registerDirectly=true)</annotation>
+ <property name="serverConfiguration"><inject bean="UnifiedInvokerConfiguration"/></property>
+ </bean>
+
+
+ <!-- Remoting server configuration -->
+ <bean name="UnifiedInvokerConfiguration" class="org.jboss.remoting.ServerConfiguration">
+ <constructor>
+ <!-- transport: Others include sslsocket, bisocket, sslbisocket, http, https, rmi, sslrmi, servlet, sslservlet. -->
+ <parameter>socket</parameter>
+ </constructor>
+
+ <!-- Parameters visible to both client and server -->
+ <property name="invokerLocatorParameters">
+ <map keyClass="java.lang.String" valueClass="java.lang.String">
+ <!--entry><key>serverBindAddress</key> <value>${jboss.bind.address}</value></entry-->
+ <entry>
+ <key>serverBindAddress</key>
+ <value>
+ <value-factory bean="ServiceBindingManager" method="getStringBinding">
+ <parameter>UnifiedInvokerConnector</parameter>
+ <parameter>${host}</parameter>
+ </value-factory>
+ </value>
+ </entry>
+ <entry>
+ <key>serverBindPort</key>
+ <value>
+ <value-factory bean="ServiceBindingManager" method="getStringBinding">
+ <parameter>UnifiedInvokerConnector</parameter>
+ <parameter>${port}</parameter>
+ </value-factory>
+ </value>
+ </entry>
+ <entry><key>dataType</key> <value>invocation</value></entry>
+ <entry><key>marshaller</key> <value>org.jboss.invocation.unified.marshall.InvocationMarshaller</value></entry>
+ <entry><key>unmarshaller</key> <value>org.jboss.invocation.unified.marshall.InvocationUnMarshaller</value></entry>
+
+ <!-- A socket transport parameter -->
+ <entry><key>enableTcpNoDelay</key> <value>true</value></entry>
+
+ <!-- Selected optional parameters: -->
+
+ <!-- Parameters for connecting outside of a firewall. -->
+ <!--entry><key>clientConnectAddress</key> <value>a.b.c.d</value></entry-->
+ <!--entry><key>clientConnectPort</key> <value>7777</value></entry-->
+
+ <!-- Socket read timeout. Defaults to 60000 ms (1 minute) -->
+ <!-- on the server, 1800000 ms (30 minutes) on the client. -->
+ <!--entry><key>timeout</key> <value>120000</value></entry-->
+
+ <!-- Maximum number of connections in client invoker's -->
+ <!-- connection pool (socket transport). Defaults to 50. -->
+ <!--entry><key>clientMaxPoolSize</key> <value>20</value></entry-->
+
+ <!-- Configures traffic class on underlying sockets (socket transport). -->
+ <!-- Default value determined by socket implementation. -->
+ <!--entry><key>trafficClass</key> <value>2</value></entry-->
+ </map>
+ </property>
+
+ <!-- Parameters visible only to server -->
+ <property name="serverParameters">
+ <map keyClass="java.lang.String" valueClass="java.lang.String">
+
+ <!-- Selected optional parameters: -->
+
+ <!-- Maximum number of worker threads on the -->
+ <!-- server (socket transport). Defaults to 300. -->
+ <!--entry><key>maxPoolSize</key> <value>500</value></entry-->
+
+ <!-- Number of seconds after which an idle worker thread will be -->
+ <!-- purged (socket transport). By default purging is not enabled. -->
+ <!--entry><key>idleTimeout</key> <value>60</value></entry-->
+ </map>
+ </property>
+
+ <property name="invocationHandlers">
+ <map keyClass="java.lang.String" valueClass="java.lang.String">
+ <!-- The JSR88 deployment service StreamingTarget handler -->
+ <entry><key>JSR88</key> <value>org.jboss.deployment.remoting.DeployHandler</value></entry>
+ </map>
+ </property>
+ </bean>
+
+</deployment>
Modified: trunk/server/src/etc/deploy/remoting-service.xml
===================================================================
--- trunk/server/src/etc/deploy/remoting-service.xml 2008-11-07 23:59:31 UTC (rev 80699)
+++ trunk/server/src/etc/deploy/remoting-service.xml 2008-11-08 01:27:53 UTC (rev 80700)
@@ -7,153 +7,11 @@
<!-- ===================================================================== -->
<server>
-
-
- <!-- ==================================================================== -->
- <!-- Remoting services -->
- <!-- ==================================================================== -->
- <!-- For detailed description of all these configuration attributes, please see the -->
- <!-- JBoss Remoting User's Guide or wiki (http://www.jboss.org/wiki/Wiki.jsp?page=Remoting_configuration) -->
-
- <!-- The NetworkRegistry contains all the local and remote -->
- <!-- servers that it recognizes. The remote ones registered -->
- <!-- are dependant on the detectors running and which domains -->
- <!-- they are configured to identify. -->
- <mbean code="org.jboss.remoting.network.NetworkRegistry"
- name="jboss.remoting:service=NetworkRegistry"/>
-
- <!-- The Connector is the core component of the remoting server service. -->
- <!-- It binds the remoting invoker (transport protocol, callback configuration, -->
- <!-- data marshalling, etc.) with the invocation handlers. -->
- <mbean code="org.jboss.remoting.transport.Connector"
- name="jboss.remoting:service=Connector,transport=socket"
- display-name="Socket transport Connector">
-
- <!-- Can either just specify the InvokerLocator attribute and not the invoker element in the -->
- <!-- Configuration attribute, or do the full invoker configuration in the in invoker element -->
- <!-- of the Configuration attribute. -->
-
- <!-- Remember that if you do use more than one param on the uri, will have to include as a CDATA, -->
- <!-- otherwise, parser will complain. -->
- <!--
- <attribute name="InvokerLocator">
- <value-factory bean="ServiceBindingManager" method="getStringBinding">
- <parameter>jboss.remoting:service=Connector,transport=socket</parameter>
- <parameter><![CDATA[socket://${host}:${port}/?datatype=invocation]]></parameter>
- </value-factory>
- </attribute>
- -->
-
- <attribute name="Configuration">
- <!-- Using the following <invoker> element instead of the InvokerLocator above because specific attributes needed. -->
- <!-- If wanted to use any of the parameters below, can just add them as parameters to the url above if wanted use the InvokerLocator attribute. -->
-
- <value-factory bean="ServiceBindingManager" method="getElementBinding">
- <parameter>jboss.remoting:service=Connector,transport=socket</parameter>
- <parameter><![CDATA[
- <config>
- <!-- Other than transport type and handler, none of these configurations are required (will just use defaults). -->
- <invoker transport="socket">
- <attribute name="dataType" isParam="true">invocation</attribute>
- <attribute name="marshaller" isParam="true">org.jboss.invocation.unified.marshall.InvocationMarshaller</attribute>
- <attribute name="unmarshaller" isParam="true">org.jboss.invocation.unified.marshall.InvocationUnMarshaller</attribute>
- <!-- This will be port on which the marshall loader port runs on. -->
- <!-- <attribute name="loaderport" isParam="true">4447</attribute> -->
- <!-- The following are specific to socket invoker -->
- <!-- <attribute name="numAcceptThreads">1</attribute>-->
- <!-- <attribute name="maxPoolSize">303</attribute>-->
- <!-- <attribute name="clientMaxPoolSize" isParam="true">304</attribute>-->
- <!-- <attribute name="timeout" isParam="true">600000</attribute>-->
- <attribute name="serverBindAddress">${host}</attribute>
- <attribute name="serverBindPort">${port}</attribute>
- <!-- <attribute name="clientConnectAddress">216.23.33.2</attribute> -->
- <!-- <attribute name="clientConnectPort">7777</attribute> -->
- <attribute name="enableTcpNoDelay" isParam="true">true</attribute>
- <!-- <attribute name="backlog">200</attribute>-->
- <!-- The following is for callback configuration and is independant of invoker type -->
- <!-- <attribute name="callbackMemCeiling">30</attribute>-->
- <!-- indicates callback store by fully qualified class name -->
- <!-- <attribute name="callbackStore">org.jboss.remoting.CallbackStore</attribute>-->
- <!-- indicates callback store by object name -->
- <!-- <attribute name="callbackStore">jboss.remoting:service=CallbackStore,type=Serializable</attribute> -->
- <!-- config params for callback store. if were declaring callback store via object name, -->
- <!-- could have specified these config params there. -->
- <!-- StoreFilePath indicates to which directory to write the callback objects. -->
- <!-- The default value is the property value of 'jboss.server.data.dir' and if this is not set, -->
- <!-- then will be 'data'. Will then append 'remoting' and the callback client's session id. -->
- <!-- An example would be 'data\remoting\5c4o05l-9jijyx-e5b6xyph-1-e5b6xyph-2'. -->
- <!-- <attribute name="StoreFilePath">callback</attribute>-->
- <!-- StoreFileSuffix indicates the file suffix to use for the callback objects written to disk. -->
- <!-- The default value for file suffix is 'ser'. -->
- <!-- <attribute name="StoreFileSuffix">cst</attribute>-->
- </invoker>
-
- <!-- At least one handler is required by the connector. If have more than one, must decalre -->
- <!-- different subsystem values. Otherwise, all invocations will be routed to the only one -->
- <!-- that is declared. -->
- <handlers>
- <!-- The JSR88 deployment service StreamingTarget handler -->
- <handler subsystem="JSR88">org.jboss.deployment.remoting.DeployHandler</handler>
- </handlers>
- </config>
- ]]>
- </parameter>
- </value-factory>
- </attribute>
- <depends>jboss.remoting:service=NetworkRegistry</depends>
- </mbean>
-
-
- <!-- <mbean code="org.jboss.remoting.detection.jndi.JNDIDetector"-->
- <!-- name="jboss.remoting:service=Detector,transport=jndi">-->
- <!-- host to which the detector will connect to for the JNDI server. -->
- <!-- <attribute name="Host">localhost</attribute>-->
- <!-- port to which detector will connect to for the JNDI server. -->
- <!-- <attribute name="Port">5555</attribute>-->
- <!-- context factory string used when connecting to the JNDI server. -->
- <!-- The default is org.jnp.interfaces.NamingContextFactory. -->
- <!-- <attribute name="ContextFactory">org.acme.NamingContextFactory</attribute> -->
- <!-- url package string to use when connecting to the JNDI server. -->
- <!-- The default is org.jboss.naming:org.jnp.interfaces. -->
- <!-- <attribute name="URLPackage">org.acme.naming</attribute> -->
- <!-- Sets the number of detection iterations before manually pinging -->
- <!-- remote server to make sure still alive. This is needed since remote server -->
- <!-- could crash and yet still have an entry in the JNDI server, -->
- <!-- thus making it appear that it is still there. The default value is 5. -->
- <!-- <attribute name="CleanDetectionNumber">20</attribute>-->
-
- <!-- Specifies the domains in which the detector will recognize -->
- <!-- detections. If servers are not configured to be in these -->
- <!-- domains, they will not be added to NetworkRegistry. -->
- <!-- <attribute name="Configuration">-->
- <!-- <domains>-->
- <!-- <domain>roxanne</domain>-->
- <!-- <domain>sparky</domain>-->
- <!-- </domains>-->
- <!-- </attribute>-->
- <!-- </mbean>-->
-
<!-- ==================================================================== -->
<!-- Invokers to the JMX node -->
<!-- ==================================================================== -->
- <!-- Unified invoker (based on remoting) -->
- <!-- Can find more details on unified invoker configuration at -->
- <!-- http://docs.jboss.org/jbossas/unified_invoker/UnifiedInvoker_guide.html -->
- <mbean code="org.jboss.invocation.unified.server.UnifiedInvoker"
- name="jboss:service=invoker,type=unified">
- <!-- To turn on strict RMI exception propagation uncomment block below -->
- <!-- This will cause the UnifiedInvokerProxy to wrap RemoteExceptions -->
- <!-- within a ServerException, otherwise will throw root exception -->
- <!-- (not RemoteException) -->
- <!-- <attribute name="StrictRMIException">true</attribute> -->
- <depends>jboss:service=TransactionManager</depends>
- <depends optional-attribute-name="Connector" proxy-type="attribute">
- jboss.remoting:service=Connector,transport=socket
- </depends>
- </mbean>
-
<!-- RMI/JRMP invoker -->
<mbean code="org.jboss.invocation.jrmp.server.JRMPInvoker"
name="jboss:service=invoker,type=jrmp">
More information about the jboss-cvs-commits
mailing list