June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13587) Smallrye OpenAPI throws java.lang.NullPointerException because of null parameter schema

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFLY-13587?page=com.atlassian.jira.plugi... ] Fabio Burzigotti commented on WFLY-13587: ----------------------------------------- Hi [~pferraro], I was wondering whether this one too should be incorporated by https://issues.redhat.com/browse/WFLY-13546 WDYT? > Smallrye OpenAPI throws java.lang.NullPointerException because of null parameter schema > --------------------------------------------------------------------------------------- > > Key: WFLY-13587 > URL: https://issues.redhat.com/browse/WFLY-13587 > Project: WildFly > Issue Type: Bug > Components: MP OpenAPI > Affects Versions: 20.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > This was spotted while running RESTEasy test suite against EAP XP 1.0.0 CR1 and CR2. > Initially it seemed that the specific test case [1] was failing due to the same root cause of those tracked by the following issue: > * https://issues.redhat.com/browse/JBEAP-19600 > > Eventually it turned out that the changes to fix the above mentioned issue didn't solve this specific test case failures and a deeper investigation was done, see [2]. > Specifically a strange behavior is represented by the fact that the reproducer built manually by using the same resources used by the test case could be deployed successfully while the WAR archive generated by Arquillian in the RESTEasy TS was failing to deploy regularly. > The investigation detailed at https://github.com/smallrye/smallrye-open-api/issues/353#issuecomment-639... provided evidence that there are some cases in which the parameter schema would be set to null, so the issue [2] was created upstream. > [1] > https://github.com/resteasy/Resteasy/blob/3.11/testsuite/integration-test... > [2] > https://github.com/smallrye/smallrye-open-api/issues/359 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13515) Application does not fail when @Singleton @PostConstruct throws exception

by Panagiotis Sotiropoulos (Jira)

[ https://issues.redhat.com/browse/WFLY-13515?page=com.atlassian.jira.plugi... ] Panagiotis Sotiropoulos reassigned WFLY-13515: ---------------------------------------------- Assignee: Cheng Fang (was: Panagiotis Sotiropoulos) > Application does not fail when @Singleton @PostConstruct throws exception > ------------------------------------------------------------------------- > > Key: WFLY-13515 > URL: https://issues.redhat.com/browse/WFLY-13515 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 19.0.0.Final, 20.0.0.Beta1 > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > Labels: Regression, downstream_dependency > Attachments: helloWorld.ear > > > In EAP 6.4 , sub deployments were accessible before all Singleton's PostConstruct were finished, this was fixed via [1]. After this fix if an exception was thrown from PostConstruct, then the whole deployment was in a failed state as well. EAP 7.0 works the same as EAP 6.4 after the fix. > In EAP 7.3/7.2/7.1 when the Singleton throws an exception, the sub deployments are accessible. > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1310908 > EJB 3.1 spec, section 4.8.1: > {quote} > If the Startup annotation appears on the Singleton bean class or if the Singleton has been designated via the deployment descriptor as requiring eager initialization, the container must initialize the Singleton bean instance during the application startup sequence. The container must initialize all such startup-time Singletons before any external client requests (that is, client requests originating outside of the application) are delivered to any enterprise bean components in the application. > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6938) Startup error messages caused by expression where expressions are not allowed are confusing

by Lukas Vydra (Jira)

[ https://issues.redhat.com/browse/WFLY-6938?page=com.atlassian.jira.plugin... ] Lukas Vydra commented on WFLY-6938: ----------------------------------- I can confirm that host.xml part is issue no more. As for the main one, I will move it to WFCORE and continue with better handling of capability resolution. > Startup error messages caused by expression where expressions are not allowed are confusing > ------------------------------------------------------------------------------------------- > > Key: WFLY-6938 > URL: https://issues.redhat.com/browse/WFLY-6938 > Project: WildFly > Issue Type: Enhancement > Components: Server > Affects Versions: 10.1.0.CR1 > Reporter: Ondrej Chaloupka > Assignee: Lukas Vydra > Priority: Minor > > When a property expression is used at place where expression usage is not allowed then error message which is shown is quite confusing. From user point of view (especially the newcomer) it would be nice if the error message shows the real reason - usage of expression at place where is not permitted. > Maybe CLI could warn on usage of expression on place where is not allowed too. > Documentation recommends configuration with CLI, editing of XML file is common too. More of it there are some tasks which are harder to be done with CLI and editing XML is faster/easier. > Examples: > Setting > {code} > /subsystem=ee/managed-executor-service=default:write-attribute(name=context-service, value="${my.context.service}") > {code} > ends with this error message during startup > {code} > 14:13:21,076 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "ee"), > ("managed-executor-service" => "default") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.concurrent.ee.context.service.${my.context.service}"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.concurrent.ee.executor.default is missing [jboss.concurrent.ee.context.service.${my.context.service}]"]} > {code} > another confusion is setting name of host in {{host-slave.xml}} file. When set as > {code} > <host xmlns="urn:jboss:domain:4.2" host="${host.name}"> > {code} > then NullPointerException is thrown. > {code} > [Host Controller] 14:18:45,238 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0033: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131) > at org.jboss.as.host.controller.HostControllerConfigurationPersister.load(HostControllerConfigurationPersister.java:188) > at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:594) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299) > at java.lang.Thread.run(Thread.java:745)[Host Controller] Caused by: javax.xml.stream.XMLStreamException: ParseError > at [row,col]:[3,1][Host Controller] Message: WFLYCTL0197: Unexpected attribute 'host' encountered > at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:117) > at org.jboss.as.host.controller.parsing.HostXml_4.readHostElement(HostXml_4.java:311) > at org.jboss.as.host.controller.parsing.HostXml_4.readElement(HostXml_4.java:170) > at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:79) > at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:50) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) ... 4 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5437) Unable to deploy project to kie server

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5437?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5437: -------------------------------- Attachment: Screenshot from 2020-06-17 07-29-32.png > Unable to deploy project to kie server > -------------------------------------- > > Key: DROOLS-5437 > URL: https://issues.redhat.com/browse/DROOLS-5437 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.39.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2020-06-17 07-29-32.png, c.d is undefined 2.scesim, c.d is undefined.scesim, error.log, image-2020-06-16-21-39-06-147.png, undefinedType.webm > > > Cannot deploy any project to kie-server > Kie server fails deploying project with message [^c.d is undefined.scesim] [^c.d is undefined 2.scesim] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5437) Unable to deploy project to kie server

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5437?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-5437: ------------------------------------- [~adupliak] on my machine the issue seems be even more serious, once I start BusinessCentral with configured KieServer, I do not see any server in given perspective [1] and have an error in log [2]. [1] !Screenshot from 2020-06-17 07-29-32.png|thumbnail! [2] [^error.log] > Unable to deploy project to kie server > -------------------------------------- > > Key: DROOLS-5437 > URL: https://issues.redhat.com/browse/DROOLS-5437 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.39.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2020-06-17 07-29-32.png, c.d is undefined 2.scesim, c.d is undefined.scesim, error.log, image-2020-06-16-21-39-06-147.png, undefinedType.webm > > > Cannot deploy any project to kie-server > Kie server fails deploying project with message [^c.d is undefined.scesim] [^c.d is undefined 2.scesim] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5437) Unable to deploy project to kie server

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5437?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5437: -------------------------------- Attachment: error.log > Unable to deploy project to kie server > -------------------------------------- > > Key: DROOLS-5437 > URL: https://issues.redhat.com/browse/DROOLS-5437 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.39.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Blocker > Labels: drools-tools > Attachments: c.d is undefined 2.scesim, c.d is undefined.scesim, error.log, image-2020-06-16-21-39-06-147.png, undefinedType.webm > > > Cannot deploy any project to kie-server > Kie server fails deploying project with message [^c.d is undefined.scesim] [^c.d is undefined 2.scesim] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-1180) Red Hat Operators Mirroring is not working on Disconnected Clusters

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.redhat.com/browse/SWSQE-1180?page=com.atlassian.jira.plugi... ] Guilherme Baufaker Rêgo updated SWSQE-1180: ------------------------------------------- Attachment: Captura de Tela 2020-06-16 às 20.07.23.png > Red Hat Operators Mirroring is not working on Disconnected Clusters > ------------------------------------------------------------------- > > Key: SWSQE-1180 > URL: https://issues.redhat.com/browse/SWSQE-1180 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > Priority: Major > Attachments: Captura de Tela 2020-06-16 às 20.07.23.png > > > [https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/infra-jobs/job...] > > [https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/install-ocp-upi...] > > Failed to pull image "bastion.gbaufake-disconnected.maistra.upshift.redhat.com:55555/olm/redhat-operators:v1": rpc error: code = Unknown desc = Error reading manifest v1 in bastion.gbaufake-disconnected.maistra.upshift.redhat.com:55555/olm/redhat-operators: manifest unknown: manifest unknown > > > It seems the mirroring is not working on the PSI cluster with the mirror job. > > > > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-1180) Red Hat Operators Mirroring is not working on Disconnected Clusters

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.redhat.com/browse/SWSQE-1180?page=com.atlassian.jira.plugi... ] Guilherme Baufaker Rêgo updated SWSQE-1180: ------------------------------------------- Description: [https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/infra-jobs/job...] [https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/install-ocp-upi...] Failed to pull image "bastion.gbaufake-disconnected.maistra.upshift.redhat.com:55555/olm/redhat-operators:v1": rpc error: code = Unknown desc = Error reading manifest v1 in bastion.gbaufake-disconnected.maistra.upshift.redhat.com:55555/olm/redhat-operators: manifest unknown: manifest unknown It seems the mirroring is not working on the PSI cluster with the mirror job. picture attached. was: [https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/infra-jobs/job...] [https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/install-ocp-upi...] Failed to pull image "bastion.gbaufake-disconnected.maistra.upshift.redhat.com:55555/olm/redhat-operators:v1": rpc error: code = Unknown desc = Error reading manifest v1 in bastion.gbaufake-disconnected.maistra.upshift.redhat.com:55555/olm/redhat-operators: manifest unknown: manifest unknown It seems the mirroring is not working on the PSI cluster with the mirror job. > Red Hat Operators Mirroring is not working on Disconnected Clusters > ------------------------------------------------------------------- > > Key: SWSQE-1180 > URL: https://issues.redhat.com/browse/SWSQE-1180 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > Priority: Major > Attachments: Captura de Tela 2020-06-16 às 20.07.23.png > > > [https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/infra-jobs/job...] > > [https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/install-ocp-upi...] > > Failed to pull image "bastion.gbaufake-disconnected.maistra.upshift.redhat.com:55555/olm/redhat-operators:v1": rpc error: code = Unknown desc = Error reading manifest v1 in bastion.gbaufake-disconnected.maistra.upshift.redhat.com:55555/olm/redhat-operators: manifest unknown: manifest unknown > > > It seems the mirroring is not working on the PSI cluster with the mirror job. > picture attached. > > > > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-1180) Red Hat Operators Mirroring is not working on Disconnected Clusters

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-1180: ---------------------------------------------- Summary: Red Hat Operators Mirroring is not working on Disconnected Clusters Key: SWSQE-1180 URL: https://issues.redhat.com/browse/SWSQE-1180 Project: Kiali QE Issue Type: Bug Reporter: Guilherme Baufaker Rêgo Assignee: Filip Brychta [https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/infra-jobs/job...] [https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/install-ocp-upi...] Failed to pull image "bastion.gbaufake-disconnected.maistra.upshift.redhat.com:55555/olm/redhat-operators:v1": rpc error: code = Unknown desc = Error reading manifest v1 in bastion.gbaufake-disconnected.maistra.upshift.redhat.com:55555/olm/redhat-operators: manifest unknown: manifest unknown It seems the mirroring is not working on the PSI cluster with the mirror job. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5437) Unable to deploy project to kie server

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-5437?page=com.atlassian.jira.plug... ] Daniele Zonca reassigned DROOLS-5437: ------------------------------------- Assignee: Yeser Amer (was: Daniele Zonca) > Unable to deploy project to kie server > -------------------------------------- > > Key: DROOLS-5437 > URL: https://issues.redhat.com/browse/DROOLS-5437 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.39.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Blocker > Labels: drools-tools > Attachments: c.d is undefined 2.scesim, c.d is undefined.scesim, image-2020-06-16-21-39-06-147.png, undefinedType.webm > > > Cannot deploy any project to kie-server > Kie server fails deploying project with message [^c.d is undefined.scesim] [^c.d is undefined 2.scesim] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 June 2020