WebLogic JDBC - Profile Harvest Frequency Seconds

Question

In the company I'm providing consulting services, when the database is updated by a process outside Weblogic Web Application, the updated data is not refreshed at once. Googling a bit I've found the following parameter in JDBC configuration:

Profile Harvest Frequency Seconds

The number of seconds between when WebLogic Server harvests profile data.
When set to 0, harvesting of data is disabled.
MBean Attribute (Does not apply to application modules): 
JDBCConnectionPoolParamsBean.ProfileHarvestFrequencySeconds

Minimum value: 0
Maximum value: 2147483647

The default is set to 300.

Is this parameter that does the cache expiration? Or there's another configuration?

My idea is to expire the cache after 2 minutes.

score 0 · Accepted Answer · edited Aug 14 '13 at 15:33

0

This parameter sets how often JDBC connection is profiled and the profile information logged to your logs. http://docs.oracle.com/cd/E15051_01/wls/docs103/jdbc_admin/monitor.html

Are queries not returning the updated data? Could be a combination of the app, browser cache or another caching mechanism. If you can expand on the nature of the app and components involved, perhaps someone here could direct you in the right direction.

edited Aug 14 '13 at 15:33

Leonel Sanches da Silva

115
5

answered Aug 14 '13 at 00:14

KM.

1,746
2
18
31

Possibly should be something related with the App JPA configuration. Thank you. – Leonel Sanches da Silva Aug 14 '13 at 15:12

WebLogic JDBC - Profile Harvest Frequency Seconds

1 Answers1