![]() When calling cf logs APP_NAME -recent, you see something like this: The easiest way to identify a container out of memory situation is via the Cloud Foundry command line tool. By default, the Java buildpack expects and reserves enough memory for 250 * 1M (default value for -Xss). Another situation we have observed is that a JVM was scheduling more threads than memory was reserved for via the -Xss flag. This can happen when the JVM was given memory flags that configure it to use more memory than is available in the container. Container Out Of MemoryĪs mentioned before, a container out of memory situation occurs when your JVM tries to use more memory than your container quota allows. Since troubleshooting for both situations is significantly different, it’s crucial to understand which out of memory error you are facing to apply the correct countermeasures. Secondly, the Java Virtual Machine can still run into the ordinary situation, where there’s just not enough memory available to hold the required data into one of its memory areas, the heap being one of them.Firstly, the aforementioned container out of memory error, which happens when the container consumes more memory than allowed by its quota.Generally, we distinguish between two different out of memory situations: ![]() In part 2 we will focus on different out of memory errors that may occur with Java apps in containerized environments and how to mitigate them. Maybe we can include more information (like the current video) in the progress update event or maybe we need to send a "nowPlaying" event every now and then.In part 1 of this series we talked about Java memory management and how it is different in containers. It looks to me - from the way the app displays it - that it is waiting for TubeCast to actively send some information. This is very interesting because TubeCast doesn't respond to "updatePlaylist" commands at all. To my surprise this fixed the issue entirely. The next thing I tried is adding a video to the queue. When trying to view the current video information (by pressing on the video in the queue) one is greeted with a perpetual loading screen.The buttons at the bottom yet again don't work. Opening the queue we can see that the app still remembers the playlist but it doesn't know which video (playlist index) is playing. ![]() Pressing the play button to the right however doesn't seem to trigger a command. Opening the cast menu shows "No info available" but the volume slider still works like it should further backing up the idea that the connection isn't somehow broken. Now let's look at what happens when you open the app again:
0 Comments
Leave a Reply. |