Setting the idle timeout to 1 minute worked.
On Mon, Mar 17, 2014 at 9:19 AM, Stian Thorgersen <stian(a)redhat.com> wrote:
You should still be able to use Azure, you just need to configure
your
datasource to do validation, or to timeout idle connections.
Have a look at:
https://docs.jboss.org/author/display/WFLY8/DataSource+configuration
http://www.ironjacamar.org/doc/userguide/1.1/en-US/html_single/index.html...
https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Appli...
----- Original Message -----
> From: "Dean Peterson" <peterson.dean(a)gmail.com>
> To: "Stian Thorgersen" <stian(a)redhat.com>
> Cc: keycloak-user(a)lists.jboss.org
> Sent: Monday, 17 March, 2014 2:02:53 PM
> Subject: I think I know the cause of my JPA transaction errors
>
> I have mentioned it before but I am trying to get things to work using an
> Azure MS-SQL database. Yes, I remember being told you will not support
> that. Just in case it will spark some ideas I want to mention that I
found
> Azure closes database connections after one minute and end users have no
> control over that:
>
http://blogs.msdn.com/b/avkashchauhan/archive/2011/11/12/windows-azure-lo...
>
> This is the behavior I am seeing. I log in, let the application sit
until
> I am automatically logged out and I always get this timeout error (sql
> error: 0, SQLState: 08S01) when the JpaKeycloakSession.close() method is
> called. I will probably have to switch to a local database.
>
>
>
> >
>