[JBoss JIRA] (JGRP-2396) increasing networkdata, cpu and heap
by Rob van der Boom (Jira)
[ https://issues.jboss.org/browse/JGRP-2396?page=com.atlassian.jira.plugin.... ]
Rob van der Boom commented on JGRP-2396:
----------------------------------------
ok thanks, will do and look further into configuration to tune things.
In a few/several weeks when everything is clear will post the results.
You can close the issue if thats the way it should in this case ;-)
Thanks again,
Rob.
> increasing networkdata, cpu and heap
> ------------------------------------
>
> Key: JGRP-2396
> URL: https://issues.jboss.org/browse/JGRP-2396
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.19
> Reporter: Rob van der Boom
> Assignee: Bela Ban
> Priority: Major
> Attachments: Schermafbeelding 2019-11-08 om 15.43.04.png, Schermafbeelding 2019-11-08 om 15.44.52.png, Schermafbeelding 2019-11-08 om 16.00.48.png, jstack-production-pod0.dump, standalone-ha.xml
>
>
> hey,
> we have an keycloak (sso) setup, version 7.0.1 running in kubernetes - aws.
> Its build on wildfly 17, infinispan 9.4 and jgroups 4.0.19.
> We have 3 pods running in standalone-ha with cache setup on distribution (all 3 nodes - so equivalent to replication)
> ISSUE:
> We see a slowly growing of networkstatistics, heap and cpu, while the number of sessions in keycloak (cached) remain almost stable.
> The cpu growth is caused by the TQbundler process, which explaines the networkdata growth. It looks like this is causing also a memory leakage..
> every 5 days we have to restart the pods and then every resets to a very low level including the heap. this while all sessions are still valid and cached.
> The only issue i could find maybe related to this is:
> https://issues.jboss.org/browse/JGRP-2382?jql=project%20%3D%20JGRP%20AND%...
> Could this be the same issue and does it also cause increasing network and cpu (since that is why we have to restart, the heap has much space left !).
> And if so how does this issue continue since for us its a major issue.
> We als had this issue already in keycloak 5 (wildfly 15), thats why we upgraded to the latest available version.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (JBVFS-207) Provide way to retrieve VirtualFile instance from url.openConnection()
by Richard Opalka (Jira)
[ https://issues.jboss.org/browse/JBVFS-207?page=com.atlassian.jira.plugin.... ]
Richard Opalka updated JBVFS-207:
---------------------------------
Fix Version/s: 3.2.15
> Provide way to retrieve VirtualFile instance from url.openConnection()
> ----------------------------------------------------------------------
>
> Key: JBVFS-207
> URL: https://issues.jboss.org/browse/JBVFS-207
> Project: JBoss VFS
> Issue Type: Enhancement
> Reporter: Tomas Hofman
> Assignee: Tomas Hofman
> Priority: Major
> Fix For: 3.5.0.Alpha1, 3.2.15
>
>
> It is not possible to obtain VirtualFile (and by extensions it's physicalFile) instance wrapped in VirtualFileURLConnection without using reflection.
> Code snippet from Drools [1], where they try to get hold of {{VirtualFile#getPhysicalFile()}}:
> {code}
> private static Object findVirtualFile( URL url ) throws IOException {
> URLConnection urlConnection = url.openConnection();
> try {
> if ( urlConnection.getClass().getName().equals( "org.jboss.vfs.protocol.VirtualFileURLConnection" ) ) {
> Field f = urlConnection.getClass().getDeclaredField( "file" );
> f.setAccessible( true );
> return f.get( urlConnection );
> }
> } catch (NoSuchFieldException | IllegalAccessException e) {
> // ignored
> }
> return urlConnection.getContent();
> }
> {code}
> [1] https://github.com/kiegroup/drools/commit/2a36f67a29ed06d0f980a60ff1c81fa...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4654) [DMN Designer] Cues to help users add nodes to the diagram
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-4654?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-4654:
----------------------------------------
[~roger600] [~kgaevski] [~josephblt] This can be the DMN texts:
*_Empty state_*
(https://marvelapp.com/9ca3e3d/screen/62342327)
"To create a diagram click or click+drag a node in the left-hand palette onto the canvas."
*_Toolbox Tooltip_*
(https://marvelapp.com/9ca3e3d/screen/62342323)
"To add another node to this diagram click or click+drag a toolbox icon onto the canvas."
So.. identical to BPMN but the term "business process" is replaced in both instances with "diagram".
> [DMN Designer] Cues to help users add nodes to the diagram
> ----------------------------------------------------------
>
> Key: DROOLS-4654
> URL: https://issues.jboss.org/browse/DROOLS-4654
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: Field, Stunner, UX, UX-Field, UXTeam, drools-tools
> Attachments: mouse-pointer.svg, screenshot-1.png
>
>
> Users are unable to add nodes the process diagram. In both the legacy editor and in Stunner, they do not understand that you need to drag the components onto the canvas. Some users click and then click on the canvas, while others can't even find where, for example, the script task is.
> *_Acceptance criteria_*
> See https://issues.jboss.org/browse/RHPAM-2318 for acceptance criteria.
> The empty state text should state "diagram" and not "business process".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4694) [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4694?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4694:
--------------------------------
Description:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object (/)
- Nested data objects, more than 5 levels (x) we do not follow acceptance criteria
- Class B extends Class A (/)
- Classes added as dependencies (x) we do not follow acceptance criteria
- Classes from different package than dmn (/)
- Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- Import, rename original java class, import again (/)
- Import, delete import, import (/)
- Import, add field in original java class, import (/)
- Import, change field type in original class, import (/)
- Import, import (/)
- Import, pick also types needed for fields (/)
- Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm]
- Use imported type in dmn, test scenario (/)
was:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object (/)
- Nested data objects, more than 5 levels (x) we do not follow acceptance criteria
- Class B extends Class A (/)
- Classes added as dependencies (x) we do not follow acceptance criteria
- Classes from different package than dmn (/)
- Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- Import, rename original java class, import again (/)
- Import, delete import, import (/)
- Import, add field in original java class, import (/)
- Import, change field type in original class, import (/)
- Import, import (/)
- Import, pick also types needed for fields (/)
- Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm]
- Use imported type in dmn, test scenario
> [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
> -------------------------------------------------------------------
>
> Key: DROOLS-4694
> URL: https://issues.jboss.org/browse/DROOLS-4694
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: convert-15-fields.webm, do-not-pick-fields.webm
>
>
> Consume the service provided by DROOLS-4680 and create Data Types in the UI.
> ⚠️ Notice:
> - Respect the nesting logic
> - Use the data types manager for creating type (just like the "Add" button)
> - The new data types must be added in the end of the list
> - If a Data Type with the same name already exists, remove it, and add the new one.
> h2. Manual Scenarios
> - No fields in data object (/)
> - Nested data objects, more than 5 levels (x) we do not follow acceptance criteria
> - Class B extends Class A (/)
> - Classes added as dependencies (x) we do not follow acceptance criteria
> - Classes from different package than dmn (/)
> - Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
> - simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
> - static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
> - Import, rename original java class, import again (/)
> - Import, delete import, import (/)
> - Import, add field in original java class, import (/)
> - Import, change field type in original class, import (/)
> - Import, import (/)
> - Import, pick also types needed for fields (/)
> - Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm]
> - Use imported type in dmn, test scenario (/)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4694) [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4694?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4694:
--------------------------------
Description:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object (/)
- Nested data objects, more than 5 levels (x) we do not follow acceptance criteria
- Class B extends Class A (/)
- Classes added as dependencies (x) we do not follow acceptance criteria
- Classes from different package than dmn (/)
- Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- Import, rename original java class, import again (/)
- Import, delete import, import (/)
- Import, add field in original java class, import (/)
- Import, change field type in original class, import (/)
- Import, import (/)
- Import, pick also types needed for fields (/)
- Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm]
- Use imported type in dmn, test scenario
was:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object (/)
- Nested data objects, more than 5 levels (x) we do not follow acceptance criteria
- Class B extends Class A (/)
- Classes added as dependencies (x) we do not follow acceptance criteria
- Classes from different package than dmn (/)
- Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- Import, rename original java class, import again (/)
- Import, delete import, import (/)
- Import, add field in original java class, import (/)
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm]
- Use imported type in dmn, test scenario
> [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
> -------------------------------------------------------------------
>
> Key: DROOLS-4694
> URL: https://issues.jboss.org/browse/DROOLS-4694
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: convert-15-fields.webm, do-not-pick-fields.webm
>
>
> Consume the service provided by DROOLS-4680 and create Data Types in the UI.
> ⚠️ Notice:
> - Respect the nesting logic
> - Use the data types manager for creating type (just like the "Add" button)
> - The new data types must be added in the end of the list
> - If a Data Type with the same name already exists, remove it, and add the new one.
> h2. Manual Scenarios
> - No fields in data object (/)
> - Nested data objects, more than 5 levels (x) we do not follow acceptance criteria
> - Class B extends Class A (/)
> - Classes added as dependencies (x) we do not follow acceptance criteria
> - Classes from different package than dmn (/)
> - Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
> - simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
> - static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
> - Import, rename original java class, import again (/)
> - Import, delete import, import (/)
> - Import, add field in original java class, import (/)
> - Import, change field type in original class, import (/)
> - Import, import (/)
> - Import, pick also types needed for fields (/)
> - Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm]
> - Use imported type in dmn, test scenario
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4694) [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4694?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4694:
--------------------------------
Description:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object (/)
- Nested data objects, more than 5 levels (x) we do not follow acceptance criteria
- Class B extends Class A (/)
- Classes added as dependencies (x) we do not follow acceptance criteria
- Classes from different package than dmn (/)
- Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- Import, rename original java class, import again (/)
- Import, delete import, import (/)
- Import, add field in original java class, import (/)
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm]
- Use imported type in dmn, test scenario
was:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object (/)
- Nested data objects, more than 5 levels (x) we do not follow acceptance criteria
- Class B extends Class A (/)
- Classes added as dependencies (x) we do not follow acceptance criteria
- Classes from different package than dmn (/)
- Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- Import, rename original java class, import again (/)
- Import, delete import, import (/)
- Import, add field in original java class, import
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm]
- Use imported type in dmn, test scenario
> [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
> -------------------------------------------------------------------
>
> Key: DROOLS-4694
> URL: https://issues.jboss.org/browse/DROOLS-4694
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: convert-15-fields.webm, do-not-pick-fields.webm
>
>
> Consume the service provided by DROOLS-4680 and create Data Types in the UI.
> ⚠️ Notice:
> - Respect the nesting logic
> - Use the data types manager for creating type (just like the "Add" button)
> - The new data types must be added in the end of the list
> - If a Data Type with the same name already exists, remove it, and add the new one.
> h2. Manual Scenarios
> - No fields in data object (/)
> - Nested data objects, more than 5 levels (x) we do not follow acceptance criteria
> - Class B extends Class A (/)
> - Classes added as dependencies (x) we do not follow acceptance criteria
> - Classes from different package than dmn (/)
> - Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
> - simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
> - static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
> - Import, rename original java class, import again (/)
> - Import, delete import, import (/)
> - Import, add field in original java class, import (/)
> - Import, change field type in original class, import
> - Import, import
> - Import, pick also types needed for fields
> - Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm]
> - Use imported type in dmn, test scenario
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4694) [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4694?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4694:
--------------------------------
Description:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object (/)
- Nested data objects, more than 5 levels (x) we do not follow acceptance criteria
- Class B extends Class A (/)
- Classes added as dependencies (x) we do not follow acceptance criteria
- Classes from different package than dmn (/)
- Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- Import, rename original java class, import again (/)
- Import, delete import, import
- Import, add field in original java class, import
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm]
- Use imported type in dmn, test scenario
was:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object (/)
- Nested data objects, more than 5 levels (x) we do not follow acceptance criteria
- Class B extends Class A (/)
- Classes added as dependencies (x) we do not follow acceptance criteria
- Classes from different package than dmn (/)
- Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- Import, rename original java class, import again
- Import, delete import, import
- Import, add field in original java class, import
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm]
- Use imported type in dmn, test scenario
> [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
> -------------------------------------------------------------------
>
> Key: DROOLS-4694
> URL: https://issues.jboss.org/browse/DROOLS-4694
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: convert-15-fields.webm, do-not-pick-fields.webm
>
>
> Consume the service provided by DROOLS-4680 and create Data Types in the UI.
> ⚠️ Notice:
> - Respect the nesting logic
> - Use the data types manager for creating type (just like the "Add" button)
> - The new data types must be added in the end of the list
> - If a Data Type with the same name already exists, remove it, and add the new one.
> h2. Manual Scenarios
> - No fields in data object (/)
> - Nested data objects, more than 5 levels (x) we do not follow acceptance criteria
> - Class B extends Class A (/)
> - Classes added as dependencies (x) we do not follow acceptance criteria
> - Classes from different package than dmn (/)
> - Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
> - simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
> - static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
> - Import, rename original java class, import again (/)
> - Import, delete import, import
> - Import, add field in original java class, import
> - Import, change field type in original class, import
> - Import, import
> - Import, pick also types needed for fields
> - Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm]
> - Use imported type in dmn, test scenario
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4694) [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4694?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4694:
--------------------------------
Description:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object (/)
- Nested data objects, more than 5 levels (x) we do not follow acceptance criteria
- Class B extends Class A (/)
- Classes added as dependencies (x) we do not follow acceptance criteria
- Classes from different package than dmn (/)
- Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- Import, rename original java class, import again (/)
- Import, delete import, import (/)
- Import, add field in original java class, import
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm]
- Use imported type in dmn, test scenario
was:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object (/)
- Nested data objects, more than 5 levels (x) we do not follow acceptance criteria
- Class B extends Class A (/)
- Classes added as dependencies (x) we do not follow acceptance criteria
- Classes from different package than dmn (/)
- Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
- Import, rename original java class, import again (/)
- Import, delete import, import
- Import, add field in original java class, import
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm]
- Use imported type in dmn, test scenario
> [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
> -------------------------------------------------------------------
>
> Key: DROOLS-4694
> URL: https://issues.jboss.org/browse/DROOLS-4694
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: convert-15-fields.webm, do-not-pick-fields.webm
>
>
> Consume the service provided by DROOLS-4680 and create Data Types in the UI.
> ⚠️ Notice:
> - Respect the nesting logic
> - Use the data types manager for creating type (just like the "Add" button)
> - The new data types must be added in the end of the list
> - If a Data Type with the same name already exists, remove it, and add the new one.
> h2. Manual Scenarios
> - No fields in data object (/)
> - Nested data objects, more than 5 levels (x) we do not follow acceptance criteria
> - Class B extends Class A (/)
> - Classes added as dependencies (x) we do not follow acceptance criteria
> - Classes from different package than dmn (/)
> - Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
> - simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
> - static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...]
> - Import, rename original java class, import again (/)
> - Import, delete import, import (/)
> - Import, add field in original java class, import
> - Import, change field type in original class, import
> - Import, import
> - Import, pick also types needed for fields
> - Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm]
> - Use imported type in dmn, test scenario
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFLY-12778) EAR deployed on colocated master/slave servers does not wait for the embedded JMS services to startup properly
by Bartosz Spyrko (Jira)
[ https://issues.jboss.org/browse/WFLY-12778?page=com.atlassian.jira.plugin... ]
Bartosz Spyrko commented on WFLY-12778:
---------------------------------------
The issue can be reproduced without a colocated setup - one server with replication-master and one with replication-slave is enough.
When the master node is booted it takes over from the slave as cluster master. Until the data is replicated, Artemis server is not active and the RA is not deployed, but the boot-time deployment is processed resulting in missing services.
> EAR deployed on colocated master/slave servers does not wait for the embedded JMS services to startup properly
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12778
> URL: https://issues.jboss.org/browse/WFLY-12778
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Bartosz Spyrko
> Assignee: Bartosz Spyrko
> Priority: Major
>
> When an EAR containing MDBS is deployed in one of the colocated master/slave servers, the application does not wait for the embedded broker to start up and generates these errors in the logs:
> {code:java}
> /14:48:11,134 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "EJB_MDBEAR.ear")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.ra.activemq-ra",
> "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
> ],
> {code}
> When the broker is eventually started, these MDBs get deployed and start working fine without any redeployment but these errors are not desirable in the logs.
> Defining the resource-ref in ejb-jar.xml or annotating with @Resource does not help either.
> The application should wait for its dependencies to be available.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFLY-12778) EAR deployed on colocated master/slave servers does not wait for the embedded JMS services to startup properly
by Bartosz Spyrko (Jira)
[ https://issues.jboss.org/browse/WFLY-12778?page=com.atlassian.jira.plugin... ]
Bartosz Spyrko moved JBEAP-17991 to WFLY-12778:
-----------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-12778 (was: JBEAP-17991)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
(was: ActiveMQ)
Affects Version/s: (was: 7.1.6.GA)
(was: 7.3.0.CD17)
(was: 7.2.3.GA)
QE Test Coverage: (was: +)
> EAR deployed on colocated master/slave servers does not wait for the embedded JMS services to startup properly
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12778
> URL: https://issues.jboss.org/browse/WFLY-12778
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Bartosz Spyrko
> Assignee: Bartosz Spyrko
> Priority: Major
>
> When an EAR containing MDBS is deployed in one of the colocated master/slave servers, the application does not wait for the embedded broker to start up and generates these errors in the logs:
> {code:java}
> /14:48:11,134 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "EJB_MDBEAR.ear")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.ra.activemq-ra",
> "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
> ],
> {code}
> When the broker is eventually started, these MDBs get deployed and start working fine without any redeployment but these errors are not desirable in the logs.
> Defining the resource-ref in ejb-jar.xml or annotating with @Resource does not help either.
> The application should wait for its dependencies to be available.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months