Tomcat Manager deletion

2006-12-07 Thread Remy.Coqueugniot
Hi tomcat users,

On a win32 environment, I've installed many Tomcat instances for one
Tomcat home.
Ex:
-Service 1:
set CATALINA_HOME=C:\tomcat55
set CATALINA_BASE=C:\tomcat_appliA

-Service 2:
set CATALINA_HOME=C:\tomcat55
set CATALINA_BASE=C:\tomcat_appliB

For each of those instances, I've deployed manager with the following
context : 
 Context docBase=${catalina.home}/server/webapps/manager
privileged=true/Context

Each time, I have to restart my win32 service, the manager webapp is
deleted ?!?

Any ideas ?

Thanks,

Remy C















---
Cette communication (y compris les pieces jointes) est reservee a l'usage 
exclusif du destinataire (des destinataires) et peut contenir des informations 
privilegiees, confidentielles, exemptees de divulgation selon la loi ou 
protegees par les droits d'auteur. Si vous n'etes pas un destinataire, toute 
utilisation, divulgation, distribution, reproduction, examen ou copie (totale 
ou partielle) est non-autorisee et peut etre illegale. Tout message 
electronique est susceptible d'alteration et son integrite ne peut etre 
assuree. Sanofi Pasteur decline toute responsabilite au titre de ce message 
s'il a ete modifie ou falsifie. Si vous n'etes pas destinataire de ce message, 
merci de le detruire immediatement et d'avertir l'expediteur de l'erreur de 
distribution et de la destruction du message. Merci.
This transmission (including any attachments) is intended solely for the use of 
the addressee(s) and may contain confidential information including trade 
secrets which are privileged, confidential, exempt from disclosure under 
applicable law and/or subject to copyright. If you are not an intended 
recipient, any use, disclosure, distribution, reproduction, review or copying 
(either whole or partial) is unauthorized and may be unlawful. E-mails are 
susceptible to alteration and their integrity cannot be guaranteed.Sanofi 
Pasteur shall not be liable for this e-mail if modified or falsified. If you 
are not the intended recipient of this e-mail, please delete it immediately 
from your system and notify the sender of the wrong delivery and the mail 
deletion. Thank you.
**


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Memory leaks on webapp redeploy

2006-11-28 Thread Remy.Coqueugniot
 Is anyone running into issues with memory leaks occuring 
 whenever a webapp is redeployed? I've been having a lot of 
 problems with this. I think what's exacerbating the problem 
 is that I'm using Hibernate and JAX-WS which I have bundled 
 with my application which use a lot of memory.

Yes, we experience same problems with Tomcat 5.5.17 

We did a lot of tests and profiling instrumentations (Jprofiler powered) on 
many environments : Win32/Linux,  JDK1.4.2_12, JDL 1.5, Tomcat 5.5.17/5.5.20
Same problem: many redeployments (or reload) of a webapp throw an OutOfMemory 
for the PermGenspace. If you monitor your Jvm with Jvmstat tools you would see 
this non-heap memory never been released...

The problems seems to be located with Cglib classloaders referencing policy. 
There is a lot of topic on the Net, which may be interessing to read, but noone 
seems to have found a valuable solution. (Increasing the PermGenspace is NOT a 
reasonable solution)

The only way we found to fix it is to change the JVM. Indeed if we use the BEA 
Jrockit 1.4 JVM, the application can be deployed as many times you want...

Please give some news, if you find something useful

RC


 -Message d'origine-
 De : Jon Miller [mailto:[EMAIL PROTECTED] 
 Envoyé : mardi 28 novembre 2006 01:38
 À : Tomcat User List
 Objet : Memory leaks on webapp redeploy
 
 Hi all,
 
 
 I think I read in a FAQ that even using a singleton in your 
 app will cause memory leaks? Does anyone know if this is true?
 
 Jon
 
 
 -
 To start a new topic, e-mail: users@tomcat.apache.org To 
 unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
---
Cette communication (y compris les pieces jointes) est reservee a l'usage 
exclusif du destinataire (des destinataires) et peut contenir des informations 
privilegiees, confidentielles, exemptees de divulgation selon la loi ou 
protegees par les droits d'auteur. Si vous n'etes pas un destinataire, toute 
utilisation, divulgation, distribution, reproduction, examen ou copie (totale 
ou partielle) est non-autorisee et peut etre illegale. Tout message 
electronique est susceptible d'alteration et son integrite ne peut etre 
assuree. Sanofi Pasteur decline toute responsabilite au titre de ce message 
s'il a ete modifie ou falsifie. Si vous n'etes pas destinataire de ce message, 
merci de le detruire immediatement et d'avertir l'expediteur de l'erreur de 
distribution et de la destruction du message. Merci.
This transmission (including any attachments) is intended solely for the use of 
the addressee(s) and may contain confidential information including trade 
secrets which are privileged, confidential, exempt from disclosure under 
applicable law and/or subject to copyright. If you are not an intended 
recipient, any use, disclosure, distribution, reproduction, review or copying 
(either whole or partial) is unauthorized and may be unlawful. E-mails are 
susceptible to alteration and their integrity cannot be guaranteed.Sanofi 
Pasteur shall not be liable for this e-mail if modified or falsified. If you 
are not the intended recipient of this e-mail, please delete it immediately 
from your system and notify the sender of the wrong delivery and the mail 
deletion. Thank you.
**


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Memory leaks on webapp redeploy

2006-11-28 Thread Remy.Coqueugniot

  The problems seems to be located with Cglib classloaders 
 referencing 
  policy. There is a lot of topic on the Net, which may be 
 interessing 
  to read, but noone seems to have found a valuable solution. 
  (Increasing the PermGenspace is NOT a reasonable solution)

 That means, that hibernate apps will always generate OOM...

Not always. But some hibernate/cglib/tomcat uses seems to generate
classloader memory leak:
http://opensource.atlassian.com/confluence/spring/pages/viewpage.action?
pageId=2669

You can easily reproduce this behaviour.
Write a quite empty webapp with hibernate (so cglib too) which contains
just a JSP/servlet which do a dummy DBMS request (select sysdate from
dual) and print the result.
 -Deploy it 
 -access to your JSP/servlet
 -reload webapp
Write a Jmeter scenario that execute those 2 last steps.
Repeat it many times (10 times for a default heap sized JVM)
You will see your Permgenspace always growing and crash at the high
level (64MB default)


  The only way we found to fix it is to change the JVM. 
 Indeed if we use the BEA Jrockit 1.4 JVM, the application can 
 be deployed as many times you want...

 Great news! Do you know whether their JVM (1.5) is free to 
 download and use?
Yes it's free to download. For a commercial use you should check the
license.
But keep in mind, that may be a dangerous alternative. You don't know
yet what could append with Jrockit.
And the past releases don't tend to be stable as a sun one (to my
experiences)

Out solution is to install one instance of Tomcat per application :
reducing memory heap use, ...
And for each redeploy/reload we restart the tomcat service.
A Heavy but working solution 

RC

---
Cette communication (y compris les pieces jointes) est reservee a l'usage 
exclusif du destinataire (des destinataires) et peut contenir des informations 
privilegiees, confidentielles, exemptees de divulgation selon la loi ou 
protegees par les droits d'auteur. Si vous n'etes pas un destinataire, toute 
utilisation, divulgation, distribution, reproduction, examen ou copie (totale 
ou partielle) est non-autorisee et peut etre illegale. Tout message 
electronique est susceptible d'alteration et son integrite ne peut etre 
assuree. Sanofi Pasteur decline toute responsabilite au titre de ce message 
s'il a ete modifie ou falsifie. Si vous n'etes pas destinataire de ce message, 
merci de le detruire immediatement et d'avertir l'expediteur de l'erreur de 
distribution et de la destruction du message. Merci.
This transmission (including any attachments) is intended solely for the use of 
the addressee(s) and may contain confidential information including trade 
secrets which are privileged, confidential, exempt from disclosure under 
applicable law and/or subject to copyright. If you are not an intended 
recipient, any use, disclosure, distribution, reproduction, review or copying 
(either whole or partial) is unauthorized and may be unlawful. E-mails are 
susceptible to alteration and their integrity cannot be guaranteed.Sanofi 
Pasteur shall not be liable for this e-mail if modified or falsified. If you 
are not the intended recipient of this e-mail, please delete it immediately 
from your system and notify the sender of the wrong delivery and the mail 
deletion. Thank you.
**


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Memory leaks on webapp redeploy

2006-11-28 Thread Remy.Coqueugniot

 It's been a while since I profiled any of my apps, but that 
 used to be the case... after a few days in development of 
 auto-re-loading the webapps, we'd get an OOM. We could watch 
 the heap fill up with useless Class objects (for instance, 
 my.package.Class showed up 10 times after 9 restarts, and we 
 don't do anything crazy like keeping Class references around, 
 singletons, thread locals variables, static class data, etc.).

Same problem here. Reloading such a tiny webapp generates memory leaks
in the PermGenSpace (which is a non-heap space).
Some libraries (apparently cglib) kept some Classloaders references and
don't free them. This leads to an OOM : Out of PermgenSpace after some
reloads (or redeploy)
We have try to setup a cleaner ServletContextListener to force some
cleaning job (Introspector caches) on contextDestroyed event, but it
doesn't give any more results.

Profiling instrumentations gave us some informations about what is
loaded. But it's quite difficult to find the guilty source.

I'm very interested in the following of this issue.

RC

---
Cette communication (y compris les pieces jointes) est reservee a l'usage 
exclusif du destinataire (des destinataires) et peut contenir des informations 
privilegiees, confidentielles, exemptees de divulgation selon la loi ou 
protegees par les droits d'auteur. Si vous n'etes pas un destinataire, toute 
utilisation, divulgation, distribution, reproduction, examen ou copie (totale 
ou partielle) est non-autorisee et peut etre illegale. Tout message 
electronique est susceptible d'alteration et son integrite ne peut etre 
assuree. Sanofi Pasteur decline toute responsabilite au titre de ce message 
s'il a ete modifie ou falsifie. Si vous n'etes pas destinataire de ce message, 
merci de le detruire immediatement et d'avertir l'expediteur de l'erreur de 
distribution et de la destruction du message. Merci.
This transmission (including any attachments) is intended solely for the use of 
the addressee(s) and may contain confidential information including trade 
secrets which are privileged, confidential, exempt from disclosure under 
applicable law and/or subject to copyright. If you are not an intended 
recipient, any use, disclosure, distribution, reproduction, review or copying 
(either whole or partial) is unauthorized and may be unlawful. E-mails are 
susceptible to alteration and their integrity cannot be guaranteed.Sanofi 
Pasteur shall not be liable for this e-mail if modified or falsified. If you 
are not the intended recipient of this e-mail, please delete it immediately 
from your system and notify the sender of the wrong delivery and the mail 
deletion. Thank you.
**


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Memory leaks on webapp redeploy

2006-11-28 Thread Remy.Coqueugniot


http://wiki.apache.org/tomcat/OutOfMemory : Another link which deals
about OOM and singleton.

Have you ever tried to do some inspections with decent profiler
(OptimiseIt, Jprofiler, Yourkit, ...) ?

RC
---
Cette communication (y compris les pieces jointes) est reservee a l'usage 
exclusif du destinataire (des destinataires) et peut contenir des informations 
privilegiees, confidentielles, exemptees de divulgation selon la loi ou 
protegees par les droits d'auteur. Si vous n'etes pas un destinataire, toute 
utilisation, divulgation, distribution, reproduction, examen ou copie (totale 
ou partielle) est non-autorisee et peut etre illegale. Tout message 
electronique est susceptible d'alteration et son integrite ne peut etre 
assuree. Sanofi Pasteur decline toute responsabilite au titre de ce message 
s'il a ete modifie ou falsifie. Si vous n'etes pas destinataire de ce message, 
merci de le detruire immediatement et d'avertir l'expediteur de l'erreur de 
distribution et de la destruction du message. Merci.
This transmission (including any attachments) is intended solely for the use of 
the addressee(s) and may contain confidential information including trade 
secrets which are privileged, confidential, exempt from disclosure under 
applicable law and/or subject to copyright. If you are not an intended 
recipient, any use, disclosure, distribution, reproduction, review or copying 
(either whole or partial) is unauthorized and may be unlawful. E-mails are 
susceptible to alteration and their integrity cannot be guaranteed.Sanofi 
Pasteur shall not be liable for this e-mail if modified or falsified. If you 
are not the intended recipient of this e-mail, please delete it immediately 
from your system and notify the sender of the wrong delivery and the mail 
deletion. Thank you.
**


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Context reload mandatory ?

2006-11-02 Thread Remy.Coqueugniot
Hi tomcat users.

My environment:
Win32 + Tomcat 5.5.17 + JDK 1.4 + 1.4 compatibility package

I've got a webapp deployed under the context name /ABC
($TOMCAT_HOME/webapps/ABC)
This webapp writes some reports under ($TOMCAT_HOME/webapps/ABCReports)
When The reports is ready, an URL acces attempt on
http://localhost/ABCReports/report.html give me an 404 error.
In the manager when I reload the ABCReports context, the same URL is
OK.

Any ideas ? 



*ABC context.xml
Context antiJARLocking=true antiResourceLocking=true
/Context

---
Cette communication (y compris les pieces jointes) est reservee a l'usage 
exclusif du destinataire (des destinataires) et peut contenir des informations 
privilegiees, confidentielles, exemptees de divulgation selon la loi ou 
protegees par les droits d'auteur. Si vous n'etes pas un destinataire, toute 
utilisation, divulgation, distribution, reproduction, examen ou copie (totale 
ou partielle) est non-autorisee et peut etre illegale. Tout message 
electronique est susceptible d'alteration et son integrite ne peut etre 
assuree. Sanofi Pasteur decline toute responsabilite au titre de ce message 
s'il a ete modifie ou falsifie. Si vous n'etes pas destinataire de ce message, 
merci de le detruire immediatement et d'avertir l'expediteur de l'erreur de 
distribution et de la destruction du message. Merci.
This transmission (including any attachments) is intended solely for the use of 
the addressee(s) and may contain confidential information including trade 
secrets which are privileged, confidential, exempt from disclosure under 
applicable law and/or subject to copyright. If you are not an intended 
recipient, any use, disclosure, distribution, reproduction, review or copying 
(either whole or partial) is unauthorized and may be unlawful. E-mails are 
susceptible to alteration and their integrity cannot be guaranteed.Sanofi 
Pasteur shall not be liable for this e-mail if modified or falsified. If you 
are not the intended recipient of this e-mail, please delete it immediately 
from your system and notify the sender of the wrong delivery and the mail 
deletion. Thank you.
**


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Context reload mandatory ?

2006-11-02 Thread Remy.Coqueugniot
Thanks for your answer.

 This causes the app to be copied to the work directory and 
 read from there. Anything you write to you web app won't have 
 been copied, hence the 404. The reload causes the files to be 
 recopied.
Indeed, the work dir is full of cloned webapps, and until a reload the 
ABCReports doesn't contain my pages.
But how can I specify ABCReport not doing this copying job? Disabling 
antiJar/antiResource Locking ?

RC

 -Message d'origine-
 De : Mark Thomas [mailto:[EMAIL PROTECTED] 
 Envoyé : jeudi 2 novembre 2006 13:28
 À : Tomcat Users List
 Objet : Re: Context reload mandatory ?
 
 [EMAIL PROTECTED] wrote:
  This webapp writes some reports under 
  ($TOMCAT_HOME/webapps/ABCReports) When The reports is ready, an URL 
  acces attempt on http://localhost/ABCReports/report.html 
 give me an 404 error.
  In the manager when I reload the ABCReports context, the 
 same URL is 
  OK.
  
  Any ideas ? 
  
  *ABC context.xml
  Context antiJARLocking=true antiResourceLocking=true 
 /Context
 
 This causes the app to be copied to the work directory and 
 read from there. Anything you write to you web app won't have 
 been copied, hence the 404. The reload causes the files to be 
 recopied.
 
 Mark
 
 -
 To start a new topic, e-mail: users@tomcat.apache.org To 
 unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
---
Cette communication (y compris les pieces jointes) est reservee a l'usage 
exclusif du destinataire (des destinataires) et peut contenir des informations 
privilegiees, confidentielles, exemptees de divulgation selon la loi ou 
protegees par les droits d'auteur. Si vous n'etes pas un destinataire, toute 
utilisation, divulgation, distribution, reproduction, examen ou copie (totale 
ou partielle) est non-autorisee et peut etre illegale. Tout message 
electronique est susceptible d'alteration et son integrite ne peut etre 
assuree. Sanofi Pasteur decline toute responsabilite au titre de ce message 
s'il a ete modifie ou falsifie. Si vous n'etes pas destinataire de ce message, 
merci de le detruire immediatement et d'avertir l'expediteur de l'erreur de 
distribution et de la destruction du message. Merci.
This transmission (including any attachments) is intended solely for the use of 
the addressee(s) and may contain confidential information including trade 
secrets which are privileged, confidential, exempt from disclosure under 
applicable law and/or subject to copyright. If you are not an intended 
recipient, any use, disclosure, distribution, reproduction, review or copying 
(either whole or partial) is unauthorized and may be unlawful. E-mails are 
susceptible to alteration and their integrity cannot be guaranteed.Sanofi 
Pasteur shall not be liable for this e-mail if modified or falsified. If you 
are not the intended recipient of this e-mail, please delete it immediately 
from your system and notify the sender of the wrong delivery and the mail 
deletion. Thank you.
**


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[resolved] RE: Context reload mandatory ?

2006-11-02 Thread Remy.Coqueugniot

Thanks for your advice,

About this webapp design. 
The case is : 
 1-Some users may submit an analyse. 
 2-This analyse must complete asynchronously, and send a mail when it's done. 
 3-The URL of the report is include in the mail.
 4-When it has been read, the user may delete it.
So no need to include them in a DBMS/SCM or whatever... Just to be readable 
when it's done, and a cron will delete the too old ones.

Back to the tomcat part of the problem:
My default context.xml has been setup to force antiJar/resource locking.
So writing a ABCReport/META-INF/context.xml with just:
Context antiJARLocking=false antiResourceLocking=false
/Context
Forbids tomcat to copy it in temp dir, and reports change are available 
directly without reloading context.

May this mail be useful to some future potential readers

Thanks again

 -Message d'origine-
 De : Mikolaj Rydzewski [mailto:[EMAIL PROTECTED] 
 Envoyé : jeudi 2 novembre 2006 14:33
 À : Tomcat Users List
 Objet : Re: Context reload mandatory ?
 
 [EMAIL PROTECTED] wrote:
  Indeed, the work dir is full of cloned webapps, and until a 
 reload the ABCReports doesn't contain my pages.
  But how can I specify ABCReport not doing this copying job? 
 Disabling antiJar/antiResource Locking ?

 I think you should redesign your application.
 
  This webapp writes some reports under 
  ($TOMCAT_HOME/webapps/ABCReports)
 It is a bad thing.
 
 If you generate reports on the fly, so there's no reason to 
 save them on disk. If you want to cache them for a while use 
 some cache software/library. If you want them to persist 
 (really? why one want to persists a generated report) store 
 them in a database or in some other directory, accesible with 
 servlet or context mapping.
 
 You do use source control to have your application sources 
 consistent, right? So should you store generated, persistent 
 reports in a source control system...
 
 --
 Mikolaj Rydzewski [EMAIL PROTECTED]
 
 
---
Cette communication (y compris les pieces jointes) est reservee a l'usage 
exclusif du destinataire (des destinataires) et peut contenir des informations 
privilegiees, confidentielles, exemptees de divulgation selon la loi ou 
protegees par les droits d'auteur. Si vous n'etes pas un destinataire, toute 
utilisation, divulgation, distribution, reproduction, examen ou copie (totale 
ou partielle) est non-autorisee et peut etre illegale. Tout message 
electronique est susceptible d'alteration et son integrite ne peut etre 
assuree. Sanofi Pasteur decline toute responsabilite au titre de ce message 
s'il a ete modifie ou falsifie. Si vous n'etes pas destinataire de ce message, 
merci de le detruire immediatement et d'avertir l'expediteur de l'erreur de 
distribution et de la destruction du message. Merci.
This transmission (including any attachments) is intended solely for the use of 
the addressee(s) and may contain confidential information including trade 
secrets which are privileged, confidential, exempt from disclosure under 
applicable law and/or subject to copyright. If you are not an intended 
recipient, any use, disclosure, distribution, reproduction, review or copying 
(either whole or partial) is unauthorized and may be unlawful. E-mails are 
susceptible to alteration and their integrity cannot be guaranteed.Sanofi 
Pasteur shall not be liable for this e-mail if modified or falsified. If you 
are not the intended recipient of this e-mail, please delete it immediately 
from your system and notify the sender of the wrong delivery and the mail 
deletion. Thank you.
**


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [Isapi filter] jsessionid filtering

2006-10-30 Thread Remy.Coqueugniot

Anyone got some ideas ? 

Thanks,

RC

 -Message d'origine-
 De : [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] 
 Envoyé : vendredi 27 octobre 2006 09:48
 À : users@tomcat.apache.org
 Objet : [Isapi filter] jsessionid filtering
 
 Hi everyone,
 
 My environment: win2003 / Tomcat 5.5.17 / IIS / isapi filter 
 1.2.19.0 I've 3 instances of Tomcat running simultanously IIS 
 is configured to serve those 3 websites with a different 
 isapi filter configuration for each one.
 When a client opens a newly httpSession jsessionid is 
 inserted in the first URI . Next navigations doesn't include this.
 The problem is about what isapi really filters.
 See how the Uriworkmap is configured at the end of this mail.
 For example in the first session openning, every css file 
 acces fall in 404 beacause of the jssesionid presence in the 
 URI, and are correctly mapped in next operations.
 
 Indeed looking in the trace shows that isapi filter try to 
 remove this jsessionid from the URI, but apparently not use 
 the newly jsessionid-less URI :
 
 [Wed Oct 25 11:30:24 2006] [5564:0488] [debug] 
 jk_isapi_plugin.c (762): Filter started [Wed Oct 25 11:30:24 
 2006] [5564:0488] [debug] jk_isapi_plugin.c (828): Virtual 
 Host redirection of 
 /server1:83/application1/styles/appli.css;jsessionid=D31FF5301
 A1974701F9FE1837A18427B
 [Wed Oct 25 11:30:24 2006] [5564:0488] [trace] 
 jk_uri_worker_map.c (422): enter [Wed Oct 25 11:30:24 2006] 
 [5564:5240] [debug] jk_isapi_plugin.c (762): Filter started 
 [Wed Oct 25 11:30:24 2006] [5564:0488] [debug] 
 jk_uri_worker_map.c (443): Removing Session path 
 ';jsessionid=D31FF5301A1974701F9FE1837A18427B' URI 
 '/server1:83/application1/styles/appli.css'
 [Wed Oct 25 11:30:24 2006] [5564:0488] [debug] 
 jk_uri_worker_map.c (449): Attempting to map URI 
 '/server1:83/application1/styles/appli.css;jsessionid=D31FF530
 1A1974701F9FE1837A18427B' from 14 maps
 
 
 How can I make sure isapi filter really do its 
 jsessionid-filtering job ? Or how can say to tomcat not 
 include this jsessionid parameter, even in the first session access ?
 
 
 Thanks for your answers !
 
 
 Rémy C.
 
 
 
 
 
 -isapi_redirect.properties
 extension_uri=/jakarta/isapi_redirect.dll
 log_file=c:\Intranet\IISLog\jk_std1.log
 log_level=trace
 worker_file=c:\Intranet\IIS_jk\std1\workers.properties
 worker_mount_file=c:\Intranet\IIS_jk\std1\uriworkermap.properties
 
 
 -workers.properties
 worker.list=wlb_std
 worker.ajp13_std1.type=ajp13
 worker.ajp13_std1.host=localhost
 worker.ajp13_std1.port=8209
 worker.wlb_std.type=lb
 worker.wlb_std.balance_workers=ajp13_std1
 worker.jkstatus.type=status
 
 
 -uriworkermap.properties
 /jkmanager=jkstatus
 # applications mappings
 /application1/*=wlb_std
 # static elements served by IIS
 !/*.jpg=wlb_std
 !/*.gif=wlb_std
 !/*.png=wlb_std
 !/*.txt=wlb_std
 !/*.js=wlb_std
 !/*.xml=wlb_std
 !/*.xsl=wlb_std
 !/*.xslt=wlb_std
 !/*.htm=wlb_std
 !/*.html=wlb_std
 !/*.css=wlb_std
 !/*.swf=wlb_std
 --
 -
 Cette communication (y compris les pieces jointes) est 
 reservee a l'usage exclusif du destinataire (des 
 destinataires) et peut contenir des informations 
 privilegiees, confidentielles, exemptees de divulgation selon 
 la loi ou protegees par les droits d'auteur. Si vous n'etes 
 pas un destinataire, toute utilisation, divulgation, 
 distribution, reproduction, examen ou copie (totale ou 
 partielle) est non-autorisee et peut etre illegale. Tout 
 message electronique est susceptible d'alteration et son 
 integrite ne peut etre assuree. Sanofi Pasteur decline toute 
 responsabilite au titre de ce message s'il a ete modifie ou 
 falsifie. Si vous n'etes pas destinataire de ce message, 
 merci de le detruire immediatement et d'avertir l'expediteur 
 de l'erreur de distribution et de la destruction du message. Merci.
 This transmission (including any attachments) is intended 
 solely for the use of the addressee(s) and may contain 
 confidential information including trade secrets which are 
 privileged, confidential, exempt from disclosure under 
 applicable law and/or subject to copyright. If you are not an 
 intended recipient, any use, disclosure, distribution, 
 reproduction, review or copying (either whole or partial) is 
 unauthorized and may be unlawful. E-mails are susceptible to 
 alteration and their integrity cannot be guaranteed.Sanofi 
 Pasteur shall not be liable for this e-mail if modified or 
 falsified. If you are not the intended recipient of this 
 e-mail, please delete it immediately from your system and 
 notify the sender of the wrong delivery and the mail 
 deletion. Thank you.
 **
 
 
 -
 To start a new topic, e-mail: 

[Isapi filter] jsessionid filtering

2006-10-27 Thread Remy.Coqueugniot
Hi everyone,

My environment: win2003 / Tomcat 5.5.17 / IIS / isapi filter 1.2.19.0
I've 3 instances of Tomcat running simultanously
IIS is configured to serve those 3 websites with a different isapi filter 
configuration for each one.
When a client opens a newly httpSession jsessionid is inserted in the first URI 
. Next navigations doesn't include this.
The problem is about what isapi really filters.
See how the Uriworkmap is configured at the end of this mail.
For example in the first session openning, every css file acces fall in 404 
beacause of the jssesionid presence in the URI, and are correctly mapped in 
next operations.

Indeed looking in the trace shows that isapi filter try to remove this 
jsessionid from the URI, but apparently not use the newly jsessionid-less URI :

[Wed Oct 25 11:30:24 2006] [5564:0488] [debug] jk_isapi_plugin.c (762): Filter 
started
[Wed Oct 25 11:30:24 2006] [5564:0488] [debug] jk_isapi_plugin.c (828): Virtual 
Host redirection of 
/server1:83/application1/styles/appli.css;jsessionid=D31FF5301A1974701F9FE1837A18427B
[Wed Oct 25 11:30:24 2006] [5564:0488] [trace] jk_uri_worker_map.c (422): enter
[Wed Oct 25 11:30:24 2006] [5564:5240] [debug] jk_isapi_plugin.c (762): Filter 
started
[Wed Oct 25 11:30:24 2006] [5564:0488] [debug] jk_uri_worker_map.c (443): 
Removing Session path ';jsessionid=D31FF5301A1974701F9FE1837A18427B' URI 
'/server1:83/application1/styles/appli.css'
[Wed Oct 25 11:30:24 2006] [5564:0488] [debug] jk_uri_worker_map.c (449): 
Attempting to map URI 
'/server1:83/application1/styles/appli.css;jsessionid=D31FF5301A1974701F9FE1837A18427B'
 from 14 maps


How can I make sure isapi filter really do its jsessionid-filtering job ? Or 
how can say to tomcat not include this jsessionid parameter, even in the first 
session access ?


Thanks for your answers !


Rémy C.





-isapi_redirect.properties
extension_uri=/jakarta/isapi_redirect.dll
log_file=c:\Intranet\IISLog\jk_std1.log
log_level=trace
worker_file=c:\Intranet\IIS_jk\std1\workers.properties
worker_mount_file=c:\Intranet\IIS_jk\std1\uriworkermap.properties


-workers.properties
worker.list=wlb_std
worker.ajp13_std1.type=ajp13
worker.ajp13_std1.host=localhost
worker.ajp13_std1.port=8209
worker.wlb_std.type=lb
worker.wlb_std.balance_workers=ajp13_std1
worker.jkstatus.type=status


-uriworkermap.properties
/jkmanager=jkstatus
# applications mappings
/application1/*=wlb_std
# static elements served by IIS
!/*.jpg=wlb_std
!/*.gif=wlb_std
!/*.png=wlb_std
!/*.txt=wlb_std
!/*.js=wlb_std
!/*.xml=wlb_std
!/*.xsl=wlb_std
!/*.xslt=wlb_std
!/*.htm=wlb_std
!/*.html=wlb_std
!/*.css=wlb_std
!/*.swf=wlb_std
---
Cette communication (y compris les pieces jointes) est reservee a l'usage 
exclusif du destinataire (des destinataires) et peut contenir des informations 
privilegiees, confidentielles, exemptees de divulgation selon la loi ou 
protegees par les droits d'auteur. Si vous n'etes pas un destinataire, toute 
utilisation, divulgation, distribution, reproduction, examen ou copie (totale 
ou partielle) est non-autorisee et peut etre illegale. Tout message 
electronique est susceptible d'alteration et son integrite ne peut etre 
assuree. Sanofi Pasteur decline toute responsabilite au titre de ce message 
s'il a ete modifie ou falsifie. Si vous n'etes pas destinataire de ce message, 
merci de le detruire immediatement et d'avertir l'expediteur de l'erreur de 
distribution et de la destruction du message. Merci.
This transmission (including any attachments) is intended solely for the use of 
the addressee(s) and may contain confidential information including trade 
secrets which are privileged, confidential, exempt from disclosure under 
applicable law and/or subject to copyright. If you are not an intended 
recipient, any use, disclosure, distribution, reproduction, review or copying 
(either whole or partial) is unauthorized and may be unlawful. E-mails are 
susceptible to alteration and their integrity cannot be guaranteed.Sanofi 
Pasteur shall not be liable for this e-mail if modified or falsified. If you 
are not the intended recipient of this e-mail, please delete it immediately 
from your system and notify the sender of the wrong delivery and the mail 
deletion. Thank you.
**


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Exception processing TLD

2006-10-27 Thread Remy.Coqueugniot
Hi,

Please verify you don't have packaged your webapp with a jsp-api in your 
WEB-INF/lib 

Rémy

 -Message d'origine-
 De : Cédric Wider [mailto:[EMAIL PROTECTED] 
 Envoyé : vendredi 27 octobre 2006 14:33
 À : users@tomcat.apache.org
 Objet : Exception processing TLD
 
 I am trying to run an application using tomcat on a debian 
 based livecd (Morphix).
 I installed tomcat 5.5 using apt-get. The README.debian help 
 file says that debian is using dynamic links, so I wrote ' 
 allowLinking=true '
 to server.xml.
 
 I built the war file on another machine, where I tested it 
 before copying to the live-environment. When I start tomcat, 
 I get the following error message:
 
 Oct 27, 2006 9:31:24 AM 
 org.apache.catalina.core.StandardContext processTlds
 
 SEVERE: Error reading tld listeners javax.servlet.ServletException:
 Exception processing TLD at resource path 
 /WEB-INF/tlds/ppc.tld in context
 
 javax.servlet.ServletException: Exception processing TLD at 
 resource path /WEB-INF/tlds/ppc.tld in context
 
 I was googling around and also searching this mailinglist, 
 but couldn't find any solution for this problem. Even though 
 it appears that many users have it, it obviously might have 
 many different causes.
 What I've noticed comparing my error message to others on the 
 net, is that there is no context after the word context in 
 my error message.
 
 System information:
 Using CATALINA_BASE:   /usr/share/tomcat5.5
 Using CATALINA_HOME:   /usr/share/tomcat5.5
 Using CATALINA_TMPDIR: /usr/share/tomcat5.5/temp
 Using JRE_HOME:   /usr/share/jdk1.5.0_09
 Server version: Apache Tomcat/5.5
 Server built:   Oct 23 2006 05:06:19
 Server number:  5.5.20.0
 OS Name:Linux
 OS Version: 2.6.17-morphix
 Architecture:   i386
 JVM Version:1.5.0_09-b03
 JVM Vendor: Sun Microsystems Inc.
 
 
 Catalina.out:
 Using CATALINA_BASE:   /var/lib/tomcat5.5
 Using CATALINA_HOME:   /usr/share/tomcat5.5
 Using CATALINA_TMPDIR: /var/lib/tomcat5.5/temp
 Using JRE_HOME:   /usr/share/jdk1.5.0_09/jre
 Using Security Manager
 /etc/host.conf: line 2: bad command `127.0.0.1 
 MorphingMorphix localhost'
 Oct 27, 2006 9:31:20 AM 
 org.apache.coyote.http11.Http11BaseProtocol init
 INFO: Initializing Coyote HTTP/1.1 on http-8443 Oct 27, 2006 
 9:31:20 AM org.apache.coyote.http11.Http11BaseProtocol init
 INFO: Initializing Coyote HTTP/1.1 on http-8080 Oct 27, 2006 
 9:31:20 AM org.apache.coyote.http11.Http11BaseProtocol init
 INFO: Initializing Coyote HTTP/1.1 on http-2712 Oct 27, 2006 
 9:31:20 AM org.apache.catalina.startup.Catalina load
 INFO: Initialization processed in 2952 ms Oct 27, 2006 
 9:31:20 AM org.apache.catalina.core.StandardService start
 INFO: Starting service PPC-HTTPS
 Oct 27, 2006 9:31:20 AM org.apache.catalina.core.StandardEngine start
 INFO: Starting Servlet Engine: Apache Tomcat/5.5 Oct 27, 2006 
 9:31:20 AM org.apache.catalina.core.StandardHost start
 INFO: XML validation disabled
 log4j:WARN No appenders could be found for logger 
 (org.apache.catalina.startup.TldConfig).
 log4j:WARN Please initialize the log4j system properly.
 Oct 27, 2006 9:31:24 AM 
 org.apache.catalina.core.StandardContext processTlds
 SEVERE: Error reading tld listeners javax.servlet.ServletException:
 Exception processing TLD at resource path 
 /WEB-INF/tlds/ppc.tld in context
 javax.servlet.ServletException: Exception processing TLD at 
 resource path /WEB-INF/tlds/ppc.tld in context
 at
 org.apache.catalina.startup.TldConfig.tldScanTld(TldConfig.java:555)
 at 
 org.apache.catalina.startup.TldConfig.execute(TldConfig.java:301)
 at
 org.apache.catalina.core.StandardContext.processTlds(StandardC
 ontext.java:4302)
 at
 org.apache.catalina.core.StandardContext.start(StandardContext
 .java:4139)
 at
 org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
 at
 org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
 at
 org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
 at
 org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
 at
 org.apache.catalina.core.StandardService.start(StandardService
 .java:450)
 at
 org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
 at 
 org.apache.catalina.startup.Catalina.start(Catalina.java:551)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
 orImpl.java:39)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
 odAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at 
 org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
 at 
 org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
 
 
 
 
 Any hint?
 
 
 
---
Cette communication (y