[JBoss JIRA] (WFWIP-309) MP Fault Tolerance - WELD-001303: No active contexts for scope type javax.enterprise.context.ApplicationScoped
by Ladislav Thon (Jira)
[ https://issues.redhat.com/browse/WFWIP-309?page=com.atlassian.jira.plugin... ]
Ladislav Thon commented on WFWIP-309:
-------------------------------------
Hey [~manovotn], what does it take to make the application context active/propagated to another thread? (I was thinking perhaps we need to propagate the thread context classloader, but I figured I'd rather ask.)
> MP Fault Tolerance - WELD-001303: No active contexts for scope type javax.enterprise.context.ApplicationScoped
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-309
> URL: https://issues.redhat.com/browse/WFWIP-309
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP Fault Tolerance
> Reporter: Miroslav Novak
> Assignee: Radoslav Husar
> Priority: Blocker
>
> There is unexpected error log in following test scenario:
> - Deploy MP FT service with:
> {noformat}
> @Asynchronous
> @Bulkhead(value = 15, waitingTaskQueue = 15)
> @Timeout(value = 1000)
> @Fallback(fallbackMethod = "processFallback")
> public CompletionStage<MyConnection> bulkheadTimeout(boolean fail) throws InterruptedException {
> if (fail) {
> Thread.sleep(2000);
> }
> return CompletableFuture.completedFuture(new MyConnection() {
> @Override
> public String getData() {
> return "Hello from @Bulkhead @Timeout method";
> }
> });
> }
> private CompletionStage<MyConnection> processFallback(boolean fail) {
> return CompletableFuture.completedFuture(new MyConnection() {
> @Override
> public String getData() {
> return "Fallback Hello";
> }
> });
> }
> {noformat}
> - Send 10+ parallel requests with fail == true
> Expected result:
> All requests should go to fallback.
> Actual Result:
> This test is currently hitting issue WFWIP-308 however additionally there is error in server log:
> {code}
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) Exception in thread "pool-22-thread-4" Exception in thread "pool-22-thread-2" org.jboss.weld.contexts.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.ApplicationScoped
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:647)
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:89)
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:123)
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63)
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:87)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:131)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at org.eclipse.microprofile.metrics.MetricRegistry$Proxy$_$$_WeldClientProxy.getHistograms(Unknown Source)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at io.smallrye.faulttolerance.metrics.MetricsCollectorFactory$MetricsCollectorImpl.histogramOf(MetricsCollectorFactory.java:105)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at io.smallrye.faulttolerance.metrics.MetricsCollectorFactory$MetricsCollectorImpl.histogramUpdate(MetricsCollectorFactory.java:86)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at io.smallrye.faulttolerance.metrics.MetricsCollectorFactory$MetricsCollectorImpl.bulkheadQueueLeft(MetricsCollectorFactory.java:125)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at io.smallrye.faulttolerance.core.bulkhead.CompletionStageBulkhead$CompletionStageBulkheadTask.run(CompletionStageBulkhead.java:78)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFWIP-309) MP Fault Tolerance - WELD-001303: No active contexts for scope type javax.enterprise.context.ApplicationScoped
by Miroslav Novak (Jira)
[ https://issues.redhat.com/browse/WFWIP-309?page=com.atlassian.jira.plugin... ]
Miroslav Novak commented on WFWIP-309:
--------------------------------------
cc-ing [~lthon]
> MP Fault Tolerance - WELD-001303: No active contexts for scope type javax.enterprise.context.ApplicationScoped
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-309
> URL: https://issues.redhat.com/browse/WFWIP-309
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP Fault Tolerance
> Reporter: Miroslav Novak
> Assignee: Radoslav Husar
> Priority: Blocker
>
> There is unexpected error log in following test scenario:
> - Deploy MP FT service with:
> {noformat}
> @Asynchronous
> @Bulkhead(value = 15, waitingTaskQueue = 15)
> @Timeout(value = 1000)
> @Fallback(fallbackMethod = "processFallback")
> public CompletionStage<MyConnection> bulkheadTimeout(boolean fail) throws InterruptedException {
> if (fail) {
> Thread.sleep(2000);
> }
> return CompletableFuture.completedFuture(new MyConnection() {
> @Override
> public String getData() {
> return "Hello from @Bulkhead @Timeout method";
> }
> });
> }
> private CompletionStage<MyConnection> processFallback(boolean fail) {
> return CompletableFuture.completedFuture(new MyConnection() {
> @Override
> public String getData() {
> return "Fallback Hello";
> }
> });
> }
> {noformat}
> - Send 10+ parallel requests with fail == true
> Expected result:
> All requests should go to fallback.
> Actual Result:
> This test is currently hitting issue WFWIP-308 however additionally there is error in server log:
> {code}
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) Exception in thread "pool-22-thread-4" Exception in thread "pool-22-thread-2" org.jboss.weld.contexts.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.ApplicationScoped
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:647)
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:89)
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:123)
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63)
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:87)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:131)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at org.eclipse.microprofile.metrics.MetricRegistry$Proxy$_$$_WeldClientProxy.getHistograms(Unknown Source)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at io.smallrye.faulttolerance.metrics.MetricsCollectorFactory$MetricsCollectorImpl.histogramOf(MetricsCollectorFactory.java:105)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at io.smallrye.faulttolerance.metrics.MetricsCollectorFactory$MetricsCollectorImpl.histogramUpdate(MetricsCollectorFactory.java:86)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at io.smallrye.faulttolerance.metrics.MetricsCollectorFactory$MetricsCollectorImpl.bulkheadQueueLeft(MetricsCollectorFactory.java:125)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at io.smallrye.faulttolerance.core.bulkhead.CompletionStageBulkhead$CompletionStageBulkheadTask.run(CompletionStageBulkhead.java:78)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFWIP-309) MP Fault Tolerance - WELD-001303: No active contexts for scope type javax.enterprise.context.ApplicationScoped
by Miroslav Novak (Jira)
[ https://issues.redhat.com/browse/WFWIP-309?page=com.atlassian.jira.plugin... ]
Miroslav Novak updated WFWIP-309:
---------------------------------
Security: (was: Security Issue)
> MP Fault Tolerance - WELD-001303: No active contexts for scope type javax.enterprise.context.ApplicationScoped
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-309
> URL: https://issues.redhat.com/browse/WFWIP-309
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP Fault Tolerance
> Reporter: Miroslav Novak
> Assignee: Radoslav Husar
> Priority: Blocker
>
> There is unexpected error log in following test scenario:
> - Deploy MP FT service with:
> {noformat}
> @Asynchronous
> @Bulkhead(value = 15, waitingTaskQueue = 15)
> @Timeout(value = 1000)
> @Fallback(fallbackMethod = "processFallback")
> public CompletionStage<MyConnection> bulkheadTimeout(boolean fail) throws InterruptedException {
> if (fail) {
> Thread.sleep(2000);
> }
> return CompletableFuture.completedFuture(new MyConnection() {
> @Override
> public String getData() {
> return "Hello from @Bulkhead @Timeout method";
> }
> });
> }
> private CompletionStage<MyConnection> processFallback(boolean fail) {
> return CompletableFuture.completedFuture(new MyConnection() {
> @Override
> public String getData() {
> return "Fallback Hello";
> }
> });
> }
> {noformat}
> - Send 10+ parallel requests with fail == true
> Expected result:
> All requests should go to fallback.
> Actual Result:
> This test is currently hitting issue WFWIP-308 however additionally there is error in server log:
> {code}
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) Exception in thread "pool-22-thread-4" Exception in thread "pool-22-thread-2" org.jboss.weld.contexts.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.ApplicationScoped
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:647)
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:89)
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:123)
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63)
> 16:55:41,374 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:87)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:131)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at org.eclipse.microprofile.metrics.MetricRegistry$Proxy$_$$_WeldClientProxy.getHistograms(Unknown Source)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at io.smallrye.faulttolerance.metrics.MetricsCollectorFactory$MetricsCollectorImpl.histogramOf(MetricsCollectorFactory.java:105)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at io.smallrye.faulttolerance.metrics.MetricsCollectorFactory$MetricsCollectorImpl.histogramUpdate(MetricsCollectorFactory.java:86)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at io.smallrye.faulttolerance.metrics.MetricsCollectorFactory$MetricsCollectorImpl.bulkheadQueueLeft(MetricsCollectorFactory.java:125)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at io.smallrye.faulttolerance.core.bulkhead.CompletionStageBulkhead$CompletionStageBulkheadTask.run(CompletionStageBulkhead.java:78)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 16:55:41,375 ERROR [stderr] (pool-22-thread-2) at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13166) https connector / idletimeout / keep-alive settings
by Abdul Islam (Jira)
[ https://issues.redhat.com/browse/WFLY-13166?page=com.atlassian.jira.plugi... ]
Abdul Islam updated WFLY-13166:
-------------------------------
Description:
Hi,
We're using Wildlfy v15.0.1 and external traffic reaches Wildfly app servers via a load balancer, lately we are seeing 502 gateway timeout for certain calls. One of the recommendation from load balancer support team is to enable keep-alive settings at the app server level to match the load balancer, we have a 15 min idle time out set on load balancer. It would be great if anyone has any insights or recommendations on this topic. We basically wish to match idle time on Wildfly to whats configured in our load balancer.
I can across the link below, please confirm if its applicable to Wildfly v15.0.1
https://access.redhat.com/solutions/456733
Thanks for your help in advance.
was:
Hi,
We're using Wildlfy v15.0.1 and external traffic reaches Wildfly app servers via a load balancer, lately we are seeing 502 gateway timeout for certain calls. One of the recommendation from load balancer support team is to enable keep-alive settings at the app server level to match the load balancer, we have a 15 min idle time out set on load balancer. It would be great if anyone has any insights or recommendations on this topic. We basically wish to match idle time on Wildfly to whats configured in our load balancer.
Thanks
> https connector / idletimeout / keep-alive settings
> ---------------------------------------------------
>
> Key: WFLY-13166
> URL: https://issues.redhat.com/browse/WFLY-13166
> Project: WildFly
> Issue Type: Task
> Reporter: Abdul Islam
> Assignee: Brian Stansberry
> Priority: Major
>
> Hi,
> We're using Wildlfy v15.0.1 and external traffic reaches Wildfly app servers via a load balancer, lately we are seeing 502 gateway timeout for certain calls. One of the recommendation from load balancer support team is to enable keep-alive settings at the app server level to match the load balancer, we have a 15 min idle time out set on load balancer. It would be great if anyone has any insights or recommendations on this topic. We basically wish to match idle time on Wildfly to whats configured in our load balancer.
> I can across the link below, please confirm if its applicable to Wildfly v15.0.1
> https://access.redhat.com/solutions/456733
> Thanks for your help in advance.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13166) https connector / idletimeout / keep-alive settings
by Abdul Islam (Jira)
[ https://issues.redhat.com/browse/WFLY-13166?page=com.atlassian.jira.plugi... ]
Abdul Islam updated WFLY-13166:
-------------------------------
Description:
Hi,
We're using Wildlfy v15.0.1 and external traffic reaches Wildfly app servers via a load balancer, lately we are seeing 502 gateway timeout for certain calls. One of the recommendation from load balancer support team is to enable keep-alive settings at the app server level to match the load balancer, we have a 15 min idle time out set on load balancer. It would be great if anyone has any insights or recommendations on this topic. We basically wish to match idle time on Wildfly to whats configured in our load balancer.
Thanks
was:
Hi,
We're using Wildlfy v15.0.1 and external traffic reaches Wildfly app servers via a load balancer, lately we are seeing 502 gateway timeout for certain calls. One of the recommendation from load balancer support team is to enable keep-alive settings at the app server level to match the load balancer, we have a 15 min idle time out set on load balancer. It would be great if anyone has any insights or recommendations on this topic. W
Thanks
> https connector / idletimeout / keep-alive settings
> ---------------------------------------------------
>
> Key: WFLY-13166
> URL: https://issues.redhat.com/browse/WFLY-13166
> Project: WildFly
> Issue Type: Task
> Reporter: Abdul Islam
> Assignee: Brian Stansberry
> Priority: Major
>
> Hi,
> We're using Wildlfy v15.0.1 and external traffic reaches Wildfly app servers via a load balancer, lately we are seeing 502 gateway timeout for certain calls. One of the recommendation from load balancer support team is to enable keep-alive settings at the app server level to match the load balancer, we have a 15 min idle time out set on load balancer. It would be great if anyone has any insights or recommendations on this topic. We basically wish to match idle time on Wildfly to whats configured in our load balancer.
> Thanks
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13166) https connector / idletimeout / keep-alive settings
by Abdul Islam (Jira)
Abdul Islam created WFLY-13166:
----------------------------------
Summary: https connector / idletimeout / keep-alive settings
Key: WFLY-13166
URL: https://issues.redhat.com/browse/WFLY-13166
Project: WildFly
Issue Type: Task
Reporter: Abdul Islam
Assignee: Brian Stansberry
Hi,
We're using Wildlfy v15.0.1 and external traffic reaches Wildfly app servers via a load balancer, lately we are seeing gateway timeout 502 for certain calls. One of the recommendation from load balancer support team is to enable keep-alive settings at the app server level to match the load balancer, we have a 15 min idle time out set on load balancer. It would be great if anyone has any insights or recommendations on this topic. W
Thanks
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13166) https connector / idletimeout / keep-alive settings
by Abdul Islam (Jira)
[ https://issues.redhat.com/browse/WFLY-13166?page=com.atlassian.jira.plugi... ]
Abdul Islam updated WFLY-13166:
-------------------------------
Description:
Hi,
We're using Wildlfy v15.0.1 and external traffic reaches Wildfly app servers via a load balancer, lately we are seeing 502 gateway timeout for certain calls. One of the recommendation from load balancer support team is to enable keep-alive settings at the app server level to match the load balancer, we have a 15 min idle time out set on load balancer. It would be great if anyone has any insights or recommendations on this topic. W
Thanks
was:
Hi,
We're using Wildlfy v15.0.1 and external traffic reaches Wildfly app servers via a load balancer, lately we are seeing gateway timeout 502 for certain calls. One of the recommendation from load balancer support team is to enable keep-alive settings at the app server level to match the load balancer, we have a 15 min idle time out set on load balancer. It would be great if anyone has any insights or recommendations on this topic. W
Thanks
> https connector / idletimeout / keep-alive settings
> ---------------------------------------------------
>
> Key: WFLY-13166
> URL: https://issues.redhat.com/browse/WFLY-13166
> Project: WildFly
> Issue Type: Task
> Reporter: Abdul Islam
> Assignee: Brian Stansberry
> Priority: Major
>
> Hi,
> We're using Wildlfy v15.0.1 and external traffic reaches Wildfly app servers via a load balancer, lately we are seeing 502 gateway timeout for certain calls. One of the recommendation from load balancer support team is to enable keep-alive settings at the app server level to match the load balancer, we have a 15 min idle time out set on load balancer. It would be great if anyone has any insights or recommendations on this topic. W
> Thanks
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ELYWEB-99) [GSS][7.2.2] HTTP External Security Not Supported by Elytron
by Ashley Abdel-Sayed (Jira)
Ashley Abdel-Sayed created ELYWEB-99:
----------------------------------------
Summary: [GSS][7.2.2] HTTP External Security Not Supported by Elytron
Key: ELYWEB-99
URL: https://issues.redhat.com/browse/ELYWEB-99
Project: Elytron Web
Issue Type: Feature Request
Reporter: Ashley Abdel-Sayed
Assignee: Ashley Abdel-Sayed
For legacy security, there's an EXTERNAL HTTP authentication mechanism (io.undertow.security.impl.ExternalAuthenticationMechanism) which performs no verification and simply uses the principal that was passed from the REMOTE_USER attribute by the AJP protocol. There is a "ClientLoginModule" in legacy security used as such: https://access.redhat.com/solutions/3465231. It is a requirement to add an equivalent of this EXTERNAL mechanism available in legacy and Elytron-SASL for Elytron-HTTP in order to migrate away from legacy security.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months