Apologies, I am talking about the DBCPCOnnectionPoolLookup. Long day...
On Thu, 25 Oct 2018, at 23:13, Martijn Dekkers wrote:
> Hello all,
>
> We ran into a weird issue. We use a DBCPConnectionPool to select the
> correct db for specific queries. Every so often (3 times now today,
> few times yesterday) the DBCPConnectionPool will bug out with
> "Attributes must contain an attribute name 'database.name'" event
> though the database.name attribute is present in the flowfiles, and
> correct.>
> Sometimes restarting the ConnectionPool will help, sometimes it just
> "fixes" again. We have several SQL processors using this pool, and
> some send lots of small queries, and these are in different process
> groups. The issue always occurs with a specific PutSQL processor. We
> have a few ExecuteSQL processors that work fine.>
> The logs don't show anything out of order.
>
> Can anyone suggest a more thorough way of debugging this?
>
> Thanks
>
> Martijn
