[JBoss JIRA] (JGRP-2089) Potential deadlocks after cluster split
by Bram Klein Gunnewiek (JIRA)
Bram Klein Gunnewiek created JGRP-2089:
------------------------------------------
Summary: Potential deadlocks after cluster split
Key: JGRP-2089
URL: https://issues.jboss.org/browse/JGRP-2089
Project: JGroups
Issue Type: Feature Request
Affects Versions: 3.6.10
Reporter: Bram Klein Gunnewiek
Assignee: Bela Ban
We encountered in some rare situations where a cluster split and/or merged. The dealocks happend when using the UDP transport protocol and where caused by received lock requests from members not present in the current view.
We fixed this with: https://github.com/belaban/JGroups/pull/311
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFCORE-1657) Confusing tab completion for adding a module dependencies
by Bartosz Spyrko-Śmietanko (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1657?page=com.atlassian.jira.plugi... ]
Bartosz Spyrko-Śmietanko moved JBEAP-5221 to WFCORE-1657:
---------------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1657 (was: JBEAP-5221)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: CLI
(was: CLI)
Affects Version/s: 2.2.0.CR7
3.0.0.Alpha3
(was: 7.0.0.GA)
> Confusing tab completion for adding a module dependencies
> ---------------------------------------------------------
>
> Key: WFCORE-1657
> URL: https://issues.jboss.org/browse/WFCORE-1657
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 2.2.0.CR7, 3.0.0.Alpha3
> Reporter: Bartosz Spyrko-Śmietanko
> Assignee: Bartosz Spyrko-Śmietanko
>
> Using tab completion for adding a module dependencies with {{module add}} command could lead to invalid module.xml as CLI prompt user to use module name with "system.layers.base" prefix, which is not a part of module name.
> *reproduce*
> Add a new module via {{module add}} command, use tab-completion for dependencies
> {noformat}
> module add --name=<name> --resources=<path_to_jar> --dependencies=<TAB>
> module add --name=<name> --resources=<path_to_jar> --dependencies=system.<TAB>
> module add --name=<name> --resources=<path_to_jar> --dependencies=system.layers.<TAB>
> module add --name=<name> --resources=<path_to_jar> --dependencies=system.layers.base.<TAB>
> asm ch com gnu ibm io javaee javax net nu org sun
> {noformat}
> this way something like following is generated in module.xml file
> {code:xml}
> <dependencies>
> <module name="system.layers.base.org.jboss.as.controller"/>
> </dependencies>
> {code}
> however correct module name is {{org.jboss.as.controller}}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6836) Vault.sh misleading output
by Martin Choma (JIRA)
Martin Choma created WFLY-6836:
----------------------------------
Summary: Vault.sh misleading output
Key: WFLY-6836
URL: https://issues.jboss.org/browse/WFLY-6836
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Martin Choma
Assignee: Darran Lofthouse
Priority: Minor
Vault.sh advise to insert vault xml snippet as follows:
{code}
Vault Configuration in AS7 config file:
********************************************
...
</extensions>
<vault>
<vault-option name="KEYSTORE_URL" value="EAP_HOME/vault/vault.keystore"/>
<vault-option name="KEYSTORE_PASSWORD" value="MASK-5dOaAVafCSd"/>
<vault-option name="KEYSTORE_ALIAS" value="vault"/>
<vault-option name="SALT" value="1234abcd"/>
<vault-option name="ITERATION_COUNT" value="120"/>
<vault-option name="ENC_FILE_DIR" value="EAP_HOME/vault/"/>
</vault><management> ...
********************************************
{code}
1. User can insert this snippet on wrong place. See forum link for example. Pobably CLI command would be more suitable?
{code}
/core-service=vault:add(vault-options=[("KEYSTORE_URL" => "PATH_TO_KEYSTORE"),("KEYSTORE_PASSWORD" => "MASKED_PASSWORD"),("KEYSTORE_ALIAS" => "ALIAS"),("SALT" => "SALT"),("ITERATION_COUNT" => "ITERATION_COUNT"),("ENC_FILE_DIR" => "ENC_FILE_DIR")])
{code}
2. There is still reference to AS7
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6835) Vault.sh misleading output
by Martin Choma (JIRA)
Martin Choma created WFLY-6835:
----------------------------------
Summary: Vault.sh misleading output
Key: WFLY-6835
URL: https://issues.jboss.org/browse/WFLY-6835
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Martin Choma
Assignee: Darran Lofthouse
Priority: Minor
Vault.sh advise to insert vault xml snippet as follows:
{code}
Vault Configuration in AS7 config file:
********************************************
...
</extensions>
<vault>
<vault-option name="KEYSTORE_URL" value="EAP_HOME/vault/vault.keystore"/>
<vault-option name="KEYSTORE_PASSWORD" value="MASK-5dOaAVafCSd"/>
<vault-option name="KEYSTORE_ALIAS" value="vault"/>
<vault-option name="SALT" value="1234abcd"/>
<vault-option name="ITERATION_COUNT" value="120"/>
<vault-option name="ENC_FILE_DIR" value="EAP_HOME/vault/"/>
</vault><management> ...
********************************************
{code}
1. User can insert this snippet on wrong place. See forum link for example. Pobably CLI command would be more suitable?
{code}
/core-service=vault:add(vault-options=[("KEYSTORE_URL" => "PATH_TO_KEYSTORE"),("KEYSTORE_PASSWORD" => "MASKED_PASSWORD"),("KEYSTORE_ALIAS" => "ALIAS"),("SALT" => "SALT"),("ITERATION_COUNT" => "ITERATION_COUNT"),("ENC_FILE_DIR" => "ENC_FILE_DIR")])
{code}
2. There is still reference to AS7
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JGRP-2042) Improve performance of Message#writeHeader
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/JGRP-2042?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero commented on JGRP-2042:
---------------------------------------
Awesome! thanks. With all these fixed, looks like it might be worth profiling again..
> Improve performance of Message#writeHeader
> ------------------------------------------
>
> Key: JGRP-2042
> URL: https://issues.jboss.org/browse/JGRP-2042
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Sanne Grinovero
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.0
>
>
> The following stacktrace, taken with JFR, is highlighting a CPU consumer which could be optimised.
> {noformat}Stack Trace Sample Count Percentage(%)
> java.util.IdentityHashMap.get(Object) 66 2.224
> org.jgroups.conf.ClassConfigurator.getMagicNumber(Class) 66 2.224
> org.jgroups.Message.writeHeader(Header, DataOutput) 66 2.224
> {noformat}
> One idea could be to use an ad-hoc implementation of Map which takes advantage of the key being a {{Class}}. An interesting alternative would be to avoid the map lookup altogether, by having the Header expose a method like "writeMagicNumber(DataInput to)".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6834) Store license files in repository
by Petr Sakař (JIRA)
Petr Sakař created WFLY-6834:
--------------------------------
Summary: Store license files in repository
Key: WFLY-6834
URL: https://issues.jboss.org/browse/WFLY-6834
Project: WildFly
Issue Type: Enhancement
Components: Build System
Reporter: Petr Sakař
Assignee: Petr Sakař
store license files in the repository so the build copies the files to the distribution zip instead of downloading them.
Downloading at build time results in unpredictable errors and missing licenses when location of license is changed by project or url results in redirect.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ELY-438) There is not possibility to use alternative JSSE Cipher Suite Names for IBM JDK
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/ELY-438?page=com.atlassian.jira.plugin.sy... ]
Hynek Švábek updated ELY-438:
-----------------------------
Priority: Blocker (was: Critical)
> There is not possibility to use alternative JSSE Cipher Suite Names for IBM JDK
> -------------------------------------------------------------------------------
>
> Key: ELY-438
> URL: https://issues.jboss.org/browse/ELY-438
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Reporter: Hynek Švábek
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 1.1.0.CR1, 1.0.3.CR1
>
>
> There is not possibility to use alternative JSSE Cipher Suite Names for IBM JDK8
> Interchange TLS prefix to SSL and vice versa is not supported.
> Here is list of standard JSSE Cipher Suite Names
> http://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardNa...
> In my opinion this file is mapping file for our purpose. It is?
> https://github.com/wildfly-security/wildfly-elytron/blob/master/src/main/...
> For IBM JDK are different JSSE Cipher Suite Names (different prefix).
> Most items from this list are missing in MechanismDatabase.properties mentioned above.
> http://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/com.ibm.java.secu...
> For example:
> JSSE Cipher Suite Name *SSL_ECDHE_RSA_WITH_AES_128_CBC_SHA* is only defined for IBM JDK.
> It is *TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA* for Oracle JDK.
> If I try start server with JSSE Cipher Suite Name *SSL_ECDHE_RSA_WITH_AES_128_CBC_SHA* I will get this error:
> {code}
> 16:55:25,594 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.undertow.listener.https: org.jboss.msc.service.StartException in service jboss.undertow.listener.https: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.lang.Thread.run(Thread.java:785)
> Caused by: java.lang.IllegalArgumentException: ELY05017: Token "SSL_ECDHE_RSA_WITH_AES_128_CBC_SHA" not allowed at offset 33 of mechanism selection string "SSL_ECDHE_RSA_WITH_AES_128_CBC_SHA"
> at org.wildfly.security.ssl.CipherSuiteSelector.fromString(CipherSuiteSelector.java:399)
> at org.wildfly.extension.undertow.HttpsListenerService.startListening(HttpsListenerService.java:125)
> at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:138)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> ... 3 more
> 16:55:25,598 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("https-listener" => "https")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.undertow.listener.https" => "org.jboss.msc.service.StartException in service jboss.undertow.listener.https: Failed to start service
> Caused by: java.lang.IllegalArgumentException: ELY05017: Token \"SSL_ECDHE_RSA_WITH_AES_128_CBC_SHA\" not allowed at offset 33 of mechanism selection string \"SSL_ECDHE_RSA_WITH_AES_128_CBC_SHA\""}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months