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.
Related
Please help me I am stuck due to below weird behavior of Intellij 2021.2.4(Ultimate Edition)
I am getting error after opening project in Intellij as below :
"Accessing invalid virtual file: file://; original:12323; found:12333; File.exists()=true.
I restarted my machine on weekend and then opened the Intellij Idea today morning .
I have tried below solutions but in vain
1.Invalid Caches
2.Remove idea64.exe.vmoptions
Thanks in advance .
I had this same issue just now. For me, I was running our app via JavaScript Debug task and the app would immediately fail; I'd get the error message in a "red balloon" above my Debug tool window tab.
Following the advice of #Andrey I checked the logs. Sure enough, there was a hint:
com.intellij.openapi.vfs.InvalidVirtualFileAccessException: Accessing invalid virtual file: file:///Users/randy/projects/..../.../notifications; original:804838; found:805846; File.exists()=true
at com.intellij.openapi.vfs.newvfs.impl.VirtualDirectoryImpl.handleInvalidDirectory(VirtualDirectoryImpl.java:190)
at com.intellij.openapi.vfs.newvfs.impl.VirtualDirectoryImpl.doFindChild(VirtualDirectoryImpl.java:111)
at com.intellij.openapi.vfs.newvfs.impl.VirtualDirectoryImpl.findChild(VirtualDirectoryImpl.java:77)
at com.intellij.openapi.vfs.newvfs.impl.VirtualDirectoryImpl.findChild(VirtualDirectoryImpl.java:500)
at com.intellij.openapi.vfs.newvfs.impl.VirtualDirectoryImpl.findChild(VirtualDirectoryImpl.java:44)
at com.intellij.javascript.debugger.JavaScriptDebugProcess.isMeteorClientScript(JavaScriptDebugProcess.kt:587)
at com.intellij.javascript.debugger.JavaScriptDebugProcess.getLocationsForBreakpoint(JavaScriptDebugProcess.kt:538)
at com.intellij.javascript.debugger.JSLineBreakpointManagerBase.setBreakpoint(JSLineBreakpointManagerBase.kt:36)
at com.intellij.javascript.debugger.breakpoints.JSLineBreakpointHandler.registerBreakpoint(JSLineBreakpointHandler.kt:17)
at com.intellij.javascript.debugger.breakpoints.JSLineBreakpointHandler.registerBreakpoint(JSLineBreakpointHandler.kt:12)
IntelliJ was trying to register breakpoints when it crashed. From there, I simply opened the Breakpoints dialog and trashed everything since they were all recent and moot anyway.
After that, I just closed the debug browser window that was left from my last failed attempt, then reran the Debug config. Everything worked as expected.
Yesterday I've struggled the whole day with my webpack configuration.
I've got a apache serving my php pages, with a proxy setup in webpack-dev-server config.
The problem is that when I load the page, the bundle is found, but apparently is like its not running at all!
After a change in the configuration, it did work, and I tought that the problem was solved, but today, after changing a single line, the problem occurred again!
After going back to the working configuration, nothing changed.
What the....? Please if anybody can give me any kind of suggestion, I'll appreciate that.
The application is made with Vue js, and in the browser console there's no message at all.
Thank you.
OK,
I'm sorry for the mistake, but for an unknown reason, my configuration file did go back to a previous version and I noticed the fact just now.
After repeating the change did Yesterday, the problem disappeared. I lost half of my day figuring out the problem that blocked the script execution, so I share the part of the code I had to remove in order to get a working configuration.
I'd like to know if anybody knows, why this piece of code is preventing the scripts in the bundle from running.
optimization: {
runtimeChunk: 'single',
splitChunks : {
chunks: 'all'
}
},
Thank you all.
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
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 recently took on a project built on XUL (standalone, using xulrunner) - However I can't get it to properly run.
I'm getting this error when I attempt to start it using the command line (xulrunner.exe ../application.ini -jsconsole):
No chrome package registered for chrome://case_scenario_builder/content/case_scenario_builder.xul
The chrome.manifest file looks like this:
content case_scenario_builder file:chrome/case_scenario_builder/content/ contentaccessible=yes
content jslib jar:chrome/jslib.jar!/
skin case_scenario_builder skin file:chrome/case_scenario_builder/skin/
locale case_scenario_builder en-US chrome/case_scenario_builder/locale/en-US/
Any ideas on where I could start debugging?
I figured it out!
In case anyone else runs into this as well:
It was due to the caching system in place by default and the use of .jar containers instead of folders.
The XUL environment had cached both JS and XUL files - and even after disabling those, I had to extract everything that was in the .jar file to the content folder and update the chrome.manifest file.
Thanks for your suggestions on debugging! - they helped the process.
I guess your manifest just isn't getting loaded. To test that I'd introduce an intentional syntax error and check the error console. E.g. if you put
asdfasd
on its own line, you should get a Warning: Ignoring unrecognized chrome manifest directive 'asdfasd'. in the Error console.
(Note to other experts: initially I wanted to suggest dropping 'file:' prefix and avoiding underscores in the package name, but I tested it on a Firefox nightly, and it works fine.)
Your chrome package clearly didn't get registered. From what I can tell, the reason is the bogus file: prefix, you should drop it when specifying relative paths:
content case_scenario_builder chrome/case_scenario_builder/content/ contentaccessible=yes
Btw, I suspect that you copied contentaccessible=yes from somewhere - you should drop it as well unless you know what it does.