One of our libraries is reporting this exact problem, as well. They upgraded to 3.0.9 from 3.0.2 last week and it happened both before and after the upgrade.
One of our libraries is reporting this exact problem, as well. They upgraded to 3.0.9 from 3.0.2 last week and it happened both before and after the upgrade.