[JBoss JIRA] (WFLY-9082) Unignore test for WFLY-8316
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-9082?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas updated WFLY-9082:
-------------------------------
Description: Unignore {{org.jboss.as.test.integration.security.aselytron.SecurityDomainAsElytronSecurityRealmTestCase.testAssignRoleFromMappingModule}} in AS TS. (was: Unignore {{org.jboss.as.test.integration.security.aselytron.SecurityDomainAsElytronSecurityRealmTestCase}} in AS TS.)
> Unignore test for WFLY-8316
> ---------------------------
>
> Key: WFLY-9082
> URL: https://issues.jboss.org/browse/WFLY-9082
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Ondrej Lukas
> Assignee: Ondrej Lukas
>
> Unignore {{org.jboss.as.test.integration.security.aselytron.SecurityDomainAsElytronSecurityRealmTestCase.testAssignRoleFromMappingModule}} in AS TS.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (DROOLS-1652) Add an entry point on the kie-server to deploy a DMN files as a service
by Maciej Swiderski (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1652?page=com.atlassian.jira.plugi... ]
Maciej Swiderski commented on DROOLS-1652:
------------------------------------------
I see two approaches to this:
- if we consider it as demo only I would opt for having this to be as separate extension - so it can be deployed outside of the official distribution that way we avoid potential issues/bug reports that it won't survive server restarts
- make it all the way down to survive the restarts by saving given kjar into maven repo locally and then simply register it as any other container.
Not sure what is preferred as I don't know the origin of this request....
> Add an entry point on the kie-server to deploy a DMN files as a service
> -----------------------------------------------------------------------
>
> Key: DROOLS-1652
> URL: https://issues.jboss.org/browse/DROOLS-1652
> Project: Drools
> Issue Type: Feature Request
> Components: dmn engine, kie server
> Affects Versions: 7.1.0.Beta3
> Reporter: Edson Tirelli
> Assignee: Duncan Doyle
>
> Add an end point on the kie-server to deploy a DMN xml file directly as a service without the need for a kjar.
> In other words, the end point would accept a POST with a DMN xml file as a payload, it would internally build a kjar in memory and deploy it as a kie-container.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9082) Unignore test for WFLY-8316
by Ondrej Lukas (JIRA)
Ondrej Lukas created WFLY-9082:
----------------------------------
Summary: Unignore test for WFLY-8316
Key: WFLY-9082
URL: https://issues.jboss.org/browse/WFLY-9082
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: Ondrej Lukas
Unignore {{org.jboss.as.test.integration.security.aselytron.SecurityDomainAsElytronSecurityRealmTestCase}} in AS TS.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9081) Support ServletContainerInitializer placed on WARs
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-9081?page=com.atlassian.jira.plugin.... ]
Stuart Douglas moved UNDERTOW-1130 to WFLY-9081:
------------------------------------------------
Project: WildFly (was: Undertow)
Key: WFLY-9081 (was: UNDERTOW-1130)
> Support ServletContainerInitializer placed on WARs
> --------------------------------------------------
>
> Key: WFLY-9081
> URL: https://issues.jboss.org/browse/WFLY-9081
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Guillermo González de Agüero
> Assignee: Stuart Douglas
>
> The Servlet spec only talks about the presence of ServletContainerInitializer's within JAR files bundled on the WAR. It says nothing about what to do when found on the WAR and Undertow is ignored them right now, which is spec complaint.
> However, WildFly has the only Servlet container I'm aware of that ignores that classes, having tested Payara, WebLogic,WebSphere Liberty, Jetty, Tomcat and Resin.
> It would be good to support them on Undertow too.
> I've also opened an issue on the Servlet spec repository, so this can be clarified for future versions of the document: https://github.com/javaee/servlet-spec/issues/179
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (DROOLS-1652) Add an entry point on the kie-server to deploy a DMN files as a service
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1652?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-1652:
---------------------------------------
Maciej makes good points, I think this should really only be used for stateless DMN services for dynamic environments. I don't think we would be able to preserve it between restarts though, so it would really be a "demo" feature.
> Add an entry point on the kie-server to deploy a DMN files as a service
> -----------------------------------------------------------------------
>
> Key: DROOLS-1652
> URL: https://issues.jboss.org/browse/DROOLS-1652
> Project: Drools
> Issue Type: Feature Request
> Components: dmn engine, kie server
> Affects Versions: 7.1.0.Beta3
> Reporter: Edson Tirelli
> Assignee: Duncan Doyle
>
> Add an end point on the kie-server to deploy a DMN xml file directly as a service without the need for a kjar.
> In other words, the end point would accept a POST with a DMN xml file as a payload, it would internally build a kjar in memory and deploy it as a kie-container.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (DROOLS-1655) Memory leak for session object reference even after disposing it
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1655?page=com.atlassian.jira.plugi... ]
Edson Tirelli reassigned DROOLS-1655:
-------------------------------------
Assignee: Mario Fusco (was: Edson Tirelli)
> Memory leak for session object reference even after disposing it
> ----------------------------------------------------------------
>
> Key: DROOLS-1655
> URL: https://issues.jboss.org/browse/DROOLS-1655
> Project: Drools
> Issue Type: Feature Request
> Affects Versions: 6.5.0.Final
> Reporter: Shailesh T
> Assignee: Mario Fusco
> Priority: Critical
>
> Even after closing session, the objects into it are not getting released. This is critical problem when ruls are run on long running server with intermittent use. With huge
> number of inserted objects it leaks a considerable memory.
> Steps to reproduce:
> 1) Create a stateful session.
> 2) Insert huge number of objects into the session.
> 3) Fire rules.
> 4) Close session with dispose() call provided.
> 5) Run GC process.
> 5) If memory is measured and heap dump is taken it shows that the objects being inserted are still not garbage collected.
> Observations:
> When walked through heap dump it GC root path looks like
> this - value: myPackage.MyObject #1
> <- object - class: org.drools.core.common.DefaultFactHandle, value: myPackage.MyObject #1
> <- value - class: org.drools.core.util.ObjectHashMap$ObjectEntry, value: org.drools.core.common.DefaultFactHandle #29323
> <- [49547] - class: org.drools.core.util.Entry[], value: org.drools.core.util.ObjectHashMap$ObjectEntry #103210
> <- table - class: org.drools.core.util.ObjectHashMap, value: org.drools.core.util.Entry[] #8
> <- equalityMap - class: org.drools.core.common.ClassAwareObjectStore, value: org.drools.core.util.ObjectHashMap #7
> <- objectStore - class: org.drools.core.common.NamedEntryPoint, value: org.drools.core.common.ClassAwareObjectStore #1
> <- defaultEntryPoint - class: org.drools.core.impl.StatefulKnowledgeSessionImpl, value: org.drools.core.common.NamedEntryPoint #1
> <- value - class: java.util.concurrent.ConcurrentHashMap$HashEntry, value: org.drools.core.impl.StatefulKnowledgeSessionImpl #1
> <- [1] - class: java.util.concurrent.ConcurrentHashMap$HashEntry[], value: java.util.concurrent.ConcurrentHashMap$HashEntry #20801
> <- table - class: java.util.concurrent.ConcurrentHashMap$Segment, value: java.util.concurrent.ConcurrentHashMap$HashEntry[] #465
> <- [14] - class: java.util.concurrent.ConcurrentHashMap$Segment[], value: java.util.concurrent.ConcurrentHashMap$Segment #469
> <- segments - class: java.util.concurrent.ConcurrentHashMap, value: java.util.concurrent.ConcurrentHashMap$Segment[] #78
> <- kSessions - class: org.drools.compiler.kie.builder.impl.KieContainerImpl, value: java.util.concurrent.ConcurrentHashMap #78
> <- compiledRB - class: myPackage.RBInfo, value: org.drools.compiler.kie.builder.impl.KieContainerImpl #1
> On further investigations it was found that when new session is create, KieContainerImpl class keeps its reference into 'kSessions' Map. But when session is closed this reference is not released(though such reference is released from KnowledgeBaseImpl).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ELY-1282) Regression against ER1, When HTTP mechanism misconfigured, then deployment doesn't fail anymore
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/ELY-1282?page=com.atlassian.jira.plugin.s... ]
Farah Juma reassigned ELY-1282:
-------------------------------
Assignee: Farah Juma (was: Darran Lofthouse)
> Regression against ER1, When HTTP mechanism misconfigured, then deployment doesn't fail anymore
> -----------------------------------------------------------------------------------------------
>
> Key: ELY-1282
> URL: https://issues.jboss.org/browse/ELY-1282
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Martin Choma
> Assignee: Farah Juma
> Priority: Blocker
>
> When only one disabled mechanism is configured for undertow deployment
> {code}
> <http-authentication-factory name="elytron-http-authn-factory" http-server-mechanism-factory="wrongConfigurableHttpServerMechanismFactory" security-domain="ApplicationDomain">
> <mechanism-configuration>
> <mechanism mechanism-name="BASIC">
> <mechanism-realm realm-name="Some realm"/>
> </mechanism>
> </mechanism-configuration>
> </http-authentication-factory>
> <configurable-http-server-mechanism-factory name="wrongConfigurableHttpServerMechanismFactory" http-server-mechanism-factory="aggregateHttpServerMechanismFactory">
> <filters>
> <filter pattern="BASIC" enabling="false"/>
> </filters>
> </configurable-http-server-mechanism-factory>
> <application-security-domains>
> <application-security-domain name="ApplicationDomain" http-authentication-factory="elytron-http-authn-factory"/>
> </application-security-domains>
> {code}
> And in web.xml is configured BASIC authentication
> {code}
> <login-config>
> <auth-method>BASIC</auth-method>
> <realm-name>Test realm</realm-name>
> </login-config>
> {code}
> Till ER1 such configuration leads to deployment failure and message "There are no mechanisms available from the HttpAuthenticationFactory"
> {code}
> 07:48:46,765 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "elytron-app.war" (runtime-name: "elytron-app.war")
> 07:48:46,883 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.6.Final-redhat-1
> 07:48:46,887 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
> 07:48:46,984 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBossWS 5.1.8.Final-redhat-1 (Apache CXF 3.1.11.redhat-1)
> 07:48:47,333 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 63) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./elytron-app: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./elytron-app: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:84)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:241)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:99)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81)
> ... 6 more
> Caused by: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
> at org.wildfly.extension.undertow.ApplicationSecurityDomainDefinition$ApplicationSecurityDomainService.initialSecurityHandler(ApplicationSecurityDomainDefinition.java:460)
> at org.wildfly.extension.undertow.ApplicationSecurityDomainDefinition$ApplicationSecurityDomainService.lambda$applyElytronSecurity$2(ApplicationSecurityDomainDefinition.java:422)
> at io.undertow.servlet.core.DeploymentManagerImpl.setupSecurityHandlers(DeploymentManagerImpl.java:415)
> at io.undertow.servlet.core.DeploymentManagerImpl.access$600(DeploymentManagerImpl.java:119)
> at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:211)
> at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:174)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:239)
> ... 8 more
> 07:48:47,341 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "elytron-app.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.undertow.deployment.default-server.default-host./elytron-app" => "java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
> Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
> Caused by: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory."}}
> 07:48:47,370 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "elytron-app.war" (runtime-name : "elytron-app.war")
> 07:48:47,373 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.undertow.deployment.default-server.default-host./elytron-app: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
> {code}
> In ER2 application is deployed succesfully
> {code}
> 07:50:31,041 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "elytron-app.war" (runtime-name: "elytron-app.war")
> 07:50:31,136 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
> 07:50:31,160 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-7) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.7.Final-redhat-1
> 07:50:31,216 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBossWS 5.1.8.Final-redhat-1 (Apache CXF 3.1.11.redhat-1)
> 07:50:31,661 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0021: Registered web context: '/elytron-app' for server 'default-server'
> 07:50:31,683 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "elytron-app.war" (runtime-name : "elytron-app.war")
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFCORE-3063) Regression against ER1, When HTTP mechanism misconfigured, then deployment doesn't fail anymore
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3063?page=com.atlassian.jira.plugi... ]
Farah Juma moved ELY-1282 to WFCORE-3063:
-----------------------------------------
Project: WildFly Core (was: WildFly Elytron)
Key: WFCORE-3063 (was: ELY-1282)
> Regression against ER1, When HTTP mechanism misconfigured, then deployment doesn't fail anymore
> -----------------------------------------------------------------------------------------------
>
> Key: WFCORE-3063
> URL: https://issues.jboss.org/browse/WFCORE-3063
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Martin Choma
> Assignee: Farah Juma
> Priority: Blocker
>
> When only one disabled mechanism is configured for undertow deployment
> {code}
> <http-authentication-factory name="elytron-http-authn-factory" http-server-mechanism-factory="wrongConfigurableHttpServerMechanismFactory" security-domain="ApplicationDomain">
> <mechanism-configuration>
> <mechanism mechanism-name="BASIC">
> <mechanism-realm realm-name="Some realm"/>
> </mechanism>
> </mechanism-configuration>
> </http-authentication-factory>
> <configurable-http-server-mechanism-factory name="wrongConfigurableHttpServerMechanismFactory" http-server-mechanism-factory="aggregateHttpServerMechanismFactory">
> <filters>
> <filter pattern="BASIC" enabling="false"/>
> </filters>
> </configurable-http-server-mechanism-factory>
> <application-security-domains>
> <application-security-domain name="ApplicationDomain" http-authentication-factory="elytron-http-authn-factory"/>
> </application-security-domains>
> {code}
> And in web.xml is configured BASIC authentication
> {code}
> <login-config>
> <auth-method>BASIC</auth-method>
> <realm-name>Test realm</realm-name>
> </login-config>
> {code}
> Till ER1 such configuration leads to deployment failure and message "There are no mechanisms available from the HttpAuthenticationFactory"
> {code}
> 07:48:46,765 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "elytron-app.war" (runtime-name: "elytron-app.war")
> 07:48:46,883 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.6.Final-redhat-1
> 07:48:46,887 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
> 07:48:46,984 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBossWS 5.1.8.Final-redhat-1 (Apache CXF 3.1.11.redhat-1)
> 07:48:47,333 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 63) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./elytron-app: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./elytron-app: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:84)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:241)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:99)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81)
> ... 6 more
> Caused by: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
> at org.wildfly.extension.undertow.ApplicationSecurityDomainDefinition$ApplicationSecurityDomainService.initialSecurityHandler(ApplicationSecurityDomainDefinition.java:460)
> at org.wildfly.extension.undertow.ApplicationSecurityDomainDefinition$ApplicationSecurityDomainService.lambda$applyElytronSecurity$2(ApplicationSecurityDomainDefinition.java:422)
> at io.undertow.servlet.core.DeploymentManagerImpl.setupSecurityHandlers(DeploymentManagerImpl.java:415)
> at io.undertow.servlet.core.DeploymentManagerImpl.access$600(DeploymentManagerImpl.java:119)
> at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:211)
> at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:174)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:239)
> ... 8 more
> 07:48:47,341 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "elytron-app.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.undertow.deployment.default-server.default-host./elytron-app" => "java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
> Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
> Caused by: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory."}}
> 07:48:47,370 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "elytron-app.war" (runtime-name : "elytron-app.war")
> 07:48:47,373 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.undertow.deployment.default-server.default-host./elytron-app: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
> {code}
> In ER2 application is deployed succesfully
> {code}
> 07:50:31,041 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "elytron-app.war" (runtime-name: "elytron-app.war")
> 07:50:31,136 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
> 07:50:31,160 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-7) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.7.Final-redhat-1
> 07:50:31,216 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBossWS 5.1.8.Final-redhat-1 (Apache CXF 3.1.11.redhat-1)
> 07:50:31,661 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0021: Registered web context: '/elytron-app' for server 'default-server'
> 07:50:31,683 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "elytron-app.war" (runtime-name : "elytron-app.war")
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months