Hi all,
Here is a workaround for the problems I was having with Eclipse and
Leopard late last year. It appears to stem from 64 bit Java being
loaded instead of 32 bit and the Java Preferences application doesn't
seem to have any effect.
I did a brand new install so I cannot vouch for this solution. I am
"happy" to see that it wasn't just me. I am not sure how or where to
report this issue. Any suggestions?
Thanks to John, for letting us know.
David
Begin forwarded message:
> From: John Corrigan <wolistsj..mail.com>
> Date: January 6, 2009 4:47:26 AM PST (CA)
> To: David Holt <programmingos..ac.com>
> Subject: Re: Problem with 10.5.5 / Eclipse has returned - a solution
>
> Hi David,
>
> Not at all, please forward to the WOLips list (you're not mad :).
>
>
> A note: if you select a projects' "Application" class and select
> "Run > Debug As > Java Application" (instead of WOApplication) the
> app starts OK (it doesn't work but the "java" binary launches
> normally). Using the WOApplication launcher (ie. WOLips) launches
> the "java" binary as 64-bit on my machine (without the fix). I
> wonder if there is something that could be done within WOLips for
> this? Maybe raise a bug?
>
> It seems others are having ``java as 64 instead of 32-bit'' issues
> too:
> http://discussions.apple.com/thread.jspa?messageID=8614407
>
> For info I tried the following without success:
> - rebooted
> - clean eclipse + wolips installed.
> - run fix permissions (in Disk Utility)
> - reinstalled 10.5.5 combo update (the currently installed OS
> version).
> - update the LaunchServices database:
> /System/Library/Frameworks/CoreServices.framework/Versions/A/
> Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -
> kill -r -domain local -domain system -domain user
>
> So for now I've got a "/System/Library/Frameworks/JavaVM.framework/
> Versions/1.5.0/Home/bin/java" binary stripped of the 64-bit
> interpreter. Just happy to avoid an OS re-install!
>
> Cheers,
> John
>
>
> On 06/01/2009, at 5:26 AM, David Holt wrote:
>
>> Hi John,
>>
>> Thanks so much for following up. Do you mind if I forward the
>> solution to the WOLips list to confirm that I am not totally
>> nuts? ;-)
>>
>> I'll give it a shot when I get to the home machine tonight.
>>
>> David
>>
>>
>> On 4-Jan-09, at 11:35 PM, John Corrigan wrote:
>>
>>> Hi David,
>>>
>>> Today I hit the exact same issue ("cannot connect to vm" in
>>> eclipse) that you posted to the objectstyle.org mailing list here
>>> and have a solution of sorts that you may find useful.
>>>
>>> http://wiki.objectstyle.org/confluence/display/WOL/mail/3768844
>>>
>>> I've spent half the day looking for a workaround as re-installing
>>> the OS is too far. I eventually stumbled on a thread that
>>> basically says the OS has got mixed up somehow and is loading
>>> java as a 64-bit app in some circumstances. The main workaround
>>> is to strip the 64 bit from the "java" binary.
>>>
>>> http://discussions.apple.com/thread.jspa?messageID=8469241
>>>
>>> I used these commands:
>>>
>>> $ cp -p /System/Library/Frameworks/JavaVM.framework/Versions/
>>> 1.5.0/Home/bin/java /tmp/java_original_binary
>>> $ lipo /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/
>>> Home/bin/java -remove x86_64 -output /tmp/java
>>> $ sudo cp /tmp/java /System/Library/Frameworks/JavaVM.framework/
>>> Versions/1.5.0/Home/bin/java
>>>
>>> It may be a good idea to backup /tmp/java_original_binary to a
>>> more permanent location. It seems drastic but need an immediate
>>> solution. Don't know what happened -- I haven't touched
>>> development since before xmas til today.
>>>
>>> Hope this helps.
>>>
>>> John
>>>
>>>
>>> ps I can't update the mailing archive as I wasn't subscribed. I
>>> got your email from the webobjects-dev mailing list.
>>
>
This archive was generated by hypermail 2.0.0 : Tue Jan 06 2009 - 16:00:08 EST