Attempting to post your first DiSCOs across multiple threads causes Agent error

[karenhanson]

If you attempt to load DiSCOs using multiple threads, on the first round some fail due to a missing Agent record. The first thread creates the Agent, the next thread sees the Agent URI in the database, but when it tries to retrieve it, it's not yet in the graphdb, and so on. After the first round-trip, it's fine, but need some work to coordinate database transactions with triplestore transactions better.

[karenhanson]

I have noticed a problem with the first DiSCO on a new build returning a successful response though the graph is not saved - needs further investigation in general. You can replicate this by spinning up a local instance, posting a DiSCO and then trying to retrieve it. It is not in the database.