This is driving me up the wall.
I have a web application deployed on a JBoss server. The application works fine and dandy most days, but randomly, without warning, will suddenly throw "404" on image and javascript files, causing the page to display a blank page. The problem persists until I restart the JBoss service.
Users need to log-in first to be able to reach the page, which still works, but when this happens, right after logging in, nothing works. Checking the source and Firebug show that the main landing jsp is retrieved, but many other things 404 saying that the resource cannot be found.
There have been no path changes and no work done and the app can still be working one moment and stop the next. The log files don't show any peculiar behavior during this time period.
Are there any ideas on what could be causing this? If you need more information, I will gladly provide as I'm not sure where to begin looking.
EDIT:
I've noticed that the 404'd files are all in subdirectories of my WAR file. The pages that can still be retrieved aren't contained in subdirectories of the war file, but all the ones that become unavailable are inside folders like /images and /javascript. Is it possible there was a scanner failure?
I changed the file encoding of every jsp file from ISO-8859-1 to UTF-8.
It's been a week or so and the issue hasn't been reported again. Hopefully this is the solution.
No answer to your problem, just a tip: if you've bought EAP-licenses, you should be able to open support-cases at https://access.redhat.com.
Related
Friend gave me access to TYPO3 CMS of his page to make some changes and I can not open Filelist.
The left panel with directories is displaying but on the right, a have error 500 message in IE or in Chrome just empty frame.
I did some modifications to that page some time ago and everything was working fine then.
Can anyone help me with that ?
If a folder contains to much files you might get problems opening it in the file list module, as the gathering of all information and maybe creating of preview thumbnails may take longer than is granted to any php process.
If it's only the preview images you might be able to load the folder after some attempts, as sometime all preview images are generated, but as it also can be other delays because of too much files you need to enhace the runtimelimit
or/and you might need to restructure the files and folders.
Be aware that a moving of files with FTP/SSH might break content in the FE as you might invalidate some FAL (sys_file) records so that used files are not found any more. Better: enhance the timeout (temporarily) and move the files in the backend.
in general: if you only got a blank page you disabled all error-messages (which is ok for FE, but will leave you without hint about errors).
As a first start you could take a look in the webserver-error-log.
If you got no clues: enable errormessages in TYPO3 Install Tool (enable debug mode in "Configuration presets")
Ok.
I solved that.
I disabled that extension and then when I looked at maintenance tab on this extension i saw something like "delete LOCAL installation of this ext".
After deleting local installation and enabling system FileList instance, everything is working just fine :)
Thank You for help.
Codekit is so darn slow in reloading files. Why is that and what can I do against it?
I use MAMP3 on Yosemite with Chrome 39. Refresh delay is on 0 seconds.
I just have a bunch of php files and some less. Nothing extraordinary.
And it reloads the files with a delay of about 10seconds.
The LESS files are compiled very fast, but not the page reload. Internet sharing is deactivated.
What else could be the problem?
From time to time there is a message Codekit connection is unstable. But everything is hosted local. How can this be unstable?
Okay. I figured out some things who slow down codekit significantly.
Mistake Nr. 1: Amount of Files
It seems to play a huge role how much files are added per project. My cms lives outside webroot but my less & css live inside webroot. So I threw in the whole project including the cms. This way I had no path conflicts (lazy me). This resulted in about 4000 Files. That is too much for codekit.
Solution: Still throw in the whole project but exclude the cms folders in codekit (Yeah I know RTFM)
Mistake Nr. 2: custom file extension
I started to work with twig files (after php was done) and miraculously browser refresh stoped working. Because Codekit doesn't doesen't seem to know twig. In order to keep Browser reload working one have to add twig into the Generig Page Extensions.
Thats it. Everything works just fine now.
I have an issue in updating contents in Umbraco. Whenever I update something in Umbraco, I have to wait at least one hour, sometimes 12 hours to see the changes at front-end.
The only way to see the changes immediately at front-end is "empty the connection string value umbracoDbDSN and refresh the page, then put the connection string back and refresh the page". I have to do everything I update something in CMS.
Do you guys have any idea what is happening here? Thanks.
The problem was. Umbraco was configured to run on load balanced servers on our old servers. I had to turn it off on the new server.
<distributedCall enable="false"> in umbracoSettings.config
What version are you running? When v5 first came out, I had a big problem with that (and solved it like you by touching the web.config to force a reset. Hopefully you are not using v5 (as its been discontinued and has extreme performance issues).
I have not had that problem in any v4.x versions that I can remember; changes should show up instantly after you republish.
Are you running in a standard configuration? Using a webfarm by anyt chance?
Is the ~/App_Data/umbraco.config file being written to on publish? This is the XML cache file that is used in displaying you website.
When you publish a node, the data is serialized into XML, stored in a database table and then written out to the umbraco.config cache.
This could be some kind of permissions issue, if umbraco doesn't have rights to read/write the file. Or you could have a corrupt dll that just isn't writing to it correctly. Or perhaps it's writing it out just fine, but your server is caching you pages in a weird way. Either way, I'd take a look first at the umbraco.config and make sure the data is being written to it on publish.
I have deployed and then redeployed a .wsp on a Sharepoint 2010 server (the solution was developed on another 2010 server). The solution contains 2 web parts.
After retracting and removing the old solution, I added and deployed the same solution again, with no errors.
Afterwards, I deactivated and reactivated the feature installed through my .wsp file.
The problem is that whenever I try to add one of those 2 web parts to a page, I get an error saying "The operation could not be completed because the item was removed from the gallery".
Do you have any ideea what's happening? Anu help is greatly appreciated!
Usually this happens if the web part gets orphaned in the web part gallery. Try Deactivating your solution and Retract and Uninstall your wsp. Then check the Web Part Gallery for the site collection. If you still see your web parts there then manually delete them.
Then you can Add and Deploy your wsp and activate your solution. The web parts should then be available in the web part gallery and be able to be added to your pages.
I came across a more simple solution which worked well for me.
Go to the webparts gallery at Site Settings/Galleries/Web parts and delete problematic webpart entry. Then deactivate and reactivate the wsp which contains that webpart and everything should work fine. No need for redeployment or uninstalling.
Source
I have the same issue, but in my case after a thorough search in web part gallery found out that some web parts having the same name, but without assembly's prefix have created.
The solution is just to sort the web parts with the date and you'll get the new web parts.
Some times it happens that every thing is same as before, but SharePoint forgets the settings which are placed in webpart.xml file
This is driving me crazy. I'm developing an app in the NetBeans IDE in PHP, using the CodeIgnitor framework. I am making code changes to js and css files in NetBeans, saving them but the files the browser is loading do not contain the code changes. When I open the files directly outside of NetBeans, the saved changes aren't there.
I'm storing the javascript & css files in a folder called static, which is outside of the 'application' directory in CodeIgnitor. What's weird is any code changes in PHP files work fine. I'm guessing NetBeans is saving the changes to the js/css files somewhere else but can't find them on my hard drive. This just started happening, it was working 'normally' before.
Thanks for the help.
Al
I had the same problem, upon investigation, my browser cached my old style sheet that I had recently updated. Clearing the cache and refreshing showed my new styling, after around 20 minutes of frustration :D
This problem occurs due to browser cache. For chrome while testing open the developer mode by pressing the F12 key and set cache disabled in the network tab as shown in Image below. It will ensure that you will always get updated version of the page files.
Check to make sure that the files are where you think they are. I would imagine that CodeIgniter is rewriting the request to be inside your application folder and thus bypassing your specific folder.