February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13060) EJB client behaviour is different when deployed in a .war compared to a .ear and can result in a OOME

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-13060?page=com.atlassian.jira.plugi... ] Ranabir Chakraborty commented on WFLY-13060: -------------------------------------------- [~flavia.rainone] can you please provide the steps to recreate the issue ? > EJB client behaviour is different when deployed in a .war compared to a .ear and can result in a OOME > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-13060 > URL: https://issues.redhat.com/browse/WFLY-13060 > Project: WildFly > Issue Type: Feature Request > Components: EJB, Remoting > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Critical > > EAP 7 - EJB client behaviour is different when deployed in a .war compared to a .ear > .war gives poor performance and runs out of native memory > .ear works ok -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13088) ejb: binding should not be listed if there is no Remote interface

by Moulali Shikalwadi (Jira)

[ https://issues.redhat.com/browse/WFLY-13088?page=com.atlassian.jira.plugi... ] Moulali Shikalwadi updated WFLY-13088: -------------------------------------- Attachment: remote.jar > ejb: binding should not be listed if there is no Remote interface > ----------------------------------------------------------------- > > Key: WFLY-13088 > URL: https://issues.redhat.com/browse/WFLY-13088 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Moulali Shikalwadi > Assignee: Moulali Shikalwadi > Priority: Major > Attachments: local.jar, remote.jar > > Original Estimate: 4 minutes > Remaining Estimate: 4 minutes > > The `ejb:` binding should not be logged if the EJB does not implement the Remote interface. > The `ejb:` is a message that gives the lookup path for an EJB with a remote interface, it should only be logged if the java:jboss/exported binding is logged as these are basically the same. > EJBs that only implement a Local interface or EJBs with No interface view should not log the ejb: > 20:15:02,699 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'HelloBean' in deployment unit 'deployment "local.jar"' are as follows: > java:global/local/HelloBean!test.HelloLocal > java:app/local/HelloBean!test.HelloLocal > java:module/HelloBean!test.HelloLocal > ejb:/local/HelloBean!test.HelloLocal > java:global/local/HelloBean > java:app/local/HelloBean > java:module/HelloBean > 20:15:53,450 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) WFLYEJB0473: JNDI bindings for session bean named 'HelloBean' in deployment unit 'deployment "no-interface.jar"' are as follows: > java:global/no-interface/HelloBean!test.HelloBean > java:app/no-interface/HelloBean!test.HelloBean > java:module/HelloBean!test.HelloBean > ejb:/no-interface/HelloBean!test.HelloBean > java:global/no-interface/HelloBean > java:app/no-interface/HelloBean > java:module/HelloBean -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13088) ejb: binding should not be listed if there is no Remote interface

by Moulali Shikalwadi (Jira)

[ https://issues.redhat.com/browse/WFLY-13088?page=com.atlassian.jira.plugi... ] Moulali Shikalwadi updated WFLY-13088: -------------------------------------- Attachment: local.jar > ejb: binding should not be listed if there is no Remote interface > ----------------------------------------------------------------- > > Key: WFLY-13088 > URL: https://issues.redhat.com/browse/WFLY-13088 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Moulali Shikalwadi > Assignee: Moulali Shikalwadi > Priority: Major > Attachments: local.jar, remote.jar > > Original Estimate: 4 minutes > Remaining Estimate: 4 minutes > > The `ejb:` binding should not be logged if the EJB does not implement the Remote interface. > The `ejb:` is a message that gives the lookup path for an EJB with a remote interface, it should only be logged if the java:jboss/exported binding is logged as these are basically the same. > EJBs that only implement a Local interface or EJBs with No interface view should not log the ejb: > 20:15:02,699 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'HelloBean' in deployment unit 'deployment "local.jar"' are as follows: > java:global/local/HelloBean!test.HelloLocal > java:app/local/HelloBean!test.HelloLocal > java:module/HelloBean!test.HelloLocal > ejb:/local/HelloBean!test.HelloLocal > java:global/local/HelloBean > java:app/local/HelloBean > java:module/HelloBean > 20:15:53,450 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) WFLYEJB0473: JNDI bindings for session bean named 'HelloBean' in deployment unit 'deployment "no-interface.jar"' are as follows: > java:global/no-interface/HelloBean!test.HelloBean > java:app/no-interface/HelloBean!test.HelloBean > java:module/HelloBean!test.HelloBean > ejb:/no-interface/HelloBean!test.HelloBean > java:global/no-interface/HelloBean > java:app/no-interface/HelloBean > java:module/HelloBean -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13088) ejb: binding should not be listed if there is no Remote interface

by Moulali Shikalwadi (Jira)

Moulali Shikalwadi created WFLY-13088: ----------------------------------------- Summary: ejb: binding should not be listed if there is no Remote interface Key: WFLY-13088 URL: https://issues.redhat.com/browse/WFLY-13088 Project: WildFly Issue Type: Bug Components: EJB Reporter: Moulali Shikalwadi Assignee: Moulali Shikalwadi The `ejb:` binding should not be logged if the EJB does not implement the Remote interface. The `ejb:` is a message that gives the lookup path for an EJB with a remote interface, it should only be logged if the java:jboss/exported binding is logged as these are basically the same. EJBs that only implement a Local interface or EJBs with No interface view should not log the ejb: 20:15:02,699 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'HelloBean' in deployment unit 'deployment "local.jar"' are as follows: java:global/local/HelloBean!test.HelloLocal java:app/local/HelloBean!test.HelloLocal java:module/HelloBean!test.HelloLocal ejb:/local/HelloBean!test.HelloLocal java:global/local/HelloBean java:app/local/HelloBean java:module/HelloBean 20:15:53,450 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) WFLYEJB0473: JNDI bindings for session bean named 'HelloBean' in deployment unit 'deployment "no-interface.jar"' are as follows: java:global/no-interface/HelloBean!test.HelloBean java:app/no-interface/HelloBean!test.HelloBean java:module/HelloBean!test.HelloBean ejb:/no-interface/HelloBean!test.HelloBean java:global/no-interface/HelloBean java:app/no-interface/HelloBean java:module/HelloBean -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5029) Loose of focus after cloasing Collection Editor

by Anna Dupliak (Jira)

[ https://issues.redhat.com/browse/DROOLS-5029?page=com.atlassian.jira.plug... ] Anna Dupliak commented on DROOLS-5029: -------------------------------------- When this issue would be fixed then the workaround could be removed here: https://github.com/jboss-integration/bxms-qe-tests/pull/3100/commits/7458... > Loose of focus after cloasing Collection Editor > ----------------------------------------------- > > Key: DROOLS-5029 > URL: https://issues.redhat.com/browse/DROOLS-5029 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.33.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Optional > Labels: drools-tools > > When user finishes with editing collections, using Collection Editor and push *Close* or *Save* or *Cansel* then Grid of Test scenario is loosing focus and user unable to navigate it by keyboard. > Suggested behaviour: > When Collection Editor disappears after editing Collection cell A then focus should be on the cell of A. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5017) [DMN Designer] Validation issues are not shown in Alerts panel

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5017?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5017: -------------------------------- Tester: Jozef Marko > [DMN Designer] Validation issues are not shown in Alerts panel > -------------------------------------------------------------- > > Key: DROOLS-5017 > URL: https://issues.redhat.com/browse/DROOLS-5017 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.32.0.Final > Reporter: Duncan Doyle > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: Screenshot 2020-02-06 at 11.25.18.png, Screenshot from 2020-02-06 14-36-00.png, vacation-days.dmn > > > The attached DMN file is invalid as it contains a trailing space in one of its decision nodes (Base Vacation Days). I've checked with [~tari_manga], and according to him, the backend DMN validator is capable of detecting the problem and giving a proper error message. However the DMN editor in the workbench does not give any user friendly hint what the problem is, and hence it's almost impossible for a user to figure out what's wrong. > I've attached both the DMN model and a screenshot of the error message displayed by our editor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4865) Add i18n reporting for DMN V&V

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4865?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-4865: --------------------------------- Sprint: 2020 Week 07-09 (from Feb 10) > Add i18n reporting for DMN V&V > ------------------------------ > > Key: DROOLS-4865 > URL: https://issues.redhat.com/browse/DROOLS-4865 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > The current reporting from the shared V&V is showing debug messages that are not meant for user to see and the custom DMN V&V is not i18n. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4997) DMN Validation: The Alerts panel should open when validation is ran

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4997?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-4997: --------------------------------- Story Points: 3 > DMN Validation: The Alerts panel should open when validation is ran > ------------------------------------------------------------------- > > Key: DROOLS-4997 > URL: https://issues.redhat.com/browse/DROOLS-4997 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5011) Multiselect dropdown for enumerated values

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5011?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-5011: --------------------------------- Story Points: 3 > Multiselect dropdown for enumerated values > ------------------------------------------ > > Key: DROOLS-5011 > URL: https://issues.redhat.com/browse/DROOLS-5011 > Project: Drools > Issue Type: Bug > Components: Guided Template Editor > Affects Versions: 7.33.0.Final > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > Attachments: add-row.webm > > > In earlier versions business central editor for a Guided Rule Template would display list (multiselect drop down )of enumerated values in Data tab if the user added a Template Key of type Enumerations, but in latest version it's shown as a normal text field not displaying enum values drop down . -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5058) [DMN Designer] Impossible to open a decision if another opened DMN is editing a decision

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5058?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5058: -------------------------------- Steps to Reproduce: # Import Traffic Violation project # Open Traffic Violation # Copy Traffic Violation DMN (Traffic2) # Open {{Fine}} Decision # Using breadcrumb go back to Asset List (keeping Traffic Violation opened and inside Fine decision node) # Open Traffic2 # Open {{Fine}} Decision # It doesn't work was: -> Import Traffic Violation project -> Open Traffic Violation -> Copy Traffic Violation DMN (Traffic2) -> Open `Fine` Decision -> Using breadcrumb go back to Asset List (keeping Traffic Violation opened and inside Fine decision node) -> Open Traffic2 -> Open `Fine` Decision -> It doesn't work > [DMN Designer] Impossible to open a decision if another opened DMN is editing a decision > ---------------------------------------------------------------------------------------- > > Key: DROOLS-5058 > URL: https://issues.redhat.com/browse/DROOLS-5058 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Daniele Zonca > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 February 2020