This week's book giveaways are in the Refactoring and Agile forums. We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line! See this thread and this one for details.
I need some advice on whether J2EE is appropriate for an application that I will be writing. I am writing the middle tier which takes in multiple requests from client applications (as a web server does), and then relays those messages to a host system over TCP/IP. The host has a set of listening ports, but only allows one connection to each of its listening ports. So, my middle tier will basically be a message queue to manage the many client requests.
My initial thought was to create a stand alone multi-threaded system, but I wanted to know if perhaps J2EE provided infrastructure to handle this situation, so I don't have to write everything from scratch. It sounds like something like a JDBC connection pool model may be close to what I want.