[JBoss JIRA] (WFLY-12992) Log messages from io.smallrye.openapi don't have message ID
by Miroslav Novak (Jira)
[ https://issues.redhat.com/browse/WFLY-12992?page=com.atlassian.jira.plugi... ]
Miroslav Novak moved WFWIP-291 to WFLY-12992:
---------------------------------------------
Project: WildFly (was: WildFly WIP)
Key: WFLY-12992 (was: WFWIP-291)
Component/s: MP OpenAPI
(was: MP OpenAPI)
> Log messages from io.smallrye.openapi don't have message ID
> -----------------------------------------------------------
>
> Key: WFLY-12992
> URL: https://issues.redhat.com/browse/WFLY-12992
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenAPI
> Reporter: Fabio Burzigotti
> Assignee: Paul Ferraro
> Priority: Major
>
> Messages logged by io.smallrye.openapi don't have assigned ID:
> {code}
> 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.util.SchemaFactory] (MSC service thread 1-4) Processing a single @Schema annotation.
> 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.scanner.OpenApiAnnotationScanner] (MSC service thread 1-4) Processing a single @Response annotation.
> 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.scanner.OpenApiAnnotationScanner] (MSC service thread 1-4) Processing jax-rs method: {0}
> 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.scanner.OpenApiDataObjectScanner] (MSC service thread 1-4) Starting processing with root: java.lang.String
> {code}
> A search in SmallRye implementation seems to show that IDs are not used even when level is WARN:
> {code}
> $ find . -name '*.*' -type f -print0 | xargs -0 grep --color -n -e 'LOG.warn'
> ./implementation/src/main/java/io/smallrye/openapi/runtime/scanner/ParameterProcessor.java:551: LOG.warnf("Matrix parameter references missing path segment: %s", segmentName);
> ./implementation/src/main/java/io/smallrye/openapi/runtime/scanner/ParameterProcessor.java:1147: LOG.warnf("Value '%s' is not a valid %s default", stringValue, primitive.name().toLowerCase());
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4949) Blue rectangle above test scenario collection editor
by Daniele Zonca (Jira)
[ https://issues.redhat.com/browse/DROOLS-4949?page=com.atlassian.jira.plug... ]
Daniele Zonca reassigned DROOLS-4949:
-------------------------------------
Assignee: Yeser Amer (was: Daniele Zonca)
> Blue rectangle above test scenario collection editor
> ----------------------------------------------------
>
> Key: DROOLS-4949
> URL: https://issues.redhat.com/browse/DROOLS-4949
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Yeser Amer
> Priority: Minor
> Labels: drools-tools
> Attachments: Screenshot from 2020-01-17 12-30-13.png, urgent.dmn
>
>
> Issue was spotted during DROOLS-4698 review. However it can be handled separately.
> There appears misleading blue rectangle above the collection editor popup once when the editor has focus / is clicked.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-12991) SunX509 TrustManagerFactory not available from Elytron tests on IBM jdk
by Petr Kremensky (Jira)
Petr Kremensky created WFLY-12991:
-------------------------------------
Summary: SunX509 TrustManagerFactory not available from Elytron tests on IBM jdk
Key: WFLY-12991
URL: https://issues.redhat.com/browse/WFLY-12991
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: Petr Kremensky
Assignee: Petr Kremensky
On IBM JDK the following exception is thrown
{noformat}
Caused by: java.security.NoSuchAlgorithmException: SunX509 TrustManagerFactory not available
at sun.security.jca.GetInstance.getInstance(GetInstance.java:171)
at javax.net.ssl.TrustManagerFactory.getInstance(TrustManagerFactory.java:20)
at org.wildfly.extension.elytron.SSLDefinitions$2.createTrustManagerFactory(SSLDefinitions.java:869)
... 11 more
{noformat}
from
{noformat}
org.wildfly.test.integration.elytron.audit.TLSSyslogAuditLogTestCase.testSuccessfulAuthAndPermissionCheck
org.wildfly.test.integration.elytron.audit.TLSSyslogAuditLogTestCase.testFailedAuthWrongUser
org.wildfly.test.integration.elytron.audit.TLSSyslogAuditLogTestCase.testFailedAuthEmptyPassword
org.wildfly.test.integration.elytron.audit.TLSSyslogAuditLogTestCase.testFailedAuthWrongPassword
org.wildfly.test.integration.elytron.audit.TLSSyslogAuditLogTestCase.testFailedPermissionCheck
org.wildfly.test.integration.elytron.ssl.UndertowSslSecurityDomainTestCase.testForbidden
org.wildfly.test.integration.elytron.ssl.UndertowSslSecurityDomainTestCase.testUnprotectedAccess
org.wildfly.test.integration.elytron.ssl.UndertowSslSecurityDomainTestCase.testUntrustedCertificate
org.wildfly.test.integration.elytron.ssl.UndertowSslSecurityDomainTestCase.testProtectedAccess
org.wildfly.test.integration.elytron.ssl.UndertowTwoWaySslNeedClientAuthTestCase.testSendingTrustedClientCertificate
org.wildfly.test.integration.elytron.ssl.UndertowTwoWaySslTestCase.testSendingNoClientCertificate
org.wildfly.test.integration.elytron.ssl.UndertowTwoWaySslTestCase.testSendingNonTrustedClientCertificate
org.wildfly.test.integration.elytron.ssl.UndertowTwoWaySslTestCase.testSendingTrustedClientCertificate
{noformat}
These need to use IBMX509 instead.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4949) Blue rectangle above test scenario collection editor
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-4949?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-4949:
--------------------------------
Priority: Minor (was: Major)
> Blue rectangle above test scenario collection editor
> ----------------------------------------------------
>
> Key: DROOLS-4949
> URL: https://issues.redhat.com/browse/DROOLS-4949
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Daniele Zonca
> Priority: Minor
> Labels: drools-tools
> Attachments: Screenshot from 2020-01-17 12-30-13.png, urgent.dmn
>
>
> Issue was spotted during DROOLS-4698 review. However it can be handled separately.
> There appears misleading blue rectangle above the collection editor popup once when the editor has focus / is clicked.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4949) Blue rectangle above test scenario collection editor
by Jozef Marko (Jira)
Jozef Marko created DROOLS-4949:
-----------------------------------
Summary: Blue rectangle above test scenario collection editor
Key: DROOLS-4949
URL: https://issues.redhat.com/browse/DROOLS-4949
Project: Drools
Issue Type: Bug
Components: Scenario Simulation and Testing
Affects Versions: 7.32.0.Final
Reporter: Jozef Marko
Assignee: Daniele Zonca
Attachments: Screenshot from 2020-01-17 12-30-13.png, urgent.dmn
Issue was spotted during DROOLS-4698 review. However it can be handled separately.
There appears misleading blue rectangle above the collection editor popup once when the editor has focus / is clicked.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (SWSQE-1054) Bookinfo2 installation sometimes fails
by Filip Brychta (Jira)
Filip Brychta created SWSQE-1054:
------------------------------------
Summary: Bookinfo2 installation sometimes fails
Key: SWSQE-1054
URL: https://issues.redhat.com/browse/SWSQE-1054
Project: Kiali QE
Issue Type: Bug
Reporter: Filip Brychta
Assignee: Filip Brychta
Sometimes the kiali-test-mesh-operator does not notice newly created CR of bookinfo2 and resources are not created even when CR for bookinfo2 exists.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (JBEE-250) JBoss Modules based resolution executed too early in FactoryFinder
by Alessio Soldano (Jira)
[ https://issues.redhat.com/browse/JBEE-250?page=com.atlassian.jira.plugin.... ]
Alessio Soldano resolved JBEE-250.
----------------------------------
Resolution: Done
> JBoss Modules based resolution executed too early in FactoryFinder
> ------------------------------------------------------------------
>
> Key: JBEE-250
> URL: https://issues.redhat.com/browse/JBEE-250
> Project: JBoss Enterprise Spec APIs
> Issue Type: Bug
> Components: jboss-saaj-api
> Reporter: Alessio Soldano
> Assignee: Jim Ma
> Priority: Major
> Fix For: jboss-jakarta-saaj-api_1.4_spec-1.0.2.Final
>
>
> Our fork of SAAJ spec api uses JBoss Modules as one of the mechanisms for resolving factories; it looks like the resolution through jboss modules is attempted (when jboss-modules jar being available in the classpath) too early and that can result in a classloading issue when trying creating a SAAJMetaFactory instance.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (JBEE-250) JBoss Modules based resolution executed too early in FactoryFinder
by Alessio Soldano (Jira)
Alessio Soldano created JBEE-250:
------------------------------------
Summary: JBoss Modules based resolution executed too early in FactoryFinder
Key: JBEE-250
URL: https://issues.redhat.com/browse/JBEE-250
Project: JBoss Enterprise Spec APIs
Issue Type: Bug
Components: jboss-saaj-api
Reporter: Alessio Soldano
Assignee: Jim Ma
Our fork of SAAJ spec api uses JBoss Modules as one of the mechanisms for resolving factories; it looks like the resolution through jboss modules is attempted (when jboss-modules jar being available in the classpath) too early and that can result in a classloading issue when trying creating a SAAJMetaFactory instance.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months