[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:
-----------------------------------
Ok, in my case setting {{export NSS_DEFAULT_DB_TYPE=dbm}} make it work.
Thanks Darran for hint.
> 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 Fedora 27 there was 3.33 https://fedora.pkgs.org/27/fedora-x86_64/nss-3.33.0-1.0.fc27.x86_64.rpm.html
> 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
[JBoss JIRA] (WFLY-9669) JMS bridge fails to create session factory with connection timeout between WildFly and EAP 6.4
by Tomas Hofman (JIRA)
[ https://issues.jboss.org/browse/WFLY-9669?page=com.atlassian.jira.plugin.... ]
Tomas Hofman resolved WFLY-9669.
--------------------------------
Resolution: Rejected
> JMS bridge fails to create session factory with connection timeout between WildFly and EAP 6.4
> ----------------------------------------------------------------------------------------------
>
> Key: WFLY-9669
> URL: https://issues.jboss.org/browse/WFLY-9669
> Project: WildFly
> Issue Type: Bug
> Components: IIOP, JMS
> Reporter: Lin Gao
> Assignee: Tomas Hofman
>
> When having configured JMS bridge on EAP 7 with target queue on EAP 6.4 after starting the server, after short while I can see that it failed to create session factory with exception \[1\].
> I am also attaching config files of EAP 6.4 server and of EAP 7.1.0.CR4 server.
> \[1\]
> {noformat}
> 2017-11-23 16:49:31,423 WARN [org.apache.activemq.artemis.jms.bridge] (Thread-230) AMQ342010: Failed to connect JMS Bridge N/A: javax.jms.JMSException: Failed to create session factory
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:673)
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:112)
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:107)
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.createConnection(JMSBridgeImpl.java:979)
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1148)
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.setupJMSObjectsWithRetry(JMSBridgeImpl.java:1247)
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.access$2600(JMSBridgeImpl.java:75)
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl$FailureHandler.run(JMSBridgeImpl.java:1747)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: HornetQConnectionTimedOutException[errorType=CONNECTION_TIMEDOUT message=HQ119013: Timed out waiting to receive cluster topology. Group:null]
> at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:946)
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:669)
> ... 10 more
> 2017-11-23 16:49:31,443 INFO [org.apache.activemq.artemis.jms.bridge] (Thread-230) AMQ341000: Failed to set up JMS bridge N/A connections. Most probably the source or target servers are unavailable. Will retry after a pause of 2,500 ms
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9669) JMS bridge fails to create session factory with connection timeout between WildFly and EAP 6.4
by Tomas Hofman (JIRA)
[ https://issues.jboss.org/browse/WFLY-9669?page=com.atlassian.jira.plugin.... ]
Tomas Hofman commented on WFLY-9669:
------------------------------------
Marking as rejected, see JBEAP-13840 for details.
> JMS bridge fails to create session factory with connection timeout between WildFly and EAP 6.4
> ----------------------------------------------------------------------------------------------
>
> Key: WFLY-9669
> URL: https://issues.jboss.org/browse/WFLY-9669
> Project: WildFly
> Issue Type: Bug
> Components: IIOP, JMS
> Reporter: Lin Gao
> Assignee: Tomas Hofman
>
> When having configured JMS bridge on EAP 7 with target queue on EAP 6.4 after starting the server, after short while I can see that it failed to create session factory with exception \[1\].
> I am also attaching config files of EAP 6.4 server and of EAP 7.1.0.CR4 server.
> \[1\]
> {noformat}
> 2017-11-23 16:49:31,423 WARN [org.apache.activemq.artemis.jms.bridge] (Thread-230) AMQ342010: Failed to connect JMS Bridge N/A: javax.jms.JMSException: Failed to create session factory
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:673)
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:112)
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:107)
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.createConnection(JMSBridgeImpl.java:979)
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1148)
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.setupJMSObjectsWithRetry(JMSBridgeImpl.java:1247)
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.access$2600(JMSBridgeImpl.java:75)
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl$FailureHandler.run(JMSBridgeImpl.java:1747)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: HornetQConnectionTimedOutException[errorType=CONNECTION_TIMEDOUT message=HQ119013: Timed out waiting to receive cluster topology. Group:null]
> at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:946)
> at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:669)
> ... 10 more
> 2017-11-23 16:49:31,443 INFO [org.apache.activemq.artemis.jms.bridge] (Thread-230) AMQ341000: Failed to set up JMS bridge N/A connections. Most probably the source or target servers are unavailable. Will retry after a pause of 2,500 ms
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3787) JMX audit logging should support all the handlers supported by core audit logging
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3787?page=com.atlassian.jira.plugi... ]
Darran Lofthouse commented on WFCORE-3787:
------------------------------------------
+1 To Brian's comment - [~jamezp] I know you raised some concerns about duplication as well during the Elytron integration.
I feel we may need to assemble a small team to finish off the future of auditing.
I don't think this Jira is going to a suitable location for a long discussion but I did have a discussion with Stuart a while back where he pointed out smaller subsystems give better slimming opportunities than big subsystems so that is also something I am going to explore this year with Elytron (With the related discussions). May even be able to look at some form of audit subsystem.
> JMX audit logging should support all the handlers supported by core audit logging
> ---------------------------------------------------------------------------------
>
> Key: WFCORE-3787
> URL: https://issues.jboss.org/browse/WFCORE-3787
> Project: WildFly Core
> Issue Type: Feature Request
> Components: JMX
> Affects Versions: 5.0.0.Alpha5
> Reporter: Yeray Borges
> Assignee: Yeray Borges
>
> Users can enable audit logging for the management interfaces, which will log all operations performed using the management console, management CLI, or custom application that uses the Management API.
> JMX subsystem can use the handlers defined for audit logging, but at this moment, only {{file-handler}} and {{syslog-handler}} can be used in JMX subsystem.
> This issue will extend the list of supported handlers for JMX subsystem to all handlers supported by core audit logging.
> The handlers supported by core audit logging are:
> * file-handler
> * in-memory-handler
> * periodic-rotating-file-handler
> * size-rotating-file-handler
> * syslog-handler
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-5574) org.wildfly.test.extension.rts InboundBridgeTestCase failing when transaction uses JTS
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/WFLY-5574?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris reassigned WFLY-5574:
-------------------------------------
Assignee: (was: Gytis Trikleris)
> org.wildfly.test.extension.rts InboundBridgeTestCase failing when transaction uses JTS
> --------------------------------------------------------------------------------------
>
> Key: WFLY-5574
> URL: https://issues.jboss.org/browse/WFLY-5574
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite, Transactions
> Affects Versions: 10.0.0.CR3
> Reporter: Ondra Chaloupka
> Priority: Minor
> Attachments: server.log
>
>
> There is failures in testcase org.wildfly.test.extension.rts.InboundBridgeTestCase when transaction uses JTS.
> Example of the failure
> {code}
> testCommit(org.wildfly.test.extension.rts.InboundBridgeTestCase) Time elapsed: 2.54 sec <<< FAILURE!
> java.lang.AssertionError: expected:<4> but was:<5>
> {code}
> The JBOSS_HOME distribution is change to transaction to be run with JTS: changing the {{docs/example/standalone-rts.xml}} to switch transactions parameter in iiop orb subsystem to {{full}} and adding {{jts}} element to transactions subsystem.
> When JBOSS_HOME is set then I've run the test in this way
> {{./integration-tests.sh clean install -Dts.noSmoke -Dts.rts -Djboss.dist=$JBOSS_HOME -Dtest=InboundBridgeTestCase}}
--
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 edited comment on ELY-1578 at 5/11/18 5:32 AM:
------------------------------------------------------------
[~rlucente-se-jboss] and how does your pkcs11.cfg looks like then? Do you have to use dbm: prefix there? E.g. nssSecmodDirectory = dbm:$HOME/fipsdb ?
And which version of nss do you use?
I have recreated fipsdb with these commands, but I run into same error
was (Author: mchoma):
[~rlucente-se-jboss] and how does your pkcs11.cfg looks like then? Do you have to use dbm: prefix there? E.g. nssSecmodDirectory = dbm:$HOME/fipsdb ?
> 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 Fedora 27 there was 3.33 https://fedora.pkgs.org/27/fedora-x86_64/nss-3.33.0-1.0.fc27.x86_64.rpm.html
> 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
[JBoss JIRA] (SWSQE-202) Complete Cloud definition for b15.jonqe.lab.eng.bos.redhat.com on Jenkins2
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/SWSQE-202?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on SWSQE-202:
----------------------------------
Would be good to get this fixed asap, as we need it to run automated approval tests for the Jaeger container images. There is currently a new version of the images (1.4.1), where I have used a different productisation approach, so would like to check that this has all worked properly.
> Complete Cloud definition for b15.jonqe.lab.eng.bos.redhat.com on Jenkins2
> --------------------------------------------------------------------------
>
> Key: SWSQE-202
> URL: https://issues.jboss.org/browse/SWSQE-202
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Kevin Earls
> Assignee: Michael Foley
> Priority: Blocker
>
> In order to be able to complete https://issues.jboss.org/browse/KIALI-336 I need to be able to launch tests on B15 from Jenkins2. I have created a new entry named b15.jonqe.lab.eng.bos.redhat.com under Manage Jenkins -> Configure System but was not able to get it to connect. The following items are still required
> 1. This entry needs to be configured so it can connect in the same way that the B21 entry does. The "Kubernetes server certificate key" needs to be added, as well as proper credentials.
> 2. A kubernetes pod template needs to be added, similar to the jenkins-slave-maven entry that exists for B21. Names should be updated so it is clear which cluster these are running on.
> 3. A "jaeger-test" project should be created on B15, and it should be recreated whenever that cluster is recreated.
--
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 commented on ELY-1578:
-----------------------------------
[~rlucente-se-jboss] and how does your pkcs11.cfg looks like then? Do you have to use dbm: prefix there? E.g. nssSecmodDirectory = dbm:$HOME/fipsdb ?
> 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 Fedora 27 there was 3.33 https://fedora.pkgs.org/27/fedora-x86_64/nss-3.33.0-1.0.fc27.x86_64.rpm.html
> 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
[JBoss JIRA] (WFCORE-3830) JAVA_OPTS is not passed to DC and HC JVMs in domain.ps1
by Marek Kopecký (JIRA)
Marek Kopecký created WFCORE-3830:
-------------------------------------
Summary: JAVA_OPTS is not passed to DC and HC JVMs in domain.ps1
Key: WFCORE-3830
URL: https://issues.jboss.org/browse/WFCORE-3830
Project: WildFly Core
Issue Type: Bug
Components: Scripts
Reporter: Marek Kopecký
Assignee: Kabir Khan
Priority: Critical
JAVA_OPTS is not passed to DC and HC JVMs in domain.ps1
Steps to reproduce:
# start powershell
# $env:JAVA_OPTS = "-Da=b"
# ./domain.bat
# WMIC PROCESS get Commandline | findstr java
# check that "a" property is present in DC or HC
# exit domain.bat
# ./domain.ps1
# WMIC PROCESS get Commandline | findstr java
# check that "a" property is *not* present in DC or HC
cc: [~jamezp]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months