[JBoss JIRA] (ELY-1621) BC FIPS with CLI: the trustAnchors parameter must be non-empty
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1621?page=com.atlassian.jira.plugin.s... ]
Martin Choma commented on ELY-1621:
-----------------------------------
Just debugged server side and it behaves the same. Error havent occured just because truststore contains another certificate.
And I think BC behaves as documented. Because when I look into keystore it contains only one entry - PrivateKeyEntry, which contains certificate. BC ignores this as documented.
{code}
[mchoma@dhcp-10-40-4-105 bcfips_cli]$ keytool \
> -list\
> -keystore /home/mchoma/task/bcfips_cli/keystore.bcfks\
> -provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider\
> -providerpath /home/mchoma/.m2/repository/org/bouncycastle/fips/bc-fips/1.0.1/bc-fips-1.0.1.jar\
> -storetype BCFKS\
> -storepass password\
> -v
Keystore type: BCFKS
Keystore provider: BCFIPS
Your keystore contains 1 entry
Alias name: appserver
Creation date: Aug 2, 2018
Entry type: PrivateKeyEntry
Certificate chain length: 1
Certificate[1]:
Owner: CN=appserver, OU=QE, O=Redhat, L=Brno, ST=CR, C=CZ
Issuer: CN=appserver, OU=QE, O=Redhat, L=Brno, ST=CR, C=CZ
Serial number: 76e851f0
Valid from: Thu Aug 02 07:34:51 CEST 2018 until: Sat Aug 01 07:34:51 CEST 2020
Certificate fingerprints:
MD5: 67:16:51:BB:55:A9:53:F1:85:42:63:50:9D:CF:2A:7F
SHA1: 75:11:07:22:5A:F9:AB:F9:70:1A:8E:FD:BC:3B:A3:51:50:19:71:99
SHA256: 8A:B2:4D:88:F2:B6:64:2F:5D:A4:69:FF:6A:2A:64:F6:99:78:8E:80:2B:8E:7F:82:E4:C7:CC:91:9B:DD:02:1E
Signature algorithm name: SHA256WITHRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3
*******************************************
*******************************************
{code}
> BC FIPS with CLI: the trustAnchors parameter must be non-empty
> --------------------------------------------------------------
>
> Key: ELY-1621
> URL: https://issues.jboss.org/browse/ELY-1621
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.5.1.Final
> Reporter: Martin Choma
> Priority: Blocker
> Attachments: cli-test-wildfly-config.xml, jboss-cli.log, keystore.bcfks
>
>
> I am trying to connect from jboss-cli.sh to EAP server. To reproduce the problem it is enough BC FIPS is used only on client side.
> {code:java|titlejboss-cli.log}
> 08:13:18,469 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: java.lang.ExceptionInInitializerError
> at org.wildfly.security.auth.client.AuthenticationContext.lambda$static$0(AuthenticationContext.java:54)
> at org.wildfly.common.context.ContextManager.getPrivileged(ContextManager.java:286)
> at org.wildfly.security.auth.client.AuthenticationContext.captureCurrent(AuthenticationContext.java:86)
> at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:146)
> at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:291)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Caused by: org.wildfly.security.auth.client.InvalidAuthenticationConfigurationException: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:40)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.<clinit>(DefaultAuthenticationContextProvider.java:36)
> ... 14 more
> Caused by: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:525)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextRuleType$11(ElytronXmlParser.java:711)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseRulesType$13(ElytronXmlParser.java:749)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:356)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:231)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:192)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:38)
> ... 16 more
> Caused by: java.security.KeyStoreException: initialization failed
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:150)
> at javax.net.ssl.TrustManagerFactory.init(TrustManagerFactory.java:250)
> at org.wildfly.security.auth.client.ElytronXmlParser$TrustManagerBuilder.build(ElytronXmlParser.java:590)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:523)
> ... 22 more
> Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
> at java.security.cert.PKIXParameters.setTrustAnchors(PKIXParameters.java:200)
> at java.security.cert.PKIXParameters.<init>(PKIXParameters.java:120)
> at java.security.cert.PKIXBuilderParameters.<init>(PKIXBuilderParameters.java:104)
> at org.bouncycastle.jsse.provider.ProvX509TrustManagerImpl.<init>(ProvX509TrustManagerImpl.java:53)
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:146)
> ... 25 more
> {code}
> When I use non-FIPS java with CLI I can make it work. It does occure also when connecting to default unsecured port 9990.
> I have double check truststore is there. Correct password is used. Server has permission to open the truststure. And truststore contains certificate
> When I use BCFKS truststore on server side, e.g. in 2-way http communication it works.
> So it looks to me something on client side is missing? Any hint?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-79) java.lang.NoSuchMethodError: org.hibernate.type.AbstractSingleColumnStandardBasicType.replace(Ljava/lang/Object; Ljava/lang/Object; Lorg/hibernate/engine/spi/SessionImplementor; Ljava/lang/Object; Ljava/util/Map; )Ljava/lang/Object;
by Martin Simka (JIRA)
Martin Simka created WFWIP-79:
---------------------------------
Summary: java.lang.NoSuchMethodError: org.hibernate.type.AbstractSingleColumnStandardBasicType.replace(Ljava/lang/Object;Ljava/lang/Object;Lorg/hibernate/engine/spi/SessionImplementor;Ljava/lang/Object;Ljava/util/Map;)Ljava/lang/Object;
Key: WFWIP-79
URL: https://issues.jboss.org/browse/WFWIP-79
Project: WildFly WIP
Issue Type: Bug
Components: JPA
Reporter: Martin Simka
Assignee: Gail Badner
Priority: Blocker
it looks like I found another incompatibility in Type package.
{noformat}
java.lang.NoSuchMethodError: org.hibernate.type.AbstractSingleColumnStandardBasicType.replace(Ljava/lang/Object;Ljava/lang/Object;Lorg/hibernate/engine/spi/SessionImplementor;Ljava/lang/Object;Ljava/util/Map;)Ljava/lang/Object;
at org.hibernate.test.type.TypeTest.runBasicTests(TypeTest.java:366)
at org.hibernate.test.type.TypeTest.testBigDecimalType(TypeTest.java:99)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at org.hibernate.testing.junit4.ExtendedFrameworkMethod.invokeExplosively(ExtendedFrameworkMethod.java:45)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2708) Icon for test results dock
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2708?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2708:
-------------------------------------
[~Rikkola] Thanks, the icon is intended for the tab portion of the Results dock (when it's in place.)
> Icon for test results dock
> --------------------------
>
> Key: DROOLS-2708
> URL: https://issues.jboss.org/browse/DROOLS-2708
> Project: Drools
> Issue Type: Sub-task
> Components: Scenario Simulation and Testing, Test Scenarios Editor
> Reporter: Liz Clayton
> Assignee: Brian Dellascio
> Labels: UX, UXTeam, VisualDesign
>
> As a practitioner I need to know which docked tab indicates the Scenario Test results panel within the test editor.
> Notes:
> Icon needed for the right panel dock (functions as a tab) - same behavior as all Process Designer docks. Additional details outlined in icon spreadsheet and parent jira.
> Reasonable icon concept could be something like the font awesome "play-circle" icon: https://fontawesome.com/cheatsheet?from=io
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1621) BC FIPS with CLI: the trustAnchors parameter must be non-empty
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1621?page=com.atlassian.jira.plugin.s... ]
Martin Choma commented on ELY-1621:
-----------------------------------
[~rlucente-se-jboss] thank you for your input. This is interesting. Based on fact I see {{org.bouncycastle.jsse.provider.ProvX509TrustManagerImpl}} in stacktrace I would say yes I configured correctly to use BC TrustManager.
Unfortunetally I cant get into BCFIPSKeyStoreSpi while debugging, which would reveal what is going on. Now I would say something is strange with BC keystore there.
{code}
@Override
public boolean engineIsCertificateEntry(String alias)
{
ObjectData ent = entries.get(alias);
if (ent != null)
{
return ent.getType().equals(CERTIFICATE);
}
return false;
}
{code}
> BC FIPS with CLI: the trustAnchors parameter must be non-empty
> --------------------------------------------------------------
>
> Key: ELY-1621
> URL: https://issues.jboss.org/browse/ELY-1621
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.5.1.Final
> Reporter: Martin Choma
> Priority: Blocker
> Attachments: cli-test-wildfly-config.xml, jboss-cli.log, keystore.bcfks
>
>
> I am trying to connect from jboss-cli.sh to EAP server. To reproduce the problem it is enough BC FIPS is used only on client side.
> {code:java|titlejboss-cli.log}
> 08:13:18,469 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: java.lang.ExceptionInInitializerError
> at org.wildfly.security.auth.client.AuthenticationContext.lambda$static$0(AuthenticationContext.java:54)
> at org.wildfly.common.context.ContextManager.getPrivileged(ContextManager.java:286)
> at org.wildfly.security.auth.client.AuthenticationContext.captureCurrent(AuthenticationContext.java:86)
> at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:146)
> at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:291)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Caused by: org.wildfly.security.auth.client.InvalidAuthenticationConfigurationException: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:40)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.<clinit>(DefaultAuthenticationContextProvider.java:36)
> ... 14 more
> Caused by: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:525)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextRuleType$11(ElytronXmlParser.java:711)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseRulesType$13(ElytronXmlParser.java:749)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:356)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:231)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:192)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:38)
> ... 16 more
> Caused by: java.security.KeyStoreException: initialization failed
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:150)
> at javax.net.ssl.TrustManagerFactory.init(TrustManagerFactory.java:250)
> at org.wildfly.security.auth.client.ElytronXmlParser$TrustManagerBuilder.build(ElytronXmlParser.java:590)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:523)
> ... 22 more
> Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
> at java.security.cert.PKIXParameters.setTrustAnchors(PKIXParameters.java:200)
> at java.security.cert.PKIXParameters.<init>(PKIXParameters.java:120)
> at java.security.cert.PKIXBuilderParameters.<init>(PKIXBuilderParameters.java:104)
> at org.bouncycastle.jsse.provider.ProvX509TrustManagerImpl.<init>(ProvX509TrustManagerImpl.java:53)
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:146)
> ... 25 more
> {code}
> When I use non-FIPS java with CLI I can make it work. It does occure also when connecting to default unsecured port 9990.
> I have double check truststore is there. Correct password is used. Server has permission to open the truststure. And truststore contains certificate
> When I use BCFKS truststore on server side, e.g. in 2-way http communication it works.
> So it looks to me something on client side is missing? Any hint?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1621) BC FIPS with CLI: the trustAnchors parameter must be non-empty
by Rich Lucente (JIRA)
[ https://issues.jboss.org/browse/ELY-1621?page=com.atlassian.jira.plugin.s... ]
Rich Lucente commented on ELY-1621:
-----------------------------------
I hope I'm tracking the discussion here ... I guess this makes sense to me if I have a canonically issued certificate where on the server side the keystore contains the server certificate and key; the server truststore contains the intermediate CA (optionally, that signed the server certificate and any client potential certificates) and the root CA certificate (optionally, that signed either the server/client certificates or the intermediate CA). On the client side, the truststore would contain the root CA and the keystore would include the client certificate and key.
I know our docs discuss self-signed certificates in all the examples, but none of my customers actually do that. So truststores only containing intermediate or root CA certificates makes sense to me.
> BC FIPS with CLI: the trustAnchors parameter must be non-empty
> --------------------------------------------------------------
>
> Key: ELY-1621
> URL: https://issues.jboss.org/browse/ELY-1621
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.5.1.Final
> Reporter: Martin Choma
> Priority: Blocker
> Attachments: cli-test-wildfly-config.xml, jboss-cli.log, keystore.bcfks
>
>
> I am trying to connect from jboss-cli.sh to EAP server. To reproduce the problem it is enough BC FIPS is used only on client side.
> {code:java|titlejboss-cli.log}
> 08:13:18,469 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: java.lang.ExceptionInInitializerError
> at org.wildfly.security.auth.client.AuthenticationContext.lambda$static$0(AuthenticationContext.java:54)
> at org.wildfly.common.context.ContextManager.getPrivileged(ContextManager.java:286)
> at org.wildfly.security.auth.client.AuthenticationContext.captureCurrent(AuthenticationContext.java:86)
> at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:146)
> at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:291)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Caused by: org.wildfly.security.auth.client.InvalidAuthenticationConfigurationException: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:40)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.<clinit>(DefaultAuthenticationContextProvider.java:36)
> ... 14 more
> Caused by: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:525)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextRuleType$11(ElytronXmlParser.java:711)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseRulesType$13(ElytronXmlParser.java:749)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:356)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:231)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:192)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:38)
> ... 16 more
> Caused by: java.security.KeyStoreException: initialization failed
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:150)
> at javax.net.ssl.TrustManagerFactory.init(TrustManagerFactory.java:250)
> at org.wildfly.security.auth.client.ElytronXmlParser$TrustManagerBuilder.build(ElytronXmlParser.java:590)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:523)
> ... 22 more
> Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
> at java.security.cert.PKIXParameters.setTrustAnchors(PKIXParameters.java:200)
> at java.security.cert.PKIXParameters.<init>(PKIXParameters.java:120)
> at java.security.cert.PKIXBuilderParameters.<init>(PKIXBuilderParameters.java:104)
> at org.bouncycastle.jsse.provider.ProvX509TrustManagerImpl.<init>(ProvX509TrustManagerImpl.java:53)
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:146)
> ... 25 more
> {code}
> When I use non-FIPS java with CLI I can make it work. It does occure also when connecting to default unsecured port 9990.
> I have double check truststore is there. Correct password is used. Server has permission to open the truststure. And truststore contains certificate
> When I use BCFKS truststore on server side, e.g. in 2-way http communication it works.
> So it looks to me something on client side is missing? Any hint?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10782) IllegalArgumentException from messaging-activemq after migration from EAP 6.4.x
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10782?page=com.atlassian.jira.plugin... ]
Petr Kremensky updated WFLY-10782:
----------------------------------
Description:
Trying to boot the server with configuration migrated from EAP 6.4.x fails with {{IllegalArgumentException: Cannot require dependency more than once:service jboss.binding.messaging-throughput}}.
*Reproduce*
{noformat}
WORKSPACE=`pwd`
CONFIG=standalone-full.xml
unzip -q jboss-eap-6.4.20.zip
cp -r ${WILDFLY}/dist/target/wildfly-14.0.0.Beta2-SNAPSHOT wildfly
SOURCE_HOME=${WORKSPACE}/jboss-eap-6.4
TARGET_HOME=${WORKSPACE}/wildfly
cp ${SOURCE_HOME}/standalone/configuration/${CONFIG} ${TARGET_HOME}/standalone/configuration
${TARGET_HOME}/bin/standalone.sh -c ${CONFIG} --start-mode=admin-only &
${TARGET_HOME}/bin/jboss-cli.sh --connect --controller=remote://localhost:9999
# Migrate
/subsystem=jacorb:migrate
/subsystem=messaging:migrate
/subsystem=web:migrate
/subsystem=cmp:remove
/extension=org.jboss.as.cmp:remove
/subsystem=jaxr:remove
/extension=org.jboss.as.jaxr:remove
/subsystem=threads:remove
/extension=org.jboss.as.threads:remove
reload
{noformat}
*Outcome*
{noformat}
12:39:40,016 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 47) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "messaging-activemq"),
("server" => "default")
]): java.lang.IllegalArgumentException: Cannot require dependency more than once:service jboss.binding.messaging-throughput
{noformat}
*Attachments:*
[^standalone-full-6.4.20.xml] - out-of-box 6.4.20 config file
[^standalone-full-wildfly.xml] - out-of-box Wildfly 32910b3 (Thu Aug 2 10:49:25 CEST 2018) config file
[^standalone-full-6.4.20-to-wildfly.xml] - configuration produced by migration
This was working with 01852ab revision (Mon Jul 16 07:41:15 CEST 2018), unfortunately my automation for migration tool testing (which helps me to hit the issue) was broken due to galleon2 move, so without more investigation involved I'm unable to tell precise date when the issue appeared.
The issue is regression thus marking as a blocker.
was:
Trying to boot the server with configuration migrated from EAP 6.4.x fails with {{IllegalArgumentException: Cannot require dependency more than once:service jboss.binding.messaging-throughput}}.
*Reproduce*
{noformat}
WORKSPACE=`pwd`
CONFIG=standalone-full.xml
unzip -q jboss-eap-6.4.20.zip
cp -r ${WILDFLY}/dist/target/wildfly-14.0.0.Beta2-SNAPSHOT wildfly
SOURCE_HOME=${WORKSPACE}/jboss-eap-6.4
TARGET_HOME=${WORKSPACE}/wildfly
cp ${SOURCE_HOME}/standalone/configuration/${CONFIG} ${TARGET_HOME}/standalone/configuration
${TARGET_HOME}/bin/standalone.sh -c ${CONFIG} --start-mode=admin-only &
${TARGET_HOME}/bin/jboss-cli.sh --connect --controller=remote://localhost:9999
# Migrate
/subsystem=jacorb:migrate
/subsystem=messaging:migrate
/subsystem=web:migrate
/subsystem=cmp:remove
/extension=org.jboss.as.cmp:remove
/subsystem=jaxr:remove
/extension=org.jboss.as.jaxr:remove
/subsystem=threads:remove
/extension=org.jboss.as.threads:remove
reload
{noformat}
*Outcome*
{noformat}
12:39:40,016 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 47) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "messaging-activemq"),
("server" => "default")
]): java.lang.IllegalArgumentException: Cannot require dependency more than once:service jboss.binding.messaging-throughput
{noformat}
*Attachments:*
[^standalone-full-6.4.20.xml] - out-of-box 6.4.20 config file
[^standalone-full-wildfly.xml] - out-of-box Wildfly 32910b3 (Thu Aug 2 10:49:25 CEST 2018) config file
[^standalone-full-6.4.20-to-wildfly.xml] - configuration produced by migration
This was working with 01852ab revision (Mon Jul 16 07:41:15 CEST 2018), unfortunately my automation was broken due to galleon2 move, so without more investigation involved I'm unable to tell precise date when the issue appeared.
The issue is regression thus marking as a blocker.
> IllegalArgumentException from messaging-activemq after migration from EAP 6.4.x
> -------------------------------------------------------------------------------
>
> Key: WFLY-10782
> URL: https://issues.jboss.org/browse/WFLY-10782
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Migration
> Environment: {noformat}
> ../wildfly] $ git rev-parse --short HEAD
> 0236eda5a2
> {noformat}
> Reporter: Petr Kremensky
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: standalone-full-6.4.20-to-wildfly.xml, standalone-full-6.4.20.xml, standalone-full-wildfly.xml
>
>
> Trying to boot the server with configuration migrated from EAP 6.4.x fails with {{IllegalArgumentException: Cannot require dependency more than once:service jboss.binding.messaging-throughput}}.
>
> *Reproduce*
> {noformat}
> WORKSPACE=`pwd`
> CONFIG=standalone-full.xml
> unzip -q jboss-eap-6.4.20.zip
> cp -r ${WILDFLY}/dist/target/wildfly-14.0.0.Beta2-SNAPSHOT wildfly
> SOURCE_HOME=${WORKSPACE}/jboss-eap-6.4
> TARGET_HOME=${WORKSPACE}/wildfly
> cp ${SOURCE_HOME}/standalone/configuration/${CONFIG} ${TARGET_HOME}/standalone/configuration
> ${TARGET_HOME}/bin/standalone.sh -c ${CONFIG} --start-mode=admin-only &
> ${TARGET_HOME}/bin/jboss-cli.sh --connect --controller=remote://localhost:9999
> # Migrate
> /subsystem=jacorb:migrate
> /subsystem=messaging:migrate
> /subsystem=web:migrate
> /subsystem=cmp:remove
> /extension=org.jboss.as.cmp:remove
> /subsystem=jaxr:remove
> /extension=org.jboss.as.jaxr:remove
> /subsystem=threads:remove
> /extension=org.jboss.as.threads:remove
> reload
> {noformat}
>
> *Outcome*
> {noformat}
> 12:39:40,016 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 47) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default")
> ]): java.lang.IllegalArgumentException: Cannot require dependency more than once:service jboss.binding.messaging-throughput
> {noformat}
>
> *Attachments:*
> [^standalone-full-6.4.20.xml] - out-of-box 6.4.20 config file
> [^standalone-full-wildfly.xml] - out-of-box Wildfly 32910b3 (Thu Aug 2 10:49:25 CEST 2018) config file
> [^standalone-full-6.4.20-to-wildfly.xml] - configuration produced by migration
>
> This was working with 01852ab revision (Mon Jul 16 07:41:15 CEST 2018), unfortunately my automation for migration tool testing (which helps me to hit the issue) was broken due to galleon2 move, so without more investigation involved I'm unable to tell precise date when the issue appeared.
> The issue is regression thus marking as a blocker.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1621) BC FIPS with CLI: the trustAnchors parameter must be non-empty
by Rich Lucente (JIRA)
[ https://issues.jboss.org/browse/ELY-1621?page=com.atlassian.jira.plugin.s... ]
Rich Lucente commented on ELY-1621:
-----------------------------------
I remember reading Section 2.2 of BC-FJA-(D)TLSUserGuide-1.0.5.pdf which states "The TrustManagers produced by the BCJSSE provider will ignore private keys in any KeyStores passed into to their factories. Only simple certificate entries in a KeyStore will be used to create a TrustManager." Are we using the BCJSSE TrustManagers?
> BC FIPS with CLI: the trustAnchors parameter must be non-empty
> --------------------------------------------------------------
>
> Key: ELY-1621
> URL: https://issues.jboss.org/browse/ELY-1621
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.5.1.Final
> Reporter: Martin Choma
> Priority: Blocker
> Attachments: cli-test-wildfly-config.xml, jboss-cli.log, keystore.bcfks
>
>
> I am trying to connect from jboss-cli.sh to EAP server. To reproduce the problem it is enough BC FIPS is used only on client side.
> {code:java|titlejboss-cli.log}
> 08:13:18,469 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: java.lang.ExceptionInInitializerError
> at org.wildfly.security.auth.client.AuthenticationContext.lambda$static$0(AuthenticationContext.java:54)
> at org.wildfly.common.context.ContextManager.getPrivileged(ContextManager.java:286)
> at org.wildfly.security.auth.client.AuthenticationContext.captureCurrent(AuthenticationContext.java:86)
> at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:146)
> at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:291)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Caused by: org.wildfly.security.auth.client.InvalidAuthenticationConfigurationException: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:40)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.<clinit>(DefaultAuthenticationContextProvider.java:36)
> ... 14 more
> Caused by: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:525)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextRuleType$11(ElytronXmlParser.java:711)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseRulesType$13(ElytronXmlParser.java:749)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:356)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:231)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:192)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:38)
> ... 16 more
> Caused by: java.security.KeyStoreException: initialization failed
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:150)
> at javax.net.ssl.TrustManagerFactory.init(TrustManagerFactory.java:250)
> at org.wildfly.security.auth.client.ElytronXmlParser$TrustManagerBuilder.build(ElytronXmlParser.java:590)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:523)
> ... 22 more
> Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
> at java.security.cert.PKIXParameters.setTrustAnchors(PKIXParameters.java:200)
> at java.security.cert.PKIXParameters.<init>(PKIXParameters.java:120)
> at java.security.cert.PKIXBuilderParameters.<init>(PKIXBuilderParameters.java:104)
> at org.bouncycastle.jsse.provider.ProvX509TrustManagerImpl.<init>(ProvX509TrustManagerImpl.java:53)
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:146)
> ... 25 more
> {code}
> When I use non-FIPS java with CLI I can make it work. It does occure also when connecting to default unsecured port 9990.
> I have double check truststore is there. Correct password is used. Server has permission to open the truststure. And truststore contains certificate
> When I use BCFKS truststore on server side, e.g. in 2-way http communication it works.
> So it looks to me something on client side is missing? Any hint?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1623) BC FIPS FipsOperationError: Module checksum failed: entry
by Martin Choma (JIRA)
Martin Choma created ELY-1623:
---------------------------------
Summary: BC FIPS FipsOperationError: Module checksum failed: entry
Key: ELY-1623
URL: https://issues.jboss.org/browse/ELY-1623
Project: WildFly Elytron
Issue Type: Bug
Components: SSL
Affects Versions: 1.5.1.Final
Reporter: Martin Choma
Priority: Trivial
In tests I am registering bc providers for EAP server using {{-Djava.ext.dirs}} system property. When this folder contains two jars bc-fips-1.0.1.jar and bc-fips-debug-1.0.1.jar I get exception
{code}
Exception in thread "main" org.bouncycastle.crypto.fips.FipsOperationError: Module checksum failed: entry
at org.bouncycastle.crypto.fips.FipsStatus.checksumValidate(Unknown Source)
at org.bouncycastle.crypto.fips.FipsStatus.isReady(Unknown Source)
at org.bouncycastle.crypto.CryptoServicesRegistrar.getDefaultMode(Unknown Source)
at org.bouncycastle.crypto.CryptoServicesRegistrar.<clinit>(Unknown Source)
at org.bouncycastle.jcajce.provider.ProvSecureHash$MD5.configure(Unknown Source)
at org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider.<init>(Unknown Source)
at org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider.<init>(Unknown Source)
at org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider.<init>(Unknown Source)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:221)
at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:206)
at java.security.AccessController.doPrivileged(Native Method)
at sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:206)
at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:187)
at sun.security.jca.ProviderList.loadAll(ProviderList.java:282)
at sun.security.jca.ProviderList.removeInvalid(ProviderList.java:299)
at sun.security.jca.Providers.getFullProviderList(Providers.java:173)
at java.security.Security.insertProviderAt(Security.java:360)
at java.security.Security.addProvider(Security.java:403)
at org.jboss.modules.Main$AddProviderAction.run(Main.java:667)
at org.jboss.modules.Main$AddProviderAction.run(Main.java:659)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.modules.Main.main(Main.java:576)
Caused by: java.lang.NullPointerException: entry
at java.util.zip.ZipFile.getInputStream(ZipFile.java:361)
at java.util.jar.JarFile.getInputStream(JarFile.java:447)
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10782) IllegalArgumentException from messaging-activemq after migration from EAP 6.4.x
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10782?page=com.atlassian.jira.plugin... ]
Petr Kremensky updated WFLY-10782:
----------------------------------
Environment:
{noformat}
../wildfly] $ git rev-parse --short HEAD
0236eda5a2
{noformat}
> IllegalArgumentException from messaging-activemq after migration from EAP 6.4.x
> -------------------------------------------------------------------------------
>
> Key: WFLY-10782
> URL: https://issues.jboss.org/browse/WFLY-10782
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Migration
> Environment: {noformat}
> ../wildfly] $ git rev-parse --short HEAD
> 0236eda5a2
> {noformat}
> Reporter: Petr Kremensky
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: standalone-full-6.4.20-to-wildfly.xml, standalone-full-6.4.20.xml, standalone-full-wildfly.xml
>
>
> Trying to boot the server with configuration migrated from EAP 6.4.x fails with {{IllegalArgumentException: Cannot require dependency more than once:service jboss.binding.messaging-throughput}}.
>
> *Reproduce*
> {noformat}
> WORKSPACE=`pwd`
> CONFIG=standalone-full.xml
> unzip -q jboss-eap-6.4.20.zip
> cp -r ${WILDFLY}/dist/target/wildfly-14.0.0.Beta2-SNAPSHOT wildfly
> SOURCE_HOME=${WORKSPACE}/jboss-eap-6.4
> TARGET_HOME=${WORKSPACE}/wildfly
> cp ${SOURCE_HOME}/standalone/configuration/${CONFIG} ${TARGET_HOME}/standalone/configuration
> ${TARGET_HOME}/bin/standalone.sh -c ${CONFIG} --start-mode=admin-only &
> ${TARGET_HOME}/bin/jboss-cli.sh --connect --controller=remote://localhost:9999
> # Migrate
> /subsystem=jacorb:migrate
> /subsystem=messaging:migrate
> /subsystem=web:migrate
> /subsystem=cmp:remove
> /extension=org.jboss.as.cmp:remove
> /subsystem=jaxr:remove
> /extension=org.jboss.as.jaxr:remove
> /subsystem=threads:remove
> /extension=org.jboss.as.threads:remove
> reload
> {noformat}
>
> *Outcome*
> {noformat}
> 12:39:40,016 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 47) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default")
> ]): java.lang.IllegalArgumentException: Cannot require dependency more than once:service jboss.binding.messaging-throughput
> {noformat}
>
> *Attachments:*
> [^standalone-full-6.4.20.xml] - out-of-box 6.4.20 config file
> [^standalone-full-wildfly.xml] - out-of-box Wildfly 32910b3 (Thu Aug 2 10:49:25 CEST 2018) config file
> [^standalone-full-6.4.20-to-wildfly.xml] - configuration produced by migration
>
> This was working with 01852ab revision (Mon Jul 16 07:41:15 CEST 2018), unfortunately my automation was broken due to galleon2 move, so without more investigation involved I'm unable to tell precise date when the issue appeared.
> The issue is regression thus marking as a blocker.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10783) ChannelServiceConfigurator failed to open a port while deploying kitchenskink qs on migrated server
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10783?page=com.atlassian.jira.plugin... ]
Petr Kremensky updated WFLY-10783:
----------------------------------
Environment:
{noformat}
../wildfly] $ git rev-parse --short HEAD
0236eda5a2
{noformat}
> ChannelServiceConfigurator failed to open a port while deploying kitchenskink qs on migrated server
> ---------------------------------------------------------------------------------------------------
>
> Key: WFLY-10783
> URL: https://issues.jboss.org/browse/WFLY-10783
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Migration
> Environment: {noformat}
> ../wildfly] $ git rev-parse --short HEAD
> 0236eda5a2
> {noformat}
> Reporter: Petr Kremensky
> Assignee: Paul Ferraro
> Priority: Blocker
> Attachments: jboss-kitchensink.war
>
>
> Trying to deploy kitchensink quickstart on the server with configuration migrated from EAP 6.4.x fails with {{java.lang.IllegalStateException: java.lang.Exception: failed to open a port in range 55200-55200}}.
> *Reproduce*
> {noformat}
> WORKSPACE=`pwd`
> CONFIG=standalone-ha.xml
> unzip -q jboss-eap-6.4.20.zip
> cp -r ${WILDFLY}/dist/target/wildfly-14.0.0.Beta2-SNAPSHOT wildfly
> SOURCE_HOME=${WORKSPACE}/jboss-eap-6.4
> TARGET_HOME=${WORKSPACE}/wildfly
> cp ${SOURCE_HOME}/standalone/configuration/${CONFIG} ${TARGET_HOME}/standalone/configuration
> ${TARGET_HOME}/bin/standalone.sh -c ${CONFIG} --start-mode=admin-only &
> ${TARGET_HOME}/bin/jboss-cli.sh --connect --controller=remote://localhost:9999
> # Migrate
> /subsystem=web:migrate
> /subsystem=threads:remove
> /extension=org.jboss.as.threads:remove
> reload
> deploy jboss-kitchensink.war
> {noformat}
>
> *Outcome*
> {noformat}
> 14:44:13,799 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 56) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee-ejb: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee-ejb: java.lang.IllegalStateException: java.lang.Exception: failed to open a port in range 55200-55200
> at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:70) [wildfly-clustering-service-14.0.0.Beta2-SNAPSHOT.jar:14.0.0.Beta2-SNAPSHOT]
> at org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117) [wildfly-clustering-service-14.0.0.Beta2-SNAPSHOT.jar:14.0.0.Beta2-SNAPSHOT]
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171]
> at org.jboss.threads.JBossThread.run(JBossThread.java:485) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> Caused by: java.lang.IllegalStateException: java.lang.Exception: failed to open a port in range 55200-55200
> at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:116)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:58)
> at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:67) [wildfly-clustering-service-14.0.0.Beta2-SNAPSHOT.jar:14.0.0.Beta2-SNAPSHOT]
> ... 7 more
> Caused by: java.lang.Exception: failed to open a port in range 55200-55200
> at org.jgroups.protocols.UDP.createMulticastSocketWithBindPort(UDP.java:519)
> at org.jgroups.protocols.UDP.createSockets(UDP.java:357)
> at org.jgroups.protocols.UDP.start(UDP.java:300)
> at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:861)
> at org.jgroups.JChannel.startStack(JChannel.java:1023)
> at org.jgroups.JChannel._preConnect(JChannel.java:886)
> at org.jgroups.JChannel.connect(JChannel.java:390)
> at org.jgroups.JChannel.connect(JChannel.java:384)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:112)
> ... 9 more
> {noformat}
> This works fine with EAP 7.1.3 as a TARGET_SERVER, thus marking as a blocker due to a regression.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months