[JBoss JIRA] (DROOLS-2249) Generate Decision Table Graph automatically
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2249?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2249:
--------------------------------
Component/s: Guided Decision Table Editor
(was: decision tables)
> Generate Decision Table Graph automatically
> -------------------------------------------
>
> Key: DROOLS-2249
> URL: https://issues.jboss.org/browse/DROOLS-2249
> Project: Drools
> Issue Type: Feature Request
> Components: Guided Decision Table Editor
> Reporter: Ivo Bek
> Assignee: Michael Anstis
> Labels: codefest
>
> We think that the user doesn't need to create multiple decision table graphs in a single project. Instead whenever user creates his/her first decision table, the graph should be generated automatically and should contain all the decision tables available in the project.
> When a user opens a decision table, the editor could have a button "Display Linked Tables" which would open the graph.
> Then, we could remove the Decision Table Graph from the new Asset list because there would always be just single graph generated automatically and accessible from the asset list and/or Decision Table editor.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2249) Generate Decision Table Graph automatically
by Ivo Bek (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2249?page=com.atlassian.jira.plugi... ]
Ivo Bek reassigned DROOLS-2249:
-------------------------------
Assignee: Michael Anstis (was: Mario Fusco)
> Generate Decision Table Graph automatically
> -------------------------------------------
>
> Key: DROOLS-2249
> URL: https://issues.jboss.org/browse/DROOLS-2249
> Project: Drools
> Issue Type: Feature Request
> Components: Guided Decision Table Editor
> Reporter: Ivo Bek
> Assignee: Michael Anstis
> Labels: codefest
>
> We think that the user doesn't need to create multiple decision table graphs in a single project. Instead whenever user creates his/her first decision table, the graph should be generated automatically and should contain all the decision tables available in the project.
> When a user opens a decision table, the editor could have a button "Display Linked Tables" which would open the graph.
> Then, we could remove the Decision Table Graph from the new Asset list because there would always be just single graph generated automatically and accessible from the asset list and/or Decision Table editor.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9687) Apply InfiniteOrPositiveValidators to messaging attributes allow valid value -1
by Kabir Khan (JIRA)
Kabir Khan created WFLY-9687:
--------------------------------
Summary: Apply InfiniteOrPositiveValidators to messaging attributes allow valid value -1
Key: WFLY-9687
URL: https://issues.jboss.org/browse/WFLY-9687
Project: WildFly
Issue Type: Enhancement
Components: JMS
Affects Versions: 11.0.0.CR1
Reporter: Chao Wang
Assignee: Chao Wang
Fix For: 12.0.0.Alpha1
There are several attributes defined from ActiveMQ Artemis configuration parameters in ActiveMQClient.java and ActiveMQDefaultConfiguration.java are allowed to take value -1.
As they miss proper InfiniteOrPositiveValidators, they can also take any negative values which is incorrect.
{noformat}
ActiveMQClient.java
public static final long DEFAULT_CLIENT_FAILURE_CHECK_PERIOD_INVM = -1;
public static final long DEFAULT_CONNECTION_TTL_INVM = -1;
public static final int DEFAULT_CONSUMER_MAX_RATE = -1;
public static final int DEFAULT_CONFIRMATION_WINDOW_SIZE = -1;
public static final int DEFAULT_PRODUCER_MAX_RATE = -1;
public static final int DEFAULT_THREAD_POOL_MAX_SIZE = -1;
ActiveMQDefaultConfiguration.java
private static long DEFAULT_CONNECTION_TTL_OVERRIDE = -1;
private static int DEFAULT_JOURNAL_POOL_FILES = -1;
private static long DEFAULT_CONNECTION_TTL_OVERRIDE = -1;
private static int DEFAULT_JOURNAL_PERF_BLAST_PAGES = -1;
private static long DEFAULT_SERVER_DUMP_INTERVAL = -1;
private static long DEFAULT_MEMORY_MEASURE_INTERVAL = -1;
private static int DEFAULT_BRIDGE_INITIAL_CONNECT_ATTEMPTS = -1;
private static int DEFAULT_BRIDGE_RECONNECT_ATTEMPTS = -1;
private static int DEFAULT_BRIDGE_PRODUCER_WINDOW_SIZE = -1;
private static int DEFAULT_CLUSTER_INITIAL_CONNECT_ATTEMPTS = -1;
private static int DEFAULT_CLUSTER_RECONNECT_ATTEMPTS = -1;
private static int DEFAULT_HAPOLICY_BACKUP_REQUEST_RETRIES = -1;
private static int DEFAULT_GROUPING_HANDLER_GROUP_TIMEOUT = -1;
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2249) Generate Decision Table Graph automatically
by Ivo Bek (JIRA)
Ivo Bek created DROOLS-2249:
-------------------------------
Summary: Generate Decision Table Graph automatically
Key: DROOLS-2249
URL: https://issues.jboss.org/browse/DROOLS-2249
Project: Drools
Issue Type: Feature Request
Components: decision tables
Reporter: Ivo Bek
Assignee: Mario Fusco
We think that the user doesn't need to create multiple decision table graphs in a single project. Instead whenever user creates his/her first decision table, the graph should be generated automatically and should contain all the decision tables available in the project.
When a user opens a decision table, the editor could have a button "Display Linked Tables" which would open the graph.
Then, we could remove the Decision Table Graph from the new Asset list because there would always be just single graph generated automatically and accessible from the asset list and/or Decision Table editor.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-6660) Allow to dump Artemis journal to file by CLI operation
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-6660?page=com.atlassian.jira.plugin.... ]
Kabir Khan commented on WFLY-6660:
----------------------------------
[~mnovak] Done
> Allow to dump Artemis journal to file by CLI operation
> ------------------------------------------------------
>
> Key: WFLY-6660
> URL: https://issues.jboss.org/browse/WFLY-6660
> Project: WildFly
> Issue Type: Feature Request
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Miroslav Novak
> Assignee: Jeff Mesnil
> Attachments: journal.txt
>
>
> For debugging and investigation purposes it would useful to have CLI operation which would dump content of Artemis journal directory.
> New CLI operation like {{print-journal-date-content}} would print content of journal to a file.
> It would do the same thing like following Artemis CLI command:
> {code}
> .../activemq-artemis/artemis-distribution/target/apache-artemis-1.3.0-SNAPSHOT-bin/apache-artemis-1.3.0-SNAPSHOT/bin/artemis data print --bindings bindings --journal journal --paging paging --large-messages largemessages
> {code}
> This should work only in Admin only mode as dumping journal in run-time is not possible when data changes.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9684) Provide minimalistic profile for Artemis backup configuration
by Kabir Khan (JIRA)
Kabir Khan created WFLY-9684:
--------------------------------
Summary: Provide minimalistic profile for Artemis backup configuration
Key: WFLY-9684
URL: https://issues.jboss.org/browse/WFLY-9684
Project: WildFly
Issue Type: Feature Request
Components: JMS
Affects Versions: 10.0.0.Final
Reporter: Miroslav Novak
Assignee: Jeff Mesnil
If Artemis is configured as dedicated backup, no deployments like MDB,EJB,Servlets should be deployed to it. It should serve to its purpose which is to wait for Wildfly 10 with Artemis configured as live to fail.
We should provide minimalistic configuration for Wildfly serving purely as Artemis backup server.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9685) JMS Bridge should display statistics about messages that have been processed.
by Kabir Khan (JIRA)
Kabir Khan created WFLY-9685:
--------------------------------
Summary: JMS Bridge should display statistics about messages that have been processed.
Key: WFLY-9685
URL: https://issues.jboss.org/browse/WFLY-9685
Project: WildFly
Issue Type: Feature Request
Components: JMS
Affects Versions: 10.0.0.Final
Environment: JBoss EAP 7
Reporter: Chen Maoqian
Assignee: Chen Maoqian
The JMS bridge should show some statistics about messages that have been processed through the bridge for example:
- number of messages successfully committed
- number of messages aborted/rollback
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9686) Allow to dump Artemis journal to file by CLI operation
by Kabir Khan (JIRA)
Kabir Khan created WFLY-9686:
--------------------------------
Summary: Allow to dump Artemis journal to file by CLI operation
Key: WFLY-9686
URL: https://issues.jboss.org/browse/WFLY-9686
Project: WildFly
Issue Type: Feature Request
Components: JMS
Affects Versions: 10.0.0.Final
Reporter: Miroslav Novak
Assignee: Jeff Mesnil
For debugging and investigation purposes it would useful to have CLI operation which would dump content of Artemis journal directory.
New CLI operation like {{print-journal-date-content}} would print content of journal to a file.
It would do the same thing like following Artemis CLI command:
{code}
.../activemq-artemis/artemis-distribution/target/apache-artemis-1.3.0-SNAPSHOT-bin/apache-artemis-1.3.0-SNAPSHOT/bin/artemis data print --bindings bindings --journal journal --paging paging --large-messages largemessages
{code}
This should work only in Admin only mode as dumping journal in run-time is not possible when data changes.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months