Hi Wolfram,
thanks a lot for your reply! (from your name I assume you are German, like me...?)
However, it is indeed not a good practice, to issue a new port for a any new virutal host, this matter was addressed very early to the GlassFish developer team, and seems not to have been considered even in the latest releases of V3-Prelude.
The VirtualHost Support of GlassFish is obviously an administrator's burden no one can take. This is to the fact, that GlassFish is full of bugs.
The V2.1 only appends the jsessionid to the url, if the particular app runs either in context root / or if the main applett carries the same name as the package itself (war-file-name).
If you have to deny cookies for security reasons you'll go precisely through a surprise.
As well it seems, that the GlassFish developer team turns a blind eye on the sparc platforms for some reason. It is usual, that you have a server running without a gui desktop in place. The -c option is completely missing to install the pack in console mode.
Following the advices of
http://weblogs.java.net/blog/jfarcand/archive/2008/08/fronting_glassf.html to get the mod_jk connector up and running screws not only your glassfish, it screws yourself as well as you can't face the reason why.
If you use the update tool in V3, install the recommended updates/add-ons and restart the GF, you'll end up in re-installing your GF. This is to being not able to start your domain anymore.
Nevertheless: GlassFish v3.0-SNAPSHOT (build b49) is open by default anonymously - no PW requiered.
If you set up the admin user / or assign a PW to the default anonymous user, you can not stop the domain from the command line.
But you can perform this task by simply issuing: pkill java (!!!!!!)
GlassFish v3.0-SNAPSHOT (build b49) does not write the docroot value to domain.xml, even if you define the parameter in that file, it won't be recogniced by the web frontend.
On this side we started with V2.1 -> V2.1 HDAB -> V3 GlassFish v3.0-SNAPSHOT (build b49).
From release to release the performance / throughput is reducing a lot. Everything gets much slower.
Finally, a well documentation for Virtual Host Environments without the need of:
- additional ports
- additional instances
- additional domains
would be a nice to have.
All these issues Macromedia could arrange years ago with Coldfusion MX Enterprise.
And speaking frankly to you: I am currently very pissed as we have a lot of development work to do for clients requiring GlassFish. But the documentation is poor, and even if you follow up with them, you fail. You have to fight with bugs and confusing release names.
The response time of that forum here is more than poor.
Btw: What is the difference between V3-Preview and V3-Prelude?
And if Java App-Server require multiple instances/domains/ports to provide virtual host facilities, than how would we end up?
Back to the roots of the internet? Every Domain gets it's own server system?
This precisely ends up in having more server machines running in Europe than citizens!
However, I'll take a look to Tomcat and JBoss if it much easier and more well documentaded than GlassFish.
Best Regards,
Dave
Managing Director
[DE]SYSTEMS ENGINEERING Ltd.
Sun Principal Partner
www.dese.co.uk
contact[\at/]dese.co.uk
[Message sent by forum member 'seagate' (seagate)]
http://forums.java.net/jive/thread.jspa?messageID=349187