On 08/01/2014, at 6:09 AM, Chuck Hill wrote:
> This looks suspicious, "unable to create new native thread”. Check the
> ulimit on those machines. Is something running the machine out of threads
> (Apache child processes gone insane)? Or does it just need a higher limit?
Thanks Chuck—I think
in the order of days after
launch) apparently because it's out of memory:
---
2014-01-03 22:08:56,759 WARN 26.47 MB/30.28 MB [WorkerThread11]
logging.ERXNSLogLog4jBridge (ERXNSLogLog4jBridge.java:44) -
: Exception occurred
while handling request:
com.webobjects.foun
order of days after
launch) apparently because it's out of memory:
---
2014-01-03 22:08:56,759 WARN 26.47 MB/30.28 MB [WorkerThread11]
logging.ERXNSLogLog4jBridge (ERXNSLogLog4jBridge.java:44) -
: Exception occurred
while handling request:
com.webobjects.foundation.NSForwar
This is the default limits on a CentOS 5 box. They are actually lowers than
yours. But they might be using a container like OpenVZ that have other limits.
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size
These are the limits, but I don't see where the problem is, can you
please have a look?
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i
Please send your replies to the mailing list instead of directly to me…….
> Thanks a lot, for the link. On the system itself I did a top and it looked as
> if 3GB free Memory where available,
> that should be enough. But this is not a "real" server but a server partition
> on a web server hoster
Le 2013-10-25 à 04:59, ute Hoffmann a écrit :
> Hi,
> I'm have a WebObjects Deployment scenario where I cannot get the app to start.
>
> After a long trail of removing Issues I get this error message, when I try to
> start from shell.
>
> Starting the App via JavaMonitor: App dies without lo
Hi,
I'm have a WebObjects Deployment scenario where I cannot get the app
to start.
After a long trail of removing Issues I get this error message, when
I try to start from shell.
Starting the App via JavaMonitor: App dies without log, even with
288M allocated.
With the same allocated me
roblem sometimes, cleaning the project and restarting
>>>> Eclipse usually fix it.
>>>>
>>>>> Bringing an old project up to date, which has to deploy on 5.3. Reverted
>>>>> my local WO frameworks to 5.3.3, using the wonder jars required just fo
3.4.2 and WOLips 3.4.5830. Ant builds fail with out of memory
errors, during "installing into dist". Research so far turned
up thread about specifying ant args for memory, and I've
already got that, although I don't think eclip
gt;> Eclipse usually fix it.
>>>>
>>>>> Bringing an old project up to date, which has to deploy on 5.3. Reverted
>>>>> my local WO frameworks to 5.3.3, using the wonder jars required just for
>>>>> mail, using the 5.3 for that
il, using the 5.3 for that too. Eclipse 3.4.2
and WOLips 3.4.5830. Ant builds fail with out of memory errors,
during "installing into dist". Research so far turned up thread
about specifying ant args for memory, and I've already got that,
although I don't think eclipse
Ant builds fail with out of memory errors,
during "installing into dist". Research so far turned up thread
about specifying ant args for memory, and I've already got that,
although I don't think eclipse uses that from within the IDE. Any
ideas?
Bill
g the 5.3 for that too. Eclipse 3.4.2
and WOLips 3.4.5830. Ant builds fail with out of memory errors,
during "installing into dist". Research so far turned up thread
about specifying ant args for memory, and I've already got that,
although I don't think eclipse uses that
and WOLips 3.4.5830. Ant builds fail with out of memory errors,
during "installing into dist". Research so far turned up thread
about specifying ant args for memory, and I've already got that,
although I don't think eclipse uses that from within the IDE.
Bringing an old project up to date, which has to deploy on 5.3.
Reverted my local WO frameworks to 5.3.3, using the wonder jars
required just for mail, using the 5.3 for that too. Eclipse 3.4.2 and
WOLips 3.4.5830. Ant builds fail with out of memory errors, during
"installing into
>>> (on 3.5 cocoa 64)
>>>
>>> Yep, thanks... I noticed that too after sending out the email. So I have
>>> removed the duplicate settings. It seems to help some.
>>>
>>> Now, that you mentioned it, I just got a new 64-bit iMac, so I&
-bit iMac, so I'll give
>> Eclipse 3.5.x Cocoa 64bit a try. I had tried the 32-bit version and that
>> one was not running out of memory but it was getting painfully slow.
>> Hopefully the 64-bit version works better. :-/
>>
>> Thanks
>> Ricardo
>
-bit iMac, so I'll
give Eclipse 3.5.x Cocoa 64bit a try. I had tried the 32-bit
version and that one was not running out of memory but it was
getting painfully slow. Hopefully the 64-bit version works
better. :-/
Thanks
Ricardo
___
Do
il. So I have
removed the duplicate settings. It seems to help some.
Now, that you mentioned it, I just got a new 64-bit iMac, so I'll give Eclipse
3.5.x Cocoa 64bit a try. I had tried the 32-bit version and that one was not
running out of memory but it was getting painfully slow. H
It looks like you're setting -Xms and -Xmx twice. The latter setting it to
40/256. Try removing those. FWIW I run -Xms128m -Xmx512m without issue. (on 3.5
cocoa 64)
tb
On Nov 12, 2009, at 4:30 PM, Ricardo J. Parada wrote:
> $ cat ./Eclipse.app/Contents/MacOS/eclipse.ini
> --launcher.library
> .
On Nov 12, 2009, at 1:30 PM, Ricardo J. Parada wrote:
Hi All,
Eclipse seems to be running out of memory when I do certain things
such as rebuilding, updating all projects using subclipse, etc.
Does anybody see anything wrong or that I should change in my
current eclipse.ini file
Hi All,
Eclipse seems to be running out of memory when I do certain things such as
rebuilding, updating all projects using subclipse, etc. Does anybody see
anything wrong or that I should change in my current eclipse.ini file displayed
below? My computer has 4GB of ram. It amazes me that
le is used by Ant
runtime.
set ANT_OPTS="-Xms512m -Xmx512m" (Windows)
export ANT_OPTS="-Xms512m -Xmx512m" (ksh/bash)
setenv ANT_OPTS "-Xms512m -Xmx512m" (tcsh/csh)
Why would it compile within the IDE, but run out of memory in the
command line?
Because Ecli
export ANT_OPTS="-Xms512m -Xmx512m" (ksh/bash)
setenv ANT_OPTS "-Xms512m -Xmx512m" (tcsh/csh)
Why would it compile within the IDE, but run out of memory in the
command line?
Because Eclipse has more memory allocated to it. IIRC there was a bug
in some earlier versions that
?
Why would it compile within the IDE, but run out of memory in the
command line?
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
application runs out of memory and quits.
Does:
pageConfiguration = 'Foo' => useBatchingDisplayGroup = true [100]
help?
cug
--
http://www.event-s.net
Thanks!
I found that to get it working I also had to set
pageConfiguration = 'QueryFoo' => pageName = ERNEULis
*
Cheers, Anjo
Am 04.06.2008 um 08:53 schrieb Guido Neitzer:
On 03.06.2008, at 23:31, Johan Henselmans wrote:
I found that to get it working I also had to set
pageConfiguration = 'QueryFoo' => pageName = ERNEUListPage
That should be done by the rules in ERNeutralLook (which I don't
use, s
On 03.06.2008, at 23:31, Johan Henselmans wrote:
I found that to get it working I also had to set
pageConfiguration = 'QueryFoo' => pageName = ERNEUListPage
That should be done by the rules in ERNeutralLook (which I don't use,
so no idea right now).
which brings me to the next question: in
Op 3 jun 2008, om 17:37 heeft Guido Neitzer het volgende geschreven:
On 03.06.2008, at 07:32, Johan Henselmans wrote:
When I do a search on a record, it replies properly. But when I do
not fill in any query, the application runs out of memory and quits.
Does:
pageConfiguration =
pageConf="Foo" => fetchLimit = 5
Cheers, Anjo
Am 03.06.2008 um 16:32 schrieb Johan Henselmans:
I have a database with a table filled with about 1 records.
When I do a search on a record, it replies properly. But when I do
not fill in any query, the application runs out
On 03.06.2008, at 07:32, Johan Henselmans wrote:
When I do a search on a record, it replies properly. But when I do
not fill in any query, the application runs out of memory and quits.
Does:
pageConfiguration = 'Foo' => useBatchingDisplayGroup = true [100]
help?
cug
--
htt
I have a database with a table filled with about 1 records.
When I do a search on a record, it replies properly. But when I do not
fill in any query, the application runs out of memory and quits.
Does anybody know why that is? Do I have to reduce the set somehow?
jun 03 15:44:34
I've never used jconsole, but you should be able to use JProfiler to
see exactly what's being held onto.
ms
On May 7, 2008, at 3:40 PM, Andrew Lindesay wrote:
Hello Miguel & David;
Aren't you just pulling too many data at the same time from the DB?
If that were true then one might expect
Hello Miguel & David;
Aren't you just pulling too many data at the same time from the DB?
If that were true then one might expect the same failure to exhibit
itself after a change of database, but this is not the case.
Use a simple profiler, like JProfiler or jconsole to track the
memory
Thanks Miguel I had not used jconsole before nice, simple and
free.
I have some background processes that risk running out of memory such
as importing millions of rows of data from CSV files and creating
EO's. I know that EC recycling and many other strategies are
recomm
ap
space the JVM is configured to may lead to Out of memory problems.
Use a simple profiler, like JProfiler or jconsole to track the
memory usage. JProfiler is very powerful, but jconsole will be enough
for most of these problems. Check <http://terminalapp.net/profiling-webobjects
hi David,
Look, it seems to me that is not a problem of db, OutOfMemoryError is an
error that occurs when Java has no more Memory avviable. check this:
http://members.cisecurity.org/kb/article.php?id=023
2008/5/7 David Griffith <[EMAIL PROTECTED]>:
> Hi all,
>
> Does anyone know if there is a fi
Hi all,
Does anyone know if there is a fix for this, other than moving from
mySQL to another DB? I am experiencing the same problems.
Regards,
David.
On 21 Apr 2008, at 19:04, Simon McLean wrote:
Yes, I've seen it with MySQL. We still get it now, but very very
rarely.
Simon
On 21 Apr
Yes, I've seen it with MySQL. We still get it now, but very very rarely.
Simon
On 21 Apr 2008, at 02:35, Lachlan Deck wrote:
Hi there,
has anyone seen this before? Is it just coincidental? Usually when I
see OutOfMemoryErrors it's due to some infinite loop or some bug...
WO5.3.3, Mysql jc
Hi Andrew,
thanks for the info...
On 21/04/2008, at 2:54 PM, Andrew Lindesay wrote:
Hello Lachlan;
I have "reasonable suspicions" that the MySQL driver leaks -- the
most damning of which is a project wherein the instances went down
frequently owing to memory exhaustion, but immediately af
Hello Lachlan;
I have "reasonable suspicions" that the MySQL driver leaks -- the most
damning of which is a project wherein the instances went down
frequently owing to memory exhaustion, but immediately after a
migration to PostgreSQL in 2006, the memory exhaustion problem stopped
and ins
Hi there,
has anyone seen this before? Is it just coincidental? Usually when I
see OutOfMemoryErrors it's due to some infinite loop or some bug...
WO5.3.3, Mysql jconnector 5.0.6
com.webobjects.foundation.NSForwardException for
java.lang.OutOfMemoryError: Java heap space
at java.lang
Hi!
Well, I strongly support that change! I don't think the locking
semantics will be a problem (even if the context gets unlocked before
being GCed, who cares), but I only thought about this less than 10
seconds... :) It's not a really urgent change because, as you said,
it only causes
Just to clarify: if we use an ERXEC for a temporary job and no
longer need the EC afterwards we should explicitly dispose() it to
mark it for the GC ? Otherwise it will stick around forever ?
No, it's attached to a thread local which gets cleaned up at the end
of the RR loop (or when your thr
The problem was that I was creating another context inside the
cycle (in a called method) and copying some objects to it, trying
to save, catching OL exceptions, etc. It's that technique I
described on my blog: create very very localized EC, do stuff on
it, try to save, if it goes wrong, t
The problem was that I was creating another context inside the
cycle (in a called method) and copying some objects to it, trying to
save, catching OL exceptions, etc. It's that technique I described
on my blog: create very very localized EC, do stuff on it, try to
save, if it goes wrong, t
Hi!
On 2007/11/28, at 18:36, Chuck Hill wrote:
The ways of WO are many and mysterious. :-)
Indeed.
The problem was that I was creating another context inside the
cycle (in a called method) and copying some objects to it, trying to
save, catching OL exceptions, etc. It's that techniq
On Nov 28, 2007, at 5:38 AM, Miguel Arroz wrote:
Hi!
I'm having an Out of memory exception (and consequently
application death) that I can't figure out why it happens. I
suspect it's because I'm assuming something about the WO behaviour
that is not correct (as usua
I looked at the code and UTF-16 encoding for string file is broken and
has been broken for a while. UTF-8 works fine and I have done UTF-8
string encoded file for English, French, Arabic and Japanese. You have
to be careful as the system or the IDE sometimes messes up the files.
Encoding de
28.11.2007 um 14:38 schrieb Miguel Arroz:
Hi!
I'm having an Out of memory exception (and consequently
application death) that I can't figure out why it happens. I
suspect it's because I'm assuming something about the WO behaviour
that is not correct (as usual).
Th
Am 28.11.2007 um 14:38 schrieb Miguel Arroz:
Hi!
I'm having an Out of memory exception (and consequently
application death) that I can't figure out why it happens. I
suspect it's because I'm assuming something about the WO behaviour
that is not correct (as usual)
Hi!
I'm having an Out of memory exception (and consequently
application death) that I can't figure out why it happens. I suspect
it's because I'm assuming something about the WO behaviour that is
not correct (as usual).
The problem is this: I have an action th
Just FYI, UTF-16 used to work fine for me (as soon as I edited the
files in BBedit and nothing else) using the latest WO 5.3 and Apple
Tiger...
UTF-8 did not work properly for french accents, unbreakable spaces and
so on if I remember properly.
Regards and thanks for taking care about this
Am 27.11.2007 um 20:45 schrieb Chuck Hill:
IIRC, there is a problem with UTF-8 in that it does not always
detect UTF-8 properly and sometimes uses a western latin encoding
for UTF-8 files. That is why people started to use UTF-16. Anjo
should recall more.
It sucked, so I converted the
Hi!
True, I use UTF-16 (with no WO-related problems at all) because of
that. I would love to go back to UTF-8, as Subversion is not the best
friend of UTF-16...
Yours
Miguel Arroz
On 2007/11/27, at 19:45, Chuck Hill wrote:
IIRC, there is a problem with UTF-8 in that it does not alway
IIRC, there is a problem with UTF-8 in that it does not always detect
UTF-8 properly and sometimes uses a western latin encoding for UTF-8
files. That is why people started to use UTF-16. Anjo should recall
more.
Chuck
On Nov 27, 2007, at 11:42 AM, Daryl Lee wrote:
Looks like this has
Looks like this has been a bug in WO for quite a while and not a
regression in WO 5.4. Our Unicode/UTF-16 detection for .strings files
is faulty. Until we fix this, UTF-8 is working great. Thanks for
filing a bug Fabrice.
On Nov 22, 2007, at 1:18 AM, Fabrice Pipart wrote:
Hi dear list !
Hi dear list !
Like many I guess, I am adapting my project to Leopard and WO 5.4
I have many details to solve but one is more a problem than others.
My app is terribly slowed down under Leopard.
But now it becomes even more obvious why.
I very often get that kind of error after something like 2
This morning, I got a new error message when building Wonder:
[javadoc] javadoc: error - java.lang.OutOfMemoryError: Please increase
memory.
[javadoc] For example, on the Sun Classic or HotSpot VMs, add the option
-J-Xmx
[javadoc] such as -J-Xmx32m.
[javadoc] Generating /Users/les/WonderLa
Am 19.09.2007 um 05:19 schrieb Chuck Hill:
This, or a related issue can be triggered by firing a large (many
members) back pointing relationship. Sometimes for efficiency,
these are best managed manually and not modeled as a relationship.
You should always model every relationship. You ca
g. This is why I am running out of memory.
It turns out that a derived attribute that I was using to search
the LOB combined with other fields in the main artifact (using the
coalesce function) caused the LOB to be loaded into memory behind
the scenes with each record. Not good for perform
luded, not faulted as I
was expecting. This is why I am running out of memory.
It turns out that a derived attribute that I was using to search the
LOB combined with other fields in the main artifact (using the
coalesce function) caused the LOB to be loaded into memory behind the
scenes
Hi,
I have recently solved an out of memory problem in a list page by
using a batching display group that just fetches one page worth of
records at a time.
Now I find that creating an object from that page is once again
trying to fetch every record in the data table prior to allowing me
On Jun 28, 2007, at 3:14 AM, Ken Anderson wrote:
In case you're not understanding what Uli is telling you here, he's
recommending that you use a new editing context instead of your
session editing context for each invocation. Although your myLog
instance will eventually be garbage collect
On Jun 28, 2007, at 1:54 AM, Muckenhirn, Ralf wrote:
Hello,
I know there were some big discussions about that problem before.
But I have not found any solution for my problem until now.
I’ve created a small and very simple web-service using WebObjects
to reproduce my problem (see belo
Thanks for your help. It seems to help.
Ralf
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Ken Anderson
Gesendet: Donnerstag, 28. Juni 2007 12:14
An: Ulrich Köster
Cc: webobjects-dev Development
Betreff: Re: Out of memory
In case you're not understanding wha
In case you're not understanding what Uli is telling you here, he's
recommending that you use a new editing context instead of your
session editing context for each invocation. Although your myLog
instance will eventually be garbage collected, other resources that
EOF creates will live as
public class MyService implements IMyService {
public void storeToDB(String text1, String text2, String
text3, String text4, String text5) {
EOEditingContext ec = new EOEditingContext();
//or
// EOObjectStoreCoordinator parent = new EOObjectStoreCoordinator();
// EOEdit
Hello,
I know there were some big discussions about that problem before. But I
have not found any solution for my problem until now.
I've created a small and very simple web-service using WebObjects to
reproduce my problem (see below). I then calling this web-service from a
small application
created a custom image element starting from code someone
on this site donated. That fixed the memory leak for my application.
-tom
On Aug 30, 2006, at 1:00 PM, [EMAIL PROTECTED]
wrote:
Date: Wed, 30 Aug 2006 12:53:46 -0400
From: Marc Respass <[EMAIL PROTECTED]>
Subject: out of memo
On Aug 30, 2006, at 9:53 AM, Marc Respass wrote:
Hi All,
I'm getting out of memory exceptions in my app. I do need to go
through it and see if there is anything I can do to manage memory
better, but until then, I tried increasing the memory of the JVM. I
did it by adding
-Xm
All,
I'm getting out of memory exceptions in my app. I do need to go
through it and see if there is anything I can do to manage memory
better, but until then, I tried increasing the memory of the JVM. I
did it by adding
-Xmx256M -Xms128m to the Additional Arguments section of the
Hi All,
I'm getting out of memory exceptions in my app. I do need to go
through it and see if there is anything I can do to manage memory
better, but until then, I tried increasing the memory of the JVM. I
did it by adding
-Xmx256M -Xms128m to the Additional Arguments section of the
74 matches
Mail list logo
