Re: WO5.1.3 and java1.4 on solaris
Re: WO5.1.3 and java1.4 on solaris
- Subject: Re: WO5.1.3 and java1.4 on solaris
- From: Michael Müller <email@hidden>
- Date: Fri, 11 Apr 2003 11:35:42 +0200
hi kaj,
> Does any of you out there use WO5.1.3 and java1.4 on solaris for
> deployment? Any problems?
we used to, but reverted to java1.3, because of some strange(?)
memory allocation/freeing problem that only showed on java1.4:
short version: allocated memory wasn't freed to the OS in the
expected manner, even though garbage collection ran and
our profiling tool(s) reported that the java heap size was
back to normal.
maybe we just weren't able to configure to the 1.4-HotSpot-VM
correctly, but god knows, we tried. ;-)
hints welcome...
--micha
--
-----------------------------------------------------
Michael M|ller (mailto:email@hidden)
Condat Informationssysteme AG
Alt-Moabit 91 D, 10559 Berlin, Germany
Fon: +49.30.3949-1227; Fax: +49.30.3949-1300
http://www.condat.de/
> -----Urspr|ngliche Nachricht-----
> Von: Kaj Hejer [mailto:email@hidden]
> Gesendet: Freitag, 11. April 2003 10:35
> An: email@hidden
> Betreff: WO5.1.3 and java1.4 on solaris
>
>
> Hi!
>
> We would like to run WO apps under java1.4 on solaris. Because of the
> "NullPointerException in _eoForGID" bug (see email bellow) we can't
> use WO5.2.1 in deployment so we use WO 5.1.3.
>
> Does any of you out there use WO5.1.3 and java1.4 on solaris for
> deployment? Any problems?
>
>
> -Kaj :)
>
>
>
>
>
> --- begin forwarded text
>
>
> Date: Thu, 10 Apr 2003 17:09:11 +0200
> To: email@hidden, email@hidden
> From: Kaj Hejer <email@hidden>
> Subject: Re: WO 5.2 - NullPointerException in _eoForGID
> (EOEditingContext)
> Cc:
> Bcc:
> X-Attachments:
>
> At 09:15 +0100 08-01-2003, Kaj Hejer wrote:
> >At 11:09 +0100 17-12-02, email@hidden wrote:
> >>Hello,
> >>
> >>I am also getting lots of NullPointerException in _eoForGID.
> >>
> >>Am I the only one?
>
>
>
> >java.lang.NullPointerException
> > at
> >com.webobjects.eocontrol.EOEditingContext._eoForGID(EOEditing
> Context.java:2545)
> > at
> >com.webobjects.eocontrol.EOEditingContext.editingContextDidFo
> rgetObjectWithGlobalID(EOEditingContext.java:3802)
> > at
> >com.webobjects.eocontrol.EOEditingContext.editingContextDidFo
> rgetObjectWithGlobalID(EOEditingContext.java:3821)
> > at
> >com.webobjects.eocontrol.EOEditingContext._processReferenceQu
> eue(EOEditingContext.java:4697)
> > at
> >com.webobjects.eocontrol.EOEditingContext.unlockObjectStore(E
> OEditingContext.java:4629)
> > at
>
>
>
> Hi!
>
> We now get this stacktrace on ec.saveChanges() on WO5.2.1 on solaris.
> This bug is listed as fixed in WO5.2.1 in
> http://docs.info.apple.com/article.html?artnum=75433
>
> ---
> NullPointerException in EOEditingContext._eoForGID()
>
> Apple Reference 3132579
>
> ISSUE:
>
> There were potential causes of null pointer exceptions in the
> EOEditingContext._eoforGID() method.
>
> RESOLUTION:
>
> This issue has been corrected.
> ---
>
> Has anyone else out there seen this issue in WO5.2.1?
>
>
> -Kaj :)
>
> --- end forwarded text
> _______________________________________________
> 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.
_______________________________________________
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.