Application Server returning before transaction is flushed

[Alex Kudlick]

Hi,

We're having a problem that has manifested more frequently as our database load increases. The problem seems to be that the application server sometimes returns a result before the transaction is fully committed.

We have an access pattern where clients make a POST to create a user, then use the token from the response to authenticate for subsequent requests. Sometimes the next request using the token doesn't see the user identified by the token in the database. Whenever I check later the data is present. It only fails on the requests that come immediately after the first create request.

We use Mysql 5.6, dropwizard 1.2.9, and dropwizard-hibernate 1.2.9

Any help would be appreciated. 

[Jochen Schalanda]

Hi Alex,

Dropwizard 1.2.x is quite ancient. Please try upgrading to Dropwizard 2.0.x and see if it resolves your issues.

Cheers,

Jochen

--
You received this message because you are subscribed to the Google Groups "dropwizard-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dropwizard-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dropwizard-user/d6c0dd7f-6192-4e94-aac0-ed1c4de5abdan%40googlegroups.com.