July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10298) Fail to open hibernate statistics

by Marek Marusic (JIRA)

[ https://issues.jboss.org/browse/WFLY-10298?page=com.atlassian.jira.plugin... ] Marek Marusic reassigned WFLY-10298: ------------------------------------ Assignee: Marek Marusic > Fail to open hibernate statistics > --------------------------------- > > Key: WFLY-10298 > URL: https://issues.jboss.org/browse/WFLY-10298 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Environment: wildfly12 > Reporter: Cora Kwok > Assignee: Marek Marusic > Attachments: Screenshot_2018-07-18_12-55-15.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10688) Bad unit conversion of jdbc-network-timeout attribute

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-10688?page=com.atlassian.jira.plugin... ] Kabir Khan commented on WFLY-10688: ----------------------------------- [~eduda] is this a blocker for the beta or just for WF14? If it is not for the beta please add the blocker-WF14 label so it is clear when looking at https://issues.jboss.org/issues/?filter=12335707 that it is not for the beta (actually this is no longer an issue now that I have resolved it). If it is for the beta, I guess we ought to clone it into a JBEAP issue and [~jmesnil] backports it. > Bad unit conversion of jdbc-network-timeout attribute > ----------------------------------------------------- > > Key: WFLY-10688 > URL: https://issues.jboss.org/browse/WFLY-10688 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 13.0.0.Final > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Blocker > Fix For: 14.0.0.CR1 > > > In the messaging subsystem there is an attribute {{jdbc-network-timeout}} with default value 20 seconds. However this parameter is passed to ActiveMQ Artemis as 20 000 000 milliseconds (20 000 seconds). > For reproducing the issue just configure JDBC persistence store and attach debugger with breakpoint on {{AbstractJDBCDriver::connect}}. > *Blocker* priority was set because it is regression against Wildfly 12. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10165) [Artemis 2.x upgrade] Bad unit conversion of jdbc-network-timeout attribute

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-10165?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFLY-10165: ------------------------------ Fix Version/s: 14.0.0.CR1 > [Artemis 2.x upgrade] Bad unit conversion of jdbc-network-timeout attribute > --------------------------------------------------------------------------- > > Key: WFLY-10165 > URL: https://issues.jboss.org/browse/WFLY-10165 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Blocker > Labels: feature-branch-blocker > Fix For: 14.0.0.CR1 > > > In the messaging subsystem there is an attribute {{jdbc-network-timeout}} with default value 20 seconds. However this parameter is passed to ActiveMQ Artemis as 20 000 000 milliseconds (20 000 seconds). > For reproducing the issue just configure JDBC persistence store and attach debugger with breakpoint on {{AbstractJDBCDriver::connect}}. > *Blocker* priority was set because it is regression against Wildfly 12. > The issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-339) Fix failing UI automation tests

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-339?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-339: -------------------------------------- PR sent https://github.com/Kiali-QE/kiali-qe-python/pull/60 > Fix failing UI automation tests > ------------------------------- > > Key: SWSQE-339 > URL: https://issues.jboss.org/browse/SWSQE-339 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/run-python-ui-te... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

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

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created WFWIP-62: -------------------------------------- Summary: Support for java.net.InetAddress out-of-the-box conversion Key: WFWIP-62 URL: https://issues.jboss.org/browse/WFWIP-62 Project: WildFly WIP 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)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-346) Bookinfo Timeouts

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-346?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-346: ------------------------------------ [http://git.host.prod.eng.bos.redhat.com/git/kiali-qe-utils.git/commit/?id...] > Bookinfo Timeouts > ----------------- > > Key: SWSQE-346 > URL: https://issues.jboss.org/browse/SWSQE-346 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > Bookinfo has been timing out waiting for the app to be ready. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-346) Bookinfo Timeouts

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-346: ---------------------------------- Summary: Bookinfo Timeouts Key: SWSQE-346 URL: https://issues.jboss.org/browse/SWSQE-346 Project: Kiali QE Issue Type: Bug Reporter: Matt Mahoney Assignee: Matt Mahoney Bookinfo has been timing out waiting for the app to be ready. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

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

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFWIP-59?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda commented on WFWIP-59: ---------------------------------------- If this is "no-go" to enable CDI, we should notify users if they are using MP Config annotations while CDI is not enabled. This would be new issue not to mix it. > Enable CDI by default when MP Config usage is detected in the deployment > ------------------------------------------------------------------------ > > Key: WFWIP-59 > URL: https://issues.jboss.org/browse/WFWIP-59 > Project: WildFly WIP > Issue Type: Enhancement > Components: MP Config > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Critical > > 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)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3519) Add JASPI Module

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3519?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3519: -------------------------------- Fix Version/s: 6.0.0.Alpha5 (was: 6.0.0.Alpha4) > Add JASPI Module > ---------------- > > Key: WFCORE-3519 > URL: https://issues.jboss.org/browse/WFCORE-3519 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 6.0.0.Alpha5 > > > (Copy from WildFly) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3961) Upgrade Elytron Web to 1.2.0.Final

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3961?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3961: -------------------------------- Fix Version/s: 6.0.0.Alpha5 (was: 6.0.0.Alpha4) > Upgrade Elytron Web to 1.2.0.Final > ---------------------------------- > > Key: WFCORE-3961 > URL: https://issues.jboss.org/browse/WFCORE-3961 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 6.0.0.Alpha5 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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