As you have tuned the server and you're already using the "G1 (Garbage First) collector" which I would have recommended, please edit the [Wowza-Install]/conf/Tune.xml file to remove the comments "<!--" and "-->" from around the VMOptions/HeapDumpOnOutOfMemoryError which will create a heapdump when Wowza runs out of memory. The result should look like this.
You will need to save the Tune.xml file after editing and restart Wowza for the changes to take effect.
After you have done this, wait until Wowza runs out of memory and it will create the heapdump which you will need to upload to a sharing site or FTP or web server for download and analysis.
Create a ticket with Wowza support by emailing firstname.lastname@example.org
When creating a ticket please attach a ZIP file which contains the following directories and files:
Please make sure you provide logs which show Wowza server starting.
If you are not sure how to get this information please see the following tutorial.
How to create a compressed zip file in Windows, OS X, and Linux
As for the other message, please see it below followed by the cause.
WARN server comment LiveMediaStreamReceiver.doWatchdog: streamTimeout: Resetting connection
Cause: Wowza can't connect to a MediaCaster stream. It could be a problem with the network or a problem with the source. For example, the camera was reached, but rejected the connection. Wowza will continue trying to reconnect until the stream is available again.
You can use the How to troubleshoot error messages article for referencing common messages in the error log.