[ 
https://issues.apache.org/jira/browse/NIFI-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Kell resolved NIFI-2179.
----------------------------------
       Resolution: Not A Problem
    Fix Version/s:     (was: 1.0.0)

It had something to do with a custom nar

org.apache.nifi.nar.ExtensionManager Attempt was made to load 
org.apache.nifi.dbcp.DBCPConnectionPool from 
org.apache.nifi.nar.NarClassLoader[.\work\nar\extensions\nifi-dbcp-service-nar-0.6.1.nar-unpacked]
 but that class name is already loaded/registered from 
org.apache.nifi.nar.NarClassLoader[.\work\nar\extensions\nifi-hsdg-nar-1.0.nar-unpacked].
  This may cause unpredictable behavior.  Order of NARs is not guaranteed.

> ExecuteSQL and PutSQL can't assignt controller service
> ------------------------------------------------------
>
>                 Key: NIFI-2179
>                 URL: https://issues.apache.org/jira/browse/NIFI-2179
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 0.6.0, 0.6.1
>         Environment: Windows 7 , Linux Red Hat Enterprise
>            Reporter: Alexander Kell
>            Priority: Critical
>              Labels: ControllerService, SQL
>         Attachments: Wrong_controllerservicetype.png
>
>
> ExecuteSQL Processor is broken, it is not possible to assignt a neccesary 
> controllerservice connection.
> I created a working SQL Controller , it is not possible to assignt this 
> controller to created ExecuteSQL Processor , even if i create one 
> controllerservice out of property page , it is not possible for the processor 
> to use this service. 
> It has probably nothing to do with changes in processor code ... it has 
> probably spomething to do with controller service  ... i just tested it with 
> 0.5.0 and it works ... it is broken since 0.6.0
> Maybe it has something to do with NIFI-1800: Tie Controller Services to 
> Process Groups.
> or 
> NIFI-1994: Fixed issue with Controller Service Fully Qualified Class 



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

Reply via email to