[JBoss JIRA] (JGRP-2236) UNICAST max_xmit_req_size doesn't work
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2236?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2236:
--------------------------------
Fixed on master and 3.6. Do you guys want to create a one-off? The commits are 416f3c739c2ce577f3961900030c8c6aa65cab07 on master and c198b3ab4449dc12a6eef588e4b60832d82265d0 on 3.6.
> UNICAST max_xmit_req_size doesn't work
> --------------------------------------
>
> Key: JGRP-2236
> URL: https://issues.jboss.org/browse/JGRP-2236
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.1
> Reporter: Dennis Reed
> Assignee: Bela Ban
> Fix For: 3.6.15, 4.0.9
>
>
> UNICAST3 sets max_xmit_req_size to avoid requesting too many messages to fit into the maximum message size.
> But the check is implemented incorrectly, so it is not effective.
> JGRP000029: node1: failed sending message to node2 (120314 bytes): java.io.IOException: Message too long, headers: UNICAST3: XMIT_REQ, seqno=0, TP: [cluster_name=cluster]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JGRP-2236) UNICAST max_xmit_req_size doesn't work
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2236?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2236:
---------------------------
Fix Version/s: 3.6.15
> UNICAST max_xmit_req_size doesn't work
> --------------------------------------
>
> Key: JGRP-2236
> URL: https://issues.jboss.org/browse/JGRP-2236
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.1
> Reporter: Dennis Reed
> Assignee: Bela Ban
> Fix For: 3.6.15, 4.0.9
>
>
> UNICAST3 sets max_xmit_req_size to avoid requesting too many messages to fit into the maximum message size.
> But the check is implemented incorrectly, so it is not effective.
> JGRP000029: node1: failed sending message to node2 (120314 bytes): java.io.IOException: Message too long, headers: UNICAST3: XMIT_REQ, seqno=0, TP: [cluster_name=cluster]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFCORE-3434) ERROR in logs while using vault in system properties
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3434?page=com.atlassian.jira.plugi... ]
Chao Wang moved JBEAP-13854 to WFCORE-3434:
-------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-3434 (was: JBEAP-13854)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
> ERROR in logs while using vault in system properties
> ----------------------------------------------------
>
> Key: WFCORE-3434
> URL: https://issues.jboss.org/browse/WFCORE-3434
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 4.0.0.Alpha3
> Environment: JBoss EAP 7.1 Beta
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Minor
>
> Getting below ERROR message in server.log when *Picketbox Vault expressions* used in *system properties*.:
> {code:java}
> ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0230: Vault is not initialized; resolution of vault expressions is not possible
> {code}
> Below expressions are resolving fine but due to race condition this ERROR message got printed in the logs.
> {code:java}
> <system-properties>
> <property name="javax.net.ssl.trustStore" value="/home/jboss-eap-7.1/vault/vault.keystore"/>
> <property name="javax.net.ssl.trustStorePassword" value="${VAULT::datasource::password::1}"/>
> </system-properties>
> <vault>
> <vault-option name="KEYSTORE_URL" value="/home/jboss-eap-7.1/vault/vault.keystore"/>
> <vault-option name="KEYSTORE_PASSWORD" value="MASK-2GAtdnlXL8H"/>
> <vault-option name="KEYSTORE_ALIAS" value="vault"/>
> <vault-option name="SALT" value="12345678"/>
> <vault-option name="ITERATION_COUNT" value="44"/>
> <vault-option name="ENC_FILE_DIR" value="/home/jboss-eap-7.1/vault/"/>
> </vault>
> {code}
> Expression is actually resolving to the correct value and that can be check using below CLI command :
> {code:java}
> /core-service=platform-mbean/type=runtime:read-attribute(name=system-properties).
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFCORE-3434) ERROR in logs while using vault in system properties
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3434?page=com.atlassian.jira.plugi... ]
Chao Wang updated WFCORE-3434:
------------------------------
Affects Version/s: 4.0.0.Alpha3
> ERROR in logs while using vault in system properties
> ----------------------------------------------------
>
> Key: WFCORE-3434
> URL: https://issues.jboss.org/browse/WFCORE-3434
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 4.0.0.Alpha3
> Environment: JBoss EAP 7.1 Beta
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Minor
>
> Getting below ERROR message in server.log when *Picketbox Vault expressions* used in *system properties*.:
> {code:java}
> ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0230: Vault is not initialized; resolution of vault expressions is not possible
> {code}
> Below expressions are resolving fine but due to race condition this ERROR message got printed in the logs.
> {code:java}
> <system-properties>
> <property name="javax.net.ssl.trustStore" value="/home/jboss-eap-7.1/vault/vault.keystore"/>
> <property name="javax.net.ssl.trustStorePassword" value="${VAULT::datasource::password::1}"/>
> </system-properties>
> <vault>
> <vault-option name="KEYSTORE_URL" value="/home/jboss-eap-7.1/vault/vault.keystore"/>
> <vault-option name="KEYSTORE_PASSWORD" value="MASK-2GAtdnlXL8H"/>
> <vault-option name="KEYSTORE_ALIAS" value="vault"/>
> <vault-option name="SALT" value="12345678"/>
> <vault-option name="ITERATION_COUNT" value="44"/>
> <vault-option name="ENC_FILE_DIR" value="/home/jboss-eap-7.1/vault/"/>
> </vault>
> {code}
> Expression is actually resolving to the correct value and that can be check using below CLI command :
> {code:java}
> /core-service=platform-mbean/type=runtime:read-attribute(name=system-properties).
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFCORE-3434) ERROR in logs while using vault in system properties
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3434?page=com.atlassian.jira.plugi... ]
Chao Wang updated WFCORE-3434:
------------------------------
Component/s: Domain Management
> ERROR in logs while using vault in system properties
> ----------------------------------------------------
>
> Key: WFCORE-3434
> URL: https://issues.jboss.org/browse/WFCORE-3434
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 4.0.0.Alpha3
> Environment: JBoss EAP 7.1 Beta
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Minor
>
> Getting below ERROR message in server.log when *Picketbox Vault expressions* used in *system properties*.:
> {code:java}
> ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0230: Vault is not initialized; resolution of vault expressions is not possible
> {code}
> Below expressions are resolving fine but due to race condition this ERROR message got printed in the logs.
> {code:java}
> <system-properties>
> <property name="javax.net.ssl.trustStore" value="/home/jboss-eap-7.1/vault/vault.keystore"/>
> <property name="javax.net.ssl.trustStorePassword" value="${VAULT::datasource::password::1}"/>
> </system-properties>
> <vault>
> <vault-option name="KEYSTORE_URL" value="/home/jboss-eap-7.1/vault/vault.keystore"/>
> <vault-option name="KEYSTORE_PASSWORD" value="MASK-2GAtdnlXL8H"/>
> <vault-option name="KEYSTORE_ALIAS" value="vault"/>
> <vault-option name="SALT" value="12345678"/>
> <vault-option name="ITERATION_COUNT" value="44"/>
> <vault-option name="ENC_FILE_DIR" value="/home/jboss-eap-7.1/vault/"/>
> </vault>
> {code}
> Expression is actually resolving to the correct value and that can be check using below CLI command :
> {code:java}
> /core-service=platform-mbean/type=runtime:read-attribute(name=system-properties).
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (DROOLS-1763) Dependent rule not firing
by David Wade (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1763?page=com.atlassian.jira.plugi... ]
David Wade edited comment on DROOLS-1763 at 11/28/17 12:17 AM:
---------------------------------------------------------------
Ahh,
{code}
KnowledgeBuilderConfiguration kbc= KnowledgeBuilderFactory.newKnowledgeBuilderConfiguration();
kbc.setOption(PropertySpecificOption.ALLOWED);
KnowledgeBuilder knowledgeBuilder = KnowledgeBuilderFactory.newKnowledgeBuilder(kbc);
knowledgeBuilder.add(ResourceFactory.newByteArrayResource(taxRule.getRuleXml().getBytes()), ResourceType.DRL);
Collection<KiePackage> knowledgePackages = knowledgeBuilder.getKnowledgePackages();
KieBaseConfiguration kieBaseConfiguration = KnowledgeBaseFactory.newKnowledgeBaseConfiguration();
kieBaseConfiguration.setOption(ConstraintJittingThresholdOption.get(40));
knowledgeBase = KnowledgeBaseFactory.newKnowledgeBase(kieBaseConfiguration);
knowledgeBase.addPackages(knowledgePackages)
{code}
was (Author: david.wade):
Ahh,
{{
KieServices ks = KieServices.Factory.get();
Properties properties = new Properties();
properties.setProperty("drools.propertySpecific", "ALLOWED");
properties.setProperty("drools.jittingThreshold", "40");
ks.newKieBaseConfiguration(properties);
}}
But I can't see where I can pass that configuration back in.
> Dependent rule not firing
> -------------------------
>
> Key: DROOLS-1763
> URL: https://issues.jboss.org/browse/DROOLS-1763
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.0.0.Beta7, 7.3.0.Final
> Environment: Linux all versions.
> JDK 1.8.0 Update 144
> Reporter: David Wade
> Assignee: Mario Fusco
> Attachments: 7.0.0.Beta6.txt, 7.3.0.Final.txt
>
>
> We have been using Drools since 2.x.
> Currently we use 7.0.0.Beta6 which works.
> We can't upgrade because since 7.0.0.Beta7 rules dependent on the consequence of another rule are not firing for some reason. This happens for us on 7.0.0.Beta7 through to 7.3.0.Final.
> Consider the following two rules. When run on 7.0.0.Beta6 both rules fire. From Beta7 through to 7.3.0.Final, only the SQ rule fire, despite the RC rule passing its conditions
> {code}
> rule "H2"
> salience -300
> when
> segment:SegmentWithTax(
> containsTax("SQ")
> , notContainsTax("H2", "RC")
> )
> then
> segment.addPercentageTaxEntry(taxCodeMap,"SQ","RC_13_PERCENT");
> end
> rule "SQ"
> when
> segment:SegmentWithTax(
> !containsTax("SQ")
> )
> then
> modify(segment) {
> addTaxEntry(taxCodeMap,"SQ_TRANSFER_TRANSIT_LESS_THAN_FOUR_HOURS")
> }
> end
> {code}
> Will attach Drools trace logging output * 2. One for [^7.0.0.Beta6.txt] , one for [^7.3.0.Final.txt] .
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFCORE-3432) Correct ManagementResourceRegistration runtime-only metadata
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3432?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-3432:
------------------------------------------
It looks like 3) is problematic, as currently /deployment=foo.war:read-resource(recursive=true, include-runtime=false) is returning the subsystem children, even though it shouldn't. :( So fixing the MRR may break users who are counting on the bug, including Arquillian -- see WFARQ-35.
> Correct ManagementResourceRegistration runtime-only metadata
> ------------------------------------------------------------
>
> Key: WFCORE-3432
> URL: https://issues.jboss.org/browse/WFCORE-3432
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
>
> We have MRRs, e.g. ServerEnvironmentResourceDescription, where the resources are runtime-only but the MRR.isRuntimeOnly() is not stating that.
> 3 possible aspects to this:
> 1) Audit uses of Resource.Factory.create(true[,...]) and check that those are also setting up the ResourceDefinition correctly so the MRR reports runtime-only.
> 2) Change the ConcreteResourceRegistration stuff such that it ignores the ResourceDefinition if the parent is runtime-only. IOW, runtime-only parents can't have non-runtime-only children. This would wipe out a category of possilbe errors in the setup of the children.
> 3) Have ExtensionRegistry/SubsystemRegistrationImpl ensure that the registrations for deployment resource children are runtime-only.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (DROOLS-1763) Dependent rule not firing
by David Wade (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1763?page=com.atlassian.jira.plugi... ]
David Wade edited comment on DROOLS-1763 at 11/27/17 9:27 PM:
--------------------------------------------------------------
Ahh,
{{
KieServices ks = KieServices.Factory.get();
Properties properties = new Properties();
properties.setProperty("drools.propertySpecific", "ALLOWED");
properties.setProperty("drools.jittingThreshold", "40");
ks.newKieBaseConfiguration(properties);
}}
But I can't see where I can pass that configuration back in.
was (Author: david.wade):
Ahh,
{{
KieServices ks = KieServices.Factory.get();
Properties properties = new Properties();
properties.setProperty("drools.propertySpecific", "ALLOWED");
properties.setProperty("drools.jittingThreshold", "40");
ks.newKieBaseConfiguration(properties);
}}
> Dependent rule not firing
> -------------------------
>
> Key: DROOLS-1763
> URL: https://issues.jboss.org/browse/DROOLS-1763
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.0.0.Beta7, 7.3.0.Final
> Environment: Linux all versions.
> JDK 1.8.0 Update 144
> Reporter: David Wade
> Assignee: Mario Fusco
> Attachments: 7.0.0.Beta6.txt, 7.3.0.Final.txt
>
>
> We have been using Drools since 2.x.
> Currently we use 7.0.0.Beta6 which works.
> We can't upgrade because since 7.0.0.Beta7 rules dependent on the consequence of another rule are not firing for some reason. This happens for us on 7.0.0.Beta7 through to 7.3.0.Final.
> Consider the following two rules. When run on 7.0.0.Beta6 both rules fire. From Beta7 through to 7.3.0.Final, only the SQ rule fire, despite the RC rule passing its conditions
> {code}
> rule "H2"
> salience -300
> when
> segment:SegmentWithTax(
> containsTax("SQ")
> , notContainsTax("H2", "RC")
> )
> then
> segment.addPercentageTaxEntry(taxCodeMap,"SQ","RC_13_PERCENT");
> end
> rule "SQ"
> when
> segment:SegmentWithTax(
> !containsTax("SQ")
> )
> then
> modify(segment) {
> addTaxEntry(taxCodeMap,"SQ_TRANSFER_TRANSIT_LESS_THAN_FOUR_HOURS")
> }
> end
> {code}
> Will attach Drools trace logging output * 2. One for [^7.0.0.Beta6.txt] , one for [^7.3.0.Final.txt] .
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (DROOLS-1763) Dependent rule not firing
by David Wade (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1763?page=com.atlassian.jira.plugi... ]
David Wade commented on DROOLS-1763:
------------------------------------
Ahh,
{{
KieServices ks = KieServices.Factory.get();
Properties properties = new Properties();
properties.setProperty("drools.propertySpecific", "ALLOWED");
properties.setProperty("drools.jittingThreshold", "40");
ks.newKieBaseConfiguration(properties);
}}
> Dependent rule not firing
> -------------------------
>
> Key: DROOLS-1763
> URL: https://issues.jboss.org/browse/DROOLS-1763
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.0.0.Beta7, 7.3.0.Final
> Environment: Linux all versions.
> JDK 1.8.0 Update 144
> Reporter: David Wade
> Assignee: Mario Fusco
> Attachments: 7.0.0.Beta6.txt, 7.3.0.Final.txt
>
>
> We have been using Drools since 2.x.
> Currently we use 7.0.0.Beta6 which works.
> We can't upgrade because since 7.0.0.Beta7 rules dependent on the consequence of another rule are not firing for some reason. This happens for us on 7.0.0.Beta7 through to 7.3.0.Final.
> Consider the following two rules. When run on 7.0.0.Beta6 both rules fire. From Beta7 through to 7.3.0.Final, only the SQ rule fire, despite the RC rule passing its conditions
> {code}
> rule "H2"
> salience -300
> when
> segment:SegmentWithTax(
> containsTax("SQ")
> , notContainsTax("H2", "RC")
> )
> then
> segment.addPercentageTaxEntry(taxCodeMap,"SQ","RC_13_PERCENT");
> end
> rule "SQ"
> when
> segment:SegmentWithTax(
> !containsTax("SQ")
> )
> then
> modify(segment) {
> addTaxEntry(taxCodeMap,"SQ_TRANSFER_TRANSIT_LESS_THAN_FOUR_HOURS")
> }
> end
> {code}
> Will attach Drools trace logging output * 2. One for [^7.0.0.Beta6.txt] , one for [^7.3.0.Final.txt] .
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (DROOLS-1763) Dependent rule not firing
by David Wade (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1763?page=com.atlassian.jira.plugi... ]
David Wade commented on DROOLS-1763:
------------------------------------
Hmm, how do I set that property when not configuring via kmodule.xml.
We set things up manually, because, well because we do...
So programatically, where should I be setting that property.... KieServices/KieFileSystem/KieBuilder/elsewhere.
> Dependent rule not firing
> -------------------------
>
> Key: DROOLS-1763
> URL: https://issues.jboss.org/browse/DROOLS-1763
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.0.0.Beta7, 7.3.0.Final
> Environment: Linux all versions.
> JDK 1.8.0 Update 144
> Reporter: David Wade
> Assignee: Mario Fusco
> Attachments: 7.0.0.Beta6.txt, 7.3.0.Final.txt
>
>
> We have been using Drools since 2.x.
> Currently we use 7.0.0.Beta6 which works.
> We can't upgrade because since 7.0.0.Beta7 rules dependent on the consequence of another rule are not firing for some reason. This happens for us on 7.0.0.Beta7 through to 7.3.0.Final.
> Consider the following two rules. When run on 7.0.0.Beta6 both rules fire. From Beta7 through to 7.3.0.Final, only the SQ rule fire, despite the RC rule passing its conditions
> {code}
> rule "H2"
> salience -300
> when
> segment:SegmentWithTax(
> containsTax("SQ")
> , notContainsTax("H2", "RC")
> )
> then
> segment.addPercentageTaxEntry(taxCodeMap,"SQ","RC_13_PERCENT");
> end
> rule "SQ"
> when
> segment:SegmentWithTax(
> !containsTax("SQ")
> )
> then
> modify(segment) {
> addTaxEntry(taxCodeMap,"SQ_TRANSFER_TRANSIT_LESS_THAN_FOUR_HOURS")
> }
> end
> {code}
> Will attach Drools trace logging output * 2. One for [^7.0.0.Beta6.txt] , one for [^7.3.0.Final.txt] .
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months