May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10432) JMS queue resource is not found

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-10432?page=com.atlassian.jira.plugin... ] Stuart Douglas commented on WFLY-10432: --------------------------------------- So there are a few parts to this issue: The first is that @BeforeClass is not guaranteed to run before @Deployment so there is no guarantee the queue is created before the deployment. This can be worked around by using ServerSetupTask which is guaranteed to run before the deployment. The second is that this test should never have passed in the first place. It uses @Resource on a CDI bean without @Produces which should not have been supported. CDI uses resource produces to bridge the gap between name based and type safe injection, which is why producer fields are required. The third is that it appears that CDI @Resource and EE @Resource are handled in subtly different ways. A mappedName or lookup of 'foo' on an EE resource translates to java:comp/env/foo, while for a CDI bean it translates to java:/foo. This is unspecified behaviour, so the spec gives no guidance here. The easiest way to make this test pass is to change the lookup to be explicit (i.e. prefix with java:/), and change the setup to use @ServerSetup. > JMS queue resource is not found > ------------------------------- > > Key: WFLY-10432 > URL: https://issues.jboss.org/browse/WFLY-10432 > Project: WildFly > Issue Type: Bug > Components: Naming > Affects Versions: 13.0.0.Beta1 > Reporter: Erich Duda > Priority: Blocker > > Deploying of \[1\] fails with following exception. > {code} > org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy InjectionTest.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.module.InjectionTest.InjectionTest.env.jms.queue.test"],"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.InjectionTest.InjectionTest.env.\"org.jboss.resteasy.test.cdi.injection.resource.CDIInjectionResourceProducer\".bookQueue is missing [jboss.naming.context.java.module.InjectionTest.InjectionTest.env.jms.queue.test]"]}}} > {code} > The deployment is part of Resteasy test suite. The same test works with Wildfly 12. > *Blocker priority* was chosen because this is regression against Wildfly 12. > *User's impact:* Some deployments can stop working after upgrade to Wildfly 13. > I found out that the regression is caused by the commit [WFLY-10358|https://github.com/wildfly/wildfly/commit/a9b7a64ac3f556f2f7a5...] > \[1\] https://github.com/resteasy/Resteasy/blob/master/testsuite/integration-te... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9658) Batch jobs in a sub-deployment can be started but not queried

by Alessandro Moscatelli (JIRA)

[ https://issues.jboss.org/browse/WFLY-9658?page=com.atlassian.jira.plugin.... ] Alessandro Moscatelli commented on WFLY-9658: --------------------------------------------- Nothing to be sorry about, thank you for your effort > Batch jobs in a sub-deployment can be started but not queried > ------------------------------------------------------------- > > Key: WFLY-9658 > URL: https://issues.jboss.org/browse/WFLY-9658 > Project: WildFly > Issue Type: Bug > Components: Batch > Reporter: James Perkins > Assignee: James Perkins > > In an EAR deployment that contains a multiple batch deployments each sub-deployment can start jobs from other sub-deployments, but the job information cannot be queried. For example a job can be started from a WAR that is in an EJB, however you cannot execute {{JobOperator.getJobInstance()}} from the WAR on the same job. > Visibility should be consistent for starting and querying batch jobs. > More details on https://github.com/jberet/jsr352/issues/105. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10437) Consolidate Infinispan subsystem services using multi-value service installation

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-10437: ----------------------------------- Summary: Consolidate Infinispan subsystem services using multi-value service installation Key: WFLY-10437 URL: https://issues.jboss.org/browse/WFLY-10437 Project: WildFly Issue Type: Enhancement Components: Clustering Affects Versions: 13.0.0.Beta1 Reporter: Paul Ferraro Assignee: Paul Ferraro The Infinispan subsystem installs quite a few services per container and per cache. We should be able to lower the memory footprint of this subsystem by consolidating services wherever possible, by leveraging MSC 1.4.x multi-value service installation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10438) Create a regression mixed-domain test for a missing host-exclude

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-10438: --------------------------------------- Summary: Create a regression mixed-domain test for a missing host-exclude Key: WFLY-10438 URL: https://issues.jboss.org/browse/WFLY-10438 Project: WildFly Issue Type: Task Components: Management, Test Suite Reporter: Brian Stansberry Assignee: Jeff Mesnil We need a simple test that a slave running the version before the current one can boot and run a minimal server. Basically to catch the need for a fix like WFLY-10396 whenever we add a new extension. Something like: Base domain config must be the standard one we ship. It will include all extensions. Test adds a minimal profile -- bare bones logging subsystem or perhaps no subsystem at all, can only have config that has been legal from the beginning -- and a server group using that profile. The server-group is added to the 'active-server-groups' attribute in the host-exclude resource for the slave's version. Slave host.xml has 1 server only, and in that server group. Launch the DC using the current release and the slave using the legacy release. Prove the slave server can start. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10436) Consolidate JGroups subsystem services using multi-value service installation

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-10436: ----------------------------------- Summary: Consolidate JGroups subsystem services using multi-value service installation Key: WFLY-10436 URL: https://issues.jboss.org/browse/WFLY-10436 Project: WildFly Issue Type: Enhancement Components: Clustering Affects Versions: 13.0.0.Beta1 Reporter: Paul Ferraro Assignee: Paul Ferraro The JGroups subsystem installs quite a few services per stack and per channel. We should be able to lower the memory footprint of this subsystem by consolidating services wherever possible, by leveraging MSC 1.4.x multi-value service installation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9658) Batch jobs in a sub-deployment can be started but not queried

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9658?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-9658: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/11271 (was: https://issues.jboss.org/browse/WFLY-9658) > Batch jobs in a sub-deployment can be started but not queried > ------------------------------------------------------------- > > Key: WFLY-9658 > URL: https://issues.jboss.org/browse/WFLY-9658 > Project: WildFly > Issue Type: Bug > Components: Batch > Reporter: James Perkins > Assignee: James Perkins > > In an EAR deployment that contains a multiple batch deployments each sub-deployment can start jobs from other sub-deployments, but the job information cannot be queried. For example a job can be started from a WAR that is in an EJB, however you cannot execute {{JobOperator.getJobInstance()}} from the WAR on the same job. > Visibility should be consistent for starting and querying batch jobs. > More details on https://github.com/jberet/jsr352/issues/105. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10435) JSF can be activated for EAR deployments

by James Perkins (JIRA)

James Perkins created WFLY-10435: ------------------------------------ Summary: JSF can be activated for EAR deployments Key: WFLY-10435 URL: https://issues.jboss.org/browse/WFLY-10435 Project: WildFly Issue Type: Bug Components: JSF Reporter: James Perkins Assignee: James Perkins Priority: Critical Fix For: 13.0.0.CR1 If a library in the {{EAR/lib}} directory contains descriptors that would enable JSF then JSF would be activated for EAR. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9658) Batch jobs in a sub-deployment can be started but not queried

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9658?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-9658: ------------------------------------- [~alessandromoscatelli] Sorry for taking so long on this. Hopefully it will make WildFly 13. > Batch jobs in a sub-deployment can be started but not queried > ------------------------------------------------------------- > > Key: WFLY-9658 > URL: https://issues.jboss.org/browse/WFLY-9658 > Project: WildFly > Issue Type: Bug > Components: Batch > Reporter: James Perkins > Assignee: James Perkins > > In an EAR deployment that contains a multiple batch deployments each sub-deployment can start jobs from other sub-deployments, but the job information cannot be queried. For example a job can be started from a WAR that is in an EJB, however you cannot execute {{JobOperator.getJobInstance()}} from the WAR on the same job. > Visibility should be consistent for starting and querying batch jobs. > More details on https://github.com/jberet/jsr352/issues/105. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10358) Resource annotations should create bindings even if they are not used on a component

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10358?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-10358: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/11203, https://github.com/wildfly/wildfly/pull/11241 (was: https://github.com/wildfly/wildfly/pull/11203) > Resource annotations should create bindings even if they are not used on a component > ------------------------------------------------------------------------------------ > > Key: WFLY-10358 > URL: https://issues.jboss.org/browse/WFLY-10358 > Project: WildFly > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10358) Resource annotations should create bindings even if they are not used on a component

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10358?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-10358: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/11203 > Resource annotations should create bindings even if they are not used on a component > ------------------------------------------------------------------------------------ > > Key: WFLY-10358 > URL: https://issues.jboss.org/browse/WFLY-10358 > Project: WildFly > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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