[JBoss JIRA] (WFWIP-282) MP Fault Tolerance - UnsupportedOperationException error during undeploy
by Miroslav Novak (Jira)
Miroslav Novak created WFWIP-282:
------------------------------------
Summary: MP Fault Tolerance - UnsupportedOperationException error during undeploy
Key: WFWIP-282
URL: https://issues.redhat.com/browse/WFWIP-282
Project: WildFly WIP
Issue Type: Bug
Components: MP Fault Tolerance
Reporter: Miroslav Novak
Assignee: Radoslav Husar
If MP FT application is undeployed then following errors are logged:
{code}
15:21:59,393 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 78) WFLYUT0022: Unregistered web context: '/test' from server 'default-server'
15:21:59,407 ERROR [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0043: Deployment unit processor org.jboss.as.weld.deployment.processors.WeldBeanManagerServiceProcessor@2feaf5f5 unexpectedly threw an exception during undeploy phase INSTALL of deployment "test.war": java.lang.UnsupportedOperationException
at java.util.concurrent.CopyOnWriteArrayList$COWIterator.remove(CopyOnWriteArrayList.java:1178)
at java.util.Collections$CheckedCollection$1.remove(Collections.java:3077)
at java.util.Collection.removeIf(Collection.java:415)
at org.jboss.as.weld.deployment.processors.WeldBeanManagerServiceProcessor.undeploy(WeldBeanManagerServiceProcessor.java:145)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:245)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:238)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1795)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1764)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
15:21:59,424 ERROR [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0043: Deployment unit processor org.jboss.as.ee.concurrent.deployers.EEConcurrentContextProcessor@678bc2e4 unexpectedly threw an exception during undeploy phase POST_MODULE of deployment "test.war": java.lang.UnsupportedOperationException
at java.util.concurrent.CopyOnWriteArrayList$COWIterator.remove(CopyOnWriteArrayList.java:1178)
at java.util.Collections$CheckedCollection$1.remove(Collections.java:3077)
at java.util.Collection.removeIf(Collection.java:415)
at org.jboss.as.ee.concurrent.deployers.EEConcurrentContextProcessor.undeploy(EEConcurrentContextProcessor.java:119)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:245)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:238)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1795)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1764)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
15:21:59,425 ERROR [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0043: Deployment unit processor org.jboss.as.connector.deployers.ra.processors.CachedConnectionManagerSetupProcessor@7c025ffb unexpectedly threw an exception during undeploy phase POST_MODULE of deployment "test.war": java.lang.UnsupportedOperationException
at java.util.concurrent.CopyOnWriteArrayList$COWIterator.remove(CopyOnWriteArrayList.java:1178)
at java.util.Collections$CheckedCollection$1.remove(Collections.java:3077)
at java.util.Collection.removeIf(Collection.java:415)
at org.jboss.as.connector.deployers.ra.processors.CachedConnectionManagerSetupProcessor.undeploy(CachedConnectionManagerSetupProcessor.java:75)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:245)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:238)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1795)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1764)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
15:21:59,425 ERROR [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0043: Deployment unit processor org.jboss.as.ee.naming.ModuleContextProcessor@7aab312f unexpectedly threw an exception during undeploy phase POST_MODULE of deployment "test.war": java.lang.UnsupportedOperationException
at java.util.concurrent.CopyOnWriteArrayList$COWIterator.remove(CopyOnWriteArrayList.java:1178)
at java.util.Collections$CheckedCollection$1.remove(Collections.java:3077)
at java.util.Collection.removeIf(Collection.java:415)
at org.jboss.as.ee.naming.ModuleContextProcessor.undeploy(ModuleContextProcessor.java:111)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:245)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:238)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1795)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1764)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
15:21:59,426 ERROR [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0043: Deployment unit processor org.jboss.as.webservices.deployers.GracefulShutdownIntegrationProcessor@775cb98a unexpectedly threw an exception during undeploy phase POST_MODULE of deployment "test.war": java.lang.UnsupportedOperationException
at java.util.concurrent.CopyOnWriteArrayList$COWIterator.remove(CopyOnWriteArrayList.java:1178)
at java.util.Collections$CheckedCollection$1.remove(Collections.java:3077)
at java.util.Collection.removeIf(Collection.java:415)
at org.jboss.as.webservices.deployers.GracefulShutdownIntegrationProcessor.undeploy(GracefulShutdownIntegrationProcessor.java:52)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:245)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:238)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1795)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1764)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
15:21:59,432 ERROR [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0043: Deployment unit processor org.jboss.as.txn.deployment.TransactionLeakRollbackProcessor@3f268819 unexpectedly threw an exception during undeploy phase PARSE of deployment "test.war": java.lang.UnsupportedOperationException
at java.util.concurrent.CopyOnWriteArrayList$COWIterator.remove(CopyOnWriteArrayList.java:1178)
at java.util.Collections$CheckedCollection$1.remove(Collections.java:3077)
at java.util.Collection.removeIf(Collection.java:415)
at org.jboss.as.txn.deployment.TransactionLeakRollbackProcessor.undeploy(TransactionLeakRollbackProcessor.java:59)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:245)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:238)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1795)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1764)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
15:21:59,440 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 50ms
15:21:59,457 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location /home/mnovak/tmp/wildfly-19.0.0.Beta1-SNAPSHOT/standalone/data/content/eb/abb19cbac681b1f3366cf8a71164c11f26b9aa/content
15:21:59,458 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war")
{code}
Expected result is that no errors are logged during undeploy.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12861) microprofile-config subsystem should not expose smallrye implementation to deployments
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-12861?page=com.atlassian.jira.plugi... ]
Paul Ferraro edited comment on WFLY-12861 at 12/10/19 9:55 PM:
---------------------------------------------------------------
After some analysis, smallrye-config is completely reliant on the TCCL in a number of areas, including:
* its CDI portable extension (specifically via ConfigProvider.getConfig())
* ConfigBuilder implementation
* default Class converters
... rendering it infeasible to remove this deployment dependency without completely re-implementing much of smallrye-config.
was (Author: pferraro):
After some analysis, smallrye-config relies heavily on the TCCL to instrument its CDI portable extension (specifically via ConfigProvider.getConfig()) rendering it infeasible to remove this deployment dependency without completely re-implementing the Extension.
> microprofile-config subsystem should not expose smallrye implementation to deployments
> --------------------------------------------------------------------------------------
>
> Key: WFLY-12861
> URL: https://issues.redhat.com/browse/WFLY-12861
> Project: WildFly
> Issue Type: Bug
> Components: MP Config
> Affects Versions: 18.0.1.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
>
> Smallrye is an implementation detail of the specification and should not be exposed to deployments. It seems the only reasons to expose io.smallrye.config to a deployment is to allow CDI to dynamically load its portable extension. Registering these manually removes that requirement.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12861) microprofile-config subsystem should not expose smallrye implementation to deployments
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-12861?page=com.atlassian.jira.plugi... ]
Paul Ferraro edited comment on WFLY-12861 at 12/10/19 9:55 PM:
---------------------------------------------------------------
After some analysis, smallrye-config is completely reliant on the TCCL in a number of areas, including:
* its CDI portable extension (via ConfigProvider.getConfig())
* ConfigBuilder implementation
* default Class converters
... rendering it infeasible to remove this deployment dependency without completely re-implementing much of smallrye-config.
was (Author: pferraro):
After some analysis, smallrye-config is completely reliant on the TCCL in a number of areas, including:
* its CDI portable extension (specifically via ConfigProvider.getConfig())
* ConfigBuilder implementation
* default Class converters
... rendering it infeasible to remove this deployment dependency without completely re-implementing much of smallrye-config.
> microprofile-config subsystem should not expose smallrye implementation to deployments
> --------------------------------------------------------------------------------------
>
> Key: WFLY-12861
> URL: https://issues.redhat.com/browse/WFLY-12861
> Project: WildFly
> Issue Type: Bug
> Components: MP Config
> Affects Versions: 18.0.1.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
>
> Smallrye is an implementation detail of the specification and should not be exposed to deployments. It seems the only reasons to expose io.smallrye.config to a deployment is to allow CDI to dynamically load its portable extension. Registering these manually removes that requirement.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12861) microprofile-config subsystem should not expose smallrye implementation to deployments
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-12861?page=com.atlassian.jira.plugi... ]
Paul Ferraro edited comment on WFLY-12861 at 12/10/19 9:29 PM:
---------------------------------------------------------------
After some analysis, smallrye-config relies heavily on the TCCL to instrument its CDI portable extension (specifically via ConfigProvider.getConfig()) rendering it infeasible to remove this deployment dependency without completely re-implementing the Extension.
was (Author: pferraro):
After some analysis, smallrye-config relies heavily on the TCCL to instrument its CDI portable extension (specifically via ConfigProvider.getConfig()) rendering it infeasible to remove this deployment dependency without completely rewriting the Extension implementation.
> microprofile-config subsystem should not expose smallrye implementation to deployments
> --------------------------------------------------------------------------------------
>
> Key: WFLY-12861
> URL: https://issues.redhat.com/browse/WFLY-12861
> Project: WildFly
> Issue Type: Bug
> Components: MP Config
> Affects Versions: 18.0.1.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
>
> Smallrye is an implementation detail of the specification and should not be exposed to deployments. It seems the only reasons to expose io.smallrye.config to a deployment is to allow CDI to dynamically load its portable extension. Registering these manually removes that requirement.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12861) microprofile-config subsystem should not expose smallrye implementation to deployments
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-12861?page=com.atlassian.jira.plugi... ]
Paul Ferraro edited comment on WFLY-12861 at 12/10/19 9:27 PM:
---------------------------------------------------------------
After some analysis, smallrye-config relies heavily on the TCCL to instrument its CDI portable extension (specifically via ConfigProvider.getConfig()) rendering it infeasible to remove this deployment dependency without completely rewriting the Extension implementation.
was (Author: pferraro):
After some analysis, smallrye-config relies heavily on the TCCL to instrument its CDI portable extension (specifically via ConfigProvider.getConfig()) rendering it infeasible to achieve this without completely rewriting the Extension implementation.
> microprofile-config subsystem should not expose smallrye implementation to deployments
> --------------------------------------------------------------------------------------
>
> Key: WFLY-12861
> URL: https://issues.redhat.com/browse/WFLY-12861
> Project: WildFly
> Issue Type: Bug
> Components: MP Config
> Affects Versions: 18.0.1.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
>
> Smallrye is an implementation detail of the specification and should not be exposed to deployments. It seems the only reasons to expose io.smallrye.config to a deployment is to allow CDI to dynamically load its portable extension. Registering these manually removes that requirement.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12861) microprofile-config subsystem should not expose smallrye implementation to deployments
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-12861?page=com.atlassian.jira.plugi... ]
Paul Ferraro commented on WFLY-12861:
-------------------------------------
After some analysis, smallrye-config relies heavily on the TCCL to instrument its CDI portable extension (specifically via ConfigProvider.getConfig()) rendering it infeasible to achieve this without completely rewriting the Extension implementation.
> microprofile-config subsystem should not expose smallrye implementation to deployments
> --------------------------------------------------------------------------------------
>
> Key: WFLY-12861
> URL: https://issues.redhat.com/browse/WFLY-12861
> Project: WildFly
> Issue Type: Bug
> Components: MP Config
> Affects Versions: 18.0.1.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
>
> Smallrye is an implementation detail of the specification and should not be exposed to deployments. It seems the only reasons to expose io.smallrye.config to a deployment is to allow CDI to dynamically load its portable extension. Registering these manually removes that requirement.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-4296) Rewrite parsing of modified properties
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-4296?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi updated DROOLS-4296:
--------------------------------------
Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 50-52 (from Dec 9) (was: 2019 Week 44-46 (from Okt 28))
> Rewrite parsing of modified properties
> --------------------------------------
>
> Key: DROOLS-4296
> URL: https://issues.redhat.com/browse/DROOLS-4296
> Project: Drools
> Issue Type: Enhancement
> Reporter: Luca Molteni
> Assignee: Toshiya Kobayashi
> Priority: Minor
> Labels: good-first-issue
>
> See Consequence::findModifiedProperties
> Currently modified properties are parsed throughout the consequence, but that information is already present after the preprocessing of the ModifyStatement so it can be simplified a lot.
> This can be forward ported to Kogito also
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12861) microprofile-config subsystem should not expose smallrye implementation to deployments
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-12861?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFLY-12861:
--------------------------------
Description: Smallrye is an implementation detail of the specification and should not be exposed to deployments. It seems the only reasons to expose io.smallrye.config to a deployment is to allow CDI to dynamically load its portable extension. Registering these manually removes that requirement. (was: Smallrye is an implementation detail of the specification and should not be exposed to deployments. It seems the only reasons to expose io.smallrye.config to a deployment is to allow CDI to dynamically load its portable extension, and for lazy service loading of the ConfigProviderResolver implementation. Registering these manually removes that requirement.)
> microprofile-config subsystem should not expose smallrye implementation to deployments
> --------------------------------------------------------------------------------------
>
> Key: WFLY-12861
> URL: https://issues.redhat.com/browse/WFLY-12861
> Project: WildFly
> Issue Type: Bug
> Components: MP Config
> Affects Versions: 18.0.1.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
>
> Smallrye is an implementation detail of the specification and should not be exposed to deployments. It seems the only reasons to expose io.smallrye.config to a deployment is to allow CDI to dynamically load its portable extension. Registering these manually removes that requirement.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months