August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-87) [Artemis 2.x upgrade] Transaction remained in prepared state after failover of MDB

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFWIP-87?page=com.atlassian.jira.plugin.s... ] Miroslav Novak edited comment on WFWIP-87 at 8/15/18 11:54 AM: --------------------------------------------------------------- Run with WF master:https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x... was (Author: mnovak): Run with WF master: https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... > [Artemis 2.x upgrade] Transaction remained in prepared state after failover of MDB > ---------------------------------------------------------------------------------- > > Key: WFWIP-87 > URL: https://issues.jboss.org/browse/WFWIP-87 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Justin Bertram > Priority: Blocker > > There is regression in test scenario where MDB failovers from live to backup. Live is cleanly shutdown. > Problem is that after MDB failovers to backup then there is still transaction in prepared state which survive periodic recovery cycles. > Link to build: > https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-87) [Artemis 2.x upgrade] Transaction remained in prepared state after failover of MDB

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFWIP-87?page=com.atlassian.jira.plugin.s... ] Miroslav Novak edited comment on WFWIP-87 at 8/15/18 11:52 AM: --------------------------------------------------------------- Run with WF master: https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... was (Author: mnovak): Run with WF master: https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... > [Artemis 2.x upgrade] Transaction remained in prepared state after failover of MDB > ---------------------------------------------------------------------------------- > > Key: WFWIP-87 > URL: https://issues.jboss.org/browse/WFWIP-87 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Justin Bertram > Priority: Blocker > > There is regression in test scenario where MDB failovers from live to backup. Live is cleanly shutdown. > Problem is that after MDB failovers to backup then there is still transaction in prepared state which survive periodic recovery cycles. > Link to build: > https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1642) Compilation error on JDK 11: cannot find class sun.reflect.Reflection

by Ondrej Kotek (JIRA)

Ondrej Kotek created ELY-1642: --------------------------------- Summary: Compilation error on JDK 11: cannot find class sun.reflect.Reflection Key: ELY-1642 URL: https://issues.jboss.org/browse/ELY-1642 Project: WildFly Elytron Issue Type: Bug Components: Build Affects Versions: 1.5.1.Final Environment: openjdk version "11-ea" 2018-09-25 OpenJDK Runtime Environment 18.9 (build 11-ea+25) OpenJDK 64-Bit Server VM 18.9 (build 11-ea+25, mixed mode) Reporter: Ondrej Kotek Priority: Critical {{mvn test}} results in compilation error: {noformat} [ERROR] /home/okotek/git/wildfly-elytron/src/main/java/org/wildfly/security/manager/WildFlySecurityManager.java:[58,19] cannot find symbol symbol: class Reflection location: package sun.reflect {noformat} Blocks testing on JDK 11, setting to Critical. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10855) Support for java.net.InetAddress out-of-the-box conversion

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10855?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFWIP-62 to WFLY-10855: ---------------------------------------------- Project: WildFly (was: WildFly WIP) Key: WFLY-10855 (was: WFWIP-62) Component/s: MP Config (was: MP Config) > Support for java.net.InetAddress out-of-the-box conversion > ---------------------------------------------------------- > > Key: WFLY-10855 > URL: https://issues.jboss.org/browse/WFLY-10855 > Project: WildFly > Issue Type: Enhancement > Components: MP Config > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > > Payara provides out of the box support for java.net.InetAddress conversion. > https://blog.payara.fish/recent-additions-in-microprofile-config-1.1 > We could add this support too so there is no-effort migration path for MP Config from Payara to WildFly or WildFly Swarm. > {code} > // Injection of an InetAddress object on top of the MicroProfile Config specification > @Inject > @ConfigProperty(name = "application.address", defaultValue = "10.0.0.1") > InetAddress inetAddress; > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10854) Default value defined on injection point of List and Set fields is not taken into account

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10854?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFWIP-55 to WFLY-10854: ---------------------------------------------- Project: WildFly (was: WildFly WIP) Key: WFLY-10854 (was: WFWIP-55) Component/s: MP Config (was: MP Config) > Default value defined on injection point of List and Set fields is not taken into account > ----------------------------------------------------------------------------------------- > > Key: WFLY-10854 > URL: https://issues.jboss.org/browse/WFLY-10854 > Project: WildFly > Issue Type: Bug > Components: MP Config > Environment: {noformat} > git@github.com:jmesnil/wildfly.git:WFLY-10522_microprofile-config-smallrye_extension > {noformat} > Reporter: Petr Kremensky > Assignee: Jeff Mesnil > > Assume we define a following injection points: > {code:java} > @Inject > @ConfigProperty(name = "myPets", defaultValue = "horse,monkey") > private String[] myArrayPets; > @Inject > @ConfigProperty(name = "myPets", defaultValue = "cat,lama") > private List<String> myListPets; > @Inject > @ConfigProperty(name = "myPets", defaultValue = "dog,mouse") > private Set<String> mySetPets; > {code} > Passing a -DmyPets=snake,ox property work as expected: > {noformat} > myArrayPets : [snake,ox] > myListPets : [snake,ox] > mySetPets : [snake,ox] > {noformat} > but trying to use the defults I get: > {noformat} > myArrayPets : [horse,monkey] > myListPets : <empty list> > mySetPets : <empty set> > {noformat} > defaults are not applied to List and Set fields, no exception is thrown. > Another inconsistency between Array and Set+List I run into is behaviour on missing property (myPets is not set): > *Array* > {code:java} > @Inject > @ConfigProperty(name = "myPets") > private String[] myArrayPets; > >>> > 08:34:05,178 ERROR [stderr] (MSC service thread 1-2) org.jboss.weld.exceptions.DeploymentException: Error while validating Configuration > 08:34:05,178 ERROR [stderr] (MSC service thread 1-2) No Config Value exists for myPets > myArrayPets : [org.eclipse.microprofile.config.configproperty.unconfigureddvalue] > {code} > *Set, List* > {code:java} > @Inject > @ConfigProperty(name = "myPets") > private List<String> myListPets; > @Inject > @ConfigProperty(name = "myPets") > private Set<String> mySetPets; > >>> > no errors > myListPets : <empty list> > mySetPets : <empty set> > {code} > https://microprofile.io/project/eclipse/microprofile-config/spec/src/main... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10853) Description of the elements in newly introduced microprofile-config-smallrye subsystem could be more informative

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10853?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFWIP-61 to WFLY-10853: ---------------------------------------------- Project: WildFly (was: WildFly WIP) Key: WFLY-10853 (was: WFWIP-61) Component/s: MP Config (was: MP Config) > Description of the elements in newly introduced microprofile-config-smallrye subsystem could be more informative > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10853 > URL: https://issues.jboss.org/browse/WFLY-10853 > Project: WildFly > Issue Type: Bug > Components: MP Config > Environment: git@github.com:jmesnil/wildfly.git:WFLY-10522_microprofile-config-smallrye_extension > Reporter: Jan Stourac > Assignee: Jeff Mesnil > > Description of the elements in /subsystem=microprofile-config-smallrye could give more info, so far it states just: > {code:title=/subsystem=microprofile-config-smallrye:read-resource-description} > "config-source-provider" => { > "description" => "Config Source Provider", > "config-source" => { > "description" => "Config Source", > {code} > Maybe adding also information about what those elements are used for could improve user experience, e.g.: > {code} > "config-source-provider" => { > "description" => "Config Source Provider can be used to register own implementation for config-source with your specific way of configuration", > "config-source" => { > "description" => "Config Source contains configured configuration sources that are utilized for configuration", > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-87) [Artemis 2.x upgrade] Transaction remained in prepared state after failover of MDB

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFWIP-87?page=com.atlassian.jira.plugin.s... ] Miroslav Novak commented on WFWIP-87: ------------------------------------- Run with WF master: https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... > [Artemis 2.x upgrade] Transaction remained in prepared state after failover of MDB > ---------------------------------------------------------------------------------- > > Key: WFWIP-87 > URL: https://issues.jboss.org/browse/WFWIP-87 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Justin Bertram > Priority: Blocker > > There is regression in test scenario where MDB failovers from live to backup. Live is cleanly shutdown. > Problem is that after MDB failovers to backup then there is still transaction in prepared state which survive periodic recovery cycles. > Link to build: > https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-90) [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFWIP-90?page=com.atlassian.jira.plugin.s... ] Miroslav Novak commented on WFWIP-90: ------------------------------------- Run with Wildlfy master (Artemis 1.5.5.012): https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... > [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart > ------------------------------------------------------------------------------- > > Key: WFWIP-90 > URL: https://issues.jboss.org/browse/WFWIP-90 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > > There are undelivered messages in scenario with where servers in remote JCA topology are restarted. There are undelivered message after test. > Test scenario: > * Start 2 server in Artemis cluster > * Start 2 servers with MDB connected to Artemis cluster > ** MDB resends messages from InQueue to OutQueue from/to remote cluster > * Send messages to InQueue > * Restart all server (one by one) > * Consumes messages from OutQueue > Results: > After the test there are missing messages in OutQueue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10852) smallrye-config: Consider logging a message when properties with same key and ordinal are present

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10852?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFWIP-60 to WFLY-10852: ---------------------------------------------- Project: WildFly (was: WildFly WIP) Key: WFLY-10852 (was: WFWIP-60) Component/s: MP Config (was: MP Config) > smallrye-config: Consider logging a message when properties with same key and ordinal are present > ------------------------------------------------------------------------------------------------- > > Key: WFLY-10852 > URL: https://issues.jboss.org/browse/WFLY-10852 > Project: WildFly > Issue Type: Enhancement > Components: MP Config > Reporter: Michal Jurc > Assignee: Jeff Mesnil > > Consider a deployment with default {{microprofile-config.properties}}: > {code}managementDefault=Default value from default microprofile-config.properties{code} > Deployment is deployed on server with the following {{ConfigSource}} defined: > {code}[standalone@localhost:9990 /] /subsystem=microprofile-config-smallrye/config-source=testdefault:read-resource > { > "outcome" => "success", > "result" => { > "class" => undefined, > "dir" => undefined, > "ordinal" => 100, > "properties" => {"managementDefault" => "Value from WildFly microprofile-config-smallrye config-source"} > } > } > {code} > Property {{"managementDefault"}} is always resolved to {{"Value from WildFly microprofile-config-smallrye config-source"}} in deployment. > It would be useful to log a {{WARN}} level message when there is conflict like this with a notification of {{ConfigSources}} to save detective work in real world scenarios. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10851) Enable CDI by default when MP Config usage is detected in the deployment

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10851?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFWIP-59 to WFLY-10851: ---------------------------------------------- Project: WildFly (was: WildFly WIP) Key: WFLY-10851 (was: WFWIP-59) Component/s: MP Config (was: MP Config) > Enable CDI by default when MP Config usage is detected in the deployment > ------------------------------------------------------------------------ > > Key: WFLY-10851 > URL: https://issues.jboss.org/browse/WFLY-10851 > Project: WildFly > Issue Type: Enhancement > Components: MP Config > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > > Enable CDI by default when MP Config usage is detected in the deployment. > Currently users are forced to add empty {{beans.xml}} to the deployment every time they want to use MP Config - e.g. in simple servlet scenario > {code} > @WebServlet("/") > public class HelloServlet extends HttpServlet { > @Inject > @ConfigProperty(name = "port_number") > Integer port; > @Override > protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws IOException { > resp.getWriter().println("Value of port: " + port); > } > } > {code} > MP Config without CDI makes no sense to me. MP Config subsystem should be able to ensure CDI is enabled. CCing [~manovotn] [~brian.stansberry] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

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 August 2018