April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11956) @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11956?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11956: ------------------------------------ Attachment: logging.txt > @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-11956 > URL: https://issues.jboss.org/browse/WFLY-11956 > Project: WildFly > Issue Type: Bug > Components: Bean Validation > Affects Versions: 16.0.0.Final > Reporter: Joerg Baesner > Assignee: Brian Stansberry > Priority: Major > Attachments: logging.txt, playground.zip > > > Having a bean class with {{@ApplicationScoped}}, which has a {{@PostConstruct}} and is implementing the following _Interface_: > {code} > @Path("/validated") > public interface ValidatedJaxRsInterface { > > @GET > @Valid > @Produces(MediaType.APPLICATION_JSON) > GreetingModel getHelloGreeting(); > } > {code} > will result in calling the {{getHelloGreeting}} method of the implementation class twice *_before_* the {{@PostConstruct}} is getting executed. > This can be reproduced with the attached reproducer application... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11956) @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11956?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11956: ------------------------------------ Attachment: logging.txt > @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-11956 > URL: https://issues.jboss.org/browse/WFLY-11956 > Project: WildFly > Issue Type: Bug > Components: Bean Validation > Affects Versions: 16.0.0.Final > Reporter: Joerg Baesner > Assignee: Brian Stansberry > Priority: Major > Attachments: logging.txt, playground.zip > > > Having a bean class with {{@ApplicationScoped}}, which has a {{@PostConstruct}} and is implementing the following _Interface_: > {code} > @Path("/validated") > public interface ValidatedJaxRsInterface { > > @GET > @Valid > @Produces(MediaType.APPLICATION_JSON) > GreetingModel getHelloGreeting(); > } > {code} > will result in calling the {{getHelloGreeting}} method of the implementation class twice *_before_* the {{@PostConstruct}} is getting executed. > This can be reproduced with the attached reproducer application... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4412) Eliminate deprecated CapabilityServiceTarget.addCapability() usages

by Richard Opalka (Jira)

Richard Opalka created WFCORE-4412: -------------------------------------- Summary: Eliminate deprecated CapabilityServiceTarget.addCapability() usages Key: WFCORE-4412 URL: https://issues.jboss.org/browse/WFCORE-4412 Project: WildFly Core Issue Type: Enhancement Components: IO, Remoting, Security, Server Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 9.0.0.Beta3 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4411) Introduce CapabilityServiceBuilder.setInstance(Service service) overriding method

by Richard Opalka (Jira)

Richard Opalka created WFCORE-4411: -------------------------------------- Summary: Introduce CapabilityServiceBuilder.setInstance(Service service) overriding method Key: WFCORE-4411 URL: https://issues.jboss.org/browse/WFCORE-4411 Project: WildFly Core Issue Type: Feature Request Components: Server Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 9.0.0.Beta3 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11965) Upgrade WildFly HTTP Client to 1.0.15.Final

by Ilia Vassilev (Jira)

Ilia Vassilev created WFLY-11965: ------------------------------------ Summary: Upgrade WildFly HTTP Client to 1.0.15.Final Key: WFLY-11965 URL: https://issues.jboss.org/browse/WFLY-11965 Project: WildFly Issue Type: Component Upgrade Reporter: Ilia Vassilev Assignee: Stuart Douglas Fix For: 16.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11965) Upgrade WildFly HTTP Client to 1.0.15.Final

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/WFLY-11965?page=com.atlassian.jira.plugin... ] Ilia Vassilev updated WFLY-11965: --------------------------------- Fix Version/s: (was: 16.0.0.Beta1) > Upgrade WildFly HTTP Client to 1.0.15.Final > ------------------------------------------- > > Key: WFLY-11965 > URL: https://issues.jboss.org/browse/WFLY-11965 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Ilia Vassilev > Assignee: Stuart Douglas > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3858) DMN large memory allocation bug

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3858?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-3858: ----------------------------------- Security: (was: Red Hat Internal) > DMN large memory allocation bug > ------------------------------- > > Key: DROOLS-3858 > URL: https://issues.jboss.org/browse/DROOLS-3858 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3710) HA CEP Kafka

by Rajesh Rajasekaran (Jira)

[ https://issues.jboss.org/browse/DROOLS-3710?page=com.atlassian.jira.plugi... ] Rajesh Rajasekaran commented on DROOLS-3710: -------------------------------------------- Hi [~jpetrlik] I agree we need a BAPL jira to track product delivery. It's best if one of the PM's ([~ibek] [~mfentanes] ) or PO ([~tirelli] ) create it. > HA CEP Kafka > ------------- > > Key: DROOLS-3710 > URL: https://issues.jboss.org/browse/DROOLS-3710 > Project: Drools > Issue Type: Epic > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > > All the steps are described here https://docs.google.com/document/d/1Wt-lHm1BTRbgX8okCcjDZSLEaE34WP4sgqMfC... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELYWEB-49) Release Elytron Web 1.5.0.CR1

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELYWEB-49?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved ELYWEB-49. ------------------------------------ Resolution: Done > Release Elytron Web 1.5.0.CR1 > ----------------------------- > > Key: ELYWEB-49 > URL: https://issues.jboss.org/browse/ELYWEB-49 > Project: Elytron Web > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.5.0.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3185) Run parallel boot tasks in coarser grained chunks

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-3185?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3185: ------------------------------------- Description: Currently parallel boot works by executing one task per Extension.initializeParsers call, one per Extension.initialize call and 2 per subsystem, one for execution of Stage.MODEL ops and one for Stage.RUNTIME ops. The Extension.initializeParsers tasks complete before boot proceeds to the point where any Extension.initialize tasks run, and the Extension.initialize tasks complete before the Stage.MODEL tasks run. The Stage.MODEL tasks do the large bulk of their work before the Stage.RUNTIME tasks run, but they do block waiting for the Stage.RUNTIME tasks and the rest of the boot to complete. The rough effect of all this is we are allocating 2 threads per subsystem to do parallel boot, and at various points we have 1 thread per subsystem concurrently working. For a brief period (doing Stage.DONE of the post-extension boot op) we have 2 threads per subsystem concurrently working. My measurements show that all of this concurrent work reduces boot time about 400ms on my machine, using the full WildFly standalone-full.xml config. However, this approach uses a lot of threads. So the task here is to look into how to get the same or better boot speed while using fewer threads. (Note the threads will expire and be gc'd after boot.) The obvious way to do this is to look at each of the 4 task types discussed in the first paragraph and group things into larger units of work than a single extension/subsystem. Initial work on doing this shows that using more coarse grained chunks does not result in reduced boot time, but also seems not to increase boot time. Further measurement is needed to confirm this though, and small tweaks may show different results. -Another thing to consider is allowing the Stage.MODEL tasks to complete without waiting for the overall boot op to complete. This might reduce the max number of threads involved and perhaps will allow a tiny bit more parallelization of work. The key here is ensuring the Stage.MODEL tasks are not able to affect the state of the final system in an invalid way. That could be problematic or fragile, so it's just something to consider, and if done must be done with great care.- Even if this work produces no reduction in boot time, if it produces no increase there is some value in incorporating it, as avoiding unnecessary thread creation improves the impression of the efficiency and good design of the software. _In particular, with a default thread stack size of 1024K, allocating an extra 50+ threads at boot means the process will consume an extra 50MB of RSS beyond what it would otherwise need. That memory should eventually be returned to the OS, and it's possible that later use of the server will result in a peak memory use after boot that's higher than what's needed at boot, but still, in a memory constrained environment (think cloud with applications trying to live in a smaller memory budget), requesting an extra 50MB beyond what provides benefit is not immaterial._ was: Currently parallel boot works by executing one task per Extension.initializeParsers call, one per Extension.initialize call and 2 per subsystem, one for execution of Stage.MODEL ops and one for Stage.RUNTIME ops. The Extension.initializeParsers tasks complete before boot proceeds to the point where any Extension.initialize tasks run, and the Extension.initialize tasks complete before the Stage.MODEL tasks run. The Stage.MODEL tasks do the large bulk of their work before the Stage.RUNTIME tasks run, but they do block waiting for the Stage.RUNTIME tasks and the rest of the boot to complete. The rough effect of all this is we are allocating 2 threads per subsystem to do parallel boot, and at various points we have 1 thread per subsystem concurrently working. For a brief period (doing Stage.DONE of the post-extension boot op) we have 2 threads per subsystem concurrently working. My measurements show that all of this concurrent work reduces boot time about 400ms on my machine, using the full WildFly standalone-full.xml config. However, this approach uses a lot of threads. So the task here is to look into how to get the same or better boot speed while using fewer threads. (Note the threads will expire and be gc'd after boot.) The obvious way to do this is to look at each of the 4 task types discussed in the first paragraph and group things into larger units of work than a single extension/subsystem. Initial work on doing this shows that using more coarse grained chunks does not result in reduced boot time, but also seems not to increase boot time. Further measurement is needed to confirm this though, and small tweaks may show different results. -Another thing to consider is allowing the Stage.MODEL tasks to complete without waiting for the overall boot op to complete. This might reduce the max number of threads involved and perhaps will allow a tiny bit more parallelization of work. The key here is ensuring the Stage.MODEL tasks are not able to affect the state of the final system in an invalid way. That could be problematic or fragile, so it's just something to consider, and if done must be done with great care.- Even if this work produces no reduction in boot time, if it produces no increase there is some value in incorporating it, as avoiding unnecessary thread creation improves the impression of the efficiency and good design of the software. > Run parallel boot tasks in coarser grained chunks > ------------------------------------------------- > > Key: WFCORE-3185 > URL: https://issues.jboss.org/browse/WFCORE-3185 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > Currently parallel boot works by executing one task per Extension.initializeParsers call, one per Extension.initialize call and 2 per subsystem, one for execution of Stage.MODEL ops and one for Stage.RUNTIME ops. The Extension.initializeParsers tasks complete before boot proceeds to the point where any Extension.initialize tasks run, and the Extension.initialize tasks complete before the Stage.MODEL tasks run. The Stage.MODEL tasks do the large bulk of their work before the Stage.RUNTIME tasks run, but they do block waiting for the Stage.RUNTIME tasks and the rest of the boot to complete. > The rough effect of all this is we are allocating 2 threads per subsystem to do parallel boot, and at various points we have 1 thread per subsystem concurrently working. For a brief period (doing Stage.DONE of the post-extension boot op) we have 2 threads per subsystem concurrently working. > My measurements show that all of this concurrent work reduces boot time about 400ms on my machine, using the full WildFly standalone-full.xml config. However, this approach uses a lot of threads. So the task here is to look into how to get the same or better boot speed while using fewer threads. (Note the threads will expire and be gc'd after boot.) > The obvious way to do this is to look at each of the 4 task types discussed in the first paragraph and group things into larger units of work than a single extension/subsystem. > Initial work on doing this shows that using more coarse grained chunks does not result in reduced boot time, but also seems not to increase boot time. Further measurement is needed to confirm this though, and small tweaks may show different results. > -Another thing to consider is allowing the Stage.MODEL tasks to complete without waiting for the overall boot op to complete. This might reduce the max number of threads involved and perhaps will allow a tiny bit more parallelization of work. The key here is ensuring the Stage.MODEL tasks are not able to affect the state of the final system in an invalid way. That could be problematic or fragile, so it's just something to consider, and if done must be done with great care.- > Even if this work produces no reduction in boot time, if it produces no increase there is some value in incorporating it, as avoiding unnecessary thread creation improves the impression of the efficiency and good design of the software. > > _In particular, with a default thread stack size of 1024K, allocating an extra 50+ threads at boot means the process will consume an extra 50MB of RSS beyond what it would otherwise need. That memory should eventually be returned to the OS, and it's possible that later use of the server will result in a peak memory use after boot that's higher than what's needed at boot, but still, in a memory constrained environment (think cloud with applications trying to live in a smaller memory budget), requesting an extra 50MB beyond what provides benefit is not immaterial._ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2019