[JBoss JIRA] (DROOLS-2699) Beta node indexes don't support type coercion
by Toshiya Kobayashi (JIRA)
Toshiya Kobayashi created DROOLS-2699:
-----------------------------------------
Summary: Beta node indexes don't support type coercion
Key: DROOLS-2699
URL: https://issues.jboss.org/browse/DROOLS-2699
Project: Drools
Issue Type: Bug
Components: core engine
Reporter: Toshiya Kobayashi
Assignee: Mario Fusco
When there is a type mismatch (e.g. String vs Integer) in a constraint, usually a type is coerced and a rule is fired.
{code}
rule "R2"
when
$f : MyFactB( strData == 20 )
then
System.out.println( "R2 fired : $f = " + $f );
end
{code}
As far as I investigate, in case of AlphaNode, MVEL does the coercion. Also AlphaNode hashing does the coercion (https://github.com/kiegroup/drools/blob/7.5.0.Final/drools-core/src/main/...).
However, in case of JoinNode, it doesn't coerce so doesn't fire.
{code}
rule "R1"
when
MyFactA( $i : intData )
$f : MyFactB( strData == $i )
then
System.out.println( "R1 fired : $f = " + $f );
end
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2698) Beta node indexes don't support type coercion
by Toshiya Kobayashi (JIRA)
Toshiya Kobayashi created DROOLS-2698:
-----------------------------------------
Summary: Beta node indexes don't support type coercion
Key: DROOLS-2698
URL: https://issues.jboss.org/browse/DROOLS-2698
Project: Drools
Issue Type: Bug
Components: core engine
Reporter: Toshiya Kobayashi
Assignee: Mario Fusco
When there is a type mismatch (e.g. String vs Integer) in a constraint, usually a type is coerced and a rule is fired.
{code}
rule "R2"
when
$f : MyFactB( strData == 20 )
then
System.out.println( "R2 fired : $f = " + $f );
end
{code}
As far as I investigate, in case of AlphaNode, MVEL does the coercion. Also AlphaNode hashing does the coercion (https://github.com/kiegroup/drools/blob/7.5.0.Final/drools-core/src/main/...).
However, in case of JoinNode, it doesn't coerce so doesn't fire.
{code}
rule "R1"
when
MyFactA( $i : intData )
$f : MyFactB( strData == $i )
then
System.out.println( "R1 fired : $f = " + $f );
end
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10629) Server startup wrongly deploys all xml files and never stops
by Nuno Godinho de Matos (JIRA)
[ https://issues.jboss.org/browse/WFLY-10629?page=com.atlassian.jira.plugin... ]
Nuno Godinho de Matos commented on WFLY-10629:
----------------------------------------------
I am pretty certain it is the eclipse plugin or the settings of the plugin in eclipse oxygen.
As I said, if I go back to my eclipse indigo workspace and use my problematic wildfly instance and start it up, I never see an ifinite standalone.xml backup and deploy.
I have only seen this happening on oxygen.
Thanks
> Server startup wrongly deploys all xml files and never stops
> ------------------------------------------------------------
>
> Key: WFLY-10629
> URL: https://issues.jboss.org/browse/WFLY-10629
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Reporter: Arnie Morein
> Assignee: Jason Greene
>
> I have downloaded WF 12 and 13, then imported each into Eclipse (Oxygen.3a Release (4.7.3a)), OS is Win 7/x64; then used add-user to set up admin user. Then from both the command line and from within Eclipse, when the software starts up all of the xml configuration files get deployed at the same time despite the fact that the --server-config=standalone.xml parameter is present in either environment. What's worse, it starts versioning them and re-deploying them over and over and over again.
> {quote}
> 15:45:42,229 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started client-mappings cache from ejb container
> 15:45:42,319 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone.xml" (runtime-name : "standalone.xml")
> 15:45:42,320 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-load-balancer.xml" (runtime-name : "standalone-load-balancer.xml")
> 15:45:42,324 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-ha.xml" (runtime-name : "standalone-ha.xml")
> 15:45:42,324 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-full.xml" (runtime-name : "standalone-full.xml")
> 15:45:42,325 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-full-ha.xml" (runtime-name : "standalone-full-ha.xml")
> 15:45:42,326 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-ee8.xml" (runtime-name : "standalone-ee8.xml")
> 15:45:42,407 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
> 15:45:42,410 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> 15:45:42,411 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> 15:45:42,411 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 13.0.0.Final (WildFly Core 5.0.0.Final) started in 6285ms - Started 549 of 746 services (326 se
> rvices are lazy, passive or on-demand)
> 15:45:42,575 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:45:42,578 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "standalone.boot.xml" (runtime-name: "standalone.boot.xml")
> 15:45:42,581 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "standalone.initial.xml" (runtime-name: "standalone.initial.xml")
> 15:45:42,724 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.last.xml" (runtime-name : "standalone.last.xml")
> 15:45:42,725 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.initial.xml" (runtime-name : "standalone.initial.xml")
> 15:45:42,726 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.boot.xml" (runtime-name : "standalone.boot.xml")
> 15:45:47,921 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 28ms
> 15:45:47,928 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
> 15:45:47,930 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "standalone.v1.xml" (runtime-name: "standalone.v1.xml")
> 15:45:47,982 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 55ms
> 15:45:47,984 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:45:48,059 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml"
> 15:45:48,060 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.v1.xml" (runtime-name : "standalone.v1.xml")
> 15:45:48,060 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.xml" with deployment "standalone.xml"
> 15:45:53,233 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 13ms
> 15:45:53,236 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "standalone.v2.xml" (runtime-name: "standalone.v2.xml")
> 15:45:53,237 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
> 15:45:53,249 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 15ms
> 15:45:53,252 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:45:53,340 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml"
> 15:45:53,341 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.v2.xml" (runtime-name : "standalone.v2.xml")
> 15:45:53,342 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.xml" with deployment "standalone.xml"{quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10661) IllegalMonitorStateException if session invalidated after redirect
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-10661?page=com.atlassian.jira.plugin... ]
Stuart Douglas reassigned WFLY-10661:
-------------------------------------
Assignee: Paul Ferraro (was: Stuart Douglas)
> IllegalMonitorStateException if session invalidated after redirect
> ------------------------------------------------------------------
>
> Key: WFLY-10661
> URL: https://issues.jboss.org/browse/WFLY-10661
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Environment: EAP 7.1.3
> Reporter: Aaron Ogburn
> Assignee: Paul Ferraro
> Attachments: undertow1374.war
>
>
> response.sendRedirect unlocks the session. So attempting session.invalidate after any sendRedirect throws an IllegalMonitorStateException when it attempts to unlock it again:
> {code}
> 16:35:11,267 INFO [stdout] (default task-1) --------------------------->StampedLock.unlock java.util.concurrent.locks.StampedLock@2a03fe4a[Unlocked] 257
> 16:35:11,267 INFO [stdout] (default task-1) java.util.concurrent.locks.StampedLock.unlock(StampedLock.java:603)
> 16:35:11,267 INFO [stdout] (default task-1) org.wildfly.clustering.web.undertow.session.DistributableSessionManager.lambda$getSessionCloseTask$1(DistributableSessionManager.java:103)
> 16:35:11,267 INFO [stdout] (default task-1) org.wildfly.clustering.web.undertow.session.DistributableSession.requestDone(DistributableSession.java:96)
> 16:35:11,267 INFO [stdout] (default task-1) io.undertow.servlet.spec.ServletContextImpl.updateSessionAccessTime(ServletContextImpl.java:860)
> 16:35:11,267 INFO [stdout] (default task-1) io.undertow.servlet.spec.HttpServletResponseImpl.responseDone(HttpServletResponseImpl.java:572)
> 16:35:11,267 INFO [stdout] (default task-1) io.undertow.servlet.spec.HttpServletResponseImpl.sendRedirect(HttpServletResponseImpl.java:203)
> 16:35:11,267 INFO [stdout] (default task-1) org.apache.jsp.hi_jsp._jspService(hi_jsp.java:136)
> ...
> Caused by: java.lang.IllegalMonitorStateException
> at java.util.concurrent.locks.StampedLock.unlock(StampedLock.java:609)
> at org.wildfly.clustering.web.undertow.session.DistributableSessionManager.lambda$getSessionCloseTask$1(DistributableSessionManager.java:103)
> at org.wildfly.clustering.web.undertow.session.DistributableSession.invalidate(DistributableSession.java:218)
> at io.undertow.servlet.spec.HttpSessionImpl.invalidate(HttpSessionImpl.java:198)
> at org.apache.jsp.hi_jsp._jspService(hi_jsp.java:137)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:433)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10661) IllegalMonitorStateException if session invalidated after redirect
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-10661?page=com.atlassian.jira.plugin... ]
Stuart Douglas moved UNDERTOW-1374 to WFLY-10661:
-------------------------------------------------
Project: WildFly (was: Undertow)
Key: WFLY-10661 (was: UNDERTOW-1374)
Component/s: Clustering
(was: Servlet)
Affects Version/s: (was: 1.4.18.SP6)
(was: 1.4.25.Final)
> IllegalMonitorStateException if session invalidated after redirect
> ------------------------------------------------------------------
>
> Key: WFLY-10661
> URL: https://issues.jboss.org/browse/WFLY-10661
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Environment: EAP 7.1.3
> Reporter: Aaron Ogburn
> Assignee: Stuart Douglas
> Attachments: undertow1374.war
>
>
> response.sendRedirect unlocks the session. So attempting session.invalidate after any sendRedirect throws an IllegalMonitorStateException when it attempts to unlock it again:
> {code}
> 16:35:11,267 INFO [stdout] (default task-1) --------------------------->StampedLock.unlock java.util.concurrent.locks.StampedLock@2a03fe4a[Unlocked] 257
> 16:35:11,267 INFO [stdout] (default task-1) java.util.concurrent.locks.StampedLock.unlock(StampedLock.java:603)
> 16:35:11,267 INFO [stdout] (default task-1) org.wildfly.clustering.web.undertow.session.DistributableSessionManager.lambda$getSessionCloseTask$1(DistributableSessionManager.java:103)
> 16:35:11,267 INFO [stdout] (default task-1) org.wildfly.clustering.web.undertow.session.DistributableSession.requestDone(DistributableSession.java:96)
> 16:35:11,267 INFO [stdout] (default task-1) io.undertow.servlet.spec.ServletContextImpl.updateSessionAccessTime(ServletContextImpl.java:860)
> 16:35:11,267 INFO [stdout] (default task-1) io.undertow.servlet.spec.HttpServletResponseImpl.responseDone(HttpServletResponseImpl.java:572)
> 16:35:11,267 INFO [stdout] (default task-1) io.undertow.servlet.spec.HttpServletResponseImpl.sendRedirect(HttpServletResponseImpl.java:203)
> 16:35:11,267 INFO [stdout] (default task-1) org.apache.jsp.hi_jsp._jspService(hi_jsp.java:136)
> ...
> Caused by: java.lang.IllegalMonitorStateException
> at java.util.concurrent.locks.StampedLock.unlock(StampedLock.java:609)
> at org.wildfly.clustering.web.undertow.session.DistributableSessionManager.lambda$getSessionCloseTask$1(DistributableSessionManager.java:103)
> at org.wildfly.clustering.web.undertow.session.DistributableSession.invalidate(DistributableSession.java:218)
> at io.undertow.servlet.spec.HttpSessionImpl.invalidate(HttpSessionImpl.java:198)
> at org.apache.jsp.hi_jsp._jspService(hi_jsp.java:137)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:433)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2697) [DMN Designer] Improve readability of node labels
by Michael Anstis (JIRA)
Michael Anstis created DROOLS-2697:
--------------------------------------
Summary: [DMN Designer] Improve readability of node labels
Key: DROOLS-2697
URL: https://issues.jboss.org/browse/DROOLS-2697
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Affects Versions: 7.8.0.Final
Reporter: Michael Anstis
Assignee: Michael Anstis
Node names are bold text without background rectangle and hence _merge_ into the node SVG. It'd be nicer to change font to regular and provide a (white) background rectangle to improve readability.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2563) [DMN Editor] Add support to define data-types
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2563?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2563:
----------------------------------------
[~uxdlc] [~karreiro] I did propose in the original description that this may be transformed into a top-level JIRA if the effort required suggested so.
[~karreiro] You mention in today's meeting that you wanted to add sub-tasks so it might be worth transforming sooner than later.
> [DMN Editor] Add support to define data-types
> ---------------------------------------------
>
> Key: DROOLS-2563
> URL: https://issues.jboss.org/browse/DROOLS-2563
> Project: Drools
> Issue Type: Sub-task
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Guilherme Carreiro
>
> As a practitioner, I want to be able to define Data Types in the UI, so that when the DMN engine evaluates a decision table input/output it will check if the type of the value matches the specified type.
> Verification conditions:
> Support added for the User to define data-types ({{ItemDefinition}}).
> This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years