Remoting WildFly Subsystem Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(18 intermediate revisions by the same user not shown)
Line 1: Line 1:
=External=
* https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Administration_and_Configuration_Guide/sect-Remoting.html#Configure_the_Remoting_Subsystem
=Internal=
=Internal=


Line 6: Line 10:
=Overview=
=Overview=


==WildFly 9==
The default port the remoting connector listens on is 4447.
 
==EAP7, WildFly 9==


<pre>
<pre>
Line 38: Line 44:


=Configuration Elements=
=Configuration Elements=
==<tt><worker-thread-pool></tt>==
<pre>
<subsystem xmlns="urn:jboss:domain:remoting:1.1">
    <worker-thread-pool read-threads="1" task-keepalive="60" task-max-threads="16" task-core-thread="4" task-limit="16384" write-threads="1" />
    ...
</subsystem>
</pre>
For more details on the remoting worker thread pool see [[Remoting WildFly Subsystem Concepts#Threading_Model|Remoting Threading Model]].


==<tt><endpoint></tt>==
==<tt><endpoint></tt>==
Line 62: Line 79:


Remove "security-realm" configuration attribute from the connector configuration element.
Remove "security-realm" configuration attribute from the connector configuration element.
=Configuring Remoting Subsystem to Support Deployed EJB Client Contexts=
{{Internal|JBoss_Instance_Configuration_to_Support_Deployed_EJB_Client_Contexts#Remoting_Subsystem_Configuration|JBoss Instance Configuration to Support Deployed EJB Client Contexts}}

Latest revision as of 20:31, 24 March 2017

External

Internal

Overview

The default port the remoting connector listens on is 4447.

EAP7, WildFly 9

<subsystem xmlns="urn:jboss:domain:remoting:3.0">
    <endpoint worker="default"/>
    <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>
</subsystem>

EAP 6.4

<subsystem xmlns="urn:jboss:domain:remoting:1.2">
    <connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/>
</subsystem>

<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
    ...
    <socket-binding name="remoting" port="4447"/>
    ...
</socket-binding-group>

Schema


https://github.com/wildfly/?

TODO: Link to .xsd.

Configuration Elements

<worker-thread-pool>

<subsystem xmlns="urn:jboss:domain:remoting:1.1">
    <worker-thread-pool read-threads="1" task-keepalive="60" task-max-threads="16" task-core-thread="4" task-limit="16384" write-threads="1" />
    ...
</subsystem>

For more details on the remoting worker thread pool see Remoting Threading Model.

<endpoint>

The Remoting endpoint uses the XNIO Worker declared and configured by the io subsystem. The XNIO worker's configuration is described here: io subsystem worker configuration.

<connector>

name

socket-binding

security-realm

The presence of the 'security-realm' attribute in the remoting connector configuration triggers enabling of authentication within the remoting service. For more details about remoting security see Remoting Subsystem Concepts - Security.

<http-connector>

The connector-ref is the name of the Undertow http-listener, so if the name of that connector changes, the Remoting reference should also change.

Disabling Remoting Authentication

EAP 6.4

Remove "security-realm" configuration attribute from the connector configuration element.

Configuring Remoting Subsystem to Support Deployed EJB Client Contexts

JBoss Instance Configuration to Support Deployed EJB Client Contexts