December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2181) Icons (Edit, Collapse, Delete etc) do not respond to mouse clicks

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2181?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2181: ---------------------------------------- Checked {{master}} branch running in IDEA and it works OK.. investigating.. > Icons (Edit, Collapse, Delete etc) do not respond to mouse clicks > ----------------------------------------------------------------- > > Key: DROOLS-2181 > URL: https://issues.jboss.org/browse/DROOLS-2181 > Project: Drools > Issue Type: Bug > Components: Guided Decision Tree Editor > Affects Versions: 7.5.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > > - Double-click on a node (object/action) to edit/delete/collapse. > - Pop-up shows the icons/buttons. > - Click on Edit/Delete/collapse icon. Icons are frozen. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2181) Icons (Edit, Collapse, Delete etc) do not respond to mouse clicks

by Michael Anstis (JIRA)

Michael Anstis created DROOLS-2181: -------------------------------------- Summary: Icons (Edit, Collapse, Delete etc) do not respond to mouse clicks Key: DROOLS-2181 URL: https://issues.jboss.org/browse/DROOLS-2181 Project: Drools Issue Type: Bug Components: Guided Decision Tree Editor Affects Versions: 7.5.0.Final Reporter: Michael Anstis Assignee: Michael Anstis - Double-click on a node (object/action) to edit/delete/collapse. - Pop-up shows the icons/buttons. - Click on Edit/Delete/collapse icon. Icons are frozen. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9606) Upgrade ejb-client to 4.0.10.Final

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-9606?page=com.atlassian.jira.plugin.... ] Ivo Studensky closed WFLY-9606. ------------------------------- Resolution: Rejected > Upgrade ejb-client to 4.0.10.Final > ---------------------------------- > > Key: WFLY-9606 > URL: https://issues.jboss.org/browse/WFLY-9606 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB > Reporter: Ivo Studensky > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9606) Upgrade ejb-client to 4.0.10.Final

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-9606?page=com.atlassian.jira.plugin.... ] Ivo Studensky commented on WFLY-9606: ------------------------------------- My expectation that JBEAP-12666 needs another fix while it is open was wrong, I am sorry for that. I will close the upgrade issues and move the component jira to ON_QA then. > Upgrade ejb-client to 4.0.10.Final > ---------------------------------- > > Key: WFLY-9606 > URL: https://issues.jboss.org/browse/WFLY-9606 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB > Reporter: Ivo Studensky > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2180) [Guided Rule Editor] NPE closing a Guided Rule with an incomplete ActionCallMethod

by Michael Anstis (JIRA)

Michael Anstis created DROOLS-2180: -------------------------------------- Summary: [Guided Rule Editor] NPE closing a Guided Rule with an incomplete ActionCallMethod Key: DROOLS-2180 URL: https://issues.jboss.org/browse/DROOLS-2180 Project: Drools Issue Type: Bug Components: Guided Rule Editor Affects Versions: 7.5.0.Final Reporter: Michael Anstis Assignee: Michael Anstis Priority: Minor The implementation of {{ActionCallMethod.hashCode()}} fails if the "method name" is {{null}}. This scenario can arise if you create a new Guided Rule, add a "Call method on..." action and leave it incomplete. Trying to close the editor results in a NPE error (as the "is dirty" mechanism uses {{hashCode()}} implementations). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1405) The password attribute of resource owner credentials should support a credential store reference

by Martin Mazanek (JIRA)

[ https://issues.jboss.org/browse/ELY-1405?page=com.atlassian.jira.plugin.s... ] Martin Mazanek reassigned ELY-1405: ----------------------------------- Assignee: Martin Mazanek > The password attribute of resource owner credentials should support a credential store reference > ------------------------------------------------------------------------------------------------ > > Key: ELY-1405 > URL: https://issues.jboss.org/browse/ELY-1405 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Martin Mazanek > Fix For: 1.2.0.Beta11 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9616) Ability to specify thread pool used per EJB or deployment

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/WFLY-9616?page=com.atlassian.jira.plugin.... ] Brad Maxwell updated WFLY-9616: ------------------------------- Description: Request the ability to specify a particular thread pool to be used for an EJB or deployment to limit potential deadlocks such as a large number of Async EJB calls invoking other EJBs and not having enough resources to process the request. And a configurable fairness method to prevent one requestor from potentially taking priority. (was: Request the ability to specify a particular thread pool to be used for an EJB or deployment to limit potential deadlocks such as a large number of Async EJB calls invoking other EJBs and not having enough resources to process the request.) > Ability to specify thread pool used per EJB or deployment > --------------------------------------------------------- > > Key: WFLY-9616 > URL: https://issues.jboss.org/browse/WFLY-9616 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Affects Versions: 11.0.0.Final > Reporter: Brad Maxwell > > Request the ability to specify a particular thread pool to be used for an EJB or deployment to limit potential deadlocks such as a large number of Async EJB calls invoking other EJBs and not having enough resources to process the request. And a configurable fairness method to prevent one requestor from potentially taking priority. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9616) Ability to specify thread pool used per EJB or deployment

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-9616: ---------------------------------- Summary: Ability to specify thread pool used per EJB or deployment Key: WFLY-9616 URL: https://issues.jboss.org/browse/WFLY-9616 Project: WildFly Issue Type: Feature Request Components: EJB Affects Versions: 11.0.0.Final Reporter: Brad Maxwell Request the ability to specify a particular thread pool to be used for an EJB or deployment to limit potential deadlocks such as a large number of Async EJB calls invoking other EJBs and not having enough resources to process the request. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9610) Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution

by Cheng Fang (JIRA)

[ https://issues.jboss.org/browse/WFLY-9610?page=com.atlassian.jira.plugin.... ] Cheng Fang commented on WFLY-9610: ---------------------------------- The max-threads attribute in batch subsystem is the max number of threads in the thread pool used only by batch runtime. > Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9610 > URL: https://issues.jboss.org/browse/WFLY-9610 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 9.0.1.Final > Environment: Cluster, standalone-full-ha > Reporter: Serg Pol > Assignee: Cheng Fang > > Start of a BatchJob is called and record/entry is absent sometimes in DB table "step_execution" as well as Endtime and Exitstatus in the table job_execution (there is just info about start of BatchJob). > There are no any error nessages. > BatchJob is not started in this case according Log. > Any idea? Thanks -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-283) Investigate Elytron and gssproxy interoperability

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-283?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-283: -------------------------------- Even after patching openjdk to fix issue above (patch in attachement openjdk-patch-native-mechs.patch), the JVM crash in native acceptContext(): {code} Current thread (0x00007f8bbc3c8000): JavaThread "management task-1" [_thread_in_native, id=10598, stack(0x00007f8b9b73b000,0x00007f8b9b83c000)] Stack: [0x00007f8b9b73b000,0x00007f8b9b83c000], sp=0x00007f8b9b839a20, free space=1018k Native frames: (J=compiled Java code, A=aot compiled Java code, j=interpreted, Vv=VM code, C=native code) C [libc.so.6+0x932b2] cfree+0x32 Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) j sun.security.jgss.wrapper.GSSLibStub.acceptContext(JLorg/ietf/jgss/ChannelBinding;[BLsun/security/jgss/wrapper/NativeGSSContext;)[B+0 java.security.jgss@9-internal j sun.security.jgss.wrapper.NativeGSSContext.acceptSecContext(Ljava/io/InputStream;I)[B+68 java.security.jgss@9-internal j sun.security.jgss.GSSContextImpl.acceptSecContext(Ljava/io/InputStream;Ljava/io/OutputStream;)V+233 java.security.jgss@9-internal j sun.security.jgss.GSSContextImpl.acceptSecContext([BII)[B+24 java.security.jgss@9-internal j org.wildfly.security.sasl.gs2.Gs2SaslServer.evaluateMessage(I[B)[B+586 {code} Looks like this will need some more JDK fixes... I think this issue should be postponed for now, until this will be resolved in JDK... [~dlofthouse] Do we have contact to OpenJDK developers, to forwared them this issue? (openjdk jira is not public) > Investigate Elytron and gssproxy interoperability > ------------------------------------------------- > > Key: ELY-283 > URL: https://issues.jboss.org/browse/ELY-283 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: Peter Skopek > Assignee: Jan Kalina > Fix For: 2.0.0.Alpha1 > > Attachments: openjdk-patch-native-mechs.patch > > > Investigate Elytron and gssproxy interoperability. > https://fedorahosted.org/gss-proxy/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 December 2017