[JBoss JIRA] (DROOLS-3548) Thread remains used by loadbalancer when connection to kie-server failed
by Hiroko Miura (Jira)
[ https://issues.jboss.org/browse/DROOLS-3548?page=com.atlassian.jira.plugi... ]
Hiroko Miura updated DROOLS-3548:
---------------------------------
Description:
When KieServicesClient fails to connect to KieServer, LoadBalancer is invoked to check availability of server like the following.
~~~
[2019/01/24 18:19:38.411] [pool-1-thread-1] [DEBUG] (LoadBalancer.java:149) - Starting to scan if any of the failed endpoints is back online
org.kie.server.common.rest.NoEndpointFoundException: No available endpoints found
at org.kie.server.client.balancer.impl.AbstractBalancerStrategy.checkEmpty(AbstractBalancerStrategy.java:27)
at org.kie.server.client.balancer.impl.RoundRobinBalancerStrategy.next(RoundRobinBalancerStrategy.java:37)
at org.kie.server.client.balancer.LoadBalancer.getUrl(LoadBalancer.java:52)
at org.kie.server.client.impl.AbstractKieServicesClientImpl.invoke(AbstractKieServicesClientImpl.java:809)
at org.kie.server.client.impl.AbstractKieServicesClientImpl.makeHttpGetRequestAndCreateServiceResponse(AbstractKieServicesClientImpl.java:177)
at org.kie.server.client.impl.KieServicesClientImpl.getServerInfo(KieServicesClientImpl.java:159)
at org.kie.server.client.impl.KieServicesClientImpl.getCapabilitiesFromServer(KieServicesClientImpl.java:132)
at org.kie.server.client.impl.KieServicesClientImpl.init(KieServicesClientImpl.java:87)
at org.kie.server.client.impl.KieServicesClientImpl.<init>(KieServicesClientImpl.java:74)
at org.kie.server.client.KieServicesFactory.newKieServicesClient(KieServicesFactory.java:101)
at com.sample.rules.test.KieServerRestClientTest.connectionFailureTest(KieServerRestClientTest.java:55)
~~~
But after that, the thread used by LoadBalancer remains until termination of client application as LoadBalancer.close() is not called.
was:
When KieServicesClient fails to connect to KieServer, LoadBalancer is invoked to check availability of server like the following.
[2019/01/24 18:19:38.411] [pool-1-thread-1] [DEBUG] (LoadBalancer.java:149) - Starting to scan if any of the failed endpoints is back online
org.kie.server.common.rest.NoEndpointFoundException: No available endpoints found
at org.kie.server.client.balancer.impl.AbstractBalancerStrategy.checkEmpty(AbstractBalancerStrategy.java:27)
at org.kie.server.client.balancer.impl.RoundRobinBalancerStrategy.next(RoundRobinBalancerStrategy.java:37)
at org.kie.server.client.balancer.LoadBalancer.getUrl(LoadBalancer.java:52)
at org.kie.server.client.impl.AbstractKieServicesClientImpl.invoke(AbstractKieServicesClientImpl.java:809)
at org.kie.server.client.impl.AbstractKieServicesClientImpl.makeHttpGetRequestAndCreateServiceResponse(AbstractKieServicesClientImpl.java:177)
at org.kie.server.client.impl.KieServicesClientImpl.getServerInfo(KieServicesClientImpl.java:159)
at org.kie.server.client.impl.KieServicesClientImpl.getCapabilitiesFromServer(KieServicesClientImpl.java:132)
at org.kie.server.client.impl.KieServicesClientImpl.init(KieServicesClientImpl.java:87)
at org.kie.server.client.impl.KieServicesClientImpl.<init>(KieServicesClientImpl.java:74)
at org.kie.server.client.KieServicesFactory.newKieServicesClient(KieServicesFactory.java:101)
at com.sample.rules.test.KieServerRestClientTest.connectionFailureTest(KieServerRestClientTest.java:55)
But after that, the thread used by LoadBalancer remains until termination of client application as LoadBalancer.close() is not called.
> Thread remains used by loadbalancer when connection to kie-server failed
> ------------------------------------------------------------------------
>
> Key: DROOLS-3548
> URL: https://issues.jboss.org/browse/DROOLS-3548
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 7.11.0.Final, 7.14.0.Final
> Environment: - Red Hat Decision Manager
> - 7
> - Red Hat Process Automation Manager
> - 7
> Reporter: Hiroko Miura
> Assignee: Maciej Swiderski
> Priority: Major
> Labels: support
> Attachments: rules-client.zip
>
>
> When KieServicesClient fails to connect to KieServer, LoadBalancer is invoked to check availability of server like the following.
> ~~~
> [2019/01/24 18:19:38.411] [pool-1-thread-1] [DEBUG] (LoadBalancer.java:149) - Starting to scan if any of the failed endpoints is back online
> org.kie.server.common.rest.NoEndpointFoundException: No available endpoints found
> at org.kie.server.client.balancer.impl.AbstractBalancerStrategy.checkEmpty(AbstractBalancerStrategy.java:27)
> at org.kie.server.client.balancer.impl.RoundRobinBalancerStrategy.next(RoundRobinBalancerStrategy.java:37)
> at org.kie.server.client.balancer.LoadBalancer.getUrl(LoadBalancer.java:52)
> at org.kie.server.client.impl.AbstractKieServicesClientImpl.invoke(AbstractKieServicesClientImpl.java:809)
> at org.kie.server.client.impl.AbstractKieServicesClientImpl.makeHttpGetRequestAndCreateServiceResponse(AbstractKieServicesClientImpl.java:177)
> at org.kie.server.client.impl.KieServicesClientImpl.getServerInfo(KieServicesClientImpl.java:159)
> at org.kie.server.client.impl.KieServicesClientImpl.getCapabilitiesFromServer(KieServicesClientImpl.java:132)
> at org.kie.server.client.impl.KieServicesClientImpl.init(KieServicesClientImpl.java:87)
> at org.kie.server.client.impl.KieServicesClientImpl.<init>(KieServicesClientImpl.java:74)
> at org.kie.server.client.KieServicesFactory.newKieServicesClient(KieServicesFactory.java:101)
> at com.sample.rules.test.KieServerRestClientTest.connectionFailureTest(KieServerRestClientTest.java:55)
> ~~~
> But after that, the thread used by LoadBalancer remains until termination of client application as LoadBalancer.close() is not called.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3549) [GSS] Thread remains used by loadbalancer when connection to kie-server failed
by Hiroko Miura (Jira)
Hiroko Miura created DROOLS-3549:
------------------------------------
Summary: [GSS] Thread remains used by loadbalancer when connection to kie-server failed
Key: DROOLS-3549
URL: https://issues.jboss.org/browse/DROOLS-3549
Project: Drools
Issue Type: Bug
Components: kie server
Affects Versions: 7.11.0.Final, 7.14.0.Final
Environment: - Red Hat Decision Manager
- 7
- Red Hat Process Automation Manager
- 7
Reporter: Hiroko Miura
Assignee: Maciej Swiderski
Attachments: rules-client.zip
When KieServicesClient fails to connect to KieServer, LoadBalancer is invoked to check availability of server like the following.
[2019/01/24 18:19:38.411] [pool-1-thread-1] [DEBUG] (LoadBalancer.java:149) - Starting to scan if any of the failed endpoints is back online
org.kie.server.common.rest.NoEndpointFoundException: No available endpoints found
at org.kie.server.client.balancer.impl.AbstractBalancerStrategy.checkEmpty(AbstractBalancerStrategy.java:27)
at org.kie.server.client.balancer.impl.RoundRobinBalancerStrategy.next(RoundRobinBalancerStrategy.java:37)
at org.kie.server.client.balancer.LoadBalancer.getUrl(LoadBalancer.java:52)
at org.kie.server.client.impl.AbstractKieServicesClientImpl.invoke(AbstractKieServicesClientImpl.java:809)
at org.kie.server.client.impl.AbstractKieServicesClientImpl.makeHttpGetRequestAndCreateServiceResponse(AbstractKieServicesClientImpl.java:177)
at org.kie.server.client.impl.KieServicesClientImpl.getServerInfo(KieServicesClientImpl.java:159)
at org.kie.server.client.impl.KieServicesClientImpl.getCapabilitiesFromServer(KieServicesClientImpl.java:132)
at org.kie.server.client.impl.KieServicesClientImpl.init(KieServicesClientImpl.java:87)
at org.kie.server.client.impl.KieServicesClientImpl.<init>(KieServicesClientImpl.java:74)
at org.kie.server.client.KieServicesFactory.newKieServicesClient(KieServicesFactory.java:101)
at com.sample.rules.test.KieServerRestClientTest.connectionFailureTest(KieServerRestClientTest.java:55)
But after that, the thread used by LoadBalancer remains until termination of client application as LoadBalancer.close() is not called.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3548) Thread remains used by loadbalancer when connection to kie-server failed
by Hiroko Miura (Jira)
[ https://issues.jboss.org/browse/DROOLS-3548?page=com.atlassian.jira.plugi... ]
Hiroko Miura updated DROOLS-3548:
---------------------------------
Attachment: rules-client.zip
> Thread remains used by loadbalancer when connection to kie-server failed
> ------------------------------------------------------------------------
>
> Key: DROOLS-3548
> URL: https://issues.jboss.org/browse/DROOLS-3548
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 7.11.0.Final, 7.14.0.Final
> Environment: - Red Hat Decision Manager
> - 7
> - Red Hat Process Automation Manager
> - 7
> Reporter: Hiroko Miura
> Assignee: Maciej Swiderski
> Priority: Major
> Labels: support
> Attachments: rules-client.zip
>
>
> When KieServicesClient fails to connect to KieServer, LoadBalancer is invoked to check availability of server like the following.
> [2019/01/24 18:19:38.411] [pool-1-thread-1] [DEBUG] (LoadBalancer.java:149) - Starting to scan if any of the failed endpoints is back online
> org.kie.server.common.rest.NoEndpointFoundException: No available endpoints found
> at org.kie.server.client.balancer.impl.AbstractBalancerStrategy.checkEmpty(AbstractBalancerStrategy.java:27)
> at org.kie.server.client.balancer.impl.RoundRobinBalancerStrategy.next(RoundRobinBalancerStrategy.java:37)
> at org.kie.server.client.balancer.LoadBalancer.getUrl(LoadBalancer.java:52)
> at org.kie.server.client.impl.AbstractKieServicesClientImpl.invoke(AbstractKieServicesClientImpl.java:809)
> at org.kie.server.client.impl.AbstractKieServicesClientImpl.makeHttpGetRequestAndCreateServiceResponse(AbstractKieServicesClientImpl.java:177)
> at org.kie.server.client.impl.KieServicesClientImpl.getServerInfo(KieServicesClientImpl.java:159)
> at org.kie.server.client.impl.KieServicesClientImpl.getCapabilitiesFromServer(KieServicesClientImpl.java:132)
> at org.kie.server.client.impl.KieServicesClientImpl.init(KieServicesClientImpl.java:87)
> at org.kie.server.client.impl.KieServicesClientImpl.<init>(KieServicesClientImpl.java:74)
> at org.kie.server.client.KieServicesFactory.newKieServicesClient(KieServicesFactory.java:101)
> at com.sample.rules.test.KieServerRestClientTest.connectionFailureTest(KieServerRestClientTest.java:55)
> But after that, the thread used by LoadBalancer remains until termination of client application as LoadBalancer.close() is not called.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3548) Thread remains used by loadbalancer when connection to kie-server failed
by Hiroko Miura (Jira)
Hiroko Miura created DROOLS-3548:
------------------------------------
Summary: Thread remains used by loadbalancer when connection to kie-server failed
Key: DROOLS-3548
URL: https://issues.jboss.org/browse/DROOLS-3548
Project: Drools
Issue Type: Bug
Components: kie server
Affects Versions: 7.14.0.Final, 7.11.0.Final
Environment: - Red Hat Decision Manager
- 7
- Red Hat Process Automation Manager
- 7
Reporter: Hiroko Miura
Assignee: Maciej Swiderski
When KieServicesClient fails to connect to KieServer, LoadBalancer is invoked to check availability of server like the following.
[2019/01/24 18:19:38.411] [pool-1-thread-1] [DEBUG] (LoadBalancer.java:149) - Starting to scan if any of the failed endpoints is back online
org.kie.server.common.rest.NoEndpointFoundException: No available endpoints found
at org.kie.server.client.balancer.impl.AbstractBalancerStrategy.checkEmpty(AbstractBalancerStrategy.java:27)
at org.kie.server.client.balancer.impl.RoundRobinBalancerStrategy.next(RoundRobinBalancerStrategy.java:37)
at org.kie.server.client.balancer.LoadBalancer.getUrl(LoadBalancer.java:52)
at org.kie.server.client.impl.AbstractKieServicesClientImpl.invoke(AbstractKieServicesClientImpl.java:809)
at org.kie.server.client.impl.AbstractKieServicesClientImpl.makeHttpGetRequestAndCreateServiceResponse(AbstractKieServicesClientImpl.java:177)
at org.kie.server.client.impl.KieServicesClientImpl.getServerInfo(KieServicesClientImpl.java:159)
at org.kie.server.client.impl.KieServicesClientImpl.getCapabilitiesFromServer(KieServicesClientImpl.java:132)
at org.kie.server.client.impl.KieServicesClientImpl.init(KieServicesClientImpl.java:87)
at org.kie.server.client.impl.KieServicesClientImpl.<init>(KieServicesClientImpl.java:74)
at org.kie.server.client.KieServicesFactory.newKieServicesClient(KieServicesFactory.java:101)
at com.sample.rules.test.KieServerRestClientTest.connectionFailureTest(KieServerRestClientTest.java:55)
But after that, the thread used by LoadBalancer remains until termination of client application as LoadBalancer.close() is not called.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-11641) Layers for servlet and full galleon feature-packs
by Jean-Francois Denise (Jira)
Jean-Francois Denise created WFLY-11641:
-------------------------------------------
Summary: Layers for servlet and full galleon feature-packs
Key: WFLY-11641
URL: https://issues.jboss.org/browse/WFLY-11641
Project: WildFly
Issue Type: Enhancement
Components: Build System
Reporter: Jean-Francois Denise
Assignee: Jean-Francois Denise
In order to take benefit from galleon layers feature, the servlet and full galleon feature-packs should define layers that could then be used to build custom installation. The layers are not intended to be exposed as a public contract, they are an implementation detail allowing for internal custom provisioning.
Only standalone configurations are impacted by layers.
We are proposing:
1) Define a set of servlet layers:
ee
legacy-security
naming
undertow
undertow-load-balancer
vault
web-server (complete servlet container)
2) Express the servlet default standalone configurations by a set of layers. The default configuration based on layers would be identical to the current one (based on feature-groups). feature-groups are the place where feature configuration occurs, layers are referencing feature-groups. The default configuration extends layers with legacy security aspects and undertow welcome content.
3) Define a first set of full layers that target standalone kind of configurations.
List of layers, layers defined in this feature-pack depend at least on web-server servlet layer.
cdi
h2-database
jaxrs
jms-activemq
jpa
microprofile
resource-adapters
4) Some servlet layers are extended to include packages present in full feature-pack:
ee
undertow
vault
5) Cloud profile layer
cloud-profile (aggregation layer of cdi, jaxrs, jms-activemq,jpa,microprofile,resource-adapters)
6) Resource management API is used to advertise modules injected in deployment units. Impacted subsystems: ee, security, connector, microprofile, jpa, jaxrs, weld, bean-validation.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JGRP-2234) Unlocked locks stay locked forever
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2234?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2234:
---------------------------
Fix Version/s: 3.6.18
> Unlocked locks stay locked forever
> ----------------------------------
>
> Key: JGRP-2234
> URL: https://issues.jboss.org/browse/JGRP-2234
> Project: JGroups
> Issue Type: Bug
> Reporter: Bram Klein Gunnewiek
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.0.11, 3.6.18
>
> Attachments: ClusterSplitLockTest.java, jg_clusterlock_output_testfail.txt
>
>
> As discussed in the mailing list we have issues where locks from the central lock protocol stay locked forever when the coordinator of the cluster disconnects. We can reproduce this with the attached ClusterSplitLockTest.java. Its a race condition and we need to run the test a lot of times (sometimes > 20) before we encounter a failure.
> What we think is happening:
> In a three node cluster (node A, B and C where node A is the coordinator) unlock requests from B and/or C can be missed when node A leaves and B and/or C don't have the new view installed yet. When, for example, node B takes over coordination it creates the lock table based on the back-ups. Lets say node C has locked the lock with name 'lockX'. Node C performs an unlock of 'lockX' just after node A (gracefully) leaves and sends the unlock request to node A since node C doesn't have the correct view installed yet. Node B has recreated the lock table where 'lockX' is locked by Node C. Node C doesn't resend the unlock request so 'lockX' gets locked forever.
> Attached is the testng test we wrote and the output of a test failure.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months