September 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1511) RemoteDomainConnection.close() will block forever if the master HC is not running

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1511?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1511: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1012850 > RemoteDomainConnection.close() will block forever if the master HC is not running > ---------------------------------------------------------------------------------- > > Key: WFLY-1511 > URL: https://issues.jboss.org/browse/WFLY-1511 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 8.0.0.Alpha1 > Reporter: Brian Stansberry > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Beta1 > > > RemoteDomainConnection.close() overrides FutureManagementChannel.close() to first send a "unregister" message to the master HC before calling the superclass functionality. > Problem is this call tries to open a connection to the master and will block forever waiting for it to connect if the master isn't available, as seen at http://fpaste.org/18232/37105700/ > That example was from AutoIgnoredResourcesDomainTestCase which is concurrently shutting down the hosts in the domain, meaning the master can be shutting down in the middle of or prior to slave shutdown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-78) Intermittent failures in RespawnTestCase

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-78?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-78: --------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1012809|https://bugzilla.redhat.com/show_bug.cgi?id=1012809] from ASSIGNED to POST > Intermittent failures in RespawnTestCase > ---------------------------------------- > > Key: WFLY-78 > URL: https://issues.jboss.org/browse/WFLY-78 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha1 > > > Problems like [1] still pop up fairly frequently. It seems the same 3 tests fail. > Failed tests: testReloadHcButNotServers(org.jboss.as.test.integration.respawn.RespawnTestCase) > testReloadHcButNotServersWithFailedServer(org.jboss.as.test.integration.respawn.RespawnTestCase) testHCReloadAbortPreservesServers(org.jboss.as.test.integration.respawn.RespawnTestCase) > [1] http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-ignore/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-78) Intermittent failures in RespawnTestCase

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-78?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-78: --------------------------------------------- Ivo Studensky <istudens(a)redhat.com> made a comment on [bug 1012809|https://bugzilla.redhat.com/show_bug.cgi?id=1012809] Relevant PR: https://github.com/jbossas/jboss-eap/pull/474 > Intermittent failures in RespawnTestCase > ---------------------------------------- > > Key: WFLY-78 > URL: https://issues.jboss.org/browse/WFLY-78 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha1 > > > Problems like [1] still pop up fairly frequently. It seems the same 3 tests fail. > Failed tests: testReloadHcButNotServers(org.jboss.as.test.integration.respawn.RespawnTestCase) > testReloadHcButNotServersWithFailedServer(org.jboss.as.test.integration.respawn.RespawnTestCase) testHCReloadAbortPreservesServers(org.jboss.as.test.integration.respawn.RespawnTestCase) > [1] http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-ignore/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2113) NamingBindingResourceDefinition attribute validation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2113?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2113: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1006206|https://bugzilla.redhat.com/show_bug.cgi?id=1006206] from ON_QA to VERIFIED > NamingBindingResourceDefinition attribute validation > ---------------------------------------------------- > > Key: WFLY-2113 > URL: https://issues.jboss.org/browse/WFLY-2113 > Project: WildFly > Issue Type: Feature Request > Components: Naming > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Fix For: 8.0.0.Beta1 > > > Missing attribute validation may end up on an invalid naming subsystem config, which then prevents server start. For instance it is possible to use the CLI to add a simple binding without value defined, or change an existing resource value attribute to null. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2113) NamingBindingResourceDefinition attribute validation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2113?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2113: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> made a comment on [bug 1006206|https://bugzilla.redhat.com/show_bug.cgi?id=1006206] Verified in 6.2.0.ER3, thanks. > NamingBindingResourceDefinition attribute validation > ---------------------------------------------------- > > Key: WFLY-2113 > URL: https://issues.jboss.org/browse/WFLY-2113 > Project: WildFly > Issue Type: Feature Request > Components: Naming > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Fix For: 8.0.0.Beta1 > > > Missing attribute validation may end up on an invalid naming subsystem config, which then prevents server start. For instance it is possible to use the CLI to add a simple binding without value defined, or change an existing resource value attribute to null. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1752) CDI TCK @WebServiceRef injection tests failing

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/WFLY-1752?page=com.atlassian.jira.plugin.... ] Jozef Hartinger reassigned WFLY-1752: ------------------------------------- Assignee: Jozef Hartinger (was: Martin Kouba) > CDI TCK @WebServiceRef injection tests failing > ---------------------------------------------- > > Key: WFLY-1752 > URL: https://issues.jboss.org/browse/WFLY-1752 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Web Services > Affects Versions: 8.0.0.Alpha3 > Reporter: Jozef Hartinger > Assignee: Jozef Hartinger > Fix For: 8.0.0.Beta1 > > > {noformat} > org.jboss.arquillian.test.spi.ArquillianProxyException: org.jboss.wsf.spi.WSFException : Cannot create service [Proxied because : Original exception not deserilizable, ClassNotFoundException] > at org.jboss.wsf.spi.WSFException.rethrow(WSFException.java:55) > at org.jboss.wsf.stack.cxf.client.serviceref.AbstractServiceObjectFactoryJAXWS.getObjectInstance(AbstractServiceObjectFactoryJAXWS.java:90) > at org.jboss.wsf.stack.cxf.client.serviceref.CXFServiceRefFactoryImpl.newServiceRef(CXFServiceRefFactoryImpl.java:38) > at org.jboss.as.webservices.webserviceref.WebServiceManagedReferenceFactory.getReference(WebServiceManagedReferenceFactory.java:37) > at org.jboss.as.weld.services.bootstrap.ManagedReferenceFactoryToResourceReferenceFactoryAdapter.createResource(ManagedReferenceFactoryToResourceReferenceFactoryAdapter.java:41) > 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:348) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:59) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:91) > at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:158) > at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:69) > at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:738) > at org.jboss.weld.injection.producer.AbstractMemberProducer.getReceiver(AbstractMemberProducer.java:110) > at org.jboss.weld.injection.producer.AbstractMemberProducer.produce(AbstractMemberProducer.java:129) > at org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:189) > at org.jboss.weld.bean.builtin.ee.EEResourceProducerField.createUnderlying(EEResourceProducerField.java:149) > at org.jboss.weld.bean.builtin.ee.EEResourceProducerField.access$000(EEResourceProducerField.java:53) > at org.jboss.weld.bean.builtin.ee.EEResourceProducerField$EEResourceCallable.call(EEResourceProducerField.java:73) > at org.jboss.weld.bean.builtin.CallableMethodHandler.invoke(CallableMethodHandler.java:45) > at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) > at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:101) > at org.jboss.cdi.tck.tests.lookup.injection.non.contextual.ws.SheepWS$-1409013730$Proxy$_$$_Weld$Proxy$.isSheepInjected(Unknown Source) > at org.jboss.cdi.tck.tests.lookup.injection.non.contextual.ws.WebServiceResourceTest.testResourceInvocation(WebServiceResourceTest.java:86) > Caused by: java.lang.InstantiationException: org.jboss.cdi.tck.tests.lookup.injection.non.contextual.ws.SheepWSEndPointService > at java.lang.Class.newInstance(Class.java:359) > at org.jboss.wsf.stack.cxf.client.serviceref.AbstractServiceObjectFactoryJAXWS.instantiateService(AbstractServiceObjectFactoryJAXWS.java:241) > at org.jboss.wsf.stack.cxf.client.serviceref.AbstractServiceObjectFactoryJAXWS.getObjectInstance(AbstractServiceObjectFactoryJAXWS.java:68) > ... 128 more > {noformat} > The affected CDI TCK tests: > org.jboss.cdi.tck.tests.implementation.simple.resource.broken.type.ws.ResourceDefinitionWithDifferentTypeTest > org.jboss.cdi.tck.tests.lookup.injection.non.contextual.ws.WebServiceResourceTest -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2165) Error Weld when starting WildFly 8 with Spring 3 - NullPointerException

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/WFLY-2165?page=com.atlassian.jira.plugin.... ] Jozef Hartinger reassigned WFLY-2165: ------------------------------------- Assignee: Jozef Hartinger (was: Matus Abaffy) > Error Weld when starting WildFly 8 with Spring 3 - NullPointerException > ----------------------------------------------------------------------- > > Key: WFLY-2165 > URL: https://issues.jboss.org/browse/WFLY-2165 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Reporter: Raul Abreu Leite > Assignee: Jozef Hartinger > Priority: Critical > Fix For: 8.0.0.Beta1 > > > When I update my application, from Jboss-as 7.1.1.Final to Wildfly 8.0.0.Alpha4, there was an error that I can not fix. > {code:java} > 19:57:20,955 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."cineserver.war".component."org.springframework.web.context.request.async.StandardServletAsyncWebRequest".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cineserver.war".component."org.springframework.web.context.request.async.StandardServletAsyncWebRequest".WeldInstantiator: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1900) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > Caused by: java.lang.NullPointerException > at org.jboss.weld.injection.InjectionPointFactory.getParameterInjectionPoints(InjectionPointFactory.java:245) > at org.jboss.weld.injection.AbstractCallableInjectionPoint.<init>(AbstractCallableInjectionPoint.java:49) > at org.jboss.weld.injection.ConstructorInjectionPoint.<init>(ConstructorInjectionPoint.java:59) > at org.jboss.weld.injection.InjectionPointFactory.createConstructorInjectionPoint(InjectionPointFactory.java:173) > at org.jboss.weld.injection.producer.DefaultInstantiator.<init>(DefaultInstantiator.java:46) > at org.jboss.weld.injection.producer.BasicInjectionTarget.initInstantiator(BasicInjectionTarget.java:144) > at org.jboss.weld.injection.producer.BasicInjectionTarget.<init>(BasicInjectionTarget.java:72) > at org.jboss.as.weld.injection.NonContextualComponentInjectionTarget.<init>(NonContextualComponentInjectionTarget.java:48) > at org.jboss.as.weld.injection.NonContextualComponentInjectionTarget.<init>(NonContextualComponentInjectionTarget.java:44) > at org.jboss.as.weld.injection.WeldComponentService.start(WeldComponentService.java:129) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > ... 3 more > 19:57:21,018 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "cineserver.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cineserver.war\".component.\"org.springframework.web.context.request.async.StandardServletAsyncWebRequest\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cineserver.war\".component.\"org.springframework.web.context.request.async.StandardServletAsyncWebRequest\".WeldInstantiator: Failed to start service > Caused by: java.lang.NullPointerException"}} > 19:57:21,018 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "cineserver.war" was rolled back with the following failure message: > {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cineserver.war\".component.\"org.springframework.web.context.request.async.StandardServletAsyncWebRequest\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cineserver.war\".component.\"org.springframework.web.context.request.async.StandardServletAsyncWebRequest\".WeldInstantiator: Failed to start service > Caused by: java.lang.NullPointerException"}} > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1791) Unable to use Filter Expressions in filter-spec

by Emmanuel Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-1791?page=com.atlassian.jira.plugin.... ] Emmanuel Hugonnet commented on WFLY-1791: ----------------------------------------- The argument values are parsed a second time which means that the escaped char have been unescaped. Changing this in the PR: https://github.com/wildfly/wildfly/pull/5159 > Unable to use Filter Expressions in filter-spec > ------------------------------------------------ > > Key: WFLY-1791 > URL: https://issues.jboss.org/browse/WFLY-1791 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: Emmanuel Hugonnet > Assignee: Alexey Loubyansky > Priority: Minor > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-78) Intermittent failures in RespawnTestCase

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-78?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-78: --------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1012809|https://bugzilla.redhat.com/show_bug.cgi?id=1012809] from NEW to ASSIGNED > Intermittent failures in RespawnTestCase > ---------------------------------------- > > Key: WFLY-78 > URL: https://issues.jboss.org/browse/WFLY-78 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha1 > > > Problems like [1] still pop up fairly frequently. It seems the same 3 tests fail. > Failed tests: testReloadHcButNotServers(org.jboss.as.test.integration.respawn.RespawnTestCase) > testReloadHcButNotServersWithFailedServer(org.jboss.as.test.integration.respawn.RespawnTestCase) testHCReloadAbortPreservesServers(org.jboss.as.test.integration.respawn.RespawnTestCase) > [1] http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-ignore/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-78) Intermittent failures in RespawnTestCase

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-78?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-78: --------------------------------------------- Ivo Studensky <istudens(a)redhat.com> made a comment on [bug 1012809|https://bugzilla.redhat.com/show_bug.cgi?id=1012809] Description of problem: Intermittent failures still happen within EAP PR testing. This is a backport of WFLY-78 to EAP 6.2. > Intermittent failures in RespawnTestCase > ---------------------------------------- > > Key: WFLY-78 > URL: https://issues.jboss.org/browse/WFLY-78 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha1 > > > Problems like [1] still pop up fairly frequently. It seems the same 3 tests fail. > Failed tests: testReloadHcButNotServers(org.jboss.as.test.integration.respawn.RespawnTestCase) > testReloadHcButNotServersWithFailedServer(org.jboss.as.test.integration.respawn.RespawnTestCase) testHCReloadAbortPreservesServers(org.jboss.as.test.integration.respawn.RespawnTestCase) > [1] http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-ignore/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2013