[JBoss JIRA] (WFWIP-16) [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64
by Petr Sakař (JIRA)
[ https://issues.jboss.org/browse/WFWIP-16?page=com.atlassian.jira.plugin.s... ]
Petr Sakař commented on WFWIP-16:
---------------------------------
If AMQ team is building prod version of artemis 2.x they have to build natives which are part ot the component. Not EAP
> [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64
> -----------------------------------------------------------------
>
> Key: WFWIP-16
> URL: https://issues.jboss.org/browse/WFWIP-16
> Project: WildFly WIP
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
>
> LibAIO does not get loaded on RHEL 6 x86_64:
> {code}
> [hudson@rhel6-large-2723 bin]$ sh standalone.sh -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=1000
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /tmp/jboss-eap
> JAVA: java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> ...
> 10:14:31,918 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance.
> 10:14:32,017 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=true,journalDirectory=/tmp/jboss-eap/standalone/data/activemq/journal,bindingsDirectory=/tmp/jboss-eap/standalone/data/activemq/bindings,largeMessagesDirectory=/tmp/jboss-eap/standalone/data/activemq/largemessages,pagingDirectory=/tmp/jboss-eap/standalone/data/activemq/paging)
> 10:14:32,110 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221013: Using NIO Journal
> ...
> {code}
> libAIO in artemis journal module from WF branch. Not from Artemis 2.5.0.Final tag.
> Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a)
> Artemis: upstreadm master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2794) [DMN Designer] Data-types: Support usage in grids
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2794?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2794:
-----------------------------------
Epic Status: In Progress (was: To Do)
> [DMN Designer] Data-types: Support usage in grids
> -------------------------------------------------
>
> Key: DROOLS-2794
> URL: https://issues.jboss.org/browse/DROOLS-2794
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> Listing requirements here; and then possibly move this to an EPIC and add smaller tasks.
> *_General_*
> - (x) {{<< Back to XXX}} does not update if name changed in Properties panel
> - (x) "TypeRef" on Properties panel should show "Output Data Type"
> *_Literal Expression_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
> - (x) Update header when Output Data Type is changed via Properties panel
> *_Decision Table_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
> - (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns
> - (x) {{InputClause}} columns header should show Input Data Type
> - (x) {{InputClause}} columns should support changing the Input Data Type
> - (x) {{OutputClause}} columns header should show Input Data Type
> - (x) {{OutputClause}} columns should support changing the Input Data Type
> *_Context_*
> - (x) Grid header _could_ show Output Data Type (for Decision/BKM)
> - (/) Editing Output Data Type (for Decision/BKM) is possible via Properties panel
> - (x) {{ContextEntry}} should show Output Data Type (for {{ContextEntry}})
> - (x) {{ContextEntry}} should support changing the Output Data Type (for {{ContextEntry}})
> *_Relation_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
> - (x) {{InformationItem}} column should show Input Data Type
> - (x) {{InformationItem}} column should support changing Input Data Type
> *_Invocation_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2564) [DMN Designer] Data-types: Grid: General
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2564?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2564:
-----------------------------------
Comment: was deleted
(was: A comment with security level 'Red Hat Employee' was removed.)
> [DMN Designer] Data-types: Grid: General
> ----------------------------------------
>
> Key: DROOLS-2564
> URL: https://issues.jboss.org/browse/DROOLS-2564
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2798) [DMN Designer] Data-types: Grid: Invocation
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2798?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2798:
-----------------------------------
Description:
*_Invocation_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
was:
*_Relation_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) {{InformationItem}} column should show Input Data Type
- (x) {{InformationItem}} column should support changing Input Data Type
> [DMN Designer] Data-types: Grid: Invocation
> -------------------------------------------
>
> Key: DROOLS-2798
> URL: https://issues.jboss.org/browse/DROOLS-2798
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> *_Invocation_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2798) [DMN Designer] Data-types: Grid: Invocation
by Michael Anstis (JIRA)
Michael Anstis created DROOLS-2798:
--------------------------------------
Summary: [DMN Designer] Data-types: Grid: Invocation
Key: DROOLS-2798
URL: https://issues.jboss.org/browse/DROOLS-2798
Project: Drools
Issue Type: Feature Request
Components: DMN Editor
Reporter: Michael Anstis
Assignee: Michael Anstis
*_Relation_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) {{InformationItem}} column should show Input Data Type
- (x) {{InformationItem}} column should support changing Input Data Type
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2797) [DMN Designer] Data-types: Grid: Relation
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2797?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2797:
-----------------------------------
Description:
*_Relation_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) {{InformationItem}} column should show Input Data Type
- (x) {{InformationItem}} column should support changing Input Data Type
was:
*_Context_*
- (x) Grid header _could_ show Output Data Type (for Decision/BKM)
- (/) Editing Output Data Type (for Decision/BKM) is possible via Properties panel
- (x) {{ContextEntry}} should show Output Data Type (for {{ContextEntry}})
- (x) {{ContextEntry}} should support changing the Output Data Type (for {{ContextEntry}})
> [DMN Designer] Data-types: Grid: Relation
> -----------------------------------------
>
> Key: DROOLS-2797
> URL: https://issues.jboss.org/browse/DROOLS-2797
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> *_Relation_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
> - (x) {{InformationItem}} column should show Input Data Type
> - (x) {{InformationItem}} column should support changing Input Data Type
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2796) [DMN Designer] Data-types: Grid: Context
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2796?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2796:
-----------------------------------
Description:
*_Context_*
- (x) Grid header _could_ show Output Data Type (for Decision/BKM)
- (/) Editing Output Data Type (for Decision/BKM) is possible via Properties panel
- (x) {{ContextEntry}} should show Output Data Type (for {{ContextEntry}})
- (x) {{ContextEntry}} should support changing the Output Data Type (for {{ContextEntry}})
was:
*_Decision Table_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns
- (x) {{InputClause}} columns header should show Input Data Type
- (x) {{InputClause}} columns should support changing the Input Data Type
- (x) {{OutputClause}} columns header should show Input Data Type
- (x) {{OutputClause}} columns should support changing the Input Data Type
> [DMN Designer] Data-types: Grid: Context
> ----------------------------------------
>
> Key: DROOLS-2796
> URL: https://issues.jboss.org/browse/DROOLS-2796
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> *_Context_*
> - (x) Grid header _could_ show Output Data Type (for Decision/BKM)
> - (/) Editing Output Data Type (for Decision/BKM) is possible via Properties panel
> - (x) {{ContextEntry}} should show Output Data Type (for {{ContextEntry}})
> - (x) {{ContextEntry}} should support changing the Output Data Type (for {{ContextEntry}})
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2797) [DMN Designer] Data-types: Grid: Relation
by Michael Anstis (JIRA)
Michael Anstis created DROOLS-2797:
--------------------------------------
Summary: [DMN Designer] Data-types: Grid: Relation
Key: DROOLS-2797
URL: https://issues.jboss.org/browse/DROOLS-2797
Project: Drools
Issue Type: Feature Request
Components: DMN Editor
Reporter: Michael Anstis
Assignee: Michael Anstis
*_Context_*
- (x) Grid header _could_ show Output Data Type (for Decision/BKM)
- (/) Editing Output Data Type (for Decision/BKM) is possible via Properties panel
- (x) {{ContextEntry}} should show Output Data Type (for {{ContextEntry}})
- (x) {{ContextEntry}} should support changing the Output Data Type (for {{ContextEntry}})
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months