Re: Re: tomcat5
Hola
el que comentes correcte, pero el fitxer mod_jk.conf no el tinc
no se si es correcta pero a la pàgina de tomcat diu que el
conector jk
també funciona per a apache2,
he instalat amb apt-get install libapache2_mod_jk, no se si
finalment hauré de compilar el mod_jk2 ? es recomenable?
adjunto arxius com demanes
server.xml
<Server port="8005" shutdown="SHUTDOWN" debug="0">
<Listener
className="org.apache.catalina.mbeans.ServerLifecycleListener"
debug="0"/>
<Listener
className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
debug="0"/>
<!-- Global JNDI resources -->
<GlobalNamingResources>
<!-- Test entry for demonstration purposes -->
<Environment name="simpleValue" type="java.lang.Integer"
value="30"/>
<!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users -->
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved">
</Resource>
<ResourceParams name="UserDatabase">
<parameter>
<name>factory</name>
<value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
</parameter>
<parameter>
<name>pathname</name>
<value>conf/tomcat-users.xml</value>
</parameter>
</ResourceParams>
</GlobalNamingResources>
<!-- A "Service" is a collection of one or more "Connectors"
that share
a single "Container" (and therefore the web
applications visible
within that Container). Normally, that Container is an
"Engine",
but this is not required.
Note: A "Service" is not itself a "Container", so you
may not
define subcomponents such as "Valves" or "Loggers" at
this level.
-->
<!-- Define the Tomcat Stand-Alone Service -->
<Service name="Tomcat-Standalone">
<!-- A "Connector" represents an endpoint by which
requests are received
and responses are returned. Each Connector passes
requests on to the
associated "Container" (normally an Engine) for
processing.
-->
<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port
8180 -->
<Connector
className="org.apache.coyote.tomcat5.CoyoteConnector"
port="8180" minProcessors="5" maxProcessors="75"
enableLookups="true" acceptCount="10" debug="0"
connectionTimeout="20000"
useURIValidationHack="false" />
<!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
<Connector
className="org.apache.coyote.tomcat5.CoyoteConnector"
port="8009" minProcessors="5" maxProcessors="75"
enableLookups="true" acceptCount="10" debug="0"
connectionTimeout="20000"
useURIValidationHack="false"
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
<!-- An Engine represents the entry point (within
Catalina) that processes
every request. The Engine implementation for Tomcat
stand alone
analyzes the HTTP headers included with the request,
and passes them
on to the appropriate Host (virtual host). -->
<!-- Define the top level container in our container
hierarchy
The name must be Catalina for correct function of the
admin webapp -->
<Engine name="Catalina" defaultHost="localhost" debug="0">
<!-- Global logger unless overridden at lower levels -->
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="catalina_" suffix=".log" timestamp="true"/>
<!-- Because this Realm is here, an instance will be
shared globally -->
<Realm
className="org.apache.catalina.realm.UserDatabaseRealm"
debug="0" resourceName="UserDatabase"/>
<!-- Define the default virtual host -->
<Host name="localhost" debug="0" appBase="webapps"
unpackWARs="true" autoDeploy="true">
<!-- Logger shared by all Contexts related to this
virtual host. -->
<Logger className="org.apache.catalina.logger.FileLogger"
directory="logs" prefix="localhost_" suffix=".log"
timestamp="true"/>
</Host>
</Engine>
</Service>
</Server>
workers.properties
worker.list=worker1
# Set properties for worker1 (ajp13)
worker.worker1.type=ajp13
worker.worker1.host=localhost
worker.worker1.port=8009
worker.worker1.lbfactor=50
worker.worker1.cachesize=10
worker.worker1.cache_timeout=600
worker.worker1.socket_keepalive=1
worker.worker1.socket_timeout=300
gracies
>asegurat que
> - a workers.properties tens definit el port 8009
> - a server.xml també tens el connector ajp al 8009
> - que tens definides les rutes a mod_jk.conf
>annexa els tres arxius i t'ho mire
>El 12/12/05, Victor <a
href="javascript:sendMsg('<llistes@ya.com>');"><llistes@ya.com></a>
va escriure:
>> En/na Sergi Baila ha escrit:
>> He repasat el tema. Ja he publicat l'article que comentava
abans al
>> meu blog www.sargue.net.
>>
>> El port 8009 es el port del AJP13, el connector per a
servir peticions
>> dinàmics a través d'un servidor web com Apache per exemple. En
>> l'article explico com fer la connexió.
>>
>> Per defecto el Tomcat escolta al port 8080 peticions HTTP
(per fer les
>> proves). Despres el pots tancar si només fas servir la
connexió via
>> Apache.
>>
>> Salut!
>>
>> On 12/11/05, matze <a
href="javascript:sendMsg('<matze@riseup.net>');"><matze@riseup.net></a>
wrote:
>>
>>
>> no en se molt, intenta conectar-te a localhost:8180 per a
veure si's
>> carrega una pagina del tomcat. tambe pots executar netstat
-tlnp, et
>> dona un llistat dels programes que escolten en ports tcp.
el port 8009
>> *crec* que serveix per a rebre peticions executar, no com a
interfaz
>> d'usuari, si es aixi no es extrany que no't diu res si no
li envias
>> cap peticio.
>>
>> matze
>>
>> El Sun, Dec 11, 2005 at 01:25:51PM +0100 Victor ha dit:
>>
>>
>>
>> Bones a tothom,
>>
>> He instalat el tomcat5 i l'arranco i no dona cap error al
fitxer de
>> server.xml que crec que es on es defineix el port
>> hi ha el 8009, pero al fer localhost:8009 hem diu que res
de res
>>
>> Al apache2 l'he instalat el mod_jk ja que el mod_jk2 no hi
és als
>> repositoris, i segons he vist en algunes pàgines abans hi
era , alguna
>> raó hi haurà.
>> l'apache2 carrega el modul jk , també hi tinc el ssh al
port 443 i
>> funciona perfectament,
>>
>> algú sap com fer anar l'apache i el tomcat5 alhora? o com
>> saber si realment el Tomcat esta funcionan i a quin port ?
>> Tinc la maquina virtual de Sun i el Kaffe, el tomcat
m'hagafa el jdk de
>> Sun que es el que esta definit al $PATH, que si no ho he
fet malament
>> l'he definit al .profile
>> al igual que les varibles de CATALINA
>>
>> faig un startup.sh desde el directori on hi ha el tomcat
desprès
>> de fer apt-get install tomcat5
>>
>>
>> gracies.
>>
>>
>>
>> --
>> If you don't know where you are going,
>> you will probably end up somewhere else
>> (Laurence J. Peter)
>> .''`.
>> using free software / Debian GNU/Linux | <a
href="/app/message?l=es&o=8&url=http%3A%2F%2Fdebian%2Eorg"
target="_blank">http://debian.org</a> : :' :
>> `. `'`
>> gpg --keyserver keys.indymedia.org --recv-keys B9A88F6F `-
>>
>>
>> --
>> To UNSUBSCRIBE, email to
>> <a
href="javascript:sendMsg('debian-user-catalan-REQUEST@lists.debian.org');">debian-user-catalan-REQUEST@lists.debian.org</a>
>> with a subject of "unsubscribe". Trouble? Contact
>> <a
href="javascript:sendMsg('listmaster@lists.debian.org');">listmaster@lists.debian.org</a>
>>
>>
>>
>>
>> --
>> www.sargue.net
>>
>>
>>
>>
>> Gracies he mirat el teu article , però he seguit els
teus passos i
>> res, hem sembla que apache2 va diferent
>> de fet tinc el mod_jk muntat i l'he carregat amb el
a2enmod jk, ara
>> funciona el tomcat al port 8080
>> l'apache com al dir de pàgines no hi tinc index en
llista els
>> directoris i el següent al fer <a
href="/app/message?l=es&o=8&url=http%3A%2F%2Flocalhost%3A"
target="_blank">http://localhost:</a>
>> Apache/2.0.55 (Debian) mod_jk/1.2.14 PHP/5.0.5-3
mod_ssl/2.0.55
>> OpenSSL/0.9.8a Server at localhost Port 80
>>
>> les pàgines *.jsp les he de tenir a
{$catalina_home}/webapp cert?
>> i com les crido des de localhost sense posar :8080 he de
definir el webapp
>> al /var/www / que es el directori per defecte del apache2?
>>
>> Aquestes son darreres lineas del log error .
>>
>> [Mon Dec 12 14:43:01 2005] [error]
ajp_service::jk_ajp_common.c (1758):
>> Error connecting to tomcat. Tomcat is probably not started
or is listening
>> on the wrong port. worker=ajp13_worker failed
>> [Mon Dec 12 14:43:01 2005] [info] jk_handler::mod_jk.c
(1971): Service
>> error=0 for worker=ajp13_worker
>>
>>
>> k2:/home/victor# /etc/init.d/apache2 force-reload
>> Forcing reload of apache 2.0 web server...grep:
/etc/apache2/conf.d/[^.#]*:
>> El fitxer o directori no existeix
>> [Mon Dec 12 14:50:13 2005] [warn] module ssl_module is
already loaded,
>> skipping
>> [Mon Dec 12 14:50:13 2005] [warn] module ssl_module is
already loaded,
>> skipping
>> [Mon Dec 12 14:50:13 2005] [warn] NameVirtualHost
localhost:443 has no
>> VirtualHosts
>> [Mon Dec 12 14:50:13 2005] [warn] NameVirtualHost *:0 has
no VirtualHosts
>> [Mon Dec 12 14:50:15 2005] [warn] module ssl_module is
already loaded,
>> skipping
>> [Mon Dec 12 14:50:15 2005] [warn] module ssl_module is
already loaded,
>> skipping
>> [Mon Dec 12 14:50:15 2005] [warn] NameVirtualHost
localhost:443 has no
>> VirtualHosts
>> [Mon Dec 12 14:50:15 2005] [warn] NameVirtualHost *:0 has
no VirtualHosts
>>
>>
>> Aquest darrer missatge al recarregar l'apache suposo no
te res a veure
>> però alguna cosa a la configuració del ssl deu estar
malament no ?
>>
>>
>>
>>
>> -- To UNSUBSCRIBE, email to
>> <a
href="javascript:sendMsg('debian-user-catalan-REQUEST@lists.debian.org');">debian-user-catalan-REQUEST@lists.debian.org</a>
with a subject
>> of "unsubscribe". Trouble? Contact <a
href="javascript:sendMsg('listmaster@lists.debian.org');">listmaster@lists.debian.org</a>
>--
>Salutacions.
>Rafel Puchades
Reply to: