[JBoss JIRA] (DROOLS-3960) Executable Model - kie-maven-plugin fails to generate model with a mix of Java and DRL facts
by Dmitri Tsveitel (Jira)
Dmitri Tsveitel created DROOLS-3960:
---------------------------------------
Summary: Executable Model - kie-maven-plugin fails to generate model with a mix of Java and DRL facts
Key: DROOLS-3960
URL: https://issues.jboss.org/browse/DROOLS-3960
Project: Drools
Issue Type: Bug
Components: executable model
Affects Versions: 7.20.0.Final
Reporter: Dmitri Tsveitel
Assignee: Luca Molteni
Attachments: example.zip
Trying to generate a fully compiled kmodule with kie-maven-plugin. It works when all facts are defined in DRL, but fails when some facts are defined as Java POJOs. It appears to not find Java classes when compiling DRL.
Sample project is attached.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years
[JBoss JIRA] (JGRP-2343) Change in IPv4 versus IPv6 picking algorithm
by Bela Ban (Jira)
Bela Ban created JGRP-2343:
------------------------------
Summary: Change in IPv4 versus IPv6 picking algorithm
Key: JGRP-2343
URL: https://issues.jboss.org/browse/JGRP-2343
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 4.1.1
When https://issues.jboss.org/browse/JGRP-2305 was implemented, IPv4 was favored unless {{java.net.preferIPv6Addresses}} was set.
However, this makes the following case fail: no {{java.net.preferXXX}} option is set and the configuration contains one or more IPv6 addresses, e.g. {{UDP bind_addr="::1"}}.
This will fail, as the new algorithm sets the stack type as IPv4 (it works when {{java.net.preferIPv6Addresses}} is set).
Change:
* Look at all IP addresses in a configuration
* If all addresses are IPv6 and the stack type is IPv4 (and IPv6 is available) -> switch to IPv6 as stack type
* If all addresses are IPv4 and the stack type is IPv6 (and IPv4 is available) -> switch to IPv4 stack type
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years
[JBoss JIRA] (DROOLS-3959) [DMN Designer] Collapsed data type entry is unexpectedly expanded
by Jozef Marko (Jira)
Jozef Marko created DROOLS-3959:
-----------------------------------
Summary: [DMN Designer] Collapsed data type entry is unexpectedly expanded
Key: DROOLS-3959
URL: https://issues.jboss.org/browse/DROOLS-3959
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.21.0.Final
Reporter: Jozef Marko
Assignee: Michael Anstis
Attachments: collapse-expand.webm
The collapsed data type entry is unexpectedly expanded if user insert a new field below it. For more details, see the attached video [^collapse-expand.webm].
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years
[JBoss JIRA] (WFCORE-4398) WorkerResourceDefinition.WorkerWriteAttributeHandler implementations incorrectly handle undefined values
by Michal Petrov (Jira)
[ https://issues.jboss.org/browse/WFCORE-4398?page=com.atlassian.jira.plugi... ]
Michal Petrov reassigned WFCORE-4398:
-------------------------------------
Assignee: Michal Petrov (was: Flavia Rainone)
> WorkerResourceDefinition.WorkerWriteAttributeHandler implementations incorrectly handle undefined values
> --------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4398
> URL: https://issues.jboss.org/browse/WFCORE-4398
> Project: WildFly Core
> Issue Type: Bug
> Components: IO
> Affects Versions: 6.0.2.Final, 7.0.0.Final, 8.0.0.Final, 9.0.0.Beta1
> Reporter: Brian Stansberry
> Assignee: Michal Petrov
> Priority: Major
>
> The WorkerResourceDefinition.WorkerWriteAttributeHandler implementations are not checking for undefined values before attempting type conversions:
> {code}
> 10:12:28,243 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("undefine-attribute") failed - address: ([
> ("subsystem" => "io"),
> ("worker" => "default")
> ]): java.lang.IllegalArgumentException
> at org.jboss.dmr.ModelValue.asInt(ModelValue.java:61)
> at org.jboss.dmr.ModelNode.asInt(ModelNode.java:288)
> at org.wildfly.extension.io.WorkerResourceDefinition$5.setValue(WorkerResourceDefinition.java:201)
> at org.wildfly.extension.io.WorkerResourceDefinition$WorkerWriteAttributeHandler.applyUpdateToRuntime(WorkerResourceDefinition.java:262)
> at org.jboss.as.controller.AbstractWriteAttributeHandler$1.execute(AbstractWriteAttributeHandler.java:104)
> {code}
> That stack trace maps to WildFly 14 / WildFly Core 6 code.
> It should be fine for the attributes that have default values, as there the default value would be passed in instead of undefined. But for the others some sort of handling is needed.
> I believe that special handling should be to pass in the default value used in the XNIO code.
> _*Any change to add any default value to the IO subsystem management API should be done via a separate JIRA. Do not mix this bug fix with an API change.*_
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years