dynaTrace Client 5.0.0 javaws not working on OSX 10.8.2
Hi all,
We have just completed upgrade from 4.2 to 5.0. I am having one weird issue with launching dynaTrace client from web portal on Mac OSX. Version 4.2 worked great, but the new 5.0 launches the app, I see the DynaTrace 5.0 splash screen and then it immediately closes after launch.
I have java 1.7.0_10 installed. (I know that Java 7 runs because I see Java 7 splash screen)
I enabled logging and tracing, but I couldn't find any errors. Here is the log
I tried cleaning/re-installing from javaws -version
Please let me know if I can provide more details.
xxxx:client xxx$ cat Client.0.0.log +----------------------------------------------------------------------------- + dynaTrace Client Copyright (C) 2004-2012 Compuware Corporation +----------------------------------------------------------------------------- + Version 5.0.0.3772 built Fri Nov 23 14:36:50 PST 2012 + Platform: Mac OS X 10.8.2, x86_64 64bit + Running as Webstart Client from host server xxxx-1 2013-01-04 16:56:52 INFO [Discovery] Additional OSGi site plugin directory created successfully: /Users/xxxx/.dynaTrace/dynaTrace Webstart Client xxxx-1/dtplugins/plugins 2013-01-04 16:56:52 INFO [Discovery] Configuring additional bundle site /Users/xxxx/.dynaTrace/dynaTrace Webstart Client xxxx-1/dtplugins/ 2013-01-04 16:56:52 INFO [NexusServiceComponent] Master/Detail dashlet interaction service (Nexus) started 2013-01-04 16:56:53 INFO [ClientConfigManager] Configuration stored successfully 2013-01-04 16:56:53 INFO [SSLEnvironment] initializing SSL context [keystore=/Users/xxxx/.dynaTrace/dynaTrace Webstart Client xxxxx-1/conf/keystore.jks] 2013-01-04 16:56:53 INFO [Client] Client Configuration Summary: 2013-01-04 16:56:53 INFO [Client] Base directory: /Users/xxxx/.dynaTrace/dynaTrace Webstart Client xxxx-1 2013-01-04 16:56:53 INFO [Client] Config directory: /Users/xxxx/.dynaTrace/dynaTrace Webstart Client xxxx-1/conf 2013-01-04 16:56:53 INFO [Client] Cache directory: /Users/xxxx/.dynaTrace/dynaTrace Webstart Client xxxx-1/cache 2013-01-04 16:56:53 INFO [Client] Log directory: /Users/xxxx/.dynaTrace/dynaTrace Webstart Client xxxx-1/./log/client 2013-01-04 16:56:53 INFO [Client] memory: 512MB heap, 128MB perm 2013-01-04 16:56:53 INFO [NexusServiceComponent] Master/Detail dashlet interaction service (Nexus) stopped
Hi Sergey
Two things you can try:
a) instead of the webstart client give the full MacOS Client a try: dynaTrace 5.0 Client for Mac OS X
b) Did you also use Java 1.7 for your dT 4.2 client? If you used a different Java Version - could you revert back to that version and try again?
Andi
Hi Sergey!
Please can you check two more things:
c) are all Webstart plugins active at the dynaTrace Server? (see documentation: https://apmcommunity.compuware.com/community/display/DOCDT50/Webstart+Client#WebstartClient-Deployment)
d) do you have some log files in /Users/xxxx/.dynaTrace/dynaTrace Webstart Client xxxx-1/osgi?
Martin
Thanks for the hint! I did not know OSX client existed. You should add it to the regular downloads page: http://www.dynatrace.com/downloads/ . I installed it and it works great!
I do use Java 1.7 for dT 4.2 client. I can see Java 1.7 splash screen before DT client splash screen shows up, so I am sure the correct Java version is loaded.
I checked all plugins are enabled.
Here are the contents of osgi folder. I dont see any logs here:
16:56 . 16:56 .. 16:56 org.eclipse.core.runtime 16:56 org.eclipse.equinox.app 16:56 org.eclipse.equinox.launcher 16:56 org.eclipse.osgi 16:56 org.eclipse.update
"javaws -viewer" shows dynaTrace app installed.
Hi Sergey
Good suggestion to add the link to the download page - will forward that to our Product Management Team.
Engineering also came back to me and said that they could reproduce the problem you experience. Good to know though that the full client install works
Andi
I think the problem is caused by a bug in Oracle Java 7. SWT applications requires to have the VM argument "-XstartOnFirstThread" set. When a new Java Web Start application is launched, Oracle Java 7 does not pass the VM argument to newly spawned processes. I've reported a new bug, which needs to be reviewed by Oracles Bug Report Review Team.
For now there are two solutions for this problem:
- install dynaTrace 5 Client for Mac OS X (as already mentioned by Andi)
- Use Apples Java SE 6 instead - see http://support.apple.com/kb/HT5559
Martin
Community Member of the Month
September 2018
Announcing Dynatrace's Community Member of the Month for September 2018, Muthu P.! Click here to read more! Employee Member of the Month
September 2018
Announcing Dynatrace's Employee Member of the Month for September 2018, Kris Z.! Click here to read more!