No it doesn’t have issues, it just works differently than BorderLayout. You really have to understand the default behavior of each layout and each component to get the most out of using them.
Two Component methods come into play when added to a Container - getPreferredSize() and getMinimumSize(). Some layout managers may or make not make use fo these. For example, a FlowLayout is gauranteed to respect both the preferred width and height, while a CardLayout will ignore both. In a BorderLayout, what is respected or ignored depends on the location - BorderLayout.NORTH & SOUTH respect the preferred height, but ignore the preferred width, BorderLayout.CENTER ignores both.
Knowing how a LayoutManager handles preferred size is not enough, however. You also need to know what the default preferred size of a particular component is, and what the LayoutManager will do when it ignores the preferred size. This is why your Canvas is giving you trouble.
A Canvas by default has a preferred width of 0 and a preferred height of 0. FlowLayout respects preferred width and height. Therefore, when the Canvas is added to the layout its size will be set by a FLowLayout to 0,0 - and will therefore not be visible. BorderLayout.CENTER ignores the preferred size completely, and the default behavior is to stretch the component in both dimensions to fill the remaining space in the Container. So if you have an empty Container with a BorderLayout manager, your Canvas will fill be sized to fill the container if you add it to the CENTER> Adding to NORTH or SOUTH respects the preffered height, but stretches the Component to fill the width of the Container, while adding to EAST or WEST repsects the preferred width, but stretches the Component to fill the height of the Container.
Obviously, GLCanvas did not override the Canvas getPreferredSize method. And IIRC GLCanvas is final, so you will need to know the properties of each layout manager in order to use it effectively.