Web appliction is getting hanged.... 2004-07-12 - By Guy Katz
Back
hi;
you should look and JVM flags, specifically the one that is responsible for
the memory space where the JVM loads its classes (cant remember the flag
name).
we had our application hang similar to what you describe because of the fact
that there was not enough space for the JVM to load the classes that were
used (the default is not enough for large scale applications).
-- --Original Message-- --
From: A mailing list for Java(tm) 2 Platform, Enterprise Edition
[mailto:J2EE-INTEREST@(protected)]On Behalf Of Manish Malhotra
Sent: Monday, July 12, 2004 8:41 AM
To: J2EE-INTEREST@(protected)
Subject: Re: Web appliction is getting hanged....
Thanks a lot Tim,
I understand Deadlock condition you mentioned. But Im not able to understand
the last line
'I would also look at checking for the existing row in the insert
qualification, not a separate select.'
Is this means that , I can directly insert the data and if SQL exception
throws in case of DuplicateKeyException then return otherwise insert is
automatically successful.
Please reply as soon as possible. Or if you have any other solution /
suggesion then please let me know.
regards,
Manish Malhotra
-- --Original Message-- --
From: A mailing list for Java(tm) 2 Platform, Enterprise Edition
[mailto:J2EE-INTEREST@(protected)]On Behalf Of Tim Wood
Sent: Monday, July 12, 2004 11:10 AM
To: J2EE-INTEREST@(protected)
Subject: Re: Web appliction is getting hanged....
At 09:22 PM 07/11/04, you wrote:
>Hi,
>Im working on WEB Application and server is WAS5.1.
>Im doing load testing on my applciation but unfortunately it failed.
>And the results are also abrupt. Like some times it hanged after 10
>simultaneous request. Some time goes upto 20 users an then hanged.
>The use / work of the tested screen is to insert data in the Oracle 9i
>tables. And no heavy searching is going on. But before inserting it fires a
>select query to check that the data which needs to be inserted is already
>present or not. If not then insert data.
Sounds like a classic deadlock situation; user A selects within a
transaction and sharelocks some tables; user B does his select, then
attempts an insert, which blocks on A's locks. Then A tries the insert and
it blocks on B's locks: deadlock. I say this not knowing the specific
locking behavior or how your Oracle instance is set to handle deadlocks so
it could be off the mark. I would also look at checking for the existing
row in the insert qualification, not a separate select.
TW
===========================================================================
To unsubscribe, send email to listserv@(protected) and include in the body
of the message "signoff J2EE-INTEREST". For general help, send email to
listserv@(protected) and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to listserv@(protected) and include in the body
of the message "signoff J2EE-INTEREST". For general help, send email to
listserv@(protected) and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to listserv@(protected) and include in the body
of the message "signoff J2EE-INTEREST". For general help, send email to
listserv@(protected) and include in the body of the message "help".
|
|
