November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12759) Extract microprofile-config galleon layer from observability.

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12759?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12759: ----------------------------------------- He who files a PR wins :) . WFLY-12723 > Extract microprofile-config galleon layer from observability. > ------------------------------------------------------------- > > Key: WFLY-12759 > URL: https://issues.jboss.org/browse/WFLY-12759 > Project: WildFly > Issue Type: Task > Components: Build System > Affects Versions: 18.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Some microprofile extensions only depend on microprofile-config and not health or metrics. Splitting this into a separate layer will accommodate layers for other microprofile specs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12759) Extract microprofile-config galleon layer from observability.

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12759?page=com.atlassian.jira.plugin... ] Paul Ferraro reassigned WFLY-12759: ----------------------------------- Assignee: Paul Ferraro (was: Brian Stansberry) > Extract microprofile-config galleon layer from observability. > ------------------------------------------------------------- > > Key: WFLY-12759 > URL: https://issues.jboss.org/browse/WFLY-12759 > Project: WildFly > Issue Type: Task > Components: Build System > Affects Versions: 18.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Some microprofile extensions only depend on microprofile-config and not health or metrics. Splitting this into a separate layer will accommodate layers for other microprofile specs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3739) [IBM JDK] Unable to start server with FIPS Bouncy Castle

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-3739?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-3739: ---------------------------------- Labels: (was: OpenJ9) > [IBM JDK] Unable to start server with FIPS Bouncy Castle > -------------------------------------------------------- > > Key: WFCORE-3739 > URL: https://issues.jboss.org/browse/WFCORE-3739 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 5.0.0.Alpha2 > Environment: java -version > java version "1.8.0_161" > Java(TM) SE Runtime Environment (build 8.0.5.10 - pxa6480sr5fp10-20180214_01(SR5 FP10)) > IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64 Compressed References 20180208_378436 (JIT enabled, AOT enabled) > OpenJ9 - 39bb844 > OMR - c04ccb2 > IBM - 2321a81) > JCL - 20180209_01 based on Oracle jdk8u161-b12 > Reporter: Martin Choma > Priority: Major > > {code} > 18:09:45,494 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.as: org.jboss.msc.service.StartException in service jboss.as: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1706) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:811) > Caused by: java.lang.IllegalStateException: WFLYDR0005: Cannot obtain SHA-1 MessageDigest > at org.jboss.as.repository.ContentRepositoryImpl.<init>(ContentRepositoryImpl.java:92) > at org.jboss.as.repository.ContentRepository$Factory.addService(ContentRepository.java:185) > at org.jboss.as.server.ApplicationServerService.start(ApplicationServerService.java:145) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > ... 6 more > Caused by: java.security.NoSuchAlgorithmException: SHA-1 MessageDigest not available > at sun.security.jca.GetInstance.getInstance(GetInstance.java:171) > at java.security.Security.getImpl(Security.java:706) > at java.security.MessageDigest.getInstance(MessageDigest.java:178) > at org.jboss.as.repository.ContentRepositoryImpl.<init>(ContentRepositoryImpl.java:90) > ... 10 more > {code} > SHA-1 is hardcoded in server, which apparently is not available in FIPS BC. > {code:java|title=ContentRepositoryImpl.java} > protected ContentRepositoryImpl(final File repoRoot, final File tmpRoot, long obsolescenceTimeout, long lockTimeout) { > Assert.checkNotNullParam("repoRoot", repoRoot); > Assert.checkNotNullParam("tmpRoot", tmpRoot); > checkDirectory(repoRoot); > this.repoRoot = repoRoot; > checkDirectory(tmpRoot); > this.tmpRoot = tmpRoot; > this.obsolescenceTimeout = obsolescenceTimeout; > this.lockTimeout = lockTimeout; > try { > this.messageDigest = MessageDigest.getInstance("SHA-1"); > } catch (NoSuchAlgorithmException e) { > throw DeploymentRepositoryLogger.ROOT_LOGGER.cannotObtainSha1(e, MessageDigest.class.getSimpleName()); > } > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12759) Extract microprofile-config galleon layer from observability.

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12759: ----------------------------------- Summary: Extract microprofile-config galleon layer from observability. Key: WFLY-12759 URL: https://issues.jboss.org/browse/WFLY-12759 Project: WildFly Issue Type: Task Components: Build System Affects Versions: 18.0.0.Final Reporter: Paul Ferraro Assignee: Brian Stansberry Some microprofile extensions only depend on microprofile-config and not health or metrics. Splitting this into a separate layer will accommodate layers for other microprofile specs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3739) [IBM JDK] Unable to start server with FIPS Bouncy Castle

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-3739?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-3739: --------------------------------------- [~mchoma] I think we could probably close this. I tried this with OpenJ9 + OpenJDK 8 and didn't have any issues starting WildFly. > [IBM JDK] Unable to start server with FIPS Bouncy Castle > -------------------------------------------------------- > > Key: WFCORE-3739 > URL: https://issues.jboss.org/browse/WFCORE-3739 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 5.0.0.Alpha2 > Environment: java -version > java version "1.8.0_161" > Java(TM) SE Runtime Environment (build 8.0.5.10 - pxa6480sr5fp10-20180214_01(SR5 FP10)) > IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64 Compressed References 20180208_378436 (JIT enabled, AOT enabled) > OpenJ9 - 39bb844 > OMR - c04ccb2 > IBM - 2321a81) > JCL - 20180209_01 based on Oracle jdk8u161-b12 > Reporter: Martin Choma > Priority: Major > Labels: OpenJ9 > > {code} > 18:09:45,494 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.as: org.jboss.msc.service.StartException in service jboss.as: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1706) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:811) > Caused by: java.lang.IllegalStateException: WFLYDR0005: Cannot obtain SHA-1 MessageDigest > at org.jboss.as.repository.ContentRepositoryImpl.<init>(ContentRepositoryImpl.java:92) > at org.jboss.as.repository.ContentRepository$Factory.addService(ContentRepository.java:185) > at org.jboss.as.server.ApplicationServerService.start(ApplicationServerService.java:145) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > ... 6 more > Caused by: java.security.NoSuchAlgorithmException: SHA-1 MessageDigest not available > at sun.security.jca.GetInstance.getInstance(GetInstance.java:171) > at java.security.Security.getImpl(Security.java:706) > at java.security.MessageDigest.getInstance(MessageDigest.java:178) > at org.jboss.as.repository.ContentRepositoryImpl.<init>(ContentRepositoryImpl.java:90) > ... 10 more > {code} > SHA-1 is hardcoded in server, which apparently is not available in FIPS BC. > {code:java|title=ContentRepositoryImpl.java} > protected ContentRepositoryImpl(final File repoRoot, final File tmpRoot, long obsolescenceTimeout, long lockTimeout) { > Assert.checkNotNullParam("repoRoot", repoRoot); > Assert.checkNotNullParam("tmpRoot", tmpRoot); > checkDirectory(repoRoot); > this.repoRoot = repoRoot; > checkDirectory(tmpRoot); > this.tmpRoot = tmpRoot; > this.obsolescenceTimeout = obsolescenceTimeout; > this.lockTimeout = lockTimeout; > try { > this.messageDigest = MessageDigest.getInstance("SHA-1"); > } catch (NoSuchAlgorithmException e) { > throw DeploymentRepositoryLogger.ROOT_LOGGER.cannotObtainSha1(e, MessageDigest.class.getSimpleName()); > } > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4730) Scenario description column appears on breakdown tab when creating DMN based scenario

by Anna Dupliak (Jira)

Anna Dupliak created DROOLS-4730: ------------------------------------ Summary: Scenario description column appears on breakdown tab when creating DMN based scenario Key: DROOLS-4730 URL: https://issues.jboss.org/browse/DROOLS-4730 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Affects Versions: 7.29.0.Final Reporter: Anna Dupliak Assignee: Gabriele Cardosi Attachments: Traffic Violation Rules.dmn, image-2019-11-05-18-56-17-983.png When User goes to Background tab there should be only one column with given. But for Dmn based scenarios there is also description column. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4729) Change Unexpected error on Error if DMN got invalidated

by Anna Dupliak (Jira)

[ https://issues.jboss.org/browse/DROOLS-4729?page=com.atlassian.jira.plugi... ] Anna Dupliak updated DROOLS-4729: --------------------------------- Description: If user created DMN based scenario test and used a property from it and after some time that property disappeared - then if we reopen test scenario editor we got *Error as expected see* !image-2019-11-05-18-30-40-011.png|thumbnail! But if user wants to edit any of the value we got *Unexpected error* !image-2019-11-05-18-31-30-232.png|thumbnail! Steps to reproduce # Import DMN [^Traffic Violation Rules.dmn] # Create test scenario asset for this dmn and save # Go back to DMN and remove Driver Should the driver... DMN objects and save # Open test scenario was: If user created DMN based scenario test and used a property from it and after some time that property disappeared - then if we reopen test scenario editor we got Error as expected see [Expected error|ˆimage-2019-11-05-18-30-40-011.png] , but if user wants to edit any of the value we got Unexpected error !image-2019-11-05-18-31-30-232.png|thumbnail! Steps to reproduce # Import DMN [^Traffic Violation Rules.dmn] # Create test scenario asset for this dmn and save # Go back to DMN and remove Driver Should the driver... DMN objects and save # Open test scenario > Change Unexpected error on Error if DMN got invalidated > -------------------------------------------------------- > > Key: DROOLS-4729 > URL: https://issues.jboss.org/browse/DROOLS-4729 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.29.0.Final > Reporter: Anna Dupliak > Assignee: Daniele Zonca > Priority: Minor > Labels: CustomerFocus > Attachments: Traffic Violation Rules.dmn, image-2019-11-05-18-30-40-011.png, image-2019-11-05-18-31-30-232.png > > > If user created DMN based scenario test and used a property from it and after some time that property disappeared - then if we reopen test scenario editor we got > *Error as expected see* > !image-2019-11-05-18-30-40-011.png|thumbnail! > But if user wants to edit any of the value we got > *Unexpected error* > !image-2019-11-05-18-31-30-232.png|thumbnail! > Steps to reproduce > # Import DMN [^Traffic Violation Rules.dmn] > # Create test scenario asset for this dmn and save > # Go back to DMN and remove Driver Should the driver... DMN objects and save > # Open test scenario -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12757) Create 'microprofile' integration test module

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12757?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12757: ---------------------------------- Component/s: MP Config MP Fault Tolerance MP Health MP Metrics MP OpenAPI MP OpenTracing > Create 'microprofile' integration test module > --------------------------------------------- > > Key: WFLY-12757 > URL: https://issues.jboss.org/browse/WFLY-12757 > Project: WildFly > Issue Type: Task > Components: MP Config, MP Fault Tolerance, MP Health, MP Metrics, MP OpenAPI, MP OpenTracing > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 19.0.0.Beta1 > > > We need a place where to stick microprofile integration tests which run against a server provisioned with all microprofile integration modules. Moreover, since these modules are not in the default server configuration, we will use galleon to provision the server with fault-tolerance, jwt, openapi, etc galleon layers. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4729) Change Unexpected error on Error if DMN got invalidated

by Anna Dupliak (Jira)

[ https://issues.jboss.org/browse/DROOLS-4729?page=com.atlassian.jira.plugi... ] Anna Dupliak updated DROOLS-4729: --------------------------------- Description: If user created DMN based scenario test and used a property from it and after some time that property disappeared - then if we reopen test scenario editor we got Error as expected see [Expected error|ˆimage-2019-11-05-18-30-40-011.png] , but if user wants to edit any of the value we got Unexpected error !image-2019-11-05-18-31-30-232.png|thumbnail! Steps to reproduce # Import DMN [^Traffic Violation Rules.dmn] # Create test scenario asset for this dmn and save # Go back to DMN and remove Driver Should the driver... DMN objects and save # Open test scenario was: If user created DMN based scenario test and used a property from it and after some time that property disappeared - then if we reopen test scenario editor we got Error as expected see !image-2019-11-05-18-30-40-011.png|thumbnail! , but if user wants to edit any of the value we got Unexpected error !image-2019-11-05-18-31-30-232.png|thumbnail! Steps to reproduce # Import DMN [^Traffic Violation Rules.dmn] # Create test scenario asset for this dmn and save # Go back to DMN and remove Driver Should the driver... DMN objects and save # Open test scenario > Change Unexpected error on Error if DMN got invalidated > -------------------------------------------------------- > > Key: DROOLS-4729 > URL: https://issues.jboss.org/browse/DROOLS-4729 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.29.0.Final > Reporter: Anna Dupliak > Assignee: Daniele Zonca > Priority: Minor > Labels: CustomerFocus > Attachments: Traffic Violation Rules.dmn, image-2019-11-05-18-30-40-011.png, image-2019-11-05-18-31-30-232.png > > > If user created DMN based scenario test and used a property from it and after some time that property disappeared - then if we reopen test scenario editor we got Error as expected see [Expected error|ˆimage-2019-11-05-18-30-40-011.png] , but if user wants to edit any of the value we got Unexpected error !image-2019-11-05-18-31-30-232.png|thumbnail! > Steps to reproduce > # Import DMN [^Traffic Violation Rules.dmn] > # Create test scenario asset for this dmn and save > # Go back to DMN and remove Driver Should the driver... DMN objects and save > # Open test scenario -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4729) Change Unexpected error on Error if DMN got invalidated

by Anna Dupliak (Jira)

Anna Dupliak created DROOLS-4729: ------------------------------------ Summary: Change Unexpected error on Error if DMN got invalidated Key: DROOLS-4729 URL: https://issues.jboss.org/browse/DROOLS-4729 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Affects Versions: 7.29.0.Final Reporter: Anna Dupliak Assignee: Daniele Zonca Attachments: Traffic Violation Rules.dmn, image-2019-11-05-18-30-40-011.png, image-2019-11-05-18-31-30-232.png If user created DMN based scenario test and used a property from it and after some time that property disappeared - then if we reopen test scenario editor we got Error as expected see !image-2019-11-05-18-30-40-011.png|thumbnail! , but if user wants to edit any of the value we got Unexpected error !image-2019-11-05-18-31-30-232.png|thumbnail! Steps to reproduce # Import DMN [^Traffic Violation Rules.dmn] # Create test scenario asset for this dmn and save # Go back to DMN and remove Driver Should the driver... DMN objects and save # Open test scenario -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 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 November 2019