On my Windows 7 x64 machine, I'm having problems launching my remotely deployed Web Start app (the Web Start app launches correctly on another PC as expected). In IE or FF, I click on the web start launch link, the JNLP is downloaded, it seems to get executed and nothing happens. I see javaws.exe processes running. I don't see a java.exe running.
I don't know if it's related but I also can't get the java console to run. In the Control Panel Java applet settings, I have have enabled "Show console" and "place Java icon in the system tray". I don't see the Java icon in the system tray either.
I'm running Java 1.6.0_21 (32 bit). I'm able to run Netbeans so the it appears as if Java is installed correctly on my machine. Why isn't web start working?
A firewall on my corporate joined domain was the problem. It was preventing web start as well as other types of apps from working correctly or even launching. Opening ports resolved it.
Are you absolutely certain that your Windows browser is binding the JNLP suffix to the javaws executable?
If you download the file, and double click, does it open correctly? If not, then right click, and investigate what is presented under Open With...
I had the same symptoms when I switched JNLP specifiction to 6.0. So I simply solved it by going back to 1.5, which I think is default in NetBeans, at least up til 6.7.
<jnlp spec="6.0+"...
Related
We've got a JavaFX 2 application developed in NetBeans 8.0.2, being packaged for deployment with WiX 3.9.1208, but we are having a problem on a few seemingly random machines.
After installing, when attempting to run the application, a dialog box is shown with the name of the executable and "Unable to invoke method" in the title. After clicking OK, the same box is shown again but with "Unable to launch JVM" in the title.
We are bundling Java 8u45 32-bit with the MSI, and everything seems to work on most machines, but we have had the above issue a couple of times on users machines, across WinXP, Win7 32-bit and Win8.1 64-bit running on a Mac in Parallels. Doesn't seem to make a difference whether Java is already installed on the users machine or not, and we can't figure out what could we causing the problem.
We haven't customised the WiX deployment in any way, just used what was out the box to start with, and we have very little experience in deploying Java applications.
We've been unable to reproduce this issue on any of our setups. Thanks in advance for any ideas on what could be happening!
Regards,
Richard
We deploy our application as a JNLP launch file and/or as a webpage applet.
I have a customer that updated his MAC OSX system to the latest Java Version 1.8_40. After upgrading the JNLP launch stopped working. It seems to start Java (flashes blue java logo) then stops. No Exception is thrown. I suspect yet another OSX security hurdle.
We adjusted his OSX Security settings to trust our application.
We adjusted his Java security to trust our site.
We also adjusted the Safari preferences to allow the application to run unrestricted ("unsafe mode").
The application is signed with a code signing certificate.
The customer can use the Applet launch method using the safari Java plugin.
All other customers (OSX & Windows) are generally fine.
If this is a new MAC Java issue I'd like to get ahead of it.
Anyone else out there see this? Any clues about what is causing the issue?
Our guess is that the cause of this bug has been backported to 8u40. We find that the application cannot get focus once the new blue Java splash screen is shown. We can also reproduce this on all the demo webstart apps on Oracle's own site, so it isn't our code.
You can confirm this bug by running your webstart instance with -Xnosplash to skip that splash screen. Unfortunately you cannot add that parameter to the jnlp file.
We can only reproduce this problem on OSX 10.10 (Yosemite).
A workaround (if you can control the client Java settings) is to add "-Xdebug" in Java Control Panel -> Java -> View... -> Runtime Parameters.
Update: the bug has been fixed and backported to 1.8u40. Oracle have also silently updated their downloads to the new build (1.8u40b27) as can be seen here I don't know that people already running 1.8u40 will get an update automatically.
When i add '-Xdebug' in the Java Control Panel as a Runtime Parameter it works for me.
I created a program using javaexe, a wrapper for Java programs that allows them to be launched by an exe file. This program contains a service part, a taskbar part (they send messages one to another). The program purpose is to send SMS and the list of the SMS sent is available from the taskbar icon.
The program has been working since a few years on a Windows XP computer, but I would like to launch it from my Windows 8.1 laptop computer, and when I launch the EXE, the splash screen is displayed, the service is installed, but the icon in the taskbar does not appear, and the serviceInit method does not seem to be run.
Where does the problem come from? My computer uses Windows 8.1, with Avast! as antivirus and the Comodo firewall. I obviously tested my program having disabled these 2 security programs (Avast! and Comodo) but there is still the same problem.
I use also JavaExe for an interactive service and I tested it on Windows 8.1 Pro (32bits)
with JRE 1.7 and 1.8....and it works fine, manually and automatically (after reboot) : the service running and the taskbar running also and communicates.
My .exe isn't fixed to run always as admin. When I install the service, I right-click and run it "as admin".
But, if I fix the .exe to always run as admin, I just double-click on .exe to install the service, but the taskbar doesn't run automatically after reboot : Windows 8.1 block the applications that automatically run as admin when the user log on.
I tested also the examples of JavaExe (example8 and 23) and it also works.
Have you the same problem with JavaExe's examples ?
I am running the 64-bit install of IBM Rational Application Developer (RAD) 8.0.4 on Windows 7. I have WebSphere Application Server (WAS) v6.1 running within it. To be honest, I'm not completely sure if the WAS server is 32- or 64-bit. My problems are:
Except for a few useless lines of logging at WAS startup, I get no logging in the RAD console at all. Not even when there's an exception thrown-- no strack trace, nothing. I cannot find the SystemOut.log file in the place that the WebSphere Properties dialog claims that it is. However, there is one in C:\Users\myUser\AppData\Local\VirtualStore\Program Files\IBM\SDP\runtimes\base_v61\profiles\was61profile1\logs\server1\SystemOut.log, but I do not know how to configure RAD/Eclipse to see it.
I do see an Access is Denied message as the first line of what I can see in the Console. But RAD is not clear about what or whom is being denied access, and in all other ways the server works just fine, except...
I cannot seem to get the WAS instance to run in Debug mode. If I "Restart in Debug...", RAD complies, but the server in the Servers panel of Eclipse does not show "Degugging, Synchronized"-- it simply shows "Started, Synchronized"-- just like it would if started normally. The Debug panel in Eclipse shows the server there, and claims that the debugger is listening on Port 8001. But the application will not stop on any breakpoints.
My colleagues are running identical Windows 7 machines, but have the 32-bit RAD 8.0.4, and don't seem to have this problem. I'm not ready to concede and re-install RAD down to 32-bit, nor do I have the time. There's got to be some other solution.
Work with the admin console and turn on the debug flag.
Start the server from the command line (not from within RAD) and the server would start in the debug mode.
Now try and debug a remote application (like you would any remote application within Eclipse) to attach RAD to this application Server.
Try and see if it works this way.
I would also try and see if the server is running in a debug mode (by looking for a netstat on the port 7777 which is the default debugging port)
HTH
I was able to resolve the logging by giving the LOCAL_MACHINE/Users group more permission on the file-system tree where RAD is installed (C:\Program Files\IBM\SDP\). I have found that when I run RAD "as administrator" in Windows 7, the logging problem I had went away.
Perhaps I should have done more granular analysis to figure out precisely which directory at a lower level might've needed different/more permissions, rather than changing it for all of the RAD install tree; but this works for me at the moment.
UPDATE 11.22.2013
I think the ultimate culprit was Windows 7 UAC. Apparently, applications installed within the default "Program Files" or "Program Files (x86)" directories receive extra security constraints when UAC is fully enabled. Running the server in Debug and the Console logging seem to need permission to modify things that Windows 7 feels like shouldn't be modified without elevated privileges. By either NOT installing RAD in the default Program Files or Program Files (x86) directories, OR completely disabling UAC, the problem is resolved. Disabling UAC could be considered risky, so the solution for me was to reinstall RAD outside of the default Program Files locations.
When I run my java web application from eclipse using tomcat server, system gets restart. Its not even showing any exception or errors.
My system Configuration is,
window xp sp3 32-bit
JDK1.5.0
eclipse helios
tomcat server 6.0
Please help me to solve this problem.
The problem may be either with your eclipse version or with the server or any code fragment which you are using. Try with fresh version of eclipse and server, if the problem still exists, check the system for any virus. If that also give negative check recently added code fragments..