[JBoss JIRA] (WFLY-12671) Memory Leak of PersistenceUnitMetadataImpl
by Robin Schimpf (Jira)
[ https://issues.jboss.org/browse/WFLY-12671?page=com.atlassian.jira.plugin... ]
Robin Schimpf commented on WFLY-12671:
--------------------------------------
I currently no longer think the leak of the PersistenceUnitMetadataImpl objects is caused by Wildfly rather than our handling with the Quartz scheduler since I only had instances left in the ApplicationShutdownHooks. I'm checking our application if we shutdown everything correctly.
> Memory Leak of PersistenceUnitMetadataImpl
> ------------------------------------------
>
> Key: WFLY-12671
> URL: https://issues.jboss.org/browse/WFLY-12671
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 17.0.1.Final
> Reporter: Robin Schimpf
> Assignee: Scott Marlow
> Priority: Major
> Attachments: Trying_to_catch_memory_leak_with_more_trace_logging.patch, jcaleakmarlow.txt, memory leak after 4 deployments.PNG, memory leak after 5 deployments.PNG, memory leak with directory scanner undeploy and deploy.PNG, persistence-unit-not-stopped.txt, persistence-unit-stopped.txt
>
>
> After updating from Wildfly 13 to Wildfly 17 we noticed a slowdown of our application after multiple deployments to the application server without restarting it between the deployments. Heapdumps are showing that after redeployment the number of {{PersistenceUnitMetadataImpl}} are growing (see screenshots).
> We are deploying 2 ear files and 2 war files. Only one ear has a database connection configured. We are using the bundeled hibernate version of Wildfly 17.
> The ear structure is like the following:
> {noformat}
> - app.ear
> |
> |- META-INF
> |
> |- lib
> | |
> | |- all dependencies
> |
> |- own jars and wars (e.g. jpa)
> {noformat}
> Since I failed to create a reproducing project for this behaviour I added some trace logging (Patch attached). The only difference I noticed was that sometimes the {{Stopping Persistence Unit}} logstatement is missing before the {{Stopped subdeployment}} logstatement.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-11722) Internal Server Error (500) when using directory-listing in FileHandler
by Ingo Weiss (Jira)
[ https://issues.jboss.org/browse/WFLY-11722?page=com.atlassian.jira.plugin... ]
Ingo Weiss resolved WFLY-11722.
-------------------------------
Resolution: Done
> Internal Server Error (500) when using directory-listing in FileHandler
> -----------------------------------------------------------------------
>
> Key: WFLY-11722
> URL: https://issues.jboss.org/browse/WFLY-11722
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 15.0.1.Final
> Reporter: Adam Krajcik
> Assignee: Ingo Weiss
> Priority: Minor
>
> When I added a bad symlink to the *welcome-content* and allowed *directory-listing* in the file handler of the *welcome-content* server returns Internal Server Error (500) when accessing the folder containing the bad symlink. However, no exception is logged in the output on WildFly.
> I also tried to use simple example application - _File Serving_ from [Undertow Examples|https://github.com/undertow-io/undertow/tree/master/examples] where I can see the following exception when accessing the directory with the bad symlink:
> {code}
> java.lang.RuntimeException: java.nio.file.NoSuchFileException: /home/akrajcik/Pictures/pictures
> at io.undertow.server.handlers.resource.PathResource.getLastModified(PathResource.java:62)
> at io.undertow.server.handlers.resource.DirectoryUtils.renderDirectoryListing(DirectoryUtils.java:139)
> at io.undertow.server.handlers.resource.DirectoryUtils.renderDirectoryListing(DirectoryUtils.java:162)
> at io.undertow.server.handlers.resource.ResourceHandler$1.handleRequest(ResourceHandler.java:233)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:364)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.lang.Thread.run(Thread.java:811)
> Caused by: java.nio.file.NoSuchFileException: /home/akrajcik/Pictures/pictures
> at sun.nio.fs.UnixException.translateToIOException(UnixException.java:98)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:114)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:119)
> at sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.java:67)
> at sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:156)
> at sun.nio.fs.LinuxFileSystemProvider.readAttributes(LinuxFileSystemProvider.java:111)
> at java.nio.file.Files.readAttributes(Files.java:1748)
> at java.nio.file.Files.getLastModifiedTime(Files.java:2277)
> at io.undertow.server.handlers.resource.PathResource.getLastModified(PathResource.java:60)
> ... 8 more
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12689) WAR deployment fails due to NPE when both MBean and persistence-unit are packaged
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-12689?page=com.atlassian.jira.plugin... ]
Radoslav Husar reassigned WFLY-12689:
-------------------------------------
Assignee: Masafumi Miura (was: Kabir Khan)
> WAR deployment fails due to NPE when both MBean and persistence-unit are packaged
> ---------------------------------------------------------------------------------
>
> Key: WFLY-12689
> URL: https://issues.jboss.org/browse/WFLY-12689
> Project: WildFly
> Issue Type: Bug
> Components: JMX, JPA / Hibernate, Server
> Affects Versions: 18.0.0.Final
> Reporter: Masafumi Miura
> Assignee: Masafumi Miura
> Priority: Major
>
> When a web application contains both MBean (jboss-service.xml) and persistence-unit (persistence.xml), the WAR deployment fails due to the following NullPointerException:
> {code}
> 11:51:03,041 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."helloworld-mbean-webapp.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."helloworld-mbean-webapp.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "helloworld-mbean-webapp.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> 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)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.service.MBeanServices.<init>(MBeanServices.java:107)
> at org.jboss.as.service.ParsedServiceDeploymentProcessor.addServices(ParsedServiceDeploymentProcessor.java:124)
> at org.jboss.as.service.ParsedServiceDeploymentProcessor.deploy(ParsedServiceDeploymentProcessor.java:109)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
> ... 8 more
> ...(snip)...
> 11:51:03,687 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "helloworld-mbean-webapp.war")]) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"helloworld-mbean-webapp.war\".INSTALL" => "WFLYSRV0153: Failed to process phase INSTALL of deployment \"helloworld-mbean-webapp.war\"
> Caused by: java.lang.NullPointerException"},
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.deployment.unit.\"helloworld-mbean-webapp.war\".WeldStartService",
> "jboss.deployment.unit.\"helloworld-mbean-webapp.war\".beanmanager"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.deployment.unit.\"helloworld-mbean-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"helloworld-mbean-webapp.war\".WeldStartService, jboss.deployment.unit.\"helloworld-mbean-webapp.war\".beanmanager]",
> "jboss.deployment.unit.\"helloworld-mbean-webapp.war\".batch.artifact.factory is missing [jboss.deployment.unit.\"helloworld-mbean-webapp.war\".beanmanager]"
> ]
> }
> {code}
> This NPE happens because [WebNonTxEmCloserAction#dependencies()|https://github.com/wildfly/wildfly/...] returns null. It should return Collections.emptySet() instead of null.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (DROOLS-4658) Executable model compilation fails with ClassCastException when using accumulate and additional constraint
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-4658?page=com.atlassian.jira.plugi... ]
Mario Fusco reassigned DROOLS-4658:
-----------------------------------
Assignee: Luca Molteni (was: Mario Fusco)
> Executable model compilation fails with ClassCastException when using accumulate and additional constraint
> ----------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-4658
> URL: https://issues.jboss.org/browse/DROOLS-4658
> Project: Drools
> Issue Type: Bug
> Components: core engine, executable model
> Affects Versions: 7.28.0.Final
> Reporter: Martin Weiler
> Assignee: Luca Molteni
> Priority: Major
> Labels: support
>
> A rule containing the following constraint:
> {noformat}
> when
> $customer : Customer( code == "RHT" )
> $max1 : Number() from accumulate(
> StockTick( company == $customer.code
> , $time : dueDate);
> max($time.getTime().getTime()))
> {noformat}
> fails with a ClassCastException when building with the executable model:
> {noformat}
> java.lang.ClassCastException: com.github.javaparser.ast.expr.NameExpr cannot be cast to com.github.javaparser.ast.expr.LambdaExpr
> at org.drools.modelcompiler.builder.generator.visitor.accumulate.AccumulateVisitorPatternDSL.lambda$composeTwoBindings$4(AccumulateVisitorPatternDSL.java:67)
> at java.util.Optional.ifPresent(Optional.java:159)
> at org.drools.modelcompiler.builder.generator.visitor.accumulate.AccumulateVisitorPatternDSL.composeTwoBindings(AccumulateVisitorPatternDSL.java:64)
> at org.drools.modelcompiler.builder.generator.visitor.accumulate.AccumulateVisitorPatternDSL.lambda$null$1(AccumulateVisitorPatternDSL.java:53)
> at java.util.Optional.ifPresent(Optional.java:159)
> at org.drools.modelcompiler.builder.generator.visitor.accumulate.AccumulateVisitorPatternDSL.lambda$processNewBinding$3(AccumulateVisitorPatternDSL.java:53)
> at java.util.Optional.ifPresent(Optional.java:159)
> at org.drools.modelcompiler.builder.generator.visitor.accumulate.AccumulateVisitorPatternDSL.processNewBinding(AccumulateVisitorPatternDSL.java:44)
> at org.drools.modelcompiler.builder.generator.visitor.accumulate.AccumulateVisitor.classicAccumulate(AccumulateVisitor.java:129)
> at org.drools.modelcompiler.builder.generator.visitor.accumulate.AccumulateVisitor.visit(AccumulateVisitor.java:107)
> at org.drools.modelcompiler.builder.generator.visitor.ModelGeneratorVisitor.visit(ModelGeneratorVisitor.java:122)
> at org.drools.compiler.lang.descr.PatternDescr.accept(PatternDescr.java:272)
> at org.drools.modelcompiler.builder.generator.visitor.AndVisitor.visit(AndVisitor.java:29)
> at org.drools.modelcompiler.builder.generator.visitor.ModelGeneratorVisitor.visit(ModelGeneratorVisitor.java:69)
> at org.drools.modelcompiler.builder.generator.ModelGenerator.processRule(ModelGenerator.java:176)
> at org.drools.modelcompiler.builder.generator.ModelGenerator.generateModel(ModelGenerator.java:156)
> at org.drools.modelcompiler.builder.ModelBuilderImpl.compileKnowledgePackages(ModelBuilderImpl.java:176)
> at org.drools.modelcompiler.builder.ModelBuilderImpl.buildRules(ModelBuilderImpl.java:121)
> at org.drools.modelcompiler.builder.ModelBuilderImpl.buildPackages(ModelBuilderImpl.java:71)
> at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:108)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12689) WAR deployment fails due to NPE when both MBean and persistence-unit are packaged
by Masafumi Miura (Jira)
[ https://issues.jboss.org/browse/WFLY-12689?page=com.atlassian.jira.plugin... ]
Masafumi Miura updated WFLY-12689:
----------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/12727
> WAR deployment fails due to NPE when both MBean and persistence-unit are packaged
> ---------------------------------------------------------------------------------
>
> Key: WFLY-12689
> URL: https://issues.jboss.org/browse/WFLY-12689
> Project: WildFly
> Issue Type: Bug
> Components: JMX, JPA / Hibernate, Server
> Affects Versions: 18.0.0.Final
> Reporter: Masafumi Miura
> Assignee: Kabir Khan
> Priority: Major
>
> When a web application contains both MBean (jboss-service.xml) and persistence-unit (persistence.xml), the WAR deployment fails due to the following NullPointerException:
> {code}
> 11:51:03,041 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."helloworld-mbean-webapp.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."helloworld-mbean-webapp.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "helloworld-mbean-webapp.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> 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)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.service.MBeanServices.<init>(MBeanServices.java:107)
> at org.jboss.as.service.ParsedServiceDeploymentProcessor.addServices(ParsedServiceDeploymentProcessor.java:124)
> at org.jboss.as.service.ParsedServiceDeploymentProcessor.deploy(ParsedServiceDeploymentProcessor.java:109)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
> ... 8 more
> ...(snip)...
> 11:51:03,687 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "helloworld-mbean-webapp.war")]) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"helloworld-mbean-webapp.war\".INSTALL" => "WFLYSRV0153: Failed to process phase INSTALL of deployment \"helloworld-mbean-webapp.war\"
> Caused by: java.lang.NullPointerException"},
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.deployment.unit.\"helloworld-mbean-webapp.war\".WeldStartService",
> "jboss.deployment.unit.\"helloworld-mbean-webapp.war\".beanmanager"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.deployment.unit.\"helloworld-mbean-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"helloworld-mbean-webapp.war\".WeldStartService, jboss.deployment.unit.\"helloworld-mbean-webapp.war\".beanmanager]",
> "jboss.deployment.unit.\"helloworld-mbean-webapp.war\".batch.artifact.factory is missing [jboss.deployment.unit.\"helloworld-mbean-webapp.war\".beanmanager]"
> ]
> }
> {code}
> This NPE happens because [WebNonTxEmCloserAction#dependencies()|https://github.com/wildfly/wildfly/...] returns null. It should return Collections.emptySet() instead of null.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12689) WAR deployment fails due to NPE when both MBean and persistence-unit are packaged
by Masafumi Miura (Jira)
Masafumi Miura created WFLY-12689:
-------------------------------------
Summary: WAR deployment fails due to NPE when both MBean and persistence-unit are packaged
Key: WFLY-12689
URL: https://issues.jboss.org/browse/WFLY-12689
Project: WildFly
Issue Type: Bug
Components: JMX, JPA / Hibernate, Server
Affects Versions: 18.0.0.Final
Reporter: Masafumi Miura
Assignee: Kabir Khan
When a web application contains both MBean (jboss-service.xml) and persistence-unit (persistence.xml), the WAR deployment fails due to the following NullPointerException:
{code}
11:51:03,041 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."helloworld-mbean-webapp.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."helloworld-mbean-webapp.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "helloworld-mbean-webapp.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
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)
Caused by: java.lang.NullPointerException
at org.jboss.as.service.MBeanServices.<init>(MBeanServices.java:107)
at org.jboss.as.service.ParsedServiceDeploymentProcessor.addServices(ParsedServiceDeploymentProcessor.java:124)
at org.jboss.as.service.ParsedServiceDeploymentProcessor.deploy(ParsedServiceDeploymentProcessor.java:109)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
... 8 more
...(snip)...
11:51:03,687 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "helloworld-mbean-webapp.war")]) - failure description: {
"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"helloworld-mbean-webapp.war\".INSTALL" => "WFLYSRV0153: Failed to process phase INSTALL of deployment \"helloworld-mbean-webapp.war\"
Caused by: java.lang.NullPointerException"},
"WFLYCTL0412: Required services that are not installed:" => [
"jboss.deployment.unit.\"helloworld-mbean-webapp.war\".WeldStartService",
"jboss.deployment.unit.\"helloworld-mbean-webapp.war\".beanmanager"
],
"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"jboss.deployment.unit.\"helloworld-mbean-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"helloworld-mbean-webapp.war\".WeldStartService, jboss.deployment.unit.\"helloworld-mbean-webapp.war\".beanmanager]",
"jboss.deployment.unit.\"helloworld-mbean-webapp.war\".batch.artifact.factory is missing [jboss.deployment.unit.\"helloworld-mbean-webapp.war\".beanmanager]"
]
}
{code}
This NPE happens because [WebNonTxEmCloserAction#dependencies()|https://github.com/wildfly/wildfly/...] returns null. It should return Collections.emptySet() instead of null.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12688) Error when maintaining Datasources & Drivers via Console
by Norito Agetsuma (Jira)
Norito Agetsuma created WFLY-12688:
--------------------------------------
Summary: Error when maintaining Datasources & Drivers via Console
Key: WFLY-12688
URL: https://issues.jboss.org/browse/WFLY-12688
Project: WildFly
Issue Type: Bug
Components: Web Console
Affects Versions: 18.0.0.Final
Environment: Apache Maven 3.6.0
Maven home: /usr/share/maven
Java version: 13, vendor: Ubuntu, runtime: /usr/lib/jvm/java-13-openjdk-amd64
Default locale: de_DE, platform encoding: UTF-8
OS name: "linux", version: "5.0.0-31-generic", arch: "amd64", family: "unix"
Reporter: Norito Agetsuma
Assignee: Harald Pehl
When opening 'Datasources & Drivers -> JDBC Drivers' an message is popping up saying that an internal error occured with Details "newValue is null"
After clicking the "+" to add a JDBC Driver I can add the JDBC driver indeed but the drivers are not showing up in the console.
When opening 'Datasources & Drivers -> Datasources' the datasources are listed correctly. But when trying to add another Datasource the same internal message is popping up and it ist not possible to add the Datasouce via Console
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12655) Exception with web.xml url-pattern
by Flavia Rainone (Jira)
[ https://issues.jboss.org/browse/WFLY-12655?page=com.atlassian.jira.plugin... ]
Flavia Rainone commented on WFLY-12655:
---------------------------------------
I created a issue for this: https://github.com/eclipse-ee4j/jacc/issues/56
> Exception with web.xml url-pattern
> ----------------------------------
>
> Key: WFLY-12655
> URL: https://issues.jboss.org/browse/WFLY-12655
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 18.0.0.Final
> Reporter: Frank Heldt
> Assignee: Flavia Rainone
> Priority: Blocker
> Fix For: 19.0.0.Beta1
>
>
> Defining and securing 2 folders in a war with similar names given this Exception on deployment:
> {code}
> 12:38:37,994 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."java-web-project.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."java-web-project.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service
> at org.jboss.as.security@18.0.0.Final//org.jboss.as.security.service.JaccService.start(JaccService.java:107)
> 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:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.IllegalArgumentException: Invalid prefix pattern in URLPatternList
> at javax.security.jacc.api@2.0.0.Final//javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:308)
> at javax.security.jacc.api(a)2.0.0.Final//javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79)
> at javax.security.jacc.api(a)2.0.0.Final//javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160)
> at org.wildfly.extension.undertow@18.0.0.Final//org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:303)
> at org.wildfly.extension.undertow@18.0.0.Final//org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64)
> at org.jboss.as.security@18.0.0.Final//org.jboss.as.security.service.JaccService.start(JaccService.java:86)
> ... 8 more
> {code}
> This is the corresponding part of the web.xml:
> {code}
> <security-constraint>
> <web-resource-collection>
> <web-resource-name>Area</web-resource-name>
> <url-pattern>/area/*</url-pattern>
> </web-resource-collection>
> <auth-constraint>
> <role-name>role1</role-name>
> <role-name>role2</role-name>
> </auth-constraint>
> <user-data-constraint>
> <transport-guarantee>CONFIDENTIAL</transport-guarantee>
> </user-data-constraint>
> </security-constraint>
> <security-constraint>
> <web-resource-collection>
> <web-resource-name>Area 51</web-resource-name>
> <url-pattern>/area51/*</url-pattern>
> </web-resource-collection>
> <auth-constraint>
> <role-name>role1</role-name>
> </auth-constraint>
> <user-data-constraint>
> <transport-guarantee>CONFIDENTIAL</transport-guarantee>
> </user-data-constraint>
> </security-constraint>
> {code}
> Looks like this only happens when the url-pattern starts with the same characters (eg /area/* and /area51/*).
> The same war under WildFly 17.0.1 works as expected.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months