I have problem with Mapman 3.0.0 in OSX. After the latest Java update Mapman crashes. All ideas are welcomed.
Johannes


Report (truncated):
Process:         MapMan [890]
Path:            /Applications/MapMan/MapMan.app/Contents/MacOS/MapMan
Identifier:      com.apple.javajdk15.MapMan
Version:         ??? (10.0)
Code Type:       X86 (Native)
Parent Process:  launchd [129]

Interval Since Last Report:          620610 sec
Crashes Since Last Report:           15
Per-App Interval Since Last Report:  22313 sec
Per-App Crashes Since Last Report:   8

Date/Time:       2009-06-24 13:06:59.322 +0200
OS Version:      Mac OS X 10.5.7 (9J61)
Report Version:  6
Anonymous UUID:  D382EF0E-6CEA-4D6A-9FC4-04F1D39C175D

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000f875897b
Crashed Thread:  0

Application Specific Information:

Java information:
Version: Java HotSpot(TM) Client VM (1.5.0_19-137 mixed mode, sharing)
Virtual Machine version: Java HotSpot(TM) Client VM (1.5.0_19-137) for macosx-x86, built on May 29 2009 13:21:56 by root with gcc 4.0.1 (Apple Inc. build 5465)
Exception type: Bus Error (0xa) at pc=0x96b7c688

Current thread (0x0100c9e0):  JavaThread "AWT-AppKit" daemon [_thread_in_native, id=-1608964320]
Stack: [0xbf800000,0xc0000000)
Java Threads: ( => current thread )
 0x01079530 JavaThread "Thread-39" daemon [_thread_blocked, id=11318784]
 0x01076160 JavaThread "Thread-38" [_thread_in_native, id=11334144]
 0x01001770 JavaThread "DestroyJavaVM" [_thread_blocked, id=-1333784576]
 0x010387b0 JavaThread "TimerQueue" daemon [_thread_blocked, id=11101184]
 0x01036690 JavaThread "Thread-4" [_thread_blocked, id=10497536]
 0x01016590 JavaThread "AWT-EventQueue-0" [_thread_blocked, id=10201088]
 0x0100ea30 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=9602560]

This is seems to be an internal java problem.
However you should use Java 1.6 as stated on the download page. Maybe switching to 1.6 fixes the problem as it is a different virtual machine.

I have the following to chose from in java prefs:
J2SE 5.0 32-bit
Java SE 6 64-bit
J2SE 5.0 64-bit
J2SE 1.4.2 32-bit
Which to chose
I have a macPro 09 (64-bit)

Although I now am running java 1.6
johanneshanson$ java -version
java version "1.6.0_13"
Java(TM) SE Runtime Environment (build 1.6.0_13-b03-211)
Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02-83, mixed mode)

Mapman uses java1.5 according to the error message. However I only have Java1.6 in 64-bits. Is that a problem?

Just Install a second time, you should be presented with a dialog to choose the java virtual machine.

The dialog does not show up as in windows. The step is indicated but the for some reason it directly jumps to the following step. clicking the previous button then jumps back two steps.

Johannes

I will have to look into this on MacOS.
One hint could be to look into the MapMan.lax file in the installation directory which has an entry like:

lax.nl.current.vm=/usr/lib/jvm/java-6-sun/jre/bin/java

Try changing that to meet your java virtual engine.

Axel

Sorry,
I can not find the file can yo tell me where it is supposed to be located?

I have to apologize, its different on MacOSX.
We have to wait until tomorrow to have a solution from our Mac-xpert.
The only chance I see from my point of view is installing a second time even if it hops over the dialog, to see if automatically picks up the new java version.
As a very last solution we can always start MapMan manually from a script, but then you have to get all the jar files on the path. I would rather wait for some info from our Mac man.

Axel

thanks,

Johannes
s.j.hanson@uu.nl

I have set up my system to match yours but i cannot reproduce the error. MapMan does not crash no matter if i run it using java 1.5.0_19 oder 1.6.0_13. Did MapMan crash on your system directly at the startup or when you were trying to use a certain functionality?

bests,
Marc

I have made it to crash during
Import of new data (both exl and txt)
downloading new mappings
downloading new pathways
'painting' old pathways with data imported before

I also tried to clean the system from all old mapman files but have so far been unsuccessfully. The uninstaller leaves files as the newly installed version still shows my old data-sets and mapping etc.

1.)
That was done on purpose to leave the configuration untouched.
It shouldn't pose a problem as you can use the File Menu Prefernces Dialog and choose reinstall. That will reinstall all the pathways, mappings and data files.
2.)
I have found dialogs which are only closeable using the return key, they do not react on the button. I will have a look into that to fix it.
3.)
Crash means the application just dies like you mentioned in your first post as a java crash?

I reinstalled using the preference dialog and still get the java crash

According to the report it is still java 1.5 used.

allthough I generally have java 1.6 running:
dhcp-50-127:~ johanneshanson$ java -versionjava version "1.6.0_13"
Java(TM) SE Runtime Environment (build 1.6.0_13-b03-211)
Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02-83, mixed mode)

Finally I started it from the command line (Marc confirmed that it did not crash than;-)):

go into /Applications/MapMan/lib and call the application directly:

That solved it for us. We have found that the problem lies in the installer which decides to use 1.5 even if it finds 1.6. I will have to look into the installer and check how we can circumvent that.

Thanks,
I do get this back when I past it into terminal (followed by return).
Do I have to edit the text you suggested?
JH


Exception in thread "main" java.lang.NoClassDefFoundError: de/rzpd/mapman/ImageAnnotator
Caused by: java.lang.ClassNotFoundException: de.rzpd.mapman.ImageAnnotator
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:319)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:330)
at java.lang.ClassLoader.loadClass(ClassLoader.java:254)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:402)

You need to be in the correct directory, I had a typo in the path, sorry. The files mentioned on the command line (the -cp jar files) should reside in that directory:

Now it works!!!

Thanks for all the help,

Johannes

Many thanks for your input, directing us to the problem.

Axel