Downloading large files produces OutOfMemoryError

Hello,

for testing the bandwidth of my server I downloaded some
large files from it. I can reproduce that with a file size
of about 100 MB glassfish runs out of heap space. This
happens with glassfish on Linux with the out-of-the-box
configuration.

This is the stack trace in server.log:

[#|2007-11-05T21:14:32.546+0000|WARNING|sun-appserver9.1|jav
ax.enterprise.system.stream.err|_ThreadID=32;_ThreadName=htt
pSSLWorkerThread-8080-1;_RequestID=eb54a213-42ff-4431-8a46-1
95fa2aeb8e4;|java.lang.OutOfMemoryError: Java heap space
        at
java.nio.HeapByteBuffer.<init>(HeapByteBuffer.java:39)

        at
java.nio.ByteBuffer.allocate(ByteBuffer.java:312)
        at
com.sun.enterprise.web.connector.grizzly.SocketChannelOutput
Buffer.realWriteBytes(SocketChannelOutputBuffer.java:130)
        at
org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOu
tputBuffer.doWrite(InternalOutputBuffer.java:851)
        at
org.apache.coyote.http11.filters.IdentityOutputFilter.doWrit
e(IdentityOutputFilter.java:141)
        at
org.apache.coyote.http11.InternalOutputBuffer.doWrite(Intern
alOutputBuffer.java:626)
        at
org.apache.coyote.Response.doWrite(Response.java:599)
        at
org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(Output
Buffer.java:404)
        at
org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.j
ava:417)
        at
org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.
java:357)
        at
org.apache.coyote.tomcat5.OutputBuffer.close(OutputBuffer.ja
va:320)
        at
org.apache.coyote.tomcat5.CoyoteResponse.finishResponse(Coyo
teResponse.java:577)
        at
org.apache.coyote.tomcat5.CoyoteAdapter.afterService(CoyoteA
dapter.java:316)
        at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTas
k.postResponse(DefaultProcessorTask.java:582)
        at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTas
k.doProcess(DefaultProcessorTask.java:569)
        at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTas
k.process(DefaultProcessorTask.java:813)
        at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.exe
cuteProcessorTask(DefaultReadTask.java:339)
        at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doT
ask(DefaultReadTask.java:261)
        at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doT
ask(DefaultReadTask.java:212)
        at
com.sun.enterprise.web.portunif.PortUnificationPipeline$PUTa
sk.doTask(PortUnificationPipeline.java:361)
        at
com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBa
se.java:265)
        at
com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread
.run(SSLWorkerThread.java:106)
|#]

This is not a real problem for me currently as I don't have
such large files, but nevertheless I find it strange that
the file size is relevant.

Regards
Stephan
[Message sent by forum member 'smuehlst' (smuehlst)]

http://forums.java.net/jive/thread.jspa?messageID=244143


------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribeglassfish.dev.java.net
For additional commands, e-mail: users-helpglassfish.dev.java.net

This is fixed in the latest builds and will be in the
update.
[Message sent by forum member 'whartung' (whartung)]

http://forums.java.net/jive/thread.jspa?messageID=244154


------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribeglassfish.dev.java.net
For additional commands, e-mail: users-helpglassfish.dev.java.net