May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11880) Add a SASL mechanism reference to the documentation

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11880?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11880: --------------------------------- Fix Version/s: 18.0.0.Final (was: 17.0.0.Beta1) > Add a SASL mechanism reference to the documentation > --------------------------------------------------- > > Key: WFLY-11880 > URL: https://issues.jboss.org/browse/WFLY-11880 > Project: WildFly > Issue Type: Task > Components: Documentation, Security > Reporter: Darran Lofthouse > Priority: Major > Fix For: 18.0.0.Final > > > A mechanism by mechanism listing, describing the mech, any features / requirements of the mech and any properties or other configuration affecting the mech. > This will need to cover both the client and server perspectives. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12120) Upgrade websocket-api_1.1_spec to 1.1.4.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12120?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-12120: --------------------------------- Fix Version/s: 18.0.0.Final (was: 17.0.0.Beta1) > Upgrade websocket-api_1.1_spec to 1.1.4.Final > --------------------------------------------- > > Key: WFLY-12120 > URL: https://issues.jboss.org/browse/WFLY-12120 > Project: WildFly > Issue Type: Task > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > Fix For: 18.0.0.Final > > > Upgrade the version of websocket-api-spec 1.1 at the server to 1.1.4.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12090) Unknown service name jboss.ejb and txn

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12090?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-12090: --------------------------------- Fix Version/s: 18.0.0.Final (was: 17.0.0.Beta1) > Unknown service name jboss.ejb and txn > -------------------------------------- > > Key: WFLY-12090 > URL: https://issues.jboss.org/browse/WFLY-12090 > Project: WildFly > Issue Type: Bug > Components: EJB, Transactions > Affects Versions: 17.0.0.Alpha1 > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > Fix For: 18.0.0.Final > > > When EJBRemoting service is not started (it is LAZY), but XA recovery has, we could have the following sort of error: > {code} > 16:51:46,785 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: WFTXN0034: Failed to acquire a connection for this operation > at org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.provider.remoting.RemotingRemoteTransactionPeer.getOperationsXA(RemotingRemoteTransactionPeer.java:139) > at org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.provider.remoting.RemotingRemoteTransactionPeer.recover(RemotingRemoteTransactionPeer.java:202) > at org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.SubordinateXAResource.recover(SubordinateXAResource.java:201) > at org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.SubordinateXAResource.recover(SubordinateXAResource.java:197) > at org.jboss.jts//com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryFirstPass(XARecoveryModule.java:634) > at org.jboss.jts//com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:226) > at org.jboss.jts//com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:171) > at org.jboss.jts//com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:770) > at org.jboss.jts//com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:382) > Caused by: org.jboss.remoting3.ServiceOpenException: Unknown service name jboss.ejb > at org.jboss.remoting@5.0.10.Final-SNAPSHOT//org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:429) > at org.jboss.remoting@5.0.10.Final-SNAPSHOT//org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:46) > at org.jboss.xnio@3.7.2.Final-SNAPSHOT//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.jboss.xnio@3.7.2.Final-SNAPSHOT//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at org.jboss.xnio.nio@3.7.2.Final-SNAPSHOT//org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) > at org.jboss.xnio.nio@3.7.2.Final-SNAPSHOT//org.xnio.nio.WorkerThread.run(WorkerThread.java:591) > Suppressed: org.jboss.remoting3.ServiceOpenException: Unknown service name txn > ... 6 more > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12051) Elytron: Ability to load the attributes of an identity from multiple sources

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12051?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-12051: --------------------------------- Fix Version/s: 18.0.0.Final (was: 17.0.0.Beta1) > Elytron: Ability to load the attributes of an identity from multiple sources > ---------------------------------------------------------------------------- > > Key: WFLY-12051 > URL: https://issues.jboss.org/browse/WFLY-12051 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 18.0.0.Final > > > In previous versions a {{security-domain}} was used to merge or add roles from multiple repositories. For example the roles for the users were obtained from two different ldaps and a database. All the roles were merged and the final authenticated principal belonged to all of them. The old picketbox subsystem used stacking of login modules (and password) to implement this feature. This use-case is not rare among the customers. > This issue is avoiding migrations from the old security subsystem to elytron. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12045) Some clustering test cases do not close JNDI InitialContext between tests

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12045?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-12045: --------------------------------- Fix Version/s: 18.0.0.Final (was: 17.0.0.Beta1) > Some clustering test cases do not close JNDI InitialContext between tests > ------------------------------------------------------------------------- > > Key: WFLY-12045 > URL: https://issues.jboss.org/browse/WFLY-12045 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 17.0.0.Alpha1 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Major > Fix For: 18.0.0.Final > > > The test case RemoteStatelessFailoverTestCase makes use of the helper class EJBRemoteDirectory to lookup JNDI names for beans in test cases. The EJB client then uses the resulting proxies to make invocations on the beans. > This helper class is defined statically and initialized before any of the test cases run. Consequenty, the InitialContext created by the helper class is used across multiple test cases. The effect of this is that all of the proxies used in the test case are created from the same InitialContext. Consequently, they share a RemoteEJBDiscoveryProvider instance which is a class used to maintain information about server and module deployments which the EJB client references during invocation to find a suitable target for the invocation. > This means that any server startup or shutdown activities are passed from one test case to another. This is not wanted as crash failures or shutdowns in one test will contaminate the next test, and this is exactly what is happening in a particular failure of this test. > If your test class only involves one test, then static usage will work, but probably not recommended. > UPDATE: This problem is present in a few other test cases, so I have updated them. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

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

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-12128: ------------------------------------- Summary: 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 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, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3652) DMN popover - Enter to apply

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3652?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3652: ------------------------------------------- To clarify ^^ this would be for pop-overs initiated by *clicking* - not necessarily the hover type... > DMN popover - Enter to apply > ----------------------------- > > Key: DROOLS-3652 > URL: https://issues.jboss.org/browse/DROOLS-3652 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Michael Anstis > Priority: Major > Labels: UX, drools-tools > Attachments: Screen Shot 2019-02-13 at 1.20.35 PM.png > > > When the user changes the field value (name in this example), it would be nice if hitting ENTER would apply the name, and take the focus highlight off. The other field is being applied dynamically, so the assumption is that this one is as well. > !Screen Shot 2019-02-13 at 1.20.35 PM.png|thumbnail! > p.s. this is the pop-over that needs to be updated to support Expression instead of Name. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3652) DMN popover - Enter to apply

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3652?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3652: ------------------------------------------- [~manstis] [~karreiro] I think it would be good to add a few more things to pop-overs: * Submit buttons (Cancel, Save/OK) * Close button for the popover ( X ) Designs I have posted to this jira show examples of this: https://issues.jboss.org/browse/DROOLS-3077. I'm just trying to track this to make sure this enhancement gets added - will this get covered in another jira? Thanks cc [~zhutaojiajia] ^^ > DMN popover - Enter to apply > ----------------------------- > > Key: DROOLS-3652 > URL: https://issues.jboss.org/browse/DROOLS-3652 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Michael Anstis > Priority: Major > Labels: UX, drools-tools > Attachments: Screen Shot 2019-02-13 at 1.20.35 PM.png > > > When the user changes the field value (name in this example), it would be nice if hitting ENTER would apply the name, and take the focus highlight off. The other field is being applied dynamically, so the assumption is that this one is as well. > !Screen Shot 2019-02-13 at 1.20.35 PM.png|thumbnail! > p.s. this is the pop-over that needs to be updated to support Expression instead of Name. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12127) ClientClusterNodeSelectorTestCase leaks CustomClusterNodeSelector to other tests

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12127?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12127: ---------------------------------- Description: {noformat} [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.824 s <<< FAILURE! - in org.jboss.as.test.clustering.cluster.ejb.remote.ClientRemoteStatelessEJBFailoverTestCase [ERROR] test(org.jboss.as.test.clustering.cluster.ejb.remote.ClientRemoteStatelessEJBFailoverTestCase) Time elapsed: 5.809 s <<< ERROR! java.lang.IllegalStateException: EJBCLIENT000076: Configured selector "org.jboss.as.test.clustering.cluster.ejb.remote.ClientClusterNodeSelectorTestCase$CustomClusterNodeSelector@59532566" returned unknown node "node-3" {noformat} Introduced in f3577724aabac8f3104b35e696f0c9d16b6797ca > ClientClusterNodeSelectorTestCase leaks CustomClusterNodeSelector to other tests > -------------------------------------------------------------------------------- > > Key: WFLY-12127 > URL: https://issues.jboss.org/browse/WFLY-12127 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > {noformat} > [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.824 s <<< FAILURE! - in org.jboss.as.test.clustering.cluster.ejb.remote.ClientRemoteStatelessEJBFailoverTestCase > [ERROR] test(org.jboss.as.test.clustering.cluster.ejb.remote.ClientRemoteStatelessEJBFailoverTestCase) Time elapsed: 5.809 s <<< ERROR! > java.lang.IllegalStateException: EJBCLIENT000076: Configured selector "org.jboss.as.test.clustering.cluster.ejb.remote.ClientClusterNodeSelectorTestCase$CustomClusterNodeSelector@59532566" returned unknown node "node-3" > {noformat} > Introduced in f3577724aabac8f3104b35e696f0c9d16b6797ca -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12127) ClientClusterNodeSelectorTestCase leaks CustomClusterNodeSelector to other tests

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-12127: ------------------------------------- Summary: ClientClusterNodeSelectorTestCase leaks CustomClusterNodeSelector to other tests Key: WFLY-12127 URL: https://issues.jboss.org/browse/WFLY-12127 Project: WildFly Issue Type: Bug Components: Clustering, Test Suite Affects Versions: 13.0.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 May 2019