November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1708) java.lang.NoSuchFieldError: state on jdk 1.8.0_191

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/ELY-1708?page=com.atlassian.jira.plugin.s... ] Martin Choma updated ELY-1708: ------------------------------ Summary: java.lang.NoSuchFieldError: state on jdk 1.8.0_191 (was: java.lang.NoSuchFieldError: state on oracle jdk 1.8.0_191) > java.lang.NoSuchFieldError: state on jdk 1.8.0_191 > -------------------------------------------------- > > Key: ELY-1708 > URL: https://issues.jboss.org/browse/ELY-1708 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.7.0.CR3 > Reporter: Martin Choma > Priority: Blocker > > - on oracle java version "1.8.0_181" it was ok on oracle java version "1.8.0_191" it fails > - I have checked oracle jdk 1.8.0_191 release notes and this seems relevant to this issue https://bugs.java.com/view_bug.do?bug_id=JDK-8074462 > - I have seen so far only in FIPS TS (BC and PKCS11) > - I dont see on openjdk > - I dont see on oracle jdk 11 > - I have reported to oracle but get no link to issue tracker back. They just told me "We will contact you if needed" :) > - similar problem https://youtrack.jetbrains.com/issue/JT-49978 > {noformat} > 21:19:11 java.lang.NoSuchFieldError: state > 21:19:11 at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:198) > 21:19:11 at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037) > 21:19:11 at sun.security.ssl.Handshaker.process_record(Handshaker.java:965) > 21:19:11 at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1064) > 21:19:11 at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367) > 21:19:11 at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395) > 21:19:11 at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379) > 21:19:11 at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:394) > 21:19:11 at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:353) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11265) wildfly-feature-pack -- Dependency Error

by Dennis Gesker (Jira)

[ https://issues.jboss.org/browse/WFLY-11265?page=com.atlassian.jira.plugin... ] Dennis Gesker commented on WFLY-11265: -------------------------------------- Thanks, Brain. I opened a new issue on the eclipse-ee4j site. https://github.com/eclipse-ee4j/soteria/issues/236 <https://mailtrack.io/trace/link/544d5afd9cff39f10f51cbc1de9c91e020af1e1e?...> Dennis On Mon, Nov 5, 2018 at 7:27 AM Brian Stansberry (Jira) <issues(a)jboss.org> -- Dennis R. Gesker [image: LinkedIn] <https://mailtrack.io/trace/link/d1bb13a14ab2fb3bc9204b027761b32def94448a?...>[image: WordPress] <https://mailtrack.io/trace/link/460c1db6bad44dbb9faedbd69835b12fc7b5acad?...>[image: Gesker] <https://mailtrack.io/trace/link/66aa15f9fb11a7bbf4449265745128bd3a8d191f?...>[image: GPG_PGP] <https://mailtrack.io/trace/link/100ed4c1aab023e2b98a983beee97e4d5bad66c6?...>[image: dennis(a)gesker.com] <dennis(a)gesker.com> “Be without fear in the face of your enemies. Be brave and upright that God may love thee. Speak the truth always, even if it leads to your death. Safeguard the helpless and do no wrong – that is your oath.”* -The Knight’s Oath (Kingdom of Heaven)* > wildfly-feature-pack -- Dependency Error > ---------------------------------------- > > Key: WFLY-11265 > URL: https://issues.jboss.org/browse/WFLY-11265 > Project: WildFly > Issue Type: Bug > Affects Versions: 14.0.0.Final > Environment: Ubuntu 18.10 > JDK 11 > WildFly 14.0.1.Final > Reporter: Dennis Gesker > Assignee: Jason Greene > Priority: Major > Labels: wildfly-feature-pack > Fix For: 14.0.0.Final > > > In my gradle build I've added: > * providedCompile "org.wildfly:wildfly-feature-pack:14.0.1.Final"* > > But, I'm getting: > > *> Could not resolve javax.security.enterprise:javax.security.enterprise-api:1.1-b01-SNAPSHOT. > Required by: > project : > org.wildfly:wildfly-feature-pack:14.0.1.Final > org.glassfish.soteria:javax.security.enterprise:1.0* > > Could not resolve javax.security.enterprise:javax.security.enterprise-api:1.1-b01-SNAPSHOT. > > Unable to load Maven meta-data from https://repository.jboss.org/nexus/content/groups/public-jboss/javax/secu.... > > Could not get resource 'https://repository.jboss.org/nexus/content/groups/public-jboss/javax/secu...'. > > Could not GET 'https://repository.jboss.org/nexus/content/groups/public-jboss/javax/secu...'. > > extension (10) should not be presented in server_hello > > Presently I have the following repositories in my build: > > jcenter() > mavenCentral() > > maven { > name "Gradle Repository" > url "https://plugins.gradle.org/m2/" > } > maven { > name "JBoss Public Maven Repository Group" > url "https://repository.jboss.org/nexus/content/groups/public-jboss/" > } > maven { > name "JBoss Public Maven Repository Group" > url "http://repository.jboss.org/nexus/content/groups/public/" > } > > > But, I suspect I am missing a repository specific to WildFly. Or, maybe there is a bad entry in the POM? > > Thanks, > Dennis -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-208) Missing -Djava.util.logging.manager=org.jboss.logmanager.LogManager for tests on IBM JDK

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-208?page=com.atlassian.jira.plugin... ] James Perkins reassigned LOGMGR-208: ------------------------------------ Assignee: Nikoleta Žiaková > Missing -Djava.util.logging.manager=org.jboss.logmanager.LogManager for tests on IBM JDK > ---------------------------------------------------------------------------------------- > > Key: LOGMGR-208 > URL: https://issues.jboss.org/browse/LOGMGR-208 > Project: JBoss Log Manager > Issue Type: Bug > Affects Versions: 2.1.5.Final > Reporter: Nikoleta Žiaková > Assignee: Nikoleta Žiaková > Priority: Major > Fix For: 2.2.0.Final > > > There are several test failures on IBM JDK with following error: > {quote} > The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") > {quote} > This is similar to WFCORE-3797 but profile for IBM cannot be added since Maven is run with different JDK than the tests themselves - build requires JDK11 and the tests are run on IBM JDK 1.8 using {{java8.home}} property. > Simple fix is to add "-Djava.util.logging.manager=org.jboss.logmanager.LogManager" to surefire argLine like at https://github.com/nziakova/jboss-logmanager/commit/ae67e8b517866b80f7797... > [~jamezp] WDYT? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

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

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-209?page=com.atlassian.jira.plugin... ] James Perkins commented on LOGMGR-209: -------------------------------------- It seems regenerating the keys using the IBM JDK works on both OpenJDK, Oracle JDK and the IBM JDK. > NoSuchAlgorithmException in SocketHandlerTests on IBM JDK > --------------------------------------------------------- > > Key: LOGMGR-209 > URL: https://issues.jboss.org/browse/LOGMGR-209 > Project: JBoss Log Manager > Issue Type: Bug > Affects Versions: 2.1.5.Final > Reporter: Nikoleta Žiaková > Assignee: James Perkins > Priority: Major > > 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.12.1#712002)

7 years, 8 months

1
0
0 / 0

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

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-209?page=com.atlassian.jira.plugin... ] James Perkins reassigned LOGMGR-209: ------------------------------------ Assignee: James Perkins > NoSuchAlgorithmException in SocketHandlerTests on IBM JDK > --------------------------------------------------------- > > Key: LOGMGR-209 > URL: https://issues.jboss.org/browse/LOGMGR-209 > Project: JBoss Log Manager > Issue Type: Bug > Affects Versions: 2.1.5.Final > Reporter: Nikoleta Žiaková > Assignee: James Perkins > Priority: Major > > 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.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3148) [DMN Designer] Graph view is taking the Name from the InformationItem and not the Decision

by Daniel José dos Santos (Jira)

[ https://issues.jboss.org/browse/DROOLS-3148?page=com.atlassian.jira.plugi... ] Daniel José dos Santos commented on DROOLS-3148: ------------------------------------------------ Yes, it's fixed by [JBPM-7166.|https://issues.jboss.org/browse/JBPM-7166] > [DMN Designer] Graph view is taking the Name from the InformationItem and not the Decision > ------------------------------------------------------------------------------------------ > > Key: DROOLS-3148 > URL: https://issues.jboss.org/browse/DROOLS-3148 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Blocker > Labels: drools-tools > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-484) Fix Json format change

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-484?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-484. ---------------------------------- Resolution: Done https://github.com/Kiali-QE/kiali-qe-python/pull/97 > Fix Json format change > ---------------------- > > Key: SWSQE-484 > URL: https://issues.jboss.org/browse/SWSQE-484 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/run-python-ui-te... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-448) Add missing Label checks for all objects

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-448?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-448. ---------------------------------- Resolution: Done > Add missing Label checks for all objects > ---------------------------------------- > > Key: SWSQE-448 > URL: https://issues.jboss.org/browse/SWSQE-448 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4198) Remove org.dom4j dependency from the org.jboss.log4j.logmanager module

by James Perkins (Jira)

James Perkins created WFCORE-4198: ------------------------------------- Summary: Remove org.dom4j dependency from the org.jboss.log4j.logmanager module Key: WFCORE-4198 URL: https://issues.jboss.org/browse/WFCORE-4198 Project: WildFly Core Issue Type: Task Components: Logging Reporter: James Perkins Assignee: James Perkins For some reason a {{org.dom4j}} dependency was added to the {{org.jboss.log4j.logmanager}} module. This was marked as option and doesn't seem to be used in log4j so it should be removed. My guess would be the {{java.xml}} module now covers the required implementation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3243) [DMN Designer] Move the Data Type dialog to a tab in the DMN editor

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3243?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3243: --------------------------------------- Story Points: 3 (was: 5) > [DMN Designer] Move the Data Type dialog to a tab in the DMN editor > ------------------------------------------------------------------- > > Key: DROOLS-3243 > URL: https://issues.jboss.org/browse/DROOLS-3243 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > https://issues.jboss.org/browse/DROOLS-3156 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 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 November 2018