March 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4426) do not revertReloadRequired unless reload was required

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-4426: --------------------------------- Summary: do not revertReloadRequired unless reload was required Key: WFLY-4426 URL: https://issues.jboss.org/browse/WFLY-4426 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 9.0.0.Alpha1 Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 9.0.0.Beta1 HornetQReloadRequiredHandlers will call context.reloadRequired() if there performRuntime method is called and a HornetQ server service is installed. In turn, it calls context.revertReloadRequired() in their rollbackRuntime if a HornetQ server service is installed. However it is possible that at boot time, there is not HornetQ server installed when the performRuntime is installed (so context.reloadRequired is not called). Then if an operation fails at boot time and the HornetQReloadRequiredHandlers op is rolled back, there will then be an installed HornetQ server and context.revertReloadRequired() will be called. This generated a NPE before WFCORE-591 but it is also a programming error to call context.revertReloadRequired() in a OSH if context.reloadRequired() has not been called beforehands -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-596) ObjectTypeValidator should give a more meaningful error message.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-596: --------------------------------------- Summary: ObjectTypeValidator should give a more meaningful error message. Key: WFCORE-596 URL: https://issues.jboss.org/browse/WFCORE-596 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Affects Versions: 1.0.0.Alpha19 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-596) ObjectTypeValidator should give a more meaningful error message.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-596?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFCORE-596: ------------------------------------ Description: Presently the error is reported as: - {code} throw new OperationFailedException("invalid type key"); {code} If you are making a call with a complex object type you have no idea as to what is really wrong. > ObjectTypeValidator should give a more meaningful error message. > ---------------------------------------------------------------- > > Key: WFCORE-596 > URL: https://issues.jboss.org/browse/WFCORE-596 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 1.0.0.Alpha19 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > Presently the error is reported as: - > {code} > throw new OperationFailedException("invalid type key"); > {code} > If you are making a call with a complex object type you have no idea as to what is really wrong. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4424) NullPointerException in AbstractCommonConfigResolver.resolveEndpointConfig

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-4424?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on WFLY-4424: --------------------------------------- Gytis, please try with https://github.com/asoldano/wildfly/tree/WFLY-4424 , which has a tentative fix for the issue (https://github.com/asoldano/wildfly/commit/393681028b247ae49d9b56dd73b334...). If it solves the problem here as I expect, I can have the new Phase IDs added to wildfly-core and eventually send a proper PR for this jira. Thanks. > NullPointerException in AbstractCommonConfigResolver.resolveEndpointConfig > -------------------------------------------------------------------------- > > Key: WFLY-4424 > URL: https://issues.jboss.org/browse/WFLY-4424 > Project: WildFly > Issue Type: Bug > Components: Web Services > Reporter: Gytis Trikleris > Assignee: Alessio Soldano > > Lately we started to get following exception in our XTS tests: > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."xtstest.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xtstest.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "xtstest.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.NullPointerException > at org.jboss.ws.common.configuration.AbstractCommonConfigResolver.resolveEndpointConfig(AbstractCommonConfigResolver.java:129) > at org.jboss.as.webservices.deployers.WSIntegrationProcessorJAXWS_HANDLER.processAnnotation(WSIntegrationProcessorJAXWS_HANDLER.java:95) > at org.jboss.as.webservices.deployers.AbstractIntegrationProcessorJAXWS.deploy(AbstractIntegrationProcessorJAXWS.java:74) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > {code} > It is intermittent and seems to be caused by some sort of race condition. > It started to happen once this commit was introduced: https://github.com/wildfly/wildfly/commit/c0c1e82d8472e1b29c679380d5e0aea... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4425) Adding of JMS/MDB annotations in classes of project switches off activation-call of install singleton service in cluster

by Serg Jackbean (JIRA)

Serg Jackbean created WFLY-4425: ----------------------------------- Summary: Adding of JMS/MDB annotations in classes of project switches off activation-call of install singleton service in cluster Key: WFLY-4425 URL: https://issues.jboss.org/browse/WFLY-4425 Project: WildFly Issue Type: Bug Components: Clustering, EJB, JMS, MSC Affects Versions: 8.2.0.Final Environment: Windows. JDK 7 Reporter: Serg Jackbean Assignee: Paul Ferraro Adding of JMS/MDB annotations in classes of project switches off activation-call of install singleton service in cluster. singleton service in cluster: https://github.com/wildfly/quickstart/tree/master/cluster-ha-singleton MDB classes from example: https://blogs.oracle.com/arungupta/entry/simple_jms_2_0_sample JMS Annotations example: http://www.mastertheboss.com/jboss-server/jboss-jms/jms-20-tutorial-on-wi... (by the way. what is right method of invoking methods of singletone in cluster? method getValue in example - doesn't contain any arguments) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-595) PrimitiveListAttributeDefinitions also missing opportunity to add type information from ObjectTypeAttributeDefinition

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-595?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFCORE-595: ------------------------------------ Labels: affects_elytron (was: ) > PrimitiveListAttributeDefinitions also missing opportunity to add type information from ObjectTypeAttributeDefinition > --------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-595 > URL: https://issues.jboss.org/browse/WFCORE-595 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: affects_elytron > Fix For: 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1920) FC: Flag NO_FC is not applied on RPC calls/responses

by Karim AMMOUS (JIRA)

[ https://issues.jboss.org/browse/JGRP-1920?page=com.atlassian.jira.plugin.... ] Karim AMMOUS closed JGRP-1920. ------------------------------ Resolution: Rejected > FC: Flag NO_FC is not applied on RPC calls/responses > ---------------------------------------------------- > > Key: JGRP-1920 > URL: https://issues.jboss.org/browse/JGRP-1920 > Project: JGroups > Issue Type: Bug > Reporter: Karim AMMOUS > Assignee: Bela Ban > Fix For: 3.6.3 > > > When we set Flag.NO_FC on an RPC call through "RequestOptions", we expect that both request and response will be not rate limited. > Currently, both request and response could be slow down by flow control protocols. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-553) ModelControllerClientOperationHandler doesn't manage the clientRequestExecutor properly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-553?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-553: ------------------------------------------------ baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1199319|https://bugzilla.redhat.com/show_bug.cgi?id=1199319] from ASSIGNED to POST > ModelControllerClientOperationHandler doesn't manage the clientRequestExecutor properly > ---------------------------------------------------------------------------------------- > > Key: WFCORE-553 > URL: https://issues.jboss.org/browse/WFCORE-553 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha18 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.Beta1 > > > ModelControllerClientOperationHandler's constructor creates a ThreadPoolExecutor for handling client requests and then the class doesn't clean it up. > In addition, an instance of ModelControllerClientOperationHandler is created per channel, not one per ModelControllerClientOperationHandlerFactoryService. I know I at least thought of the thread pool as being per remote management interface, not per channel. > Making it be per ModelControllerClientOperationHandlerFactoryService and cleaning it up in that service's stop would be the easiest fix, but the pool settings may not be appropriate if we do that, so tread carefully. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-595) PrimitiveListAttributeDefinitions also missing opportunity to add type information from ObjectTypeAttributeDefinition

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-595: --------------------------------------- Summary: PrimitiveListAttributeDefinitions also missing opportunity to add type information from ObjectTypeAttributeDefinition Key: WFCORE-595 URL: https://issues.jboss.org/browse/WFCORE-595 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4424) NullPointerException in AbstractCommonConfigResolver.resolveEndpointConfig

by Gytis Trikleris (JIRA)

Gytis Trikleris created WFLY-4424: ------------------------------------- Summary: NullPointerException in AbstractCommonConfigResolver.resolveEndpointConfig Key: WFLY-4424 URL: https://issues.jboss.org/browse/WFLY-4424 Project: WildFly Issue Type: Bug Components: Web Services Reporter: Gytis Trikleris Assignee: Alessio Soldano Lately we started to get following exception in our XTS tests: {code} ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."xtstest.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xtstest.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "xtstest.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.NullPointerException at org.jboss.ws.common.configuration.AbstractCommonConfigResolver.resolveEndpointConfig(AbstractCommonConfigResolver.java:129) at org.jboss.as.webservices.deployers.WSIntegrationProcessorJAXWS_HANDLER.processAnnotation(WSIntegrationProcessorJAXWS_HANDLER.java:95) at org.jboss.as.webservices.deployers.AbstractIntegrationProcessorJAXWS.deploy(AbstractIntegrationProcessorJAXWS.java:74) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) ... 5 more {code} It is intermittent and seems to be caused by some sort of race condition. It started to happen once this commit was introduced: https://github.com/wildfly/wildfly/commit/c0c1e82d8472e1b29c679380d5e0aea... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 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 March 2015