[JBoss JIRA] (WFLY-10985) UnsupportedOperationException thrown during start if CredentialReference is used in messaging-activemq subsystem
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFLY-10985?page=com.atlassian.jira.plugin... ]
ehsavoie Hugonnet commented on WFLY-10985:
------------------------------------------
Be careful to have the alias added to the credential store
/subsystem=elytron/credential-store=bridge-cs001:add(relative-to=jboss.server.data.dir, location=bridge-cs001.jceks,create=true,credential-reference={clear-text=pass123})
/subsystem=elytron/credential-store=bridge-cs001:add-alias(alias=john_out_alias_wrong, entry-type=org.wildfly.security.credential.PasswordCredential,secret-value=pass123)
before adding the bridge
> UnsupportedOperationException thrown during start if CredentialReference is used in messaging-activemq subsystem
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10985
> URL: https://issues.jboss.org/browse/WFLY-10985
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Reporter: Miroslav Novak
> Assignee: Jeff Mesnil
> Priority: Critical
> Attachments: standalone-full-ha.xml
>
>
> If messaging subsystem is referencing elytron's credential store like in:
> {code}
> <bridge name="myBridge" queue-name="jms.queue.InQueue" forwarding-address="jms.queue.OutQueue" ha="true" reconnect-attempts="-1" use-duplicate-detection="true" user="johnOut" static-connectors="bridge-connector">
> <credential-reference store="bridge-cs001" alias="john_out_alias_wrong"/>
> </bridge>
> {code}
> then during start server throws exception:
> {code}
> 12:49:04,367 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 66) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default")
> ]): java.lang.UnsupportedOperationException
> at org.jboss.msc.service.ServiceBuilderImpl.addDependency(ServiceBuilderImpl.java:409)
> at org.jboss.msc.service.DelegatingServiceBuilder.addDependency(DelegatingServiceBuilder.java:147)
> at org.jboss.as.controller.security.CredentialReference.getCredentialSourceSupplier(CredentialReference.java:323)
> at org.wildfly.extension.messaging.activemq.ServerAdd.addBridgeCredentialStoreReference(ServerAdd.java:732)
> at org.wildfly.extension.messaging.activemq.ServerAdd.access$200(ServerAdd.java:175)
> at org.wildfly.extension.messaging.activemq.ServerAdd$2.execute(ServerAdd.java:439)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
> 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:1349)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {code}
> Attaching standalone-full-ha.xml with which is possible to reproduce the issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2980) kie-pmml module has groupId org.drools
by Tibor Zimányi (JIRA)
Tibor Zimányi created DROOLS-2980:
-------------------------------------
Summary: kie-pmml module has groupId org.drools
Key: DROOLS-2980
URL: https://issues.jboss.org/browse/DROOLS-2980
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.11.0.Final
Reporter: Tibor Zimányi
Assignee: Lance Leverich
kie-pmml module has groupId org.drools. However other kie-* modules use org.kie. We should use org.kie also for kie-pmml.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-10669) MBean Support
by Bartosz Baranowski (JIRA)
[ https://issues.jboss.org/browse/WFLY-10669?page=com.atlassian.jira.plugin... ]
Bartosz Baranowski resolved WFLY-10669.
---------------------------------------
Assignee: Bartosz Baranowski (was: Jason Greene)
Resolution: Rejected
Any EAP related issues must be rised via access.redhat.com through valid subscription.
> MBean Support
> -------------
>
> Key: WFLY-10669
> URL: https://issues.jboss.org/browse/WFLY-10669
> Project: WildFly
> Issue Type: Bug
> Reporter: Karthik Babu
> Assignee: Bartosz Baranowski
> Attachments: DNBIJbossStatisticsService.java
>
>
> Hi,
> I have defined an mbean and deployed the same in .sar file using jboss 7.0.0 . But while accessing the same through jndiName (using org.springframework.jndi.JndiObjectFactoryBean) , it is throwing the following exception. could you please check and provide help in this regard. Same configuration seems to be working fine in jboss 6.3
> Attached the java file with the Mbean service defined.
> Inside Jboss-service.xml in sar file :
> <mbean code="com.dnbgp.monitoring.jmx.DNBIJbossStatisticsService"
> name="dnbi.external.dependency.statistics:service=DunsLinkJMXJNDI">
> </mbean>
> Inside applicationContext.xml :
> <bean id="DBCallsStatisticsService" class="org.springframework.jndi.JndiObjectFactoryBean">
> <property name="jndiName" value="DBCallsJMXJNDI" />
> </bean>
> Exception Received during the Jboss start up:
> 06:25:47,775 ERROR [org.springframework.web.struts.ContextLoaderPlugIn] (ServerService Thread Pool -- 86) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ProductOrderStatisticsService' defined in ServletContext resource [/WEB-INF/monitoringSpringApplicationContext.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: ProductOrderJMXJNDI -- service jboss.naming.context.java.ProductOrderJMXJNDI
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1482)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:521)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)
> at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295)
> at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)
> at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292)
> at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)
> at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:608)
> at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932)
> at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479)
> at org.springframework.web.struts.ContextLoaderPlugIn.createWebApplicationContext(ContextLoaderPlugIn.java:354)
> at org.springframework.web.struts.ContextLoaderPlugIn.initWebApplicationContext(ContextLoaderPlugIn.java:295)
> at org.springframework.web.struts.ContextLoaderPlugIn.init(ContextLoaderPlugIn.java:225)
> at org.apache.struts.action.ActionServlet.initModulePlugIns(ActionServlet.java:869)
> at org.apache.struts.action.ActionServlet.init(ActionServlet.java:350)
> at livexp.ui.web.EnhancedLiveXPActionServlet.init(EnhancedLiveXPActionServlet.java:263)
> at javax.servlet.GenericServlet.init(GenericServlet.java:244)
> at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:117)
> at org.wildfly.extension.undertow.security.RunAsLifecycleInterceptor.init(RunAsLifecycleInterceptor.java:78)
> at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:103)
> at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:239)
> at io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:133)
> at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:527)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:101)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: javax.naming.NameNotFoundException: ProductOrderJMXJNDI -- service jboss.naming.context.java.ProductOrderJMXJNDI
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:154)
> at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:87)
> at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:152)
> at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:178)
> at org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:95)
> at org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java:105)
> at org.springframework.jndi.JndiObjectFactoryBean.lookupWithFallback(JndiObjectFactoryBean.java:201)
> at org.springframework.jndi.JndiObjectFactoryBean.afterPropertiesSet(JndiObjectFactoryBean.java:187)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1541)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1479)
> ... 30 more
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (ELY-1622) BC FIPS with CLI: SunX509 KeyManagerFactory not available
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1622?page=com.atlassian.jira.plugin.s... ]
Martin Choma commented on ELY-1622:
-----------------------------------
??Note that the security-property won't affect the creation of the client SSLContext that's configured in the wildfly-config.xml file.??
Oh, sure, that was my mistake.
> BC FIPS with CLI: SunX509 KeyManagerFactory not available
> ---------------------------------------------------------
>
> Key: ELY-1622
> URL: https://issues.jboss.org/browse/ELY-1622
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.5.1.Final
> Reporter: Martin Choma
> Assignee: Farah Juma
> Priority: Blocker
> Fix For: 1.5.2.Final
>
> Attachments: cli-test-wildfly-config.xml, jboss-cli.log, truststore.bcfks
>
>
> I am trying to connect from jboss-cli.sh to EAP server. To reproduce the problem it is enough BC FIPS is used only on client side.
> {code:java|titlejboss-cli.log}
> 11:50:25,147 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:330)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:291)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Caused by: org.jboss.as.cli.CommandLineException: Failed to resolve host 'localhost'
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1256)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328)
> ... 5 more
> Caused by: java.io.IOException: Failed to obtain SSLContext
> at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:156)
> at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222)
> ... 8 more
> Caused by: java.security.KeyManagementException: java.security.NoSuchAlgorithmException: SunX509 KeyManagerFactory not available
> at org.bouncycastle.jsse.provider.ProvSSLContextSpi.selectKeyManager(ProvSSLContextSpi.java:589)
> at org.bouncycastle.jsse.provider.ProvSSLContextSpi.engineInit(ProvSSLContextSpi.java:531)
> at javax.net.ssl.SSLContext.init(SSLContext.java:282)
> at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:372)
> at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53)
> at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:221)
> at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:208)
> at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:153)
> ... 10 more
> Caused by: java.security.NoSuchAlgorithmException: SunX509 KeyManagerFactory not available
> at sun.security.jca.GetInstance.getInstance(GetInstance.java:159)
> at javax.net.ssl.KeyManagerFactory.getInstance(KeyManagerFactory.java:137)
> at org.bouncycastle.jsse.provider.ProvSSLContextSpi.selectKeyManager(ProvSSLContextSpi.java:583)
> ... 17 more
> {code}
> When I use non-FIPS java with CLI I can make it work. It does occure also when connecting to default unsecured port 9990.
> When I use BCFKS truststore on server side, e.g. in 2-way http communication it works.
> I believe problem is I cant configure algorithm for keymanager on client side in wildfly-config.xml. (At least I don't see how could I do so).
> BC provider does not know SunX509 arlgorithm, rather X509, X.509 or PKIX could be used.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2979) Test Scenario: unable to select rule defined in xlsx in EXPECTATION settings
by Hiroko Miura (JIRA)
Hiroko Miura created DROOLS-2979:
------------------------------------
Summary: Test Scenario: unable to select rule defined in xlsx in EXPECTATION settings
Key: DROOLS-2979
URL: https://issues.jboss.org/browse/DROOLS-2979
Project: Drools
Issue Type: Bug
Components: Test Scenarios Editor
Affects Versions: 7.7.0.Final
Environment: Red Hat Decision Manager 7.0.0
Reporter: Hiroko Miura
Assignee: Toni Rikkola
In Test Scenario editor, when setting EXPECTATION, rule which is defined in XLSX is not listed in selection list of rule like an attached image.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2978) Test Scenario: unable to select rule defined in xlsx in EXPECTATION settings
by Hiroko Miura (JIRA)
Hiroko Miura created DROOLS-2978:
------------------------------------
Summary: Test Scenario: unable to select rule defined in xlsx in EXPECTATION settings
Key: DROOLS-2978
URL: https://issues.jboss.org/browse/DROOLS-2978
Project: Drools
Issue Type: Bug
Components: Test Scenarios Editor
Affects Versions: 7.7.0.Final
Environment: Red Hat Decision Manager 7.0.0
Reporter: Hiroko Miura
Assignee: Toni Rikkola
Attachments: repo.zip, rule-selection-in-EXPECTATION.png
In Test Scenario editor, when setting EXPECTATION, rule which is defined in XLSX is not listed in selection list of rule like an attached image.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months