After upgrading my application to WebLogic 10.3.4, I am facing an issue with the cache implementation. The data in the drop downs in my application are cached and it used to populate properly when the application was deployed in WLS9.2. But after moving to 10.3.4, I had to restart my managed servers & clean the /tmp folder manually to populate those data. Once the data is populated , again within 24hrs or so, the data would not get populated again & I would need to restart the managed servers again.
I don't think this could be an issue with 10.3.4 but, I am not sure whether there are any settings which I need to do while configuring the Weblogic 10.3.4. There is no code change involved except that the code is complied in Java 1.6 instead of 1.4.
I am wondering is there any known issue against 10.3.4 associated with this issue.
are you running multiple WL Server instances on the same machine?
Prasanth S Pillai
Joined: Oct 28, 2009
I have a clustered enviornment with 1 admin server and 3 managed servers in 3 machines. To be precise, 1 Admin Server and 1 Managed Server in machine A, next managed Server is machine B and the 3rd managed server in machine C.