June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3034) CLI with PKCS11 keystore cannot connect to server and throws java.security.KeyManagementException

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3034?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved JBEAP-11885 to WFCORE-3034: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3034 (was: JBEAP-11885) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: (was: 7.1.0.ER1) > CLI with PKCS11 keystore cannot connect to server and throws java.security.KeyManagementException > ------------------------------------------------------------------------------------------------- > > Key: WFCORE-3034 > URL: https://issues.jboss.org/browse/WFCORE-3034 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Labels: eap7.1-rfe-failure > Fix For: 3.0.0.Beta28 > > > When trying to connect with CLI to server using PKCS11 (and FIPS): > * CLI can connect with the old workaround described in 7.0 documentation > {code} > JAVA_OPTS="$JAVA_OPTS -Djavax.net.ssl.trustStore=NONE -Djavax.net.ssl.trustStoreType=PKCS11" > JAVA_OPTS="$JAVA_OPTS -Djavax.net.ssl.keyStore=NONE -Djavax.net.ssl.keyStoreType=PKCS11 -Djavax.net.ssl.keyStorePassword=imapassword" > {code} > * When providing -Dwildfly.config.url, no matter what's in the path (even if it's non-existent file), CLI throws following error: > {code} > java.security.KeyManagementException: FIPS mode: only SunJSSE TrustManagers may be used: FIPS mode: only SunJSSE TrustManagers may be used > {code} > * If I set up BOTH the JAVA_OPTS and wildfly-config.xml, the config is parsed properly (throwing errors in case of wrong path, malformed xml etc.) and CLI connects successfully. > I'm marking it as a blocker now, since this is basically the functionality required by EAP7-610. But the old workaround still works just fine, so I think this isn't high priority if we're ok to postpone the RFE. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3034) CLI with PKCS11 keystore cannot connect to server and throws java.security.KeyManagementException

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3034?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-3034: ------------------------------------- Fix Version/s: 3.0.0.Beta28 > CLI with PKCS11 keystore cannot connect to server and throws java.security.KeyManagementException > ------------------------------------------------------------------------------------------------- > > Key: WFCORE-3034 > URL: https://issues.jboss.org/browse/WFCORE-3034 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Labels: eap7.1-rfe-failure > Fix For: 3.0.0.Beta28 > > > When trying to connect with CLI to server using PKCS11 (and FIPS): > * CLI can connect with the old workaround described in 7.0 documentation > {code} > JAVA_OPTS="$JAVA_OPTS -Djavax.net.ssl.trustStore=NONE -Djavax.net.ssl.trustStoreType=PKCS11" > JAVA_OPTS="$JAVA_OPTS -Djavax.net.ssl.keyStore=NONE -Djavax.net.ssl.keyStoreType=PKCS11 -Djavax.net.ssl.keyStorePassword=imapassword" > {code} > * When providing -Dwildfly.config.url, no matter what's in the path (even if it's non-existent file), CLI throws following error: > {code} > java.security.KeyManagementException: FIPS mode: only SunJSSE TrustManagers may be used: FIPS mode: only SunJSSE TrustManagers may be used > {code} > * If I set up BOTH the JAVA_OPTS and wildfly-config.xml, the config is parsed properly (throwing errors in case of wrong path, malformed xml etc.) and CLI connects successfully. > I'm marking it as a blocker now, since this is basically the functionality required by EAP7-610. But the old workaround still works just fine, so I think this isn't high priority if we're ok to postpone the RFE. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity

by Nuno Godinho de Matos (JIRA)

[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ] Nuno Godinho de Matos commented on WFLY-8954: --------------------------------------------- Hi Scott, Have you guys decided on an appropriate approach to tackle this issue? Kindest regards. > Wildfly 10 with eclipselink Onscucess observer gets stale entity > ---------------------------------------------------------------- > > Key: WFLY-8954 > URL: https://issues.jboss.org/browse/WFLY-8954 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.Final > Reporter: Nuno Godinho de Matos > Assignee: Scott Marlow > > Hi, > In widlfly there seems to be an important issue concerning CDI events and observing these events during onsuccess. At least while using eclipselink. > When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an entity A, fires an event stating entity A has been modified, and an observer consumes this event during transaction success. > Then the observer will be working with stale entities that do not reflect the modifications done to the entity. > A sample application for this issue is available in: > https://github.com/99sono/wildfly10-observe-on-success-stale-entity > The widlfly configuration xml for the sample application, is available in the application itself, as can be seen in the readme documentation. > Many thanks for taking a look. > Kindest regards. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9031) Default session draining strategy should perform draining if last cluster member is leaving

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9031?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9031: --------------------------------- Priority: Major (was: Critical) > Default session draining strategy should perform draining if last cluster member is leaving > ------------------------------------------------------------------------------------------- > > Key: WFLY-9031 > URL: https://issues.jboss.org/browse/WFLY-9031 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 10.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Currently, the default session draining strategy consults implementation of org.jboss.modcluster.container.Context#isDistributable for whether session draining is enabled org.jboss.modcluster.config.impl.SessionDrainingStrategyEnum#isEnabled. In fact the method consulted should be checking for whether data is available on other nodes; since if the last member is leaving a data loss will occur. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9031) Default session draining strategy should perform draining if last cluster member is leaving

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9031?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9031: --------------------------------- Affects Version/s: 10.1.0.Final > Default session draining strategy should perform draining if last cluster member is leaving > ------------------------------------------------------------------------------------------- > > Key: WFLY-9031 > URL: https://issues.jboss.org/browse/WFLY-9031 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 10.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > Currently, the default session draining strategy consults implementation of org.jboss.modcluster.container.Context#isDistributable for whether session draining is enabled org.jboss.modcluster.config.impl.SessionDrainingStrategyEnum#isEnabled. In fact the method consulted should be checking for whether data is available on other nodes; since if the last member is leaving a data loss will occur. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9032) Default session draining strategy should perform draining if last cluster member is leaving

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-9032: ------------------------------------ Summary: Default session draining strategy should perform draining if last cluster member is leaving Key: WFLY-9032 URL: https://issues.jboss.org/browse/WFLY-9032 Project: WildFly Issue Type: Bug Components: mod_cluster Affects Versions: 10.1.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Critical Currently, the default session draining strategy consults implementation of org.jboss.modcluster.container.Context#isDistributable for whether session draining is enabled org.jboss.modcluster.config.impl.SessionDrainingStrategyEnum#isEnabled. In fact the method consulted should be checking for whether data is available on other nodes; since if the last member is leaving a data loss will occur. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9031) Default session draining strategy should perform draining if last cluster member is leaving

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9031?page=com.atlassian.jira.plugin.... ] Radoslav Husar moved MODCLUSTER-601 to WFLY-9031: ------------------------------------------------- Project: WildFly (was: mod_cluster) Key: WFLY-9031 (was: MODCLUSTER-601) Component/s: mod_cluster (was: Core & Container Integration (Java)) Affects Version/s: (was: 1.3.7.Final) > Default session draining strategy should perform draining if last cluster member is leaving > ------------------------------------------------------------------------------------------- > > Key: WFLY-9031 > URL: https://issues.jboss.org/browse/WFLY-9031 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > Currently, the default session draining strategy consults implementation of org.jboss.modcluster.container.Context#isDistributable for whether session draining is enabled org.jboss.modcluster.config.impl.SessionDrainingStrategyEnum#isEnabled. In fact the method consulted should be checking for whether data is available on other nodes; since if the last member is leaving a data loss will occur. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1643) Evaluate current code base for PMML and Score cards

by Lance Leverich (JIRA)

Lance Leverich created DROOLS-1643: -------------------------------------- Summary: Evaluate current code base for PMML and Score cards Key: DROOLS-1643 URL: https://issues.jboss.org/browse/DROOLS-1643 Project: Drools Issue Type: Sub-task Components: core engine Reporter: Lance Leverich Assignee: Lance Leverich Review and understand the current code base for PMML and Score cards. In particular, look for ways that the generated rules can be less complex. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9030) Cleaning after the build shouldn't fail if the removal of files doesn't succeed

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFLY-9030: --------------------------------------- Summary: Cleaning after the build shouldn't fail if the removal of files doesn't succeed Key: WFLY-9030 URL: https://issues.jboss.org/browse/WFLY-9030 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 11.0.0.Alpha1 Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet Priority: Minor [16:19:40][Step 4/5] [INFO] --- maven-clean-plugin:3.0.0:clean (clean-test-servers) @ wildfly-testsuite-integration-mixed-domain --- [16:19:40][Step 4/5] [INFO] Deleting C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\mixed-domain\target\jbossas (includes = [], excludes = [**/*.log]) [16:19:40][Step 4/5] [INFO] Deleting C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\mixed-domain\target\old-versions (includes = [], excludes = [**/*.log]) [16:19:42][Step 4/5] Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:3.0.0:clean (clean-test-servers) on project wildfly-testsuite-integration-mixed-domain: Failed to clean project: Failed to delete ... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9029) Cleaning after the build shouldn't fail if the removal of files doesn't succeed

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFLY-9029: --------------------------------------- Summary: Cleaning after the build shouldn't fail if the removal of files doesn't succeed Key: WFLY-9029 URL: https://issues.jboss.org/browse/WFLY-9029 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 11.0.0.Alpha1 Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet Priority: Minor [16:19:40][Step 4/5] [INFO] --- maven-clean-plugin:3.0.0:clean (clean-test-servers) @ wildfly-testsuite-integration-mixed-domain --- [16:19:40][Step 4/5] [INFO] Deleting C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\mixed-domain\target\jbossas (includes = [], excludes = [**/*.log]) [16:19:40][Step 4/5] [INFO] Deleting C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\mixed-domain\target\old-versions (includes = [], excludes = [**/*.log]) [16:19:42][Step 4/5] Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:3.0.0:clean (clean-test-servers) on project wildfly-testsuite-integration-mixed-domain: Failed to clean project: Failed to delete ... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

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