September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10680) Upgrade Hibernate ORM from 5.1.14 to 5.1.15

by Bartosz Spyrko-Śmietanko (JIRA)

[ https://issues.jboss.org/browse/WFLY-10680?page=com.atlassian.jira.plugin... ] Bartosz Spyrko-Śmietanko resolved WFLY-10680. --------------------------------------------- Resolution: Out of Date Resolving, as hibernate ORM was moved to 3.5.x (WFLY-10519). > Upgrade Hibernate ORM from 5.1.14 to 5.1.15 > ------------------------------------------- > > Key: WFLY-10680 > URL: https://issues.jboss.org/browse/WFLY-10680 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Bartosz Spyrko-Śmietanko > Labels: downstream_dependency > > https://github.com/hibernate/hibernate-orm/compare/5.1.14...5.15 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11082) ClassCastExceptions and unexpected ServletContainerInitializer executions

by Alexander Kudrevatykh (JIRA)

[ https://issues.jboss.org/browse/WFLY-11082?page=com.atlassian.jira.plugin... ] Alexander Kudrevatykh updated WFLY-11082: ----------------------------------------- Description: I got unexpected ClassCastExceptions in setup as in attached test ServiceLoader provide only one instance of SCI, but wildlfy executes it twice More weird - wrong Set of classes passed to onStartup method - classes are not extends @HandlesTypes annotation (because they loaded with different classloaders) sorry for complex description, look for attached test was: I got unexpected ClassCastExceptions in setup as in attached test ServiceLoader provide only one instance of SCI, but wildlfy executes it twice More wired - wrong Set of classes passed to onStartup method - classes are not extends @HandlesTypes annotation (because they loaded with different classloaders) sorry for complex description, look for attached test > ClassCastExceptions and unexpected ServletContainerInitializer executions > ------------------------------------------------------------------------- > > Key: WFLY-11082 > URL: https://issues.jboss.org/browse/WFLY-11082 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 14.0.1.Final > Reporter: Alexander Kudrevatykh > Assignee: Jason Greene > Attachments: dependencies.zip > > > I got unexpected ClassCastExceptions in setup as in attached test > ServiceLoader provide only one instance of SCI, but wildlfy executes it twice > More weird - wrong Set of classes passed to onStartup method - classes are not extends @HandlesTypes annotation (because they loaded with different classloaders) > sorry for complex description, look for attached test -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11082) ClassCastExceptions and unexpected ServletContainerInitializer executions

by Alexander Kudrevatykh (JIRA)

[ https://issues.jboss.org/browse/WFLY-11082?page=com.atlassian.jira.plugin... ] Alexander Kudrevatykh updated WFLY-11082: ----------------------------------------- Component/s: Web (Undertow) > ClassCastExceptions and unexpected ServletContainerInitializer executions > ------------------------------------------------------------------------- > > Key: WFLY-11082 > URL: https://issues.jboss.org/browse/WFLY-11082 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 14.0.1.Final > Reporter: Alexander Kudrevatykh > Assignee: Jason Greene > Attachments: dependencies.zip > > > I got unexpected ClassCastExceptions in setup as in attached test > ServiceLoader provide only one instance of SCI, but wildlfy executes it twice > More wired - wrong Set of classes passed to onStartup method - classes are not extends @HandlesTypes annotation (because they loaded with different classloaders) > sorry for complex description, look for attached test -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11082) ClassCastExceptions and unexpected ServletContainerInitializer executions

by Alexander Kudrevatykh (JIRA)

Alexander Kudrevatykh created WFLY-11082: -------------------------------------------- Summary: ClassCastExceptions and unexpected ServletContainerInitializer executions Key: WFLY-11082 URL: https://issues.jboss.org/browse/WFLY-11082 Project: WildFly Issue Type: Bug Affects Versions: 14.0.1.Final Reporter: Alexander Kudrevatykh Assignee: Jason Greene Attachments: dependencies.zip I got unexpected ClassCastExceptions in setup as in attached test ServiceLoader provide only one instance of SCI, but wildlfy executes it twice More wired - wrong Set of classes passed to onStartup method - classes are not extends @HandlesTypes annotation (because they loaded with different classloaders) sorry for complex description, look for attached test -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4132) LogManager stops any logging output after changing "encoding" attribute to file-handler

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4132?page=com.atlassian.jira.plugi... ] James Perkins moved WFLY-11078 to WFCORE-4132: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4132 (was: WFLY-11078) Component/s: Logging (was: Logging) Affects Version/s: (was: 14.0.0.Final) > LogManager stops any logging output after changing "encoding" attribute to file-handler > --------------------------------------------------------------------------------------- > > Key: WFCORE-4132 > URL: https://issues.jboss.org/browse/WFCORE-4132 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Masafumi Miura > Assignee: James Perkins > > When setting "encoding" attribute on the file handler (file-handler, periodic-rotating-file-handler, size-rotating-file-handler, and periodic-size-rotating-file-handler) in CLI, LogManager throw the following error message in the console log and stops any logging output to the file-handler. > Note that the stack trace below "org.jboss.logmanager.Logger.logRaw(Logger.java:850)" can differ. It looks like this error just happens on the first logging output after the configuration change. > Even after executing ":reload" the instance via CLI, no log message are output to the file-handler. The instance needs to restart to output the file-handler. > {code} > LogManager error of type FLUSH_FAILURE: Error on flush > java.io.IOException: Stream Closed > at java.io.FileOutputStream.writeBytes(Native Method) > at java.io.FileOutputStream.write(FileOutputStream.java:326) > at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) > at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140) > at org.jboss.logmanager.handlers.UninterruptibleOutputStream.flush(UninterruptibleOutputStream.java:110) > at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297) > at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141) > at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229) > at java.io.BufferedWriter.flush(BufferedWriter.java:254) > at org.jboss.logmanager.handlers.WriterHandler.safeFlush(WriterHandler.java:170) > at org.jboss.logmanager.handlers.WriterHandler.flush(WriterHandler.java:139) > at org.jboss.logmanager.ExtHandler.doPublish(ExtHandler.java:105) > at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:67) > at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:77) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:333) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:341) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:341) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:341) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:341) > at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:341) > at org.jboss.logmanager.Logger.logRaw(Logger.java:850) > at org.jboss.logmanager.Logger.log(Logger.java:802) > at org.jboss.logging.JBossLogManagerLogger.doLogf(JBossLogManagerLogger.java:53) > at org.jboss.logging.Logger.logf(Logger.java:2398) > at org.jboss.as.mail.extension.MailLogger_$logger.unboundMailSession(MailLogger_$logger.java:42) > at org.jboss.as.mail.extension.MailSessionAdd$1.handleEvent(MailSessionAdd.java:150) > at org.jboss.msc.service.ServiceControllerImpl$LifecycleListenerTask.execute(ServiceControllerImpl.java:1857) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364) > at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4131) Upgrade jboss-logmanager from 2.1.4.Final to 2.1.5.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4131?page=com.atlassian.jira.plugi... ] James Perkins reassigned WFCORE-4131: ------------------------------------- Assignee: James Perkins > Upgrade jboss-logmanager from 2.1.4.Final to 2.1.5.Final > -------------------------------------------------------- > > Key: WFCORE-4131 > URL: https://issues.jboss.org/browse/WFCORE-4131 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: James Perkins > Assignee: James Perkins > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4131) Upgrade jboss-logmanager from 2.1.4.Final to 2.1.5.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4131?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4131: ---------------------------------- Component/s: Logging > Upgrade jboss-logmanager from 2.1.4.Final to 2.1.5.Final > -------------------------------------------------------- > > Key: WFCORE-4131 > URL: https://issues.jboss.org/browse/WFCORE-4131 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4131) Upgrade jboss-logmanager from 2.1.4.Final to 2.1.5.Final

by James Perkins (JIRA)

James Perkins created WFCORE-4131: ------------------------------------- Summary: Upgrade jboss-logmanager from 2.1.4.Final to 2.1.5.Final Key: WFCORE-4131 URL: https://issues.jboss.org/browse/WFCORE-4131 Project: WildFly Core Issue Type: Component Upgrade Reporter: James Perkins -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1684) Release WildFly Elytron 1.7.0.CR2

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1684: ------------------------------------- Summary: Release WildFly Elytron 1.7.0.CR2 Key: ELY-1684 URL: https://issues.jboss.org/browse/ELY-1684 Project: WildFly Elytron Issue Type: Bug Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.7.0.CR2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1663) BC FIPS, Management Interface, ELY04001: No algorithm found matching TLS/SSL protocol selection criteria

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-1663?page=com.atlassian.jira.plugin.s... ] Farah Juma commented on ELY-1663: --------------------------------- [~mchoma] Just noticed a small difference between the "not ok" and "ok" logs: For the "not ok" case: {code} 08:01:49,728 TRACE [org.wildfly.security] (MSC service thread 1-1) Supported protocols are: [TLSv1.2] {code} For the "ok" case: {code} 07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Supported protocols are: [TLSV1.2] {code} So "TLSv1.2" vs "TLSV1.2". > BC FIPS, Management Interface, ELY04001: No algorithm found matching TLS/SSL protocol selection criteria > -------------------------------------------------------------------------------------------------------- > > Key: ELY-1663 > URL: https://issues.jboss.org/browse/ELY-1663 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.6.0.Final > Reporter: Martin Choma > Priority: Critical > > Rarely 1:30 it happens there occures error accessing http management interface secured with TLS with BC FIPS > {code} > Operation {"operation" => "add","address" => [("subsystem" => "elytron"),("server-ssl-context" => "test-server-ssl-context")],"key-manager" => "key-manager-name_test-server-ssl-context","cipher-suite-filter" => "TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA256,TLS_DHE_DSS_WITH_AES_256_CBC_SHA,TLS_DHE_DSS_WITH_AES_256_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256","trust-manager" => "trust-manager-name_test-server-ssl-context","protocols" => ["TLSv1.2"],"need-client-auth" => true} failed: {"outcome" => "failed","failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.test-server-ssl-context" => "java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria > Caused by: java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria"}},"rolled-back" => true} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service org.wildfly.security.ssl-context.test-server-ssl-context: org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.test-server-ssl-context: java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria > at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:982) > at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria > at org.wildfly.security.ssl.SSLUtils.lambda$createSslContextFactory$1(SSLUtils.java:130) > at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:340) > at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53) > at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:980) > ... 9 more > {code} > Some facts > * It happens only on management interface BC FIPS TLS tests > * It does not occur on Undertow secured with BC FIPS > * Previously there was issue with similar error but that happened everywhere https://issues.jboss.org/browse/ELY-1618 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 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 September 2018