March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9981) [7.2] Logging README refers to gc.log which is not configured upstream

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9981?page=com.atlassian.jira.plugin.... ] Sande Gilda moved JBEAP-14336 to WFLY-9981: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9981 (was: JBEAP-14336) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Quickstarts (was: Quickstarts) Target Release: (was: 7.2.0.EO12.GA) Affects Version/s: (was: 7.2.0.EO12.GA) > [7.2] Logging README refers to gc.log which is not configured upstream > ---------------------------------------------------------------------- > > Key: WFLY-9981 > URL: https://issues.jboss.org/browse/WFLY-9981 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Sande Gilda > Assignee: Sande Gilda > > The `logging` quickstart mentions the `gc.log` file but does not mention that it is only available when garbage collection is enabled. This setting is enabled by default in JBoss EAP, but not in WildFly. We need to update the README file for the `logging` quickstart with this information so that it is accurate in both the upstream and downstream README files. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9981) [EO12] Logging README refers to gc.log which is not configured upstream

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9981?page=com.atlassian.jira.plugin.... ] Sande Gilda updated WFLY-9981: ------------------------------ Summary: [EO12] Logging README refers to gc.log which is not configured upstream (was: [7.2] Logging README refers to gc.log which is not configured upstream) > [EO12] Logging README refers to gc.log which is not configured upstream > ----------------------------------------------------------------------- > > Key: WFLY-9981 > URL: https://issues.jboss.org/browse/WFLY-9981 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Sande Gilda > Assignee: Sande Gilda > > The `logging` quickstart mentions the `gc.log` file but does not mention that it is only available when garbage collection is enabled. This setting is enabled by default in JBoss EAP, but not in WildFly. We need to update the README file for the `logging` quickstart with this information so that it is accurate in both the upstream and downstream README files. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9980) [7.2] Moved hard-coded doc URLs in READMEs to the attribute file.

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9980?page=com.atlassian.jira.plugin.... ] Sande Gilda moved JBEAP-14337 to WFLY-9980: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9980 (was: JBEAP-14337) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Quickstarts (was: Quickstarts) Target Release: (was: 7.backlog.GA) Fix Version/s: (was: 7.2.0.EO12.GA) > [7.2] Moved hard-coded doc URLs in READMEs to the attribute file. > ----------------------------------------------------------------- > > Key: WFLY-9980 > URL: https://issues.jboss.org/browse/WFLY-9980 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Sande Gilda > Assignee: Sande Gilda > > Now that the README files are in AsciiDoc format, we should replace hard-coded URLs with attributes to make it easier to update them with each release. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9980) [EO12] Moved hard-coded doc URLs in READMEs to the attribute file.

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9980?page=com.atlassian.jira.plugin.... ] Sande Gilda updated WFLY-9980: ------------------------------ Summary: [EO12] Moved hard-coded doc URLs in READMEs to the attribute file. (was: [7.2] Moved hard-coded doc URLs in READMEs to the attribute file.) > [EO12] Moved hard-coded doc URLs in READMEs to the attribute file. > ------------------------------------------------------------------ > > Key: WFLY-9980 > URL: https://issues.jboss.org/browse/WFLY-9980 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Sande Gilda > Assignee: Sande Gilda > > Now that the README files are in AsciiDoc format, we should replace hard-coded URLs with attributes to make it easier to update them with each release. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9979) Resteasy client quickstart dependency fix

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9979?page=com.atlassian.jira.plugin.... ] Sande Gilda moved JBEAP-14298 to WFLY-9979: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9979 (was: JBEAP-14298) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Quickstarts (was: Quickstarts) Target Release: (was: 7.backlog.GA) > Resteasy client quickstart dependency fix > ----------------------------------------- > > Key: WFLY-9979 > URL: https://issues.jboss.org/browse/WFLY-9979 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Martin Mazanek > Assignee: Martin Mazanek > > resteasy-jaxrs-client quickstart has wrong maven dependencies. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2373) BRL "is contained in the (comma separated) list" does not produce multiselect dropdown

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2373?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2373: -------------------------------- Summary: BRL "is contained in the (comma separated) list" does not produce multiselect dropdown (was: DRL "is contained in the (comma separated) list" does not produce multiselect dropdown) > BRL "is contained in the (comma separated) list" does not produce multiselect dropdown > -------------------------------------------------------------------------------------- > > Key: DROOLS-2373 > URL: https://issues.jboss.org/browse/DROOLS-2373 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor, Guided Rule Editor > Affects Versions: 7.6.0.Final > Environment: Tomcat 8.5 / RHEL 7 > Reporter: Yannick Geerts > Assignee: Michael Anstis > > Google groups link: https://groups.google.com/forum/#!topic/drools-usage/VElZ3KAZMIs -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2373) BRL "is contained in the (comma separated) list" does not produce multiselect dropdown

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2373?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2373: -------------------------------- Steps to Reproduce: 1) Create a guided decision table 2) Add a BRL condition on a fact-field that has an enum attached to it and where the condition is "is contained in the (comma separated) list = $templatekey" 3) Look at the guided decision table, and verify that the $templatekey field is a singleselect dropdown while a multiselect dropdown is expected. was: 1) Create a guided decision table 2) Add a DRL condition on a fact-field that has an enum attached to it and where the condition is "is contained in the (comma separated) list = $templatekey" 3) Look at the guided decision table, and verify that the $templatekey field is a singleselect dropdown while a multiselect dropdown is expected. > BRL "is contained in the (comma separated) list" does not produce multiselect dropdown > -------------------------------------------------------------------------------------- > > Key: DROOLS-2373 > URL: https://issues.jboss.org/browse/DROOLS-2373 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor, Guided Rule Editor > Affects Versions: 7.6.0.Final > Environment: Tomcat 8.5 / RHEL 7 > Reporter: Yannick Geerts > Assignee: Michael Anstis > > Google groups link: https://groups.google.com/forum/#!topic/drools-usage/VElZ3KAZMIs -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5808) IndexOutOfBoundsException after stopping deployment of HA Singleton deployment

by Michal Vinkler (JIRA)

[ https://issues.jboss.org/browse/WFLY-5808?page=com.atlassian.jira.plugin.... ] Michal Vinkler commented on WFLY-5808: -------------------------------------- The issue did not manifest in any recent test, therefore we can verify/close it. > IndexOutOfBoundsException after stopping deployment of HA Singleton deployment > ------------------------------------------------------------------------------ > > Key: WFLY-5808 > URL: https://issues.jboss.org/browse/WFLY-5808 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR5 > Reporter: Michal Vinkler > Assignee: Paul Ferraro > Priority: Minor > > Seen only once so far in failover tests - HA Singleton deployment scenarios. Is probably closely related to JBEAP-2254 as it occured during the events described there, namely: > - redeploy will fail > - This node will no longer operate as the singleton provider > - *IndexOutOfBoundsException* appears, see the stacktrace below > - the node is re-elected as the singleton provider and the deployment starts successfully > Stacktrace: > {code} > [JBossINF] [0m[31m05:51:00,920 ERROR [org.jgroups.protocols.pbcast.GMS] (Incoming-14,ee,perf19) JGRP000027: failed passing message up: java.lang.RuntimeException: org.infinispan.commons.CacheListenerException: ISPN000280: Caught exception [java.lang.IndexOutOfBoundsException] while invoking method [public void org.infinispan.container.versioning.NumericVersionGenerator$RankCalculator.calculateRank(org.infinispan.notifications.cachemanagerlistener.event.ViewChangedEvent)] on listener instance: org.infinispan.container.versioning.NumericVersionGenerator$RankCalculator@3118031c > [JBossINF] at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:689) > [JBossINF] at org.jgroups.JChannel.up(JChannel.java:738) > [JBossINF] at org.jgroups.fork.ForkProtocolStack.up(ForkProtocolStack.java:123) > [JBossINF] at org.jgroups.stack.Protocol.up(Protocol.java:374) > [JBossINF] at org.jgroups.protocols.FORK.up(FORK.java:118) > [JBossINF] at org.jgroups.protocols.FRAG2.up(FRAG2.java:165) > [JBossINF] at org.jgroups.protocols.FlowControl.up(FlowControl.java:394) > [JBossINF] at org.jgroups.protocols.FlowControl.up(FlowControl.java:394) > [JBossINF] at org.jgroups.protocols.pbcast.GMS.installView(GMS.java:735) > [JBossINF] at org.jgroups.protocols.pbcast.CoordGmsImpl.handleViewChange(CoordGmsImpl.java:244) > [JBossINF] at org.jgroups.protocols.pbcast.GMS.up(GMS.java:925) > [JBossINF] at org.jgroups.stack.Protocol.up(Protocol.java:412) > [JBossINF] at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:294) > [JBossINF] at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:474) > [JBossINF] at org.jgroups.protocols.pbcast.NAKACK2.deliverBatch(NAKACK2.java:982) > [JBossINF] at org.jgroups.protocols.pbcast.NAKACK2.removeAndPassUp(NAKACK2.java:912) > [JBossINF] at org.jgroups.protocols.pbcast.NAKACK2.handleMessage(NAKACK2.java:846) > [JBossINF] at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:618) > [JBossINF] at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:155) > [JBossINF] at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:200) > [JBossINF] at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:310) > [JBossINF] at org.jgroups.protocols.MERGE3.up(MERGE3.java:285) > [JBossINF] at org.jgroups.protocols.Discovery.up(Discovery.java:295) > [JBossINF] at org.jgroups.protocols.TP.passMessageUp(TP.java:1577) > [JBossINF] at org.jgroups.protocols.TP$3.run(TP.java:1511) > [JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [JBossINF] at java.lang.Thread.run(Thread.java:745) > [JBossINF] Caused by: org.infinispan.commons.CacheListenerException: ISPN000280: Caught exception [java.lang.IndexOutOfBoundsException] while invoking method [public void org.infinispan.container.versioning.NumericVersionGenerator$RankCalculator.calculateRank(org.infinispan.notifications.cachemanagerlistener.event.ViewChangedEvent)] on listener instance: org.infinispan.container.versioning.NumericVersionGenerator$RankCalculator@3118031c > [JBossINF] at org.infinispan.notifications.impl.AbstractListenerImpl$ListenerInvocationImpl$1.run(AbstractListenerImpl.java:291) > [JBossINF] at org.infinispan.util.concurrent.WithinThreadExecutor.execute(WithinThreadExecutor.java:21) > [JBossINF] at org.infinispan.notifications.impl.AbstractListenerImpl$ListenerInvocationImpl.invoke(AbstractListenerImpl.java:309) > [JBossINF] at org.infinispan.notifications.cachemanagerlistener.CacheManagerNotifierImpl.notifyViewChange(CacheManagerNotifierImpl.java:88) > [JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport$NotifyViewChange.emitNotification(JGroupsTransport.java:774) > [JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.viewAccepted(JGroupsTransport.java:850) > [JBossINF] at org.jgroups.blocks.MessageDispatcher.handleUpEvent(MessageDispatcher.java:605) > [JBossINF] at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:686) > [JBossINF] ... 27 more > [JBossINF] Caused by: java.lang.IndexOutOfBoundsException: Index: 0 > [JBossINF] at org.infinispan.commons.util.InfinispanCollections$EmptyList.get(InfinispanCollections.java:115) > [JBossINF] at org.infinispan.container.versioning.NumericVersionGenerator.findAddressRank(NumericVersionGenerator.java:115) > [JBossINF] at org.infinispan.container.versioning.NumericVersionGenerator.calculateRank(NumericVersionGenerator.java:101) > [JBossINF] at org.infinispan.container.versioning.NumericVersionGenerator$RankCalculator.calculateRank(NumericVersionGenerator.java:126) > [JBossINF] at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > [JBossINF] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [JBossINF] at java.lang.reflect.Method.invoke(Method.java:497) > [JBossINF] at org.infinispan.notifications.impl.AbstractListenerImpl$ListenerInvocationImpl$1.run(AbstractListenerImpl.java:286) > [JBossINF] ... 34 more > {code} > Link: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-singl... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2374) [DMN Designer] Literal Expression Cell can not be updated once erased

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2374?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2374: -------------------------------- Steps to Reproduce: # Create new DRG # Add decision node # Open the decision node # There is context grid with one undefined cell # Specify the cell as function # Double click the cell with FEEL expression - *it is Literal Expression Cell* # Type some value # Click outside the Function Grid # Double click the cell with FEEL expression again # Erase previously typed value # Click outside the Function Grid # Double click the cell with FEEL expression again -- The exception will appear -- !Screenshot from 2018-03-08 11-58-35.png|thumbnail! was: # Create new DRG # Add decision node # Open the decision node # There is context grid with one undefined cell # Specify the cell as function # Double click the cell with FEEL expression # Type some value # Click outside the Function Grid # Double click the cell with FEEL expression again # Erase previously typed value # Click outside the Function Grid # Double click the cell with FEEL expression again -- The exception will appear -- !Screenshot from 2018-03-08 11-58-35.png|thumbnail! > [DMN Designer] Literal Expression Cell can not be updated once erased > --------------------------------------------------------------------- > > Key: DROOLS-2374 > URL: https://issues.jboss.org/browse/DROOLS-2374 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Attachments: Screenshot from 2018-03-08 11-58-35.png > > > There is issue when user wants to type text into previously erased Literal Expression Cell. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2374) [DMN Designer] Literal Expression Cell can not be updated once erased

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2374?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2374: -------------------------------- Priority: Critical (was: Major) > [DMN Designer] Literal Expression Cell can not be updated once erased > --------------------------------------------------------------------- > > Key: DROOLS-2374 > URL: https://issues.jboss.org/browse/DROOLS-2374 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Critical > Attachments: Screenshot from 2018-03-08 11-58-35.png > > > There is issue when user wants to type text into previously erased Literal Expression Cell. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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