• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
_eoForGID exception (was: java 1.4 solaris memory issue)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

_eoForGID exception (was: java 1.4 solaris memory issue)


  • Subject: _eoForGID exception (was: java 1.4 solaris memory issue)
  • From: Kaj Hejer <email@hidden>
  • Date: Tue, 16 Sep 2003 22:30:40 +0200

At 14:54 -0700 11-04-2003, Cliff Tuel wrote:
> Earlier today there was a note about a memory bug associated with Java
 1.4 on Solaris.  Is the Java 1.4/Solaris memory allocation/freeing issue
 specific only to WebObject 5.1.x on Solaris with Java 1.4 or is it a
 more general Java 1.4 bug on Solaris?  Does WebObject 5.2.1 address the
 memory issue?

If you're referring to the post by Kaj Hejer <email@hidden>, he clarified for me off-list that he got the _eoForGID exception with 5.2.1 on Java 1.3.1, **not** 1.4.x. He was merely asking if upgrading to 1.4.x would help. Their temporary solution was to revert to WebObjects 5.1.3.



Hi!

It is me with the _eoForGID issue again :)

Anyone else of you ppl out there sometimes seeing this exception on WO5.2.1? Maybe we should create a group on yahoo to share our frustrations ;-)

We are randomly getting the _eoForGID NullPointerException in WO5.2.1 when calling saveChanges on the parent after calling save changes on its child editingContext. The parent editingContext is session.defaultEditingContext.

I have written a jwebunit testsuite (http://jwebunit.sourceforge.net/) to run some automated test on one of our applications.

When runnning this testsuite against a WO5.2.1 application using childEditingContext as described above we are randomly getting the stacktrace bellow.

This issue seems to just come when using a nested ec.

I find it strange that not more ppl actually are reporting this eoForGID issue on the WO mailinglists since we have see this issue in almost every application we have deployed on WO5.2.1 which are using nested editingContexts. I think I only have seen 5 or 6 ppl posting about this issue.

Ref. the following post about the _eoForGID issue to email@hidden a while ago:

At 12:45 -0800 31-01-2003, Ben Trumbull wrote:
At 0:04 -0700 1/31/03, Dave Rathnow wrote:
Has anyone seen a stack trace similar to the one at the bottom?

It's a known issue in 5.2, but oddly, only seems to effect a few people. --

Can it something with our setup or our way of doing things? We see this issue on both osx and solaris. We are using Oracle. Why only seems to effect a few people?


We don't see this issue with WO5.1.3.

Yes, we have filed a bugreport :) I think it was in january 2003.

A typical stacktrace for this exception looks like the one bellow:

error: 2003-09-16 16:32:06 Etc/GMT:unittest:Controller:SaveChanges:Exception: java.lang.NullPointerException
java.lang.NullPointerException
at com.webobjects.eocontrol.EOEditingContext._eoForGID(EOEditingContext.java:2543)
at com.webobjects.eocontrol.EOEditingContext.editingContextDidForgetObjectWithGlobalID(EOEditingContext.java:3804)
at com.webobjects.eocontrol.EOEditingContext.editingContextDidForgetObjectWithGlobalID(EOEditingContext.java:3823)
at com.webobjects.eocontrol.EOEditingContext._processReferenceQueue(EOEditingContext.java:4706)
at com.webobjects.eocontrol.EOEditingContext._sendOrEnqueueNotification(EOEditingContext.java:4662)
at com.webobjects.eocontrol.EOEditingContext._globalIDChanged(EOEditingContext.java:1930)
at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.webobjects.foundation.NSSelector._safeInvokeMethod(NSSelector.java:120)
at com.webobjects.foundation.NSNotificationCenter$_Entry.invokeMethod(NSNotificationCenter.java:598)
at com.webobjects.foundation.NSNotificationCenter.postNotification(NSNotificationCenter.java:542)
at com.webobjects.foundation.NSNotificationCenter.postNotification(NSNotificationCenter.java:572)
at com.webobjects.eoaccess.EODatabaseContext.commitChanges(EODatabaseContext.java:6516)
at com.webobjects.eocontrol.EOObjectStoreCoordinator.saveChangesInEditingContext(EOObjectStoreCoordinator.java:421)
at com.webobjects.eocontrol.EOEditingContext.saveChanges(EOEditingContext.java:3128)
at NettskjemaComponent.saveChanges(NettskjemaComponent.java:189)




-Kaj :)
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: _eoForGID exception (was: java 1.4 solaris memory issue)
      • From: Kaj Hejer <email@hidden>
  • Prev by Date: RE: WebObjects and iCal
  • Next by Date: Which datatype? NSMutableArray, Vector, Array ???
  • Previous by thread: Re: using EOAttribute-properties in WebObjectsBuilder
  • Next by thread: Re: _eoForGID exception (was: java 1.4 solaris memory issue)
  • Index(es):
    • Date
    • Thread