date:20040806

Graham Leggett wrote:
> 
> >   Bounding to client connection is not needed(?).
> >   Since AJP can serve multiple request trough the same
> >   backend connection, no need to create separate conn_rec.
> >   For now comment out all the set/get module config.
> 
> Is there still a reason why in proxy_http the backend 
> connection still needs to be broken when the frontend client 
> breaks the connection? This behaviour was originally done 
> like that because there was no pool (until now :)).
>

I don't think so. The backend connection will have to be made
using HTTP/1.1 no mater what the client actually wants. If that doesn't
break
any RFC then we can use that.  
Well, I've designed the connection pool to support that, but I've choose the
conservative approach (for now :)).

> In theory, as long as the backend connection is made using 
> HTTP/1.1, and has keepalive enabled, that keepalive 
> connection could be reused for other frontend connections 
> from different clients.
> 

Sure, but only if that's really allowed.
I'm a little bit concerned about ssl connections, but in that case we can
make a decision
and either bound to the client or not.

I can make a configurable test solution that will allow us to test how this
'unbound mode' behaves in real-world situations.
It is very easy to do (just change conn->close_on_recycle to 0). Right now
it's hard-coded inside each scheme handler, but it can be set as
configurable option.
For serving static content from cluster of backend servers it wouldn't make
a difference, not sure for other contents.
Of course it would be a performance boost not needing to reconnect all the
time, but rather when the backend disconnects.

MT.

smime.p7s
Description: S/MIME cryptographic signature

DO NOT REPLY [Bug 30285] - Jasper fails to compile in a reloaded webapp with static method signature change

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30285

Jasper fails to compile in a reloaded webapp with static method signature change

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |



--- Additional Comments From [EMAIL PROTECTED]  2004-08-07 04:28 ---
Sorry,I missed that step in defect report.
Java servlet file,is compiled and put into WEB-INF\classes by IDE.

Then i reload the servlet.
The new changes are effective.

Only jasper fails.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru

Извините, программа не смогла распознть команду в вашем письме



Список команд нашей службы рассылки



Подтверждение регистрации в рассылках:

CONFIRM [EMAIL PROTECTED] password

пример: CONFIRM [EMAIL PROTECTED] 12ndjk45  



Подписка на рассылку:

SUBSCRIBE list.code

пример: SUBSCRIBE vf.news



Отписка от рассылки:

UNSUBSCRIBE list.code

или

UNSUBSCRIBE [EMAIL PROTECTED] list.code

пример: UNSUBSCRIBE vf.news

пример: UNSUBSCRIBE *   (отказ от всех рассылок)

пример: UNSUBSCRIBE [EMAIL PROTECTED] vf.news



Приостановление получения рассылок:

PAUSE  



Возобновление получения рассылок:

UNPAUSE 



Получение краткого списка рассылок (без описания - только названия):

LIST



Получение подробной информации (описание, статистика):

INFO list.code

пример: INFO vf.news



Получение списка рассылок, на которые вы подписаны:

WHICH



Письма с командами должны быть адресованы на адрес [EMAIL PROTECTED]

Сами команды пишутся в теле письма. Если вы даете одновременно несколько команд в 
одном письме, то каждую команду начинайте с новой строки.

Не забывайте, что все функции управления рассылками доступны и через веб-интерфейс по 
адресу http://list.mnogo.ru/


Izvinite, programma ne smogla raspoznt' komandu v vashem pis'me



Spisok komand nashej sluzhby rassylki



Podtverzhdenie registracii v rassylkax:

CONFIRM [EMAIL PROTECTED] password

primer: CONFIRM [EMAIL PROTECTED] 12ndjk45  



Podpiska na rassylku:

SUBSCRIBE list.code

primer: SUBSCRIBE vf.news



Otpiska ot rassylki:

UNSUBSCRIBE list.code

ili

UNSUBSCRIBE [EMAIL PROTECTED] list.code

primer: UNSUBSCRIBE vf.news

primer: UNSUBSCRIBE *   (otkaz ot vsex rassylok)

primer: UNSUBSCRIBE [EMAIL PROTECTED] vf.news



Priostanovlenie polucheniya rassylok:

PAUSE  



Vozobnovlenie polucheniya rassylok:

UNPAUSE 



Poluchenie kratkogo spiska rassylok (bez opisaniya - tol'ko nazvaniya):

LIST



Poluchenie podrobnoj informacii (opisanie, statistika):

INFO list.code

primer: INFO vf.news



Poluchenie spiska rassylok, na kotorye vy podpisany:

WHICH



Pis'ma s komandami dolzhny byt' adresovany na adres [EMAIL PROTECTED]

Sami komandy pishutsya v tele pis'ma. Esli vy daete odnovremenno neskol'ko komand v 
odnom pis'me, to kazhduyu komandu nachinajte s novoj stroki.

Ne zabyvajte, chto vse funkcii upravleniya rassylkami dostupny i cherez veb-interfejs 
po adresu http://list.mnogo.ru/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 27371] - java.lang.ThreadDeath caused by log4j when reloading Tomcat app

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27371

java.lang.ThreadDeath caused by log4j when reloading Tomcat app





--- Additional Comments From [EMAIL PROTECTED]  2004-08-07 00:55 ---

I was looking at the WebappClassLoader class and it contains a started attribute
that is used to determine that if the WebappClassLoader instance was started
before it can be used to load classes. The started attribute is set using the
classes start and stop methods. The ThreadDeath exception is being thrown
because when the WebappClassLoader instance is calling the loadClass method it
checks that the started attribute is true. If it isn't, it throws the
ThreadDeath exception.

I then looked at the StandardContext class. It contains a method called reload
that is used whenever it wants to reload that particular web application
associated to that instance of StandardContext. I also noticed that the
StandardContext method will associate a single WebappLoader to the
StandardContext instance. This WebappLoader contain the ClassLoader used by this
StandardContext web application. The assignment of the WebappLoader is done only
once and it is done within the start method only. This method initially checks
if the WebappLoader has been associated to the StandardContext. It will then
only assign a WebappLoader to the StandardContext if their was none.

I deduced by looking at these sections of the code that it seems like whenever a
 StandardContext web application is being reloaded. Its WebappLoader
WebappClassLoader start method is not be called before loading any of the web
application classes. It does seem like its stop method is being called whenever
the web application is being stopped.

This is why I believe that the WebappClassLoader is not being properly setup
before being used.

I am basing this on looking at the code only. I have not tried to debug this
case. It is only a theory based on observations and nothing else.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Human Resources

2004-08-06 Thread HR

We are in receipt of your resume. Your resume is being reviewed. Due to
the overwhelming response, please do not call us regarding your status.
We will contact you if we feel we will be able to help you at this time.
If you do not hear from us within the week, please feel free to resubmit
in two months. Thank you for your interest

 

Human Resources

Arenas Entertainment

100 N. Crescent Dr., Garden Level

Beverly Hills, CA 90210

(310) 385-4458 Fax

[EMAIL PROTECTED]

 

 

This e-mail and any attached files may contain confidential and/or
privileged material for the sole use of the intended recipient. Any
review, use, distribution or disclosure by others is strictly
prohibited. If you are not the intended recipient (or authorized to
receive this e-mail for the recipient), please contact the sender by
reply e-mail and delete all copies of this e-mail.

 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: cvs commit: jakarta-tomcat-connectors/ajp/proxy proxy_ajp.c

2004-08-06 Thread Graham Leggett

[EMAIL PROTECTED] wrote:
  Bounding to client connection is not needed(?).
  Since AJP can serve multiple request trough the same
  backend connection, no need to create separate conn_rec.
  For now comment out all the set/get module config.
Is there still a reason why in proxy_http the backend connection still 
needs to be broken when the frontend client breaks the connection? This 
behaviour was originally done like that because there was no pool (until 
now :)).

In theory, as long as the backend connection is made using HTTP/1.1, and 
has keepalive enabled, that keepalive connection could be reused for 
other frontend connections from different clients.

Regards,
Graham
--


smime.p7s
Description: S/MIME Cryptographic Signature

DO NOT REPLY [Bug 27371] - java.lang.ThreadDeath caused by log4j when reloading Tomcat app

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27371

java.lang.ThreadDeath caused by log4j when reloading Tomcat app





--- Additional Comments From [EMAIL PROTECTED]  2004-08-06 17:57 ---
What are you basing this on?  Any code references would be nice.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 27371] - java.lang.ThreadDeath caused by log4j when reloading Tomcat app

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27371

java.lang.ThreadDeath caused by log4j when reloading Tomcat app





--- Additional Comments From [EMAIL PROTECTED]  2004-08-06 17:55 ---

It seems to me that tomcat reuses these classloaders and I have a feeling that
when the classloader is being reused. The classloader start method does not get
called, causing the classloader to not have been "started", generating the
ThreadDeath exception whenever the loadClass method is called.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-tomcat-connectors/ajp/proxy proxy_ajp.c

mturk   2004/08/06 10:41:25

  Modified:ajp/proxy proxy_ajp.c
  Log:
  Bounding to client connection is not needed(?).
  Since AJP can serve multiple request trough the same
  backend connection, no need to create separate conn_rec.
  For now comment out all the set/get module config.
  
  Revision  ChangesPath
  1.13  +7 -1  jakarta-tomcat-connectors/ajp/proxy/proxy_ajp.c
  
  Index: proxy_ajp.c
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/ajp/proxy/proxy_ajp.c,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- proxy_ajp.c   6 Aug 2004 17:12:00 -   1.12
  +++ proxy_ajp.c   6 Aug 2004 17:41:25 -   1.13
  @@ -334,10 +334,12 @@
   /* only use stored info for top-level pages. Sub requests don't share 
* in keepalives
*/
  +#if 0
   if (!r->main) {
   backend = (proxy_conn_rec *) ap_get_module_config(c->conn_config,
 &proxy_ajp_module);
   }
  +#endif
   /* create space for state information */
   if (!backend) {
   status = ap_proxy_acquire_connection(scheme, &backend, worker, r->server);
  @@ -364,11 +366,12 @@
   
   if (status != OK)
   goto cleanup;
  -
   /* Step Two: Make the Connection */
   status = ap_proxy_connect_backend(scheme, backend, worker, r->server);
   if (status != OK)
   goto cleanup;
  +#if 0
  +/* XXX: we don't need to create the bound client connection */
   
   /* Step Three: Create conn_rec */
   if (!backend->connection) {
  @@ -376,6 +379,7 @@
   if (status != OK)
   goto cleanup;
   }
  +#endif
  
  
   /* Step Four: Send the Request */
  @@ -388,8 +392,10 @@
   status = ap_proxy_ajp_process_response(p, r, origin, backend,
  conf, server_portstr);
   cleanup:
  +#if 0
   /* Clear the module config */
   ap_set_module_config(c->conn_config, &proxy_ajp_module, NULL);
  +#endif
   /* Do not close the socket */
   ap_proxy_release_connection(scheme, backend, r->server);
   return status;
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [AJP] proxy status

 

> 
> Standard:
> Apache2.0.50/proxy_http   276 req/sec
> 
> New implementain (DEBUG compile):
> Apache2.0.50/proxy_http   329 req/sec
>  
>

Apache2.0.50/proxy_ajp  750 req/sec
Apache2.0.50/mod_jk 730 req/sec

So, we are slihtly faster :)

MT.


smime.p7s
Description: S/MIME cryptographic signature

RE: StandardClassLoader ?

2004-08-06 Thread Shapira, Yoav


Hola,
FWIW, I think current startup time is reasonable.  Most serious apps will do stuff in 
their ServletContextListener#contextInitialized or Servlet#init methods that will 
eclipse the Tomcat startup time anyhow.  I don't see it as an area of significant 
concern ;)

Yoav Shapira
Millennium Research Informatics


>-Original Message-
>From: Remy Maucherat [mailto:[EMAIL PROTECTED]
>Sent: Friday, August 06, 2004 1:09 PM
>To: Tomcat Developers List
>Subject: Re: StandardClassLoader ?
>
>Costin Manolache wrote:
>
>> Remy Maucherat wrote:
>>
>>> Costin Manolache wrote:
>>>
 Remy Maucherat wrote:

>  From my profile, the bottleneck for the startup time is XML
> parsing and accessing entries in JARs (we can't do anything about
> that), with a




 Did you try a pull parser ? kxml2 is really fast and only 42K :-)

 The other approach - which I think may have a lot of benefits - is
 to use some caches. For XML - you would need to make few of the
 classes serializable, or create few wrappers that are serializable.
 And whenver a change is detected - reparse. Not trivial code, but
 you can get a lot
 in cutting server.xml and web.xml parsing.
>>>
>>>
>>>
>>> The time is mostly parsing web.xml. However, it's nothing when
>>> compared to starting certain webapps (such as the admin webapp),
>>> where *one* webapp takes more time than starting up the rest of
>>> Tomcat (including all the simple webapps, JMX and the modeler
>>> descriptors, etc).
>>
>>
>> Does it really need "load-on-startup" for its ApplicationServlet ??
>
>Try it without ;)
>
>> Do we really need to load /admin on startup ? Most people never use it,
>> or use it only ocasionally. How many times do you configure the server ?
>
>I know, but it doesn't work right now (it's Struts' fault :( ). If you
>have ideas to make it work, then I'm obviously +1 for removing the
>load-on-startup thing.
>
>> Having "lazy loaded" webapps as a generic solution will help both
>> admin/ but also other infrequently used webapps. BTW - load-on-startup
>> doesn't necesarily mean "server startup" ( at least that's my
>> understanding ), it means when the webapp is started.
>
>I don't think we can have that. It doesn't fit the way the other stuff
>works (deployer, mapper).
>
>>
>>> The other big problem is the (needed) JAR parsing for TLDs during the
>>> deployment of a webapp.
>>
>> I tought we already have some code to cache the tlds and avoid
>> reparsing. This could be extended to the entire web.xml, and if we do
>> this - probably validation can be on ( since it'll happen only first
>> time and on web.xml change ).
>
>Yes, but the first time, it hurts ;)
>
>>
>>> Classloding and XML parsing are negligible when compared to these two
>>> things. So why bother ?
>>
>> You're right.
>>
>>> If I do the server.xml persistence that I envision, I'm using DOM for
>>> everything anyway.
>>
>> Well, you can use DOM for web.xml - but you need DOM only when
>> changing settings, so you can also create the dom lazy, and use the
>> .ser form
>> on regular startup.
>
>DOM is for server.xml. I don't think we need to save web.xml, right ?
>
>>
>>
>>>
 The jar index is also quite usefull IMO (  is it implemented in
 WebappClassLoader ? I can't find any code ).
>>>
>>>
>>>
>>> No, there's no index. I think it could be useful (mark that some
>>> packages are available in some JARs).
>>
>>
>> I was talking about the JDK1.4 index ( we already have > index=true...> ). URLClassLoader has this, but not our
>> findResourceInternal.
>>
>> But as you said - it's not a big priority.
>
>Yes, it should be added. This must be why the old StdCL performed worse
>than the UCL.
>
>>
>>> The thing I was planning to try just in case for StdCL was to load
>>> everything on creation of the classloader. Since in the end most
>>> classes will be loaded on startup, it would remove the need for syncing.
>>
>> Do you think syncing is a big problem ? Most of the time it should be
>> a free lock, and that is supposed to be reasonably fast.
>
>Yes, it should, but I thought maybe we could get a little something here
>(and with all the funky URL stuff the URL CL does).
>
>>
>> I'm curious how JDK1.5 support for multiple processes works and if we
>> could get some classes shared / cached.
>>
>> In any case - unless loading classes on startup without sync has a big
>> perf. improvement, I think it may be better to do the other
>> optimizations first.
>
>I agree. I'm kinda running out of optimization ideas, though (I don't
>know if you profiled the regular request processing lately, but there's
>really nothing left). There doesn't seem to be too much which is doable
>with the startup overall.
>
>Rémy
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business com

cvs commit: jakarta-tomcat-connectors/ajp/proxy proxy_ajp.c

mturk   2004/08/06 10:12:00

  Modified:ajp/proxy proxy_ajp.c
  Log:
  Use the new connection pool for AJP.
  
  Revision  ChangesPath
  1.12  +75 -346   jakarta-tomcat-connectors/ajp/proxy/proxy_ajp.c
  
  Index: proxy_ajp.c
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/ajp/proxy/proxy_ajp.c,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- proxy_ajp.c   2 Aug 2004 17:05:06 -   1.11
  +++ proxy_ajp.c   6 Aug 2004 17:12:00 -   1.12
  @@ -20,24 +20,6 @@
   
   module AP_MODULE_DECLARE_DATA proxy_ajp_module;
   
  -int ap_proxy_ajp_canon(request_rec *r, char *url);
  -int ap_proxy_ajp_handler(request_rec *r, proxy_server_conf *conf,
  -  char *url, const char *proxyname, 
  -  apr_port_t proxyport);
  -
  -typedef struct {
  -const char *name;
  -apr_port_t  port;
  -apr_sockaddr_t *addr;
  -apr_socket_t   *sock;
  -int close;
  -void   *data;  /* To store ajp data */
  -} proxy_ajp_conn_t;
  -
  -static apr_status_t ap_proxy_ajp_cleanup(request_rec *r,
  -  proxy_ajp_conn_t *p_conn,
  -  proxy_conn_rec *backend);
  -
   /*
* Canonicalise http-like URLs.
*  scheme is the scheme for the URL
  @@ -116,230 +98,9 @@
   }

   static
  -apr_status_t ap_proxy_http_determine_connection(apr_pool_t *p, request_rec *r,
  -proxy_ajp_conn_t *p_conn,
  -conn_rec *c,
  -proxy_server_conf *conf,
  -apr_uri_t *uri,
  -char **url,
  -const char *proxyname,
  -apr_port_t proxyport,
  -char *server_portstr,
  -int server_portstr_size) {
  -int server_port;
  -apr_status_t err;
  -apr_sockaddr_t *uri_addr;
  -/*
  - * Break up the URL to determine the host to connect to
  - */
  -
  -/* we break the URL into host, port, uri */
  -if (APR_SUCCESS != apr_uri_parse(p, *url, uri)) {
  -return ap_proxyerror(r, HTTP_BAD_REQUEST,
  - apr_pstrcat(p,"URI cannot be parsed: ", *url,
  - NULL));
  -}
  -if (!uri->port) {
  -uri->port = apr_uri_port_of_scheme(uri->scheme);
  -}
  -
  -ap_log_error(APLOG_MARK, APLOG_DEBUG, 0, r->server,
  - "proxy: AJP connecting %s to %s:%d", *url, uri->hostname,
  - uri->port);
  -
  -/* do a DNS lookup for the destination host */
  -/* see memory note above */
  -err = apr_sockaddr_info_get(&uri_addr, apr_pstrdup(c->pool, uri->hostname),
  -APR_UNSPEC, uri->port, 0, c->pool);
  -
  -/* allocate these out of the connection pool - the check on
  - * r->connection->id makes sure that this string does not get accessed
  - * past the connection lifetime */
  -/* are we connecting directly, or via a proxy? */
  -if (proxyname) {
  -p_conn->name = apr_pstrdup(c->pool, proxyname);
  -p_conn->port = proxyport;
  -/* see memory note above */
  -err = apr_sockaddr_info_get(&p_conn->addr, p_conn->name, APR_UNSPEC,
  -p_conn->port, 0, c->pool);
  -} else {
  -p_conn->name = apr_pstrdup(c->pool, uri->hostname);
  -p_conn->port = uri->port;
  -p_conn->addr = uri_addr;
  -*url = apr_pstrcat(p, uri->path, uri->query ? "?" : "",
  -   uri->query ? uri->query : "",
  -   uri->fragment ? "#" : "",
  -   uri->fragment ? uri->fragment : "", NULL);
  -}
  -
  -if (err != APR_SUCCESS) {
  -return ap_proxyerror(r, HTTP_BAD_GATEWAY,
  - apr_pstrcat(p, "DNS lookup failure for: ",
  - p_conn->name, NULL));
  -}
  -
  -/* Get the server port for the Via headers */
  -{
  -server_port = ap_get_server_port(r);
  -if (ap_is_default_port(server_port, r)) {
  -strcpy(server_portstr,"");
  -} else {
  -apr_snprintf(server_portstr, server_portstr_size, ":%d",
  - server_port);
  -}
  -}
  -
  -/* check if ProxyBlock directive on this host */
  -if (OK != ap_proxy_checkproxyblock(r, conf, uri_addr)) {
  -return ap_proxyerror(r, HTTP_FORBIDDEN,
  - "Connect to remote mac

Costin Manolache wrote:
Remy Maucherat wrote:
Costin Manolache wrote:
Remy Maucherat wrote:
From my profile, the bottleneck for the startup time is XML
parsing and accessing entries in JARs (we can't do anything about
that), with a

Did you try a pull parser ? kxml2 is really fast and only 42K :-)
The other approach - which I think may have a lot of benefits - is
to use some caches. For XML - you would need to make few of the
classes serializable, or create few wrappers that are serializable.
And whenver a change is detected - reparse. Not trivial code, but
you can get a lot
in cutting server.xml and web.xml parsing.

Does it really need "load-on-startup" for its ApplicationServlet ??
Try it without ;)
Do we really need to load /admin on startup ? Most people never use it,
or use it only ocasionally. How many times do you configure the server ?
I know, but it doesn't work right now (it's Struts' fault :( ). If you
have ideas to make it work, then I'm obviously +1 for removing the
load-on-startup thing.

Having "lazy loaded" webapps as a generic solution will help both
admin/ but also other infrequently used webapps. BTW - load-on-startup
doesn't necesarily mean "server startup" ( at least that's my
understanding ), it means when the webapp is started.
I don't think we can have that. It doesn't fit the way the other stuff
works (deployer, mapper).

The other big problem is the (needed) JAR parsing for TLDs during the
deployment of a webapp.
I tought we already have some code to cache the tlds and avoid
reparsing. This could be extended to the entire web.xml, and if we do
this - probably validation can be on ( since it'll happen only first
time and on web.xml change ).
Yes, but the first time, it hurts ;)

Classloding and XML parsing are negligible when compared to these two
things. So why bother ?
You're right.
If I do the server.xml persistence that I envision, I'm using DOM for
everything anyway.
Well, you can use DOM for web.xml - but you need DOM only when
changing settings, so you can also create the dom lazy, and use the
.ser form
on regular startup.
DOM is for server.xml. I don't think we need to save web.xml, right ?

The jar index is also quite usefull IMO ( is it implemented in
WebappClassLoader ? I can't find any code ).

No, there's no index. I think it could be useful (mark that some
packages are available in some JARs).

I was talking about the JDK1.4 index ( we already have ). URLClassLoader has this, but not our
findResourceInternal.

But as you said - it's not a big priority.
Yes, it should be added. This must be why the old StdCL performed worse
than the UCL.

The thing I was planning to try just in case for StdCL was to load
everything on creation of the classloader. Since in the end most
classes will be loaded on startup, it would remove the need for syncing.
Do you think syncing is a big problem ? Most of the time it should be
a free lock, and that is supposed to be reasonably fast.
Yes, it should, but I thought maybe we could get a little something here
(and with all the funky URL stuff the URL CL does).

I'm curious how JDK1.5 support for multiple processes works and if we
could get some classes shared / cached.

In any case - unless loading classes on startup without sync has a big
perf. improvement, I think it may be better to do the other
optimizations first.
I agree. I'm kinda running out of optimization ideas, though (I don't
know if you profiled the regular request processing lately, but there's
really nothing left). There doesn't seem to be too much which is doable
with the startup overall.

Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 27371] - java.lang.ThreadDeath caused by log4j when reloading Tomcat app

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27371

java.lang.ThreadDeath caused by log4j when reloading Tomcat app





--- Additional Comments From [EMAIL PROTECTED]  2004-08-06 16:25 ---
I can confirm that the following does _not_ solve the ThreadDeath exception 
when Tomcat reloads the context following a class compile.

import org.apache.log4j.LogManager;
import org.apache.commons.logging.LogFactory;

public void contextDestroyed(ServletContextEvent scE) { 
LogManager.shutdown();
LogFactory.releaseAll();
}

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Yahoo! Auto Response

2004-08-06 Thread ugurlar

We are on vacation until beginning of November 2004.

2004 Kasim ayina kadar tatildeyiz.






Original Message:


X-Rocket-Spam: 212.175.79.10
X-YahooFilteredBulk: 212.175.79.10
X-Rocket-Track: 47992: 20 ; SERVER=216.155.197.136
X-Originating-IP: [212.175.79.10]
Return-Path: <[EMAIL PROTECTED]>
Received: from 212.175.79.10  (EHLO yahoo.com) (212.175.79.10)
  by mta116.mail.re2.yahoo.com with SMTP; Fri, 06 Aug 2004 08:28:31 -0700
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Failure ([EMAIL PROTECTED])
Date: Fri, 6 Aug 2004 18:29:22 +0300
MIME-Version: 1.0
Content-Type: multipart/related;
type="multipart/alternative";
boundary="=_NextPart_000_001B_01C0CA81.7B015D10"
X-Priority: 1
X-MSMail-Priority: High

This is a multi-part message in MIME format.

--=_NextPart_000_001B_01C0CA81.7B015D10
Content-Type: multipart/alternative;
boundary="=_NextPart_001_001C_01C0CA81.7B015D10"

--=_NextPart_001_001C_01C0CA81.7B015D10
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

--=_NextPart_001_001C_01C0CA81.7B015D10
_
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: StandardClassLoader ?

2004-08-06 Thread Costin Manolache

Remy Maucherat wrote:
Costin Manolache wrote:
Remy Maucherat wrote:
From my profile, the bottleneck for the startup time is XML parsing
and accessing entries in JARs (we can't do anything about that), with a

Did you try a pull parser ? kxml2 is really fast and only 42K :-)
The other approach - which I think may have a lot of benefits - is to
use some caches. For XML - you would need to make few of the classes
serializable, or create few wrappers that are serializable. And
whenver a change is detected - reparse. Not trivial code, but you can
get a lot
in cutting server.xml and web.xml parsing.

The time is mostly parsing web.xml. However, it's nothing when compared
to starting certain webapps (such as the admin webapp), where *one*
webapp takes more time than starting up the rest of Tomcat (including
all the simple webapps, JMX and the modeler descriptors, etc).
Does it really need "load-on-startup" for its ApplicationServlet ??
Do we really need to load /admin on startup ? Most people never use it,
or use it only ocasionally. How many times do you configure the server ?
Having "lazy loaded" webapps as a generic solution will help both admin/
but also other infrequently used webapps. BTW - load-on-startup doesn't
necesarily mean "server startup" ( at least that's my understanding ),
it means when the webapp is started.

Classloding and XML parsing are negligible when compared to these two
things. So why bother ?
You're right.

If I do the server.xml persistence that I envision, I'm using DOM for
everything anyway.
Well, you can use DOM for web.xml - but you need DOM only when changing
settings, so you can also create the dom lazy, and use the .ser form
on regular startup.

The jar index is also quite usefull IMO ( is it implemented in
WebappClassLoader ? I can't find any code ).

No, there's no index. I think it could be useful (mark that some
packages are available in some JARs).
I was talking about the JDK1.4 index ( we already have ). URLClassLoader has this, but not our findResourceInternal.

But as you said - it's not a big priority.

The thing I was planning to try just in case for StdCL was to load
everything on creation of the classloader. Since in the end most classes
will be loaded on startup, it would remove the need for syncing.
Do you think syncing is a big problem ? Most of the time it should be a
free lock, and that is supposed to be reasonably fast.

I'm curious how JDK1.5 support for multiple processes works and if we
could get some classes shared / cached.

In any case - unless loading classes on startup without sync has a big
perf. improvement, I think it may be better to do the other
optimizations first.

Costin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: StandardClassLoader ?

2004-08-06 Thread Remy Maucherat

Costin Manolache wrote:
Remy Maucherat wrote:
 From my profile, the bottleneck for the startup time is XML parsing 
and accessing entries in JARs (we can't do anything about that), with a 

Did you try a pull parser ? kxml2 is really fast and only 42K :-)
The other approach - which I think may have a lot of benefits - is to 
use some caches. For XML - you would need to make few of the classes 
serializable, or create few wrappers that are serializable.  And 
whenver a change is detected - reparse. Not trivial code, but you can 
get a lot
in cutting server.xml and web.xml parsing.
The time is mostly parsing web.xml. However, it's nothing when compared 
to starting certain webapps (such as the admin webapp), where *one* 
webapp takes more time than starting up the rest of Tomcat (including 
all the simple webapps, JMX and the modeler descriptors, etc).

The other big problem is the (needed) JAR parsing for TLDs during the 
deployment of a webapp.

Classloding and XML parsing are negligible when compared to these two 
things. So why bother ?

If I do the server.xml persistence that I envision, I'm using DOM for 
everything anyway.

The jar index is also quite usefull IMO (  is it implemented in
WebappClassLoader ? I can't find any code ).
No, there's no index. I think it could be useful (mark that some 
packages are available in some JARs).

The thing I was planning to try just in case for StdCL was to load 
everything on creation of the classloader. Since in the end most classes 
will be loaded on startup, it would remove the need for syncing.

Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: StandardClassLoader ?

2004-08-06 Thread Costin Manolache

Remy Maucherat wrote:
 From my profile, the bottleneck for the startup time is XML parsing and 
accessing entries in JARs (we can't do anything about that), with a 
Did you try a pull parser ? kxml2 is really fast and only 42K :-)
The other approach - which I think may have a lot of benefits - is to 
use some caches. For XML - you would need to make few of the classes 
serializable, or create few wrappers that are serializable.  And whenver 
a change is detected - reparse. Not trivial code, but you can get a lot
in cutting server.xml and web.xml parsing.

The jar index is also quite usefull IMO (  is it implemented in
WebappClassLoader ? I can't find any code ).
Costin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [AJP] proxy status

 

Remy Maucherat wrote:

> >Yes, only the single DNS per worker(connection pool) query is used 
> >(unless entire worker is recycled).
> >  
> >
> So the DNS lookup happens once, right ? Good.
>

And...

Standard:
Apache2.0.50/proxy_http 276 req/sec

New implementain (DEBUG compile):
Apache2.0.50/proxy_http 329 req/sec
 

MT.


smime.p7s
Description: S/MIME cryptographic signature

cvs commit: jakarta-tomcat-connectors/ajp/proxy proxy_http.c

mturk   2004/08/06 07:12:22

  Modified:ajp/proxy proxy_http.c
  Log:
  Always use the cleanup. Do not close the socket directly.
  
  Revision  ChangesPath
  1.4   +2 -6  jakarta-tomcat-connectors/ajp/proxy/proxy_http.c
  
  Index: proxy_http.c
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/ajp/proxy/proxy_http.c,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- proxy_http.c  6 Aug 2004 14:05:45 -   1.3
  +++ proxy_http.c  6 Aug 2004 14:12:22 -   1.4
  @@ -795,9 +795,7 @@
   len = ap_getline(buffer, sizeof(buffer), rp, 0);
   }
   if (len <= 0) {
  -apr_socket_close(backend->sock);
  -backend->sock = NULL;
  -//backend->connection = NULL;
  +ap_proxy_http_cleanup(NULL, r, backend);
   ap_log_rerror(APLOG_MARK, APLOG_ERR, 0, r,
 "proxy: error reading status line from remote "
 "server %s", backend->hostname);
  @@ -819,9 +817,7 @@
* if the status line was > 8192 bytes
*/
   else if ((buffer[5] != '1') || (len >= sizeof(buffer)-1)) {
  -apr_socket_close(backend->sock);
  -//backend->connection = NULL;
  -backend->sock = NULL;
  +ap_proxy_http_cleanup(NULL, r, backend);
   return ap_proxyerror(r, HTTP_BAD_GATEWAY,
   apr_pstrcat(p, "Corrupt status line returned by remote "
   "server: ", buffer, NULL));
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-tomcat-connectors/ajp/proxy proxy_http.c proxy_util.c

mturk   2004/08/06 07:05:46

  Modified:ajp/proxy proxy_http.c proxy_util.c
  Log:
  Fix the assertion bug for reslist caused by returning the
  same connection back to the pool twice.
  
  Revision  ChangesPath
  1.3   +8 -13 jakarta-tomcat-connectors/ajp/proxy/proxy_http.c
  
  Index: proxy_http.c
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/ajp/proxy/proxy_http.c,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- proxy_http.c  6 Aug 2004 11:44:45 -   1.2
  +++ proxy_http.c  6 Aug 2004 14:05:45 -   1.3
  @@ -796,7 +796,8 @@
   }
   if (len <= 0) {
   apr_socket_close(backend->sock);
  -backend->connection = NULL;
  +backend->sock = NULL;
  +//backend->connection = NULL;
   ap_log_rerror(APLOG_MARK, APLOG_ERR, 0, r,
 "proxy: error reading status line from remote "
 "server %s", backend->hostname);
  @@ -819,7 +820,8 @@
*/
   else if ((buffer[5] != '1') || (len >= sizeof(buffer)-1)) {
   apr_socket_close(backend->sock);
  -backend->connection = NULL;
  +//backend->connection = NULL;
  +backend->sock = NULL;
   return ap_proxyerror(r, HTTP_BAD_GATEWAY,
   apr_pstrcat(p, "Corrupt status line returned by remote "
   "server: ", buffer, NULL));
  @@ -1029,7 +1031,7 @@
* backend server from hanging around waiting
* for a slow client to eat these bytes
*/
  -ap_proxy_http_cleanup(NULL, r, backend);
  +backend->close = 1;
   /* signal that we must leave */
   finish = TRUE;
   }
  @@ -1092,18 +1094,11 @@
   /* if the connection is < HTTP/1.1, or Connection: close,
* we close the socket, otherwise we leave it open for KeepAlive support
*/
  -if (backend->close) {
  +if (backend->close || (r->proto_num < HTTP_VERSION(1,1))) {
   backend->close_on_recycle = 1;
  -ap_set_module_config(r->connection, &proxy_http_module, backend);
  +ap_set_module_config(r->connection->conn_config, &proxy_http_module, NULL);
   ap_proxy_release_connection(scheme, backend, r->server);
   }
  -else if(r->proto_num < HTTP_VERSION(1,1)) {
  -if (backend->sock) {
  -apr_socket_close(backend->sock);
  -backend->sock = NULL;
  -backend->connection = NULL;
  -}
  -}
   return OK;
   }
   
  @@ -1231,7 +1226,7 @@
   /* Step Five: Receive the Response */
   status = ap_proxy_http_process_response(p, r, backend, backend->connection, 
conf,
   server_portstr);
  -if ( status != OK ) {
  +if (status != OK) {
   /* clean up even if there is an error */
   ap_proxy_http_cleanup(scheme, r, backend);
   return status;
  
  
  
  1.20  +22 -39jakarta-tomcat-connectors/ajp/proxy/proxy_util.c
  
  Index: proxy_util.c
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/ajp/proxy/proxy_util.c,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- proxy_util.c  6 Aug 2004 11:43:53 -   1.19
  +++ proxy_util.c  6 Aug 2004 14:05:45 -   1.20
  @@ -1319,14 +1319,24 @@
   static apr_status_t connection_cleanup(void *theconn)
   {
   proxy_conn_rec *conn = (proxy_conn_rec *)theconn;
  +proxy_worker *worker = conn->worker;
  +
   /* deterimine if the connection need to be closed */
   if (conn->close_on_recycle) {
   if (conn->sock)
   apr_socket_close(conn->sock);
   conn->sock = NULL;
   }
  -conn->connection = NULL;
  -ap_proxy_release_connection(NULL, conn, NULL);
  +#if APR_HAS_THREADS
  +if (worker->hmax && worker->cp->res) {
  +apr_reslist_release(worker->cp->res, (void *)conn);
  +}
  +else
  +#endif
  +{
  +worker->cp->conn = conn;
  +}
  +
   /* Allways return the SUCCESS */
   return APR_SUCCESS;
   }
  @@ -1486,39 +1496,12 @@
  server_rec *s)
   {
   apr_status_t rv = APR_SUCCESS;
  -proxy_worker *worker = conn->worker;
   
  -if (!worker) {
  -/* something bad happened. Obviously bug.
  - * for now make a core dump.
  - */
  -}
  -
  -/* Need to close the connection */
  -if (conn->sock && conn->close) {
  -apr_socket_close(conn->sock);
  -conn->sock = NULL;
  -}
  -conn->clo

RE: Tomcat hangs

2004-08-06 Thread Shapira, Yoav


Hi,
This discussion belongs on the tomcat-user list, not tomcat-dev, so
please continue it there.  Thanks,

Yoav Shapira
Millennium Research Informatics


>-Original Message-
>From: Gaurav Handa [mailto:[EMAIL PROTECTED]
>Sent: Friday, August 06, 2004 9:53 AM
>To: Tomcat Developers List
>Subject: RE: Tomcat hangs
>
>Is it the acceptCount attribute that i need to modify
>
>Regards,
>Gaurav Handa
>9281
>
>
>-Original Message-
>From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
>Sent: Friday, August 06, 2004 7:21 PM
>To: Tomcat Developers List
>Subject: RE: Tomcat hangs
>
>
>
>Hi,
>You can replicate (not share) sessions via clustering: see the
>Clustering How-To in the Tomcat docs.
>
>You can add request processing threads to your server by configuring
the
>Connector element in server.xml.  See the Connector configuration
>reference page in the Tomcat docs.
>
>Yoav Shapira
>Millennium Research Informatics
>
>
>>-Original Message-
>>From: Gaurav Handa [mailto:[EMAIL PROTECTED]
>>Sent: Friday, August 06, 2004 9:46 AM
>>To: [EMAIL PROTECTED]
>>Subject: Tomcat hangs
>>
>>hi
>>
>> i have one problem in Tomcat. I have XSLT generated webpage which
>contains
>>60-100 images. The src of these
>> images is my web server where tomcat is running. After 4-5 users
>>simultaneouly request for this page the tomcat
>> hangs. Can any one help me on this? . My webserver uses a framework
to
>>maintain the database sessions, can they
>> be shared via clustering or load balancing
>>
>>Regards,
>>Gaurav Handa
>>9281
>>
>>
>>-
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>This e-mail, including any attachments, is a confidential business
>communication, and may contain information that is confidential,
>proprietary
>and/or privileged.  This e-mail is intended only for the individual(s)
to
>whom it is addressed, and may not be saved, copied, printed, disclosed
or
>used by anyone else.  If you are not the(an) intended recipient, please
>immediately delete this e-mail from your computer system and notify the
>sender.  Thank you.
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [AJP] proxy status

2004-08-06 Thread Remy Maucherat

Mladen Turk wrote:
No the request is still 1.0 and proxy_http checks r->proto_num <
HTTP_VERSION(1,1).
Requested standard servlet/HelloWorldExample.¨
 

Ok. You can hack a little ab.c to have it generate a HTTP/1.1 request ;)
Obviously HTTP/1.0 is not favorable for proxying, so I think HTTP/1.1 
would look better.

Did you solve the DNS querying issue ?
   

Yes, only the single DNS per worker(connection pool) query is used (unless
entire worker is recycled).
 

So the DNS lookup happens once, right ? Good.
Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [AJP] proxy status

2004-08-06 Thread jean-frederic clere

Mladen Turk wrote:
Hi all,
I've finished the connection pool for mod_proxy.
The proxy_http now uses the connection pool (cca 10% speedup for HTTP1.0,
the 1.1 should be even higher, but the ab doesn't support 1.1).
If someone is willing to test and chase the bugs, he's more then welcome :).
I have "started" to document  the new things in 
jakarta-tomcat-connectors/jk/xdocs/proxy.xml fill free to improve it.

TODO:
1. Porting the mechanism from http to proxy_ajp.
2. Using connection pool in ftp.
3. Actually build proxy_balancer [mturk]
BUGS:
- Still OS 10048)Only one usage of each socket address on WIN32.
  I'll dig into it to find the reason.
- Assertion failed: rl->ntotal == 0, file .\misc\apr_reslist.c, line 164
  This manifests on server shutdown. I've probably done some mess with
  pool cleanup. It would be great if someone finds the cause :)

Regards,
MT.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat hangs

2004-08-06 Thread Gaurav Handa

Is it the acceptCount attribute that i need to modify

Regards,
Gaurav Handa
9281


-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Friday, August 06, 2004 7:21 PM
To: Tomcat Developers List
Subject: RE: Tomcat hangs



Hi,
You can replicate (not share) sessions via clustering: see the
Clustering How-To in the Tomcat docs.

You can add request processing threads to your server by configuring the
Connector element in server.xml.  See the Connector configuration
reference page in the Tomcat docs.

Yoav Shapira
Millennium Research Informatics


>-Original Message-
>From: Gaurav Handa [mailto:[EMAIL PROTECTED]
>Sent: Friday, August 06, 2004 9:46 AM
>To: [EMAIL PROTECTED]
>Subject: Tomcat hangs
>
>hi
>
> i have one problem in Tomcat. I have XSLT generated webpage which
contains
>60-100 images. The src of these
> images is my web server where tomcat is running. After 4-5 users
>simultaneouly request for this page the tomcat
> hangs. Can any one help me on this? . My webserver uses a framework to
>maintain the database sessions, can they
> be shared via clustering or load balancing
>
>Regards,
>Gaurav Handa
>9281
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential, proprietary
and/or privileged.  This e-mail is intended only for the individual(s) to
whom it is addressed, and may not be saved, copied, printed, disclosed or
used by anyone else.  If you are not the(an) intended recipient, please
immediately delete this e-mail from your computer system and notify the
sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat hangs

2004-08-06 Thread Gaurav Handa

hi shapira

what is the maximum limit of these threads?

Regards,
Gaurav Handa
9281


-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Friday, August 06, 2004 7:21 PM
To: Tomcat Developers List
Subject: RE: Tomcat hangs



Hi,
You can replicate (not share) sessions via clustering: see the
Clustering How-To in the Tomcat docs.

You can add request processing threads to your server by configuring the
Connector element in server.xml.  See the Connector configuration
reference page in the Tomcat docs.

Yoav Shapira
Millennium Research Informatics


>-Original Message-
>From: Gaurav Handa [mailto:[EMAIL PROTECTED]
>Sent: Friday, August 06, 2004 9:46 AM
>To: [EMAIL PROTECTED]
>Subject: Tomcat hangs
>
>hi
>
> i have one problem in Tomcat. I have XSLT generated webpage which
contains
>60-100 images. The src of these
> images is my web server where tomcat is running. After 4-5 users
>simultaneouly request for this page the tomcat
> hangs. Can any one help me on this? . My webserver uses a framework to
>maintain the database sessions, can they
> be shared via clustering or load balancing
>
>Regards,
>Gaurav Handa
>9281
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential, proprietary
and/or privileged.  This e-mail is intended only for the individual(s) to
whom it is addressed, and may not be saved, copied, printed, disclosed or
used by anyone else.  If you are not the(an) intended recipient, please
immediately delete this e-mail from your computer system and notify the
sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat hangs

2004-08-06 Thread Shapira, Yoav


Hi,
You can replicate (not share) sessions via clustering: see the
Clustering How-To in the Tomcat docs.

You can add request processing threads to your server by configuring the
Connector element in server.xml.  See the Connector configuration
reference page in the Tomcat docs.

Yoav Shapira
Millennium Research Informatics


>-Original Message-
>From: Gaurav Handa [mailto:[EMAIL PROTECTED]
>Sent: Friday, August 06, 2004 9:46 AM
>To: [EMAIL PROTECTED]
>Subject: Tomcat hangs
>
>hi
>
> i have one problem in Tomcat. I have XSLT generated webpage which
contains
>60-100 images. The src of these
> images is my web server where tomcat is running. After 4-5 users
>simultaneouly request for this page the tomcat
> hangs. Can any one help me on this? . My webserver uses a framework to
>maintain the database sessions, can they
> be shared via clustering or load balancing
>
>Regards,
>Gaurav Handa
>9281
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat hangs

2004-08-06 Thread Gaurav Handa

hi 

 i have one problem in Tomcat. I have XSLT generated webpage which contains
60-100 images. The src of these
 images is my web server where tomcat is running. After 4-5 users
simultaneouly request for this page the tomcat
 hangs. Can any one help me on this? . My webserver uses a framework to
maintain the database sessions, can they
 be shared via clustering or load balancing

Regards,
Gaurav Handa
9281


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [AJP] proxy status

 

Graham Leggett wrote:
> 
> Cool bananas! Possible stupid question: how do I get hold of 
> this code? 
> (Which repository is it in?)
>

http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-connectors/ajp/proxy/

Works both on 2.1 and 2.0.
 
> > TODO:
> > 1. Porting the mechanism from http to proxy_ajp.
> > 2. Using connection pool in ftp.
> > 3. Actually build proxy_balancer [mturk]
> 
> So to clarify, the proxy framework (ie mod_proxy) now has a 
> connection pool, and mod_proxy_http now uses it (with 
> proxy_ajp on the way)?
>

Yes. 

> I am trying to work out which bits are built into proxy, and 
> which bits are in a separate module via a hook. I'd like to 
> see all this stuff go into httpd v2.0 if possible, and want 
> to figure out what the impact will be.
>

Regarding latest discussinon on HTTP-dev reharding backports, I wish you all
the luck :).
 
> There is currently lots of work on mod_cache* and mod_ldap* 
> in httpd, with talk of releasing httpd v2.2 GA around Apachecon time.
> 

MT.


smime.p7s
Description: S/MIME cryptographic signature

cvs commit: jakarta-tomcat-catalina/webapps/docs/config ajp.xml

2004-08-06 Thread yoavs

yoavs   2004/08/06 06:14:26

  Modified:webapps/docs changelog.xml
   webapps/docs/config ajp.xml
  Log:
  Fixed broken link to JK docs on AJP page.
  
  Revision  ChangesPath
  1.88  +3 -0  jakarta-tomcat-catalina/webapps/docs/changelog.xml
  
  Index: changelog.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/changelog.xml,v
  retrieving revision 1.87
  retrieving revision 1.88
  diff -u -r1.87 -r1.88
  --- changelog.xml 5 Aug 2004 20:10:48 -   1.87
  +++ changelog.xml 6 Aug 2004 13:14:25 -   1.88
  @@ -64,6 +64,9 @@
 
   29869: Better JMX/JSR77 support in StandardContext and 
StandardWrapper. (remm)
 
  +   
  +Fixed broken link to JK documenration from AJP Connector reference page. 
(yoavs)
  +  
   
 
   
  
  
  
  1.6   +5 -3  jakarta-tomcat-catalina/webapps/docs/config/ajp.xml
  
  Index: ajp.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/ajp.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- ajp.xml   23 Jul 2004 14:13:41 -  1.5
  +++ ajp.xml   6 Aug 2004 13:14:26 -   1.6
  @@ -144,15 +144,17 @@
   
   
   
  -  
  +  None at this time.
   
   
   
   
   
   
  -  Please refer to the http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/doc/";>JK 
documentation 
  - for HOWTOs and complete configuration information.
  +  Please refer to the 
  +JK documentation 
  + for HOW-TOs and complete configuration information.
  +  
   
   
   
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [AJP] proxy status

2004-08-06 Thread Graham Leggett

Mladen Turk wrote:
I've finished the connection pool for mod_proxy.
The proxy_http now uses the connection pool (cca 10% speedup for HTTP1.0,
the 1.1 should be even higher, but the ab doesn't support 1.1).
If someone is willing to test and chase the bugs, he's more then welcome :).
Cool bananas! Possible stupid question: how do I get hold of this code? 
(Which repository is it in?)

TODO:
1. Porting the mechanism from http to proxy_ajp.
2. Using connection pool in ftp.
3. Actually build proxy_balancer [mturk]
So to clarify, the proxy framework (ie mod_proxy) now has a connection 
pool, and mod_proxy_http now uses it (with proxy_ajp on the way)?

I am trying to work out which bits are built into proxy, and which bits 
are in a separate module via a hook. I'd like to see all this stuff go 
into httpd v2.0 if possible, and want to figure out what the impact will be.

There is currently lots of work on mod_cache* and mod_ldap* in httpd, 
with talk of releasing httpd v2.2 GA around Apachecon time.

Regards,
Graham
--


smime.p7s
Description: S/MIME Cryptographic Signature

Muchas gracias por su sugerencia

2004-08-06 Thread [EMAIL PROTECTED]

De nuestra mayor consideración:

Muchas gracias por su sugerencia. La tendremos en cuenta para el momento en que surja 
la oportunidad de ofrecer nuevos cursos.

Cordialmente,

Equipo de En Plenitud
www.enplenitud.com
[EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [AJP] proxy status

Remy Maucherat wrote:
> >
> >I've finished the connection pool for mod_proxy.
> >The proxy_http now uses the connection pool (cca 10% speedup for 
> >HTTP1.0, the 1.1 should be even higher, but the ab doesn't 
> support 1.1).
> >  
> >
> You should probably test with "-k" = HTTP/1.0 with keepalive, 
> and request something which sets the content-length.

No the request is still 1.0 and proxy_http checks r->proto_num <
HTTP_VERSION(1,1).
Requested standard servlet/HelloWorldExample.

> Did you solve the DNS querying issue ?
> 

Yes, only the single DNS per worker(connection pool) query is used (unless
entire worker is recycled).

MT.

smime.p7s
Description: S/MIME cryptographic signature

Re: [AJP] proxy status

2004-08-06 Thread Remy Maucherat

Mladen Turk wrote:
Hi all,
I've finished the connection pool for mod_proxy.
The proxy_http now uses the connection pool (cca 10% speedup for HTTP1.0,
the 1.1 should be even higher, but the ab doesn't support 1.1).
 

You should probably test with "-k" = HTTP/1.0 with keepalive, and 
request something which sets the content-length.
Did you solve the DNS querying issue ?

Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[AJP] proxy status

Hi all,

I've finished the connection pool for mod_proxy.
The proxy_http now uses the connection pool (cca 10% speedup for HTTP1.0,
the 1.1 should be even higher, but the ab doesn't support 1.1).
If someone is willing to test and chase the bugs, he's more then welcome :).

TODO:
1. Porting the mechanism from http to proxy_ajp.
2. Using connection pool in ftp.
3. Actually build proxy_balancer [mturk]

BUGS:
- Still OS 10048)Only one usage of each socket address on WIN32.
  I'll dig into it to find the reason.

- Assertion failed: rl->ntotal == 0, file .\misc\apr_reslist.c, line 164
  This manifests on server shutdown. I've probably done some mess with
  pool cleanup. It would be great if someone finds the cause :)



Regards,
MT.


smime.p7s
Description: S/MIME cryptographic signature

cvs commit: jakarta-tomcat-connectors/ajp/proxy proxy_http.c

mturk   2004/08/06 04:44:45

  Modified:ajp/proxy proxy_http.c
  Log:
  We have a proxy-http using connection pool ;)
  Need some thorough testing.
  
  Revision  ChangesPath
  1.2   +82 -284   jakarta-tomcat-connectors/ajp/proxy/proxy_http.c
  
  Index: proxy_http.c
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/ajp/proxy/proxy_http.c,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- proxy_http.c  3 Aug 2004 10:01:18 -   1.1
  +++ proxy_http.c  6 Aug 2004 11:44:45 -   1.2
  @@ -20,20 +20,13 @@
   module AP_MODULE_DECLARE_DATA proxy_http_module;
   
   int ap_proxy_http_canon(request_rec *r, char *url);
  -int ap_proxy_http_handler(request_rec *r, proxy_server_conf *conf,
  +int ap_proxy_http_handler(request_rec *r, proxy_worker *worker,
  +  proxy_server_conf *conf,
 char *url, const char *proxyname, 
 apr_port_t proxyport);
   
  -typedef struct {
  -const char *name;
  -apr_port_t  port;
  -apr_sockaddr_t *addr;
  -apr_socket_t   *sock;
  -int close;
  -} proxy_http_conn_t;
  -
  -static apr_status_t ap_proxy_http_cleanup(request_rec *r,
  -  proxy_http_conn_t *p_conn,
  +static apr_status_t ap_proxy_http_cleanup(const char *scheme,
  +  request_rec *r,
 proxy_conn_rec *backend);
   
   /*
  @@ -146,7 +139,8 @@
   const char* domainp ;
   const char* pathe = NULL;
   const char* domaine = NULL;
  -size_t l1, l2, i, poffs = 0, doffs = 0 ;
  +size_t l1, l2, poffs = 0, doffs = 0 ;
  +int i;
   int ddiff = 0 ;
   int pdiff = 0 ;
   char* ret ;
  @@ -248,230 +242,8 @@
   }
   
   static
  -apr_status_t ap_proxy_http_determine_connection(apr_pool_t *p, request_rec *r,
  -proxy_http_conn_t *p_conn,
  -conn_rec *c,
  -proxy_server_conf *conf,
  -apr_uri_t *uri,
  -char **url,
  -const char *proxyname,
  -apr_port_t proxyport,
  -char *server_portstr,
  -int server_portstr_size) {
  -int server_port;
  -apr_status_t err;
  -apr_sockaddr_t *uri_addr;
  -/*
  - * Break up the URL to determine the host to connect to
  - */
  -
  -/* we break the URL into host, port, uri */
  -if (APR_SUCCESS != apr_uri_parse(p, *url, uri)) {
  -return ap_proxyerror(r, HTTP_BAD_REQUEST,
  - apr_pstrcat(p,"URI cannot be parsed: ", *url,
  - NULL));
  -}
  -if (!uri->port) {
  -uri->port = apr_uri_port_of_scheme(uri->scheme);
  -}
  -
  -ap_log_error(APLOG_MARK, APLOG_DEBUG, 0, r->server,
  - "proxy: HTTP connecting %s to %s:%d", *url, uri->hostname,
  - uri->port);
  -
  -/* do a DNS lookup for the destination host */
  -/* see memory note above */
  -err = apr_sockaddr_info_get(&uri_addr, apr_pstrdup(c->pool, uri->hostname),
  -APR_UNSPEC, uri->port, 0, c->pool);
  -
  -/* allocate these out of the connection pool - the check on
  - * r->connection->id makes sure that this string does not get accessed
  - * past the connection lifetime */
  -/* are we connecting directly, or via a proxy? */
  -if (proxyname) {
  -p_conn->name = apr_pstrdup(c->pool, proxyname);
  -p_conn->port = proxyport;
  -/* see memory note above */
  -err = apr_sockaddr_info_get(&p_conn->addr, p_conn->name, APR_UNSPEC,
  -p_conn->port, 0, c->pool);
  -} else {
  -p_conn->name = apr_pstrdup(c->pool, uri->hostname);
  -p_conn->port = uri->port;
  -p_conn->addr = uri_addr;
  -*url = apr_pstrcat(p, uri->path, uri->query ? "?" : "",
  -   uri->query ? uri->query : "",
  -   uri->fragment ? "#" : "",
  -   uri->fragment ? uri->fragment : "", NULL);
  -}
  -
  -if (err != APR_SUCCESS) {
  -return ap_proxyerror(r, HTTP_BAD_GATEWAY,
  - apr_pstrcat(p, "DNS lookup failure for: ",
  - p_conn->name, NULL));
  -}
  -
  -/* Get the server port for the Via headers */
  -{
  -server_port = ap_get_server_port(r);
  -if (ap_is_default_

cvs commit: jakarta-tomcat-connectors/ajp/proxy proxy_util.c

mturk   2004/08/06 04:43:53

  Modified:ajp/proxy proxy_util.c
  Log:
  A lot :) Make the things work...
  
  Revision  ChangesPath
  1.19  +70 -40jakarta-tomcat-connectors/ajp/proxy/proxy_util.c
  
  Index: proxy_util.c
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/ajp/proxy/proxy_util.c,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- proxy_util.c  6 Aug 2004 05:42:14 -   1.18
  +++ proxy_util.c  6 Aug 2004 11:43:53 -   1.19
  @@ -996,7 +996,7 @@
   char *c, *uri = apr_pstrdup(p, url);
   int i;
   
  -c = strchr(url, ':');   
  +c = strchr(uri, ':');   
   if (c == NULL || c[1] != '/' || c[2] != '/' || c[3] == '\0')
  return NULL;
   /* remove path from uri */
  @@ -1020,7 +1020,7 @@
   int port;
   apr_status_t rc = 0;
   
  -c = strchr(url, ':');   
  +c = strchr(uri, ':');   
   if (c == NULL || c[1] != '/' || c[2] != '/' || c[3] == '\0')
  return "Bad syntax for a remote proxy server";
   /* remove path from uri */
  @@ -1032,14 +1032,12 @@
   if (sscanf(q + 1, "%u", &port) != 1 || port > 65535) {
   return "Bad syntax for a remote proxy server (bad port number)";
   }
  -*q = '\0';
   }
   else
   port = -1;
   ap_str_tolower(uri);
   *balancer = apr_array_push(conf->balancers);
  -(*balancer)->name = apr_pstrdup(p, uri);
  -*c = '\0';
  +(*balancer)->name = uri;
   (*balancer)->workers = apr_array_make(p, 5, sizeof(proxy_runtime_worker));
   /* XXX Is this a right place to create mutex */
   #if APR_HAS_THREADS
  @@ -1061,21 +1059,31 @@
   char *c, *uri = apr_pstrdup(p, url);
   int i;
   
  -c = strchr(url, ':');   
  +c = strchr(uri, ':');   
   if (c == NULL || c[1] != '/' || c[2] != '/' || c[3] == '\0')
  return NULL;
   /* remove path from uri */
   if ((c = strchr(c + 3, '/')))
   *c = '\0';
  +
   worker = (proxy_worker *)conf->workers->elts;
   for (i = 0; i < conf->workers->nelts; i++) {
  -if (strcasecmp(worker->name, uri) == 0)
  +if (strcasecmp(worker->name, uri) == 0) {
   return worker;
  +}
   worker++;
   }
   return NULL;
   }
   
  +static apr_status_t conn_pool_cleanup(void *thepool)
  +{
  +proxy_conn_pool *cp = (proxy_conn_pool *)thepool;
  +/* Close the socket */
  +cp->addr = NULL;
  +return APR_SUCCESS;
  +}
  +
   static void init_conn_pool(apr_pool_t *p, proxy_worker *worker)
   {
   apr_pool_t *pool;
  @@ -1091,29 +1099,12 @@
* proxy_conn_pool is permanently attached to the worker. 
*/
   cp = (proxy_conn_pool *)apr_pcalloc(p, sizeof(proxy_conn_pool));
  -cp->pool = pool;
  -#if APR_HAS_THREADS
  -{
  -int mpm_threads;
  -ap_mpm_query(AP_MPMQ_MAX_THREADS, &mpm_threads);
  -if (mpm_threads > 1) {
  -/* Set hard max to no more then mpm_threads */
  -if (worker->hmax == 0 || worker->hmax > mpm_threads)
  - worker->hmax = mpm_threads;
  -if (worker->smax == 0 || worker->smax > worker->hmax)
  - worker->smax = worker->hmax;
  -/* Set min to be lower then smax */
  -if (worker->min > worker->smax)
  - worker->min = worker->smax; 
  -}
  -else {
  -/* This will supress the apr_reslist creation */
  -worker->min = worker->smax = worker->hmax = 0;
  -}
  -}
  -#endif
  -
  +cp->pool = pool;
   worker->cp = cp;
  +apr_pool_cleanup_register(p, (void *)cp,
  +  conn_pool_cleanup,
  +  apr_pool_cleanup_null);  
  +
   }
   
   PROXY_DECLARE(const char *) ap_proxy_add_worker(proxy_worker **worker,
  @@ -1136,13 +1127,13 @@
   if (sscanf(q + 1, "%u", &port) != 1 || port > 65535) {
   return "Bad syntax for a remote proxy server (bad port number)";
   }
  -*q = '\0';
   }
   else
   port = -1;
   ap_str_tolower(uri);
   *worker = apr_array_push(conf->workers);
  -(*worker)->name = apr_pstrdup(p, url);
  +memset(*worker, 0, sizeof(proxy_worker));
  +(*worker)->name = (*worker)->hostname = apr_pstrdup(p, uri);
   *c = '\0';
   (*worker)->scheme = uri;
   if (port == -1)
  @@ -1321,6 +1312,7 @@
   if (conn->sock)
   apr_socket_close(conn->sock);
   conn->sock = NULL;
  +conn->pool = NULL;
   return APR_SUCCESS;
   }
   
  @@ -1332,7 +1324,6 @@
   if (conn->sock)
   apr_socket_close(conn->sock);
   conn->sock = NULL;
  -
   }
   conn->connection = NULL;
   ap_proxy_release_connection(NULL, conn, NULL);
  @@ -1359,7 +1350,8 @@
   *reso

cvs commit: jakarta-tomcat-connectors/ajp/proxy mod_proxy.c

mturk   2004/08/06 04:42:40

  Modified:ajp/proxy mod_proxy.c
  Log:
  Change the scheme handler hook to include worker.
  
  Revision  ChangesPath
  1.29  +10 -9 jakarta-tomcat-connectors/ajp/proxy/mod_proxy.c
  
  Index: mod_proxy.c
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/ajp/proxy/mod_proxy.c,v
  retrieving revision 1.28
  retrieving revision 1.29
  diff -u -r1.28 -r1.29
  --- mod_proxy.c   5 Aug 2004 17:46:58 -   1.28
  +++ mod_proxy.c   6 Aug 2004 11:42:39 -   1.29
  @@ -619,7 +619,7 @@
   /* handle the scheme */
   ap_log_error(APLOG_MARK, APLOG_DEBUG, 0, r->server,
"Trying to run scheme_handler against proxy");
  -access_status = proxy_run_scheme_handler(r, conf, url, 
ents[i].hostname, ents[i].port);
  +access_status = proxy_run_scheme_handler(r, worker, conf, url, 
ents[i].hostname, ents[i].port);
   
   /* an error or success */
   if (access_status != DECLINED && access_status != HTTP_BAD_GATEWAY) 
{
  @@ -638,7 +638,7 @@
   /* handle the scheme */
   ap_log_error(APLOG_MARK, APLOG_DEBUG, 0, r->server,
"Trying to run scheme_handler");
  -access_status = proxy_run_scheme_handler(r, conf, url, NULL, 0);
  +access_status = proxy_run_scheme_handler(r, worker, conf, url, NULL, 0);
   if (DECLINED == access_status) {
   ap_log_error(APLOG_MARK, APLOG_WARNING, 0, r->server,
   "proxy: No protocol handler was valid for the URL %s. "
  @@ -892,7 +892,7 @@
   }
   }
   else {
  -proxy_worker *worker = ap_proxy_get_worker(cmd->pool, conf, r);
  +proxy_worker *worker = ap_proxy_get_worker(cmd->temp_pool, conf, r);
   if (!worker) {
   const char *err = ap_proxy_add_worker(&worker, cmd->pool, conf, r);
   if (err)
  @@ -1552,13 +1552,14 @@
   )
   
   APR_IMPLEMENT_EXTERNAL_HOOK_RUN_FIRST(proxy, PROXY, int, scheme_handler, 
  - (request_rec *r, proxy_server_conf *conf, 
  - char *url, const char *proxyhost, 
  - apr_port_t proxyport),(r,conf,url,
  - proxyhost,proxyport),DECLINED)
  + (request_rec *r, proxy_worker *worker,
  +  proxy_server_conf *conf, 
  +  char *url, const char *proxyhost, 
  +  apr_port_t proxyport),(r,worker,conf,
  +  url,proxyhost,proxyport),DECLINED)
   APR_IMPLEMENT_EXTERNAL_HOOK_RUN_FIRST(proxy, PROXY, int, canon_handler, 
  - (request_rec *r, char *url),(r,
  - url),DECLINED)
  +  (request_rec *r, char *url),(r,
  +  url),DECLINED)
   APR_IMPLEMENT_EXTERNAL_HOOK_RUN_FIRST(proxy, PROXY, int, pre_request, (
 proxy_worker **worker,
 proxy_balancer **balancer,
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-tomcat-connectors/ajp/proxy mod_proxy.h

mturk   2004/08/06 04:41:40

  Modified:ajp/proxy mod_proxy.h
  Log:
  Change the scheme handler hook to include worker.
  We will probably need the balancer too, but that can wait for now.
  
  Revision  ChangesPath
  1.25  +5 -5  jakarta-tomcat-connectors/ajp/proxy/mod_proxy.h
  
  Index: mod_proxy.h
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/ajp/proxy/mod_proxy.h,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- mod_proxy.h   6 Aug 2004 05:42:14 -   1.24
  +++ mod_proxy.h   6 Aug 2004 11:41:40 -   1.25
  @@ -294,7 +294,7 @@
   APR_OPTIONAL_HOOK(proxy,name,fn,pre,succ,order)
   
   APR_DECLARE_EXTERNAL_HOOK(proxy, PROXY, int, scheme_handler, (request_rec *r, 
  -  proxy_server_conf *conf, char *url, 
  +  proxy_worker *worker, proxy_server_conf *conf, char *url, 
 const char *proxyhost, apr_port_t proxyport))
   APR_DECLARE_EXTERNAL_HOOK(proxy, PROXY, int, canon_handler, (request_rec *r, 
 char *url))
  @@ -358,14 +358,14 @@
   PROXY_DECLARE(const char *) ap_proxy_add_balancer(proxy_balancer **balancer, 
apr_pool_t *p, proxy_server_conf *conf, const char *url);
   PROXY_DECLARE(void) ap_proxy_add_worker_to_balancer(proxy_balancer *balancer, 
proxy_worker *worker);
   PROXY_DECLARE(int) ap_proxy_pre_request(proxy_worker **worker, proxy_balancer 
**balancer, request_rec *r, proxy_server_conf *conf, char **url);
  -PROXY_DECLARE(apr_status_t) ap_proxy_determine_connection(apr_pool_t *p, 
request_rec *r, proxy_server_conf *conf, proxy_worker *worker, proxy_conn_rec *conn,
  -  apr_pool_t *ppool, 
apr_uri_t *uri, char **url, const char *proxyname, apr_port_t proxyport,
  -  char *server_portstr, int 
server_portstr_size);
  +PROXY_DECLARE(int) ap_proxy_determine_connection(apr_pool_t *p, request_rec *r, 
proxy_server_conf *conf, proxy_worker *worker, proxy_conn_rec *conn,
  + apr_pool_t *ppool, apr_uri_t *uri, 
char **url, const char *proxyname, apr_port_t proxyport,
  + char *server_portstr, int 
server_portstr_size);
   PROXY_DECLARE(int) ap_proxy_acquire_connection(const char *proxy_function, 
proxy_conn_rec **conn, proxy_worker *worker, server_rec *s);
   PROXY_DECLARE(int) ap_proxy_release_connection(const char *proxy_function, 
proxy_conn_rec *conn, server_rec *s);
   PROXY_DECLARE(apr_status_t) ap_proxy_close_connection(proxy_conn_rec *conn);
   PROXY_DECLARE(int) ap_proxy_connect_backend(const char *proxy_function, 
proxy_conn_rec *conn, proxy_worker *worker, server_rec *s);
  -PROXY_DECLARE(int) ap_proxy_connection_create(const char *proxy_function, 
proxy_conn_rec *conn, int close_on_recycle, conn_rec *c, server_rec *s);
  +PROXY_DECLARE(int) ap_proxy_connection_create(const char *proxy_function, 
proxy_conn_rec *conn, conn_rec *c, server_rec *s);
   
   /* For proxy_util */
   extern module PROXY_DECLARE_DATA proxy_module;
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Robert Knittel/Chemetall GmbH/Chemetall ist außer Haus. Robert Knittel/Chemetall GmbH/Chemetall is absent.

2004-08-06 Thread robert . knittel

Ich werde ab  06.08.2004 nicht im Büro sein. Ich kehre zurück am
01.09.2004.

Ich bin vom 06.08.2004 - 31.08.2004 nicht im Büro
Ich werde Ihre Nachricht nach meiner Rückkehr am 01.09.2004 beantworten.
Während dieser Zeit werde ich durch meine Kollegin, Frau Petra Brendel,
vertreten.

Sie ist erreichbar unter
Telefon: 0049 - 69 - 7165 2349
Fax:   0049 - 69 - 7165 2936
e-mail:   [EMAIL PROTECTED]

I am out of office from 06.08.2004 till 31.08.2004
I will answer your e-mail on my return on 01.09.2004
During this time my colleague, Mrs. Petra Brendel, will support me and
answer my e-mails

You can contact her under
phone:  +49 69 7165 2349
Fax:  +49 69 7165 2936
e-mail:  [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru

Рассылка: Mnogo.ru

Описание:

Основные рассылки сервера Mnogo.ru

Количество подписавшихся: 23

Периодичность: 



Для того, чтобы подписаться, отправьте письмо на адрес [EMAIL PROTECTED] с указанием в 
теле письма команды subscribe 
 




Rassylka: Mnogo.ru

Opisanie:

Osnovnye rassylki servera Mnogo.ru

Kolichestvo podpisavshixsya: 23

Periodichnost': 



Dlya togo, chtoby podpisat'sya, otprav'te pis'mo na adres [EMAIL PROTECTED] s 
ukazaniem v tele pis'ma komandy subscribe 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru

Рассылка: Mnogo.ru

Описание:

Основные рассылки сервера Mnogo.ru

Количество подписавшихся: 23

Периодичность: 



Для того, чтобы подписаться, отправьте письмо на адрес [EMAIL PROTECTED] с указанием в 
теле письма команды subscribe 
 




Rassylka: Mnogo.ru

Opisanie:

Osnovnye rassylki servera Mnogo.ru

Kolichestvo podpisavshixsya: 23

Periodichnost': 



Dlya togo, chtoby podpisat'sya, otprav'te pis'mo na adres [EMAIL PROTECTED] s 
ukazaniem v tele pis'ma komandy subscribe 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru

Рассылка: Mnogo.ru

Описание:

Основные рассылки сервера Mnogo.ru

Количество подписавшихся: 23

Периодичность: 



Для того, чтобы подписаться, отправьте письмо на адрес [EMAIL PROTECTED] с указанием в 
теле письма команды subscribe 
 




Rassylka: Mnogo.ru

Opisanie:

Osnovnye rassylki servera Mnogo.ru

Kolichestvo podpisavshixsya: 23

Periodichnost': 



Dlya togo, chtoby podpisat'sya, otprav'te pis'mo na adres [EMAIL PROTECTED] s 
ukazaniem v tele pis'ma komandy subscribe 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru

Рассылка: Mnogo.ru

Описание:

Основные рассылки сервера Mnogo.ru

Количество подписавшихся: 23

Периодичность: 



Для того, чтобы подписаться, отправьте письмо на адрес [EMAIL PROTECTED] с указанием в 
теле письма команды subscribe 
 




Rassylka: Mnogo.ru

Opisanie:

Osnovnye rassylki servera Mnogo.ru

Kolichestvo podpisavshixsya: 23

Periodichnost': 



Dlya togo, chtoby podpisat'sya, otprav'te pis'mo na adres [EMAIL PROTECTED] s 
ukazaniem v tele pis'ma komandy subscribe 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru

Рассылка: Mnogo.ru

Описание:

Основные рассылки сервера Mnogo.ru

Количество подписавшихся: 23

Периодичность: 



Для того, чтобы подписаться, отправьте письмо на адрес [EMAIL PROTECTED] с указанием в 
теле письма команды subscribe 
 




Rassylka: Mnogo.ru

Opisanie:

Osnovnye rassylki servera Mnogo.ru

Kolichestvo podpisavshixsya: 23

Periodichnost': 



Dlya togo, chtoby podpisat'sya, otprav'te pis'mo na adres [EMAIL PROTECTED] s 
ukazaniem v tele pis'ma komandy subscribe 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru

Рассылка: Mnogo.ru

Описание:

Основные рассылки сервера Mnogo.ru

Количество подписавшихся: 23

Периодичность: 



Для того, чтобы подписаться, отправьте письмо на адрес [EMAIL PROTECTED] с указанием в 
теле письма команды subscribe 
 




Rassylka: Mnogo.ru

Opisanie:

Osnovnye rassylki servera Mnogo.ru

Kolichestvo podpisavshixsya: 23

Periodichnost': 



Dlya togo, chtoby podpisat'sya, otprav'te pis'mo na adres [EMAIL PROTECTED] s 
ukazaniem v tele pis'ma komandy subscribe 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru

Рассылка: Mnogo.ru

Описание:

Основные рассылки сервера Mnogo.ru

Количество подписавшихся: 23

Периодичность: 



Для того, чтобы подписаться, отправьте письмо на адрес [EMAIL PROTECTED] с указанием в 
теле письма команды subscribe 
 




Rassylka: Mnogo.ru

Opisanie:

Osnovnye rassylki servera Mnogo.ru

Kolichestvo podpisavshixsya: 23

Periodichnost': 



Dlya togo, chtoby podpisat'sya, otprav'te pis'mo na adres [EMAIL PROTECTED] s 
ukazaniem v tele pis'ma komandy subscribe 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru

Рассылка: Mnogo.ru

Описание:

Основные рассылки сервера Mnogo.ru

Количество подписавшихся: 23

Периодичность: 



Для того, чтобы подписаться, отправьте письмо на адрес [EMAIL PROTECTED] с указанием в 
теле письма команды subscribe 
 




Rassylka: Mnogo.ru

Opisanie:

Osnovnye rassylki servera Mnogo.ru

Kolichestvo podpisavshixsya: 23

Periodichnost': 



Dlya togo, chtoby podpisat'sya, otprav'te pis'mo na adres [EMAIL PROTECTED] s 
ukazaniem v tele pis'ma komandy subscribe 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru

Рассылка: Mnogo.ru

Описание:

Основные рассылки сервера Mnogo.ru

Количество подписавшихся: 23

Периодичность: 



Для того, чтобы подписаться, отправьте письмо на адрес [EMAIL PROTECTED] с указанием в 
теле письма команды subscribe 
 




Rassylka: Mnogo.ru

Opisanie:

Osnovnye rassylki servera Mnogo.ru

Kolichestvo podpisavshixsya: 23

Periodichnost': 



Dlya togo, chtoby podpisat'sya, otprav'te pis'mo na adres [EMAIL PROTECTED] s 
ukazaniem v tele pis'ma komandy subscribe 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru

Рассылка: Mnogo.ru

Описание:

Основные рассылки сервера Mnogo.ru

Количество подписавшихся: 23

Периодичность: 



Для того, чтобы подписаться, отправьте письмо на адрес [EMAIL PROTECTED] с указанием в 
теле письма команды subscribe 
 




Rassylka: Mnogo.ru

Opisanie:

Osnovnye rassylki servera Mnogo.ru

Kolichestvo podpisavshixsya: 23

Periodichnost': 



Dlya togo, chtoby podpisat'sya, otprav'te pis'mo na adres [EMAIL PROTECTED] s 
ukazaniem v tele pis'ma komandy subscribe 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru

Рассылка: Mnogo.ru

Описание:

Основные рассылки сервера Mnogo.ru

Количество подписавшихся: 23

Периодичность: 



Для того, чтобы подписаться, отправьте письмо на адрес [EMAIL PROTECTED] с указанием в 
теле письма команды subscribe 
 




Rassylka: Mnogo.ru

Opisanie:

Osnovnye rassylki servera Mnogo.ru

Kolichestvo podpisavshixsya: 23

Periodichnost': 



Dlya togo, chtoby podpisat'sya, otprav'te pis'mo na adres [EMAIL PROTECTED] s 
ukazaniem v tele pis'ma komandy subscribe 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru





Список команд нашей службы рассылки



Подтверждение регистрации в рассылках:

CONFIRM [EMAIL PROTECTED] password

пример: CONFIRM [EMAIL PROTECTED] 12ndjk45  



Подписка на рассылку:

SUBSCRIBE list.code

пример: SUBSCRIBE vf.news



Отписка от рассылки:

UNSUBSCRIBE list.code

или

UNSUBSCRIBE [EMAIL PROTECTED] list.code

пример: UNSUBSCRIBE vf.news

пример: UNSUBSCRIBE *   (отказ от всех рассылок)

пример: UNSUBSCRIBE [EMAIL PROTECTED] vf.news



Приостановление получения рассылок:

PAUSE  



Возобновление получения рассылок:

UNPAUSE 



Получение краткого списка рассылок (без описания - только названия):

LIST



Получение подробной информации (описание, статистика):

INFO list.code

пример: INFO vf.news



Получение списка рассылок, на которые вы подписаны:

WHICH



Письма с командами должны быть адресованы на адрес [EMAIL PROTECTED]

Сами команды пишутся в теле письма. Если вы даете одновременно несколько команд в 
одном письме, то каждую команду начинайте с новой строки.

Не забывайте, что все функции управления рассылками доступны и через веб-интерфейс по 
адресу http://list.mnogo.ru/






Spisok komand nashej sluzhby rassylki



Podtverzhdenie registracii v rassylkax:

CONFIRM [EMAIL PROTECTED] password

primer: CONFIRM [EMAIL PROTECTED] 12ndjk45  



Podpiska na rassylku:

SUBSCRIBE list.code

primer: SUBSCRIBE vf.news



Otpiska ot rassylki:

UNSUBSCRIBE list.code

ili

UNSUBSCRIBE [EMAIL PROTECTED] list.code

primer: UNSUBSCRIBE vf.news

primer: UNSUBSCRIBE *   (otkaz ot vsex rassylok)

primer: UNSUBSCRIBE [EMAIL PROTECTED] vf.news



Priostanovlenie polucheniya rassylok:

PAUSE  



Vozobnovlenie polucheniya rassylok:

UNPAUSE 



Poluchenie kratkogo spiska rassylok (bez opisaniya - tol'ko nazvaniya):

LIST



Poluchenie podrobnoj informacii (opisanie, statistika):

INFO list.code

primer: INFO vf.news



Poluchenie spiska rassylok, na kotorye vy podpisany:

WHICH



Pis'ma s komandami dolzhny byt' adresovany na adres [EMAIL PROTECTED]

Sami komandy pishutsya v tele pis'ma. Esli vy daete odnovremenno neskol'ko komand v 
odnom pis'me, to kazhduyu komandu nachinajte s novoj stroki.

Ne zabyvajte, chto vse funkcii upravleniya rassylkami dostupny i cherez veb-interfejs 
po adresu http://list.mnogo.ru/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru

Рассылка: Mnogo.ru

Описание:

Основные рассылки сервера Mnogo.ru

Количество подписавшихся: 23

Периодичность: 



Для того, чтобы подписаться, отправьте письмо на адрес [EMAIL PROTECTED] с указанием в 
теле письма команды subscribe 
 




Rassylka: Mnogo.ru

Opisanie:

Osnovnye rassylki servera Mnogo.ru

Kolichestvo podpisavshixsya: 23

Periodichnost': 



Dlya togo, chtoby podpisat'sya, otprav'te pis'mo na adres [EMAIL PROTECTED] s 
ukazaniem v tele pis'ma komandy subscribe 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru

Рассылка: Mnogo.ru

Описание:

Основные рассылки сервера Mnogo.ru

Количество подписавшихся: 23

Периодичность: 



Для того, чтобы подписаться, отправьте письмо на адрес [EMAIL PROTECTED] с указанием в 
теле письма команды subscribe 
 




Rassylka: Mnogo.ru

Opisanie:

Osnovnye rassylki servera Mnogo.ru

Kolichestvo podpisavshixsya: 23

Periodichnost': 



Dlya togo, chtoby podpisat'sya, otprav'te pis'mo na adres [EMAIL PROTECTED] s 
ukazaniem v tele pis'ma komandy subscribe 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru

Рассылка: Mnogo.ru

Описание:

Основные рассылки сервера Mnogo.ru

Количество подписавшихся: 23

Периодичность: 



Для того, чтобы подписаться, отправьте письмо на адрес [EMAIL PROTECTED] с указанием в 
теле письма команды subscribe 
 




Rassylka: Mnogo.ru

Opisanie:

Osnovnye rassylki servera Mnogo.ru

Kolichestvo podpisavshixsya: 23

Periodichnost': 



Dlya togo, chtoby podpisat'sya, otprav'te pis'mo na adres [EMAIL PROTECTED] s 
ukazaniem v tele pis'ma komandy subscribe 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru

Рассылка: Mnogo.ru

Описание:

Основные рассылки сервера Mnogo.ru

Количество подписавшихся: 23

Периодичность: 



Для того, чтобы подписаться, отправьте письмо на адрес [EMAIL PROTECTED] с указанием в 
теле письма команды subscribe 
 




Rassylka: Mnogo.ru

Opisanie:

Osnovnye rassylki servera Mnogo.ru

Kolichestvo podpisavshixsya: 23

Periodichnost': 



Dlya togo, chtoby podpisat'sya, otprav'te pis'mo na adres [EMAIL PROTECTED] s 
ukazaniem v tele pis'ma komandy subscribe 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru

Рассылка: Mnogo.ru

Описание:

Основные рассылки сервера Mnogo.ru

Количество подписавшихся: 23

Периодичность: 



Для того, чтобы подписаться, отправьте письмо на адрес [EMAIL PROTECTED] с указанием в 
теле письма команды subscribe 
 




Rassylka: Mnogo.ru

Opisanie:

Osnovnye rassylki servera Mnogo.ru

Kolichestvo podpisavshixsya: 23

Periodichnost': 



Dlya togo, chtoby podpisat'sya, otprav'te pis'mo na adres [EMAIL PROTECTED] s 
ukazaniem v tele pis'ma komandy subscribe 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 30510] New: - Tomcat shutdown does not work properly when started as daemon

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30510

Tomcat  shutdown does not work properly when started as daemon

   Summary: Tomcat  shutdown does not work properly when started as
daemon
   Product: Tomcat 5
   Version: 5.0.27
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: Critical
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Hi,

we are planning to use tomcat 5.0.27 as a servlet container and web server for
our web application on our Linux servers (SuSE 7.2). Startup of tomcat5 as a
daemon works fine if there is no tomcat running. Unfortunaltely, we experience
that the shutdown of a tomcat server started as a daemon using the jsvc
bootstrap and the Tomcat5.sh script shipped with tomcat 5.0.27 does not work.
The following is written to the log file $CATALINA_HOME/logs/catalina.out:

jsvc.exec error: Service exit with a return value of 143

In addition, the file /var/run/jsvc.pid is still present.

If you now try to restart the tomcat server using the daemon start script, the
startup fails with a heap error in the virtual machine causing a sigsegv (signal
11) in /lib/libc.so.6). See cut-out of the log file below for more detailed
information. I hope anybody can help as this problem really prevents us from
using tomcat!


 cut-out from catalina.out --

06-Aug-2004 17:13:43 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
06-Aug-2004 17:13:43 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2351 ms
06-Aug-2004 17:13:44 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
06-Aug-2004 17:13:44 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.0.27

06-Aug-2004 17:10:50 org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
06-Aug-2004 17:10:50 org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment ( non-jmx )
06-Aug-2004 17:10:50 org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL
file:/opt/tomcat/jakarta-tomcat-5.0.27/conf/Catalina/localhost/admin.xml
06-Aug-2004 17:10:51 org.apache.struts.util.PropertyMessageResources 
INFO: Initializing, config='org.apache.struts.util.LocalStrings', returnNull=true
06-Aug-2004 17:10:51 org.apache.struts.util.PropertyMessageResources 
INFO: Initializing, config='org.apache.struts.action.ActionResources',
returnNull=true
06-Aug-2004 17:10:52 org.apache.struts.util.PropertyMessageResources 
INFO: Initializing, config='org.apache.webapp.admin.ApplicationResources',
returnNull=true
06-Aug-2004 17:10:54 org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL
file:/opt/tomcat/jakarta-tomcat-5.0.27/conf/Catalina/localhost/balancer.xml
06-Aug-2004 17:10:54 org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL
file:/opt/tomcat/jakarta-tomcat-5.0.27/conf/Catalina/localhost/manager.xml
06-Aug-2004 17:10:54 org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path  from URL
file:/opt/tomcat/jakarta-tomcat-5.0.27/webapps/ROOT
06-Aug-2004 17:10:54 org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /jsp-examples from URL
file:/opt/tomcat/jakarta-tomcat-5.0.27/webapps/jsp-ex
06-Aug-2004 17:10:55 org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /servlets-examples from URL
file:/opt/tomcat/jakarta-tomcat-5.0.27/webapps/s
06-Aug-2004 17:10:55 org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tomcat-docs from URL
file:/opt/tomcat/jakarta-tomcat-5.0.27/webapps/tomcat-
06-Aug-2004 17:10:55 org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /webdav from URL
file:/opt/tomcat/jakarta-tomcat-5.0.27/webapps/webdav
06-Aug-2004 17:10:55 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
06-Aug-2004 17:10:55 org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
06-Aug-2004 17:10:55 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=1/40 
config=/opt/tomcat/jakarta-tomcat-5.0.27/conf/jk2.properties
06-Aug-2004 17:10:55 org.apache.catalina.startup.Catalina start
INFO: Server startup in 5354 ms
jsvc.exec error: Service exit with a return value of 143
06-A

Robert Knittel/Chemetall GmbH/Chemetall ist außer Haus. Robert Knittel/Chemetall GmbH/Chemetall is absent.

2004-08-06 Thread robert . knittel

Ich werde ab  06.08.2004 nicht im Büro sein. Ich kehre zurück am
01.09.2004.

Ich bin vom 06.08.2004 - 31.08.2004 nicht im Büro
Ich werde Ihre Nachricht nach meiner Rückkehr am 01.09.2004 beantworten.
Während dieser Zeit werde ich durch meine Kollegin, Frau Petra Brendel,
vertreten.

Sie ist erreichbar unter
Telefon: 0049 - 69 - 7165 2349
Fax:   0049 - 69 - 7165 2936
e-mail:   [EMAIL PROTECTED]

I am out of office from 06.08.2004 till 31.08.2004
I will answer your e-mail on my return on 01.09.2004
During this time my colleague, Mrs. Petra Brendel, will support me and
answer my e-mails

You can contact her under
phone:  +49 69 7165 2349
Fax:  +49 69 7165 2936
e-mail:  [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

òÁÓÓÙÌËÉ mnogo.ru