May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4478) Eliminate CapabilityServiceTarget & CapabilityServiceBuilder deprecated methods usages

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4478?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4478: -------------------------------- Fix Version/s: 9.0.0.Beta8 (was: 9.0.0.Beta7) > Eliminate CapabilityServiceTarget & CapabilityServiceBuilder deprecated methods usages > -------------------------------------------------------------------------------------- > > Key: WFCORE-4478 > URL: https://issues.jboss.org/browse/WFCORE-4478 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 9.0.0.Beta8 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4477) Introduce CapabilityServiceBuilder.setInstance(RuntimeCapability cap) overriding method

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4477?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4477: -------------------------------- Fix Version/s: 9.0.0.Beta8 (was: 9.0.0.Beta7) > Introduce CapabilityServiceBuilder.setInstance(RuntimeCapability cap) overriding method > --------------------------------------------------------------------------------------- > > Key: WFCORE-4477 > URL: https://issues.jboss.org/browse/WFCORE-4477 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 9.0.0.Beta8 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4395) The single mapper validation added via WFCORE-2364 happens at Runtime, this should be a Model time check.

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4395?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4395: -------------------------------- Fix Version/s: 9.0.0.Beta8 (was: 9.0.0.Beta7) > The single mapper validation added via WFCORE-2364 happens at Runtime, this should be a Model time check. > --------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4395 > URL: https://issues.jboss.org/browse/WFCORE-4395 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Priority: Major > Fix For: 9.0.0.Beta8 > > > If possible the mappers should be flagged as being mutually exclusive, however failing that the validation should happen during Stage.MODEL. > Presently this leads to an unsatisifed dependency: - > {noformat} > 14:21:59,055 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("security-domain" => "demon-domain") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-realm.demo-realm"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-domain.demon-domain.initial is missing [org.wildfly.security.security-realm.demo-realm]"] > } > {noformat} > Despite this error the underlying cause is not logged at any level. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4282) Remove use of java.security.acl APIs in Elytron PolicyDefinitions

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4282?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4282: -------------------------------- Fix Version/s: 9.0.0.Beta8 (was: 9.0.0.Beta7) > Remove use of java.security.acl APIs in Elytron PolicyDefinitions > ----------------------------------------------------------------- > > Key: WFCORE-4282 > URL: https://issues.jboss.org/browse/WFCORE-4282 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Priority: Critical > Labels: Java13 > Fix For: 9.0.0.Beta8 > > > The 'java.security.acls' packages has been deprecated and flagged for removal, this will be removed in Java 13 > https://bugs.openjdk.java.net/browse/JDK-8191138 > Within the Elytron subsystem we are presently using it within the PolicyDefinitions / Subject conversion likely to maintain compatibility with prior PicketBox implementations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4071) Selecting instance header by keyboard throws an error

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4071?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-4071: ------------------------------- Sprint: 2019 Week 20-22 > Selecting instance header by keyboard throws an error > ----------------------------------------------------- > > Key: DROOLS-4071 > URL: https://issues.jboss.org/browse/DROOLS-4071 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.23.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation > Attachments: bind-select.webm > > > If you bind the instance header and then select that instance header by keyboard an error is thrown. Please use the sample *Mortgages* and follow the video. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2349) MULTI_PING: callback is not set in async discovery

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2349?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2349. ---------------------------- Resolution: Done > MULTI_PING: callback is not set in async discovery > -------------------------------------------------- > > Key: JGRP-2349 > URL: https://issues.jboss.org/browse/JGRP-2349 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.1 > > > When MERGE3 calls FIND_MBRS_ASYNC, MULTI_PING does not set the callback in the discovery protocols it manages. The result is that merging doesn't succeed when MULTI_PING is in the stack. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2349) MULTI_PING: callback is not set in async discovery

by Bela Ban (Jira)

Bela Ban created JGRP-2349: ------------------------------ Summary: MULTI_PING: callback is not set in async discovery Key: JGRP-2349 URL: https://issues.jboss.org/browse/JGRP-2349 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 4.1.1 When MERGE3 calls FIND_MBRS_ASYNC, MULTI_PING does not set the callback in the discovery protocols it manages. The result is that merging doesn't succeed when MULTI_PING is in the stack. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1813) Deprecate Provider implementations that are in the base module

by Diana Vilkolakova (Jira)

Diana Vilkolakova created ELY-1813: -------------------------------------- Summary: Deprecate Provider implementations that are in the base module Key: ELY-1813 URL: https://issues.jboss.org/browse/ELY-1813 Project: WildFly Elytron Issue Type: Task Reporter: Diana Vilkolakova Assignee: Diana Vilkolakova Copy all Provider implementations that are in the base module and should be in their own module to the proper location. Deprecate those in the base module. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4079) Update version.com.fasterxml.jackson to 2.9.9

by Tibor Zimanyi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4079?page=com.atlassian.jira.plugi... ] Tibor Zimanyi updated DROOLS-4079: ---------------------------------- Sprint: 2019 Week 20-22 > Update version.com.fasterxml.jackson to 2.9.9 > --------------------------------------------- > > Key: DROOLS-4079 > URL: https://issues.jboss.org/browse/DROOLS-4079 > Project: Drools > Issue Type: Task > Affects Versions: 8.0.0.Final > Reporter: Tibor Zimanyi > Assignee: Tibor Zimanyi > Priority: Major > Labels: kogito, submarine > Fix For: 8.0.0.Final > > > Jackson versions older than 2.9.9 contains various vulnerabilities [1]. This needs to be updated in kogito-bom. > [1] https://www.cvedetails.com/vulnerability-list/vendor_id-15866/product_id-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12128) NPE in StatefulSessionSynchronizationInterceptor.java:210

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFLY-12128?page=com.atlassian.jira.plugin... ] Cheng Fang commented on WFLY-12128: ----------------------------------- Okay, now I see this in the test output file (attached). > NPE in StatefulSessionSynchronizationInterceptor.java:210 > --------------------------------------------------------- > > Key: WFLY-12128 > URL: https://issues.jboss.org/browse/WFLY-12128 > Project: WildFly > Issue Type: Bug > Components: EJB, Transactions > Affects Versions: 17.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Cheng Fang > Priority: Major > Attachments: org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatefulEJBFailoverTestCase-output.txt > > > Reproducer > {code} > ./integration-tests.sh clean install -Dts.noSmoke -Dts.clustering -Dtest=org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatefulEJBFailoverTestCase > {code} > {noformat} > .[0m.[33m18:10:40,409 WARN [org.jboss.as.txn] (default task-2) WFLYTX0027: The pre-jca synchronization org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor$StatefulSessionSynchronization@f525ed4 associated with tx Local transaction (delegate=T > ransactionImple < ac, BasicAction: 0:ffffc0a80002:-642358e3:5ce8176c:3d status: ActionStatus.ABORTED >, owner=Local transaction context for provider JBoss JTA transaction provider) failed during after completion: java.lang.NullPointerException > at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.releaseInstance(StatefulSessionSynchronizationInterceptor.java:210) > at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.handleAfterCompletion(StatefulSessionSynchronizationInterceptor.java:297) > at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor$StatefulSessionSynchronization.afterCompletion(StatefulSessionSynchronizationInterceptor.java:270) > at org.jboss.as.txn.service.internal.tsr.JCAOrderedLastSynchronizationList.afterCompletion(JCAOrderedLastSynchronizationList.java:144) > at org.wildfly.transaction.client.AbstractTransaction.performConsumer(AbstractTransaction.java:223) > at org.wildfly.transaction.client.AbstractTransaction$AssociatingSynchronization.afterCompletion(AbstractTransaction.java:306) > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:545) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:472) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:127) > at com.arjuna.ats.arjuna.AtomicAction.cancel(AtomicAction.java:215) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollback(TransactionImple.java:284) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Entry.rollbackLocal(JBossLocalTransactionProvider.java:353) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.rollbackLocal(JBossJTALocalTransactionProvider.java:132) > at org.wildfly.transaction.client.LocalTransaction.rollback(LocalTransaction.java:93) > at org.wildfly.transaction.client.AbstractTransaction.performConsumer(AbstractTransaction.java:241) > at org.wildfly.transaction.client.AbstractTransaction.performConsumer(AbstractTransaction.java:247) > at org.wildfly.transaction.client.AbstractTransaction.performAction(AbstractTransaction.java:267) > at org.wildfly.transaction.client.provider.remoting.TransactionServerChannel.lambda$handleUserTxnRollback$0(TransactionServerChannel.java:223) > at org.wildfly.security.auth.server.SecurityIdentity.runAsConsumer(SecurityIdentity.java:361) > at org.wildfly.security.auth.server.Scoped.runAsConsumer(Scoped.java:112) > at org.wildfly.security.auth.server.Scoped.runAs(Scoped.java:60) > at org.wildfly.transaction.client.provider.remoting.TransactionServerChannel.handleUserTxnRollback(TransactionServerChannel.java:220) > at org.wildfly.transaction.client.provider.remoting.TransactionServerChannel$ReceiverImpl.handleMessage(TransactionServerChannel.java:99) > at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:942) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 May 2019