Please share with the community what you think needs improvement with JBoss Enterprise Application Platform.
What are its weaknesses? What would you like to see changed in a future version?
I'd like to see some sort of functional requirement that can convert technical requirements in the JBoss platform.
I might not be the best person to discuss what features are missing as I am only a developer. I rely on the connection point mechanics, thread pulling mechanics. That's as far as I go. In terms of more details about the solution, I'm not very experienced. I'm not sure if any features are really lacking. If you compare IBM and JBoss, in terms of administration, troubleshooting, and monitoring, there were more advanced tools in IBM than JBoss. They might be able to make some improvements there. IBM offered JAVA profiling, which is something I used often and I wish that JBoss had something similar. We are using an inactive/active configuration. We need this topology for our customer, and therefore we configured the queues to behave in an inactive/active configuration and occasionally we are still experiencing some problems in balancing the messages between the queues. I don't know if they improved on this in newer versions of the solution (as we aren't using the latest). Perhaps this is our mistake. We're not on the latest version, however, due to the fact that the customer doesn't want to migrate to the latest version.
This solution needs better management UI.
We all know it's really hard to get good pricing and cost information.
Please share what you can so you can help your peers.