Since switching to Tomcat 8, I continually get messages like this in my catalina.out
org.apache.catalina.webresources.Cache.getResource Unable to add the resource at [/intranet/includes/MailFunctions.jsp] to the cache because there was insufficient free space available after evicting expired cache entries - consider increasing the maximum size of the cache
I've found in the docs to add entries like cachingAllowed="false" antiResourceLocking="false" antiJARLocking="true" cacheMaxSize="0" cacheTTL="1" to my META-INF/context.xml file which I've done, but this doesn't seem to eliminate the problem.
Does anyone know how to stop these messages?
Thanks
I had the same issue but found an answer in another post which worked for me
In your $CATALINA_BASE/conf/context.xml add the block below before
</Context>
<Resources cachingAllowed="true" cacheMaxSize="100000" />
This solved it for me.
“inside the tag ” in where, I think ：
Tomcat/bin/catalina.bat int this add set JAVA_OPTS=-Xms256m -Xmx512m -Djava.awt.headless=true [-XX:MaxPermSize=128M]
eclipse->windows->preferences..->tomcat->jvm..->jvm add -Xms256m -Xmx512m
eclipse->preference->Java->instal jres->edit add -Xms256M -Xmx640M -XX:PermSize=256m -XX:MaxPermSize=768m
For anyone else unable to find an answer to this problem, the answer seems
to be as simple as adding this to your $SERVER_HOME/conf/context.xml
inside the tag
Related
I work still view month on a project with RapidClipse 4.0
I deployed on the production server several versions of the project war files. Everything worked fine.
After the last deployment I got a blank screen after loading the application URL
For the server I use a docker container with following setting:
Apache Tomcat/8.5.43, JVM: 1.8.0_222-b10, 3.10.105, amd64
My first thought was: "ok you did something wrong in your code.. turn back and every thing is fine.... :-((
It wasn't !!
I used several versions which runs fine befor.
I stopped the application, redeployed it and deleted it.
Then I deployed an older version....and once again a version older..a.s.o
Non of the versions which worked fine befor did work again.
I got every time the same result: after loading the application a blank white screen.
So far so bad:
I tried to look into ../conf/server.xml if deployment parameter is set correctly:
<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true">
looked fine!
I enhanced the cache by:
$CATALINA_BASE/conf/context.xml added following code:
<Resources cachingAllowed="true" cacheMaxSize="100000" />
also without success.
I tried to look in catalina.out: There is still nothing helpfull:
14-Aug-2019 20:29:21.087 INFO [http-nio-8080-exec-6] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/usr/local/tomcat/webapps/RC_07.war]
14-Aug-2019 20:29:31.190 INFO [http-nio-8080-exec-6] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [/usr/local/tomcat/webapps/RC_07.war] has finished in [10,102] ms
after debug in browser I got following:
257ms Processing time was 134ms
257msReferenced paintables: 6
283msEstablishing push connection
300msCould not load theme from http://myIP:8888/RC_07/VAADIN/themes//styles.css?v=7.7.13
310msPush connection established using long-polling
I searched also in the history of the docker container an found that this problem (300ms....) still persists from beginning, over all versions I deployed before.
Out of this, I assume, that this could not be the reason, too.
Or am I wrong?
I searched around this VAADIN Problem and found a lot, but I was not able to solve it. The styles.css file are still in place on the server.
I am wondering on ..../VAADIN/themes//styles.css...
the double slash in error message.
But in my code I couldn't find similar.
Also the buildpath in eclipse includes the folder structure like expected.
Now I am at the end!
I am confused, how I should go ahead to figure out the reason for this behavior, or much better to fix it.
Any idea/ help would be welcome!!
Thank you in advance
rgds
OpaHeinz
After long research, togehter with RapidClipse support we found the solution.
I had two issues:
1) unknown how, we assume, that there was an error in the MainUI xml file.
After resetting with and high of view and layout, and turning back to setting before,
the page elements were visible again in design view.
2) there is a parameter for the theme under MainUI properties - misc -
This parameter was set, but without content. This results in a code line: this.setTheme("");
After resetting this, a deployment was possible like before.
Everything is fine now.
Thanks again to RapidClipse support.
I've performed an update from typo3 4.7.20 to 6.2.15. The process worked fine and there were no critical errors while running the install tool.
The frontend looks fine but the backend is broken:
I've removed all uncompatible extensions before I run the update. I've also checked all settings in the installationtool und deleted the temp/cache folder first.
I've got the feeling that the error is caused by the TemplaVoila! extension, I'm using v. 1.9.8. Firebug does not shows any error.
Does anyone had a similar problem and have already solved it?
Thank you very much!
I have come across this one multiple times. More often it is because there is a broken TBE_STYLES. I suggest you look around for $TBE_STYLES in your typo3conf folder and disable it for the time being. Most likely it will be in the extTables.php or some other file which is included dynamically.
seems BE is working, but you css does not got loaded.
check your 'web inspecter' to see if you get errors on loading CSS.
clear your cache (remove everything in typo3temp) and try again
Today I cloned the Dojo Boilerplate and I'm running build.sh for the first time.
Messages like "warn(216) dojo/has plugin resource could not be resolved during build-time" are showing up in the console, and I wonder how much these warnings matter. Should I try to resolve them?
There always will be a lot of this kinds of warnings in build report. I seldom find that this will cause issues in your final building.
Don't worry about warning, just go head. Unless you see some errors in the report, you need to fix the errors.
Here is standard response from dojo https://bugs.dojotoolkit.org/ticket/15903
You can use grep to filer out messages starting for ex. from warn or info
src/util/buildscripts/build.sh --profile devel.profile.js | grep -vE "^warn|^info"
I'm trying to run Selenium tests using Play's built-in testing framework (TestServer, FakeApp, running() method) and running it through SBT, but the logging level for HTMLUNIT seems to be set at debug; causing a very large stack of useless messages.
I've already tried this:
Setting com.gargoylesoftware.htmlunit=ERROR in application.conf
Setting <logger name="com.gargoylesoftware.htmlunit" level="ERROR"/> in application-logger.xml
Doing the same thing as above but in test/resources/logback-test.xml
None of these seem to work. Looking at the log messages, it seems that it does understand that there is a logback-test.xml yet it just ignores it when it comes to HTMLUNIT.
Thanks
Figured it out. My problem was a lack of understanding of how play loads up xml files for logback.
There are 3 files that configure logback in play: logback.xml, application-logger.xml and application.conf. My issue was that I was declaring the levels in logback.xml (which loads before application-logger) but those settings were being overloaded by application-logger.
Putting the log levels on application-logger fixed the issue.
i have a strange problem. I have an ICEFaces(1.8.2) + Facelets application im working on and every time i make a change to it and deploy i must restart Glassfish(2.1.1) else i get a "java.lang.ClassCastException" on my entities. The error message is :
java.lang.ClassCastException: za.co.africanpulse.rms.frontend.domain.Menuheader cannot be cast to za.co.africanpulse.rms.frontend.domain.Menuheader
If i restart Glassfish as said above all is ok... but this is getting kinda irratating. I dont quite know what exactly you would like me to post so that my problem is easier identified / understood. Anyways any help will be most appreciated.
Many many thanks
You should probably open an issue with the GlassFish project: https://glassfish.dev.java.net/servlets/ProjectIssues.
StackOverflow isn't really designed to be a bug reporting/analysis tool.
That said... someone might have run into this and you could 'Get Lucky'...
Edit 1:
For example, this query: http://www.google.com/search?q=glassfish+icefaces+facelet+classcastexception
Netted this hit: http://seamframework.org/Community/HelpOnSeam220ICEfaces181AndGlassfish21
which looks like it may be useful.
When the web.xml servlet version is below 2.5 and jsf is still at 1.1 specified in the faces-config.xml then strange persistence related issues will arise. In my case entities could not be cast to themselves..???
After changing servlet version and jsf version i could successfully inject EntityManagers into my DAOs...