September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2904) Show menu to add row and column

by Gabriele Cardosi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2904?page=com.atlassian.jira.plugi... ] Gabriele Cardosi commented on DROOLS-2904: ------------------------------------------ In this version the "collapsed cell" issue won't be addressed. It will be fixed withhttps://issues.jboss.org/browse/DROOLS-2981 > Show menu to add row and column > ------------------------------- > > Key: DROOLS-2904 > URL: https://issues.jboss.org/browse/DROOLS-2904 > Project: Drools > Issue Type: Sub-task > Reporter: Juraj Soltes > Assignee: Gabriele Cardosi > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2904) Show menu to add row and column

by Gabriele Cardosi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2904?page=com.atlassian.jira.plugi... ] Gabriele Cardosi commented on DROOLS-2904: ------------------------------------------ In this version the "collapsed cell" issue won't be addressed. It will be fixed withhttps://issues.jboss.org/browse/DROOLS-2981 > Show menu to add row and column > ------------------------------- > > Key: DROOLS-2904 > URL: https://issues.jboss.org/browse/DROOLS-2904 > Project: Drools > Issue Type: Sub-task > Reporter: Juraj Soltes > Assignee: Gabriele Cardosi > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2981) Fix collapsed cells issue in grid

by Gabriele Cardosi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2981?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-2981: ------------------------------------- Sprint: 2018 Week 39-41 (was: 2018 Week 42-44) > Fix collapsed cells issue in grid > --------------------------------- > > Key: DROOLS-2981 > URL: https://issues.jboss.org/browse/DROOLS-2981 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > > Currently, inside the grid, cells of subsequent rows are collapsed (with an arrow to expand/collapse) if the values are the same. This is the default behaviour. > This fix will remove that behaviour, so cells will not get collapsed if values are the same. > Estimation has been set to medium because it is not known, yet, how and where that behaviour has been implemented and so how easy/hard could be to modify it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2981) Fix collapsed cells issue in grid

by Gabriele Cardosi (JIRA)

Gabriele Cardosi created DROOLS-2981: ---------------------------------------- Summary: Fix collapsed cells issue in grid Key: DROOLS-2981 URL: https://issues.jboss.org/browse/DROOLS-2981 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Currently, inside the grid, cells of subsequent rows are collapsed (with an arrow to expand/collapse) if the values are the same. This is the default behaviour. This fix will remove that behaviour, so cells will not get collapsed if values are the same. Estimation has been set to medium because it is not known, yet, how and where that behaviour has been implemented and so how easy/hard could be to modify it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2981) Fix collapsed cells issue in grid

by Gabriele Cardosi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2981?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-2981: ------------------------------------- Sprint: 2018 Week 45-47 > Fix collapsed cells issue in grid > --------------------------------- > > Key: DROOLS-2981 > URL: https://issues.jboss.org/browse/DROOLS-2981 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > > Currently, inside the grid, cells of subsequent rows are collapsed (with an arrow to expand/collapse) if the values are the same. This is the default behaviour. > This fix will remove that behaviour, so cells will not get collapsed if values are the same. > Estimation has been set to medium because it is not known, yet, how and where that behaviour has been implemented and so how easy/hard could be to modify it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2981) Fix collapsed cells issue in grid

by Gabriele Cardosi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2981?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-2981: ------------------------------------- Sprint: 2018 Week 42-44 (was: 2018 Week 45-47) > Fix collapsed cells issue in grid > --------------------------------- > > Key: DROOLS-2981 > URL: https://issues.jboss.org/browse/DROOLS-2981 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > > Currently, inside the grid, cells of subsequent rows are collapsed (with an arrow to expand/collapse) if the values are the same. This is the default behaviour. > This fix will remove that behaviour, so cells will not get collapsed if values are the same. > Estimation has been set to medium because it is not known, yet, how and where that behaviour has been implemented and so how easy/hard could be to modify it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10986) Concurrent Modification Exception when starting server with external JMS broker

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-10986?page=com.atlassian.jira.plugin... ] Kabir Khan commented on WFLY-10986: ----------------------------------- [~mstyk] I was mentioning Miroslav for some reason. Does my PR at https://github.com/wildfly/wildfly/pull/11652 solve it? > Concurrent Modification Exception when starting server with external JMS broker > ------------------------------------------------------------------------------- > > Key: WFLY-10986 > URL: https://issues.jboss.org/browse/WFLY-10986 > Project: WildFly > Issue Type: Bug > Components: JCA, JMS > Affects Versions: 14.0.1.Final > Reporter: Martin Styk > Assignee: Stefano Maestri > Priority: Blocker > > Start of a WildFly with resource adapter configured to remote messaging broker sometimes fails with following error. > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.resourceadapters.ra."wmq.jmsra".CF: org.jboss.msc.service.StartException in service jboss.resourceadapters.ra."wmq.jmsra".CF: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556) > 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:1364) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.util.ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909) > at java.util.ArrayList$Itr.next(ArrayList.java:859) > at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1042) > at org.jboss.as.connector.metadata.api.resourceadapter.ActivationSecurityUtil.isLegacySecurityRequired(ActivationSecurityUtil.java:41) > at org.jboss.as.connector.subsystems.resourceadapters.ConnectionDefinitionService.start(ConnectionDefinitionService.java:68) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698) > ... 6 more > {code} > This issue was introduced in fix for WFLY-9978 in [this commit |https://github.com/ehsavoie/wildfly/commit/8d35c77130c8ba8c47008e1de1225971fa5d8c2e] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10998) Concurrent Modification Exception when starting server with external JMS broker

by Kabir Khan (JIRA)

Kabir Khan created WFLY-10998: --------------------------------- Summary: Concurrent Modification Exception when starting server with external JMS broker Key: WFLY-10998 URL: https://issues.jboss.org/browse/WFLY-10998 Project: WildFly Issue Type: Bug Components: JCA, JMS Affects Versions: 14.0.1.Final Reporter: Martin Styk Assignee: Stefano Maestri Priority: Blocker Start of a WildFly with resource adapter configured to remote messaging broker sometimes fails with following error. {code} ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.resourceadapters.ra."wmq.jmsra".CF: org.jboss.msc.service.StartException in service jboss.resourceadapters.ra."wmq.jmsra".CF: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556) 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:1364) at java.lang.Thread.run(Thread.java:748) Caused by: java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909) at java.util.ArrayList$Itr.next(ArrayList.java:859) at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1042) at org.jboss.as.connector.metadata.api.resourceadapter.ActivationSecurityUtil.isLegacySecurityRequired(ActivationSecurityUtil.java:41) at org.jboss.as.connector.subsystems.resourceadapters.ConnectionDefinitionService.start(ConnectionDefinitionService.java:68) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698) ... 6 more {code} This issue was introduced in fix for WFLY-9978 in [this commit |https://github.com/ehsavoie/wildfly/commit/8d35c77130c8ba8c47008e1de1225971fa5d8c2e] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10997) WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-10997?page=com.atlassian.jira.plugin... ] Lin Gao updated WFLY-10997: --------------------------- Summary: WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups (was: [GSS](7.2.z) WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups) > WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-10997 > URL: https://issues.jboss.org/browse/WFLY-10997 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Lin Gao > Assignee: Lin Gao > Labels: downstream_dependency > Original Estimate: 3 days > Remaining Estimate: 3 days > > WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups > Using WildFlyInitialContextFactory and calling a remote EJB server. > Observations: > 1) If the ejb lookup is "reproducer/TestSLSB!test.Test" (basically like a RemoteNaming lookup), the ejb is invoked successfully, but the caller is seen as anonymous instead of the ejbuser which is specified in the Context properties. > Using the ejb-client type lookup: ejb:/reproducer/TestSLSB!test.Test , then it shows up as ejbuser as expected > 2) if a client creates 2 InitialContexts and uses the lookup reproducer/TestSLSB!test.Test" on ctx1 , then uses the lookup "ejb:/reproducer/TestSLSB!test.Test " on ctx2 in that order, then they both show anonymous (as if it uses only the context that was created first). > If you switch the order, and use ejb:/reproducer/TestSLSB!test.Test first, then they both show ejbuser -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10985) UnsupportedOperationException thrown during start if CredentialReference is used in messaging-activemq subsystem

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10985?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFLY-10985: --------------------------------------- [~ehugonnet] I've checked your fix for WFCORE-4090 and reproducer is passing. :-) > UnsupportedOperationException thrown during start if CredentialReference is used in messaging-activemq subsystem > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10985 > URL: https://issues.jboss.org/browse/WFLY-10985 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final > Reporter: Miroslav Novak > Assignee: ehsavoie Hugonnet > Priority: Critical > Attachments: bridge-cs001.jceks, standalone-full-ha.xml > > > If messaging subsystem is referencing elytron's credential store like in: > {code} > <bridge name="myBridge" queue-name="jms.queue.InQueue" forwarding-address="jms.queue.OutQueue" ha="true" reconnect-attempts="-1" use-duplicate-detection="true" user="johnOut" static-connectors="bridge-connector"> > <credential-reference store="bridge-cs001" alias="john_out_alias_wrong"/> > </bridge> > {code} > then during start server throws exception: > {code} > 12:49:04,367 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 66) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging-activemq"), > ("server" => "default") > ]): java.lang.UnsupportedOperationException > at org.jboss.msc.service.ServiceBuilderImpl.addDependency(ServiceBuilderImpl.java:409) > at org.jboss.msc.service.DelegatingServiceBuilder.addDependency(DelegatingServiceBuilder.java:147) > at org.jboss.as.controller.security.CredentialReference.getCredentialSourceSupplier(CredentialReference.java:323) > at org.wildfly.extension.messaging.activemq.ServerAdd.addBridgeCredentialStoreReference(ServerAdd.java:732) > at org.wildfly.extension.messaging.activemq.ServerAdd.access$200(ServerAdd.java:175) > at org.wildfly.extension.messaging.activemq.ServerAdd$2.execute(ServerAdd.java:439) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384) > 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:1349) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {code} > Attaching standalone-full-ha.xml with which is possible to reproduce the issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 2018