[JBoss JIRA] (WFLY-8240) Upgrade jgroups-azure to 1.1.0.Final
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-8240:
------------------------------------
Summary: Upgrade jgroups-azure to 1.1.0.Final
Key: WFLY-8240
URL: https://issues.jboss.org/browse/WFLY-8240
Project: WildFly
Issue Type: Task
Components: Clustering
Reporter: Radoslav Husar
Assignee: Radoslav Husar
* azure-storage client v5 upgrade
* wrong configuration parameters now correctly fail fast
* project testable with JDK9
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (WFLY-8239) Upgrade jgroups-azure to 1.1.0.Final
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-8239:
------------------------------------
Summary: Upgrade jgroups-azure to 1.1.0.Final
Key: WFLY-8239
URL: https://issues.jboss.org/browse/WFLY-8239
Project: WildFly
Issue Type: Task
Components: Clustering
Reporter: Radoslav Husar
Assignee: Radoslav Husar
* azure-storage client v5 upgrade
* wrong configuration parameters now correctly fail fast
* project testable with JDK9
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (WFLY-8238) Unable to undefine credential-reference
by Claudio Miranda (JIRA)
[ https://issues.jboss.org/browse/WFLY-8238?page=com.atlassian.jira.plugin.... ]
Claudio Miranda updated WFLY-8238:
----------------------------------
Description:
A bridge is added and a credential-reference is set.
However a "password" attribute cannot be set as the alternatives constraint validates the data, but the password attribute has a default value.
Also neither credential-reference and password are required=true, so they may be undefined.
{code}
/profile=full/subsystem=messaging-activemq/server=default/bridge=test1:add(discovery-group=mane,queue-name=DLQ,forwarding-address=DLQ)
/profile=full/subsystem=messaging-activemq/server=default/bridge=test1:write-attribute(name=credential-reference,value={clear-text=senha1})
/profile=full/subsystem=messaging-activemq/server=default/bridge=test1:undefine-attribute(name=credential-reference)
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description" => "WFLYMSGAMQ0069: Attribute (credential-reference) can not been undefined as the resource does not define any alternative to this attribute."},
"rolled-back" => true
}
{code}
The same problem, when user adds a bridge with a password and later wants to undefine it to add a credential-reference
{code}
/profile=full/subsystem=messaging-activemq/server=default/bridge=test1:add(discovery-group=mane,queue-name=DLQ,forwarding-address=DLQ,password=senha1)
/profile=full/subsystem=messaging-activemq/server=default/bridge=test1:undefine-attribute(name=password)
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description" => "WFLYMSGAMQ0069: Attribute (password) can not been undefined as the resource does not define any alternative to this attribute."},
"rolled-back" => true
}
{code}
was:
A bridge is added and a credential-reference is set.
However a "password" attribute cannot be set as the alternatives constraint validates the data, but the password attribute has a default value.
Also neither credential-reference and password are required=true, so they may be undefined.
{code}
/profile=full/subsystem=messaging-activemq/server=default/bridge=test1:add(discovery-group=mane,queue-name=DLQ,forwarding-address=DLQ)
/profile=full/subsystem=messaging-activemq/server=default/bridge=test1:write-attribute(name=credential-reference,value={clear-text=senha1})
/profile=full/subsystem=messaging-activemq/server=default/bridge=test1:undefine-attribute(name=credential-reference)
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description" => "WFLYMSGAMQ0069: Attribute (credential-reference) can not been undefined as the resource does not define any alternative to this attribute."},
"rolled-back" => true
}
{code}
> Unable to undefine credential-reference
> ---------------------------------------
>
> Key: WFLY-8238
> URL: https://issues.jboss.org/browse/WFLY-8238
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Security
> Reporter: Claudio Miranda
> Assignee: Jeff Mesnil
>
> A bridge is added and a credential-reference is set.
> However a "password" attribute cannot be set as the alternatives constraint validates the data, but the password attribute has a default value.
> Also neither credential-reference and password are required=true, so they may be undefined.
> {code}
> /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:add(discovery-group=mane,queue-name=DLQ,forwarding-address=DLQ)
> /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:write-attribute(name=credential-reference,value={clear-text=senha1})
> /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:undefine-attribute(name=credential-reference)
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "WFLYMSGAMQ0069: Attribute (credential-reference) can not been undefined as the resource does not define any alternative to this attribute."},
> "rolled-back" => true
> }
> {code}
> The same problem, when user adds a bridge with a password and later wants to undefine it to add a credential-reference
> {code}
> /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:add(discovery-group=mane,queue-name=DLQ,forwarding-address=DLQ,password=senha1)
> /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:undefine-attribute(name=password)
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "WFLYMSGAMQ0069: Attribute (password) can not been undefined as the resource does not define any alternative to this attribute."},
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (WFLY-8238) Unable to undefine credential-reference
by Claudio Miranda (JIRA)
Claudio Miranda created WFLY-8238:
-------------------------------------
Summary: Unable to undefine credential-reference
Key: WFLY-8238
URL: https://issues.jboss.org/browse/WFLY-8238
Project: WildFly
Issue Type: Bug
Components: JMS, Security
Reporter: Claudio Miranda
Assignee: Jeff Mesnil
A bridge is added and a credential-reference is set.
However a "password" attribute cannot be set as the alternatives constraint validates the data, but the password attribute has a default value.
Also neither credential-reference and password are required=true, so they may be undefined.
{code}
/profile=full/subsystem=messaging-activemq/server=default/bridge=test1:add(discovery-group=mane,queue-name=DLQ,forwarding-address=DLQ)
/profile=full/subsystem=messaging-activemq/server=default/bridge=test1:write-attribute(name=credential-reference,value={clear-text=senha1})
/profile=full/subsystem=messaging-activemq/server=default/bridge=test1:undefine-attribute(name=credential-reference)
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description" => "WFLYMSGAMQ0069: Attribute (credential-reference) can not been undefined as the resource does not define any alternative to this attribute."},
"rolled-back" => true
}
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (WFCORE-2328) CLI connect command should accept a --bind parameter
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-2328:
----------------------------------------
Summary: CLI connect command should accept a --bind parameter
Key: WFCORE-2328
URL: https://issues.jboss.org/browse/WFCORE-2328
Project: WildFly Core
Issue Type: Enhancement
Components: CLI
Reporter: Brian Stansberry
Priority: Minor
When you launch the CLI you can pass a --bind=xxx param which then controls the client side bind address used for connections. But you can't specify this with the connect command itself.
This is minor; I just noticed it while experimenting with the fix for WFCORE-2225 when I wanted to confirm the fix was working by using the CLI.
Also, I noticed that if I did a "connect --bind=192.168.1.10" the CLI accepted the invalide command.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (DROOLS-1451) NPE when building KieBase with OOPath in a declared window
by Marek Winkler (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1451?page=com.atlassian.jira.plugi... ]
Marek Winkler updated DROOLS-1451:
----------------------------------
Steps to Reproduce:
Please run the tests {{org.drools.testcoverage.functional.oopath.OOPathCepTest}} for declared windows (does not matter if time or length) from PR \[1].
\[1] https://github.com/droolsjbpm/drools/pull/1117
> NPE when building KieBase with OOPath in a declared window
> ----------------------------------------------------------
>
> Key: DROOLS-1451
> URL: https://issues.jboss.org/browse/DROOLS-1451
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.0.0.Beta6
> Environment: Reproducible with 7.0.0-SNAPSHOT.
> Reporter: Marek Winkler
> Assignee: Mario Fusco
> Attachments: oopath-cep-stacktrace.txt
>
>
> When using an OOPath expression in a declared window (does not matter if a length or a time window), a NPE is thrown. For instance, a rule such as:
> {code}
> declare window Pings
> MessageEvent( /msg{ message == 'Ping' } ) over window:length( 2 )
> end
> rule R when
> $messageEvent: MessageEvent() from window Pings
> then
> events.add( $messageEvent );
> end
> {code}
> produces the following exception (see the attachment for the full stacktrace) when building the KieBase:
> {code}
> java.lang.NullPointerException
> at org.drools.core.reteoo.builder.WindowReferenceBuilder.build(WindowReferenceBuilder.java:40)
> at org.drools.core.reteoo.builder.PatternBuilder.attachPattern(PatternBuilder.java:116)
> at org.drools.core.reteoo.builder.PatternBuilder.build(PatternBuilder.java:77)
> at org.drools.core.reteoo.builder.GroupElementBuilder$AndBuilder.build(GroupElementBuilder.java:108)
> at org.drools.core.reteoo.builder.GroupElementBuilder.build(GroupElementBuilder.java:68)
> at org.drools.core.reteoo.builder.ReteooRuleBuilder.addSubRule(ReteooRuleBuilder.java:164)
> at org.drools.core.reteoo.builder.ReteooRuleBuilder.addRule(ReteooRuleBuilder.java:136)
> at org.drools.core.reteoo.ReteooBuilder.addRule(ReteooBuilder.java:110)
> ...
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:630)
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (DROOLS-1451) NPE when building KieBase with OOPath in a declared window
by Marek Winkler (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1451?page=com.atlassian.jira.plugi... ]
Marek Winkler updated DROOLS-1451:
----------------------------------
Attachment: oopath-cep-stacktrace.txt
> NPE when building KieBase with OOPath in a declared window
> ----------------------------------------------------------
>
> Key: DROOLS-1451
> URL: https://issues.jboss.org/browse/DROOLS-1451
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.0.0.Beta6
> Environment: Reproducible with 7.0.0-SNAPSHOT.
> Reporter: Marek Winkler
> Assignee: Mario Fusco
> Attachments: oopath-cep-stacktrace.txt
>
>
> When using an OOPath expression in a declared window (does not matter if a length or a time window), a NPE is thrown. For instance, a rule such as:
> {code}
> declare window Pings
> MessageEvent( /msg{ message == 'Ping' } ) over window:length( 2 )
> end
> rule R when
> $messageEvent: MessageEvent() from window Pings
> then
> events.add( $messageEvent );
> end
> {code}
> produces the following exception (see the attachment for the full stacktrace) when building the KieBase:
> {code}
> java.lang.NullPointerException
> at org.drools.core.reteoo.builder.WindowReferenceBuilder.build(WindowReferenceBuilder.java:40)
> at org.drools.core.reteoo.builder.PatternBuilder.attachPattern(PatternBuilder.java:116)
> at org.drools.core.reteoo.builder.PatternBuilder.build(PatternBuilder.java:77)
> at org.drools.core.reteoo.builder.GroupElementBuilder$AndBuilder.build(GroupElementBuilder.java:108)
> at org.drools.core.reteoo.builder.GroupElementBuilder.build(GroupElementBuilder.java:68)
> at org.drools.core.reteoo.builder.ReteooRuleBuilder.addSubRule(ReteooRuleBuilder.java:164)
> at org.drools.core.reteoo.builder.ReteooRuleBuilder.addRule(ReteooRuleBuilder.java:136)
> at org.drools.core.reteoo.ReteooBuilder.addRule(ReteooBuilder.java:110)
> ...
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:630)
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (DROOLS-1451) NPE when building KieBase with OOPath in a declared window
by Marek Winkler (JIRA)
Marek Winkler created DROOLS-1451:
-------------------------------------
Summary: NPE when building KieBase with OOPath in a declared window
Key: DROOLS-1451
URL: https://issues.jboss.org/browse/DROOLS-1451
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.0.0.Beta6
Environment: Reproducible with 7.0.0-SNAPSHOT.
Reporter: Marek Winkler
Assignee: Mario Fusco
When using an OOPath expression in a declared window (does not matter if a length or a time window), a NPE is thrown. For instance, a rule such as:
{code}
declare window Pings
MessageEvent( /msg{ message == 'Ping' } ) over window:length( 2 )
end
rule R when
$messageEvent: MessageEvent() from window Pings
then
events.add( $messageEvent );
end
{code}
produces the following exception (see the attachment for the full stacktrace) when building the KieBase:
{code}
java.lang.NullPointerException
at org.drools.core.reteoo.builder.WindowReferenceBuilder.build(WindowReferenceBuilder.java:40)
at org.drools.core.reteoo.builder.PatternBuilder.attachPattern(PatternBuilder.java:116)
at org.drools.core.reteoo.builder.PatternBuilder.build(PatternBuilder.java:77)
at org.drools.core.reteoo.builder.GroupElementBuilder$AndBuilder.build(GroupElementBuilder.java:108)
at org.drools.core.reteoo.builder.GroupElementBuilder.build(GroupElementBuilder.java:68)
at org.drools.core.reteoo.builder.ReteooRuleBuilder.addSubRule(ReteooRuleBuilder.java:164)
at org.drools.core.reteoo.builder.ReteooRuleBuilder.addRule(ReteooRuleBuilder.java:136)
at org.drools.core.reteoo.ReteooBuilder.addRule(ReteooBuilder.java:110)
...
at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:630)
...
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months