CyTG
asked on
J2EE troubleshotting, repeated executions of business logic..
OC4J 9.0.4.0.0 (ejb2.0), Oracle9i, Swing client for a three tier setup...
- Problem has gotten worse over time, with code that have not been altered
- Problem persists in persistence(pun intented), we experience double insertions of data, for no apparent reason
- Business logic that should prevent this kind of behavior is not present or not executed
- User presses button once, 99% of the time only one set of inserts happen, sometimes two (few oocassions more, one time 130!!), swing client will act like 'hanging'
- Timestamp comparrision in one case revealed that there were 5 seconds between the dupes (equals 5 second client hang?)
hypothesis ; connections/operations succeed but return a false state, thus the application layer(JDBC driver?) repeats the task ? Other than that, a far fetched idea about a flawed connection pool in OC4J for transaction handling (wich does not explain the entire scenario) i am kinda blank on this one..
Of course the problem is non repeatable in 'safe envoriment' ... only happens in wild (read : production !!!!!)
Have ANYONE seens something like this before ? Im on the verge of blaming the hardware here .. nic's routers whatever ... i cant see what else ..
Funny thing is, that this HAS worked flawless for like 6mo's .. then suddenly... and in decreasing intervals...
Ideas ?
- Problem has gotten worse over time, with code that have not been altered
- Problem persists in persistence(pun intented), we experience double insertions of data, for no apparent reason
- Business logic that should prevent this kind of behavior is not present or not executed
- User presses button once, 99% of the time only one set of inserts happen, sometimes two (few oocassions more, one time 130!!), swing client will act like 'hanging'
- Timestamp comparrision in one case revealed that there were 5 seconds between the dupes (equals 5 second client hang?)
hypothesis ; connections/operations succeed but return a false state, thus the application layer(JDBC driver?) repeats the task ? Other than that, a far fetched idea about a flawed connection pool in OC4J for transaction handling (wich does not explain the entire scenario) i am kinda blank on this one..
Of course the problem is non repeatable in 'safe envoriment' ... only happens in wild (read : production !!!!!)
Have ANYONE seens something like this before ? Im on the verge of blaming the hardware here .. nic's routers whatever ... i cant see what else ..
Funny thing is, that this HAS worked flawless for like 6mo's .. then suddenly... and in decreasing intervals...
Ideas ?
TimYates
I'd start by comparing every library on both the production machine and the dev machine... You may find that there are 2 different versions of something low level...
Then I'd check that the database is not running out of ids/diskspace/log space, and see if there are any errors in any of the log files it may generate...
How long has it been since you've shut down your app server. Sorry for a MS-like "solution", but I am wondering if some cache or other issues may have built up in you containers.
ASKER
TimYates -> i have copied the entire installation from production (oc4j) to ensure the exact same setup in the test envoriment .... still not repeatable. The database is supposedly doing fine, no warnings/errors in the logs ...
bvanderveen -> actually we've begun rebooting both database and application server each night .. problem persists(pun intented again)
Thanks for the suggestions though ! :o)
Regards.
bvanderveen -> actually we've begun rebooting both database and application server each night .. problem persists(pun intented again)
Thanks for the suggestions though ! :o)
Regards.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.