[ 
https://issues.apache.org/jira/browse/NIFI-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385899#comment-15385899
 ] 

Oleg Zhurakousky commented on NIFI-2155:
----------------------------------------

[~mattyb149] I can no longer reproduce this error and I also see that the 
_org.apache.nifi.web.api.dto.DtoFactory_ has changed since you've reported it 
and line 2882 now points to an empty space in the code. Could you please verify 
that this is still a valid bug and provide steps to reproduce it?

> Cannot disable a controller service if referenced by a processor
> ----------------------------------------------------------------
>
>                 Key: NIFI-2155
>                 URL: https://issues.apache.org/jira/browse/NIFI-2155
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Matt Burgess
>            Assignee: Oleg Zhurakousky
>             Fix For: 1.0.0
>
>
> When a Controller Service (such as Database Connection Pool) is referenced by 
> a processor and enabled, then disabling it causes an NPE:
> {code}
> 2016-06-30 09:33:01,850 INFO [NiFi Web Server-79] 
> org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) 
> PUT 
> http://127.0.0.1:8989/nifi-api/controller-services/1d1acd4d-3946-4cd5-9074-94f89de5be9e/references
>  (source ip: 127.0.0.1)
> 2016-06-30 09:33:01,856 ERROR [NiFi Web Server-79] 
> o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: 
> java.lang.NullPointerException. Returning Internal Server Error response.
> java.lang.NullPointerException: null
>   at 
> org.apache.nifi.web.api.dto.DtoFactory.createRevisionDTO(DtoFactory.java:2882)
>  ~[classes/:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade.createControllerServiceReferencingComponentsEntity(StandardNiFiServiceFacade.java:1761)
>  ~[classes/:1.0.0-SNAPSHOT]
> {code}
> If the controller service is not referenced by a processor, it can be 
> disabled successfully.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to