John, Could you fetch the latest from that branch? It has one of the commits for MINIFI-246 within it.
On Fri, Mar 31, 2017 at 11:05 AM, Marc P. <[email protected]> wrote: > The issue is related to https://issues.apache.org/jira/browse/MINIFI-246. > > I'm able to easily re-produce it. I submitted a PR for that but I'm going > to verify that it is indeed fixed and push the fix to that branch so you > can test it. I'll update you shortly. > > On Fri, Mar 31, 2017 at 11:03 AM, jbkuyke <[email protected]> wrote: > >> Hi, Marc-- >> >> It's actually from one of your branches: https://github.com/phrocker/ >> nifi-minifi-cpp/tree/MINIFI-239 >> <https://github.com/phrocker/nifi-minifi-cpp/tree/MINIFI-239>. Config >> file below. >> >> Thanks! >> >> >> >> # Licensed to the Apache Software Foundation (ASF) under one or more >> # contributor license agreements. See the NOTICE file distributed with >> # this work for additional information regarding copyright ownership. >> # The ASF licenses this file to You under the Apache License, Version 2.0 >> # (the \"License\"); you may not use this file except in compliance with >> # the License. You may obtain a copy of the License at >> # >> # http://www.apache.org/licenses/LICENSE-2.0 >> # >> # Unless required by applicable law or agreed to in writing, software >> # distributed under the License is distributed on an \"AS IS\" BASIS, >> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. >> # See the License for the specific language governing permissions and >> # limitations under the License. >> Flow Controller: >> id: dfbdefde-d9f4-4d93-bee8-9807d83bca9b >> name: MiNiFi Flow >> Processors: >> - name: GetFile >> id: 471deef6-2a6e-4a7d-912a-81cc17e3a206 >> class: org.apache.nifi.processors.standard.GetFile >> max concurrent tasks: 1 >> scheduling strategy: TIMER_DRIVEN >> scheduling period: 1 sec >> penalization period: 30 sec >> yield period: 1 sec >> run duration nanos: 0 >> auto-terminated relationships list: >> Properties: >> Input Directory: /tmp/getfile >> Keep Source File: true >> File Filter: ".*" >> - name: InvokeHTTP >> id: 2895e9dc-1555-11e7-ad3e-02420a006502 >> class: org.apache.nifi.processors.standard.InvokeHTTP >> max concurrent tasks: 16 >> scheduling strategy: EVENT_DRIVEN >> scheduling period: 1 sec >> penalization period: 30 sec >> yield period: 1 sec >> run duration nanos: 0 >> auto-terminated relationships list: >> Properties: >> HTTP Method: POST >> Remote URL: "localhost" >> - name: ListenHTTP >> id: 98906056-14af-11e7-a4be-02420a003702 >> class: org.apache.nifi.processors.standard.ListenHTTP >> max concurrent tasks: 16 >> scheduling strategy: TIMER_DRIVEN >> scheduling period: 1 sec >> penalization period: 30 sec >> yield period: 1 sec >> run duration nanos: 0 >> auto-terminated relationships list: >> Properties: >> Listening Port: 8888 >> - name: LogAttribute >> id: 2579157d-c331-4016-918d-8cd6f7d56e51 >> class: org.apache.nifi.processors.standard.LogAttribute >> max concurrent tasks: 1 >> scheduling strategy: EVENT_DRIVEN >> scheduling period: 1 sec >> penalization period: 30 sec >> yield period: 1 sec >> run duration nanos: 0 >> auto-terminated relationships list: [ success, failure ] >> Properties: >> Connections: >> - name: TransferFilesToPost >> id: 471deef6-2a6e-4a7d-912a-81cc17e3a207 >> source id: 471deef6-2a6e-4a7d-912a-81cc17e3a206 >> source relationship name: success >> destination id: 2895e9dc-1555-11e7-ad3e-02420a006502 >> # destination id: 98906056-14af-11e7-a4be-02420a003702 >> max work queue size: 0 >> max work queue data size: 1 MB >> flowfile expiration: 60 sec >> - name: ListenHTTPToLog >> id: 98906056-14af-11e7-a4be-02420a003702 >> source id: 98906056-14af-11e7-a4be-02420a003702 >> source relationship name: success >> destination id: 2579157d-c331-4016-918d-8cd6f7d56e51 >> max work queue size: 0 >> max work queue data size: 1 MB >> flowfile expiration: 60 sec >> Remote Processing Groups: [] >> >> >> On Fri, Mar 31, 2017 at 10:55 AM, Marc <[email protected]> wrote: >> >> > Hi Jon, >> > Are you running this from master? >> > >> > I have seen that error. Can you provide your config YAML file? >> > >> > On Fri, Mar 31, 2017 at 10:53 AM, John Kuykendall <[email protected]> >> > wrote: >> > >> > > Hello-- >> > > >> > > I'm new to nifi development. I'm working with a minifi graph that runs >> > > successfully the first time I set it up, but then each subsequent >> time it >> > > terminates with: >> > > >> > > terminate called after throwing an instance of 'std::bad_weak_ptr' >> > > what(): bad_weak_ptr >> > > Aborted (core dumped) >> > > >> > > If I rebuild (or even just restart the vm I'm working on), it again >> works >> > > the first time, but not subsequent times. >> > > >> > > Has anyone seen this type of error before? >> > > >> > > Thanks, >> > > John >> > > >> > >> > >
