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 < [email protected]> wrote: > Probably connection pool is exhausted. > > On Wed, 15 Aug 2018 at 11:44 Lone Pine Account <[email protected]> > 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 input set, it is not working but I can't figure >> out why. >> >> Attached is my setup. The ReplaceText processor fills up the success >> queue, and rather than processing these it appears that the PutSQL just >> keeps filling up its "In" port with more copies of them - the number of >> "In" for PutSQL keeps going up, but nothing comes off the success queue. >> >> So I'm trying to debug: >> - I've attached LogAttribute processors to the ReplaceText processor, and >> verified that the SQL commands are correct. >> - I've attached LogAttribute processors to all of the PutSQL >> relationships, and none receive output. >> - I've looked through the app logs and there is nothing coming up for my >> PutSQL processor. >> >> Where can I look to figure out why the PutSQL processor is no longer >> writing to the database? >> >> Thanks >> >
