In Weblogic 10.3.5, is there any way to expire an html file from cache without going through a server restart - caching

In Weblogic 10.3.5, is there any way to expire an html file from cache without going through a server restart. I am supporting a server with frequent HTML changes and hoping to find a way not to restart the server each time the HTML is updated. Environment is supporting a PeopleSoft domain. Thanks.

There's a way indeed, the parameter "Resource Reload Check (in seconds)" which can be found on a web app setup is what you're looking for. I've setup this to 5(secondes) in order to have a periodic refresh on dynamic ressources generated by an application engine (an xml parsed by an xslt)
For some details here's doc of 12.1.2 but I confirm it exists also on 10.3.4 (so on your version too) : https://docs.oracle.com/middleware/1212/wls/WLACH/pagehelp/J2EEwebappwebappconfigurationtitle.html

Related

Kibana not saving dev tools history across sessions

I have Kibana plugin installed in each ES node. Kibana is behind nginx reverse proxy because it's served from /kibana/ route. Elastic is protected with SearchGuard plugin.
Question: History for dev tools/console is reset with each login (after each login, history is empty). Now, I'm not sure if I'm missing something or that's expected behaviour when SearchGuard is in use? I remember that worked well before installing SearchGuard. Not sure if it's coincidence or it's indeed related. It's saving properly during one session.
Elastic version: 6.1.3
Thank you!
It's stored in local storage under sense:editor_state in Chrome.
If it's wiped out daily or the cache is cleared, so will your searches be.
use ?load_from= in your url and save your queries in a json file... be aware of CORS if you use a web app of your own.

Remove limits on parse server after migration

I've migrated my parse app on a IBM Bluemix hosting using this node js app https://github.com/ukmadlz/parse-on-bluemix
Despite the parse server is now installed only on my hosting environment I'm trying to remove the very annoying limit of 30 requests per sec.
Does anybody know how to that? I've tried looking into parse server source code but I couldn't spot it..
Thanks
It's was already removed in parse server open source.

JDeveloper 11.1.1.6 weblogic startup issue

I created an simple skeletal web application. I created only a simple blank JSF page. Right click and run. Then I got the following message in the Log console.
The Server Instance cannot be started because the Integrated Weblogic domain was not built successfully.
Can anybody suggest me why I am getting this error?
Your question does not provide detailed information.
The best way would be to go to weblogic domain options from start menu and create a new domain.
Then link that domain in jdeveloper and use the same. Delete the integrated domain i.e. base_domain folder.
There were 2 ways this problem can be fixed:
Try starting and fixing any issues with the Integrated weblogic domain. Till that is not starting successfully, JDeveloper cannot do anything on that. For me one time startup of the current domain outside of the Jdeveloper solved the issue. After that it was working fine from JDeveloper too.
Another option is as stated by vijayinani above to create a new domain and link it. But, beware your integrated base_domain is not having anything which you need to preserve if you plan to delete that.

VS2013 Web Deploy Replace from Server error

I have deployed web applications using web deploy on to iis7.5 without issues, the preview works and It updates only the necessary files when publishing again. We have designers who like to change the css files with FTP and I thought the Replace fileName from server commands in Visual Studio would be great to pull their changes into TFS.
Every time I run it it comes up with the error :
The synchronization is being stopped because the maximum number of sync passes '5' has been exceeded even though all the changes could not be applied. This could occur if there are external changes being made to the destination.
If anyone could shine some light on the error or some documentation regarding this feature, that would be great.
Web Deploy does at least 2 passes to do a remote sync (when either the client or server is remote which is in your case too). At the end of these passes, web deploy does a metadata check to see if all the files are in sync.
If by then other changes have happened (such as someone else started a web deploy sync to the same destination, or a few files were edited via the web or via ftp or any other means) then web deploy will attempt a 3rd pass to get them in sync with the source. If the changes keep happening the passes will keep happening.
But since we dont want to sync the content for ever we placed a max retry limit of 5. You can actually override to something higher but its not recommended.
Update:
You can set this in two ways:
pass in a flag -retryAttempts=7 (or any number) to msdeploy from command line
Set RetryAttemptsForDeployment in VS targets or use it as an MSBuild property. Its described here

Liferay Community Edition centralized/shared storage issue

For quite some time I've been working on getting the community version of Liferay 6.0.6 (windows 2003 + Apache Httpd 2.2 + Apache Tomcat 6.0.29 ) to run on shared storage environment. Only the application base (webapps) is currently running from the shared storage. But I also wanted to move the "data" and "deploy" directory to the shared storage. So please provide any custom settings/changes that needs to be performed to change the location of these two directories/folders.
Whenever I change the "deploy destination directory" some portlets work, but not all (Custom portlets). It'll be great if anybody can provide certain points/checklist which needs to be followed in this situation.
Additionally, the configurations files used are attached along with this thread. If any other files is needed please let me know the same.
Thank you for your support in advance. All efforts are appreciated.
Thanks,
Joji VJ
Try to set Cache Page Definition Only at System Level,
By using this option create a single cached copy of the page definition in the system cache for all users.
Because the page definition is the same for all users, page customization options are disabled. This caching option greatly reduces storage requirements and improves performance.

Resources