Coming soon: Our first 10Gbit/s Port at BCIX .
Monthly Archive for May, 2007
Regarding the article on golem, Sun Studio 12, based on NetBeans 5.5.1, will be available in June 2007.
There’s a lot of documentation for glassfish V2 and the the Sun Java Enterprise System Application Server 9.2 distro on the web. Besides wikis and blogs, there’s the “official” documentation set for glassfish V2, which is the same as the documentation set for Sun Java Enterprise System Application Server 9.1.
Because there are differences between these two distributions, the documentation refers to them.
In the Installation Guide (which I checked first) for example, the different installation methods for these distributions are explained. For earlier Versions of the Sun Java Enterprise System Application, there’s another distribution with the Sun Java™ Enterprise System (Java ES) installer, which also refered in the “Uninstalling Application Server Software” chapter. So, maybe we’ll have three types of glassfish V2 distros and install methods in future?
After setting up glassfish V2 I was interested in tuning and what the Sun Java System Application Server 9.1 PerformanceTuning Guide recommends for production mode. Focusing on the administrative part, I was wondering if there are tips for modifing the default JVM and Solaris 10 settings for different type of Servers like the Sun T2000 Niagara server or Sun X4200 Galaxy AMD Opteron servers. Looking at the section “Tuning for Solaris”, gives me a couple of tuning parameters listed. Looking at them and comparing them to
the Solaris 10 Tunable Parameters Reference Manual shows up, that the suggested Tuning parameters are for Solaris 8 or 9 but not for Solaris 10. Disappointed looking around, I found interesting values to start with in the submitted SPEC jAppServer2004 Results for Sun Java Enterprise System Application Server 9.0 .
I raised issue #3082 for updating tuning parameters to Solaris 10.
UPDATE: Also see gfwiki.
Running a web server in front of a java application server makes sense in almost all production scenarios, where end users from the internet connect directly to your site. The web server offers you much more configuration, security and performance features than the integrated http connector of any java application server. Software developers sometimes argue, that it should work (and of course it does). But if you want to speed up your website and tune your weblayer with optimizing settings like cache-control headers, turn of Etags and so on, a java application server doesn’t allow you to modify this settings.
Therefore, web servers like apache httpd are running in front of the application server and you can configure almost everything you want with apache httpd and apache modules. The connections from apache to the java application server (cluster) are configured through additional apache modules. Commercial Vendors like BEA offers you apache modules for Weblogic to connect. For Tomcat we saw a lot of different modules over the last years. These were mod_jk, mod_webapp, mod_jk2 and the return of mod_jk. With apache 2.2, there’s a build in module, called mod_proxy_ajp. The connection from apache to tomcat with the mod_jk or the mod_proxy_ajp is done by the AJP protocol, which is a binary protocol and faster than http. Before apache 2.2 and its mod_proxy_ajp module, some people used mod_proxy as a revers proxy from apache to tomcat. This might be good for small web sites, and if you do not need to pass some additional informations to you app server.
Now to glassfish. Currently, glassfish V1 and V2 ships only with a http connector module. There’s no apache httpd mod_glassfish or something like that. You can connect with httpd’s mod_proxy_reverse.
But regarding some blog entries from Jean-Francois Arcand and Amy Roh, it’s possible to extend glassfish with the libs ( tomcat-ajp.jar modeler-1.1.jar commons-logging-1.0.4.jar) from tomcat and tweak some config files.
But stop. Are there different versions of these jars? Which jar version fits to which glassfish version?
Some people already blogged about their problems to extend glassfish withe the ajp protocol.
Why does the glassfish distribution currently do not bundle the ajp libs and missing configurations in the config files?
In my opinion, it is very very important for the future success of glassfish, to offer build in connectors to apache (with ajp), to Sun JES Web Server (an NSAPI Module?) and MS IIS . These connectors should be well documented and easy to configure for admins and developers.
Here my first experience installing glassfish V2 beta. I started installing glassfish V2 build 33 in a Solaris 10 11/06 local zone. The hardware I installed glassfish is a Sun X4200M2, 4Cores 2,4 Ghz each and 4GB RAM.
Here the steps to do:
Download Glassfish
> wget
http://java.net/download/javaee5/promoted/SunOS_X86/glassfish-installer-v2-b33.jar
Setup Glassfish
> java -Xmx256m -jar glassfish-installer-v2-b33.jar
> cd glassfish
> ant -f setup.xml
BUILD SUCCESSFUL
Total time: 31 seconds
Starting glassfish
>cd bin
>./asadmin start-domain domain1
Accessing Glassfish Webadmin
Firefox: http://localhost:4848/ user: admin password: adminadmin (both defaults…)
There’s a good article by Nelson Segura-Nunez which describes, how to install Jira, Atlassian’s cool Bug Tracking, Issue Tracking, & Project Management Software on Sun WebServer 7 . If you also want to install Confluence on Sun Web Server 7, it’s much more easy than Jira. Just deploy the WAR-File…
Seen at the Airport Zurich
There’s a new OpenSolaris project called Web Stack which is based on the Cool Stack project. Today, OpenSolaris and Solaris is bundeled with some web tier components like apache, mysql, postgresql, but in Solaris 10 with rather outdated versions. Things like php, rails are missing from Solaris 10. Sun also offers Sun CoolThreads Optimized Open Source Software Stack (Cool Stack), but currently, there is no information, wether Sun will release security patches for these packages. Because of this, I would not use coolstack in production.
It would be great to have an up-to-date version of apache, php, mysql and on pre-installed in /usr/sfw/ with each Solaris installation, as we know it from common Linux distros. This could be an important improvement for Solaris in the future.
I hope the web stack project helps to improve Solaris and makes it Web2.0 ready.
Regarding a presentation of RIPE, we will run out of AS Numbers sometime between late 2010 and early 2013. The allocation rate is currently about 10-12 ASN/day. Therefore, 32bit ASN (ASN32) will be introduced. The transition phase started on 1/1/2007. After 1/1/2009, RIPE will give you ASN32 by default, after 1/1/2010 the RIR will only give an ASN32. All ISP and Carriers should be aware, to have their BGP Routers up to date. Currently, Juniper and Redback announced official support for ASN32. Today, only 15 ASN32 are assigned from RIPE. The ASN32 looks like the following: AS3.2
