Re: java heap trouble after 5.4.1 upgrade, opensnoop to the rescue
Re: java heap trouble after 5.4.1 upgrade, opensnoop to the rescue
- Subject: Re: java heap trouble after 5.4.1 upgrade, opensnoop to the rescue
- From: Archibal Singleton <email@hidden>
- Date: Fri, 22 Feb 2008 09:07:58 -0300
I was also using the symbolic links install for coexisting 5.3.x and
5.4.x installs.
But could never shake a feeling of unease with this setup: /System is
Apple's territory and one should avoid messing with stuff there at all
costs... (Besides I too have been bitten by problems similar to the
one you're experimenting with symlinks).
So a few weeks ago, when WO 5.4.1 came out I finally decided to try
again (could not make it work in previous attempts) and switch to
using the wo.wosystemroot (and friends) property in ~/Library/
wobuild.properties to designate the proper WebObjects System
Frameworks to use.
Thanks to Anjo recent changes this now works smoothly and is IMHO a
more elegant solution
*** Disclaimer: I'm still a WO newbie.
Now I simply leave the normal WO 5.4x install as it is. I installed
the 5.3.x WO System Frameworks somewhere in my ~/Library and change
wo.wosystemroot to point the the one I wish to use.
HTH
= tmk =
On 20 Feb 2008, at 07:34, Johan Henselmans wrote:
Just a reminder for some other mindless soul...
I am one of the many that have WebObjects53 and 54 installed side by
side on Leopard, with symbolic links to the respective libraries:
lrwxr-xr-x 1 root wheel 70 20 feb 11:11
JavaEOInterfaceSwing.framework -> /System/Library/Frameworks/
WebObjects54/JavaEOInterfaceSwing.framework
lrwxr-xr-x 1 root wheel 63 20 feb 11:11 JavaEOProject.framework
-> /System/Library/Frameworks/WebObjects54/JavaEOProject.framework
lrwxr-xr-x 1 root wheel 66 20 feb 11:11
JavaEORuleSystem.framework -> /System/Library/Frameworks/
WebObjects54/JavaEORuleSystem.framework
lrwxr-xr-x 1 root wheel 60 20 feb 11:11 JavaEOTool.framework -
> /System/Library/Frameworks/WebObjects54/JavaEOTool.framework
drwxr-xr-x 26 root wheel 884 30 okt 13:05 WebObjects53
drwxr-xr-x 26 root wheel 884 20 feb 03:23 WebObjects54
After I installed WebObjects 5.4.1, I reversed back to WebObjects
5.3 via a script along the lines of:
**********
for framework in `ls /System/Library/Frameworks/WebObjects53`; do
rm /System/Library/Frameworks/$framework; ln -sf /System/Library/
Frameworks/WebObjects53/$framework /System/Library/Frameworks/
$framework; done
for framework in `ls /Library/Frameworks/Wonder53`; do rm /Library/
Frameworks/$framework; ln -sf /Library/Frameworks/
Wonder53/$framework /Library/Frameworks/$framework; done
for jar in `ls /Library/WebObjects/libWonder53`; do rm /Library/
WebObjects/lib/$jar; ln -sf /Library/WebObjects/libWonder53/$jar /
Library/WebObjects/lib/$jar; done
for app in `ls /Library/WebObjects/JavaAppsWO53`; do rm /Library/
WebObjects/JavaApplications/$app; ln -sf /Library/WebObjects/
JavaAppsWO53/$app /Library/WebObjects/JavaApplications/$app; done
*************
But I got a message with which I had struggled before: I started an
application in Eclipse, and then I got the message: java heap space,
and the application would stop.
The previous time it had to do with a classlist and a shared archive
that was not properly updated, but that looked allright this time.
I reminded that Leopard has dtrace on board, and started opensnoop
before running the app again in Eclipse, to see if something was
wrong:
Then I found this:
**********
502 896 java 8 /System/Library/Frameworks/WebObjects54/
JavaWebObjects.framework/./JavaWebObjects.framework
502 896 java 8 /System/Library/Frameworks/WebObjects54/
JavaWebObjects.framework/./JavaWebObjects.framework/
JavaWebObjects.framework
502 896 java 8 /System/Library/Frameworks/WebObjects54/
JavaWebObjects.framework/./JavaWebObjects.framework/
JavaWebObjects.framework/JavaWebObjects.framework
502 896 java 8 /System/Library/Frameworks/WebObjects54/
JavaWebObjects.framework/./JavaWebObjects.framework/
JavaWebObjects.framework/JavaWebObjects.framework/
JavaWebObjects.framework
**********
etcetera, etcetera.
I looked in the framework, and then I discovered what had gone
wrong: the Webobjects update had overwritten the symbolic links, and
after applying the script, the symbolic links were not removed, but
placed inside the frameworks that were still there. That caused a
fatal loop, and that got Eclipse into a java heap space error.
After removing the symbolic links inside the Frameworks with
for i in /System/Library/Frameworks/WebObjects53/*; do rm $i/$i; done
for i in /System/Library/Frameworks/WebObjects54/*; do rm $i/$i; done
all was well again.
Regards,
Johan Henselmans
http://www.netsense.nl
Tel: +31-20-6267538
Fax: +31-20-6273852
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden