Hi Benson,
I actually thought max wait timeout served this purpose.
But since you tell me this doesn't work, I'll look further into this
tomorrow. If necessary I'll file a bug/RFE.
But a workaround did cross my mind. While not possible on glassfish, you can
always set a maximum table lock time on the database table/server.
This should have a similar effect.
At least you should be able to use this for development (and maybe even in
prod) until you know of a better solution, since making the change
afterwards will not require modifications to the source code.
Sorry I can't be of more help right now.
Wim
-----Original Message-----
From: Wim Verreycken [mailto:wim_at_pizzastop.be]
Sent: dinsdag 26 augustus 2008 23:54
To: users_at_glassfish.dev.java.net
Subject: RE: Strange Server behaviour
I'm looking at this now. By the way I think the previous solution will also
not have the desired effect. I think this TransactionTimeout is the maximum
timeperiod in which it is possible to commit(). So that is not what you
want. I'll look into it further, but I don't know it right away.
-----Original Message-----
From: Wim Verreycken [mailto:wim_at_pizzastop.be]
Sent: dinsdag 26 augustus 2008 16:29
To: users_at_glassfish.dev.java.net
Subject: RE: Strange Server behaviour
Don't know if I can help here.
At first I thought when reading this :
Isn't that the whole idea behind transactions??
Then I realized you app probably keeps waiting and waiting even after
sqlplus commits.
No sure if it helps, but you might wanna take a look at :
http://java.sun.com/j2ee/1.4/docs/api/javax/transaction/UserTransaction.html
Wim
-----Original Message-----
From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
Sent: dinsdag 26 augustus 2008 13:31
To: users_at_glassfish.dev.java.net
Subject: Strange Server behaviour
Hi,
The behavious is related to the DB transaction behaviour. Here is the setup
:
1. Oracle DB
2. Sun App. Server 8.1
There is an application running on App. Server 8.1 which is to update/insert
a record in a table. What I did right now is.
1. Using sqlplus to update a record but not commit.
2. Using the application to update the same record.
The server behaviour is :
1. It starts to wait for the sqlplus to commit I guess
2. The application keeps waiting and displays server busy blue screen
after 10 mins.
I tried to change the different timeout value(Transaction timeout, Retry
timeout, Max Wait Timeout) into shorter interval, but the server still takes
10 mins to display server blue screen.
Please suggest how to shorten the 10 mins interval.
Thanks
Benson
[Message sent by forum member 'bensonfungjava' (bensonfungjava)]
http://forums.java.net/jive/thread.jspa?messageID=295340
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net