PUBLIC MARKS with tag tomcat

Les deux projets Java open sources les plus populaires viennent de sortir de nouvelles versions stables.

Tomcat 6 (download, documentation) implements the "Servlet 2.5 and JSP 2.1 specifications

It was a completely new Tomcat-Apache plug-in that handles the communication between Tomcat and Apache.

UsingMod_jk1.2WithJBoss

Utilisez Apache Http et Apache Tomcat ...

Run Tomcat as unprivileged user on Debian 3.1 (sarge)

Lambda Probe - Open source Tomcat management and monitoring tool

If your enterprise Java development is light weight and strictly avoids EJBs, you would probably consider Apache Tomcat as your first choice application server. However not only has Tomcat become rather heavy over time but it also isn't the only option you have. The list of Java servers is quite long, but it normally comes down to Tomcat, Jetty and Resin.Apache Tomcat is easily the most popular of the three and the "Powered By Tomcat" section lists some of the more well known names running Tomcat.

Tutorials for Hibernate, EJB 2, EJB 3 Struts, JavaServerfaces (JSF) Tomcat, JBoss, Myeclipse, Eclipse and other

This morning, I did some comparisons between Jetty 5.1.5rc1, Tomcat 5.5.9 and Resin 3.0.14 (OS version).

JBoss Application Server is the #1 most widely used Java application server on the market. A J2EE certified platform for developing and deploying enterprise Java applications, Web applications, and Portals, JBoss Application Server provides the full range of J2EE 1.4 features as well as extended enterprise services including clustering, caching, and persistence.

Jboss persiste et signe dans sa stratégie de harcèlement des géants du Middleware. Hier, l'éditeur a dévoilé Jboss Messaging, son nouveau serveur de messages et Jboss Web son serveur Web dérivé d'Apache. Les deux logiciels seront des composants essentiels de son prochain serveur d'application attendu pour le second semestre.

What are the advantages and disadvantages of using Tomcat embedded inside of JBoss Application Server versus running Tomcat independently?

Lors de la mise en production d'une application Internet ou intranet, il est fréquent de vouloir protéger les transferts par une connexion sécurisée (HTTPS). Même si Tomcat le permet (il suffit d'activer une option dans le server.xml de Tomcat), utiliser Apache est un meilleur choix du fait de sa vitesse. De plus l'utilisation d'Apache permet de se débarrasser des :8080 et autres numéros de ports dans l'url, du fameux " /MonApp " à la fin de la dite url et enfin la possibilité il offre une intégration plus aisée dans un environnement avec charge répartie (Load Balancing).

The latest version of the Tomcat servlet container provides clustering and load balancing capabilities that are essential for deploying scalable and robust web applications. The first part of this article provides an overview of installation, configuration, usage, and extension of clustering and load balancing features. The second will introduce a sample web application to demonstrate the steps involved in configuring Tomcat server instances to enable clustering, and will study session persistence using in-memory replication in the cluster environment.

Si vous utilisez Windows NT/2000/XP, vous pouvez installer Tomcat comme service: Pour cela, saisissez la commande suivante dans une fenêtre DOS : "�TALINA_HOME%bintomcat.exe" -install Tomcat "%JAVA_HOME%jrebinhotspotjvm.dll" -Djava.class.path="�TALINA_HOME%binbootstrap.jar;%JAVA_HOME%libtools.jar" -Dcatalina.home="�TALINA_HOME%" -Xrs -start org.apache.catalina.startup.Bootstrap -params start -stop org.apache.catalina.startup.Bootstrap -params stop -out "�TALINA_HOME%"logsstderr.log

This page discusses cluster- and clustering-related questions. Please make sure to read the Clustering HowTo page in the main Tomcat documentation bundle as well.

General Informations and FAQ about JK. JK is a project covering web-servers to Tomcat connectors, whereas mod_jk is the Apache module developed in JK.JK is a project covering web-servers to Tomcat connectors, whereas mod_jk is the Apache module developed in JK.

We have measured performance information to distinguish the differences between the Windows and Linux platforms. Given comparable hardware we found the performance differences almost trivial.

This first part of this article measures performance information in order to distinguish the differences evident between the Windows® and Linux platforms. We find that given comparable hardware the performance differences introduced are almost trivial. When the server was pressed to capacity, our Windows installation was forced turn away some traffic with minimal alteration in serviced performance, whereas our Linux installation elected to service nearly all connections at the cost of introducing latency. However, prior to reaching capacity, our Linux server appeared on average to be capable of servicing connections at a slightly faster rate than our Windows server.

Running cluster of Tomcat servers behind the Web server can be demanding task if you wish to archive maximum performance and stability. This article describes best practices how to accomplish that.