Grails Database Session Plugin June 6, 2012 | 02:07 pm

I’ve done a fair bit of updating to the Grails Database Session Plugin (originally written by Burt Beckwith), and
it is now released. The plugin solves the problem of cloud services often not having sticky sessions/session affinity, so as soon as you ramp up a second Grails application, you’re losing sessions now and again.

If you want more information on this plugin, check out this month’s GroovyMag (June 2012), where I’ve got an article going over the whole thing, including the differences in implementations, a peak under the hood, and extensive details on how to use the plugin. A summary version of it is available in the README file.

BTW, if you’d like a free copy of this month’s GroovyMag, tweet me and let me know: I have a few coupons to share around.

  • http://sourcedelica.com/blog Eric P

    This was a great article. Thanks!

  • http://clear-retainers.com/ David Rothstein

    Thanks Robert! For the post and link to the article. The article is very informative. Will tweet you for the free copy. Thanks!!

  • invalid-access

    Thanks for sharing! I’m trying to decide between using your plugin vs using Burt’s at http://grails.org/plugin/database-session. How would you compare the two? My use-case is for a Heroku integration.

  • http://robertcfischer.com/ Robert Fischer

    My work is a fork of his. I store data more efficiently than he does and have some additional functionality. He’s Burt. So it’s probably about even. :)

  • invalid-access

    LOL :-) Ok I’ll play around with both. Convince Burt to give his blessing and merge in your version as the ‘official’ grails database-session plugin?

  • Abhay

    Hey Robert.. Great plugin. It worked like a charm. Unlike the official plugin which did not work with multi-tenant-single-db plugin, your implementation worked great. One minor issue, even after logout, it appears to maintain previous session data. I redirect to the login page after logout.

    On debugging, I see that it clears the db row fine but somewhere in the chain it repopulates this data and persists it back.

    I’m writing here in the hope that you’d be able to point me to the right direction.

  • Abhay

    Hey Robert.. Great plugin. It worked like a charm. Unlike the official plugin which did not work with multi-tenant-single-db plugin, your implementation worked great. One minor issue, even after logout, it appears to maintain previous session data. I redirect to the login page after logout.

    On debugging, I see that it clears the db row fine but somewhere in the chain it repopulates this data and persists it back.

    I’m writing here in the hope that you’d be able to point me to the right direction.

  • Abhay

    Hey Robert.. Great plugin. It worked like a charm. Unlike the official plugin which did not work with multi-tenant-single-db plugin, your implementation worked great. One minor issue, even after logout, it appears to maintain previous session data. I redirect to the login page after logout.

    On debugging, I see that it clears the db row fine but somewhere in the chain it repopulates this data and persists it back.

    I’m writing here in the hope that you’d be able to point me to the right direction.

  • Abhay

    Hey Robert.. Great plugin. It worked like a charm. Unlike the official plugin which did not work with multi-tenant-single-db plugin, your implementation worked great. One minor issue, even after logout, it appears to maintain previous session data. I redirect to the login page after logout.

    On debugging, I see that it clears the db row fine but somewhere in the chain it repopulates this data and persists it back.

    I’m writing here in the hope that you’d be able to point me to the right direction.

  • Abhay

    Hey Robert.. Great plugin. It worked like a charm. Unlike the official plugin which did not work with multi-tenant-single-db plugin, your implementation worked great. One minor issue, even after logout, it appears to maintain previous session data. I redirect to the login page after logout.

    On debugging, I see that it clears the db row fine but somewhere in the chain it repopulates this data and persists it back.

    I’m writing here in the hope that you’d be able to point me to the right direction.