-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.DR16
Given that there is an XNIO worker defined in wildfly-config.xml, for example like this:
<worker xmlns="urn:xnio:3.5">
<worker-name value="myworker"/>
<outbound-bind-addresses>
<bind-address bind-address="127.0.0.9" bind-port="61111" match="0.0.0.0/0"/>
</outbound-bind-addresses>
</worker>
It is not picked up for a standalone client application.
To get a non-default configuration for an XNIO worker applied, so far we only found an ugly way to use a custom worker by creating it programmatically (and with having to twiddle with method visibility):
final Constructor constructor = XnioWorker.Builder.class.getDeclaredConstructor(Xnio.class);
constructor.setAccessible(true);
XnioWorker.Builder builder = (XnioWorker.Builder) constructor.newInstance(Xnio.getInstance());
builder.addBindAddressConfiguration(
CidrAddress.INET4_ANY_CIDR,
Inet4Address.getByName("127.0.0.9")
);
final XnioWorker worker = builder.build();
XnioWorker.getContextManager().setGlobalDefault(worker);
- is caused by
-
-
- Resolved
-
- is incorporated by
-
JBEAP-10604 Upgrade Remoting to 5.0.0.Beta21
-
- Verified
-
