[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections
by Jan-Willem Gmelig Meyling (Jira)
[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ]
Jan-Willem Gmelig Meyling commented on WFLY-10531:
--------------------------------------------------
[~gunterze] Could you create a PR of your test case for the Wildfly repo under the Integ tests module? I'm wondering whether the test will pass with the fix applied, and especially, why.
> Wildfly leaks ActiveMQ connections
> ----------------------------------
>
> Key: WFLY-10531
> URL: https://issues.jboss.org/browse/WFLY-10531
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Environment: openjdk 8 / openjdk 9, Linux
> Reporter: Marcel Šebek
> Assignee: Jeff Mesnil
> Priority: Major
> Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip
>
>
> After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on
> IJ000453: Unable to get managed connection for java:/JmsXA
> and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log:
> WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69)
> Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time.
> It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (DROOLS-3066) NPE in Drools org.drools.core.rule.SingleAccumulate.reverse(SingleAccumulate.java:124)
by Philip Harding (Jira)
Philip Harding created DROOLS-3066:
--------------------------------------
Summary: NPE in Drools org.drools.core.rule.SingleAccumulate.reverse(SingleAccumulate.java:124)
Key: DROOLS-3066
URL: https://issues.jboss.org/browse/DROOLS-3066
Project: Drools
Issue Type: Bug
Components: executable model
Affects Versions: 7.4.1.Final
Environment: Windows 7
Oracle Java Development Kit 1.8.0_111
Eclipse Oxygen 3a
Optaplanner 7.4.1.Final
Reporter: Philip Harding
Assignee: Luca Molteni
Attachments: NPE_Drools_MWE.zip
The rule
{code:java}
rule "globalRequiredPredecessorAfterMe"
when
$rpAll: Set(size>1) from accumulate (
Customer(Domicile != null, $rpAfterMe: requiredPredecessorsAfterMe);
collectSet($rpAfterMe)
)
then
scoreHolder.addMediumConstraintMatch(kcontext, - $rpAll.size()-1);
end
{code}
gives following NPE within the attached Optaplanner model:
{code:java}
Exception in thread "main" java.lang.RuntimeException: java.lang.NullPointerException
at org.drools.core.rule.SingleAccumulate.reverse(SingleAccumulate.java:124)
at org.drools.core.phreak.PhreakAccumulateNode.removeMatch(PhreakAccumulateNode.java:796)
at org.drools.core.phreak.PhreakAccumulateNode.doRightUpdatesProcessChildren(PhreakAccumulateNode.java:517)
at org.drools.core.phreak.PhreakAccumulateNode.doRightUpdates(PhreakAccumulateNode.java:450)
at org.drools.core.phreak.PhreakAccumulateNode.doNode(PhreakAccumulateNode.java:76)
at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:581)
at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:552)
at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:379)
at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:339)
at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:175)
at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:133)
at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:212)
at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:87)
at org.drools.core.concurrent.AbstractRuleEvaluator.internalEvaluateAndFire(AbstractRuleEvaluator.java:34)
at org.drools.core.concurrent.SequentialRuleEvaluator.evaluateAndFire(SequentialRuleEvaluator.java:43)
at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1067)
at org.drools.core.common.DefaultAgenda.internalFireAllRules(DefaultAgenda.java:1014)
at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1006)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1337)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1328)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1312)
at org.optaplanner.core.impl.score.director.drools.DroolsScoreDirector.calculateScore(DroolsScoreDirector.java:117)
at org.optaplanner.core.impl.score.director.AbstractScoreDirector.doAndProcessMove(AbstractScoreDirector.java:187)
at org.optaplanner.core.impl.constructionheuristic.decider.ConstructionHeuristicDecider.doMove(ConstructionHeuristicDecider.java:126)
at org.optaplanner.core.impl.constructionheuristic.decider.ConstructionHeuristicDecider.decideNextStep(ConstructionHeuristicDecider.java:100)
at org.optaplanner.core.impl.constructionheuristic.DefaultConstructionHeuristicPhase.solve(DefaultConstructionHeuristicPhase.java:74)
at org.optaplanner.core.impl.solver.AbstractSolver.runPhases(AbstractSolver.java:88)
at org.optaplanner.core.impl.solver.DefaultSolver.solve(DefaultSolver.java:191)
at canihazafischbroetchenplz.app.TestApp.main(TestApp.java:35)
Caused by: java.lang.NullPointerException
at org.drools.core.base.accumulators.CollectSetAccumulateFunction.reverse(CollectSetAccumulateFunction.java:118)
at org.drools.core.base.accumulators.CollectSetAccumulateFunction.reverse(CollectSetAccumulateFunction.java:49)
at org.drools.core.base.accumulators.JavaAccumulatorFunctionExecutor.reverse(JavaAccumulatorFunctionExecutor.java:133)
at org.drools.core.rule.SingleAccumulate.reverse(SingleAccumulate.java:116)
... 28 more
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections
by Jan-Willem Gmelig Meyling (Jira)
[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ]
Jan-Willem Gmelig Meyling commented on WFLY-10531:
--------------------------------------------------
[~jondruse] Do you have an intuition why getDelegate() returns a TransactedJMSContext but is not inTX()? I'm trying to construct a test case to verify that this is indeed my bug. (I could also just deploy your fix and see whether I get the same error over time, but I rather have a clean test, rerunnable, test case)
> Wildfly leaks ActiveMQ connections
> ----------------------------------
>
> Key: WFLY-10531
> URL: https://issues.jboss.org/browse/WFLY-10531
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Environment: openjdk 8 / openjdk 9, Linux
> Reporter: Marcel Šebek
> Assignee: Jeff Mesnil
> Priority: Major
> Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip
>
>
> After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on
> IJ000453: Unable to get managed connection for java:/JmsXA
> and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log:
> WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69)
> Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time.
> It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (WFLY-11104) JCA distributed work manager doesn't allow to add more than one
by Claudio Miranda (Jira)
Claudio Miranda created WFLY-11104:
--------------------------------------
Summary: JCA distributed work manager doesn't allow to add more than one
Key: WFLY-11104
URL: https://issues.jboss.org/browse/WFLY-11104
Project: WildFly
Issue Type: Bug
Components: JCA
Reporter: Claudio Miranda
Assignee: Stefano Maestri
There is an error trying to add a 2nd JCA distributed work manager.
{code}
[standalone@localhost:9990 /] batch
[standalone@localhost:9990 / #] /subsystem=jca/distributed-workmanager=dwm2:add(name=dwm2)
[standalone@localhost:9990 / #] /subsystem=jca/distributed-workmanager=dwm2/short-running-threads=dwm2:add(max-threads=11,queue-length=22)
[standalone@localhost:9990 / #] run-batch
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error):
WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:
Step: step-1
Operation: /subsystem=jca/distributed-workmanager=dwm2:add(name=dwm2)
Failure: WFLYCTL0436: Cannot register capability
'org.wildfly.connector.workmanager' at location '[
("subsystem" => "jca"),
("distributed-workmanager" => "dwm2")
]' as it is already registered in context 'global' at location(s) '[[
("subsystem" => "jca"),
("distributed-workmanager" => "dwm1")
]]'
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (WFLY-9447) NPE in ejb client and clean shutdown ERROR [org.jboss.ejb.client.invocation] (default task-8) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-9447?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-9447:
--------------------------------------
[~tommaso-borgato] The NPE occurs regardless of that configuration.
> NPE in ejb client and clean shutdown ERROR [org.jboss.ejb.client.invocation] (default task-8) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9447
> URL: https://issues.jboss.org/browse/WFLY-9447
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 14.0.1.Final, 11.0.0.CR1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: 15.0.0.Alpha1
>
>
> {noformat}
> ESC[0m13:59:55,004 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0211: Suspending server with 15000 ms timeout.
> ESC[0mESC[0m13:59:55,006 INFO [org.jboss.as.ejb3] (management-handler-thread - 1) WFLYEJB0493: EJB subsystem suspension complete
> ESC[0mESC[0m13:59:55,008 INFO [org.jboss.as.server] (Management Triggered Shutdown) WFLYSRV0241: Shutting down in response to management operation 'shutdown'
> ESC[0mESC[0m13:59:55,027 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0019: Host default-host stopping
> ESC[0mESC[0m13:59:55,028 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 72) MODCLUSTER000002: Initiating mod_cluster shutdown
> ESC[0mESC[0m13:59:55,039 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000080: Disconnecting JGroups channel ejb
> ESC[0mESC[0m13:59:55,039 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000080: Disconnecting JGroups channel ejb
> ESC[0mESC[0m13:59:55,039 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000080: Disconnecting JGroups channel ejb
> ESC[0mESC[0m13:59:55,040 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000082: Stopping the RpcDispatcher for channel ejb
> ESC[0mESC[0m13:59:55,040 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000082: Stopping the RpcDispatcher for channel ejb
> ESC[0mESC[0m13:59:55,040 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000082: Stopping the RpcDispatcher for channel ejb
> ESC[0mESC[0m13:59:55,042 INFO [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 74) ISPN000029: Passivating all entries to disk
> ESC[0mESC[0m13:59:55,046 INFO [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 74) ISPN000030: Passivated 2 entries in 3 milliseconds
> ESC[0mESC[0m13:59:55,055 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
> ESC[0mESC[0m13:59:55,055 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 74) WFLYCLINF0003: Stopped twocluster-terminus.jar cache from ejb container
> ESC[0m13:59:55,057 DEBUG [org.jboss.ejb.client.invocation] (pool-1-thread-1) Calling invoke(module = /twocluster-forwarder-tx/ForwardingStatefulSBImpl, strong affinity = Cluster "ejb-forwarder", weak affinity = Node "clusterA-node0"):
> ESC[0m13:59:55,059 INFO [org.jboss.as.test.clustering.twoclusters.bean.forwarding.AbstractForwardingStatefulSBImpl] (default task-124) getSerialAndIncrement() called on forwarding node clusterA-node0
> ESC[0mESC[31m13:59:55,062 ERROR [org.jboss.ejb.client.invocation] (default task-8) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException
> at org.jboss.as.ejb3.deployment.DeploymentRepository.getStartedModules(DeploymentRepository.java:202)
> at org.jboss.as.ejb3.remote.AssociationImpl.findEJB(AssociationImpl.java:382)
> at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:115)
> at org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleInvocationRequest(EJBServerChannel.java:450)
> at org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleMessage(EJBServerChannel.java:188)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Appears in https://github.com/jbossas/jboss-eap7/pull/2446
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (JBMETA-204) Validation errors in jboss_5_1.xsd (missing webservice-descriptionType)
by ehsavoie Hugonnet (Jira)
[ https://issues.jboss.org/browse/JBMETA-204?page=com.atlassian.jira.plugin... ]
ehsavoie Hugonnet resolved JBMETA-204.
--------------------------------------
Resolution: Out of Date
> Validation errors in jboss_5_1.xsd (missing webservice-descriptionType)
> -----------------------------------------------------------------------
>
> Key: JBMETA-204
> URL: https://issues.jboss.org/browse/JBMETA-204
> Project: JBoss Metadata
> Issue Type: Bug
> Affects Versions: 1.0.1.GA
> Environment: Eclipse 3.4, WebToolsPlatform 3.0
> Reporter: Zachary Bedell
> Assignee: Alexey Loubyansky
> Priority: Critical
>
> An additional validation issue with current trunk jboss_5_1.xsd. The webservicesType complex type references type jboss:webservice-descriptionType which is missing. Copying the type from the jboss_5_0.xsd (which appears directly the webservicesType object around line 1223) resolves the issue.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (JBMETA-403) jbxb_1_0.xsd is invalid
by ehsavoie Hugonnet (Jira)
[ https://issues.jboss.org/browse/JBMETA-403?page=com.atlassian.jira.plugin... ]
ehsavoie Hugonnet updated JBMETA-403:
-------------------------------------
Fix Version/s: 12.0.0.Final
> jbxb_1_0.xsd is invalid
> -----------------------
>
> Key: JBMETA-403
> URL: https://issues.jboss.org/browse/JBMETA-403
> Project: JBoss Metadata
> Issue Type: Bug
> Components: common
> Reporter: Rob Stryker
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> Steps to reproduce:
> 1) Open https://github.com/jboss/metadata/blob/master/common/src/main/resources/s...
> 2) Copy the text of the xsd
> 3) Go to http://www.utilities-online.info/xsdvalidation/
> 4) Paste the xsd into the text box on the right
> 5) Click the button under the text box on the right
> 6) Note the errors
> Not valid.
> Error - Line 94, 47: org.xml.sax.SAXParseException; lineNumber: 94; columnNumber: 47; src-element.3: Element 'class' has both a 'type' attribute and a 'anonymous type' child. Only one of these is allowed for an element.
> Error - Line 19, 77: org.xml.sax.SAXParseException; lineNumber: 19; columnNumber: 77; src-resolve.4.2: Error resolving component 'jbxb:package'. It was detected that 'jbxb:package' is in namespace 'http://www.jboss.org/xml/ns/jbxb', but components from this namespace are not referenceable from schema document 'null'. If this is the incorrect namespace, perhaps the prefix of 'jbxb:package' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'null'.
> Error - Line 19, 77: org.xml.sax.SAXParseException; lineNumber: 19; columnNumber: 77; src-resolve: Cannot resolve the name 'jbxb:package' to a(n) 'element declaration' component.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (JBMETA-403) jbxb_1_0.xsd is invalid
by ehsavoie Hugonnet (Jira)
[ https://issues.jboss.org/browse/JBMETA-403?page=com.atlassian.jira.plugin... ]
ehsavoie Hugonnet closed JBMETA-403.
------------------------------------
> jbxb_1_0.xsd is invalid
> -----------------------
>
> Key: JBMETA-403
> URL: https://issues.jboss.org/browse/JBMETA-403
> Project: JBoss Metadata
> Issue Type: Bug
> Components: common
> Reporter: Rob Stryker
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> Steps to reproduce:
> 1) Open https://github.com/jboss/metadata/blob/master/common/src/main/resources/s...
> 2) Copy the text of the xsd
> 3) Go to http://www.utilities-online.info/xsdvalidation/
> 4) Paste the xsd into the text box on the right
> 5) Click the button under the text box on the right
> 6) Note the errors
> Not valid.
> Error - Line 94, 47: org.xml.sax.SAXParseException; lineNumber: 94; columnNumber: 47; src-element.3: Element 'class' has both a 'type' attribute and a 'anonymous type' child. Only one of these is allowed for an element.
> Error - Line 19, 77: org.xml.sax.SAXParseException; lineNumber: 19; columnNumber: 77; src-resolve.4.2: Error resolving component 'jbxb:package'. It was detected that 'jbxb:package' is in namespace 'http://www.jboss.org/xml/ns/jbxb', but components from this namespace are not referenceable from schema document 'null'. If this is the incorrect namespace, perhaps the prefix of 'jbxb:package' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'null'.
> Error - Line 19, 77: org.xml.sax.SAXParseException; lineNumber: 19; columnNumber: 77; src-resolve: Cannot resolve the name 'jbxb:package' to a(n) 'element declaration' component.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (JBMETA-403) jbxb_1_0.xsd is invalid
by ehsavoie Hugonnet (Jira)
[ https://issues.jboss.org/browse/JBMETA-403?page=com.atlassian.jira.plugin... ]
ehsavoie Hugonnet resolved JBMETA-403.
--------------------------------------
Resolution: Done
> jbxb_1_0.xsd is invalid
> -----------------------
>
> Key: JBMETA-403
> URL: https://issues.jboss.org/browse/JBMETA-403
> Project: JBoss Metadata
> Issue Type: Bug
> Components: common
> Reporter: Rob Stryker
> Priority: Major
>
> Steps to reproduce:
> 1) Open https://github.com/jboss/metadata/blob/master/common/src/main/resources/s...
> 2) Copy the text of the xsd
> 3) Go to http://www.utilities-online.info/xsdvalidation/
> 4) Paste the xsd into the text box on the right
> 5) Click the button under the text box on the right
> 6) Note the errors
> Not valid.
> Error - Line 94, 47: org.xml.sax.SAXParseException; lineNumber: 94; columnNumber: 47; src-element.3: Element 'class' has both a 'type' attribute and a 'anonymous type' child. Only one of these is allowed for an element.
> Error - Line 19, 77: org.xml.sax.SAXParseException; lineNumber: 19; columnNumber: 77; src-resolve.4.2: Error resolving component 'jbxb:package'. It was detected that 'jbxb:package' is in namespace 'http://www.jboss.org/xml/ns/jbxb', but components from this namespace are not referenceable from schema document 'null'. If this is the incorrect namespace, perhaps the prefix of 'jbxb:package' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'null'.
> Error - Line 19, 77: org.xml.sax.SAXParseException; lineNumber: 19; columnNumber: 77; src-resolve: Cannot resolve the name 'jbxb:package' to a(n) 'element declaration' component.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (DROOLS-3000) Enhance data type restrictions UX (decision tables & DT dialog)
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3000?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro commented on DROOLS-3000:
--------------------------------------------
[~uxdlc] Thank you for the mockups. As I commented on Slack, I think that it's important to see how this components should look like when applied in the properties panel (since we're planning to reuse them).
Additionally, I think that would be good to see how the enumeration widget looks like in other types than text:
!enumration-widget.png|thumbnail!
Thank you.
> Enhance data type restrictions UX (decision tables & DT dialog)
> ---------------------------------------------------------------
>
> Key: DROOLS-3000
> URL: https://issues.jboss.org/browse/DROOLS-3000
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E...
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months