ive just been researching, i think its a java internal problem which mina uses ?

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4879883

As of 1.4.2 there is a limit to the amount of direct memory which an
application can allocate.  The default value for this limit is 64MB.
You may change it via the VM flag -XX:MaxDirectMemorySize, which takes
a size parameter just like the other memory-sizing flags, e.g.,

    % java -XX:MaxDirectMemorySize=256M MyClass

Setting a fixed default limit was, in hindsight, a mistake.  The default
should instead be proportional to the amount of memory dedicated to the
Java heap.  The default will be changed so that it's roughly equal to the
heap's maximum size, i.e, the value of Runtime.getRuntime().maxMemory().

Very unsure if that still relates to 5 but ill give it a try.


Dan Rossi wrote:
Hi even my discovery of svn not updating the io directory because its not even in the same path didnt work, i get the same error on the windows server. Its clearly a problem with files larger than 47MB , 46MB is ok :)

Dan Rossi wrote:
ok i found the setting you were talking about and got this

   [java] [INFO] 61249 DefaultQuartzScheduler_Worker-4:( org.red5.server.stream.PlaylistSubscriberStream.info ) Scheduled stop in: -1597551538
     [java] [ERROR] 61676 pool-1-thread-5:( org.red5.server.messaging.InMemoryPullPullPipe.error ) exception when pulling message from provider
     [java] java.lang.OutOfMemoryError: Direct buffer memory
     [java]     at java.nio.Bits.reserveMemory(Bits.java:633)
     [java]     at java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:95)
     [java]     at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:288)
     [java]     at org.apache.mina.common.PooledByteBufferAllocator.allocate0(PooledByteBufferAllocator.java:184)
     [java]     at org.apache.mina.common.PooledByteBufferAllocator.allocate(PooledByteBufferAllocator.java:159)
     [java]     at org.apache.mina.common.ByteBuffer.allocate(ByteBuffer.java:235)
     [java]     at org.red5.io.flv.impl.FLVReader.<init>(FLVReader.java:114)
     [java]     at org.red5.io.flv.impl.FLV.getReader(FLV.java:171)



Mondain wrote:
Im not sure what heap errors youre talking about, did you try all three buffer types? I got all of them to work for my 97mb / 101,000b FLV file. Since you say youre having heap errors you'll probably want to try the "direct" option.

Paul

On 10/31/06, Dan Rossi <[EMAIL PROTECTED]> wrote:
Hi, unfortunately it didnt fix the heap errors, if you need a 50MB+ file let me know ill ftp it somewhere.  Unfortunately i cant just get a 0.5 tarball as i need some features available in trunc, and i need to work out which version works now.

_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org





--
The early bird may get the worm, but the second mouse gets the cheese.

_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org


_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org


_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org



_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org

Reply via email to