[JBoss JIRA] (WFLY-12827) Class not found com.sun.xml.internal.ws.encoding.StringDataContentHandler
by Dominik Derwiński (Jira)
[ https://issues.jboss.org/browse/WFLY-12827?page=com.atlassian.jira.plugin... ]
Dominik Derwiński commented on WFLY-12827:
------------------------------------------
I think this can be closed, WildFly has proper jars for JavaMail. When using them MailcapCommandMap is properly initialized, because the mailcap files and extra classes exist on classpath, unlike when JAXB or JAX-WS reference implementations pull wrong (new, but stripped) activation library.
> Class not found com.sun.xml.internal.ws.encoding.StringDataContentHandler
> -------------------------------------------------------------------------
>
> Key: WFLY-12827
> URL: https://issues.jboss.org/browse/WFLY-12827
> Project: WildFly
> Issue Type: Bug
> Components: Mail
> Affects Versions: 18.0.1.Final
> Reporter: Dominik Derwiński
> Assignee: Yeray Borges
> Priority: Major
>
> Trying to send email I get:
> {noformat}
> [2019-11-26 03:10:04.781] [javax.activation] [EE-ManagedThreadFactory-default-Thread-18] [FINE ] [com.sun.activation.registries.LogSupport] [log] [43] : MailcapCommandMap: createDataContentHandler for text/plain
> [2019-11-26 03:10:04.781] [javax.activation] [EE-ManagedThreadFactory-default-Thread-18] [FINE ] [com.sun.activation.registries.LogSupport] [log] [43] : search DB #0
> [2019-11-26 03:10:04.781] [javax.activation] [EE-ManagedThreadFactory-default-Thread-18] [FINE ] [com.sun.activation.registries.LogSupport] [log] [43] : got content-handler
> [2019-11-26 03:10:04.781] [javax.activation] [EE-ManagedThreadFactory-default-Thread-18] [FINE ] [com.sun.activation.registries.LogSupport] [log] [43] : class com.sun.xml.internal.ws.encoding.StringDataContentHandler
> [2019-11-26 03:10:04.781] [javax.activation] [EE-ManagedThreadFactory-default-Thread-18] [FINE ] [com.sun.activation.registries.LogSupport] [log] [49] : Can't load DCH com.sun.xml.internal.ws.encoding.StringDataContentHandler: java.lang.ClassNotFoundException: com.sun.xml.internal.ws.encoding.StringDataContentHandler from [Module "javax.activation.api" version 1.2.1 from local module loader @82de64a (finder: local module finder @659499f1 (roots: /u01/wildfly/wildfly18/modules,/u01/wildfly/wildfly18/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> at java.base/java.lang.Class.forName0(Native Method)
> at java.base/java.lang.Class.forName(Class.java:315)
> at javax.activation.api@1.2.1//javax.activation.MailcapCommandMap.getDataContentHandler(MailcapCommandMap.java:598)
> at javax.activation.api@1.2.1//javax.activation.MailcapCommandMap.createDataContentHandler(MailcapCommandMap.java:555)
> at javax.activation.api@1.2.1//javax.activation.DataHandler.getDataContentHandler(DataHandler.java:600)
> at javax.activation.api@1.2.1//javax.activation.DataHandler.writeTo(DataHandler.java:299)
> at javax.mail.api@1.6.4//javax.mail.internet.MimeUtility.getEncoding(MimeUtility.java:316)
> at javax.mail.api@1.6.4//javax.mail.internet.MimeBodyPart.updateHeaders(MimeBodyPart.java:1551)
> at javax.mail.api@1.6.4//javax.mail.internet.MimeBodyPart.updateHeaders(MimeBodyPart.java:1148)
> at javax.mail.api@1.6.4//javax.mail.internet.MimeMultipart.updateHeaders(MimeMultipart.java:498)
> at javax.mail.api@1.6.4//javax.mail.internet.MimeBodyPart.updateHeaders(MimeBodyPart.java:1509)
> at javax.mail.api@1.6.4//javax.mail.internet.MimeMessage.updateHeaders(MimeMessage.java:2238)
> at javax.mail.api@1.6.4//javax.mail.internet.MimeMessage.saveChanges(MimeMessage.java:2198)
> at javax.mail.api@1.6.4//javax.mail.Transport.send(Transport.java:99)
> {noformat}
> Maybe it's just missing module dependency for javax.mail.api, maybe you need to include JAXB and JAXWS libraries in WildFly modules for use on JDK 11+, when they were removed from JDK.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFCORE-3948) Potential race condition on deployment of EAR when Class-Path manifest entry is in use
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFCORE-3948?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-3948:
------------------------------------------
All of my above discussion is wrong; all that's needed is for AttachmentList to be thread safe.
Why?
The DeploymentUnitPhaseService for the STRUCTURE Phase for the top level deployment installs all the SubDeploymentUnitService instances. It's a general rule that any service has a dep on the service that installed it, so that means any SubDeploymentUnitService will not start until the top level deployment has completed STRUCTURE phase and will see all its data.
Within the STRUCTURE phase, the subdeployments don't care about the data from other subdeployments.
SubDeploymentProcessor adds a dep on the STRUCTURE phase for each subdeployment to the top level deployment's PARSE phase. So all the subdeployments will have completed STRUCTURE before the top begins PARSE work. All the writes happen in STRUCTURE so they will be complete. All the reads after STRUCTURE are either by the top level deployment, which waits for the writes, or by subdeployments which are not concerned with any writes by other subdeployments.
> Potential race condition on deployment of EAR when Class-Path manifest entry is in use
> --------------------------------------------------------------------------------------
>
> Key: WFCORE-3948
> URL: https://issues.jboss.org/browse/WFCORE-3948
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Reporter: Stuart Douglas
> Assignee: Brian Stansberry
> Priority: Major
>
> Attachments#ADDITIONAL_MODULES is attached to the top level DU, but modified by sub deployments in ManifestClassPathProcessor#createAdditionalModule without any sort of synchronisation. This can result in ConcurrentModificationException when the list is read/written to by other sub deployments at the same time.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFLY-12830) interface "any" tag not working as expected
by Yann Le Tallec (Jira)
[ https://issues.jboss.org/browse/WFLY-12830?page=com.atlassian.jira.plugin... ]
Yann Le Tallec updated WFLY-12830:
----------------------------------
Description:
The {{<any>}} tag in the {{interface}} configuration of {{standalone.xml}} should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below.
This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected:
{code:xml}
<interfaces>
<interface name="management">
<any>
<inet-address value="127.0.0.1"/>
</any>
</interface>
</interfaces>
{code}
But if I add another address inside the any tag, I can't connect any more:
{code:xml}
<interfaces>
<interface name="management">
<any>
<inet-address value="127.0.0.1"/>
<inet-address value="10.20.230.26"/>
</any>
</interface>
</interfaces>
{code}
With the latter configuration, {{connect}} fails with the following error:
{noformat}
>The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused
{noformat}
Note: to easily reproduce the problem from the cli, starting from a fresh standalone install:
{code:bash}
connect
/interface=management:undefine-attribute(name=inet-address)
/interface=management:undefine-attribute(name=any)
/interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]})
reload
/interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]})
reload
{code}
Notes:
- if I use 10.20.230.1 instead of 230.26 the connection works normally.
- if I use {{subnet-match}} I get the same issue
was:
The {{<any>}} tag in the {{interface}} configuration should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below.
This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected:
{code:xml}
<interfaces>
<interface name="management">
<any>
<inet-address value="127.0.0.1"/>
</any>
</interface>
</interfaces>
{code}
But if I add another address inside the any tag, I can't connect any more:
{code:xml}
<interfaces>
<interface name="management">
<any>
<inet-address value="127.0.0.1"/>
<inet-address value="10.20.230.26"/>
</any>
</interface>
</interfaces>
{code}
With the latter configuration, {{connect}} fails with the following error:
{noformat}
>The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused
{noformat}
Note: to easily reproduce the problem from the cli, starting from a fresh standalone install:
{code:bash}
connect
/interface=management:undefine-attribute(name=inet-address)
/interface=management:undefine-attribute(name=any)
/interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]})
reload
/interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]})
reload
{code}
Notes:
- if I use 10.20.230.1 instead of 230.26 the connection works normally.
- if I use {{subnet-match}} I get the same issue
> interface "any" tag not working as expected
> -------------------------------------------
>
> Key: WFLY-12830
> URL: https://issues.jboss.org/browse/WFLY-12830
> Project: WildFly
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 17.0.1.Final
> Environment: Ubuntu 18.02
> Reporter: Yann Le Tallec
> Assignee: Darran Lofthouse
> Priority: Major
>
> The {{<any>}} tag in the {{interface}} configuration of {{standalone.xml}} should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below.
> This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected:
> {code:xml}
> <interfaces>
> <interface name="management">
> <any>
> <inet-address value="127.0.0.1"/>
> </any>
> </interface>
> </interfaces>
> {code}
> But if I add another address inside the any tag, I can't connect any more:
> {code:xml}
> <interfaces>
> <interface name="management">
> <any>
> <inet-address value="127.0.0.1"/>
> <inet-address value="10.20.230.26"/>
> </any>
> </interface>
> </interfaces>
> {code}
> With the latter configuration, {{connect}} fails with the following error:
> {noformat}
> >The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused
> {noformat}
> Note: to easily reproduce the problem from the cli, starting from a fresh standalone install:
> {code:bash}
> connect
> /interface=management:undefine-attribute(name=inet-address)
> /interface=management:undefine-attribute(name=any)
> /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]})
> reload
> /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]})
> reload
> {code}
> Notes:
> - if I use 10.20.230.1 instead of 230.26 the connection works normally.
> - if I use {{subnet-match}} I get the same issue
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFLY-12830) interface "any" tag not working as expected
by Yann Le Tallec (Jira)
[ https://issues.jboss.org/browse/WFLY-12830?page=com.atlassian.jira.plugin... ]
Yann Le Tallec updated WFLY-12830:
----------------------------------
Description:
The {{<any>}} tag in the {{interface}} configuration should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below.
This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected:
{code:xml}
<interfaces>
<interface name="management">
<any>
<inet-address value="127.0.0.1"/>
</any>
</interface>
</interfaces>
{code}
But if I add another address inside the any tag, I can't connect any more:
{code:xml}
<interfaces>
<interface name="management">
<any>
<inet-address value="127.0.0.1"/>
<inet-address value="10.20.230.26"/>
</any>
</interface>
</interfaces>
{code}
With the latter configuration, {{connect}} fails with the following error:
{noformat}
>The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused
{noformat}
Note: to easily reproduce the problem from the cli, starting from a fresh standalone install:
{code:bash}
connect
/interface=management:undefine-attribute(name=inet-address)
/interface=management:undefine-attribute(name=any)
/interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]})
reload
/interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]})
reload
{code}
Notes:
- if I use 10.20.230.1 instead of 230.26 the connection works normally.
- if I use {{subnet-match}} I get the same issue
was:
The {{<any>}} tag in the {{interface}} configuration should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below.
This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected:
{code:xml}
<interfaces>
<interface name="management">
<any>
<inet-address value="127.0.0.1"/>
</any>
</interface>
</interfaces>
{code}
But if I add another address inside the any tag, I can't connect any more:
{code:xml}
<interfaces>
<interface name="management">
<any>
<inet-address value="127.0.0.1"/>
<inet-address value="10.20.230.26"/>
</any>
</interface>
</interfaces>
{code}
With the latter configuration, {{connect}} fails with the following error:
{noformat}
>The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused
{noformat}
Note: to easily reproduce the problem from the cli, starting from a fresh standalone install:
{code:bash}
connect
/interface=management:undefine-attribute(name=inet-address)
/interface=management:undefine-attribute(name=any)
/interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]})
reload
/interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]})
reload
{code}
Notes:
- if I use 10.20.230.1 instead of 230.26 the connection works normally.
- if I use {{subvnet-match}} I get the same issue
> interface "any" tag not working as expected
> -------------------------------------------
>
> Key: WFLY-12830
> URL: https://issues.jboss.org/browse/WFLY-12830
> Project: WildFly
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 17.0.1.Final
> Environment: Ubuntu 18.02
> Reporter: Yann Le Tallec
> Assignee: Darran Lofthouse
> Priority: Major
>
> The {{<any>}} tag in the {{interface}} configuration should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below.
> This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected:
> {code:xml}
> <interfaces>
> <interface name="management">
> <any>
> <inet-address value="127.0.0.1"/>
> </any>
> </interface>
> </interfaces>
> {code}
> But if I add another address inside the any tag, I can't connect any more:
> {code:xml}
> <interfaces>
> <interface name="management">
> <any>
> <inet-address value="127.0.0.1"/>
> <inet-address value="10.20.230.26"/>
> </any>
> </interface>
> </interfaces>
> {code}
> With the latter configuration, {{connect}} fails with the following error:
> {noformat}
> >The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused
> {noformat}
> Note: to easily reproduce the problem from the cli, starting from a fresh standalone install:
> {code:bash}
> connect
> /interface=management:undefine-attribute(name=inet-address)
> /interface=management:undefine-attribute(name=any)
> /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]})
> reload
> /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]})
> reload
> {code}
> Notes:
> - if I use 10.20.230.1 instead of 230.26 the connection works normally.
> - if I use {{subnet-match}} I get the same issue
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFLY-12830) interface "any" tag not working as expected
by Yann Le Tallec (Jira)
[ https://issues.jboss.org/browse/WFLY-12830?page=com.atlassian.jira.plugin... ]
Yann Le Tallec updated WFLY-12830:
----------------------------------
Description:
The {{<any>}} tag in the {{interface}} configuration should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below.
This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected:
{code:xml}
<interfaces>
<interface name="management">
<any>
<inet-address value="127.0.0.1"/>
</any>
</interface>
</interfaces>
{code}
But if I add another address inside the any tag, I can't connect any more:
{code:xml}
<interfaces>
<interface name="management">
<any>
<inet-address value="127.0.0.1"/>
<inet-address value="10.20.230.26"/>
</any>
</interface>
</interfaces>
{code}
With the latter configuration, {{connect}} fails with the following error:
{noformat}
>The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused
{noformat}
Note: to easily reproduce the problem from the cli, starting from a fresh standalone install:
{code:bash}
connect
/interface=management:undefine-attribute(name=inet-address)
/interface=management:undefine-attribute(name=any)
/interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]})
reload
/interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]})
reload
{code}
Notes:
- if I use 10.20.230.1 instead of 230.26 the connection works normally.
- if I use {{subvnet-match}} I get the same issue
was:
The {{>any}} tag in the {{interface}} configuration should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below.
This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected:
{code:xml}
<interfaces>
<interface name="management">
<any>
<inet-address value="127.0.0.1"/>
</any>
</interface>
</interfaces>
{code}
But if I add another address inside the any tag, I can't connect any more:
{code:xml}
<interfaces>
<interface name="management">
<any>
<inet-address value="127.0.0.1"/>
<inet-address value="10.20.230.26"/>
</any>
</interface>
</interfaces>
{code}
With the latter configuration, {{connect}} fails with the following error:
{noformat}
>The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused
{noformat}
Note: to easily reproduce the problem from the cli, starting from a fresh standalone install:
{code:bash}
connect
/interface=management:undefine-attribute(name=inet-address)
/interface=management:undefine-attribute(name=any)
/interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]})
reload
/interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]})
reload
{code}
Notes:
- if I use 10.20.230.1 instead of 230.26 the connection works normally.
- if I use {{subvnet-match}} I get the same issue
> interface "any" tag not working as expected
> -------------------------------------------
>
> Key: WFLY-12830
> URL: https://issues.jboss.org/browse/WFLY-12830
> Project: WildFly
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 17.0.1.Final
> Environment: Ubuntu 18.02
> Reporter: Yann Le Tallec
> Assignee: Darran Lofthouse
> Priority: Major
>
> The {{<any>}} tag in the {{interface}} configuration should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below.
> This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected:
> {code:xml}
> <interfaces>
> <interface name="management">
> <any>
> <inet-address value="127.0.0.1"/>
> </any>
> </interface>
> </interfaces>
> {code}
> But if I add another address inside the any tag, I can't connect any more:
> {code:xml}
> <interfaces>
> <interface name="management">
> <any>
> <inet-address value="127.0.0.1"/>
> <inet-address value="10.20.230.26"/>
> </any>
> </interface>
> </interfaces>
> {code}
> With the latter configuration, {{connect}} fails with the following error:
> {noformat}
> >The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused
> {noformat}
> Note: to easily reproduce the problem from the cli, starting from a fresh standalone install:
> {code:bash}
> connect
> /interface=management:undefine-attribute(name=inet-address)
> /interface=management:undefine-attribute(name=any)
> /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]})
> reload
> /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]})
> reload
> {code}
> Notes:
> - if I use 10.20.230.1 instead of 230.26 the connection works normally.
> - if I use {{subvnet-match}} I get the same issue
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFLY-12830) interface "any" tag not working as expected
by Yann Le Tallec (Jira)
Yann Le Tallec created WFLY-12830:
-------------------------------------
Summary: interface "any" tag not working as expected
Key: WFLY-12830
URL: https://issues.jboss.org/browse/WFLY-12830
Project: WildFly
Issue Type: Feature Request
Components: Security
Affects Versions: 17.0.1.Final
Environment: Ubuntu 18.02
Reporter: Yann Le Tallec
Assignee: Darran Lofthouse
The {{>any}} tag in the {{interface}} configuration should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below.
This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected:
{code:xml}
<interfaces>
<interface name="management">
<any>
<inet-address value="127.0.0.1"/>
</any>
</interface>
</interfaces>
{code}
But if I add another address inside the any tag, I can't connect any more:
{code:xml}
<interfaces>
<interface name="management">
<any>
<inet-address value="127.0.0.1"/>
<inet-address value="10.20.230.26"/>
</any>
</interface>
</interfaces>
{code}
With the latter configuration, {{connect}} fails with the following error:
{noformat}
>The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused
{noformat}
Note: to easily reproduce the problem from the cli, starting from a fresh standalone install:
{code:bash}
connect
/interface=management:undefine-attribute(name=inet-address)
/interface=management:undefine-attribute(name=any)
/interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]})
reload
/interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]})
reload
{code}
Notes:
- if I use 10.20.230.1 instead of 230.26 the connection works normally.
- if I use {{subvnet-match}} I get the same issue
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFWIP-160) Fix throughput and response time differences between TLS 1.2 and TLS 1.3
by Andrew Haley (Jira)
[ https://issues.jboss.org/browse/WFWIP-160?page=com.atlassian.jira.plugin.... ]
Andrew Haley commented on WFWIP-160:
------------------------------------
It's hard to tell from those files what is going on. I guess I'll do my own
profiling to get some more data.
--
Andrew Haley (he/him)
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
https://keybase.io/andrewhaley
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
> Fix throughput and response time differences between TLS 1.2 and TLS 1.3
> ------------------------------------------------------------------------
>
> Key: WFWIP-160
> URL: https://issues.jboss.org/browse/WFWIP-160
> Project: WildFly WIP
> Issue Type: Task
> Components: Web (Undertow)
> Reporter: Farah Juma
> Assignee: Richard Opalka
> Priority: Blocker
> Attachments: jstourac-report.zip, performance-hotspot.png, results-tlsv12.zip, results-tlsv13.zip
>
>
> Performance with TLS 1.3 on WildFly appears to be worse than with TLS 1.2. In particular, throughput is much lower (roughly three times lower) and response time is much higher (roughly three times higher), which is not supposed to be the case. The underlying issue seems to be in Undertow or XNIO, that is the code that actually gets invoked during the TLS handshake process. Looking at CPU time, there is significantly more time being spent in [io.undertow.protocols.ssl.SslConduit$5.run()|https://github.com/undertow-...] with TLS 1.3 than with TLS 1.2.
> Steps to reproduce (taken from EAP7-1022):
> 1. Build WildFly using the following feature branches or download a QE build of WildFly [here|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/undertow-...]:
> https://github.com/fjuma/wildfly-elytron/tree/ELY-1706
> https://github.com/fjuma/wildfly-core/tree/WFCORE-4172 (Update the Elytron version in the pom.xml file to use the version built in the previous step)
> https://github.com/fjuma/wildfly/tree/WFCORE-4172 (Update the Core version in the pom.xml file to use the version built in the previous step)
> 2. Download and unzip JMeter from https://jmeter.apache.org/download_jmeter.cgi
> 3. Download attached test plan [TLSv1.3.jmx|https://issues.jboss.org/secure/attachment/12449098/12449098_...]
> 4. Start server with JDK11 and configure with TLSv1.3:
> {code}
> $ JAVA_HOME=/path/to/java/openjdk-11.0.2 <EAP_HOME>/bin/standalone.sh
> $ <EAP_HOME>/bin/jboss-cli.sh -c
> /subsystem=elytron/key-store=tls13:add(path=keystore.jks,relative-to=jboss.server.config.dir,credential-reference={clear-text=secret},type=JKS)
> /subsystem=elytron/key-store=tls13:generate-key-pair(alias=localhost,algorithm=RSA,key-size=1024,validity=365,credential-reference={clear-text=secret},distinguished-name="CN=localhost")
> /subsystem=elytron/key-store=tls13:store()
> /subsystem=elytron/key-manager=tls13:add(key-store=tls13,credential-reference={clear-text=secret})
> /subsystem=elytron/server-ssl-context=tls13:add(key-manager=tls13,protocols=["TLSv1.3"])
> batch
> /subsystem=undertow/server=default-server/https-listener=https:undefine-attribute(name=security-realm)
> /subsystem=undertow/server=default-server/https-listener=https:write-attribute(name=ssl-context,value=tls13)
> run-batch
> reload
> {code}
> 5. Start jmeter with JDK 11 and downloaded test plan
> {code}
> export JAVA_HOME=/path/to/java/openjdk-11.0.2; bin/jmeter -n -t TLSv1.3.jmx -e -l tlsv13.log -o results-tlsv13
> {code}
> 6. Set server to use TLSv1.2
> {code}
> /subsystem=elytron/server-ssl-context=tls13:write-attribute(name=protocols,value=["TLSv1.2"])
> reload
> {code}
> 7. Repeat same for TLSv1.2
> {code}
> export JAVA_HOME=/path/to/java/openjdk-11.0.2; bin/jmeter -n -t TLSv1.3.jmx -e -l tlsv12.log -o results-tlsv12
> {code}
> 8. Compare results (there will be an index.html file in the results-tlsv12 and results-tlsv13 directories)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months