Java Caching for Oracle Applications 11i: Part 2
In my previous article "Java Caching for Oracle Applications 11i: Part 1" I talked about the basics of Java Caching and how it works conceptually.

My original intention with "Part 2" was to discuss how to diagnose issues with Java Caching, but I got a bit carried away with scripts and the like so ended up creating some Metalink notes instead.
Diagnosing Database Invalidation Issues
Here's the first one:
- Diagnosing database invalidation issues with Java Cache for eBusiness Suite (Metalink Note 455194.1)
As it says on the tin, this note covers diagnosing issues with Database Invalidation. The classic symptoms being that when Responsibilities are added to a user, they are not appearing immediately (but do after Apache is bounced).
Although the scripts are listed in the note, you can also download a soft copy via the link mentioned in the note.
Diagnosing Issues with Responsibility Assignments
This issue is not actually a Java Caching problem, but the symptoms
initially look similar to those described above. The key difference
here is that the affected responsibilities still do not appear after
Apache is bounced. For details, see:
- Existing Responsibility Does Not Appear after modifying the effective date (Metalink Note 458869.1)
More on NoClassDefFoundErrors
- Investigating NoClassDefFoundError in eBusiness 11i when users login (Metalink Note 455366.1)
Hopefully you will find these notes useful towards understanding and diagnosing any Java Cache issues you find yourself facing.
Related
- Java Caching for Oracle Applications 11i: Part 1
- Latest JVM Tuning Recommendations for Apps 11i
- Using JConsole to monitor Apps 11i JVMs
- Investigating java.lang.OutOfMemoryError with Apps 11i Middle Tier JVMs
Recent Comments