-
1. Re: Connection problems with DatabaseServerLoginModule
jwkaltz May 17, 2002 11:27 AM (in response to kdavey67)I have a similar problem, even though I'm using ldap connections.
I'm afraid the only answer I can give you is that you can write your own LoginModule (which look very much like the DatabaseServerLoginModule), where you would handle that error and try again automatically. This is definitely one possibility; perhaps there is way to configure the DatabaseServerLoginModule to handle this but I am not aware of it. In any case, I suggest as a starting point to look at the source code DatabaseServerLoginModule.java -
2. Re: Connection problems with DatabaseServerLoginModule
kdavey67 May 17, 2002 1:41 PM (in response to kdavey67)Thanks, that was what I was suspecting that I needed to do. Will try it.
kmd -
3. Re: Connection problems with DatabaseServerLoginModule
starksm64 May 19, 2002 8:23 PM (in response to kdavey67)The DatabaseServerLoginModule does not hold onto a connection. It obtains a connection from the configured DataSource on each login and closes it immediately. If stale connections are showing up it is an issue with the DataSource connection pooling.
-
4. Re: Connection problems with DatabaseServerLoginModule
davidjencks May 19, 2002 9:16 PM (in response to kdavey67)Its always helpful to mention which jboss version you are using. In 3 >= rc2, you can just set idleTimeoutMinutes. It is possible to set an idletimeout in 2.4 versions, but you have to set several other parameters at the same time. Search the archives for instructions.
-
5. Re: Connection problems with DatabaseServerLoginModule
kdavey67 May 20, 2002 6:13 PM (in response to kdavey67)I am using version 2.4.6 and in my connection pool to Oracle I have a connection idle timeout already set. The connections appear to timeout properly when they are used in the application. I did not think that this was a timeout issue. It appeared to me that the loginModule was holding on to the connection and not getting a new one when the first person tried to login in. The second attempt at logging in works just fine.
100
1800000
false
kmd