AppMon WebStart client

Hi Dominik,

since the JVM of the machine in question is out of our control, I've tried to start the client using the command suggested in the post you pointed out:

javaws -wait -J-Dcom.dynatrace.client.jvmrestriction.ignore=true -J-Xmx2048m http://<server>:8020/webstart/Client/client.jnlp

This seems to work fine. Thanks for your help!

Jürg

Hi,

are there any news on this?
We'd be very grateful if there's some kind of workaround available in order to run the dT 5.6 webstart client in a Windows/Java 7/64bit environment.
Any help is highly appreciated!

Regards,
Jürg

This is Windows.  It's an unusual situation for us, a developer with a 64 bit workstation environment.  We just have to use the workstation client as the web start doesn't seem to work with 64 bit Java.  Just thought I'd throw it out there in case there was a solution I was not aware or, and so that others may be aware of it.

Hi again, Pete,
just stumbled across your post here and I know from your 5.0 to 5.6 upgrade that you use Linux for your Server / Collectors.

The stand-alone Client on Windows should just work fine with its private JRE 1.7, but on 64 bit Linux the Clients (Web start or stand-alone) are some sort of hack you may not want to get into. (On a 32 bit Linux VM (or a Mac) it would be just fine.)

So, what platform are you referring to?
Regards
G.

We've been working around the Java 1.7 problem with web start clients for a while now.  With our recent implementation of dt 5.6 we thought we had it solved, but apparently there are some issues with 64 vs. 32 bit JRE's.  Below are comments from our developer who ran into it.  Anyone else experiencing this and have anything to share regarding it?

"Eventually I was able to get the new client running. The problem I faced was I have the 64 bit version of 1.7 as well as the 32 bit as I'm running eclipse with the 64 bit version. The dynatrace client only works with the 32 bit client of java, but since I had the 64 installed it defaults to that so the client doesn't work. I tried adding the 32 bit runtime to the java config and opening the JNLP file with the 32 bit version but due to the fact that the name of the exe is the same as the 64 bit it still opens with the 64 bit.

The only way that I could get it to run was going to the command prompt and going to the 32 bit java bin folder and running the client from the command prompt.

Unless there is a way that I don't know about to force the file to be opened with the correct version of java this will just be a pain so I'll just download the desktop client and hope it doesn't have the same issue."

Thanks for the quick respose.  Any chance Dynatrace 5.5 will work?

Does the 5.6 client work with Java 1.7_51?  It sounds like things are still broken.  Our security deparatment will be pushing Java 1.7_51 very soon. I need to know if the webstart client works with this release.

Please advise.

Thanks,

Jim

I have upgraded the Java version to 1.7.0_51 and if I use Java Web start I still the error same error

<a href="http://tinypic.com?ref=20upevr" target="_blank"><img src="http://i39.tinypic.com/20upevr.png" border="0" alt="Image and video hosting by TinyPic"></a>

CacheEntry[http://dynatrace.demo.compuware.com:8020/]: updateAvailable=false,lastModified=Wed Dec 31 19:00:00 EST 1969,length=-1
CacheEntry[http://dynaTrace.demo.compuware.com:8020/images/dynatraceLogo.png]: updateAvailable=false,lastModified=Wed Dec 31 19:00:00 EST 1969,length=-1
Exception in thread "AWT-EventQueue-1" java.lang.NullPointerException
at com.sun.deploy.ui.DialogTemplate.imageAvailable(Unknown Source)
at com.sun.deploy.ui.DialogTemplate.finalImageAvailable(Unknown Source)
at com.sun.deploy.ui.ImageLoader$2.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$200(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Missing Application-Name manifest attribute for: http://dynaTrace.demo.compuware.com:8020/webstart/Client/common/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
Missing Permissions manifest attribute in main jar: http://dynaTrace.demo.compuware.com:8020/webstart/Client/common/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar

FYI, we also verified that the latest Java Update 1.7.0_51 behaves the same way as Java 1.7.0_45 and no new hurdles were put in by Oracle. After installing the FixPack in dynaTrace 5.5 or upgrading to dynaTrace 5.6, Webstart Client should work fine!

The JRE 1.6u45 on Windows XP is still reporting a missing signature in the jnlp file. Is there a possible solution to fix this problem?

Our customers, can not upgrade or downgrade their installed JRE.