[JBoss JIRA] (JGRP-2337) DiagnosticsHandler without reflection
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2337?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2337:
---------------------------
Description:
Probe.sh sends commands to cluster nodes, and they are handled by each node's DiagnosticsHandler. {{"op"}} and {{"jmx"}} commands are handled via reflection.
However, reflection is not allowed by the GraalVM running in native mode, unless all attributes and methods of all protocols would be listed in a JSON file. This is apparently very costly as the native image builder creates a transitive closure over all classes whose methods and/or fields are listed in the JSON file, and thus includes too many classes in the native image.
Investigate creating a {{ProbeHandler}} for {{"jmx""}} and {{"op"}} commands, which does not use reflection. 2 alternatives come to mind:
* Offline creation and compilation: point to a list of protocols for which code is generated (an alternative ProbeHandler class). This class is then instantiated and set in the channel at runtime by the application
* Point to a running stack. The code uses reflection (obviously this needs to run in non-native mode) to generate the native {{ProbeHandler}} from the list of protocols running in the current stack. This code can then be compiled and used in native image generation.
was:
Probe.sh sends commands to cluster nodes, and they are handled by each node's DiagnosticsHandler. {{"op"}} and {{"jmx"}} commands are handled via reflection.
However, reflection is not allowed by the GraalVM running in native mode, unless all attributes and methods of all protocols would be listed in a JSON file. This is apparently very costly as the native image builder creates a transitive closure over all classes whose methods and/or fields are listed in the JSON file, and thus includes too many classes in the native image.
Investigate creating a {{ProbeHandler}} for {{"jmx""}} and {{"op"}} commands, which does not use reflection.
Offline creation and compilation: point to a list of protocols for which code is generated (an alternative ProbeHandler class). This class is then instantiated and set in the channel at runtime by the application
> DiagnosticsHandler without reflection
> -------------------------------------
>
> Key: JGRP-2337
> URL: https://issues.jboss.org/browse/JGRP-2337
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.1.0
>
>
> Probe.sh sends commands to cluster nodes, and they are handled by each node's DiagnosticsHandler. {{"op"}} and {{"jmx"}} commands are handled via reflection.
> However, reflection is not allowed by the GraalVM running in native mode, unless all attributes and methods of all protocols would be listed in a JSON file. This is apparently very costly as the native image builder creates a transitive closure over all classes whose methods and/or fields are listed in the JSON file, and thus includes too many classes in the native image.
> Investigate creating a {{ProbeHandler}} for {{"jmx""}} and {{"op"}} commands, which does not use reflection. 2 alternatives come to mind:
> * Offline creation and compilation: point to a list of protocols for which code is generated (an alternative ProbeHandler class). This class is then instantiated and set in the channel at runtime by the application
> * Point to a running stack. The code uses reflection (obviously this needs to run in non-native mode) to generate the native {{ProbeHandler}} from the list of protocols running in the current stack. This code can then be compiled and used in native image generation.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months
[JBoss JIRA] (DROOLS-3341) Duplicate DO columns
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-3341?page=com.atlassian.jira.plugi... ]
Klara Kufova commented on DROOLS-3341:
--------------------------------------
[~a175335], I think that "duplicate column" proposed here is a misleading caption; I would rather use "duplicate instance", as the user is not actually duplicating one single column, but potentially multiple (two, three, four and more) columns of one single instance. What do you think?
!1.png|thumbnail!
> Duplicate DO columns
> --------------------
>
> Key: DROOLS-3341
> URL: https://issues.jboss.org/browse/DROOLS-3341
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Yeser Amer
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: 1.png, duplicate.png, multiDO.png
>
>
> As a user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. scenario with more than one instance of “Person”...), so that I can create a test scenario.
> * As a user I want a means to create a data object instance in the test template using an existing statement column, so that I can quickly create instances from the test table.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months
[JBoss JIRA] (DROOLS-3341) Duplicate DO columns
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-3341?page=com.atlassian.jira.plugi... ]
Klara Kufova updated DROOLS-3341:
---------------------------------
Attachment: 1.png
> Duplicate DO columns
> --------------------
>
> Key: DROOLS-3341
> URL: https://issues.jboss.org/browse/DROOLS-3341
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Yeser Amer
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: 1.png, duplicate.png, multiDO.png
>
>
> As a user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. scenario with more than one instance of “Person”...), so that I can create a test scenario.
> * As a user I want a means to create a data object instance in the test template using an existing statement column, so that I can quickly create instances from the test table.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months
[JBoss JIRA] (JGRP-2337) DiagnosticsHandler without reflection
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2337?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2337:
---------------------------
Description:
Probe.sh sends commands to cluster nodes, and they are handled by each node's DiagnosticsHandler. {{"op"}} and {{"jmx"}} commands are handled via reflection.
However, reflection is not allowed by the GraalVM running in native mode, unless all attributes and methods of all protocols would be listed in a JSON file. This is apparently very costly as the native image builder creates a transitive closure over all classes whose methods and/or fields are listed in the JSON file, and thus includes too many classes in the native image.
Investigate creating a {{ProbeHandler}} for {{"jmx""}} and {{"op"}} commands, which does not use reflection.
Offline creation and compilation: point to a list of protocols for which code is generated (an alternative ProbeHandler class). This class is then instantiated and set in the channel at runtime by the application
was:
Probe.sh sends commands to cluster nodes, and they are handled by each node's DiagnosticsHandler. {{op}} and {{jmx}} commands are handled via reflection.
However, reflection is not allowed by the GraalVM running in native mode, unless all attributes and methods of all protocols would be listed in a JSON file. This is apparently very costly as the native image builder creates a transitive closure over all classes whose methods and/or fields are listed in the JSON file, and thus includes too many classes in the native image.
Investigate creating a {{ProbeHandler}} for {{"jmx""}} and {{"op"}} commands, which does not use reflection.
Offline creation and compilation: point to a list of protocols for which code is generated (an alternative ProbeHandler class). This class is then instantiated and set in the channel at runtime by the application
> DiagnosticsHandler without reflection
> -------------------------------------
>
> Key: JGRP-2337
> URL: https://issues.jboss.org/browse/JGRP-2337
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.1.0
>
>
> Probe.sh sends commands to cluster nodes, and they are handled by each node's DiagnosticsHandler. {{"op"}} and {{"jmx"}} commands are handled via reflection.
> However, reflection is not allowed by the GraalVM running in native mode, unless all attributes and methods of all protocols would be listed in a JSON file. This is apparently very costly as the native image builder creates a transitive closure over all classes whose methods and/or fields are listed in the JSON file, and thus includes too many classes in the native image.
> Investigate creating a {{ProbeHandler}} for {{"jmx""}} and {{"op"}} commands, which does not use reflection.
> Offline creation and compilation: point to a list of protocols for which code is generated (an alternative ProbeHandler class). This class is then instantiated and set in the channel at runtime by the application
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months
[JBoss JIRA] (JGRP-2337) DiagnosticsHandler without reflection
by Bela Ban (Jira)
Bela Ban created JGRP-2337:
------------------------------
Summary: DiagnosticsHandler without reflection
Key: JGRP-2337
URL: https://issues.jboss.org/browse/JGRP-2337
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 4.1.0
Probe.sh sends commands to cluster nodes, and they are handled by each node's DiagnosticsHandler. {{op}} and {{jmx}} commands are handled via reflection.
However, reflection is not allowed by the GraalVM running in native mode, unless all attributes and methods of all protocols would be listed in a JSON file. This is apparently very costly as the native image builder creates a transitive closure over all classes whose methods and/or fields are listed in the JSON file, and thus includes too many classes in the native image.
Investigate creating a {{ProbeHandler}} for {{"jmx""}} and {{"op"}} commands, which does not use reflection.
Offline creation and compilation: point to a list of protocols for which code is generated (an alternative ProbeHandler class). This class is then instantiated and set in the channel at runtime by the application
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months
[JBoss JIRA] (SWSQE-664) Test case coverage for KIALI
by Prachi Yadav (Jira)
Prachi Yadav created SWSQE-664:
----------------------------------
Summary: Test case coverage for KIALI
Key: SWSQE-664
URL: https://issues.jboss.org/browse/SWSQE-664
Project: Kiali QE
Issue Type: QE Task
Reporter: Prachi Yadav
In test coverage graph we can see that we have covered only functional test cases. We need to include other test type of test cases.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months