[JBoss JIRA] (ELY-1578) Upgrade to Fedora 28 breaks FIPS scenarios
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1578?page=com.atlassian.jira.plugin.s... ]
Martin Choma commented on ELY-1578:
-----------------------------------
[~fjuma][~honza889][~rlucente-se-jboss] Any hints how to came over this problem? I will continue with investigation on Monday. But seems this will be the big topic.
> 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]
> 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
[JBoss JIRA] (ELY-1578) Upgrade to Fedora 28 breaks FIPS scenarios
by Martin Choma (JIRA)
Martin Choma created ELY-1578:
---------------------------------
Summary: 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
Assignee: Darran Lofthouse
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]
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
[JBoss JIRA] (ELY-1578) Upgrade to Fedora 28 breaks FIPS scenarios
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1578?page=com.atlassian.jira.plugin.s... ]
Martin Choma reassigned ELY-1578:
---------------------------------
Assignee: (was: Darran Lofthouse)
> 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]
> 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
[JBoss JIRA] (WFLY-9604) wildfly-11.0.0.Final JPA
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/WFLY-9604?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero closed WFLY-9604.
---------------------------------
> wildfly-11.0.0.Final JPA
> ------------------------
>
> Key: WFLY-9604
> URL: https://issues.jboss.org/browse/WFLY-9604
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: 11.0.0.Final
> Environment: Javaee 7, Windows 7, jdk 8 151
> Reporter: Trond Arild Lode Tobiassen Heidelberg
>
> I am deploying to above. I get this error message:
>
> {"jboss.persistenceunit.registrar#REGDB" => "org.hibernate.AnnotationException: Property no.tobiassenit.sipstack.sip.message.AbstractMessage.part has an unbound type and no explicit target entity. Resolve this Generic usage issue or set an explicit target attribute (eg @OneToMany(target=) or use an explicit @Type Caused by: org.hibernate.AnnotationException: Property no.tobiassenit.sipstack.sip.message.AbstractMessage.part has an unbound type and no explicit target entity. Resolve this Generic usage issue or set an explicit target attribute (eg @OneToMany(target=) or use an explicit @Type"},
>
>
> I have this code:
>
> @OneToOne(optional = true, cascade = CascadeType.ALL, targetEntity = AbstractPart.class)
> @JoinColumn(name = "PART", unique = false, nullable = true, updatable = false)
> protected X part;
> What about the target= vs the targetEntity=? There is no target attribute or @Type annotation available.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9604) wildfly-11.0.0.Final JPA
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/WFLY-9604?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero resolved WFLY-9604.
-----------------------------------
Resolution: Rejected
Labels: (was: task)
> wildfly-11.0.0.Final JPA
> ------------------------
>
> Key: WFLY-9604
> URL: https://issues.jboss.org/browse/WFLY-9604
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: 11.0.0.Final
> Environment: Javaee 7, Windows 7, jdk 8 151
> Reporter: Trond Arild Lode Tobiassen Heidelberg
>
> I am deploying to above. I get this error message:
>
> {"jboss.persistenceunit.registrar#REGDB" => "org.hibernate.AnnotationException: Property no.tobiassenit.sipstack.sip.message.AbstractMessage.part has an unbound type and no explicit target entity. Resolve this Generic usage issue or set an explicit target attribute (eg @OneToMany(target=) or use an explicit @Type Caused by: org.hibernate.AnnotationException: Property no.tobiassenit.sipstack.sip.message.AbstractMessage.part has an unbound type and no explicit target entity. Resolve this Generic usage issue or set an explicit target attribute (eg @OneToMany(target=) or use an explicit @Type"},
>
>
> I have this code:
>
> @OneToOne(optional = true, cascade = CascadeType.ALL, targetEntity = AbstractPart.class)
> @JoinColumn(name = "PART", unique = false, nullable = true, updatable = false)
> protected X part;
> What about the target= vs the targetEntity=? There is no target attribute or @Type annotation available.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9604) wildfly-11.0.0.Final JPA
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/WFLY-9604?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero commented on WFLY-9604:
---------------------------------------
This is either a mapping problem or a bug in Hibernate. Please use the Hibernate forums for such issues: https://discourse.hibernate.org/
> wildfly-11.0.0.Final JPA
> ------------------------
>
> Key: WFLY-9604
> URL: https://issues.jboss.org/browse/WFLY-9604
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: 11.0.0.Final
> Environment: Javaee 7, Windows 7, jdk 8 151
> Reporter: Trond Arild Lode Tobiassen Heidelberg
> Labels: task
>
> I am deploying to above. I get this error message:
>
> {"jboss.persistenceunit.registrar#REGDB" => "org.hibernate.AnnotationException: Property no.tobiassenit.sipstack.sip.message.AbstractMessage.part has an unbound type and no explicit target entity. Resolve this Generic usage issue or set an explicit target attribute (eg @OneToMany(target=) or use an explicit @Type Caused by: org.hibernate.AnnotationException: Property no.tobiassenit.sipstack.sip.message.AbstractMessage.part has an unbound type and no explicit target entity. Resolve this Generic usage issue or set an explicit target attribute (eg @OneToMany(target=) or use an explicit @Type"},
>
>
> I have this code:
>
> @OneToOne(optional = true, cascade = CascadeType.ALL, targetEntity = AbstractPart.class)
> @JoinColumn(name = "PART", unique = false, nullable = true, updatable = false)
> protected X part;
> What about the target= vs the targetEntity=? There is no target attribute or @Type annotation available.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10325) Test Suite: Integration - Web failures with -Djboss.dist
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10325?page=com.atlassian.jira.plugin... ]
Petr Kremensky commented on WFLY-10325:
---------------------------------------
{{ssl-cert-realm}} is created by WebCERTTestsSecurityDomainSetup, but is never removed by the tearDown.
> Test Suite: Integration - Web failures with -Djboss.dist
> --------------------------------------------------------
>
> Key: WFLY-10325
> URL: https://issues.jboss.org/browse/WFLY-10325
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Petr Kremensky
> Assignee: Jan Stourac
>
> Web integration tests start to fail once I point the testsuite a distribution via jboss.dist property (the property is used to run the tests against productized builds or patched EAP distributions).
> *reproduce*
> {noformat}
> git clone https://github.com/wildfly/wildfly.git ; cd wildfly
> mvn clean install -DskipTests
> cd testsuite
> mvn test -B -pl integration/web/
> # Tests run: 112, Failures: 0, Errors: 0, Skipped: 3
> mvn test -B -pl integration/web/ -Djboss.dist=$(realpath ../dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT)
> # Tests run: 109, Failures: 4, Errors: 9, Skipped: 3
> {noformat}
> There seems to be an issue with *WebCERTTestsSetup*, as once I enable the logs ( -DtestLogToFile=false ), the following errors appear.
> {noformat}
> 10:57:09,622 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("security-realm" => "ssl-cert-realm")
> ]) - failure description: {
> "WFLYCTL0080: Failed services" => {"org.wildfly.core.management.security.realm.ssl-cert-realm.key-manager" => "Failed to start service
> Caused by: java.lang.IllegalStateException: org.jboss.msc.service.StartException in anonymous service: WFLYDM0086: The KeyStore can not be found at /home/hudson/hudson_workspace/wildfly/testsuite/integration/web/target/WebCERTTestsSetup/server.keystore
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYDM0086: The KeyStore can not be found at /home/hudson/hudson_workspace/wildfly/testsuite/integration/web/target/WebCERTTestsSetup/server.keystore"},
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10325) Test Suite: Integration - Web failures with -Djboss.dist
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10325?page=com.atlassian.jira.plugin... ]
Petr Kremensky reassigned WFLY-10325:
-------------------------------------
Assignee: Jan Stourac (was: Petr Kremensky)
> Test Suite: Integration - Web failures with -Djboss.dist
> --------------------------------------------------------
>
> Key: WFLY-10325
> URL: https://issues.jboss.org/browse/WFLY-10325
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Petr Kremensky
> Assignee: Jan Stourac
>
> Web integration tests start to fail once I point the testsuite a distribution via jboss.dist property (the property is used to run the tests against productized builds or patched EAP distributions).
> *reproduce*
> {noformat}
> git clone https://github.com/wildfly/wildfly.git ; cd wildfly
> mvn clean install -DskipTests
> cd testsuite
> mvn test -B -pl integration/web/
> # Tests run: 112, Failures: 0, Errors: 0, Skipped: 3
> mvn test -B -pl integration/web/ -Djboss.dist=$(realpath ../dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT)
> # Tests run: 109, Failures: 4, Errors: 9, Skipped: 3
> {noformat}
> There seems to be an issue with *WebCERTTestsSetup*, as once I enable the logs ( -DtestLogToFile=false ), the following errors appear.
> {noformat}
> 10:57:09,622 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("security-realm" => "ssl-cert-realm")
> ]) - failure description: {
> "WFLYCTL0080: Failed services" => {"org.wildfly.core.management.security.realm.ssl-cert-realm.key-manager" => "Failed to start service
> Caused by: java.lang.IllegalStateException: org.jboss.msc.service.StartException in anonymous service: WFLYDM0086: The KeyStore can not be found at /home/hudson/hudson_workspace/wildfly/testsuite/integration/web/target/WebCERTTestsSetup/server.keystore
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYDM0086: The KeyStore can not be found at /home/hudson/hudson_workspace/wildfly/testsuite/integration/web/target/WebCERTTestsSetup/server.keystore"},
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10326) Add setting to control global disk usage for messaging journal
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-10326?page=com.atlassian.jira.plugin... ]
Jeff Mesnil moved EAP7-995 to WFLY-10326:
-----------------------------------------
Project: WildFly (was: EAP 7 Planning Pilot)
Key: WFLY-10326 (was: EAP7-995)
Issue Type: Feature Request (was: Requirement)
Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0)
Component/s: JMS
(was: JMS)
Target Release: (was: 7.2.0.GA)
Release Notes Docs Status: (was: Documented as Feature Request)
> Add setting to control global disk usage for messaging journal
> --------------------------------------------------------------
>
> 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