May 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13451) Some microprofile QS are missing in the main README

by Martin Stefanko (Jira)

Martin Stefanko created WFLY-13451: -------------------------------------- Summary: Some microprofile QS are missing in the main README Key: WFLY-13451 URL: https://issues.redhat.com/browse/WFLY-13451 Project: WildFly Issue Type: Bug Components: Quickstarts Affects Versions: 19.1.0.Final Reporter: Martin Stefanko Assignee: Martin Stefanko -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-209) NoSuchAlgorithmException in SocketHandlerTests on IBM JDK

by James Perkins (Jira)

[ https://issues.redhat.com/browse/LOGMGR-209?page=com.atlassian.jira.plugi... ] James Perkins updated LOGMGR-209: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/204, https://github.com/jboss-logging/jboss-logmanager/pull/301 (was: https://github.com/jboss-logging/jboss-logmanager/pull/204) > NoSuchAlgorithmException in SocketHandlerTests on IBM JDK > --------------------------------------------------------- > > Key: LOGMGR-209 > URL: https://issues.redhat.com/browse/LOGMGR-209 > Project: JBoss Log Manager > Issue Type: Bug > Affects Versions: 2.1.5.Final > Reporter: Nikoleta Ziakova > Assignee: James Perkins > Priority: Major > Fix For: 2.1.16.Final, 2.2.0.Final > > > Following tests fail on IBM JDK: > {code} > org.jboss.logmanager.handlers.SocketHandlerTests#testProtocolChange > org.jboss.logmanager.handlers.SocketHandlerTests#testTlsConnection > org.jboss.logmanager.handlers.SocketHandlerTests#testTlsConfig > {code} > Error: > {code} > java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: IBMJSSE2, class: com.ibm.jsse2.aj) > {code} > Stack Trace: > {code} > Caused by: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: IBMJSSE2, class: com.ibm.jsse2.aj) > at java.security.Provider$Service.newInstance(Provider.java:1628) > at sun.security.jca.GetInstance.getInstance(GetInstance.java:248) > at sun.security.jca.GetInstance.getInstance(GetInstance.java:176) > at javax.net.ssl.SSLContext.getInstance(SSLContext.java:6) > at javax.net.ssl.SSLContext.getDefault(SSLContext.java:8) > at javax.net.ssl.SSLServerSocketFactory.getDefault(SSLServerSocketFactory.java:32) > ... 29 more > Caused by: java.security.KeyStoreException: IBMKeyManager: Problem accessing key store java.io.IOException: Invalid keystore format > at com.ibm.jsse2.ah.a(ah.java:72) > at com.ibm.jsse2.aj.g(aj.java:5) > at com.ibm.jsse2.aj.<init>(aj.java:13) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:83) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57) > at java.lang.reflect.Constructor.newInstance(Constructor.java:437) > at java.security.Provider$Service.newInstance(Provider.java:1606) > ... 34 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-209) NoSuchAlgorithmException in SocketHandlerTests on IBM JDK

by James Perkins (Jira)

[ https://issues.redhat.com/browse/LOGMGR-209?page=com.atlassian.jira.plugi... ] James Perkins updated LOGMGR-209: --------------------------------- Fix Version/s: 2.1.16.Final > NoSuchAlgorithmException in SocketHandlerTests on IBM JDK > --------------------------------------------------------- > > Key: LOGMGR-209 > URL: https://issues.redhat.com/browse/LOGMGR-209 > Project: JBoss Log Manager > Issue Type: Bug > Affects Versions: 2.1.5.Final > Reporter: Nikoleta Ziakova > Assignee: James Perkins > Priority: Major > Fix For: 2.1.16.Final, 2.2.0.Final > > > Following tests fail on IBM JDK: > {code} > org.jboss.logmanager.handlers.SocketHandlerTests#testProtocolChange > org.jboss.logmanager.handlers.SocketHandlerTests#testTlsConnection > org.jboss.logmanager.handlers.SocketHandlerTests#testTlsConfig > {code} > Error: > {code} > java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: IBMJSSE2, class: com.ibm.jsse2.aj) > {code} > Stack Trace: > {code} > Caused by: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: IBMJSSE2, class: com.ibm.jsse2.aj) > at java.security.Provider$Service.newInstance(Provider.java:1628) > at sun.security.jca.GetInstance.getInstance(GetInstance.java:248) > at sun.security.jca.GetInstance.getInstance(GetInstance.java:176) > at javax.net.ssl.SSLContext.getInstance(SSLContext.java:6) > at javax.net.ssl.SSLContext.getDefault(SSLContext.java:8) > at javax.net.ssl.SSLServerSocketFactory.getDefault(SSLServerSocketFactory.java:32) > ... 29 more > Caused by: java.security.KeyStoreException: IBMKeyManager: Problem accessing key store java.io.IOException: Invalid keystore format > at com.ibm.jsse2.ah.a(ah.java:72) > at com.ibm.jsse2.aj.g(aj.java:5) > at com.ibm.jsse2.aj.<init>(aj.java:13) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:83) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57) > at java.lang.reflect.Constructor.newInstance(Constructor.java:437) > at java.security.Provider$Service.newInstance(Provider.java:1606) > ... 34 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13450) Missing README.html for microprofile-rest-client QS

by Martin Stefanko (Jira)

Martin Stefanko created WFLY-13450: -------------------------------------- Summary: Missing README.html for microprofile-rest-client QS Key: WFLY-13450 URL: https://issues.redhat.com/browse/WFLY-13450 Project: WildFly Issue Type: Bug Components: Quickstarts Reporter: Martin Stefanko Assignee: Martin Stefanko There's only README.adoc in WildFly. The adoc file is not readable because it does not have resolved attributes and includes from shared docs, thus not sufficient. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13437) Upgrade wildfly-transaction-client to 1.1.11.Final

by Ingo Weiss (Jira)

[ https://issues.redhat.com/browse/WFLY-13437?page=com.atlassian.jira.plugi... ] Ingo Weiss updated WFLY-13437: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/13272 > Upgrade wildfly-transaction-client to 1.1.11.Final > -------------------------------------------------- > > Key: WFLY-13437 > URL: https://issues.redhat.com/browse/WFLY-13437 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Blocker > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > > Diff: https://github.com/wildfly/wildfly-transaction-client/compare/1.1.10.Fina... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13437) Upgrade wildfly-transaction-client to 1.1.11.Final

by Ingo Weiss (Jira)

[ https://issues.redhat.com/browse/WFLY-13437?page=com.atlassian.jira.plugi... ] Ingo Weiss updated WFLY-13437: ------------------------------ Labels: downstream_dependency (was: ) > Upgrade wildfly-transaction-client to 1.1.11.Final > -------------------------------------------------- > > Key: WFLY-13437 > URL: https://issues.redhat.com/browse/WFLY-13437 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Blocker > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > > Diff: https://github.com/wildfly/wildfly-transaction-client/compare/1.1.10.Fina... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5320) Rule compilation error when binding fields indexed with square brackets from different Fact types

by Matteo Casalino (Jira)

Matteo Casalino created DROOLS-5320: --------------------------------------- Summary: Rule compilation error when binding fields indexed with square brackets from different Fact types Key: DROOLS-5320 URL: https://issues.redhat.com/browse/DROOLS-5320 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.37.0.Final Reporter: Matteo Casalino Assignee: Mario Fusco Attachments: binding-field-indexed-with-square-brackets2.zip Similar to DROOLS-5216, but occurs when binding the collection from a different Fact type. Example: {noformat} rule "binding field indexed with square brackets from different fact type" when Pojo2($firstItem : simpleInt) Pojo($firstItem == integerList[this.integerList.size()-1]) then end {noformat} Error: {noformat} Message [id=1, kieBase=binding-field-indexed-with-square-brackets, level=ERROR, path=org/drools/reproducer/rules.drl, line=-1, column=0 text=Comparison operation requires compatible types. Found int and class java.lang.Object] {noformat} The example works fine when compiling without executable model. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5306) DMN type design document as javadoc

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5306?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5306: ----------------------------------- Story Points: 5 (was: 3) > DMN type design document as javadoc > ----------------------------------- > > Key: DROOLS-5306 > URL: https://issues.redhat.com/browse/DROOLS-5306 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12516) EJBContext principal is not popped back after invoking another EJB using a different Security Domain

by Ingo Weiss (Jira)

[ https://issues.redhat.com/browse/WFLY-12516?page=com.atlassian.jira.plugi... ] Ingo Weiss updated WFLY-12516: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/13271 > EJBContext principal is not popped back after invoking another EJB using a different Security Domain > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-12516 > URL: https://issues.redhat.com/browse/WFLY-12516 > Project: WildFly > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Major > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5319) DMN name collision type value fix

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5319: -------------------------------------- Summary: DMN name collision type value fix Key: DROOLS-5319 URL: https://issues.redhat.com/browse/DROOLS-5319 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 May 2020