I am using Java Web Start Application with sun-glassfish 3.1 and Java7 and self signed certificate. I upgraded chrome browser to version 45 and started getting ERR_CERT_AUTHORITY_INVALID errors.
Before upgrade I had "Not Trusted...proceed?" click-through once and it was not asked later. Now I get ERR_CERT_AUTHORITY_INVALID error again and again. Strange thing is sometimes it is working and I don't get any.
I thought it might be related with Glassfish because it mostly occurs when load is high. I have seen some bug reports similar to my case but could not be sure if I'm having the same problem. I'm a novice at this area so please forgive any mistakes. Should I wait for a fix in chrome or is there anything I could do to understand and fix the error?
Related
I have a selenium java project but I have an unsual error after some weeks not working on the project.
After searching on internet, most people said it was related to the chrome driver version. This seems weid, because I use the "io.github.bonigarcia.wdm.WebDriverManager" package to handle chrome version (and as you can see, I used the 103 chrome driver version).
After downloading the next version, and use:
"System.setProperty("webdriver.chrome.driver", "C:\Users\path\webdriver\chromedriver-104.exe");" the browser even fail to open, and it print me this error message.
But it seems the version is still 103 for my "personnal" chrome browser. I tried to update it, but it remains 103..
I tried to download the 104, but it act "beta chrome"...
What am I supposed to? Is there anyone else having issue with chrome selenium lately? Is there a work around? Can someone explain why selenium even bother to know the version of my work chrome?
The bug is actually in version 103 of the Chrome browser, not chromedriver. See https://bugs.chromium.org/p/chromedriver/issues/detail?id=4121 .
I have been able to mostly work around this by adding Thread.Sleep()'s (in C#) ranging from a fraction of a second to a few seconds, before the Selenium calls which fail.
After updating Android Studio, I'm facing these errors:
Failed to find bytecode for javax/swing/JApplet
Does someone knows what the problem is?
Looks like it is a bug in 3.1. I think this issue is similar enough to be the same.
https://issuetracker.google.com/u/1/issues/72811718?pli=1
I wasted so much time trying to fix it.
I eventually completely uninstalled Studio 3.1 including User files. Then reinstalled 3.0
I am downloading a java web start app from the web, and using the jnlp file to run it in my MAC OS. But the application does not start and gives me the following error.
Now, I have read a lot about this error here and how to sign the application here and other places. Plus I have read about the security update which started this error here.
All these articles and answers give the impression that this error can only occur due to the application being from an unidentified developer.
I just wanted to confirm whether that is the case, or can there be some other reason behind this, like expired code signing cert, or a self signed cert?
If there can be multiple reasons for this error, how to find out which one it is?
Here is the problem. I have a Spring web application which I develop on two computers: one with Windows another in Linux, and I share the code via github.
So far I did not have any problems until recently. I can't run in on linux. I get 404 error. At the same time it's working perfectly fine on Windows. I even managed to run it on a completely different computer (fitted with Windows).
Both laptops were switched to Java 8 and that was my primary suspect but so far I couldn't find anything that would cause this issue..
I would appreciate if somebody pointed me the way to fix it.
I have a strange behavior with either Play 2.0 or 2.0.1 : the first or
first few requests are served quickly by the Play! server, but then
it's not responding anymore.
I reproduced the problem on several projects including the hello word sample application :
- lauching "play run"
- Go to http://localhost:9000 -> ok
- Hit refresh a few times : the requests are locked, the browser is
just loading.
I have the same behavior with Firefox and Chrome.
I guess it's a setup problem, and I may be missing something trivial,
but I can't see what.
I 'm using Mac OS X Lion and Java 7 update 4.
Thanks in advance,
Regards
It is known that Play reacts weirdly when using Jdk 7. Check the mailing list, several issues have been noticed.
Seems like the only viable solution IMO. (Using same setup as you otherwise and no problems at all)
Thank you.
It was indeed related to Java 7. I finally got it working, it took me a couple of hours to find out how.
It seems that having the JAVA_HOME variable defined to the Java 7 path is generating some conflict.
Commenting the export line in my .bashrc solved the problem :
PATH=$PATH:/Users/raphaellemaire/tools/play-2.0.1
#export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.7.0.jdk/Contents/Home
Upgrading to Play 2.0.2 appears to work, as mentioned in mkeoller's comment.