[JBoss JIRA] (DROOLS-2376) DSL expression in Guided Rule Editor
by Jeronimo Pat (JIRA)
Jeronimo Pat created DROOLS-2376:
------------------------------------
Summary: DSL expression in Guided Rule Editor
Key: DROOLS-2376
URL: https://issues.jboss.org/browse/DROOLS-2376
Project: Drools
Issue Type: Bug
Components: DSLs Editor, Guided Rule Editor
Affects Versions: 7.5.0.Final
Environment: OS : Windows 10
Server : Apache Tomcat 8
KIE Workbench : 7.5.0
Reporter: Jeronimo Pat
Assignee: Michael Anstis
Attachments: dsl.PNG
Hi,
I created a DSL file , and used the definitions in a Gudied Editor. KIE Workbench 7.5.0.
After saving the rdslr --> closing it (to return to assets view) -->. and clicking open the rdslr again , i observe that the RHS dsl definition get prefixed by a ">" symbol and workbench is unable to analyse expression.
This looks like a bug ..
here is my DSL and rdslr :-
DSL :
[when][]There is a DO = $d : DO()
[when][]- id greater than {id} = id > {id}
[when][]- name is {name} = str == {name}
[then][]Greet =System.out.println("Hello");
rdlsr : Attached in screenshot. Please observe the "<" before the DSL expression "Greet".
The ">" symbol appears automatically.
Thank you !
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9955) Compatibility problem: allow a timeout value of "0" to be set
by Ondra Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-9955?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka commented on WFLY-9955:
---------------------------------------
[~dmlloyd] I see, thank you for the clarification! I haven't realized that from the JTA spec perspective.
> Compatibility problem: allow a timeout value of "0" to be set
> -------------------------------------------------------------
>
> Key: WFLY-9955
> URL: https://issues.jboss.org/browse/WFLY-9955
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Reporter: David Lloyd
> Assignee: Amos Feng
>
> Previously we allowed a transaction timeout value of "0" to be set in the transaction subsystem, meaning "no transaction timeout". After the WF 11 changes, we've stopped allowing that value to be set. This behavior should be restored, with "0" translating into some "very large" value.
> The transaction team has indicated that using {{Integer.MAX_VALUE}} has historically exhibited problems, so a different, smaller-but-still-large value should be used in this case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9955) Compatibility problem: allow a timeout value of "0" to be set
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/WFLY-9955?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on WFLY-9955:
---------------------------------
[~ochaloup] thanks for pointing out and I think it has not been fixed yet.
> Compatibility problem: allow a timeout value of "0" to be set
> -------------------------------------------------------------
>
> Key: WFLY-9955
> URL: https://issues.jboss.org/browse/WFLY-9955
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Reporter: David Lloyd
> Assignee: Amos Feng
>
> Previously we allowed a transaction timeout value of "0" to be set in the transaction subsystem, meaning "no transaction timeout". After the WF 11 changes, we've stopped allowing that value to be set. This behavior should be restored, with "0" translating into some "very large" value.
> The transaction team has indicated that using {{Integer.MAX_VALUE}} has historically exhibited problems, so a different, smaller-but-still-large value should be used in this case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9890) "ISPN000476: Timed out waiting for responses for request X from node Y" immediately after node Y rejoins the cluster (failover)
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-9890?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on WFLY-9890:
------------------------------------
[~mvinkler] Are there actually any sampling errors? I see the timeout waiting for responses from perf20 immediately following perf20 leaving the cluster - which makes sense. These should not result in sampling errors though.
> "ISPN000476: Timed out waiting for responses for request X from node Y" immediately after node Y rejoins the cluster (failover)
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9890
> URL: https://issues.jboss.org/browse/WFLY-9890
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 12.0.0.Beta1
> Reporter: Michal Vinkler
> Assignee: Paul Ferraro
> Priority: Critical
> Fix For: 13.0.0.Beta1
>
>
> Seen in SF failover tests - scenarios:
> failover-http-granular-shutdown-repl-sync (replication granularity is set to ATTRIBUTE level)
> failover-http-session-jvmkill-repl-sync (replication granularity is set to SESSION level)
> Description: In the failover test, each server is shut down and after some time it rejoins the cluster. After joining the cluster again, the load is distributed to this node. It seems that first request for some session handled by that node produces ERROR in the log of some other server until the time another cluster topology change occurs.
> Stacktrace of the error:
> {code}
> [JBossINF] [0m[31m10:18:00,256 ERROR [org.infinispan.interceptors.impl.InvocationContextInterceptor] (timeout-thread--p12-t1) ISPN000136: Error executing command PrepareCommand, writing keys [SessionCreationMetaDataKey(f25_wwXXpvtNC9QTHZUtSwhmEUmg-wI77RL_17b9), SessionAccessMetaDataKey(f25_wwXXpvtNC9QTHZUtSwhmEUmg-wI77RL_17b9), SessionAttributeKey(f25_wwXXpvtNC9QTHZUtSwhmEUmg-wI77RL_17b9[1])]: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 30250 from perf18
> [JBossINF] at org.infinispan.remoting.transport.impl.MultiTargetRequest.onTimeout(MultiTargetRequest.java:163)
> [JBossINF] at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:86)
> [JBossINF] at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:21)
> [JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [JBossINF] at java.lang.Thread.run(Thread.java:748)
> {code}
> Client gets the stale data:
> {code}
> 2018/02/21 10:18:00:272 EST [WARN ][Runner - 16] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 60, received 59, Runner: 16>
> org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 60, received 59, Runner: 16
> at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:133)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Example - timeline:
> {code}
> 4 servers are running, 2000 clients, no issue in the beggining
> 2018/02/21 10:16:43:234 EST [INFO ][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Node 0 (perf18) is down.
> - still no issues
> 2018/02/21 10:17:43:234 EST [INFO ][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Bringing back node 0 (perf18)
> 2018/02/21 10:17:55:611 EST [INFO ][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Node 0 (perf18) is up.
> 2018/02/21 10:18:00:272 EST [WARN ][Runner - 16] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 60, received 59, Runner: 16>
> {code}
> perf20 started logging the errors meanwhile and stopped only after perf19 was shut down:
> {code}
> [JBossINF] [0m[0m10:17:50,227 INFO [org.infinispan.CLUSTER] (thread-19,ejb,perf20) ISPN000094: Received new cluster view for channel ejb: [perf19|5] (4) [perf19, perf20, perf21, perf18]
> [JBossINF] [0m[0m10:17:50,228 INFO [org.infinispan.CLUSTER] (thread-19,ejb,perf20) ISPN100000: Node perf18 joined the cluster
> [JBossINF] [0m[31m10:18:00,256 ERROR [org.infinispan.interceptors.impl.InvocationContextInterceptor] (timeout-thread--p12-t1) ISPN000136: Error executing command PrepareCommand, writing keys [SessionCreationMetaDataKey(f25_wwXXpvtNC9QTHZUtSwhmEUmg-wI77RL_17b9), SessionAccessMetaDataKey(f25_wwXXpvtNC9QTHZUtSwhmEUmg-wI77RL_17b9), SessionAttributeKey(f25_wwXXpvtNC9QTHZUtSwhmEUmg-wI77RL_17b9[1])]: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 30250 from perf18
> [JBossINF] at org.infinispan.remoting.transport.impl.MultiTargetRequest.onTimeout(MultiTargetRequest.java:163)
> [JBossINF] at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:86)
> [JBossINF] at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:21)
> [JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [JBossINF] at java.lang.Thread.run(Thread.java:748)
> [JBossINF]
> {code}
> There were no issues in this scenario in EAP 7.1.0.GA.
> Links:
> Clients: http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-fa...
> perf18: http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-fa...
> perf20: http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-fa...
> Another test:
> perf19: http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-fa...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3677) get-provider-points return /profile addresses for host level resources
by Claudio Miranda (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3677?page=com.atlassian.jira.plugi... ]
Claudio Miranda updated WFCORE-3677:
------------------------------------
Component/s: Domain Management
(was: Security)
> get-provider-points return /profile addresses for host level resources
> ----------------------------------------------------------------------
>
> Key: WFCORE-3677
> URL: https://issues.jboss.org/browse/WFCORE-3677
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Claudio Miranda
> Assignee: Darran Lofthouse
> Priority: Minor
>
> key-manager resource at /host=master/subsystem=elytron/key-manager=*
> contains the "key-store" attribute, which has a "capability-reference" => "org.wildfly.security.key-store"
> get-provider-points returns /profile addresses that should not be a valid reference for a host level resource
> {code}
> /host=master/core-service=capability-registry:get-provider-points(name="org.wildfly.security.key-store")
> {
> "outcome" => "success",
> "result" => [
> "/host=master/subsystem=elytron/key-store=*",
> "/host=master/subsystem=elytron/ldap-key-store=*",
> "/host=master/subsystem=elytron/filtering-key-store=*",
> "/profile=*/subsystem=elytron/key-store=*",
> "/profile=*/subsystem=elytron/ldap-key-store=*",
> "/profile=*/subsystem=elytron/filtering-key-store=*",
> "/profile=*/subsystem=security/elytron-key-store=*",
> "/profile=*/subsystem=security/elytron-trust-store=*"
> ]
> }
> {code}
> A test case
> {code}
> /profile=full/subsystem=elytron/key-store=ks_full:add(credential-reference={clear-text=senha},type=JKS)
> /host=master/subsystem=elytron/key-manager=my_km:add(key-store=ks_full,credential-reference={clear-text=senha})
> {
> "outcome" => "failed",
> "result" => {},
> "failure-description" => {"host-failure-descriptions" => {"master" => "WFLYCTL0369: Required capabilities are not available:
> org.wildfly.security.key-store.ks_full in context 'host'; Possible registration points for this capability:
> /host=master/subsystem=elytron/key-store=*
> /host=master/subsystem=elytron/ldap-key-store=*
> /host=master/subsystem=elytron/filtering-key-store=*
> /profile=*/subsystem=elytron/key-store=*
> /profile=*/subsystem=elytron/ldap-key-store=*
> /profile=*/subsystem=elytron/filtering-key-store=*
> /profile=*/subsystem=security/elytron-key-store=*
> /profile=*/subsystem=security/elytron-trust-store=*"}},
> "rolled-back" => true
> }
> {code}
> The returned addresses in the error message should contains only valid addresses.
> side note: CLI code completion works correctly in not showing resources from /profile addresses.
> /host=master/subsystem=elytron/key-manager=my_km:add(key-store=<tab>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3677) get-provider-points return /profile addresses for host level resources
by Claudio Miranda (JIRA)
Claudio Miranda created WFCORE-3677:
---------------------------------------
Summary: get-provider-points return /profile addresses for host level resources
Key: WFCORE-3677
URL: https://issues.jboss.org/browse/WFCORE-3677
Project: WildFly Core
Issue Type: Enhancement
Components: Security
Reporter: Claudio Miranda
Assignee: Darran Lofthouse
Priority: Minor
key-manager resource at /host=master/subsystem=elytron/key-manager=*
contains the "key-store" attribute, which has a "capability-reference" => "org.wildfly.security.key-store"
get-provider-points returns /profile addresses that should not be a valid reference for a host level resource
{code}
/host=master/core-service=capability-registry:get-provider-points(name="org.wildfly.security.key-store")
{
"outcome" => "success",
"result" => [
"/host=master/subsystem=elytron/key-store=*",
"/host=master/subsystem=elytron/ldap-key-store=*",
"/host=master/subsystem=elytron/filtering-key-store=*",
"/profile=*/subsystem=elytron/key-store=*",
"/profile=*/subsystem=elytron/ldap-key-store=*",
"/profile=*/subsystem=elytron/filtering-key-store=*",
"/profile=*/subsystem=security/elytron-key-store=*",
"/profile=*/subsystem=security/elytron-trust-store=*"
]
}
{code}
A test case
{code}
/profile=full/subsystem=elytron/key-store=ks_full:add(credential-reference={clear-text=senha},type=JKS)
/host=master/subsystem=elytron/key-manager=my_km:add(key-store=ks_full,credential-reference={clear-text=senha})
{
"outcome" => "failed",
"result" => {},
"failure-description" => {"host-failure-descriptions" => {"master" => "WFLYCTL0369: Required capabilities are not available:
org.wildfly.security.key-store.ks_full in context 'host'; Possible registration points for this capability:
/host=master/subsystem=elytron/key-store=*
/host=master/subsystem=elytron/ldap-key-store=*
/host=master/subsystem=elytron/filtering-key-store=*
/profile=*/subsystem=elytron/key-store=*
/profile=*/subsystem=elytron/ldap-key-store=*
/profile=*/subsystem=elytron/filtering-key-store=*
/profile=*/subsystem=security/elytron-key-store=*
/profile=*/subsystem=security/elytron-trust-store=*"}},
"rolled-back" => true
}
{code}
The returned addresses in the error message should contains only valid addresses.
side note: CLI code completion works correctly in not showing resources from /profile addresses.
/host=master/subsystem=elytron/key-manager=my_km:add(key-store=<tab>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9955) Compatibility problem: allow a timeout value of "0" to be set
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-9955?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-9955:
-----------------------------------
[~ochaloup] it can't be undefined because the JTA spec doesn't have such a concept for e.g. TransactionManager, so we can't rely on providers always having that capability. Coupled with it being considered poor practice, I don't feel like we should introduce this as a supported behavior into any more levels than we need to.
> Compatibility problem: allow a timeout value of "0" to be set
> -------------------------------------------------------------
>
> Key: WFLY-9955
> URL: https://issues.jboss.org/browse/WFLY-9955
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Reporter: David Lloyd
> Assignee: Amos Feng
>
> Previously we allowed a transaction timeout value of "0" to be set in the transaction subsystem, meaning "no transaction timeout". After the WF 11 changes, we've stopped allowing that value to be set. This behavior should be restored, with "0" translating into some "very large" value.
> The transaction team has indicated that using {{Integer.MAX_VALUE}} has historically exhibited problems, so a different, smaller-but-still-large value should be used in this case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months