May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-174) Openshift Clusters

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-174?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-174: ------------------------------- Team: Infrastructure (was: Infrastructure) Sprint: Kiali QE Sprint 5 (was: Kiali QE Sprint 4) > Openshift Clusters > ------------------ > > Key: SWSQE-174 > URL: https://issues.jboss.org/browse/SWSQE-174 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Priority: Critical > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-69) Investigate RH-SSO continuous productization

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-69?page=com.atlassian.jira.plugin.s... ] Matt Mahoney updated SWSQE-69: ------------------------------ Team: Infrastructure (was: Infrastructure) Sprint: SWS QE Sprint 2, Kiali QE Sprint 5 (was: SWS QE Sprint 2, Kiali QE Sprint 4) > Investigate RH-SSO continuous productization > -------------------------------------------- > > Key: SWSQE-69 > URL: https://issues.jboss.org/browse/SWSQE-69 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > > From meastman: > Whatever we come up with needs to be compatible or we at least know why we have to be > different. > From theute: > FYI, this describes the RH-SSO continuous productization: https://docs.engineering.redhat.com/display/JP/Design+document+RH-SSO+con... > RH-SSO is the guinea pig but we'll want to pick from their experience and tools to also get to a point where possibly each PR merge gets productized (means fully automated) and that would include testing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10329) Have JipiJapa enable Hibernate Search backward compatibility properties

by Sanne Grinovero (JIRA)

Sanne Grinovero created WFLY-10329: -------------------------------------- Summary: Have JipiJapa enable Hibernate Search backward compatibility properties Key: WFLY-10329 URL: https://issues.jboss.org/browse/WFLY-10329 Project: WildFly Issue Type: Task Reporter: Sanne Grinovero Assignee: Scott Marlow For Hibernate Search 5.10.x to be fully backwards compatible with the previous versions included in WildFly, we need the following property to be set by default among the Hibernate ORM configuration properties: {code} hibernate.search.index_uninverting_allowed=true {code} When set to true and the mapping actually makes use of this feature, a warning will be logged. We probably will want to document this as well: recommend users to set it to "false" explicitly, as relying on this feature has a performance penalty, yet no relying on it requires mapping changes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10327) Upgrade Hibernate ORM to 5.3.0.Final and Hibernate Search to 5.10.0.CR1

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-10327?page=com.atlassian.jira.plugin... ] Sanne Grinovero updated WFLY-10327: ----------------------------------- Summary: Upgrade Hibernate ORM to 5.3.0.Final and Hibernate Search to 5.10.0.CR1 (was: Upgrade Hibernate ORM to 5.3.0.Final) > Upgrade Hibernate ORM to 5.3.0.Final and Hibernate Search to 5.10.0.CR1 > ----------------------------------------------------------------------- > > Key: WFLY-10327 > URL: https://issues.jboss.org/browse/WFLY-10327 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10327) Upgrade Hibernate ORM to 5.3.0.Final and Hibernate Search to 5.10.0.CR1

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-10327?page=com.atlassian.jira.plugin... ] Sanne Grinovero updated WFLY-10327: ----------------------------------- Description: The Hibernate ORM and Hibernate Search update should happen at the same time as they are coupled. > Upgrade Hibernate ORM to 5.3.0.Final and Hibernate Search to 5.10.0.CR1 > ----------------------------------------------------------------------- > > Key: WFLY-10327 > URL: https://issues.jboss.org/browse/WFLY-10327 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > > The Hibernate ORM and Hibernate Search update should happen at the same time as they are coupled. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1578) Upgrade to Fedora 28 breaks FIPS scenarios

by Rich Lucente (JIRA)

[ https://issues.jboss.org/browse/ELY-1578?page=com.atlassian.jira.plugin.s... ] Rich Lucente commented on ELY-1578: ----------------------------------- https://bugs.openjdk.java.net/browse/JDK-8165996 with a commit from last December to address it. > Upgrade to Fedora 28 breaks FIPS scenarios > ------------------------------------------ > > Key: ELY-1578 > URL: https://issues.jboss.org/browse/ELY-1578 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.3.1.Final > Reporter: Martin Choma > > On Fedora 28 I get > {code} > 14:52:28,813 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.as: org.jboss.msc.service.StartException in service jboss.as: Failed to start service > at org.jboss.msc@1.3.2.Final-redhat-1//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1706) > at org.jboss.msc@1.3.2.Final-redhat-1//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.base/java.lang.Thread.run(Thread.java:844) > Caused by: java.security.ProviderException: NSS module not available: fips > at jdk.crypto.cryptoki/sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:278) > at jdk.crypto.cryptoki/sun.security.pkcs11.SunPKCS11$1.run(SunPKCS11.java:113) > at jdk.crypto.cryptoki/sun.security.pkcs11.SunPKCS11$1.run(SunPKCS11.java:110) > at java.base/java.security.AccessController.doPrivileged(Native Method) > at jdk.crypto.cryptoki/sun.security.pkcs11.SunPKCS11.configure(SunPKCS11.java:110) > at java.base/sun.security.jca.ProviderConfig$3.run(ProviderConfig.java:247) > at java.base/sun.security.jca.ProviderConfig$3.run(ProviderConfig.java:238) > at java.base/java.security.AccessController.doPrivileged(Native Method) > at java.base/sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:238) > at java.base/sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:218) > at java.base/sun.security.jca.ProviderList.getProvider(ProviderList.java:266) > at java.base/sun.security.jca.ProviderList.getService(ProviderList.java:379) > at java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:157) > at java.base/java.security.Security.getImpl(Security.java:697) > at java.base/java.security.MessageDigest.getInstance(MessageDigest.java:178) > at org.jboss.as.deployment-repository(a)5.0.0.Alpha-redhat-20180502//org.jboss.as.repository.ContentRepositoryImpl.<init>(ContentRepositoryImpl.java:90) > at org.jboss.as.deployment-repository@5.0.0.Alpha-redhat-20180502//org.jboss.as.repository.ContentRepository$Factory.addService(ContentRepository.java:185) > at org.jboss.as.server@5.0.0.Alpha-redhat-20180502//org.jboss.as.server.ApplicationServerService.start(ApplicationServerService.java:144) > at org.jboss.msc@1.3.2.Final-redhat-1//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) > at org.jboss.msc@1.3.2.Final-redhat-1//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > ... 6 more > {code} > In Fedora 28 there is nss 3.36.1 (dnf info nss.x86_64) > In nss 3.35 there was switch of format to SQL [1] > ??Applications using NSS may explicitly request to use a specific database format, by adding a type prefix to the database directory, provided at NSS initialization time. ?? > But I am not sure how to define that in java. I am using > {code:pkcs11.cfg} > name = testPkcs > nssLibraryDirectory = /usr/lib64 > nssSecmodDirectory = /opt/java/jdk-9.0.1_fips/fips/nssdb > nssDbMode = readOnly > nssModule = fips > {code} > I am awaer there is probably nothing that can be done in Elytron. I think it is matter of NSS/SunPKCS11 configuration. I create this JIRA as a place for finding out what the problem is. > [1] https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.35_re... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10106) Problem with @Schedule and daylight-saving time

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFLY-10106?page=com.atlassian.jira.plugin... ] Yeray Borges reassigned WFLY-10106: ----------------------------------- Assignee: Yeray Borges > Problem with @Schedule and daylight-saving time > ----------------------------------------------- > > Key: WFLY-10106 > URL: https://issues.jboss.org/browse/WFLY-10106 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 12.0.0.Final > Reporter: Christoph Erni > Assignee: Yeray Borges > > The method anotated with @Schedule is executed repeatedly just before entering the day of daylight-saving time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10326) Add setting to control global memory usage for messaging servers

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-10326?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-10326: ------------------------------- Summary: Add setting to control global memory usage for messaging servers (was: Add setting to control global disk usage for messaging servers) > Add setting to control global memory usage for messaging servers > ---------------------------------------------------------------- > > Key: WFLY-10326 > URL: https://issues.jboss.org/browse/WFLY-10326 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Labels: Previous_RFE > > Please see https://issues.apache.org/jira/browse/ARTEMIS-581 > Artemis defines given max amount of memory for each queue (max-size-bytes). If this amount if reached then one of the defined policies BLOCK, PAGE, FAIL or DROP is applied to newly incoming messages. > Problem is that with 400 queues and max-size-bytes=10MB, this would require 4 GB of heap memory to avoid OutOfMemoryError and crash of EAP 7 server. Thus new attribute global-max-size should be added to limit how much memory Artemis queues can consume before applying policies BLOCK, PAGE, FAIL or DROP. > There is also no check how much disk space Artemis journal is consuming. Which should be limited. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3802) Add main-class to the org.jboss.jandex module.xml to make it easier to run jandex

by Bartosz Spyrko-Śmietanko (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3802?page=com.atlassian.jira.plugi... ] Bartosz Spyrko-Śmietanko moved WFLY-1524 to WFCORE-3802: -------------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-3802 (was: WFLY-1524) Component/s: Server (was: Server) Affects Version/s: (was: 8.0.0.Alpha1) > Add main-class to the org.jboss.jandex module.xml to make it easier to run jandex > --------------------------------------------------------------------------------- > > Key: WFCORE-3802 > URL: https://issues.jboss.org/browse/WFCORE-3802 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Brad Maxwell > Assignee: Jason Greene > Priority: Minor > > Adding main-class will let JBoss Modules know the class to run and allow you to run jandex via java -jar $JBOSS_HOME/jboss-modules -mp $JBOSS_HOME/modules org.jboss.jandex > <module xmlns="urn:jboss:module:1.1" name="org.jboss.jandex"> > ... > <main-class name="org.jboss.jandex.Main"/> > ... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10328) New DataSource subsytem based on Agroal connection pool

by Luis Barreiro (JIRA)

Luis Barreiro created WFLY-10328: ------------------------------------ Summary: New DataSource subsytem based on Agroal connection pool Key: WFLY-10328 URL: https://issues.jboss.org/browse/WFLY-10328 Project: WildFly Issue Type: Feature Request Reporter: Luis Barreiro The performance team has developed an alternative to the datasource subsystem that does not rely on JCA, thus enabling applications that don't need it to remove the full JCA container. It has support for XA transactions and provides better performance over the current pooling implementation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2018