Several times now, for various clients, I've had a horriffic time with JBoss from performance and configuration points of view.

I've now been asked to choose a Java-based, or at least Java-oriented, Application Server solution, and I'm doing my homework and wonder what I'm missing.

I am aware of Glassfish, though I don't know much about it yet, and today someone mentioned Spring; what else is out there?

Requirements are modest - just:

acceptance of unsolicited connect requests from a network, and; authentication of inbound connect requests, and; thread-management of on-going Java calls over the connection, and; graceful disconnection / thread cleanup.

This is for a large Java API that's to be split into a client - application server architecture.

Comments on open licenses is appreciated.

link|improve this question
If you're just asking for a list, then hit Wikipedia. If you can better explain how JBoss isn't meeting your needs, you'll get much better answers on this site. – mfinni Feb 1 at 3:46
feedback

closed as not constructive by Zypher Feb 1 at 3:46

This question is not a good fit to our Q&A format. We expect answers to generally involve facts, references, or specific expertise; this question will likely solicit opinion, debate, arguments, polling, or extended discussion. See the FAQ for guidance on how to improve it.

Browse other questions tagged or ask your own question.