December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4779) Persisting an empty list [] gets read as a list with empty string [""] resulting in IllegalArgumentException

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4779?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4779. ---------------------------- > Persisting an empty list [] gets read as a list with empty string [""] resulting in IllegalArgumentException > ------------------------------------------------------------------------------------------------------------ > > Key: WFLY-4779 > URL: https://issues.jboss.org/browse/WFLY-4779 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 9.0.0.CR2, 10.0.0.Alpha2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 9.0.0.Final, 10.0.0.Alpha4 > > > Affects at least infinispan aliases and modcluster proxies... > (20:09:22) rhusar: pferraro: https://gist.github.com/rhusar/5eef22d7a6479f042a5d#file-gistfile1-txt-L23 > (20:09:34) rhusar: pferraro: if i write an empy list, read it back -> empty list > (20:09:57) rhusar: pferraro: if i use the default writeAttribute, reload, read it back and i have a list of size 1 containing empty String.. > (20:23:23) rhusar: pferraro: alright, this is also "broken" in the infiinispan subsystem aliases > (20:23:24) rhusar: pferraro: 20:22:55,775 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 40) WFLYCTL0013: Operation ("add") failed - address: ([ > (20:23:24) rhusar: ("subsystem" => "infinispan"), > (20:23:24) rhusar: ("cache-container" => "hibernate") > (20:23:24) rhusar: ]): java.lang.IllegalArgumentException: Empty name segment is not allowed for infinispan > (20:23:24) rhusar: at org.jboss.msc.service.ServiceName.of(ServiceName.java:90) > (20:23:24) rhusar: at org.jboss.msc.service.ServiceName.append(ServiceName.java:117) > (20:23:24) rhusar: at org.wildfly.clustering.infinispan.spi.service.CacheContainerServiceName$1.getServiceName(CacheContainerServiceName.java:35) > (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.build(CacheContainerBuilder.java:79) > (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerAddHandler.installRuntimeServices(CacheContainerAddHandler.java:165) > (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerAddHandler.performRuntime(CacheContainerAddHandler.java:82) > (20:23:24) rhusar: at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:309) > (20:23:24) rhusar: at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:130) > (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:822) > (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:620) > (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:373) > (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:349) > (20:23:24) rhusar: at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:359) > (20:23:24) rhusar: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > (20:23:24) rhusar: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > (20:23:24) rhusar: at java.lang.Thread.run(Thread.java:745) > (20:23:24) rhusar: at org.jboss.threads.JBossThread.run(JBossThread.java:320) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4656) Export dependency for "javax.jms.api" in org.jboss.genericjms module

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4656?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4656. ---------------------------- > Export dependency for "javax.jms.api" in org.jboss.genericjms module > -------------------------------------------------------------------- > > Key: WFLY-4656 > URL: https://issues.jboss.org/browse/WFLY-4656 > Project: WildFly > Issue Type: Feature Request > Components: JCA, JMS > Affects Versions: 9.0.0.CR1, 10.0.0.Alpha1 > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha5 > > > More info in WFLY-4642. > If deployment with MDB has dependency to module "org.jboss.genericjms" then module "javax.jms.api" is not loaded for the deployment and deploy fails. > This is a change in module loading behaviour against previous versions of Wildfly/EAP and complicates migration/usability. > We can avoid this by exporting "javax.jms.api" dependency in "org.jboss.genericjms" module. It should look like: > {code} > <module xmlns="urn:jboss:module:1.3" name="org.jboss.genericjms"> > ... > <dependencies> > ... > <module name="javax.jms.api" slot="main" export="true"/> > ... > </dependencies> > </module> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5143) JGroups subsystem parser should not allow thread pool to be defined per protocol

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5143?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5143. ---------------------------- > JGroups subsystem parser should not allow thread pool to be defined per protocol > -------------------------------------------------------------------------------- > > Key: WFLY-5143 > URL: https://issues.jboss.org/browse/WFLY-5143 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 10.0.0.CR1 > > > In this case, the parser does not match the schemas. There are 3 issues here: > # Thread pool elements should only be parsed for schema version >= 3.0 > # Thread pool elements are only valid children of a <transport/> element, but are currently accepted as children of a <protocol/> element. > # We should always create thread pool resources, even if xml is undefined - that way the thread pool parameters, as applied to the runtime, are expressed in the model. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5221) TimerServiceTimerService.getTimers() returns not only the associated timer entries for the current Bean

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5221?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5221. ---------------------------- > TimerServiceTimerService.getTimers() returns not only the associated timer entries for the current Bean > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-5221 > URL: https://issues.jboss.org/browse/WFLY-5221 > Project: WildFly > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Assignee: Stuart Douglas > Priority: Blocker > Fix For: 10.0.0.CR1 > > > According to the spec [1] the getTimers() method must only return timers associated to the current EJB. > This is a huge issue if timers are cancled by this collection as it will remove all timers! > [1] https://docs.oracle.com/javaee/6/api/javax/ejb/TimerService.html#getTimer... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4339) NPE when deployment contains a *-ds.xml in domain

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4339?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4339. ---------------------------- > NPE when deployment contains a *-ds.xml in domain > ------------------------------------------------- > > Key: WFLY-4339 > URL: https://issues.jboss.org/browse/WFLY-4339 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.2.0.Final > Reporter: James Perkins > Assignee: Stefano Maestri > Fix For: 10.0.0.Beta2 > > > If you build the [kitchen-sink quickstart|https://github.com/wildfly/quickstart/tree/master/kitchensink] and attempt to deploy to domain servers you'll see the following error. Same deployment works fine in standalone. > {code} > [Server:server-one] 09:25:06,563 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-14) MSC000001: Failed to start service jboss.data-source.java:jboss/datasources/KitchensinkQuickstartDS: org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/KitchensinkQuickstartDS: WFLYJCA0033: Error during the deployment of java:jboss/datasources/KitchensinkQuickstartDS > [Server:server-one] at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:142) > [Server:server-two] 09:25:06,563 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.data-source.java:jboss/datasources/KitchensinkQuickstartDS: org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/KitchensinkQuickstartDS: WFLYJCA0033: Error during the deployment of java:jboss/datasources/KitchensinkQuickstartDS > [Server:server-two] at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:142) > [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [Server:server-two] at java.lang.Thread.run(Thread.java:745) > [Server:server-two] Caused by: java.lang.NullPointerException > [Server:server-two] at org.jboss.as.connector.services.driver.registry.DriverRegistryImpl.getInstalledDriver(DriverRegistryImpl.java:93) > [Server:server-two] at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:324) > [Server:server-two] at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:135) > [Server:server-two] ... 5 more > [Server:server-two] > [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [Server:server-one] at java.lang.Thread.run(Thread.java:745) > [Server:server-one] Caused by: java.lang.NullPointerException > [Server:server-one] at org.jboss.as.connector.services.driver.registry.DriverRegistryImpl.getInstalledDriver(DriverRegistryImpl.java:93) > [Server:server-one] at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:324) > [Server:server-one] at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:135) > [Server:server-one] ... 5 more > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5278) default path for SSO should be /

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5278?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5278. ---------------------------- > default path for SSO should be / > -------------------------------- > > Key: WFLY-5278 > URL: https://issues.jboss.org/browse/WFLY-5278 > Project: WildFly > Issue Type: Enhancement > Components: Web (Undertow) > Affects Versions: 10.0.0.Beta2 > Reporter: Radim Hatlapatka > Assignee: Tomaz Cerar > Priority: Blocker > Fix For: 10.0.0.CR1 > > > Single Sign On doesn't work for two web applications with different context name. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5260) Cannot inject TransactionSynchronizationRegistry into CDI bean

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5260?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5260. ---------------------------- > Cannot inject TransactionSynchronizationRegistry into CDI bean > -------------------------------------------------------------- > > Key: WFLY-5260 > URL: https://issues.jboss.org/browse/WFLY-5260 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 10.0.0.Beta2 > Reporter: Tomas Remes > Assignee: Martin Kouba > Fix For: 10.0.0.CR1 > > > It's not possible to inject TransactionSynchronizationRegistry to CDI bean as follows: > {code} > @ApplicationScoped > public class CdiBean { > @Resource > TransactionSynchronizationRegistry transactionSynchronizationRegistry; > } > {code} > This results to: > {noformat} > java.lang.IllegalArgumentException: WFLYWELD0049: Error injecting resource into CDI managed bean. Can't find a resource named java:comp/env/org.jboss.as.test.integration.weld.jta.CdiBean/transactionSynchronizationRegistry defined on javax.transaction.TransactionSynchronizationRegistry org.jboss.as.test.integration.weld.jta.CdiBean.transactionSynchronizationRegistry > 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.NamingContext.lookup(NamingContext.java:184) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:237) > 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.jboss.as.weld.services.bootstrap.WeldResourceInjectionServices.resolveResource(WeldResourceInjectionServices.java:210) > at org.jboss.as.weld.services.bootstrap.WeldResourceInjectionServices$1.createResource(WeldResourceInjectionServices.java:158) > at org.jboss.weld.injection.AbstractResourceInjection.getResourceReference(AbstractResourceInjection.java:44) > at org.jboss.weld.injection.AbstractResourceInjection.injectResourceReference(AbstractResourceInjection.java:53) > at org.jboss.weld.util.Beans.injectEEFields(Beans.java:351) > at org.jboss.weld.injection.producer.ResourceInjector$1.proceed(ResourceInjector.java:69) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:72) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:121) > at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:159) > at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) > at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101) > at org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141) > at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) > at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:99) > at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:125) > at org.jboss.as.test.integration.weld.jta.CdiBean$Proxy$_$$_WeldClientProxy.isTransactionSynchronizationRegistryInjected(Unknown Source) > at org.jboss.as.test.integration.weld.jta.TransactionSynchronizationRegistryInjectionTestCase.testTransactionSynchronizationRegistryIsInjected(TransactionSynchronizationRegistryInjectionTestCase.java:30) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5146) Expose Infinispan's remoteCommandExecutor thread pool configuration

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5146?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5146. ---------------------------- > Expose Infinispan's remoteCommandExecutor thread pool configuration > ------------------------------------------------------------------- > > Key: WFLY-5146 > URL: https://issues.jboss.org/browse/WFLY-5146 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 10.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5070) @WebServlet.loadOnStartup=0 doesn't startup the servlet

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5070?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5070. ---------------------------- > @WebServlet.loadOnStartup=0 doesn't startup the servlet > ------------------------------------------------------- > > Key: WFLY-5070 > URL: https://issues.jboss.org/browse/WFLY-5070 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Alpha6 > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Fix For: 10.0.0.Beta2 > > > Servlet is autostarted only with loadOnStartup value > 0. Specification says value can be >= 0. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5200) Reading transport protocol metrics fails with "Protocol UDP not found in current stack"

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5200?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5200. ---------------------------- > Reading transport protocol metrics fails with "Protocol UDP not found in current stack" > --------------------------------------------------------------------------------------- > > Key: WFLY-5200 > URL: https://issues.jboss.org/browse/WFLY-5200 > Project: WildFly > Issue Type: Bug > Components: Clustering, Domain Management > Affects Versions: 10.0.0.Beta2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 10.0.0.CR1 > > > {noformat} > [standalone@localhost:9990 /] /subsystem=jgroups/channel=ee/protocol=UDP:read-attribute(name=timer-queue_max_size > { > "outcome" => "failed", > "failure-description" => "WFLYCLJG0019: Protocol UDP not found in current stack", > "rolled-back" => true > }{noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 December 2017