June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5394) Coverage Report Improvements (CVS File)

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5394?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-5394: ------------------------------------------- Fix Version/s: 7.40.0.Final (was: 7.39.0.Final) > Coverage Report Improvements (CVS File) > --------------------------------------- > > Key: DROOLS-5394 > URL: https://issues.redhat.com/browse/DROOLS-5394 > Project: Drools > Issue Type: Enhancement > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > Fix For: 7.40.0.Final > > > Proposed solution tohttps://issues.redhat.com/browse/RHPAM-2616, is to put the same data shown on Coverage Report inside the generated CSV Report file. > This means to add following data: > Overall Stats (Available rules, executed rules, coverage percentage); > Rules counters -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-322) [EAP7-1337] Allow users to setup a source clone secrets manually

by Petr Kremensky (Jira)

[ https://issues.redhat.com/browse/WFWIP-322?page=com.atlassian.jira.plugin... ] Petr Kremensky updated WFWIP-322: --------------------------------- Description: Source clone secrets are used to provide the builder Pod with access it would not normally have access to, such as private repositories or repositories with self-signed or untrusted SSL certificates. We should add {{sourceSecret}} field into SourceRepositorySpec API in order to allow users to manually add a clone secret to their setup. See https://docs.openshift.com/container-platform/4.4/builds/creating-build-i... for more details on the source secret functionality. Users could use the {{source-secret-match-uri}} method to link sourceSecret automatically, but I think we should allow them to use {{sourceSecret}} as well to provide support both options how to solve this. was: Source clone secrets are used to provide the builder Pod with access it would not normally have access to, such as private repositories or repositories with self-signed or untrusted SSL certificates. We should add {{sourceSecret}} field into SourceRepositorySpec API in order to allow users to manually add a clone secret to their setup. See https://docs.openshift.com/container-platform/4.4/builds/creating-build-i... for more details on the source secret functionality. Users could use the {{source-secret-match-uri}} method to link sourceSecret automatically, but I think we should allow them to use {{sourceSecret}} as well to provide a full support for this. > [EAP7-1337] Allow users to setup a source clone secrets manually > ---------------------------------------------------------------- > > Key: WFWIP-322 > URL: https://issues.redhat.com/browse/WFWIP-322 > Project: WildFly WIP > Issue Type: Quality Risk > Components: OpenShift > Reporter: Petr Kremensky > Assignee: Jeff Mesnil > Priority: Major > > Source clone secrets are used to provide the builder Pod with access it would not normally have access to, such as private repositories or repositories with self-signed or untrusted SSL certificates. We should add {{sourceSecret}} field into SourceRepositorySpec API in order to allow users to manually add a clone secret to their setup. See https://docs.openshift.com/container-platform/4.4/builds/creating-build-i... for more details on the source secret functionality. > > Users could use the {{source-secret-match-uri}} method to link sourceSecret automatically, but I think we should allow them to use {{sourceSecret}} as well to provide support both options how to solve this. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13234) WF17 vs. WF18: org.infinispan.hibernate-cache

by Daniel Wehrle (Jira)

[ https://issues.redhat.com/browse/WFLY-13234?page=com.atlassian.jira.plugi... ] Daniel Wehrle commented on WFLY-13234: -------------------------------------- Hi Scott, any news on this? Regards, Daniel > WF17 vs. WF18: org.infinispan.hibernate-cache > --------------------------------------------- > > Key: WFLY-13234 > URL: https://issues.redhat.com/browse/WFLY-13234 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Affects Versions: 18.0.1.Final > Reporter: Daniel Wehrle > Assignee: Scott Marlow > Priority: Major > > Hi. > Why has the entity cache transaction in org.infinispan.hibernate-cache been changed from NON_XA to NONE (default) and what are the implications? Can this lead to performance problems? > WF17 > {code} > <cache-container name="hibernate" module="org.infinispan.hibernate-cache"> > <local-cache name="entity"> > <transaction mode="NON_XA"/> > <object-memory size="10000"/> > <expiration max-idle="100000"/> > </local-cache> > {code} > WF18 > {code} > <cache-container name="hibernate" module="org.infinispan.hibernate-cache"> > <local-cache name="entity"> > <object-memory size="10000"/> > <expiration max-idle="100000"/> > </local-cache> > {code} > Best regards, > Daniel -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-322) [EAP7-1337] Allow users to setup a source clone secrets manually

by Petr Kremensky (Jira)

Petr Kremensky created WFWIP-322: ------------------------------------ Summary: [EAP7-1337] Allow users to setup a source clone secrets manually Key: WFWIP-322 URL: https://issues.redhat.com/browse/WFWIP-322 Project: WildFly WIP Issue Type: Quality Risk Components: OpenShift Reporter: Petr Kremensky Assignee: Jeff Mesnil Source clone secrets are used to provide the builder Pod with access it would not normally have access to, such as private repositories or repositories with self-signed or untrusted SSL certificates. We should add {{sourceSecret}} field into SourceRepositorySpec API in order to allow users to manually add a clone secret to their setup. See https://docs.openshift.com/container-platform/4.4/builds/creating-build-i... for more details on the source secret functionality. Users could use the {{source-secret-match-uri}} method to link sourceSecret automatically, but I think we should allow them to use {{sourceSecret}} as well to provide a full support for this. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5006) Improve readability of domain host controller server logs in tests

by Richard Achmatowicz (Jira)

[ https://issues.redhat.com/browse/WFCORE-5006?page=com.atlassian.jira.plug... ] Richard Achmatowicz reassigned WFCORE-5006: ------------------------------------------- Assignee: Richard Achmatowicz > Improve readability of domain host controller server logs in tests > ------------------------------------------------------------------ > > Key: WFCORE-5006 > URL: https://issues.redhat.com/browse/WFCORE-5006 > Project: WildFly Core > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 12.0.1.Final > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Major > Fix For: 13.0.0.Beta1 > > > When domain tests involve multiple DCs and HCs starting on the same server, its difficult to differentiate between output from different host controllers. > At a minimum, associating the configuration host name with host controller startup and started messages would help in the readability of server logs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5006) Improve readability of domain host controller server logs in tests

by Richard Achmatowicz (Jira)

[ https://issues.redhat.com/browse/WFCORE-5006?page=com.atlassian.jira.plug... ] Richard Achmatowicz updated WFCORE-5006: ---------------------------------------- Summary: Improve readability of domain host controller server logs in tests (was: Improve readability of domain host controller server logs) > Improve readability of domain host controller server logs in tests > ------------------------------------------------------------------ > > Key: WFCORE-5006 > URL: https://issues.redhat.com/browse/WFCORE-5006 > Project: WildFly Core > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 12.0.1.Final > Reporter: Richard Achmatowicz > Priority: Major > Fix For: 13.0.0.Beta1 > > > When domain tests involve multiple DCs and HCs starting on the same server, its difficult to differentiate between output from different host controllers. > At a minimum, associating the configuration host name with host controller startup and started messages would help in the readability of server logs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5006) Improve readability of domain host controller server logs

by Richard Achmatowicz (Jira)

Richard Achmatowicz created WFCORE-5006: ------------------------------------------- Summary: Improve readability of domain host controller server logs Key: WFCORE-5006 URL: https://issues.redhat.com/browse/WFCORE-5006 Project: WildFly Core Issue Type: Enhancement Components: Test Suite Affects Versions: 12.0.1.Final Reporter: Richard Achmatowicz Fix For: 13.0.0.Beta1 When domain tests involve multiple DCs and HCs starting on the same server, its difficult to differentiate between output from different host controllers. At a minimum, associating the configuration host name with host controller startup and started messages would help in the readability of server logs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12356) remoting subsystem's http-connector is missing capability reference

by Richard Achmatowicz (Jira)

[ https://issues.redhat.com/browse/WFLY-12356?page=com.atlassian.jira.plugi... ] Richard Achmatowicz commented on WFLY-12356: -------------------------------------------- Hi Ranabir I replied on https://wildfly.zulipchat.com/#narrow/stream/174184-wildfly-developers...'s.20http-connector.20is.20missing Here is the reply: ``` @Ranabir Chakraborty Ranabir, when the http remoting connector is set up, it depends on a service provided by Undertow called the HTTP_UPGRADE_REGISTRY which is used to allow Remoting to register itself with Undertow's HTTP Upgrade mechanism. In the PR Brian cited above (not yet merged), I have added a Capability in Undertow for the HTTP_UPGRADE_REGISTRY which can be used by external subsystems like Remoting. Once this PR is merged, you can complete the work by adding a dependency on the Capability for HTTP_UPGRADE_REGISTRY to the Capability for the http-connector, namely HTTP_CONNECTOR_CAPABILITY. ``` > remoting subsystem's http-connector is missing capability reference > ------------------------------------------------------------------- > > Key: WFLY-12356 > URL: https://issues.redhat.com/browse/WFLY-12356 > Project: WildFly > Issue Type: Bug > Components: Remoting > Affects Versions: 17.0.1.Final > Reporter: Radoslav Husar > Assignee: Ranabir Chakraborty > Priority: Major > Labels: ux > > http-remoting-connector is missing capability reference to the undertow connector. > {noformat} > [standalone@localhost:9990 /] /subsystem=remoting/http-connector=http-remoting-connector:write-attribute(name=connector-ref,value=foo) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {noformat} > results in a cryptic error > {noformat} > 11:33:01,792 INFO [org.jboss.as.controller] (management-handler-thread - 1) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service org.wildfly.clustering.cache.registry-entry.ejb.client-mappings, service org.wildfly.ejb.remote] > WFLYCTL0448: 5 additional services are down due to their dependencies being missing or failed > 11:33:15,334 INFO [org.jboss.as.controller] (management-handler-thread - 1) WFLYCTL0183: Service status report > WFLYCTL0185: Newly corrected services: > service jboss.ejb.association (new available) > service jboss.ejb.remoting.connector.client-mappings (new available) > service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (no longer required) > service org.wildfly.clustering.cache.registry-entry.ejb.client-mappings (new available) > service org.wildfly.clustering.cache.registry-factory.ejb.client-mappings (new available) > service org.wildfly.clustering.group.ejb (new available) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13571) JSF: selectOneMenu required+disabled true

by Cody Lerum (Jira)

[ https://issues.redhat.com/browse/WFLY-13571?page=com.atlassian.jira.plugi... ] Cody Lerum commented on WFLY-13571: ----------------------------------- Thanks [~soul2zimate] > JSF: selectOneMenu required+disabled true > ----------------------------------------- > > Key: WFLY-13571 > URL: https://issues.redhat.com/browse/WFLY-13571 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 20.0.0.Final > Reporter: erick leal > Assignee: Farah Juma > Priority: Major > Attachments: project.zip > > > Submitin selectOneMenu required=true+disabled=true result in validation error message. > Regression in WildFly 20, clicking button fires a message. > WildFly 19 it's ok. > Mojarra issue: https://github.com/eclipse-ee4j/mojarra/issues/4716 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13571) JSF: selectOneMenu required+disabled true

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFLY-13571?page=com.atlassian.jira.plugi... ] Chao Wang commented on WFLY-13571: ---------------------------------- Yes, it's related to the fix for WFLY-13497 as well. The extra validation should have only applied to UIViewParameter. I have reproduced the issue from https://github.com/codylerum/jsf-disabled-input and tried it with new fix in the linked PR. Both buttons return following messages in log without any exception: {code:java} 21:32:38,010 INFO [BackingBean] (default task-1) Text was Existing text and foo was false 21:32:38,189 INFO [BackingBean] (default task-1) Text was Existing text and foo was false {code} So the issues no longer present and is covered in the linked PR. > JSF: selectOneMenu required+disabled true > ----------------------------------------- > > Key: WFLY-13571 > URL: https://issues.redhat.com/browse/WFLY-13571 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 20.0.0.Final > Reporter: erick leal > Assignee: Farah Juma > Priority: Major > Attachments: project.zip > > > Submitin selectOneMenu required=true+disabled=true result in validation error message. > Regression in WildFly 20, clicking button fires a message. > WildFly 19 it's ok. > Mojarra issue: https://github.com/eclipse-ee4j/mojarra/issues/4716 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2020