[Red Hat JIRA] (WFLY-14361) Failed permission check during PersistenceManager.start()
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-14361:
-----------------------------------
Summary: Failed permission check during PersistenceManager.start()
Key: WFLY-14361
URL: https://issues.redhat.com/browse/WFLY-14361
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 22.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
To workaround ISPN-11121, we currently perform Cache.start() as a privileged action. However, while Infinispan *normally* starts the persistence manager during Cache.start(), this is not guaranteed, as individual components can restart without the cache itself restarting. By overriding the persistence manager component with a decorator, we can be more precise with our workaround.
While this issue is unlikely to occur in the wild, it has been observed in our CI environment:
https://ci.wildfly.org/viewLog.html?buildId=239281&buildTypeId=WF_PullReq...
{noformat}
[0m[31m17:48:28,241 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 93) MSC000001: Failed to start service org.wildfly.clustering.infinispan.cache.web."FineNonTransactionalSessionActivationTestCase.war": org.jboss.msc.service.StartException in service org.wildfly.clustering.infinispan.cache.web."FineNonTransactionalSessionActivationTestCase.war": org.infinispan.commons.CacheConfigurationException: Error starting component org.infinispan.persistence.manager.PersistenceManager
at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:66)
at org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
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)
at org.jboss.threads.JBossThread.run(JBossThread.java:513)
Caused by: org.infinispan.commons.CacheConfigurationException: Error starting component org.infinispan.persistence.manager.PersistenceManager
at org.infinispan.factories.impl.BasicComponentRegistryImpl.startWrapper(BasicComponentRegistryImpl.java:560)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.access$700(BasicComponentRegistryImpl.java:30)
at org.infinispan.factories.impl.BasicComponentRegistryImpl$ComponentWrapper.running(BasicComponentRegistryImpl.java:775)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.startDependencies(BasicComponentRegistryImpl.java:610)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.doStartWrapper(BasicComponentRegistryImpl.java:574)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.startWrapper(BasicComponentRegistryImpl.java:552)
at org.infinispan.factories.impl.BasicComponentRegistryImpl.access$700(BasicComponentRegistryImpl.java:30)
at org.infinispan.factories.impl.BasicComponentRegistryImpl$ComponentWrapper.running(BasicComponentRegistryImpl.java:775)
at org.infinispan.factories.ComponentRegistry.getLocalComponent(ComponentRegistry.java:174)
at org.infinispan.factories.ComponentRegistry.getLocalComponent(ComponentRegistry.java:180)
at org.wildfly.clustering.infinispan.spi.WildFlyInfinispanModuleLifecycle.cacheStarting(WildFlyInfinispanModuleLifecycle.java:44)
at org.infinispan.factories.ComponentRegistry.notifyCacheStarting(ComponentRegistry.java:230)
at org.infinispan.factories.ComponentRegistry.preStart(ComponentRegistry.java:220)
at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:235)
at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:210)
at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:1008)
at org.infinispan.cache.impl.AbstractDelegatingCache.start(AbstractDelegatingCache.java:512)
at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:697)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:643)
at org.infinispan.manager.DefaultCacheManager.internalGetCache(DefaultCacheManager.java:532)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:510)
at org.jboss.as.clustering.infinispan.DefaultCacheContainer.getCache(DefaultCacheContainer.java:92)
at org.wildfly.clustering.infinispan.spi.service.CacheServiceConfigurator.get(CacheServiceConfigurator.java:77)
at org.wildfly.clustering.infinispan.spi.service.CacheServiceConfigurator.get(CacheServiceConfigurator.java:55)
at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:63)
... 7 more
Caused by: java.util.concurrent.CompletionException: org.infinispan.persistence.spi.PersistenceException: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "/store/work/tc-work/aefe2f90bf7646ab/testsuite/integration/clustering/target/wildfly-1/standalone/data/infinispan/web/FineNonTransactionalSessionActivationTestCase.war.dat" "read")" in code source "(vfs:/content/ExternalizerTestCase.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.ExternalizerTestCase.war" from Service Module Loader")
at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1643)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at org.jboss.as.clustering.context.ContextReferenceExecutor.execute(ContextReferenceExecutor.java:49)
at org.jboss.as.clustering.context.ContextualExecutor$1.run(ContextualExecutor.java:70)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.infinispan.persistence.spi.PersistenceException: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "/store/work/tc-work/aefe2f90bf7646ab/testsuite/integration/clustering/target/wildfly-1/standalone/data/infinispan/web/FineNonTransactionalSessionActivationTestCase.war.dat" "read")" in code source "(vfs:/content/ExternalizerTestCase.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.ExternalizerTestCase.war" from Service Module Loader")
at org.infinispan.persistence.file.SingleFileStore.start(SingleFileStore.java:174)
at org.infinispan.persistence.support.NonBlockingStoreAdapter.lambda$start$0(NonBlockingStoreAdapter.java:108)
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1640)
... 7 more
Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "/store/work/tc-work/aefe2f90bf7646ab/testsuite/integration/clustering/target/wildfly-1/standalone/data/infinispan/web/FineNonTransactionalSessionActivationTestCase.war.dat" "read")" in code source "(vfs:/content/ExternalizerTestCase.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.ExternalizerTestCase.war" from Service Module Loader")
at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:309)
at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:201)
at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
at org.wildfly.security.manager.WildFlySecurityManager.checkRead(WildFlySecurityManager.java:374)
at java.io.File.exists(File.java:816)
at org.infinispan.persistence.file.SingleFileStore.start(SingleFileStore.java:138)
... 9 more
{noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (WFLY-14284) WildFly doesn't stop while waiting for PeriodicRecovery
by Ondrej Chaloupka (Jira)
[ https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi... ]
Ondrej Chaloupka commented on WFLY-14284:
-----------------------------------------
I see. As I can see I think the documentation needs a bit more care related this. I would think that the all places which talks about `http-remoting` should be changed but I'm not sure. If you can create an issue and assign it to me it would be nice.
Regarding the remote outbound connection. What I know the outbound connection needs to be configured with some security configuration. You will need at least the `security-realm`. The protocol is not needed when you are fine with the default one (which will be the `remote+http`). I'm not sure about username.
> WildFly doesn't stop while waiting for PeriodicRecovery
> -------------------------------------------------------
>
> Key: WFLY-14284
> URL: https://issues.redhat.com/browse/WFLY-14284
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Transactions
> Affects Versions: 18.0.1.Final, 20.0.1.Final
> Reporter: Adriano Teixeira de Souza
> Assignee: Michael Musgrove
> Priority: Major
> Attachments: ejb-configs.sh, jboss-ejb-client.xml, server(transaction).log, thread-dump-stop-1.txt
>
>
> I'm testing wildfly 20.0.1 (and 21.0.2 was tested too) for replace our old version of Wildfly 10.
> it happens that frequently we have seen that the stop function of server does not work and we need to kill the process by manual operation on the OS.
> It sounds like a dead look.
> I attatch the thread dump on this.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (WFLY-14123) Add OSGI Headers for jboss-client.jar
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFLY-14123?page=com.atlassian.jira.plugi... ]
Darran Lofthouse updated WFLY-14123:
------------------------------------
Summary: Add OSGI Headers for jboss-client.jar (was: Add OSGI Headers for jboss-ciient.jar)
> Add OSGI Headers for jboss-client.jar
> -------------------------------------
>
> Key: WFLY-14123
> URL: https://issues.redhat.com/browse/WFLY-14123
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Reporter: Darran Lofthouse
> Assignee: Moulali Shikalwadi
> Priority: Major
> Fix For: 23.0.0.Beta1
>
>
> Headers such as the following should be added:
> {code:java}
> Bundle-ManifestVersion: 2
> Bundle-SymbolicName: org.jboss.client
> Bundle-Version: 1.0
> Bundle-Name: Test
> ExtensionFragment-Host: org.openjdk.jmc.rjmxExport-
> Package: *
> Automatic-Module-Name: org.jboss.client {code}
> The reason for this change is so the jar can be copied to a Java Mission Control folder
> {{/path/to/jmc/dropins/ and these updates will correct the class loading enabling the remoting-jmx connection to be established.}}
>
>
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (WFLY-14284) WildFly doesn't stop while waiting for PeriodicRecovery
by Adriano Teixeira de Souza (Jira)
[ https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi... ]
Adriano Teixeira de Souza commented on WFLY-14284:
--------------------------------------------------
[~ochaloup] I'd like to fix de documentation but in fact I don't know how is the right way to configure Wildfly without messages about deprecations.
At this time I just had changed the protocol and use the already documented workaround for authentication. On our instances we are still getting this messages.
The Developer Guide has only one referece to remote+http protocol and the remaining use always http-remoting. Have I provide a pull request change all of them without discern the context or you want to say only about the chapter that refer to remote outbound connection?
What would be the right way to use remote outbound without username, security-realm and protocol attributes?
> WildFly doesn't stop while waiting for PeriodicRecovery
> -------------------------------------------------------
>
> Key: WFLY-14284
> URL: https://issues.redhat.com/browse/WFLY-14284
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Transactions
> Affects Versions: 18.0.1.Final, 20.0.1.Final
> Reporter: Adriano Teixeira de Souza
> Assignee: Michael Musgrove
> Priority: Major
> Attachments: ejb-configs.sh, jboss-ejb-client.xml, server(transaction).log, thread-dump-stop-1.txt
>
>
> I'm testing wildfly 20.0.1 (and 21.0.2 was tested too) for replace our old version of Wildfly 10.
> it happens that frequently we have seen that the stop function of server does not work and we need to kill the process by manual operation on the OS.
> It sounds like a dead look.
> I attatch the thread dump on this.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (WFLY-14284) WildFly doesn't stop while waiting for PeriodicRecovery
by Ondrej Chaloupka (Jira)
[ https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi... ]
Ondrej Chaloupka edited comment on WFLY-14284 at 1/27/21 6:02 AM:
------------------------------------------------------------------
[~adrianots] True. My summary is that your issue routed us to two issues. The first is the trouble in http client (ie. WEJBHTTP-53) the second is the incorrect and insufficient documentation. Do you think you can create a new separate issue for the documentation (https://issues.redhat.com/browse/WFLY, component `Documentation`)?
For sure it will be more than welcome if you provide a PR to WFLY github repository that would fix the troubles you know about - the WFLY documentation is under https://github.com/wildfly/wildfly/tree/master/docs/src/main/asciidoc.
was (Author: ochaloup):
[~adrianots] True. My summary is that your issue routed us to two issues. The first is the trouble in http client (ie. WEJBHTTP-53) the second is the incorrect and insufficient documentation. Do you think you can create a new separate issue for the documentation?
For sure it will be more than welcome if you provide a PR to WFLY github repository that would fix the troubles you know about - the WFLY documentation is under https://github.com/wildfly/wildfly/tree/master/docs/src/main/asciidoc.
> WildFly doesn't stop while waiting for PeriodicRecovery
> -------------------------------------------------------
>
> Key: WFLY-14284
> URL: https://issues.redhat.com/browse/WFLY-14284
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Transactions
> Affects Versions: 18.0.1.Final, 20.0.1.Final
> Reporter: Adriano Teixeira de Souza
> Assignee: Michael Musgrove
> Priority: Major
> Attachments: ejb-configs.sh, jboss-ejb-client.xml, server(transaction).log, thread-dump-stop-1.txt
>
>
> I'm testing wildfly 20.0.1 (and 21.0.2 was tested too) for replace our old version of Wildfly 10.
> it happens that frequently we have seen that the stop function of server does not work and we need to kill the process by manual operation on the OS.
> It sounds like a dead look.
> I attatch the thread dump on this.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (WFLY-14284) WildFly doesn't stop while waiting for PeriodicRecovery
by Ondrej Chaloupka (Jira)
[ https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi... ]
Ondrej Chaloupka edited comment on WFLY-14284 at 1/27/21 6:02 AM:
------------------------------------------------------------------
[~adrianots] True. My summary is that your issue routed us to two issues. The first is the trouble in http client (ie. WEJBHTTP-53) the second is the incorrect and insufficient documentation. Do you think you can create a new separate issue for the documentation?
For sure it will be more than welcome if you provide a PR to WFLY github repository that would fix the troubles you know about - the WFLY documentation is under https://github.com/wildfly/wildfly/tree/master/docs/src/main/asciidoc.
was (Author: ochaloup):
[~adrianots] I truly agree with you. My summary is that your issue routed us to two issues. The first is the trouble in http client (ie. WEJBHTTP-53) the second is the incorrect and insufficient documentation. Do you think you can create a new separate issue for the documentation?
For sure it will be more than welcome if you provide a PR to WFLY github repository that would fix the troubles you know about - the WFLY documentation is under https://github.com/wildfly/wildfly/tree/master/docs/src/main/asciidoc.
> WildFly doesn't stop while waiting for PeriodicRecovery
> -------------------------------------------------------
>
> Key: WFLY-14284
> URL: https://issues.redhat.com/browse/WFLY-14284
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Transactions
> Affects Versions: 18.0.1.Final, 20.0.1.Final
> Reporter: Adriano Teixeira de Souza
> Assignee: Michael Musgrove
> Priority: Major
> Attachments: ejb-configs.sh, jboss-ejb-client.xml, server(transaction).log, thread-dump-stop-1.txt
>
>
> I'm testing wildfly 20.0.1 (and 21.0.2 was tested too) for replace our old version of Wildfly 10.
> it happens that frequently we have seen that the stop function of server does not work and we need to kill the process by manual operation on the OS.
> It sounds like a dead look.
> I attatch the thread dump on this.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months