Running JNLP stucks on Verifying Application - java

We have a Java application, which is ran with JNLP file. It usually works fine, but we have one PC that is unable to run it, because during running JNLP progress bar stucks on Verifying Application step:
Verifying Application step
and it doesn't move forward.
We have already tried:
waiting for at least 15 minutes,
downloading JNLP again,
clearing java cache,
installing the lastest JRE,
Java console, but it is opened later, so it is not useful,
tried to enable logging and tracing in Java Control Panel, but logs didn't contain any errors or exceptions.
Is there any way to debug what is happening during JNLP verification? Are there any logs available?
EDIT: this is Windows machine with 1.8.0_291-b09 Java HotSpot(TM) 64-Bit Server VM installed.

We found it!
After turning on tracing and logging in Java Control Panel:
and running JNLP with verbose flag:
javaws -verbose file.jnlp
in
C:\User\user\AppData\LocalLow\Sun\Java\Deployment\log
we have found log with errors.
In this case it was:
security: Failing over to CRLs: java.net.SocketTimeoutException: Read timed out

Related

java-language-server vscode extension - Starting client failed

I'm trying to use the java-language-server vscode extension, but I am getting an error that the extension is not starting up:
[Error - 11:07:14 AM] Starting client failed
Error: spawn UNKNOWN
at ChildProcess.spawn (internal/child_process.js:403:11)
at Object.spawn (child_process.js:570:9)
at c:\Users\tdalt\.vscode-insiders\extensions\georgewfraser.vscode-javac-0.2.39\node_modules\vscode-languageclient\lib\main.js:357:40
Looks like that line is trying to run this script: dist\lang_server_windows.sh. When I manually run that script, I get this error:
/mnt/c/Users/tdalt/.vscode-insiders/extensions/georgewfraser.vscode-javac-0.2.39/dist/launch_windows.sh: 13: /mnt/c/Users/tdalt/.vscode-insiders/extensions/georgewfraser.vscode-javac-0.2.39/dist/windows/bin/java: not found
which makes me think that something needs to run before that script runs.
Haven't looked much more into it than that. I have heard good things about this extension, but just haven't been able to get it working. Has anyone run into this issue before or is able to help me resolve it?
My java -version results in
openjdk version "11.0.9.1" 2020-11-04 LTS
OpenJDK Runtime Environment Zulu11.43+55-CA (build 11.0.9.1+1-LTS)
OpenJDK 64-Bit Server VM Zulu11.43+55-CA (build 11.0.9.1+1-LTS, mixed mode)
Operating System: Windows 11 Home v22000.493
VS Code: VSCode-Insiders (Latest version)
As a side note, if anyone has a good vscode bazel setup for Java, I would love to hear any tips on setup.
I had the same problem. You're probably trying this as a Windows Standard User. This worked for me...Log out of your Standard User Windows session and log into Windows as an Admin user and then run 'VS Code' (make sure the Java extensions are present within this Admin instance of 'VS Code'). You should then be able to debug Java code avoiding the error (although the JDK will request access through Windows firewall if not already granted). Once granted, quit 'VS Code' and the Admin Windows session. Log back into Windows as Standard User, Right-click 'VS Code' and Run As Administrator and use your Admin account to run 'VS Code' It should function normally after that, just keep in mind that VS Code is running under your Windows Admin account.

64-bit RAD 8.0.4 console and debug mode problems while running WebSphere Application Server v6.1

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.

Java web start doesn't launch

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+"...

Installation of IBM RAD 7.5 fails with JVM crash

I am trying to install IBM RAD, while installation, I am getting this error -
JVM terminated exit code=8096
And the installation stops. Is there any way to rectify this problem? Why Does JVM terminates? I verified that this is the jre from IBM which is crashing.
one thing you could try is to delete the shared classes cache because this error may be caused by a corrupted cache, the commands to do that are:
java -Xshareclasses:listAllCaches // to see the caches you have
java -Xshareclasses:destroy,name=myCacheName // to destroy the cache
Or just
java -Xshareclasses:destroy // to destroy all caches...
more information here...
The solution of this problem was to DISABLE the Device3d driver. After disabling the "DirectDraw" and Direct3D accelerations, RAD installed fine.
Way to disable is - Open Display Properties -> Settings -> Advanced->Troubleshoot
And lower the Hardware Acceleration to "Disable all but basic accelerations".

Tomcat 6.0.18 service will not start on a windows server

I installed Tomcat 6.0.18 on a windows server 2003 box and it will not start as a service.
I'm running it with jdk 1.6.0_07.
It runs when I start it with tomcat6.exe.
I got a vague error in the System Event Log on Windows.
The Apache Tomcat 6 service terminated with service-specific error 0 (0x0).
I'll bite it :-)
Tomcat Service on windows is dependent on the MS C Runtime library msvcr71.dll. As long as it is in the path, the service will start just fine.
Just to prevent your other windows to be forced to use this version of the runtime library, you might want to copy the DLL to just the tomcat bin path instead of windows\system32.
From gobaco.wordpress.com
Tomcat 6 couldn’t find a file called msvcr71.dll.
I just copied it over from
c:\windows\microsoft.net\framework\v1.1.4322
to
c:\windows\system32
and was able to start tomcat.
I thought this was very strange, so I wanted to post it on SO in case anyone else runs into this problem. If someone wants to post the same answer I'll accept it.
i follow the above guide but still the same, error 0,
my process monitor log at http://www.sendspace.com/file/t0tahr
I solved the same problem enabling the default java virtual machine in the configuration app.
Assuming you have installed tomcat using:
service install tomcat-6.0.35
execute:
tomcat6w //ES/tomcat-6.0.35
a window pops up, select the java tab and click on "Use default" checkbox.
The service install script (I immagine) selected C:\Program Files(x86)\Java\jre\bin\client\jvm.dll instead.
Environment:
Windows Server standard SP2 64-bin
Java 1.6.0_23-b05 (Java hotspot 64-bit server vm 19.0-b09 mixed mode)
Apache tomcat 6.35 (you guessed this didn't you?)
I copied the msvcr71.dll from the java home directory to the bin directory of the apache-tomcat install, and the service started after that.
Even though it's an older post, I thought I'd share the knowledge about the very same issue I had, but the workaround was different.
The Apache Tomcat 7 service terminated with service-specific error 0 (0x0).
As there was no more information regarding the problem I went back to the Tomcat Control Panel and had a look at the Java path, which was pointed to an earlier installation of Java Virtual Machine:
C:\Program Files\Java\jre6\bin\client\jvm.dll, which no longer existed, so I had to change the JRE version to jre7.
Having done that, the service started up and all running now.
Hope it'll help some of you out there.

Categories

Resources