Task #1029
Case HD00011364 - Internet Banking Slow
| Status: | Development / Work In Progress | Start date: | July 13, 2011 | ||
|---|---|---|---|---|---|
| Priority: | Normal | Due date: | |||
| Assignee: |  Sarinah Darsy | % Done: | 70% | ||
| Category: | - | Spent time: | - | ||
| Target version: | - |
Description
Dear IT Server Team & Penril,
Today we received 2 complaints from customer:
a) Hasrin Abdul Rahim
- Login unsuccessful for the past 2 days (12 & 13/7/11) after keying the security question. Screen keeps looping until time out.
- His last successful login was on 8/7/11
b) Siti Zulaikha Abdullah@Choong Yen Moy (Penang Branch)
- Unable to login and received response security question is unmatched whereby customer is 100% sure that her login id & password are correct.
- Her last successful login was on 8/7/11
History
#1
Updated by Sarinah Darsy about 13 years ago
- Status changed from New - Begin Life Cycle to Development / Work In Progress
- Assignee set to Sarinah Darsy
- % Done changed from 0 to 70
This issue rectified by IT that inside Oracle there are a lot inactive session in DB for BVUSERPRD schema.
They assume that our IB didn't flush the session properly.
They ask penril to check on the session in IB once the session time out, we need to flush it.
#2
Updated by Sarinah Darsy about 13 years ago
Hi All,
I google about the DB session inactive, found this on an open forum said:
(source: http://www.velocityreviews.com/forums/t142384-inactive-oracle-sessions-due-to-jsp.html)
After lots of finding around here is how I resolved the problem:
Instead of simply calling close() methods I set them to null as well:
if (statement != null) {
statement.close();
statement = null;
}
if (connection != null) {
connection.close();
connection = null;
}
Apparently what this does is it allows the garbage collector to do its
thing on these objects.
I also made sure I closed all my resultSets in a similar way.
As a result I now have ZERO inactive sessions.
Checked at our coding, we only set method session.close() but never define it back to null.
I think this is the solution.
I will try to apply it on our application and test it whether it resolve the problem of session inactive or not.