I think it is valid but not certainly possible for the moment. These parameters are only get from jboss.xml.
It would need one MBean linked to one ejb. It is a similar problem that having control on the Cache for entity beans from external world.
I don't see how to do that now. If you have an idea on how to achieve one MBean per EJBean I would be please to help here...
At least in jboss 3 there is one mbean/ejb. I'm not sure if this was added to 2.4.4
The only way I can think of to make any sort of change to pools is to undeploy the EJB, in some way alter the jboss.xml pool sizes and then redeploy it. It means you dont have to stop the server, but you cant use 'your' system during this period. Cant believe they left this out of app servers, how can you load balance a server without causing huge disruption?
A MBean/ejb excellent!
Then alex, this is very doable to add these Container (or Ejb) specific parameter manageable from these MBean.
One MBean per ejb means per container and the jboss.xml parameters is push "in" the container at deploy time.
You can destroy the pool completely, increase its size, add one instance at one click, ... anything you want. Without having to re-deploy the EJB.
I have a too long todo list to promise anything else ;)
Of course a MBean/Ejb that is marc main job for webservices,etc. How could it be used for the pool is maybe another problem ... or exactly the same (that would be beautiful). I have to think and exercise jboss 3 a bit more...