[JBoss JIRA] (WFLY-13006) KUBE_PING Occasional NPE on shutdown
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-13006?page=com.atlassian.jira.plugi... ]
Radoslav Husar commented on WFLY-13006:
---------------------------------------
Still not released.
> KUBE_PING Occasional NPE on shutdown
> -------------------------------------
>
> Key: WFLY-13006
> URL: https://issues.redhat.com/browse/WFLY-13006
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
>
> 05:52:55,313 ERROR [org.jgroups.util.TimeScheduler3] (thread-6,null,xa-load-2) JGRP000169: failed executing task MERGE3: InfoSender: java.lang.NullPointerException
> at org.jgroups.protocols.kubernetes.KUBE_PING.readAll(KUBE_PING.java:313)
> at org.jgroups.protocols.kubernetes.KUBE_PING.findMembers(KUBE_PING.java:206)
> at org.jgroups.protocols.Discovery.invokeFindMembers(Discovery.java:216)
> at org.jgroups.protocols.Discovery.findMembers(Discovery.java:241)
> at org.jgroups.protocols.Discovery.down(Discovery.java:384)
> at org.jgroups.protocols.MERGE3$InfoSender.run(MERGE3.java:413)
> at org.jgroups.util.TimeScheduler3$Task.run(TimeScheduler3.java:328)
> at org.jgroups.util.TimeScheduler3$RecurringTask.run(TimeScheduler3.java:362)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at org.jboss.as.clustering.jgroups.ClassLoaderThreadFactory.lambda$newThread$0(ClassLoaderThreadFactory.java:52)
> at java.lang.Thread.run(Thread.java:748)
> https://github.com/jgroups-extras/jgroups-kubernetes/issues/39
> https://github.com/jgroups-extras/jgroups-kubernetes/pull/88
> Will be resolved with a next jgroups-kubernetes upgrade.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-4607) DMN DT Analysis for symbols
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-4607?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-4607:
-----------------------------------
Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2020 Week 10-12 (from Mar 2) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2020 Week 07-09 (from Feb 10))
> DMN DT Analysis for symbols
> ---------------------------
>
> Key: DROOLS-4607
> URL: https://issues.redhat.com/browse/DROOLS-4607
> Project: Drools
> Issue Type: Feature Request
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Major
>
> Extend analysis to symbolic processing in the possible cases
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-9641) Cluster EJB can not work with "-b 0.0.0.0"
by Aliaksei Makarevich (Jira)
[ https://issues.redhat.com/browse/WFLY-9641?page=com.atlassian.jira.plugin... ]
Aliaksei Makarevich edited comment on WFLY-9641 at 2/28/20 3:37 AM:
--------------------------------------------------------------------
[~gregoryhall994]
Some information about configuration found here https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... - the same solving is in forum thread (client-mapping)
We have keycloak7.0.0-docker-cluster. We changed some cli files and mount them into containers.
As for this case we change tools\cli\proxy.cli -- add line:
/socket-binding-group=standard-sockets/socket-binding=http:write-attribute(name=client-mappings, value=[{destination-address=${jboss.host.name}}])
And without this, for exaple Keycloak 9.0.0 prints in log :
WARN [org.jboss.as.ejb3.remote] (ClusterTopologyRegistrar - 1) WFLYEJB0509: Clustered EJBs in Node: bfc3539d1c33 are bound to INADDR_ANY(0.0.0.0). Either use a non-wildcard server bind address or add client-mapping entries to the relevant socket-binding for the Remoting connector
was (Author: axelmak):
[~gregoryhall994]
Some information about configuration found here https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... - the same solving is in forum thread (client-mapping)
We have keycloak7.0.0-docker-cluster. We changed some cli files and mount them into containers.
As for this case we change tools\cli\proxy.cli -- add line:
/socket-binding-group=standard-sockets/socket-binding=http:write-attribute(name=client-mappings, value=[{destination-address=${jboss.host.name}}])
> Cluster EJB can not work with "-b 0.0.0.0"
> ------------------------------------------
>
> Key: WFLY-9641
> URL: https://issues.redhat.com/browse/WFLY-9641
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 11.0.0.Final
> Reporter: Fred Ling
> Priority: Major
> Labels: cluster, ejb, wildfly
>
> The ejb cluster does not work when bind to 0.0.0.0, using --server-config=standalone-full-ha.xml -b 0.0.0.0.
> The ejb client fails to connect to the cluster nodes because it tries to connect to 0.0.0.0.
> For more information please refer to the forum thread.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13162) ConcurrentModificationException in WildFlyJobXmlResolver
by Ralf Battenfeld (Jira)
[ https://issues.redhat.com/browse/WFLY-13162?page=com.atlassian.jira.plugi... ]
Ralf Battenfeld commented on WFLY-13162:
----------------------------------------
Good morning, I can conform this issue. We are using wildfly 17, and run on RHEL7 with open jdk. We execute a cli script that updates the configuration on runtime. This causes redeployments.
> ConcurrentModificationException in WildFlyJobXmlResolver
> --------------------------------------------------------
>
> Key: WFLY-13162
> URL: https://issues.redhat.com/browse/WFLY-13162
> Project: WildFly
> Issue Type: Bug
> Components: Batch
> Affects Versions: 18.0.1.Final, 19.0.0.Beta3, 20.0.0.Beta1
> Reporter: Hielke Hoeve
> Assignee: Cheng Fang
> Priority: Major
>
> Because of a thread unsafe construction in WildFlyJobXmlResolver I am experiencing ConcurrentModificationExceptions while starting my EAR every so often. This is because every EJB of the EAR is processed by WildFlyJobXmlResolver in paralel threads. Even if it has no jbatch dependency or dependency to a EJB which does.
> This is not reproducable for every startup as it depends on the performance of the host machine, number of ejbs in ear, number of threads and thread timing.
> I have created an example project representing our project setup with which I am able to reproduce the issue using a default wildfly build. This test project contains 1 EJB with jbatch, a number of plain EJBs, a WAR which uses the jbatch EJB and an EAR.
> See below for the exception stacktrace.
> I have made a small fix for this issue @ https://github.com/hielkehoeve/wildfly/commit/82047233621c3e5bdbd45333ca4.... The example test project can also be found there.
> {code:java}
> 08:32:30,164 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."project.ear"."project-d.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."project.ear"."project-d.jar".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of subdeployment "project-d.jar" of deployment "project.ear"
> at org.jboss.as.server@10.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.util.ConcurrentModificationException
> at java.base/java.util.LinkedHashMap$LinkedHashIterator.nextNode(LinkedHashMap.java:719)
> at java.base/java.util.LinkedHashMap$LinkedKeyIterator.next(LinkedHashMap.java:741)
> at java.base/java.util.AbstractCollection.addAll(AbstractCollection.java:351)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.merge(WildFlyJobXmlResolver.java:261)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.forDeployment(WildFlyJobXmlResolver.java:127)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.forDeployment(WildFlyJobXmlResolver.java:130)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.forDeployment(WildFlyJobXmlResolver.java:130)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.forDeployment(WildFlyJobXmlResolver.java:130)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.forDeployment(WildFlyJobXmlResolver.java:130)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.BatchEnvironmentProcessor.deploy(BatchEnvironmentProcessor.java:78)
> at org.jboss.as.server@10.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
> ... 8 more
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-9641) Cluster EJB can not work with "-b 0.0.0.0"
by Aliaksei Makarevich (Jira)
[ https://issues.redhat.com/browse/WFLY-9641?page=com.atlassian.jira.plugin... ]
Aliaksei Makarevich commented on WFLY-9641:
-------------------------------------------
[~gregoryhall994]
Some information about configuration found here https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... - the same solving is in forum thread (client-mapping)
We have keycloak7.0.0-docker-cluster. We changed some cli files and mount them into containers.
As for this case we change tools\cli\proxy.cli -- add line:
/socket-binding-group=standard-sockets/socket-binding=http:write-attribute(name=client-mappings, value=[{destination-address=${jboss.host.name}}])
> Cluster EJB can not work with "-b 0.0.0.0"
> ------------------------------------------
>
> Key: WFLY-9641
> URL: https://issues.redhat.com/browse/WFLY-9641
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 11.0.0.Final
> Reporter: Fred Ling
> Priority: Major
> Labels: cluster, ejb, wildfly
>
> The ejb cluster does not work when bind to 0.0.0.0, using --server-config=standalone-full-ha.xml -b 0.0.0.0.
> The ejb client fails to connect to the cluster nodes because it tries to connect to 0.0.0.0.
> For more information please refer to the forum thread.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13162) ConcurrentModificationException in WildFlyJobXmlResolver
by Hielke Hoeve (Jira)
[ https://issues.redhat.com/browse/WFLY-13162?page=com.atlassian.jira.plugi... ]
Hielke Hoeve commented on WFLY-13162:
-------------------------------------
Also tried with Java "1.8.0_181" but still getting the error after a 2 redeploys.
> ConcurrentModificationException in WildFlyJobXmlResolver
> --------------------------------------------------------
>
> Key: WFLY-13162
> URL: https://issues.redhat.com/browse/WFLY-13162
> Project: WildFly
> Issue Type: Bug
> Components: Batch
> Affects Versions: 18.0.1.Final, 19.0.0.Beta3, 20.0.0.Beta1
> Reporter: Hielke Hoeve
> Assignee: Cheng Fang
> Priority: Major
>
> Because of a thread unsafe construction in WildFlyJobXmlResolver I am experiencing ConcurrentModificationExceptions while starting my EAR every so often. This is because every EJB of the EAR is processed by WildFlyJobXmlResolver in paralel threads. Even if it has no jbatch dependency or dependency to a EJB which does.
> This is not reproducable for every startup as it depends on the performance of the host machine, number of ejbs in ear, number of threads and thread timing.
> I have created an example project representing our project setup with which I am able to reproduce the issue using a default wildfly build. This test project contains 1 EJB with jbatch, a number of plain EJBs, a WAR which uses the jbatch EJB and an EAR.
> See below for the exception stacktrace.
> I have made a small fix for this issue @ https://github.com/hielkehoeve/wildfly/commit/82047233621c3e5bdbd45333ca4.... The example test project can also be found there.
> {code:java}
> 08:32:30,164 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."project.ear"."project-d.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."project.ear"."project-d.jar".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of subdeployment "project-d.jar" of deployment "project.ear"
> at org.jboss.as.server@10.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.util.ConcurrentModificationException
> at java.base/java.util.LinkedHashMap$LinkedHashIterator.nextNode(LinkedHashMap.java:719)
> at java.base/java.util.LinkedHashMap$LinkedKeyIterator.next(LinkedHashMap.java:741)
> at java.base/java.util.AbstractCollection.addAll(AbstractCollection.java:351)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.merge(WildFlyJobXmlResolver.java:261)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.forDeployment(WildFlyJobXmlResolver.java:127)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.forDeployment(WildFlyJobXmlResolver.java:130)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.forDeployment(WildFlyJobXmlResolver.java:130)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.forDeployment(WildFlyJobXmlResolver.java:130)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.forDeployment(WildFlyJobXmlResolver.java:130)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.BatchEnvironmentProcessor.deploy(BatchEnvironmentProcessor.java:78)
> at org.jboss.as.server@10.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
> ... 8 more
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months