EJB Bad Practices: Use of Sockets

The EJB specification sets clear rules to ensure components are portable and behave consistently across different application servers. One of these rules explicitly forbids EJB beans from acting as network servers—meaning they must not open sockets to listen for or accept incoming connections. This restriction preserves the server's ability to manage resources, control the bean's lifecycle, and maintain transactional integrity. Allowing an EJB to become a socket server conflicts with its primary role as a managed component serving EJB clients. It can destabilize the container, interfere with clustering and load balancing, and create unpredictable security and performance issues. Instead, socket-based server functionality should be implemented outside the EJB container, in a managed service or a dedicated layer, keeping the bean's design aligned with its intended client-serving architecture.