[jboss-jira] [JBoss JIRA] (WFLY-9405) NPE when trying to recursively remove the EJB subsystem

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-9405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473053#comment-13473053 ] 

Brian Stansberry commented on WFLY-9405:
----------------------------------------

The description does a recursive removal of the entire ejb3 subsystem to cause this, but that's not necessary. A targeted op would do it too:

{code}
[standalone at embedded /] /subsystem=ejb3/service=remote/channel-creation-options=MAX_OUTBOUND_MESSAGES:remove
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException",
    "rolled-back" => true
}
{code}

For this to fail the server can't be running in --admin-only (hence the workaround I posted.)

> NPE when trying to recursively remove the EJB subsystem
> -------------------------------------------------------
>
>                 Key: WFLY-9405
>                 URL: https://issues.jboss.org/browse/WFLY-9405
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 11.0.0.CR1
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>
> This fails:
> {code}
> [standalone at localhost:9990 /] /subsystem=ejb3:remove
> {
>     "outcome" => "failed",
>     "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException",
>     "rolled-back" => true
> }
> {code}
> with this in the server log:
> {code}
> 15:53:42,572 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("remove") failed - address: ([
>     ("subsystem" => "ejb3"),
>     ("service" => "remote"),
>     ("channel-creation-options" => "MAX_OUTBOUND_MESSAGES")
> ]): java.lang.NullPointerException
> 	at org.jboss.as.controller.OperationContextImpl.readResourceFromRoot(OperationContextImpl.java:894)
> 	at org.jboss.as.controller.OperationContextImpl.readResourceFromRoot(OperationContextImpl.java:884)
> 	at org.jboss.as.controller.RestartParentResourceHandlerBase.getModel(RestartParentResourceHandlerBase.java:216)
> 	at org.jboss.as.controller.RestartParentResourceHandlerBase.access$000(RestartParentResourceHandlerBase.java:39)
> 	at org.jboss.as.controller.RestartParentResourceHandlerBase$1.execute(RestartParentResourceHandlerBase.java:66)
> 	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:980)
> 	at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726)
> 	at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450)
> 	at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1402)
> 	at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:418)
> ...
> {code}
> I believe a post-boot add of this resource would fail as well.
> Problem is ChannelCreationOptionRemove and ChannelCreationOptionAdd in RemoteConnectorChannelCreationOptionResource use an incorrect parentKeyName. These handlers extend RestartParentResourceHandlerBase but are passing the *value* of the parent element as "parentKeyName" instead of its *key*; i.e. "remote" instead of "service".
> Even though this code has been like this since 2012, this is somewhat a regression since before the current version our standard configs did not include resources of this type. So users could hit this in previous releases but now they are more likely to.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)