[JBoss JIRA] (WFLY-11492) Quickstart http-custom-mechanism: documentation step fails
by Eduardo Martins (Jira)
[ https://issues.redhat.com/browse/WFLY-11492?page=com.atlassian.jira.plugi... ]
Eduardo Martins updated WFLY-11492:
-----------------------------------
Component/s: Quickstarts
> Quickstart http-custom-mechanism: documentation step fails
> ----------------------------------------------------------
>
> Key: WFLY-11492
> URL: https://issues.redhat.com/browse/WFLY-11492
> Project: WildFly
> Issue Type: Bug
> Components: Documentation, Quickstarts, Security
> Reporter: Alan Hantke
> Assignee: Sonia Zaldana
> Priority: Major
> Fix For: 21.0.0.Beta1
>
>
> Step #3, entitled *Configure the Application Security Domain* has the developer executing the following CLI command:
> {code:java}
> $ {jbossHomeName}/bin/jboss-cli.sh --connect --file=configure-security-domain.cli
> {code}
> However, this results in the following error:
> {code:java}
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error):
> WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:
> Step: step-1
> Operation: /subsystem=undertow/application-security-domain=other:add(http-authentication-factory=application-http-authentication)
> Failure: WFLYCTL0369: Required capabilities are not available:
> org.wildfly.security.http-authentication-factory.application-http-authentication; Possible registration points for this capability:
> /subsystem=elytron/http-authentication-factory=*
> {code}
> I am by no means an expert on this, but in looking at the standalone.xml file, I think that there needs to be a mate for the inserted *application-http-authentication*. I have attempted to continue without this changes installed by the CLI, but I am unable to execute the webapp even after providing the correct user/pass in the BASIC AUTH.
> I have verified that the same problem-causing syntax exists on the quickstart 'master', although I have been using branch '14.x' because neither 15.x nor 'master' would build when I execute 'mvn clean build'. Finally, the I encounter the problem with fresh installs of WildFly versions 10.1.0 and 14.0.
> Please change change the project if I have categorized the ticket incorrectly.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (WFLY-13790) Memory leak caused by org.eclipse.yasson.internal.JsonBinding
by Ahcene Kessal (Jira)
[ https://issues.redhat.com/browse/WFLY-13790?page=com.atlassian.jira.plugi... ]
Ahcene Kessal edited comment on WFLY-13790 at 9/22/20 7:00 AM:
---------------------------------------------------------------
*Attachments*:
||Attached artifacts||Description||
|app.zip|app used to trigger the memory leak|
|WFLY-13790-0.0.1-SNAPSHOT.war|built package from "app.zip"|
|wildfly-20.0.1.Final.PNG|memory graph from wildfly-20.0.1.Final|
|wildfly-20.0.1.Final+patch.PNG|memory graph from "wildfly-20.0.1.Final + patch"|
*Test description:*
Start application server "wildfly-20.0.1.Final" and "jconsole.exe" to record memory usage.
# deploy WFLY-13790-0.0.1-SNAPSHOT.war
# on browser get: [http://localhost:8080/rest/get-books]
# un-deploy WFLY-13790-0.0.1-SNAPSHOT.war
# re-deploy WFLY-13790-0.0.1-SNAPSHOT.war
# on browser get: [http://localhost:8080/rest/get-books]
repeat the above steps again and again
*note*: for deploying/un-deploying operations I used "jboss-cli.bat":
{code:java}
[standalone@localhost:9990 /] /deployment=WFLY-13790-0.0.1-SNAPSHOT.war:undeploy()
[standalone@localhost:9990 /] /deployment=WFLY-13790-0.0.1-SNAPSHOT.war:deploy {code}
*Test results:*
# with wildfly-20.0.1.Final, the JVM throws _*OutOfMemoryError*_ after 6 iterations
# I swapped "resteasy-json-binding-provider-3.12.1.Final.jar" for the one built from [https://github.com/rsearls/Resteasy/commit/55a0c2f6b3dc9b396513ec615cd49b... I repeated the test. The memory leak does not occur anymore, I repeated the test 15 times and then I stopped.
The memory graphs are attached.
The patch resolves the issue and this case can be closed.
was (Author: ahcenek):
*Attachments*:
||Attached artifacts||Description||
|app.zip|app used to trigger the memory leak|
|WFLY-13790-0.0.1-SNAPSHOT.war|built package from "app.zip"|
|wildfly-20.0.1.Final.PNG|memory graph from wildfly-20.0.1.Final|
|wildfly-20.0.1.Final+patch.PNG|memory graph from "wildfly-20.0.1.Final + patch"|
*Test description:*
Start application server "wildfly-20.0.1.Final" and "jconsole.exe" to record memory usage.
# deploy WFLY-13790-0.0.1-SNAPSHOT.war
# on browser get: [http://localhost:8080/rest/get-books]
# un-deploy WFLY-13790-0.0.1-SNAPSHOT.war
# re-deploy WFLY-13790-0.0.1-SNAPSHOT.war
# on browser get: [http://localhost:8080/rest/get-books]
repeat the above steps again and again
*note*: for deploying/un-deploying operations I used "jboss-cli.bat":
{code:java}
[standalone@localhost:9990 /] /deployment=WFLY-13790-0.0.1-SNAPSHOT.war:undeploy()
[standalone@localhost:9990 /] /deployment=WFLY-13790-0.0.1-SNAPSHOT.war:deploy {code}
*Test results:*
# with wildfly-20.0.1.Final, the JVM throws _*OutOfMemoryError*_ after 6 iterations
# I swapped "resteasy-json-binding-provider-3.12.1.Final.jar" for the one built from [https://github.com/rsearls/Resteasy/commit/55a0c2f6b3dc9b396513ec615cd49b... I repeated the test. The memory leak does not occur anymore, I repeated the test 15 times and then I stopped.
The memory graphs are attached.
The patch resolves the issue and this case can be closed.
> Memory leak caused by org.eclipse.yasson.internal.JsonBinding
> -------------------------------------------------------------
>
> Key: WFLY-13790
> URL: https://issues.redhat.com/browse/WFLY-13790
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 20.0.1.Final
> Reporter: Ahcene Kessal
> Assignee: r searls
> Priority: Major
> Attachments: WFLY-13790-0.0.1-SNAPSHOT.war, app.zip, wildfly-20.0.1.Final+patch.PNG, wildfly-20.0.1.Final.PNG
>
>
> org.eclipse.yasson.internal.JsonBinding keeps a reference on an enum after the war is undeployed which results in a classloader leak.
> 1- Deploy the following application:
>
> {code:java}
> package au.com.spatiumxl.model;
> public class Book {
> public enum Status { READ, UNREAD }
> private String title;
> private Book.Status status;
> public Book(String title) {
> this.title = title;
> this.status = Book.Status.UNREAD;
> }
> public String getTitle() {
> return title;
> }
> public Book.Status getStatus() {
> return status;
> }
> }
> {code}
>
> {code:java}
> package au.com.spatiumxl.ejb;
> [...]
> import au.com.spatiumxl.model.Book;
> @Stateless
> @LocalBean
> public class BookService {
> public List<Book> getBooks() {
> List<Book> books = new ArrayList<>();
> books.add(new Book("title1"));
> return books;
> }
> }
> {code}
>
> {code:java}
> package au.com.spatiumxl.rest;
> [...]
> import au.com.spatiumxl.ejb.BookService;
> import au.com.spatiumxl.model.Book;
> @RequestScoped
> @Path("")public
> class BookEndPoint {
> @Inject BookService bookService;
> @GET @Path("/get-books")
> @Produces("application/json")
> public List<Book> getBooks() {
> return bookService.getBooks();
> }
> }
> {code}
>
> 2- On the browser go to: http://<host>/<context-root>/.../get-books
> 3- Undeploy the war
> 4- The memory analyser shows:
> {code:java}
> java.lang.Thread
> org.jboss.modules.ModuleClassLoader
> org.jboss.modules.Module
> org.jboss.modules.LocalModuleLoader
> java.util.concurrent.ConcurrentHashMap
> java.util.concurrent.ConcurrentHashMap$Node[]
> java.util.concurrent.ConcurrentHashMap$Node
> org.jboss.modules.ModuleLoader$FutureModule
> org.jboss.modules.Module
> org.jboss.modules.ModuleClassLoader
> java.util.Vector
> java.lang.Object[]
> org.jboss.resteasy.plugins.providers.jsonb.AbstractJsonBindingProvider
> org.eclipse.yasson.internal.JsonBinding
> org.eclipse.yasson.internal.JsonbContext
> org.eclipse.yasson.internal.MappingContext
> java.util.concurrent.ConcurrentHashMap
> java.util.concurrent.ConcurrentHashMap$Node[]
> java.util.concurrent.ConcurrentHashMap$Node
> org.eclipse.yasson.internal.model.ClassModel
> org.eclipse.yasson.internal.model.PropertyModel[]
> org.eclipse.yasson.internal.model.PropertyModel
> au.com.spatiumxl.model.Book$Status
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (WFLY-13790) Memory leak caused by org.eclipse.yasson.internal.JsonBinding
by Ahcene Kessal (Jira)
[ https://issues.redhat.com/browse/WFLY-13790?page=com.atlassian.jira.plugi... ]
Ahcene Kessal commented on WFLY-13790:
--------------------------------------
*Attachments*:
||Attached artifacts||Description||
|app.zip|app used to trigger the memory leak|
|WFLY-13790-0.0.1-SNAPSHOT.war|built package from "app.zip"|
|wildfly-20.0.1.Final.PNG|memory graph from wildfly-20.0.1.Final|
|wildfly-20.0.1.Final+patch.PNG|memory graph from "wildfly-20.0.1.Final + patch"|
*Test description:*
Start application server "wildfly-20.0.1.Final" and "jconsole.exe" to record memory usage.
# deploy WFLY-13790-0.0.1-SNAPSHOT.war
# on browser get: [http://localhost:8080/rest/get-books]
# un-deploy WFLY-13790-0.0.1-SNAPSHOT.war
# re-deploy WFLY-13790-0.0.1-SNAPSHOT.war
# on browser get: [http://localhost:8080/rest/get-books]
repeat the above steps again and again
*note*: for deploying/un-deploying operations I used "jboss-cli.bat":
{code:java}
[standalone@localhost:9990 /] /deployment=WFLY-13790-0.0.1-SNAPSHOT.war:undeploy()
[standalone@localhost:9990 /] /deployment=WFLY-13790-0.0.1-SNAPSHOT.war:deploy {code}
*Test results:*
# with wildfly-20.0.1.Final, the JVM throws _*OutOfMemoryError*_ after 6 iterations
# I swapped "resteasy-json-binding-provider-3.12.1.Final.jar" for the one built from [https://github.com/rsearls/Resteasy/commit/55a0c2f6b3dc9b396513ec615cd49b... I repeated the test. The memory leak does not occur anymore, I repeated the test 15 times and then I stopped.
The memory graphs are attached.
The patch resolves the issue and this case can be closed.
> Memory leak caused by org.eclipse.yasson.internal.JsonBinding
> -------------------------------------------------------------
>
> Key: WFLY-13790
> URL: https://issues.redhat.com/browse/WFLY-13790
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 20.0.1.Final
> Reporter: Ahcene Kessal
> Assignee: r searls
> Priority: Major
> Attachments: WFLY-13790-0.0.1-SNAPSHOT.war, app.zip, wildfly-20.0.1.Final+patch.PNG, wildfly-20.0.1.Final.PNG
>
>
> org.eclipse.yasson.internal.JsonBinding keeps a reference on an enum after the war is undeployed which results in a classloader leak.
> 1- Deploy the following application:
>
> {code:java}
> package au.com.spatiumxl.model;
> public class Book {
> public enum Status { READ, UNREAD }
> private String title;
> private Book.Status status;
> public Book(String title) {
> this.title = title;
> this.status = Book.Status.UNREAD;
> }
> public String getTitle() {
> return title;
> }
> public Book.Status getStatus() {
> return status;
> }
> }
> {code}
>
> {code:java}
> package au.com.spatiumxl.ejb;
> [...]
> import au.com.spatiumxl.model.Book;
> @Stateless
> @LocalBean
> public class BookService {
> public List<Book> getBooks() {
> List<Book> books = new ArrayList<>();
> books.add(new Book("title1"));
> return books;
> }
> }
> {code}
>
> {code:java}
> package au.com.spatiumxl.rest;
> [...]
> import au.com.spatiumxl.ejb.BookService;
> import au.com.spatiumxl.model.Book;
> @RequestScoped
> @Path("")public
> class BookEndPoint {
> @Inject BookService bookService;
> @GET @Path("/get-books")
> @Produces("application/json")
> public List<Book> getBooks() {
> return bookService.getBooks();
> }
> }
> {code}
>
> 2- On the browser go to: http://<host>/<context-root>/.../get-books
> 3- Undeploy the war
> 4- The memory analyser shows:
> {code:java}
> java.lang.Thread
> org.jboss.modules.ModuleClassLoader
> org.jboss.modules.Module
> org.jboss.modules.LocalModuleLoader
> java.util.concurrent.ConcurrentHashMap
> java.util.concurrent.ConcurrentHashMap$Node[]
> java.util.concurrent.ConcurrentHashMap$Node
> org.jboss.modules.ModuleLoader$FutureModule
> org.jboss.modules.Module
> org.jboss.modules.ModuleClassLoader
> java.util.Vector
> java.lang.Object[]
> org.jboss.resteasy.plugins.providers.jsonb.AbstractJsonBindingProvider
> org.eclipse.yasson.internal.JsonBinding
> org.eclipse.yasson.internal.JsonbContext
> org.eclipse.yasson.internal.MappingContext
> java.util.concurrent.ConcurrentHashMap
> java.util.concurrent.ConcurrentHashMap$Node[]
> java.util.concurrent.ConcurrentHashMap$Node
> org.eclipse.yasson.internal.model.ClassModel
> org.eclipse.yasson.internal.model.PropertyModel[]
> org.eclipse.yasson.internal.model.PropertyModel
> au.com.spatiumxl.model.Book$Status
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (WFLY-13790) Memory leak caused by org.eclipse.yasson.internal.JsonBinding
by Ahcene Kessal (Jira)
[ https://issues.redhat.com/browse/WFLY-13790?page=com.atlassian.jira.plugi... ]
Ahcene Kessal updated WFLY-13790:
---------------------------------
Attachment: wildfly-20.0.1.Final.PNG
wildfly-20.0.1.Final+patch.PNG
app.zip
WFLY-13790-0.0.1-SNAPSHOT.war
> Memory leak caused by org.eclipse.yasson.internal.JsonBinding
> -------------------------------------------------------------
>
> Key: WFLY-13790
> URL: https://issues.redhat.com/browse/WFLY-13790
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 20.0.1.Final
> Reporter: Ahcene Kessal
> Assignee: r searls
> Priority: Major
> Attachments: WFLY-13790-0.0.1-SNAPSHOT.war, app.zip, wildfly-20.0.1.Final+patch.PNG, wildfly-20.0.1.Final.PNG
>
>
> org.eclipse.yasson.internal.JsonBinding keeps a reference on an enum after the war is undeployed which results in a classloader leak.
> 1- Deploy the following application:
>
> {code:java}
> package au.com.spatiumxl.model;
> public class Book {
> public enum Status { READ, UNREAD }
> private String title;
> private Book.Status status;
> public Book(String title) {
> this.title = title;
> this.status = Book.Status.UNREAD;
> }
> public String getTitle() {
> return title;
> }
> public Book.Status getStatus() {
> return status;
> }
> }
> {code}
>
> {code:java}
> package au.com.spatiumxl.ejb;
> [...]
> import au.com.spatiumxl.model.Book;
> @Stateless
> @LocalBean
> public class BookService {
> public List<Book> getBooks() {
> List<Book> books = new ArrayList<>();
> books.add(new Book("title1"));
> return books;
> }
> }
> {code}
>
> {code:java}
> package au.com.spatiumxl.rest;
> [...]
> import au.com.spatiumxl.ejb.BookService;
> import au.com.spatiumxl.model.Book;
> @RequestScoped
> @Path("")public
> class BookEndPoint {
> @Inject BookService bookService;
> @GET @Path("/get-books")
> @Produces("application/json")
> public List<Book> getBooks() {
> return bookService.getBooks();
> }
> }
> {code}
>
> 2- On the browser go to: http://<host>/<context-root>/.../get-books
> 3- Undeploy the war
> 4- The memory analyser shows:
> {code:java}
> java.lang.Thread
> org.jboss.modules.ModuleClassLoader
> org.jboss.modules.Module
> org.jboss.modules.LocalModuleLoader
> java.util.concurrent.ConcurrentHashMap
> java.util.concurrent.ConcurrentHashMap$Node[]
> java.util.concurrent.ConcurrentHashMap$Node
> org.jboss.modules.ModuleLoader$FutureModule
> org.jboss.modules.Module
> org.jboss.modules.ModuleClassLoader
> java.util.Vector
> java.lang.Object[]
> org.jboss.resteasy.plugins.providers.jsonb.AbstractJsonBindingProvider
> org.eclipse.yasson.internal.JsonBinding
> org.eclipse.yasson.internal.JsonbContext
> org.eclipse.yasson.internal.MappingContext
> java.util.concurrent.ConcurrentHashMap
> java.util.concurrent.ConcurrentHashMap$Node[]
> java.util.concurrent.ConcurrentHashMap$Node
> org.eclipse.yasson.internal.model.ClassModel
> org.eclipse.yasson.internal.model.PropertyModel[]
> org.eclipse.yasson.internal.model.PropertyModel
> au.com.spatiumxl.model.Book$Status
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (WFLY-13890) Several traces created in Jaeger for just one method call
by Emmanuel Hugonnet (Jira)
Emmanuel Hugonnet created WFLY-13890:
----------------------------------------
Summary: Several traces created in Jaeger for just one method call
Key: WFLY-13890
URL: https://issues.redhat.com/browse/WFLY-13890
Project: WildFly
Issue Type: Bug
Components: MP OpenTracing
Affects Versions: 21.0.0.Beta1
Reporter: Emmanuel Hugonnet
Assignee: Emmanuel Hugonnet
Fix For: 21.0.0.Final
I am migrating one opentracing/fault-tolerance test from Thorntail TS [1] and I noticed that Wildfly SNAPSHOT is behaving differently with respect to what in the subject.
The test is pretty simple, deploying a REST app which makes use of injected service which in turn leverages microprofile opentracing (via API) and fault-tolerance (via annotations). The test executes the following 2 methods in the given order:
- call {{hello}}, which is synchronous and is throwing an exception, hence failing and gets called again then ending up with the fallback. This generates 1 trace with 4 spans in Jaeger and the behavior is consistent between TT and WildFly
- call {{helloAsync}}, which is asynchronous and is throwing an exception, hence failing and getting called again (asynchronously?) then ending up with the fallback. This generates the following traces in Jaeger:
TT: 1 trace with 4 spans
WildFly: 4 separate traces , i.e. the one for the REST endpoint GET method, two for the {{helloAsync}} calls and one for the fallback.
[1]
https://github.com/rhoar-qe/thorntail-test-suite/tree/master/microprofile...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (WFLY-13889) Ongoing review of modules depending on PicketBox
by Darran Lofthouse (Jira)
Darran Lofthouse created WFLY-13889:
---------------------------------------
Summary: Ongoing review of modules depending on PicketBox
Key: WFLY-13889
URL: https://issues.redhat.com/browse/WFLY-13889
Project: WildFly
Issue Type: Task
Components: Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 22.0.0.Beta1
This follows up from WFLY-13679, ongoing work is needed to ensure PicketBox is not needed at all. The PicketBox module depends on APIs removed in Java 14 so we need to be able to eliminate it completely if legacy security it not being used.
At the same time some subsystems are defaulting to legacy security with additional configuration being required to force configuration over to an Elytron configuration, in some cases this applies even if the underlying configuration is not using security at all such as JCA resource adaptors.
We should be looking at what we can do to detect the presence of legacy security and now if not provisioned we should be able to default to Elytron based security.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (WFLY-13659) Fix modules with dependency on Legacy Security Subsystem
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFLY-13659?page=com.atlassian.jira.plugi... ]
Darran Lofthouse updated WFLY-13659:
------------------------------------
Summary: Fix modules with dependency on Legacy Security Subsystem (was: Fix modules with dependency on Legacy Security Subsystem or PicketBox)
> Fix modules with dependency on Legacy Security Subsystem
> --------------------------------------------------------
>
> Key: WFLY-13659
> URL: https://issues.redhat.com/browse/WFLY-13659
> Project: WildFly
> Issue Type: Task
> Components: Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Labels: EE9
> Fix For: 21.0.0.Final
>
>
> Various subsystems have dependencies on the legacy security subsystem, these need to be verified to make sure they are really required or adjusted to make optional.
> *org.jboss.as.security*
> {code}
> ./system/layers/base/org/wildfly/extension/request-controller/main/module.xml: <module name="org.jboss.as.security" optional="true"/>
> ./system/layers/base/org/wildfly/extension/io/main/module.xml: <module name="org.jboss.as.security" optional="true"/>
> ./system/layers/base/org/wildfly/extension/elytron/main/module.xml: <module name="org.jboss.as.security-integration" optional="true" services="import"/>
> ./system/layers/base/org/wildfly/extension/undertow/main/module.xml: <module name="org.jboss.as.security" optional="true"/>
> ./system/layers/base/org/wildfly/extension/picketlink/main/module.xml: <module name="org.jboss.as.security"/>
> ./system/layers/base/org/wildfly/extension/messaging-activemq/main/module.xml: <module name="org.jboss.as.security"/>
> ./system/layers/base/org/apache/activemq/artemis/main/module.xml: <module name="org.jboss.as.security"/>
> ./system/layers/base/org/jboss/as/vault-tool/main/module.xml: <main-class name="org.jboss.as.security.vault.VaultTool"/>
> ./system/layers/base/org/jboss/as/vault-tool/main/module.xml: <module name="org.jboss.as.security"/>
> ./system/layers/base/org/jboss/as/webservices/main/module.xml: <module name="org.jboss.as.security"/>
> ./system/layers/base/org/jboss/as/connector/main/module.xml: <module name="org.jboss.as.security"/>
> ./system/layers/base/org/jboss/as/ejb3/main/module.xml: <module name="org.jboss.as.security"/>
> ./system/layers/base/org/jboss/as/remoting/main/module.xml: <module name="org.jboss.as.security" optional="true"/>
> ./system/layers/base/org/jboss/as/appclient/main/module.xml: <module name="org.jboss.as.security"/>
> ./system/layers/base/org/jboss/as/server/main/module.xml: <module name="org.jboss.as.security" optional="true" services="import"/>
> ./system/layers/base/org/jboss/as/weld/common/main/module.xml: <module name="org.jboss.as.security" optional="true"/>
> {code}
> *org.picketbox*
> {code}
> ./system/layers/base/org/wildfly/extension/io/main/module.xml: <module name="org.picketbox" optional="true"/>
> ./system/layers/base/org/wildfly/extension/batch/jberet/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/wildfly/extension/undertow/main/module.xml: <module name="org.picketbox" optional="true"/>
> ./system/layers/base/org/wildfly/extension/picketlink/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/wildfly/extension/messaging-activemq/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/wildfly/iiop-openjdk/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/apache/activemq/artemis/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/picketlink/federation/bindings/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/picketlink/federation/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/as/webservices/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/as/connector/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/as/ejb3/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/as/remoting/main/module.xml: <module name="org.picketbox" optional="true"/>
> ./system/layers/base/org/jboss/as/appclient/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/as/security-api/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/as/server/main/module.xml: <module name="org.picketbox" optional="true"/>
> ./system/layers/base/org/jboss/as/weld/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/as/domain-management/main/module.xml: <module name="org.picketbox" optional="true"/>
> ./system/layers/base/org/jboss/as/cli/main/module.xml: <module name="org.picketbox" optional="true"/>
> ./system/layers/base/org/jboss/as/security/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/as/security-integration/main/module.xml: <module name="org.picketbox">
> ./system/layers/base/org/jboss/ws/cxf/jbossws-cxf-client/main/module.xml: <module name="org.picketbox" export="true"/>
> ./system/layers/base/org/jboss/ws/cxf/jbossws-cxf-server/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/ws/jaxws-client/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/ironjacamar/impl/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/security/negotiation/main/module.xml: <module name="org.picketbox"/>
> {code}
> The optional dependencies are probably Ok but the non-optional dependencies mean these will pull in the modules we do not want when these subsystems are provisioned.
> As there are quite a few affected modules I will likely group these into related areas and create sub tasks to track the individual problems to be addressed.
> Ignoring the optional dependencies the list of modules to target becomes:
> * org.apache.activemq.artemis
> * org.jboss.as.appclient
> * org.jboss.as.connector
> * org.jboss.as.ejb3
> * org.jboss.as.webservices
> * -org.jboss.as.weld-
> * org.jboss.ironjacamar.impl
> * org.jboss.ws.cxf.jbossws-cxf-client
> * org.jboss.ws.cxf.jbossws-cxf-server
> * org.jboss.ws.jaxws-client
> * -org.wildfly.extension.batch.jberet-
> * org.wildfly.extension.messaging-activemq
> * org.wildfly.iiop-openjdk
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (WFLY-13888) Move JWTEJBTestCase to testsuite/integration/microprofile
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFLY-13888?page=com.atlassian.jira.plugi... ]
Darran Lofthouse commented on WFLY-13888:
-----------------------------------------
FYI this will need the EJB layer adding to the server provisioned for the MicroProfile test, it was not previously possible to test EJB related tests in the microprofile testsuite.
> Move JWTEJBTestCase to testsuite/integration/microprofile
> ---------------------------------------------------------
>
> Key: WFLY-13888
> URL: https://issues.redhat.com/browse/WFLY-13888
> Project: WildFly
> Issue Type: Task
> Components: MP JWT
> Reporter: Brian Stansberry
> Assignee: Darran Lofthouse
> Priority: Major
>
> Part of our overall testing strategy is wanting to be able to run testsuite/integration/basic using the output of the ee-build maven module or provisioning using the wildfly-ee feature pack. Having a JWT test in that testsuite breaks that.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months