java.lang.OutOfMemoryError: Java heap space

[Abitur]

Hello,
I got this error message on working wowza server(it is working in our project and any errors are very sadly). Full log message:

2011-01-27  05:10:18 MSK comment server INFO 200 ...
2011-01-27  05:10:19 MSK comment server INFO 200 ...
2011-01-27  05:11:18 MSK comment server INFO 200 ...
2011-01-27  05:11:19 MSK comment server INFO 200 ...
2011-01-13  06:40:36 MSK
java.lang.OutOfMemoryError: Java heap space
        at java.nio.HeapByteBuffer.<init>(Unknown Source)
        at java.nio.ByteBuffer.allocate(Unknown Source)
        at org.apache.mina.common.SimpleByteBufferAllocator.allocate(Unknown Source)
        at org.apache.mina.common.ByteBuffer.allocate(Unknown Source)
        at org.apache.mina.transport.socket.nio.SocketIoProcessor.read(Unknown Source)
        at org.apache.mina.transport.socket.nio.SocketIoProcessor.process(Unknown Source)
        at org.apache.mina.transport.socket.nio.SocketIoProcessor.access$600(Unknown Source)
        at org.apache.mina.transport.socket.nio.SocketIoProcessor$Worker.run(Unknown Source)
        at org.apache.mina.util.NamePreservingRunnable.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
2011-01-27  05:12:17 MSK comment server INFO 200 ...
2011-01-27  05:12:18 MSK comment server INFO 200 ... 

It is a 32-bit system and I set Java max heap size to 1500M. After that I tunning all as described in General Tunning Instruction. And at error time there is no activity on wowza server, no application was started.
Here is a very strange thing - date and time of error is not correspond with date and time of other log. So I have two questions:
1. How I can to avoid such errors at all ?
2. What is the strange date\time in log file ?
Thanks for help in advance.

[charlie]

It almost seems like maybe your server is being hit with a very large TCP packet or set of packets. I might watch the incoming packets coming to Wowza using Wireshark.

Charlie

[Abitur]

Ok, thanks for your answer,
Could you explaine in more details: On which port we can get this incoming packets? Which TCP packet will be very large in this situation? How it will be better to modelling it? If we make a modelling of this situation what we should get as result, the same error ?

[charlie]

By default the server runs on TCP port 1935. You may have added other ports. Check [install-dir]/conf/VHost.xml. The ports are specified in the HostPort/Port entry. I really don't know which packets will be large. I am just assuming that an idle server doing nothing should never just run out of memory unless something is happening. All I can guess is that something is sending super large TCP packets.

Charlie

[Abitur]

Ok Charlie, thanks for your answer.
As I see it is a non standard situation and I hope that it will not be frequently happen. But every server error is very big problem and should be avoid any way.
So, I ask a one more couple of questions:
1. How we can monitor wowza, for example to know if some error occur, and if yes make restart server? As I know from wowza documentation there is a monitor mecanism(jconsole) which work on stable server, but there are no mecanism to monitor if server work normally or some error happen.
2. Can server continue working after some server error occue without restarting? My expirience show that after any server error wowza became absolutly unpredictable, and best way is make restart.

[charlie]

1. The best way to monitor is using JConsole. We do not have another method.
2. After an OutOfMemory error Wowza is unstable and must be restarted. It is best to stop and start the service.

Charlie

[Rizwana]

nice update ..................