September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-241) Release JBoss / Jakarta JACC 2.0.0.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created JBEE-241: ------------------------------------- Summary: Release JBoss / Jakarta JACC 2.0.0.Final Key: JBEE-241 URL: https://issues.jboss.org/browse/JBEE-241 Project: JBoss Enterprise Spec APIs Issue Type: Task Components: jboss-jacc-api Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jboss-jakarta-jacc-api_spec-2.0.0.Final The Jakarta version is specified as 1.5.0: - https://github.com/jakartaee/specifications/blob/master/authorization/1.5... However we have already pulled in further changes from the development branch as 1.5.0 fails the signature tests so we are effectively 1.5.0 plus the signature tests. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-240) Release JBoss / Jakarta JASPI 2.0.1.Final

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/JBEE-240?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved JBEE-240. ----------------------------------- Resolution: Done > Release JBoss / Jakarta JASPI 2.0.1.Final > ----------------------------------------- > > Key: JBEE-240 > URL: https://issues.jboss.org/browse/JBEE-240 > Project: JBoss Enterprise Spec APIs > Issue Type: Task > Components: jboss-jaspi-api > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: jboss-jakarta-jaspi-api_spec-2.0.1.Final > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12546) Upgrade ByteBuddy to 1.9.11

by Gail Badner (Jira)

Gail Badner created WFLY-12546: ---------------------------------- Summary: Upgrade ByteBuddy to 1.9.11 Key: WFLY-12546 URL: https://issues.jboss.org/browse/WFLY-12546 Project: WildFly Issue Type: Component Upgrade Components: JPA / Hibernate Reporter: Gail Badner Assignee: Gail Badner Fix For: 18.0.0.Final -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4661) Upgrade the JBoss / Jakarta JASPI Fork to 2.0.1.Final

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4661?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-4661: ------------------------------------- Summary: Upgrade the JBoss / Jakarta JASPI Fork to 2.0.1.Final (was: Upgrade the JBoss / Jakarta JASPI Fork to 2.0.0.Final) > Upgrade the JBoss / Jakarta JASPI Fork to 2.0.1.Final > ----------------------------------------------------- > > Key: WFCORE-4661 > URL: https://issues.jboss.org/browse/WFCORE-4661 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 10.0.0.Beta7 > > > This is the final step migrating to the JBoss fork of the Jakarta project. > The Jakarta version is specified as 1.1.3: - > https://github.com/jakartaee/specifications/blob/master/authentication/1.... > This release has been merged into our fork. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4514) Number of facts in KIE session does not match after leader fails

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4514?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4514: --------------------------------------- Comment: was deleted (was: Originated by: https://issues.jboss.org/browse/RHPAM-2382) > Number of facts in KIE session does not match after leader fails > ---------------------------------------------------------------- > > Key: DROOLS-4514 > URL: https://issues.jboss.org/browse/DROOLS-4514 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4514) Number of facts in KIE session does not match after leader fails

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4514?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4514: --------------------------------------- Priority: Blocker (was: Major) > Number of facts in KIE session does not match after leader fails > ---------------------------------------------------------------- > > Key: DROOLS-4514 > URL: https://issues.jboss.org/browse/DROOLS-4514 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Blocker > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-240) Release JBoss / Jakarta JASPI 2.0.1.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created JBEE-240: ------------------------------------- Summary: Release JBoss / Jakarta JASPI 2.0.1.Final Key: JBEE-240 URL: https://issues.jboss.org/browse/JBEE-240 Project: JBoss Enterprise Spec APIs Issue Type: Task Components: jboss-jaspi-api Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jboss-jakarta-jaspi-api_spec-2.0.1.Final -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-239) Release JBoss / Jakarta JASPI 2.0.0.Final

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/JBEE-239?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved JBEE-239. ----------------------------------- Resolution: Done > Release JBoss / Jakarta JASPI 2.0.0.Final > ----------------------------------------- > > Key: JBEE-239 > URL: https://issues.jboss.org/browse/JBEE-239 > Project: JBoss Enterprise Spec APIs > Issue Type: Task > Components: jboss-jaspi-api > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: jboss-jakarta-jaspi-api_spec-2.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12545) Persist empty aliases list for ejb cache causes IllegalArgumentException on server reload

by Chao Wang (Jira)

Chao Wang created WFLY-12545: -------------------------------- Summary: Persist empty aliases list for ejb cache causes IllegalArgumentException on server reload Key: WFLY-12545 URL: https://issues.jboss.org/browse/WFLY-12545 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 18.0.0.Beta1 Reporter: Chao Wang Assignee: Chao Wang Persist Empty aliases list for ejb cache causes IllegalArgumentException on reload {noformat} [standalone@localhost:9990 /] /subsystem=ejb3/cache=simple:list-add(name=aliases,value=simpleAlias) [standalone@localhost:9990 /] reload [standalone@localhost:9990 /] /subsystem=ejb3/cache=simple:list-clear(name=aliases) [standalone@localhost:9990 /] reload {noformat} {noformat} 14:17:22,624 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 49) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "ejb3"), ("cache" => "simple") ]): java.lang.IllegalArgumentException: Empty name segment is not allowed for factory at org.jboss.msc@1.4.9.Final//org.jboss.msc.service.ServiceName.of(ServiceName.java:90) at org.jboss.msc@1.4.9.Final//org.jboss.msc.service.ServiceName.append(ServiceName.java:117) at org.jboss.as.ejb3(a)18.0.0.Final-SNAPSHOT//org.jboss.as.ejb3.cache.CacheFactoryBuilderServiceNameProvider.<init>(CacheFactoryBuilderServiceNameProvider.java:36) at org.jboss.as.ejb3@18.0.0.Final-SNAPSHOT//org.jboss.as.ejb3.subsystem.CacheFactoryAdd.performRuntime(CacheFactoryAdd.java:76) at org.jboss.as.controller@10.0.0.Beta7-SNAPSHOT//org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:338) at org.jboss.as.controller@10.0.0.Beta7-SNAPSHOT//org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:159) at org.jboss.as.controller@10.0.0.Beta7-SNAPSHOT//org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) at org.jboss.as.controller@10.0.0.Beta7-SNAPSHOT//org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) at org.jboss.as.controller@10.0.0.Beta7-SNAPSHOT//org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) at org.jboss.as.controller@10.0.0.Beta7-SNAPSHOT//org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384) at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348) at java.base/java.lang.Thread.run(Thread.java:834) at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485) {noformat} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-198) Operator long-term strategy

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-198?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFWIP-198: ------------------------------- Description: Facts: # Operator creates and manges internaly several kubernetes objects; StatefulSet, Pod, Service, Routes. By rough estimation these kubernetes objects expose approximately 50 options[2]. Operator now expose approximately 10 options [1]. # EAP7-1192 is currently designed in way operator is integral part of solution. You can not turn off operator to EAP7-1192 properly work. # User cant touch internal Kubernetes objects. Operator manages them and can overwrite changes anytime. So given these facts question is what is long-term strategy with Operator? # Operator will provide all options of internal objects. Everything I am able to configure directly with Kubernetes objects I will be able to configure with Operator # Operator will expose just most useful options. If user wants to make something special he has to "turn off" operator and to be on his own. (Loosing transaction support provided by EAP7-1192) # Operator will expose just most useful options. If user wants to make something special he can and Operator won't overwritten his changes. (I dont know if it is feasible?) [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#wil... [2] https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#pods... https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#stat... https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#serv... https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#ingr... was: Facts: - Operator creates and manges internaly several kubernetes objects StatefulSet, Pod, Service, Routes. By rough estimation these kubernetes objects expose approximately 50 options[2]. Operator now expose approximately 10 options [1]. - EAP7-1192 is currently designed in way operator is integral part of solution. You can not turn off operator to EAP7-1192 properly work. - User cant touch internal Kubernetes objects. Operator manages them and can overwrite changes anytime. So given these facts question is what is long-term strategy with Operator? 1) Operator will provide all options of internal objects. Everything I am able to configure directly with Kubernetes objects I will be able to configure with Operator 2) Operator will expose just most useful options. If user wants to make something special he has to "turn off" operator and to be on his own. (Loosing transaction support provided by EAP7-1192) 3) Operator will expose just most useful options. If user wants to make something special he can and Operator won't overwritten his changes. (I dont know if it is feasible?) [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#wil... [2] https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#pods... https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#stat... https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#serv... https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#ingr... > Operator long-term strategy > --------------------------- > > Key: WFWIP-198 > URL: https://issues.jboss.org/browse/WFWIP-198 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > > Facts: > # Operator creates and manges internaly several kubernetes objects; StatefulSet, Pod, Service, Routes. By rough estimation these kubernetes objects expose approximately 50 options[2]. Operator now expose approximately 10 options [1]. > # EAP7-1192 is currently designed in way operator is integral part of solution. You can not turn off operator to EAP7-1192 properly work. > # User cant touch internal Kubernetes objects. Operator manages them and can overwrite changes anytime. > So given these facts question is what is long-term strategy with Operator? > # Operator will provide all options of internal objects. Everything I am able to configure directly with Kubernetes objects I will be able to configure with Operator > # Operator will expose just most useful options. If user wants to make something special he has to "turn off" operator and to be on his own. (Loosing transaction support provided by EAP7-1192) > # Operator will expose just most useful options. If user wants to make something special he can and Operator won't overwritten his changes. (I dont know if it is feasible?) > [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#wil... > [2] > https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#pods... > https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#stat... > https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#serv... > https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#ingr... -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 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 September 2019