[JBoss JIRA] (WFLY-9450) NPE on jaxrs subsystem of FAILED deployment
by Claudio Miranda (JIRA)
[ https://issues.jboss.org/browse/WFLY-9450?page=com.atlassian.jira.plugin.... ]
Claudio Miranda edited comment on WFLY-9450 at 10/17/17 4:32 PM:
-----------------------------------------------------------------
About the ejb3 subsystem, I am ok to not consider it a bug. I am about to change the way HAL loads the resource to consider the FAILED status and not load the subresources under it. Thanks for the feedback.
was (Author: claudio4j):
About the ejb3 subsystem, I am ok to remove it from the description. I am about to change the way HAL loads the resource to consider the FAILED status and not load the subresources under it. Thanks for the feedback.
> NPE on jaxrs subsystem of FAILED deployment
> --------------------------------------------
>
> Key: WFLY-9450
> URL: https://issues.jboss.org/browse/WFLY-9450
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Reporter: Claudio Miranda
> Assignee: Alessio Soldano
>
> read deployment resources of a server, where one deployment is in failed status, throws a NPE and doesn't return the list of deployed applications.
> To reproduce, get the kitchensink from quickstarts, change the persistence.xml to point to ExampleDS datasource, deploy and assign to main-server-group. Then disable ExampleDS, restart server-one.
> Run the following command:
> {code}
> /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {code}
> The exception in server.log
> {code}
> 2017-10-17 17:08:02,778 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "jaxrs"),
> ("rest-resource" => "org.jboss.as.quickstarts.kitchensink.rest.MemberResourceRESTService")
> ]): java.lang.NullPointerException
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.getDeployment(UndertowDeploymentService.java:170)
> at org.jboss.as.jaxrs.DeploymentRestResourcesDefintion$AbstractRestResReadHandler.execute(DeploymentRestResourcesDefintion.java:183)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:172)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:135)
> at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:231)
> {code}
> The CLI results doesn't display the error message
> {code}
> [domain@localhost:9990 /] /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {
> "outcome" => "success",
> "result" => undefined,
> "failure-description" => undefined
> }
> {code}
> There is a similar problem while reading a specific deployment,
> {code}
> /host=master/server=server-one/deployment=kitchensink.war:read-children-resources(child-type=subsystem,recursive)
> {code}
> results in the following error in server.log
> {code}
> 2017-10-17 17:16:09,857 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "ejb3"),
> ("stateless-session-bean" => "MemberRegistration")
> ]) - failure description: "WFLYEJB0370: EJB component for address [
> (\"deployment\" => \"kitchensink.war\"),
> (\"subsystem\" => \"ejb3\"),
> (\"stateless-session-bean\" => \"MemberRegistration\")
> ] is in
> state DOWN, must be in state UP"
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFLY-9450) NPE on jaxrs subsystem of FAILED deployment
by Claudio Miranda (JIRA)
[ https://issues.jboss.org/browse/WFLY-9450?page=com.atlassian.jira.plugin.... ]
Claudio Miranda commented on WFLY-9450:
---------------------------------------
About the ejb3 subsystem, I am ok to remove it. I am about to change the way HAL loads the resource to consider the FAILED status and not load the subresources under it. Thanks for the feedback.
> NPE on jaxrs subsystem of FAILED deployment
> --------------------------------------------
>
> Key: WFLY-9450
> URL: https://issues.jboss.org/browse/WFLY-9450
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Reporter: Claudio Miranda
> Assignee: Alessio Soldano
>
> read deployment resources of a server, where one deployment is in failed status, throws a NPE and doesn't return the list of deployed applications.
> To reproduce, get the kitchensink from quickstarts, change the persistence.xml to point to ExampleDS datasource, deploy and assign to main-server-group. Then disable ExampleDS, restart server-one.
> Run the following command:
> {code}
> /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {code}
> The exception in server.log
> {code}
> 2017-10-17 17:08:02,778 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "jaxrs"),
> ("rest-resource" => "org.jboss.as.quickstarts.kitchensink.rest.MemberResourceRESTService")
> ]): java.lang.NullPointerException
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.getDeployment(UndertowDeploymentService.java:170)
> at org.jboss.as.jaxrs.DeploymentRestResourcesDefintion$AbstractRestResReadHandler.execute(DeploymentRestResourcesDefintion.java:183)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:172)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:135)
> at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:231)
> {code}
> The CLI results doesn't display the error message
> {code}
> [domain@localhost:9990 /] /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {
> "outcome" => "success",
> "result" => undefined,
> "failure-description" => undefined
> }
> {code}
> There is a similar problem while reading a specific deployment,
> {code}
> /host=master/server=server-one/deployment=kitchensink.war:read-children-resources(child-type=subsystem,recursive)
> {code}
> results in the following error in server.log
> {code}
> 2017-10-17 17:16:09,857 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "ejb3"),
> ("stateless-session-bean" => "MemberRegistration")
> ]) - failure description: "WFLYEJB0370: EJB component for address [
> (\"deployment\" => \"kitchensink.war\"),
> (\"subsystem\" => \"ejb3\"),
> (\"stateless-session-bean\" => \"MemberRegistration\")
> ] is in
> state DOWN, must be in state UP"
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFLY-9450) NPE on jaxrs subsystem of FAILED deployment
by Claudio Miranda (JIRA)
[ https://issues.jboss.org/browse/WFLY-9450?page=com.atlassian.jira.plugin.... ]
Claudio Miranda edited comment on WFLY-9450 at 10/17/17 4:31 PM:
-----------------------------------------------------------------
About the ejb3 subsystem, I am ok to remove it from the description. I am about to change the way HAL loads the resource to consider the FAILED status and not load the subresources under it. Thanks for the feedback.
was (Author: claudio4j):
About the ejb3 subsystem, I am ok to remove it. I am about to change the way HAL loads the resource to consider the FAILED status and not load the subresources under it. Thanks for the feedback.
> NPE on jaxrs subsystem of FAILED deployment
> --------------------------------------------
>
> Key: WFLY-9450
> URL: https://issues.jboss.org/browse/WFLY-9450
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Reporter: Claudio Miranda
> Assignee: Alessio Soldano
>
> read deployment resources of a server, where one deployment is in failed status, throws a NPE and doesn't return the list of deployed applications.
> To reproduce, get the kitchensink from quickstarts, change the persistence.xml to point to ExampleDS datasource, deploy and assign to main-server-group. Then disable ExampleDS, restart server-one.
> Run the following command:
> {code}
> /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {code}
> The exception in server.log
> {code}
> 2017-10-17 17:08:02,778 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "jaxrs"),
> ("rest-resource" => "org.jboss.as.quickstarts.kitchensink.rest.MemberResourceRESTService")
> ]): java.lang.NullPointerException
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.getDeployment(UndertowDeploymentService.java:170)
> at org.jboss.as.jaxrs.DeploymentRestResourcesDefintion$AbstractRestResReadHandler.execute(DeploymentRestResourcesDefintion.java:183)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:172)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:135)
> at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:231)
> {code}
> The CLI results doesn't display the error message
> {code}
> [domain@localhost:9990 /] /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {
> "outcome" => "success",
> "result" => undefined,
> "failure-description" => undefined
> }
> {code}
> There is a similar problem while reading a specific deployment,
> {code}
> /host=master/server=server-one/deployment=kitchensink.war:read-children-resources(child-type=subsystem,recursive)
> {code}
> results in the following error in server.log
> {code}
> 2017-10-17 17:16:09,857 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "ejb3"),
> ("stateless-session-bean" => "MemberRegistration")
> ]) - failure description: "WFLYEJB0370: EJB component for address [
> (\"deployment\" => \"kitchensink.war\"),
> (\"subsystem\" => \"ejb3\"),
> (\"stateless-session-bean\" => \"MemberRegistration\")
> ] is in
> state DOWN, must be in state UP"
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFCORE-3362) Clean up type hierarchy of the kernel parser implementations
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-3362:
----------------------------------------
Summary: Clean up type hierarchy of the kernel parser implementations
Key: WFCORE-3362
URL: https://issues.jboss.org/browse/WFCORE-3362
Project: WildFly Core
Issue Type: Task
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
Minor stuff I want to clean up while implementing the routine new parser work for WFCORE-3309:
1) StandaloneXml/DomainXml/HostXml should not extend CommonXml as they don't use anything from it. They should directly declare the parsing/marshaling interfaces they implement.
2) CommonXml should not declare it implements XMLElementWriter, thus freeing its many subclasses that will never be used in marshaling from needing to add a writeContent method that throws UnsupportedOperationException or does nothing. Only the current version needs to have such a method, and it doesn't need to be public or implement the interface as it's only called by the StandaloneXml/DomainXml/HostXml that's in its package.
3) Various classes can be final, various methods can be private, a few other IDE warns can be cleaned up.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFLY-9451) Remove writeContentMethod from AppClientXml
by Brian Stansberry (JIRA)
Brian Stansberry created WFLY-9451:
--------------------------------------
Summary: Remove writeContentMethod from AppClientXml
Key: WFLY-9451
URL: https://issues.jboss.org/browse/WFLY-9451
Project: WildFly
Issue Type: Task
Components: Application Client
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
Once WFORE-3309 is done, the base class for AppClientXml will no longer require subclasses to implement XMLElementWriter<ModelMarshallingContext>. So AppClientXml should drop its no-op implementation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFLY-9450) NPE on jaxrs subsystem of FAILED deployment
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-9450?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-9450:
----------------------------------------
DeploymentRestResourcesDefintion needs to check that deploymentService is not null.
[~claudio4j] The EJB3 component issue would be a separate issue. TBH I'm not sure it's really a bug though. HAL should not be trying to recursively read the subsystem child resources for FAILED deployments. A FAILED deployment is basically in a broken state so the runtime services underneath it often are not present. The EJB3 resource is correctly reporting that it can't find the services it needs to respond to the management request.
Perhaps the kernel could find a way to hide the child resources of a deployment if it's not DeploymentStatus.OK, but that's not simple to do. It also -might- break someone if they had figured out some way to usefully read child resources of a failed deployment, e.g. to analyze something. I think that's a corner case though.
> NPE on jaxrs subsystem of FAILED deployment
> --------------------------------------------
>
> Key: WFLY-9450
> URL: https://issues.jboss.org/browse/WFLY-9450
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Reporter: Claudio Miranda
> Assignee: Alessio Soldano
>
> read deployment resources of a server, where one deployment is in failed status, throws a NPE and doesn't return the list of deployed applications.
> To reproduce, get the kitchensink from quickstarts, change the persistence.xml to point to ExampleDS datasource, deploy and assign to main-server-group. Then disable ExampleDS, restart server-one.
> Run the following command:
> {code}
> /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {code}
> The exception in server.log
> {code}
> 2017-10-17 17:08:02,778 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "jaxrs"),
> ("rest-resource" => "org.jboss.as.quickstarts.kitchensink.rest.MemberResourceRESTService")
> ]): java.lang.NullPointerException
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.getDeployment(UndertowDeploymentService.java:170)
> at org.jboss.as.jaxrs.DeploymentRestResourcesDefintion$AbstractRestResReadHandler.execute(DeploymentRestResourcesDefintion.java:183)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:172)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:135)
> at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:231)
> {code}
> The CLI results doesn't display the error message
> {code}
> [domain@localhost:9990 /] /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {
> "outcome" => "success",
> "result" => undefined,
> "failure-description" => undefined
> }
> {code}
> There is a similar problem while reading a specific deployment,
> {code}
> /host=master/server=server-one/deployment=kitchensink.war:read-children-resources(child-type=subsystem,recursive)
> {code}
> results in the following error in server.log
> {code}
> 2017-10-17 17:16:09,857 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "ejb3"),
> ("stateless-session-bean" => "MemberRegistration")
> ]) - failure description: "WFLYEJB0370: EJB component for address [
> (\"deployment\" => \"kitchensink.war\"),
> (\"subsystem\" => \"ejb3\"),
> (\"stateless-session-bean\" => \"MemberRegistration\")
> ] is in
> state DOWN, must be in state UP"
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFLY-9450) NPE on jaxrs subsystem of FAILED deployment
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-9450?page=com.atlassian.jira.plugin.... ]
Brian Stansberry edited comment on WFLY-9450 at 10/17/17 3:53 PM:
------------------------------------------------------------------
DeploymentRestResourcesDefintion needs to check that deploymentService is not null.
[~claudio4j] The EJB3 component issue would be a separate issue. TBH I'm not sure it's really a bug though. HAL should not be trying to recursively read the subsystem child resources for FAILED deployments. A FAILED deployment is basically in a broken state so the runtime services underneath it often are not present. The EJB3 resource is correctly reporting that it can't find the services it needs to respond to the management request.
Perhaps the kernel could find a way to hide the child resources of a deployment if it's not DeploymentStatus.OK, but that's not simple to do. It also _might_ break someone if they had figured out some way to usefully read child resources of a failed deployment, e.g. to analyze something. I think that's a corner case though.
was (Author: brian.stansberry):
DeploymentRestResourcesDefintion needs to check that deploymentService is not null.
[~claudio4j] The EJB3 component issue would be a separate issue. TBH I'm not sure it's really a bug though. HAL should not be trying to recursively read the subsystem child resources for FAILED deployments. A FAILED deployment is basically in a broken state so the runtime services underneath it often are not present. The EJB3 resource is correctly reporting that it can't find the services it needs to respond to the management request.
Perhaps the kernel could find a way to hide the child resources of a deployment if it's not DeploymentStatus.OK, but that's not simple to do. It also -might- break someone if they had figured out some way to usefully read child resources of a failed deployment, e.g. to analyze something. I think that's a corner case though.
> NPE on jaxrs subsystem of FAILED deployment
> --------------------------------------------
>
> Key: WFLY-9450
> URL: https://issues.jboss.org/browse/WFLY-9450
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Reporter: Claudio Miranda
> Assignee: Alessio Soldano
>
> read deployment resources of a server, where one deployment is in failed status, throws a NPE and doesn't return the list of deployed applications.
> To reproduce, get the kitchensink from quickstarts, change the persistence.xml to point to ExampleDS datasource, deploy and assign to main-server-group. Then disable ExampleDS, restart server-one.
> Run the following command:
> {code}
> /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {code}
> The exception in server.log
> {code}
> 2017-10-17 17:08:02,778 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "jaxrs"),
> ("rest-resource" => "org.jboss.as.quickstarts.kitchensink.rest.MemberResourceRESTService")
> ]): java.lang.NullPointerException
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.getDeployment(UndertowDeploymentService.java:170)
> at org.jboss.as.jaxrs.DeploymentRestResourcesDefintion$AbstractRestResReadHandler.execute(DeploymentRestResourcesDefintion.java:183)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:172)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:135)
> at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:231)
> {code}
> The CLI results doesn't display the error message
> {code}
> [domain@localhost:9990 /] /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {
> "outcome" => "success",
> "result" => undefined,
> "failure-description" => undefined
> }
> {code}
> There is a similar problem while reading a specific deployment,
> {code}
> /host=master/server=server-one/deployment=kitchensink.war:read-children-resources(child-type=subsystem,recursive)
> {code}
> results in the following error in server.log
> {code}
> 2017-10-17 17:16:09,857 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "ejb3"),
> ("stateless-session-bean" => "MemberRegistration")
> ]) - failure description: "WFLYEJB0370: EJB component for address [
> (\"deployment\" => \"kitchensink.war\"),
> (\"subsystem\" => \"ejb3\"),
> (\"stateless-session-bean\" => \"MemberRegistration\")
> ] is in
> state DOWN, must be in state UP"
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ]
Scott Marlow commented on WFLY-8954:
------------------------------------
FYI, tracking JPA spec issue is [https://github.com/javaee/jpa-spec/issues/150].
> Wildfly 10 with eclipselink Onscucess observer gets stale entity
> ----------------------------------------------------------------
>
> Key: WFLY-8954
> URL: https://issues.jboss.org/browse/WFLY-8954
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.0.0.Final
> Reporter: Nuno Godinho de Matos
> Assignee: Scott Marlow
> Fix For: 12.0.0.Alpha1
>
>
> Hi,
> In widlfly there seems to be an important issue concerning CDI events and observing these events during onsuccess. At least while using eclipselink.
> When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an entity A, fires an event stating entity A has been modified, and an observer consumes this event during transaction success.
> Then the observer will be working with stale entities that do not reflect the modifications done to the entity.
> A sample application for this issue is available in:
> https://github.com/99sono/wildfly10-observe-on-success-stale-entity
> The widlfly configuration xml for the sample application, is available in the application itself, as can be seen in the readme documentation.
> Many thanks for taking a look.
> Kindest regards.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFLY-9450) NPE on jaxrs subsystem of FAILED deployment
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-9450?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-9450:
--------------------------------------
Component/s: REST
Assignee: Alessio Soldano (was: Jason Greene)
> NPE on jaxrs subsystem of FAILED deployment
> --------------------------------------------
>
> Key: WFLY-9450
> URL: https://issues.jboss.org/browse/WFLY-9450
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Reporter: Claudio Miranda
> Assignee: Alessio Soldano
>
> read deployment resources of a server, where one deployment is in failed status, throws a NPE and doesn't return the list of deployed applications.
> To reproduce, get the kitchensink from quickstarts, change the persistence.xml to point to ExampleDS datasource, deploy and assign to main-server-group. Then disable ExampleDS, restart server-one.
> Run the following command:
> {code}
> /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {code}
> The exception in server.log
> {code}
> 2017-10-17 17:08:02,778 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "jaxrs"),
> ("rest-resource" => "org.jboss.as.quickstarts.kitchensink.rest.MemberResourceRESTService")
> ]): java.lang.NullPointerException
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.getDeployment(UndertowDeploymentService.java:170)
> at org.jboss.as.jaxrs.DeploymentRestResourcesDefintion$AbstractRestResReadHandler.execute(DeploymentRestResourcesDefintion.java:183)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:172)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:135)
> at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:231)
> {code}
> The CLI results doesn't display the error message
> {code}
> [domain@localhost:9990 /] /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
> {
> "outcome" => "success",
> "result" => undefined,
> "failure-description" => undefined
> }
> {code}
> There is a similar problem while reading a specific deployment,
> {code}
> /host=master/server=server-one/deployment=kitchensink.war:read-children-resources(child-type=subsystem,recursive)
> {code}
> results in the following error in server.log
> {code}
> 2017-10-17 17:16:09,857 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "kitchensink.war"),
> ("subsystem" => "ejb3"),
> ("stateless-session-bean" => "MemberRegistration")
> ]) - failure description: "WFLYEJB0370: EJB component for address [
> (\"deployment\" => \"kitchensink.war\"),
> (\"subsystem\" => \"ejb3\"),
> (\"stateless-session-bean\" => \"MemberRegistration\")
> ] is in
> state DOWN, must be in state UP"
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFLY-9450) NPE on jaxrs subsystem of FAILED deployment
by Claudio Miranda (JIRA)
Claudio Miranda created WFLY-9450:
-------------------------------------
Summary: NPE on jaxrs subsystem of FAILED deployment
Key: WFLY-9450
URL: https://issues.jboss.org/browse/WFLY-9450
Project: WildFly
Issue Type: Bug
Reporter: Claudio Miranda
Assignee: Jason Greene
read deployment resources of a server, where one deployment is in failed status, throws a NPE and doesn't return the list of deployed applications.
To reproduce, get the kitchensink from quickstarts, change the persistence.xml to point to ExampleDS datasource, deploy and assign to main-server-group. Then disable ExampleDS, restart server-one.
Run the following command:
{code}
/host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
{code}
The exception in server.log
{code}
2017-10-17 17:08:02,778 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
("deployment" => "kitchensink.war"),
("subsystem" => "jaxrs"),
("rest-resource" => "org.jboss.as.quickstarts.kitchensink.rest.MemberResourceRESTService")
]): java.lang.NullPointerException
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.getDeployment(UndertowDeploymentService.java:170)
at org.jboss.as.jaxrs.DeploymentRestResourcesDefintion$AbstractRestResReadHandler.execute(DeploymentRestResourcesDefintion.java:183)
at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:172)
at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:135)
at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:231)
{code}
The CLI results doesn't display the error message
{code}
[domain@localhost:9990 /] /host=master/server=server-one:read-children-resources(child-type=deployment,include-runtime,recursive)
{
"outcome" => "success",
"result" => undefined,
"failure-description" => undefined
}
{code}
There is a similar problem while reading a specific deployment,
{code}
/host=master/server=server-one/deployment=kitchensink.war:read-children-resources(child-type=subsystem,recursive)
{code}
results in the following error in server.log
{code}
2017-10-17 17:16:09,857 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
("deployment" => "kitchensink.war"),
("subsystem" => "ejb3"),
("stateless-session-bean" => "MemberRegistration")
]) - failure description: "WFLYEJB0370: EJB component for address [
(\"deployment\" => \"kitchensink.war\"),
(\"subsystem\" => \"ejb3\"),
(\"stateless-session-bean\" => \"MemberRegistration\")
] is in
state DOWN, must be in state UP"
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months