[JBoss JIRA] (WFLY-13038) Undertow null pointer exception after changing to random election policy
by Gagannoor Singh (Jira)
Gagannoor Singh created WFLY-13038:
--------------------------------------
Summary: Undertow null pointer exception after changing to random election policy
Key: WFLY-13038
URL: https://issues.redhat.com/browse/WFLY-13038
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 16.0.0.Final
Reporter: Gagannoor Singh
Assignee: Flavia Rainone
After changing the singleton subsystem to random election policy getting undertow null pointer exception in logs after clicking deployments->server groups-> "server group name" of HAL management console and it shows zero deployments.
We are having a clustered environment with 3 nodes.
Logs:
ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 30) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
("deployment" => "masterdata-ei-cvpartner-1.17-SNAPSHOT.war"),
("subsystem" => "undertow")
]): java.lang.NullPointerException
Singleton Setting in domain.xml :
<subsystem xmlns="urn:jboss:domain:singleton:1.0">
<singleton-policies default="default">
<singleton-policy name="default" cache-container="server">
<random-election-policy/>
</singleton-policy>
</singleton-policies>
</subsystem>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-12679) Upgrade HAL from 3.2.1 to 3.2.2
by Moulali Shikalwadi (Jira)
[ https://issues.redhat.com/browse/WFLY-12679?page=com.atlassian.jira.plugi... ]
Moulali Shikalwadi commented on WFLY-12679:
-------------------------------------------
Hi [~soul2zimate],
I tried to change the hal version from 3.2.1 to 3.2.2 but build is getting failed with below error.
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message:
org.wildfly:wildfly-galleon-pack:pom:18.0.2.Final-SNAPSHOT
org.jboss.hal:hal-console:jar:resources:3.2.2.Final:provided has transitive dependencies:
org.jetbrains:annotations:jar:16.0.1:provided
And also in the master branch I see 3.2.5.Final not 3.2.1.Final. Could you please suggest.
Thanks,
Moulali
> Upgrade HAL from 3.2.1 to 3.2.2
> -------------------------------
>
> Key: WFLY-12679
> URL: https://issues.redhat.com/browse/WFLY-12679
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Web Console
> Affects Versions: 18.0.0.Final
> Reporter: Chao Wang
> Assignee: Moulali Shikalwadi
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4956) Normarize rule constraints for property reactivity and indexing
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-4956?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi commented on DROOLS-4956:
-------------------------------------------
Executable Model has no problem with property reactivity in both cases ( "Toshiya" == name / $customer == name). However, Executable Model doesn't create index in those cases.
> Normarize rule constraints for property reactivity and indexing
> ---------------------------------------------------------------
>
> Key: DROOLS-4956
> URL: https://issues.redhat.com/browse/DROOLS-4956
> Project: Drools
> Issue Type: Bug
> Components: core engine, executable model
> Affects Versions: 7.31.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> Having a constraint like
> {code:java}
> Person(name == $customer)
> {code}
> is not really the same thing as
> {code:java}
> Person($customer == name)
> {code}
> In the second case not only you don't have property reactivity, but also you don't have indexing. This an inconsistent behaviour and hoping to fix it with a "normalization" phase where the second constraint got rewritten like the first before being analyzed by property reactivity and indexing.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-12681) Provide a 'microprofile' Galleon layer
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-12681?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFLY-12681:
----------------------------------
Summary: Provide a 'microprofile' Galleon layer (was: Create 'microprofile' layer spec)
> Provide a 'microprofile' Galleon layer
> --------------------------------------
>
> Key: WFLY-12681
> URL: https://issues.redhat.com/browse/WFLY-12681
> Project: WildFly
> Issue Type: Feature Request
> Components: Build System
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
> Labels: Microprofile
>
> We used to have a 'microprofile' layer spec aggregating all MP specs which at the moment only contained config, health and metrics which got renamed to 'observability' by WFLY-11774.
> With the introduction of new specs fault tolerance, openapi, etc. we should reintroduce the 'microprofile' layer spec which contains all of the MP specs.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months