June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1227) Release WildFly Elytron 1.1.0.Beta51

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1227?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1227. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.1.0.Beta51 > ------------------------------------ > > Key: ELY-1227 > URL: https://issues.jboss.org/browse/ELY-1227 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta51 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8902) Upgrade ejb client to 4.0.0.Beta31

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-8902?page=com.atlassian.jira.plugin.... ] Farah Juma moved JBEAP-11388 to WFLY-8902: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8902 (was: JBEAP-11388) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: EJB (was: EJB) > Upgrade ejb client to 4.0.0.Beta31 > ---------------------------------- > > Key: WFLY-8902 > URL: https://issues.jboss.org/browse/WFLY-8902 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB > Reporter: Farah Juma > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-2) [QE] - JMAN4-112 - Cross-Link JBoss Middleware services to containers

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-2?page=com.atlassian.jira.plug... ] Hayk Hovsepyan resolved HAWKULARQE-2. ------------------------------------- Resolution: Done > [QE] - JMAN4-112 - Cross-Link JBoss Middleware services to containers > --------------------------------------------------------------------- > > Key: HAWKULARQE-2 > URL: https://issues.jboss.org/browse/HAWKULARQE-2 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Prachi Yadav > Priority: Blocker > Labels: mm-integration-hawkular-qe > > See [JMAN4-112|https://issues.jboss.org/browse/JMAN4-112] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8801) Legacy EJB client dependency in wildfly-feature-pack breaks AS TS

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8801?page=com.atlassian.jira.plugin.... ] Kabir Khan reassigned WFLY-8801: -------------------------------- Assignee: Kabir Khan > Legacy EJB client dependency in wildfly-feature-pack breaks AS TS > ----------------------------------------------------------------- > > Key: WFLY-8801 > URL: https://issues.jboss.org/browse/WFLY-8801 > Project: WildFly > Issue Type: Bug > Components: EJB, Test Suite > Reporter: Josef Cacek > Assignee: Kabir Khan > Priority: Critical > > The new jboss-ejb-client-legacy dependency in wildfly-feature-pack POM breaks AS TS client tests. Users can hit this issue if they define dependencies using the feature-pack pom. > {code:xml} > <dependency> > <groupId>org.wildfly</groupId> > <artifactId>wildfly-feature-pack</artifactId> > <type>pom</type> > </dependency> > {code} > The testsuite/shared has a dependency on wildfly-feature-pack POM which newly introduces the legacy EJB client dependency. (https://github.com/wildfly/wildfly/pull/10061/files) It results in classpath issues. > When I hit the issue in my test, the test prints just this exception and the testsuite run hangs forever: > {code} > Exception in thread "XNIO-1 task-14" java.lang.NoSuchMethodError: org.jboss.ejb.client.Affinity.forUri(Ljava/net/URI;)Lorg/jboss/ejb/client/Affinity; > at org.jboss.ejb.protocol.remote.ProtocolV3ObjectResolver.<init>(ProtocolV3ObjectResolver.java:43) > at org.jboss.ejb.protocol.remote.EJBMarshallingCompatibilityHelper.getObjectResolver(EJBMarshallingCompatibilityHelper.java:42) > at org.wildfly.naming.client.remote.RemoteClientTransport$1.handleMessage(RemoteClientTransport.java:155) > at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:434) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:897) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8488) Usage of JGroups JDBC_PING attempts to delete row too late

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8488?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-8488: -------------------------------------- [~meetoblivion] Yes, the WF11 (master) is still being actively worked on to be stabilized; best use nightly build. > Usage of JGroups JDBC_PING attempts to delete row too late > ---------------------------------------------------------- > > Key: WFLY-8488 > URL: https://issues.jboss.org/browse/WFLY-8488 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: John Ament > Assignee: Paul Ferraro > > I was recently working on spinning up a Keycloak cluster. We're deployed to AWS, can't leverage UDP and wanted to have a discovery mechanism that was easy to use, so tried out JDBC_PING. While I got the cluster running, when shutting down a node I would receive an exception on the console when attempting to remove the node from the cluster. It attempts to do a delete on the row in the database after the DataSource has been shut down. > In my setup, I'm pointing JGroups at the same DataSource as Keycloak, I'm not using the properties approach. I can switch to the properties approach, but I would prefer a single pool rather than multiple connections. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8901) Cache configuration containing a custom cache store triggers ISE

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-8901: ---------------------------------- Summary: Cache configuration containing a custom cache store triggers ISE Key: WFLY-8901 URL: https://issues.jboss.org/browse/WFLY-8901 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 11.0.0.Alpha1 Reporter: Paul Ferraro Assignee: Paul Ferraro {noformat} 10:23:36,899 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service org.wildfly.clustering.infinispan.cache.store.web.dist: org.jboss.msc.service.StartException in service org.wildfly.clustering.infinispan.cache.store.web.dist: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.IllegalStateException: ISPN000912: Expecting a protected configuration for AbstractStoreConfiguration at org.infinispan.commons.configuration.attributes.AttributeSet.checkProtection(AttributeSet.java:177) at org.infinispan.configuration.cache.AbstractStoreConfiguration.<init>(AbstractStoreConfiguration.java:65) at org.jboss.as.clustering.infinispan.subsystem.CustomStoreConfiguration.<init>(CustomStoreConfiguration.java:36) at org.jboss.as.clustering.infinispan.subsystem.CustomStoreConfigurationBuilder.create(CustomStoreConfigurationBuilder.java:40) at org.jboss.as.clustering.infinispan.subsystem.CustomStoreConfigurationBuilder.create(CustomStoreConfigurationBuilder.java:32) at org.infinispan.configuration.cache.PersistenceConfigurationBuilder.create(PersistenceConfigurationBuilder.java:146) at org.jboss.as.clustering.infinispan.subsystem.StoreBuilder.getValue(StoreBuilder.java:110) at org.jboss.as.clustering.infinispan.subsystem.CustomStoreBuilder.getValue(CustomStoreBuilder.java:70) at org.jboss.as.clustering.infinispan.subsystem.CustomStoreBuilder.getValue(CustomStoreBuilder.java:46) at org.jboss.msc.service.ValueService.start(ValueService.java:49) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) ... 3 more {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-15) [QE] - JMAN4-163 - Track EAP servers connecting to the middleware manager

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-15?page=com.atlassian.jira.plu... ] Matt Mahoney updated HAWKULARQE-15: ----------------------------------- Blocking bug verified fixed: EAP Images tested: eap64-openshift:1.5-8 eap70-openshift:1.5-9 > [QE] - JMAN4-163 - Track EAP servers connecting to the middleware manager > -------------------------------------------------------------------------- > > Key: HAWKULARQE-15 > URL: https://issues.jboss.org/browse/HAWKULARQE-15 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Matt Mahoney > Labels: mm-integration-hawkular-qe > > See [JMAN4-163|https://issues.jboss.org/browse/JMAN4-163] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-15) [QE] - JMAN4-163 - Track EAP servers connecting to the middleware manager

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-15?page=com.atlassian.jira.plu... ] Matt Mahoney resolved HAWKULARQE-15. ------------------------------------ Resolution: Done > [QE] - JMAN4-163 - Track EAP servers connecting to the middleware manager > -------------------------------------------------------------------------- > > Key: HAWKULARQE-15 > URL: https://issues.jboss.org/browse/HAWKULARQE-15 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Matt Mahoney > Labels: mm-integration-hawkular-qe > > See [JMAN4-163|https://issues.jboss.org/browse/JMAN4-163] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2923) Credential reference integration with client-certificate-store does not work

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2923?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet reassigned WFCORE-2923: ----------------------------------------- Assignee: ehsavoie Hugonnet (was: Darran Lofthouse) > Credential reference integration with client-certificate-store does not work > ---------------------------------------------------------------------------- > > Key: WFCORE-2923 > URL: https://issues.jboss.org/browse/WFCORE-2923 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: ehsavoie Hugonnet > Priority: Blocker > > By WFCORE-2483 there were introduced attributes {{keystore-password-credential-reference}} and {{key-password-credential-reference}} in resource {{client-certificate-store}}, which is used when syslog server requires client authentication during TLS handshake. > However this integration does not work. > Looking into SyslogAuditLogHandler.java I am missing credential reference retrieving code {{CredentialReference.getCredentialSourceSupplier}} > {code:java|title=SyslogAuditLogHandler.java} > if (transport == Transport.TLS){ > final SSLContext context = SSLContext.getInstance("TLS"); > KeyManager[] keyManagers = null; > if (tlsClientCertStorePath != null){ > final KeyManagerFactory kmf = KeyManagerFactory.getInstance(KeyManagerFactory.getDefaultAlgorithm()); > final FileInputStream in = new FileInputStream(pathManager.resolveRelativePathEntry(tlsClientCertStorePath, tlsClientCertStoreRelativeTo)); > try { > final KeyStore ks = KeyStore.getInstance("JKS"); > ks.load(in, tlsClientCertStorePassword.toCharArray()); > kmf.init(ks, tlsClientCertStoreKeyPassword != null ? tlsClientCertStoreKeyPassword.toCharArray() : tlsClientCertStorePassword.toCharArray()); > keyManagers = kmf.getKeyManagers(); > } finally { > IoUtils.safeClose(in); > } > } > TrustManager[] trustManagers = null; > if (tlsTrustStorePath != null){ > final TrustManagerFactory tmf = TrustManagerFactory.getInstance(TrustManagerFactory.getDefaultAlgorithm()); > final FileInputStream in = new FileInputStream(pathManager.resolveRelativePathEntry(tlsTrustStorePath, tlsTrustStoreRelativeTo)); > try { > final KeyStore ks = KeyStore.getInstance("JKS"); > ks.load(in, tlsTrustStorePassword.toCharArray()); > tmf.init(ks); > trustManagers = tmf.getTrustManagers(); > } finally { > IoUtils.safeClose(in); > } > } > {code} > Tes (Ignored) https://github.com/wildfly/wildfly-core/pull/2513 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6835) Vault.sh misleading output

by Radovan Stancel (JIRA)

[ https://issues.jboss.org/browse/WFLY-6835?page=com.atlassian.jira.plugin.... ] Radovan Stancel reassigned WFLY-6835: ------------------------------------- Assignee: Radovan Stancel (was: Peter Skopek) > 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: Radovan Stancel > 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 (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2017