Re: Strange behavior with PutSQL

2018-08-15 Thread Lone Pine Account
That was it! The fragmented transactions settings were not correct. Thanks a million! On Wed, Aug 15, 2018 at 11:12 AM, Matt Burgess wrote: > Do you have a Split processor upstream? If so, is the setting of > Support Fragmented Transactions in PutSQL set to true? That > combination will have

Re: Strange behavior with PutSQL

2018-08-15 Thread Matt Burgess
Do you have a Split processor upstream? If so, is the setting of Support Fragmented Transactions in PutSQL set to true? That combination will have PutSQL try to find all the flow files with the same "fragment.id" attribute, and will only proceed if it gets "fragment.count" of them (all the flow

Re: Strange behavior with PutSQL

2018-08-15 Thread Lone Pine Account
Where would I look to see if that was the case? Is that not logged as an error somewhere? On Wed, Aug 15, 2018 at 10:49 AM, Juan Pablo Gardella < gardellajuanpa...@gmail.com> wrote: > Probably connection pool is exhausted. > > On Wed, 15 Aug 2018 at 11:44 Lone Pine Account > wrote: > >> I have

Re: Strange behavior with PutSQL

2018-08-15 Thread Juan Pablo Gardella
Probably connection pool is exhausted. On Wed, 15 Aug 2018 at 11:44 Lone Pine Account wrote: > I have a simple flow that takes the output of a ReplaceText processor and > sends it to PutSQL. > > This has been working in the past with a "toy" configuration. Now that > I'm testing it on a larger