Error whenever a java applet is loaded - java

For the past few months or so, I've been getting an error whenever I attempt to use a java applet.
I'm getting this error on every browser I use, and I get the error occasionally in linux, too.
The java applet loads for roughly 5 seconds or so, then it stops and I get two error messages, stating that an exception occurred (java.io.EOFException).
This seems to happen regardless of what website I'm using. Going to the website shows I'm running java 6 update 20, and I get no error. Googling the error turns up nothing useful - I'm not a java developer, so most of the results don't apply to me at all.
My question is this. What's causing this error, and what can I do to fix whatever issue is causing it?

Nevermind. I looked further, turns out I had to delete the trusted.certs file under ~/Application Data/Sun/Java/Deployment/Security (~/.java/deployment/security in linux). That solved the problem.

Related

Code is not compiling in Netbeans using JavaFx implementing Controllers passing parameters

I was working this afternoon in my project without problems. Before come home I did a commit to my svn to continues it in home, but now when I try to run it shows a code error that hadn't shown before. The Following code it's supposed to initiate new scene using controllers and passing parameters. Error:
Someone knows what is happening? If you say "The code is wrong" it's not possible cause I was using the exactily same code in my work.
Detail, in the afternoon i was using Mac OS and now I'm using Windows. And IDE is Netbeans in booth places
My problem was not about code, actually the code is right.
The problem ocurred because my Netbeans was pointing to a old version of JavaFX. The way to fix it was to uninstall everything about java from my computer and after reinstall with the newer versions of JDK, JavaFx and Netbeans.
Cast your loaders to their appropriate types. For the first cast it to the Login Controller and for the second cast it to the MainViewController.
NetBeans only see's an abstract Object being returned, even though what is actually being returned is a little more specific. I'm not sure why this happened when you moved from one platform to the next (I assume you have the same version and everything), but some compliers will catch this as an error and others will not. Technically there is no error, just questionable results.

t.replace is not a function in selenium RC

I am using selenium 2.25 with firefox 3.6 and I am facing issues when i run my scripts.
Below is the error in my console and system displaying alert message as "Type error $j undefined"
ERROR: Command execution failure. Please search the forum at http://clearspace.openqa.org for error details from the log window. The error message is: t.replace is not a function
May I know what is the problem here, the scripts which I used were running fine earlier, but from last week eclipse showing error as above when I run my scripts.
Selenium version:2.25
OS:Windows 7.0
Browser:Firefox
Browser version:3.6
t.replace is not a function is normally caused by trying to perform a replace on a null in JavaScript.
I suspect you are trying to interact with something on the page before all the JavaScript has finished loading and this is causing the error. This will be intermittant because sometimes the page will have fully loaded and the JavaScript on the page will have processed correctly. whilst at other times Selenium may get in there a bit too quickly.
Generally have your devs check their javaScript code, there is a path that results in a replace being performed on a null. They should have some code to protect against things like this, it's caused by bad quality code.
Basically you have found a bug.

Java/SWT: an error has occurred see log for more

We are seeing this very generic error pop up in some circumstances, but we can't seem to track down what is generating it and I'm hoping someone has some insight into where to begin. We have multiple client machines all running the same version of our software, build with SWT, and all hitting the same server, but not everyone gets this error. Nothing is showing up in our client or server logs and I have no idea what log file this error may be referring to, so it's not an error that we are catching anywhere and we have no details about this. Since it's a pop-up message that leads me to think it may be an SWT error. I've seen people mention this error when using Eclipse, but I haven't found where anyone mentioned it in an application they built.
I know this is vague, but I don't have much more to go on. Does anyone have an idea where to start looking for culprits?
Thanks
You're building an RCP application? In that case, this error is talking about the Eclipse platform log.
There should be a .metadata\.log file in your program's instance location. If you do not know your instance location, you can query it by calling:
Platform.getInstanceLocation();

Process Model Delta

I am using Eclipse IDE.
Sometimes, after I make some alterations to the code and try to run, I get "'Process Model Delta' has encountered a problem" error. If I try to run again, sometimes it runs (without giving any error again) or again gives the error and I have to restart Eclipse.
I am not pasting any piece of code here, because the code was perfectly fine in many situations when this error occurred.
Can anybody let me know the reason why this error occurs or what is the meaning of this error?
Thanks in advance!
I assume you're actually debug. It that's the case, the cause is in one of your breakpoints. See if it runs fine with breakpoints disabled. If that helps, try Debug view menu Java > Show System Threads.
Cheers,
Max

How to debug/log/trace an applet loading problem?

Recently two of our clients have reported problems with our applets. Looking at the java plugin console it is full of ClassNotFoundException so none of our code is executed.
I've been able to reproduce the stack trace using a virtual pc image with 0 free space on disk, but the problem goes away as I restore some disk space, and the users tell me that their disk is not full; they are able to create new files.
Our applet requires java 6, and the problem has appeared with updates 1, 10 and 14 of the jre. We have also tried different browsers (IE and Firefox), clearing the browser and java caches, ...
How can I debug or trace what is the jvm doing to load our applet?
I suppose that the problem lies on some security directive on windows so I'm using Sysinternal's Process Monitor to log the activity but I don't really know where to look at.
The Java cache is most likely messed up. Open Java in the Control Panel and get rid of all temporary files to see if it goes away.
Logging in the Java Console for loading applets can be enabled which helps quite alot (even if the plugin is extremely cryptic). See http://java.sun.com/javase/6/docs/technotes/guides/deployment/deployment-guide/tracing_logging.html
I've been looking at the plugin source from the JDK and I've found that there is additional debug info available in the logs setting the environment variable JPI_PLUGIN2_DEBUG.
Unfortunately I still only see ClassNotFound exceptions.
I've found a piece of the plugin code that swallows all exceptions, so maybe my users problem is there...
had similar problems a while ago. In our case, the problem seems to be how the applet tag is set up on the web page. If it is in a wrong order or contains the codebase attribute, it fails with 6u10+. This works for us:
<applet name="DMGANTT" archive="DMGantt.zip" code="dm.applet.DMGanttApplet"
width='100%' height='100%' mayscript="mayscript">
We had a similar problem with one of our clients. We discovered that it was a strange bug in some versions of Java related to proxy configuration on the client. See this article for the details
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6723715
Also, our applet failed with new versions for a different reason.
Now, in similar cases I ask them to check javatester.org, so that I can see if applets (in general) load OK in their browser. If that page loads OK, its a problem on our applet (or page). Else it's a problem in their configuration. I help them anyway but it's easier to debug.

Categories