> I think that web host provider would have to provide separate
> glassfish domain for every customer. As far as I know each
> domain lives in its own environment and if one crashes - it
> can damage only itself (question to Glassfish developers: is
> that true?).
>
> The provider could create each domain folder in customer
> private home folder, so customers could
> launch/stop/restart/reconfigure their own domains using some
> shell access (asadmin tool) or glassfish admin web-page or
> something special developed for that purpose. The real
> question is how many domains could be handled by one server
> and how many resources (memory/cpu) is required for every
> single domain excluding resources taken by deployed applications...
That's what I had assumed would have to happen, but I just didn't know
if domains could be restarted independently of each other, and if my app
causes the server/domain to die (which I've seen happen), would it take
out other domains with it? Ideally, they'd be well isolated from each
other, but I don't know how to go about testing that, so I was hoping
some of the GF devs would know for sure. Furthermore, it will be much
more convincing to my provider if the info came from someone who really
knows beyond someone like me who can only say "I think this is the way
it..." ;)
-----
Jason Lee, SCJP
Programmer/Analyst
http://www.iec-okc.com