Become a MacRumors Supporter for $25/year with no ads, private forums, and more!

Java 1.5 not working in OS X 10.8

xedod

macrumors newbie
Original poster
Jul 26, 2012
4
0
Hi there,

hopefully someone has some tips on solving this problem.
After updating to mountain lion I realised I had to get my java 1.5 working again, so I followed the steps (again) from http://www.s-seven.net/java_15_lion

I followed every step carefully but changed <key>JVMMaximumSystemVersion</key>
<string>10.7.*</string>
with 10.8.*

Now in my Java Preferences I see both J2SE 5.0 (system) entries (32-bit & 64-bit) and they are set as "on". In terminal java and javac are returning my 1.5.0_30 version.

All seems fine until I try to compile my project since I get this error:

[javac] Invalid memory access of location 0x30 eip=0x902d3280

This is the beginning of the log:
Process: javac [1252]
Path: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0_30/Home/bin/javac
Identifier: javac
Version: 12.9.0 (12.9.0)
Code Type: X86 (Native)
Parent Process: java [1249]
User ID: 502

Date/Time: 2012-07-26 22:41:03.559 -0300
OS Version: Mac OS X 10.8 (12A269)
Report Version: 10

Crashed Thread: 13

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000030

VM Regions Near 0x30:
--> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0_30/Home/bin/javac
__TEXT 0000000000001000-000000000000b000 [ 40K] r-x/rwx SM=COW /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0_30/Home/bin/javac

Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x91cbd7d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91cbccb0 mach_msg + 68
2 com.apple.CoreFoundation 0x97da2cc9 __CFRunLoopServiceMachPort + 185
3 com.apple.CoreFoundation 0x97da86af __CFRunLoopRun + 1247
4 com.apple.CoreFoundation 0x97da7d6a CFRunLoopRunSpecific + 378
5 com.apple.CoreFoundation 0x97da7bdb CFRunLoopRunInMode + 123
6 javac 0x00004fd4 0x1000 + 16340
7 javac 0x00001da6 0x1000 + 3494

Thread 1:
0 libsystem_kernel.dylib 0x91cbd7d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91cbccb0 mach_msg + 68
2 libclient.dylib 0x0039612a 0x300000 + 614698
3 libclient.dylib 0x00395cc9 0x300000 + 613577
4 libclient.dylib 0x003b747a 0x300000 + 750714
5 libclient.dylib 0x00504211 JNI_CreateJavaVM_Impl + 689
6 javac 0x00003f0f 0x1000 + 12047
7 javac 0x00004adb 0x1000 + 15067
8 libsystem_c.dylib 0x902e7557 _pthread_start + 344
9 libsystem_c.dylib 0x902d1cee thread_start + 34

Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x91cc09ae kevent + 10
1 libdispatch.dylib 0x99ce4cc5 _dispatch_mgr_invoke + 993
2 libdispatch.dylib 0x99ce47fd _dispatch_mgr_thread + 53

Thread 3:
0 libsystem_kernel.dylib 0x91cbd7d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91cbccb0 mach_msg + 68
2 libsystem_kernel.dylib 0x91cbd644 mach_msg_server + 620
3 libclient.dylib 0x0030dc35 0x300000 + 56373
4 libclient.dylib 0x0030da65 0x300000 + 55909
5 libclient.dylib 0x005deee1 JVM_RaiseSignal + 481121
6 libsystem_c.dylib 0x902eb014 _pthread_body + 72

Thread 4:
0 libsystem_kernel.dylib 0x91cbd7d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91cbccb0 mach_msg + 68
2 libclient.dylib 0x00396073 0x300000 + 614515
3 libclient.dylib 0x00395e0c 0x300000 + 613900
4 libclient.dylib 0x003965fd 0x300000 + 615933
5 libclient.dylib 0x00395f37 0x300000 + 614199
6 libclient.dylib 0x005deee1 JVM_RaiseSignal + 481121
7 libsystem_c.dylib 0x902eb014 _pthread_body + 72

Thread 5:
0 libsystem_kernel.dylib 0x91cbd7d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91cbccb0 mach_msg + 68
2 libclient.dylib 0x0039612a 0x300000 + 614698
3 libclient.dylib 0x003a548a 0x300000 + 677002
4 libclient.dylib 0x003a4ab5 0x300000 + 674485
5 libclient.dylib 0x0054dd01 JVM_MonitorWait + 481
6 ??? 0x04ae89b1 0 + 78547377
7 ??? 0x04ae29d3 0 + 78522835
8 ??? 0x04ae29d3 0 + 78522835
9 ??? 0x04ae0227 0 + 78512679
10 libclient.dylib 0x0039781a 0x300000 + 620570
11 libclient.dylib 0x003a4943 0x300000 + 674115
12 libclient.dylib 0x003a47e5 0x300000 + 673765
13 libclient.dylib 0x003a46d6 0x300000 + 673494
14 libclient.dylib 0x003a45d8 0x300000 + 673240
15 libclient.dylib 0x005deee1 JVM_RaiseSignal + 481121
16 libsystem_c.dylib 0x902eb014 _pthread_body + 72

Thread 6:
0 libsystem_kernel.dylib 0x91cbd7d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91cbccb0 mach_msg + 68
2 libclient.dylib 0x0039612a 0x300000 + 614698
3 libclient.dylib 0x003a548a 0x300000 + 677002
4 libclient.dylib 0x003a4ab5 0x300000 + 674485
5 libclient.dylib 0x0054dd01 JVM_MonitorWait + 481
6 ??? 0x04ae89b1 0 + 78547377
7 ??? 0x04ae29d3 0 + 78522835
8 ??? 0x04ae2aaa 0 + 78523050
9 ??? 0x04ae2aaa 0 + 78523050
10 ??? 0x04ae0227 0 + 78512679
11 libclient.dylib 0x0039781a 0x300000 + 620570
12 libclient.dylib 0x003a4943 0x300000 + 674115
13 libclient.dylib 0x003a47e5 0x300000 + 673765
14 libclient.dylib 0x003a46d6 0x300000 + 673494
15 libclient.dylib 0x003a45d8 0x300000 + 673240
16 libclient.dylib 0x005deee1 JVM_RaiseSignal + 481121
17 libsystem_c.dylib 0x902eb014 _pthread_body + 72

Thread 7:
0 libsystem_kernel.dylib 0x91cc00ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x902ea04c _pthread_workq_return + 45
2 libsystem_c.dylib 0x902e9e19 _pthread_wqthread + 448
3 libsystem_c.dylib 0x902d1cca start_wqthread + 30

Thread 8:
0 libsystem_kernel.dylib 0x91cc00ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x902ea04c _pthread_workq_return + 45
2 libsystem_c.dylib 0x902e9e19 _pthread_wqthread + 448
3 libsystem_c.dylib 0x902d1cca start_wqthread + 30

Thread 9:
0 libsystem_kernel.dylib 0x91cbd80e semaphore_wait_trap + 10
1 libclient.dylib 0x003b44de 0x300000 + 738526
2 libclient.dylib 0x003b3d55 0x300000 + 736597
3 libclient.dylib 0x003a45d8 0x300000 + 673240
4 libclient.dylib 0x005deee1 JVM_RaiseSignal + 481121
5 libsystem_c.dylib 0x902eb014 _pthread_body + 72

Thread 10:
0 libsystem_kernel.dylib 0x91cbd7d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91cbccb0 mach_msg + 68
2 libclient.dylib 0x0039612a 0x300000 + 614698
3 libclient.dylib 0x00395cc9 0x300000 + 613577
4 libclient.dylib 0x003b51eb 0x300000 + 741867
5 libclient.dylib 0x003b4e88 0x300000 + 741000
6 libclient.dylib 0x003a45d8 0x300000 + 673240
7 libclient.dylib 0x005deee1 JVM_RaiseSignal + 481121
8 libsystem_c.dylib 0x902eb014 _pthread_body + 72

Thread 11:
0 libsystem_kernel.dylib 0x91cbd7d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91cbccb0 mach_msg + 68
2 libclient.dylib 0x0039612a 0x300000 + 614698
3 libclient.dylib 0x00395e0c 0x300000 + 613900
4 libclient.dylib 0x003b58b0 0x300000 + 743600
5 libclient.dylib 0x003a45d8 0x300000 + 673240
6 libclient.dylib 0x005deee1 JVM_RaiseSignal + 481121
7 libsystem_c.dylib 0x902eb014 _pthread_body + 72

Thread 12:
0 libsystem_kernel.dylib 0x91cbd7d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91cbccb0 mach_msg + 68
2 libclient.dylib 0x00396073 0x300000 + 614515
3 libclient.dylib 0x003b687f 0x300000 + 747647
4 libclient.dylib 0x003b632a 0x300000 + 746282
5 libclient.dylib 0x005deee1 JVM_RaiseSignal + 481121
6 libsystem_c.dylib 0x902eb014 _pthread_body + 72

Thread 13 Crashed:
0 libsystem_c.dylib 0x902d3280 memset_pattern + 192
1 ??? 0x03961470 0 + 60167280
2 libzip.jnilib 0x000eead0 ZIP_GetEntry + 142
3 libzip.jnilib 0x000eea1d ZIP_FindEntry + 33
4 libclient.dylib 0x003598a6 0x300000 + 366758
5 libclient.dylib 0x003594b2 0x300000 + 365746
6 libclient.dylib 0x00358ba4 0x300000 + 363428
7 libclient.dylib 0x00357864 0x300000 + 358500
8 libclient.dylib 0x003570e5 0x300000 + 356581
9 libclient.dylib 0x003994ff 0x300000 + 627967
10 libclient.dylib 0x0039d6ea 0x300000 + 644842
11 ??? 0x04aee9f3 0 + 78572019
12 ??? 0x04ae2aaa 0 + 78523050
13 ??? 0x04ae2aaa 0 + 78523050
14 ??? 0x04ae2aaa 0 + 78523050
15 ??? 0x04ae2aaa 0 + 78523050
16 ??? 0x04ae2aaa 0 + 78523050
17 ??? 0x04ae2aaa 0 + 78523050
18 ??? 0x04ae2aaa 0 + 78523050
19 ??? 0x04ae2aaa 0 + 78523050
20 ??? 0x04ae2aaa 0 + 78523050
21 ??? 0x04ae2aaa 0 + 78523050
22 ??? 0x04ae2aaa 0 + 78523050
23 ??? 0x04ae2aaa 0 + 78523050
24 ??? 0x04ae2aaa 0 + 78523050
25 ??? 0x04ae2aaa 0 + 78523050
26 ??? 0x04ae2aaa 0 + 78523050
27 ??? 0x04ae2aaa 0 + 78523050
28 ??? 0x04ae2aaa 0 + 78523050
29 ??? 0x04ae2aaa 0 + 78523050
30 ??? 0x04ae2aaa 0 + 78523050
31 ??? 0x04ae2aaa 0 + 78523050
32 ??? 0x04ae2aaa 0 + 78523050
33 ??? 0x04ae2aaa 0 + 78523050
34 ??? 0x04ae2aaa 0 + 78523050
35 ??? 0x04ae2aaa 0 + 78523050
36 ??? 0x04ae2a7f 0 + 78523007
37 ??? 0x04ae2a7f 0 + 78523007
38 ??? 0x04ae2a7f 0 + 78523007
39 ??? 0x04ae0227 0 + 78512679
40 libclient.dylib 0x0039781a 0x300000 + 620570
41 libclient.dylib 0x003a4943 0x300000 + 674115
42 libclient.dylib 0x003a47e5 0x300000 + 673765
43 libclient.dylib 0x003a46d6 0x300000 + 673494
44 libclient.dylib 0x003a45d8 0x300000 + 673240
45 libclient.dylib 0x005deee1 JVM_RaiseSignal + 481121
46 libsystem_c.dylib 0x902eb014 _pthread_body + 72

Thread 13 crashed with X86 Thread State (32-bit):
eax: 0xf0f0f0f0 ebx: 0x000f746a ecx: 0xfead34c0 edx: 0x00000030
edi: 0x0152cb70 esi: 0xf0f00000 ebp: 0xb2d90238 esp: 0xb2d901c4
ss: 0x00000023 efl: 0x00010287 eip: 0x902d3280 cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000023 gs: 0x0000000f
cr2: 0x00000030
Logical CPU: 0

Binary Images:
0x1000 - 0xaff0 javac (12.9.0 - 12.9.0) <8A7007AB-1856-5316-22AC-FD9931BDF791> /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javac
0x11000 - 0x15ffd com.apple.JavaVM (14.3.0 - 14.3.0) <1163556C-5C1D-3C5A-8767-682DAE7D3174> /System/Library/Frameworks/JavaVM.framework/Versions/A/JavaVM
0x1d000 - 0x21fff JavaLaunching (24) <A0441F95-2169-3682-B9DD-0A33F3B8BC98> /System/Library/PrivateFrameworks/JavaLaunching.framework/Versions/A/JavaLaunching


As far as I can see it has to do with the Java VM. Any idea how to resolve this issue?

Thanks!
 

mjparme

macrumors newbie
Jul 27, 2012
1
0
I am also looking for a solution for this. I followed the same instructions (I actually used the shell script he links to that automates it). Then I tried to start Weblogic 9.2 (which requires java 1.5) and I got the same invalid memory exception.

I actually thought it probable that Java 1.5 wouldn't work on Mountain Lion; however, it is more of a nice to have than necessity for me.
 
Comment

xedod

macrumors newbie
Original poster
Jul 26, 2012
4
0
Well for me it's a necesity, since I'm developing with java 1.5
Hopefully someone knows how to fix this, for now I reverted to OSX 10.7 using timemachine ;(
 
Comment

andrewbarton

macrumors newbie
Jul 30, 2012
4
0
I too have this issue. I have several legacy Java projects that I maintain that have dependencies on these old versions of the JVM. Ever since Apple dropped support for Java 1.5 and 1.4.2, I have been keeping backup copies of these versions. After every major OS release and Java update, I would simply untar my archives into /System/Library/Frameworks/JavaVM.framework/Versions/ and re-establish the appropriate sim links. Mountain Lion is the first time that this failed.

I am wondering if this new issue is related to changes to keep rouge processes from running. If so, there may be some way to bless these old JVMs.

Until this issue is resolved, I will have remain on Lion.
 
Comment

andrewbarton

macrumors newbie
Jul 30, 2012
4
0
Thinking about this further, I wonder if this is simply a matter of adjusting the gatekeeper setting on Mountain Lion to be the most permissive possible. As I have reverted back to Lion on my development machine, I'll have to test this on another sacrificial computer when I have a spare moment.
 
Comment

xedod

macrumors newbie
Original poster
Jul 26, 2012
4
0
Ok, great... but as far as I remember I turned off gatekeeper and still the error appeared. A second try wouldn't do no harm so keep us posted! :)

Although you should think that gatekeeper wouldn't even allow to run java or javac in terminal... if it's turned "on", there is probably some other setting somewhere... but even on the apple support communities nobody has a clue about this problem. Hopefully we'll get some answers soon...
 
Comment

andrewbarton

macrumors newbie
Jul 30, 2012
4
0
I had a chance to try turning off gatekeeper on my other machine. Like you, this did not help. At this point, the only other thing I can think to try is to install the developer tools just in case they include some dependencies that have been removed in mountain lion.
 
Comment

xedod

macrumors newbie
Original poster
Jul 26, 2012
4
0
Great Andrew! Going to check it out! Thanks!
 
Comment
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.