The JBoss hang

[karlsruhe]

I let the JBoss Server to output one message 100000 times as following within a session bean:

for (int i=1; i<100000; i++)
{
System.out.println("This is the time:" + i);
}

But the JBoss Server hang at about 97786. Every time is different: 97794, 97760....

I use:

JBoss 3.0.2
Sun j2sdk1.4.1
Windows XP

Has anyone an idea?

[joelvogt]

how long is the test taking each time?

[karlsruhe]

I let the JBoss Server to output one message 97700 times, because ther JBoss Server will hang, if outputing one message 100000 times. It needs 14249 miliseconds. And the memory demand is doppelt(about 84MB) as usual(running JBoss server needs about 43MB). I think such simple "system.out.println" don't need so much memory. It is the JBoss Server memory weakness? Joelvogt, have you any idea?

[karlsruhe]

I let the JBoss Server to output one message 97700 times, because ther JBoss Server will hang, if outputing one message 100000 times. It needs 14249 miliseconds. And the memory demand is doppelt(about 84MB) as usual(running JBoss server needs about 43MB). I think such simple "system.out.println" don't need so much memory. It is the JBoss Server memory weakness? Joelvogt, have you any idea?

[karlsruhe]

&gt; how long is the test taking each time?
I let the JBoss Server to output one message 97700 times, because the JBoss Server will hang, if outputting one message 100000 times. It needs 14249 milliseconds. And the memory demand is double(about 84MB) as usual(running JBoss server needs about 43MB). I think such simple "System" don't need so much memory. It is the JBoss Server memory weakness? Joelvogt, have you any idea?

[karlsruhe]

I let the JBoss Server to output one message 97700 times, because the JBoss Server will hang, if outputting one message 100000 times. It needs 14249 milliseconds. And the memory demand is doppelt(about 84MB) as usual(running JBoss server needs about 43MB). I think such simple "system.out.println" don't need so much memory. It is the JBoss Server memory weakness? Joelvogt, have you any idea?

[joelvogt]

I doubt this is a memory problem as otherwise the forums would be flooded with such questions. Possibly your session bean is being timed out? Hop into standardjboss.xml and check the timeout settings. Increase them all and try again.

[bie-developer]

Printing out to the console window in windows is bad for some reason, it can hang up depending on the console settings. See if hitting enter a few times in the console window allows it to continue. Why writing out to the console suspends the JVM every once in a while is beyond me (doesnt happen in a REAL shell). I think it has something to do with the 'quick edit' mode of the CMD program. (peice of crap..)