[JBoss JIRA] (DROOLS-1244) TimedRuleExectionOption typing mistake
by Matteo Mortari (JIRA)
Matteo Mortari created DROOLS-1244:
--------------------------------------
Summary: TimedRuleExectionOption typing mistake
Key: DROOLS-1244
URL: https://issues.jboss.org/browse/DROOLS-1244
Project: Drools
Issue Type: Enhancement
Affects Versions: 7.0.0.Beta1
Reporter: Matteo Mortari
Assignee: Matteo Mortari
Priority: Minor
TimedRuleExectionOption typo in class definition and documentation.
Impacts:
* code changes
* System property / configuration
* to be properly documented (as a breaking change)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JGRP-2094) Add convenience method Rsp.readIn
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/JGRP-2094?page=com.atlassian.jira.plugin.... ]
Radim Vansa updated JGRP-2094:
------------------------------
Description:
In Infinispan, during a staggered get we prepare several {{Rsp}} s in {{RspList}} and then for each {{Rsp}} we send one message. As the {{RspList}} can be accessed by multiple threads but we don't want to synchronize the access, we just get the {{Rsp}} and fill it from the (other) received {{Rsp}}. However the fill requires several ifs:
{code}
if (rsp.hasException()) {
futureRsp.setException(rsp.getException());
} else if (rsp.wasSuspected()) {
futureRsp.setSuspected();
} else if (rsp.wasUnreachable()) {
futureRsp.setUnreachable();
} else {
futureRsp.setValue(rsp.getValue());
}
{code}
Let's add a convenience method that will just read in the flags and value.
was:
In Infinispan, during a staggered get we prepare several {{Rsp}}s in {{RspList}} and then for each {{Rsp}} we send one message. As the {{RspList}} can be accessed by multiple threads but we don't want to synchronize the access, we just get the {{Rsp}} and fill it from the (other) received {{Rsp}}. However the fill requires several ifs:
{code}
if (rsp.hasException()) {
futureRsp.setException(rsp.getException());
} else if (rsp.wasSuspected()) {
futureRsp.setSuspected();
} else if (rsp.wasUnreachable()) {
futureRsp.setUnreachable();
} else {
futureRsp.setValue(rsp.getValue());
}
{code}
Let's add a convenience method that will just read in the flags and value.
> Add convenience method Rsp.readIn
> ---------------------------------
>
> Key: JGRP-2094
> URL: https://issues.jboss.org/browse/JGRP-2094
> Project: JGroups
> Issue Type: Enhancement
> Affects Versions: 3.6.10, 4.0
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Priority: Minor
>
> In Infinispan, during a staggered get we prepare several {{Rsp}} s in {{RspList}} and then for each {{Rsp}} we send one message. As the {{RspList}} can be accessed by multiple threads but we don't want to synchronize the access, we just get the {{Rsp}} and fill it from the (other) received {{Rsp}}. However the fill requires several ifs:
> {code}
> if (rsp.hasException()) {
> futureRsp.setException(rsp.getException());
> } else if (rsp.wasSuspected()) {
> futureRsp.setSuspected();
> } else if (rsp.wasUnreachable()) {
> futureRsp.setUnreachable();
> } else {
> futureRsp.setValue(rsp.getValue());
> }
> {code}
> Let's add a convenience method that will just read in the flags and value.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JGRP-2094) Add convenience method Rsp.readIn
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/JGRP-2094?page=com.atlassian.jira.plugin.... ]
Radim Vansa updated JGRP-2094:
------------------------------
Affects Version/s: 4.0
> Add convenience method Rsp.readIn
> ---------------------------------
>
> Key: JGRP-2094
> URL: https://issues.jboss.org/browse/JGRP-2094
> Project: JGroups
> Issue Type: Enhancement
> Affects Versions: 3.6.10, 4.0
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Priority: Minor
>
> In Infinispan, during a staggered get we prepare several {{Rsp}}s in {{RspList}} and then for each {{Rsp}} we send one message. As the {{RspList}} can be accessed by multiple threads but we don't want to synchronize the access, we just get the {{Rsp}} and fill it from the (other) received {{Rsp}}. However the fill requires several ifs:
> {code}
> if (rsp.hasException()) {
> futureRsp.setException(rsp.getException());
> } else if (rsp.wasSuspected()) {
> futureRsp.setSuspected();
> } else if (rsp.wasUnreachable()) {
> futureRsp.setUnreachable();
> } else {
> futureRsp.setValue(rsp.getValue());
> }
> {code}
> Let's add a convenience method that will just read in the flags and value.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JGRP-2094) Add convenience method Rsp.readIn
by Radim Vansa (JIRA)
Radim Vansa created JGRP-2094:
---------------------------------
Summary: Add convenience method Rsp.readIn
Key: JGRP-2094
URL: https://issues.jboss.org/browse/JGRP-2094
Project: JGroups
Issue Type: Enhancement
Affects Versions: 3.6.10
Reporter: Radim Vansa
Assignee: Bela Ban
Priority: Minor
In Infinispan, during a staggered get we prepare several {{Rsp}}s in {{RspList}} and then for each {{Rsp}} we send one message. As the {{RspList}} can be accessed by multiple threads but we don't want to synchronize the access, we just get the {{Rsp}} and fill it from the (other) received {{Rsp}}. However the fill requires several ifs:
{code}
if (rsp.hasException()) {
futureRsp.setException(rsp.getException());
} else if (rsp.wasSuspected()) {
futureRsp.setSuspected();
} else if (rsp.wasUnreachable()) {
futureRsp.setUnreachable();
} else {
futureRsp.setValue(rsp.getValue());
}
{code}
Let's add a convenience method that will just read in the flags and value.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JGRP-2094) Add convenience method Rsp.readIn
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/JGRP-2094?page=com.atlassian.jira.plugin.... ]
Radim Vansa reassigned JGRP-2094:
---------------------------------
Assignee: Radim Vansa (was: Bela Ban)
> Add convenience method Rsp.readIn
> ---------------------------------
>
> Key: JGRP-2094
> URL: https://issues.jboss.org/browse/JGRP-2094
> Project: JGroups
> Issue Type: Enhancement
> Affects Versions: 3.6.10
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Priority: Minor
>
> In Infinispan, during a staggered get we prepare several {{Rsp}}s in {{RspList}} and then for each {{Rsp}} we send one message. As the {{RspList}} can be accessed by multiple threads but we don't want to synchronize the access, we just get the {{Rsp}} and fill it from the (other) received {{Rsp}}. However the fill requires several ifs:
> {code}
> if (rsp.hasException()) {
> futureRsp.setException(rsp.getException());
> } else if (rsp.wasSuspected()) {
> futureRsp.setSuspected();
> } else if (rsp.wasUnreachable()) {
> futureRsp.setUnreachable();
> } else {
> futureRsp.setValue(rsp.getValue());
> }
> {code}
> Let's add a convenience method that will just read in the flags and value.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-6903) Configuring session cookie config except for cookie name yields NPE in mod_cluster when registering with the proxy
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6903?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-6903:
---------------------------------
Component/s: Mod_Cluster
> Configuring session cookie config except for cookie name yields NPE in mod_cluster when registering with the proxy
> ------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6903
> URL: https://issues.jboss.org/browse/WFLY-6903
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Mod_Cluster
> Affects Versions: 10.0.0.Final, 10.1.0.CR1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 11.0.0.Alpha1, 11.0.0.Beta1
>
>
> To reproduce run e.g.
> {noformat}
> /subsystem=undertow/servlet-container=default/setting=session-cookie:add(http-only=true)
> {noformat}
> yields NPE when registering with the proxy
> {noformat}2016-08-01 14:42:20,623 ERROR [org.jboss.modcluster] (UndertowEventHandlerAdapter - 1) MODCLUSTER000042: Error MEM sending STATUS command to apache-server/10.0.0.1:6666, configuration will be reset: MEM: Can't read node
> 2016-08-01 14:42:30,626 ERROR [org.jboss.mod_cluster.undertow] (UndertowEventHandlerAdapter - 1) null: java.lang.NullPointerException
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPRequestFactory.createConfigRequest(DefaultMCMPRequestFactory.java:128)
> at org.jboss.modcluster.mcmp.impl.ResetRequestSourceImpl.getResetRequests(ResetRequestSourceImpl.java:89)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:399)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:365)
> at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:457)
> at org.wildfly.mod_cluster.undertow.UndertowEventHandlerAdapter.run(UndertowEventHandlerAdapter.java:179)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFCORE-1682) Missleading tab completion for edit-batch-line command
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1682?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise reassigned WFCORE-1682:
--------------------------------------------
Assignee: Jean-Francois Denise (was: Alexey Loubyansky)
> Missleading tab completion for edit-batch-line command
> ------------------------------------------------------
>
> Key: WFCORE-1682
> URL: https://issues.jboss.org/browse/WFCORE-1682
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Petr Kremensky
> Assignee: Jean-Francois Denise
>
> Tab completion for edit-batch-list command suggest to use --line-number as a command option, but that is not how the command works.
> *command usage*
> {noformat}
> [standalone@localhost:9990 /] batch
> [standalone@localhost:9990 / #] :read-resource
> [standalone@localhost:9990 / #] list-batch
> #1 /:read-resource
> [standalone@localhost:9990 / #] edit-batch-line 1 :read-attribute(name=launch-type)
> #1 :read-attribute(name=launch-type)
> [standalone@localhost:9990 / #] list-batch
> #1 :read-attribute(name=launch-type)
> {noformat}
> *actual*
> {noformat}
> [standalone@localhost:9990 / #] edit-batch-line <TAB>
> [standalone@localhost:9990 / #] edit-batch-line --<TAB>
> --help --line-number
> [standalone@localhost:9990 / #] edit-batch-line --line-number=1 :read-attribute(name=launch-type)
> Failed to parse line number '--line-number=1': For input string: "--line-number=1"
> {noformat}
> {{--line-number}} shouldn't be offered by tab completion for the command.
> Misleading tab completion ends up with syntax error.
> *expected*
> {noformat}
> [standalone@localhost:9990 / #] edit-batch-line <TAB>
> --help
> {noformat}
> The issue is a regression against EAP 7.0.0 release.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months