[JBoss JIRA] (DROOLS-2792) [DMN Designer] Data-types: Grid: LiteralExpression
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2792?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2792:
--------------------------------
Description:
*_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
h3. Manual acceptance test
- Resizing (/)
- Ctrl+C, Ctrl+v (/)
- Default Data Type for literal expression (/)
- Selecting standard, custom itemDefinition
- Long name of data type (?)
-- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Changing data type in graph node (/)
- Changing data type in properties panel (/)
- Building project
was:
*_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
h3. Manual acceptance test
- Resizing
- Ctrl+C, Ctrl+v (/)
- Default Data Type for literal expression (/)
- Selecting standard, custom itemDefinition
- Long name of data type (?)
-- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Building project
> [DMN Designer] Data-types: Grid: LiteralExpression
> --------------------------------------------------
>
> Key: DROOLS-2792
> URL: https://issues.jboss.org/browse/DROOLS-2792
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Attachments: DROOLS-2792.odt, Screen Shot 2018-08-01 at 10.11.48 AM.png, Screen Shot 2018-08-01 at 10.20.35 AM.png, Screenshot from 2018-08-09 09-21-01.png
>
>
> *_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
> h3. Manual acceptance test
> - Resizing (/)
> - Ctrl+C, Ctrl+v (/)
> - Default Data Type for literal expression (/)
> - Selecting standard, custom itemDefinition
> - Long name of data type (?)
> -- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
> - Used in levels of context grid (?)
> -- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
> -- Should be the data type shown anytime or just if literal expression is top level context entry?
> - Changing data type in graph node (/)
> - Changing data type in properties panel (/)
> - Building project
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2792) [DMN Designer] Data-types: Grid: LiteralExpression
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2792?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2792:
--------------------------------
Description:
*_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
h3. Manual acceptance test
- Resizing
- Ctrl+C, Ctrl+v (/)
- Default Data Type for literal expression (/)
- Selecting standard, custom itemDefinition
- Long name of data type (?)
-- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Building project
was:
*_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
h3. Manual acceptance test
- Resizing
- Pressing enter when selected
- Ctrl+C, Ctrl+v
- Default Data Type for literal expression (/)
- Selecting standard, custom itemDefinition
- Long name of data type (?)
-- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Building project
> [DMN Designer] Data-types: Grid: LiteralExpression
> --------------------------------------------------
>
> Key: DROOLS-2792
> URL: https://issues.jboss.org/browse/DROOLS-2792
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Attachments: DROOLS-2792.odt, Screen Shot 2018-08-01 at 10.11.48 AM.png, Screen Shot 2018-08-01 at 10.20.35 AM.png, Screenshot from 2018-08-09 09-21-01.png
>
>
> *_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
> h3. Manual acceptance test
> - Resizing
> - Ctrl+C, Ctrl+v (/)
> - Default Data Type for literal expression (/)
> - Selecting standard, custom itemDefinition
> - Long name of data type (?)
> -- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
> - Used in levels of context grid (?)
> -- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
> -- Should be the data type shown anytime or just if literal expression is top level context entry?
> - Building project
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2792) [DMN Designer] Data-types: Grid: LiteralExpression
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2792?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2792:
--------------------------------
Description:
*_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
h3. Manual acceptance test
- Resizing
- Pressing enter when selected
- Ctrl+C, Ctrl+v
- Default Data Type for literal expression (/)
- Selecting standard, custom itemDefinition
- Long name of data type (?)
-- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Building project
was:
*_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
h3. Manual acceptance test
- Resizing
- Pressing enter when selected
- Ctrl+C, Ctrl+v
- Default Data Type for literal expression
- Selecting standard, custom itemDefinition
- Long name of data type (?)
-- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Building project
> [DMN Designer] Data-types: Grid: LiteralExpression
> --------------------------------------------------
>
> Key: DROOLS-2792
> URL: https://issues.jboss.org/browse/DROOLS-2792
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Attachments: DROOLS-2792.odt, Screen Shot 2018-08-01 at 10.11.48 AM.png, Screen Shot 2018-08-01 at 10.20.35 AM.png, Screenshot from 2018-08-09 09-21-01.png
>
>
> *_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
> h3. Manual acceptance test
> - Resizing
> - Pressing enter when selected
> - Ctrl+C, Ctrl+v
> - Default Data Type for literal expression (/)
> - Selecting standard, custom itemDefinition
> - Long name of data type (?)
> -- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
> - Used in levels of context grid (?)
> -- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
> -- Should be the data type shown anytime or just if literal expression is top level context entry?
> - Building project
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-83) [Artemis 2.x upgrade] javax.jms.InvalidClientIDException: clientID=cts was already set into another connection
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFWIP-83?page=com.atlassian.jira.plugin.s... ]
Miroslav Novak commented on WFWIP-83:
-------------------------------------
[~martyn-taylor] I've started run with max-pool-size=1 and got even more failures - https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-third-...
[~gaohoward] It seems that there is previous failure. root priviliges are not required. Could you try the steps again, please?
> [Artemis 2.x upgrade] javax.jms.InvalidClientIDException: clientID=cts was already set into another connection
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-83
> URL: https://issues.jboss.org/browse/WFWIP-83
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis, JMS
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
>
> There is regression TCK 7 when running WF/EAP with Artemis 2.x resource adapter against AMQ 7.2.0.GA. WF/EAP with Artemis 2.x is last build from [2018-08-06]:
> https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP-...
> There are approximately 200 failures with exception:
> {code}
> [javatest.batch] ESC[0mESC[0m09:55:10,602 INFO [stdout] (Thread-68) 08-03-2018 09:55:10: SVR-ERROR: javax.jms.InvalidClientIDException: clientID=cts was already set into another connection
> [javatest.batch] ESC[0mESC[0m09:55:10,602 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnection.validateClientID(ActiveMQConnection.java:266)
> [javatest.batch] ESC[0mESC[0m09:55:10,602 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnection.authorize(ActiveMQConnection.java:681)
> [javatest.batch] ESC[0mESC[0m09:55:10,603 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:849)
> [javatest.batch] ESC[0mESC[0m09:55:10,603 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createXATopicConnection(ActiveMQConnectionFactory.java:387)
> [javatest.batch] ESC[0mESC[0m09:55:10,603 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection.setup(ActiveMQRAManagedConnection.java:745)
> [javatest.batch] ESC[0mESC[0m09:55:10,604 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection.<init>(ActiveMQRAManagedConnection.java:161)
> [javatest.batch] ESC[0mESC[0m09:55:10,604 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAManagedConnectionFactory.createManagedConnection(ActiveMQRAManagedConnectionFactory.java:151)
> [javatest.batch] ESC[0mESC[0m09:55:10,604 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(Semaphor
> eConcurrentLinkedDequeManagedConnectionPool.java:1326)
> [javatest.batch] ESC[0mESC[0m09:55:10,605 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinke
> dDequeManagedConnectionPool.java:499)
> [javatest.batch] ESC[0mESC[0m09:55:10,605 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:632)
> [javatest.batch] ESC[0mESC[0m09:55:10,605 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:604)
> [javatest.batch] ESC[0mESC[0m09:55:10,606 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:624)
> [javatest.batch] ESC[0mESC[0m09:55:10,610 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:430)
> [javatest.batch] ESC[0mESC[0m09:55:10,610 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:789)
> [javatest.batch] ESC[0mESC[0m09:55:10,610 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.allocateConnection(ActiveMQRASessionFactoryImpl.java:872)
> [javatest.batch] ESC[0mESC[0m09:55:10,611 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.createSession(ActiveMQRASessionFactoryImpl.java:531)
> [javatest.batch] ESC[0mESC[0m09:55:10,611 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.createSession(ActiveMQRASessionFactoryImpl.java:746)
> [javatest.batch] ESC[0mESC[0m09:55:10,611 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.createSession(ActiveMQRASessionFactoryImpl.java:751)
> [javatest.batch] ESC[0mESC[0m09:55:10,612 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAConnectionFactoryImpl.validateUser(ActiveMQRAConnectionFactoryImpl.java:475)
> [javatest.batch] ESC[0mESC[0m09:55:10,612 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAConnectionFactoryImpl.createTopicConnection(ActiveMQRAConnectionFactoryImpl.java:217)
> [javatest.batch] ESC[0mESC[0m09:55:10,612 INFO [stdout] (Thread-68) at com.sun.ts.tests.jms.ee.ejbweb.xa.TransactionTests.testInitForT(TransactionTests.java:354)
> [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at com.sun.ts.tests.jms.ee.ejbweb.xa.TransactionTests.Test06(TransactionTests.java:634)
> [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at java.lang.reflect.Method.invoke(Method.java:498)
> [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at com.sun.ts.lib.harness.EETest.run(EETest.java:550)
> [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:113)
> [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at com.sun.ts.tests.common.vehicle.ejb.EJBVehicle.runTest(EJBVehicle.java:70)
> {code}
> Note that TCK 7 is passing when trying with current Wildfly master (Artemis 1.5.5.012).
> Link to TCK 7 job:
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-third-...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2792) [DMN Designer] Data-types: Grid: LiteralExpression
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2792?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2792:
--------------------------------
Description:
*_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
h3. Manual acceptance test
- Resizing
- Pressing enter when selected
- Ctrl+C, Ctrl+v
- Default Data Type for literal expression
- Selecting standard, custom itemDefinition
- Long name of data type (?)
-- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Building project
was:
*_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
h3. Manual acceptance test
- Resizing
- Pressing enter when selected
- Ctrl+C, Ctrl+v
- Default Data Type for literal expression
- Selecting standard, custom itemDefinition
- Long name of itemDefinition
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Building project
> [DMN Designer] Data-types: Grid: LiteralExpression
> --------------------------------------------------
>
> Key: DROOLS-2792
> URL: https://issues.jboss.org/browse/DROOLS-2792
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Attachments: DROOLS-2792.odt, Screen Shot 2018-08-01 at 10.11.48 AM.png, Screen Shot 2018-08-01 at 10.20.35 AM.png, Screenshot from 2018-08-09 09-21-01.png
>
>
> *_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
> h3. Manual acceptance test
> - Resizing
> - Pressing enter when selected
> - Ctrl+C, Ctrl+v
> - Default Data Type for literal expression
> - Selecting standard, custom itemDefinition
> - Long name of data type (?)
> -- Column Width is not adapted automatically nor Data Type name is abbreviated, do we want to address somehow in future?
> - Used in levels of context grid (?)
> -- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
> -- Should be the data type shown anytime or just if literal expression is top level context entry?
> - Building project
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2792) [DMN Designer] Data-types: Grid: LiteralExpression
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2792?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2792:
--------------------------------
Description:
*_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
h3. Manual acceptance test
- Resizing
- Pressing enter when selected
- Ctrl+C, Ctrl+v
- Default Data Type for literal expression
- Selecting standard, custom itemDefinition
- Long name of itemDefinition
- Used in levels of context grid (?)
-- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
-- Should be the data type shown anytime or just if literal expression is top level context entry?
- Building project
was:
*_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
h3. Manual acceptance test
- Resizing
- Pressing enter when selected
- Ctrl+C, Ctrl+v
- Default Data Type for literal expression
- Selecting standard, custom itemDefinition
- Long name of itemDefinition
- Used in levels of context grid
- Building project
> [DMN Designer] Data-types: Grid: LiteralExpression
> --------------------------------------------------
>
> Key: DROOLS-2792
> URL: https://issues.jboss.org/browse/DROOLS-2792
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Attachments: DROOLS-2792.odt, Screen Shot 2018-08-01 at 10.11.48 AM.png, Screen Shot 2018-08-01 at 10.20.35 AM.png, Screenshot from 2018-08-09 09-21-01.png
>
>
> *_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
> h3. Manual acceptance test
> - Resizing
> - Pressing enter when selected
> - Ctrl+C, Ctrl+v
> - Default Data Type for literal expression
> - Selecting standard, custom itemDefinition
> - Long name of itemDefinition
> - Used in levels of context grid (?)
> -- !Screenshot from 2018-08-09 09-21-01.png|thumbnail!
> -- Should be the data type shown anytime or just if literal expression is top level context entry?
> - Building project
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2792) [DMN Designer] Data-types: Grid: LiteralExpression
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2792?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2792:
--------------------------------
Attachment: Screenshot from 2018-08-09 09-21-01.png
> [DMN Designer] Data-types: Grid: LiteralExpression
> --------------------------------------------------
>
> Key: DROOLS-2792
> URL: https://issues.jboss.org/browse/DROOLS-2792
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Attachments: DROOLS-2792.odt, Screen Shot 2018-08-01 at 10.11.48 AM.png, Screen Shot 2018-08-01 at 10.20.35 AM.png, Screenshot from 2018-08-09 09-21-01.png
>
>
> *_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
> h3. Manual acceptance test
> - Resizing
> - Pressing enter when selected
> - Ctrl+C, Ctrl+v
> - Default Data Type for literal expression
> - Selecting standard, custom itemDefinition
> - Long name of itemDefinition
> - Used in levels of context grid
> - Building project
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2792) [DMN Designer] Data-types: Grid: LiteralExpression
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2792?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2792:
--------------------------------
Description:
*_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
h3. Manual acceptance test
- Resizing
- Pressing enter when selected
- Ctrl+C, Ctrl+v
- Default Data Type for literal expression
- Selecting standard, custom itemDefinition
- Long name of itemDefinition
- Used in levels of context grid
- Building project
was:
*_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
> [DMN Designer] Data-types: Grid: LiteralExpression
> --------------------------------------------------
>
> Key: DROOLS-2792
> URL: https://issues.jboss.org/browse/DROOLS-2792
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Attachments: DROOLS-2792.odt, Screen Shot 2018-08-01 at 10.11.48 AM.png, Screen Shot 2018-08-01 at 10.20.35 AM.png
>
>
> *_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
> h3. Manual acceptance test
> - Resizing
> - Pressing enter when selected
> - Ctrl+C, Ctrl+v
> - Default Data Type for literal expression
> - Selecting standard, custom itemDefinition
> - Long name of itemDefinition
> - Used in levels of context grid
> - Building project
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-67) [Artemis 2.x upgrade] IndexOutOfBoundsException during receiving messages in remote JCA scenario between Artemis 1.5 and 2.x
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFWIP-67?page=com.atlassian.jira.plugin.s... ]
Miroslav Novak edited comment on WFWIP-67 at 8/9/18 3:10 AM:
-------------------------------------------------------------
[~clebert.suconic] I've updated steps to rerproduce. There is used EAP 7.1.0.GA as old server and then latest WF/Artemis 2.x build from you [1] for new server.
In my case reproducer hit the issue in 100% of runs but I believe that it's intermittent in nature.
Note that there is no Artemis cluster between old and new servers. It's common LODH scenario. Two old JMS servers in cluster. Then 2 new servers in connecting by remote JCA to old JMS cluster. JMS servers are sequentially killed and started again.
IndexOutOfBoundsException is thrown from receiver which consumes messages from OutQueue at the end of the test. It receives malformed message thus IndexOutOfBoundsException.
[1] https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP-...
was (Author: mnovak):
[~clebert.suconic] I've updated steps to rerproduce. There is used EAP 7.1.0.GA as old server and then latest WF/Artemis 2.x build from you [1] for new server.
Note that there is no Artemis cluster between old and new servers. It's common LODH scenario. Two old JMS servers in cluster. Then 2 new servers in connecting by remote JCA to old JMS cluster. JMS servers are sequentially killed and started again.
IndexOutOfBoundsException is thrown from receiver which consumes messages from OutQueue at the end of the test. It receives malformed message thus IndexOutOfBoundsException.
[1] https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP-...
> [Artemis 2.x upgrade] IndexOutOfBoundsException during receiving messages in remote JCA scenario between Artemis 1.5 and 2.x
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-67
> URL: https://issues.jboss.org/browse/WFWIP-67
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Martin Styk
> Assignee: Martyn Taylor
> Priority: Blocker
>
> *Scenario:*
> Nodes A and B are in cluster. Destinations InQueue and OutQueue are deployed on them.
> MDBs are deployed on node C and D. These MDBs read messages from InQueue of nodes A, B and sends them to OutQueue on A and B.
> Nodes A,B are running Artemis 1.5. Nodes C,D are using Artemis 2.6.
> # Client sends messages to InQueue on node A
> # MDBs on nodes C,D read messages from remote InQueue and send them to remote OutQueue on nodes A,B
> # During processing of messages nodes A and C are killed
> # Client reads messages from OutQueue on node B.
> *Issue*
> At the end of the test, client is not able to read message
> {code}
> java.lang.IndexOutOfBoundsException: readerIndex(9) + length(128) exceeds writerIndex(133): UnpooledDuplicatedByteBuf(ridx: 9, widx: 133, cap: 606, unwrapped: UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 0, widx: 606, cap: 606))
> at io.netty.buffer.AbstractByteBuf.checkReadableBytes0(AbstractByteBuf.java:1405)
> at io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1392)
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:872)
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:880)
> at io.netty.buffer.WrappedByteBuf.readBytes(WrappedByteBuf.java:649)
> at org.apache.activemq.artemis.api.core.SimpleString.readSimpleString(SimpleString.java:183)
> at org.apache.activemq.artemis.api.core.SimpleString.readSimpleString(SimpleString.java:171)
> at org.apache.activemq.artemis.api.core.SimpleString.readNullableSimpleString(SimpleString.java:158)
> at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readNullableSimpleString(ChannelBufferWrapper.java:69)
> at org.apache.activemq.artemis.reader.TextMessageUtil.readBodyText(TextMessageUtil.java:37)
> at org.apache.activemq.artemis.jms.client.ActiveMQTextMessage.doBeforeReceive(ActiveMQTextMessage.java:112)
> at org.apache.activemq.artemis.jms.client.ActiveMQMessageConsumer.getMessage(ActiveMQMessageConsumer.java:224)
> at org.apache.activemq.artemis.jms.client.ActiveMQMessageConsumer.receive(ActiveMQMessageConsumer.java:132)
> at org.jboss.qa.hornetq.apps.clients.Receiver11.receiveMessage(Receiver11.java:151)
> at org.jboss.qa.hornetq.apps.clients.ReceiverTransAck.run(ReceiverTransAck.java:89)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-26) [Artemis 2.x Upgrade] MDB doesn't find its source queue when useJndi property is set to false
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFWIP-26?page=com.atlassian.jira.plugin.s... ]
Miroslav Novak updated WFWIP-26:
--------------------------------
Component/s: JMS
> [Artemis 2.x Upgrade] MDB doesn't find its source queue when useJndi property is set to false
> ---------------------------------------------------------------------------------------------
>
> Key: WFWIP-26
> URL: https://issues.jboss.org/browse/WFWIP-26
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis, JMS
> Reporter: Martin Styk
> Assignee: Martyn Taylor
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
>
> Having a MDB configured as follows:
> {code}
> @MessageDriven(name = "mdb",
> activationConfig = {
> @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
> @ActivationConfigProperty(propertyName = "destination", propertyValue ="InQueue"),
> @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "false"),
> })
> {code}
> MDB is not able to receive messages from InQueue.
> Server logs:
> {noformat}
> 09:53:29,128 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151004: Instantiating javax.jms.Queue "jms/queue/InQueue" directly since UseJNDI=false.
> 09:53:29,188 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "Mdb.jar" (runtime-name : "Mdb.jar")
> 09:53:29,306 INFO [org.wildfly.naming] (default task-1) WildFly Naming version 1.0.7.Final
> 09:53:29,364 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151000: awaiting topic/queue creation jms/queue/InQueue
> 09:53:31,366 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151001: Attempting to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.wildfly.extension.messaging.activemq.ActiveMQResourceAdapter@2bd07716 destination=jms/queue/InQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15)
> 09:53:31,368 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151004: Instantiating javax.jms.Queue "jms/queue/InQueue" directly since UseJNDI=false.
> 09:53:33,480 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151004: Instantiating javax.jms.Queue "jms/queue/InQueue" directly since UseJNDI=false.
> 09:53:35,092 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0236: Suspending server with no timeout.
> {noformat}
> In {{ActiveMQActivation.setup()}}, call to {{setupDestination()}} is made. Destiantion InQueue is instantiated there. However, during the {{ActiveMQMessageHandler.setup()}} call. consumer can not be created for this destination and exception {{AMQ119017: Queue InQueue does not exist}} is being thrown.
> {code:title=ActiveMQActivation.setup()}
> protected synchronized void setup() throws Exception {
> logger.debug("Setting up " + spec);
> setupCF();
> setupDestination();
> Exception firstException = null;
> for (int i = 0; i < spec.getMaxSession(); i++) {
> ClientSessionFactory cf = null;
> ClientSession session = null;
> try {
> cf = factory.getServerLocator().createSessionFactory();
> session = setupSession(cf);
> ActiveMQMessageHandler handler = new ActiveMQMessageHandler(factory, this, ra.getTM(), (ClientSessionInternal) session, cf, i);
> handler.setup();
> handlers.add(handler);
> } catch (Exception e) {
> ...
> }
> }
> ...
> }
> {code}
> This is regression against Artemis 1.5.
> Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a)
> Artemis: upstream master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months