cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup catalina.properties
remm2002/11/05 00:07:46 Modified:catalina/src/share/org/apache/catalina/startup catalina.properties Log: - Keep the catalina.properties files in sync. Revision ChangesPath 1.2 +4 -4 jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/catalina.properties Index: catalina.properties === RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/catalina.properties,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- catalina.properties 24 Oct 2002 13:53:22 - 1.1 +++ catalina.properties 5 Nov 2002 08:07:46 - 1.2 -1,11 +1,10 -# +## # List of comma-separated packages that start with or equal this string # will cause a security exception to be thrown when # passed to checkPackageAccess unless the # corresponding RuntimePermission (accessClassInPackage.+package) has # been granted. -package.access=sun. - +package.access=sun.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper. # # List of comma-separated packages that start with or equal this string # will cause a security exception to be thrown when -16,8 +15,9 # by default, no packages are restricted for definition, and none of # the class loaders supplied with the JDK call checkPackageDefinition. # -#package.definition= +package.definition=sun.,java.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper. +# # # List of comma-separated paths defining the contents of the common # classloader. Prefixes should be used to define what is the repository type. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 14246] New: - setclasspath.{sh,bat} require JDK's jdb and javac
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14246.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14246
setclasspath.{sh,bat} require JDK's jdb and javac
Summary: setclasspath.{sh,bat} require JDK's jdb and javac
Product: Tomcat 4
Version: 4.1.12
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
Dunno if this is spose to work or not.
But if you try to run Tomcat4.1 against the JRE alone
this script fails because it can't find jdb and javac.
At the very least, this is a change in behavior since 4.0
-Eric
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 14246] - setclasspath.{sh,bat} require JDK's jdb and javac
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14246.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14246
setclasspath.{sh,bat} require JDK's jdb and javac
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution||INVALID
--- Additional Comments From [EMAIL PROTECTED] 2002-11-05 08:54 ---
I think it's always been clear in the documentation that Tomcat requires the
JDK, and not the JRE. Of course, this is only needed for Jasper.
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 13759] - Tomcat Coyote hangs at fill() spending 100% CPU
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13759. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13759 Tomcat Coyote hangs at fill() spending 100% CPU --- Additional Comments From [EMAIL PROTECTED] 2002-11-05 09:09 --- I don't know if: - this is actually causing the bug, and if just disconnecting fixes it (the feedback given is cryptic) - having a 0 result is a normal result (if it's not we should disconnect, otherwise, we add a sleep and a max retry) -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
French translations for servletapi4
Since I didn't have commit access to servletapi4, here are the files
to be added.
# Default localized string information
# Localized for Locale fr_FR
err.cookie_name_is_token=Le nom de cookie {0} est un token réservé
err.io.negativelength=Taille négative donnée dans la méthode write
err.io.short_read=Lecture réduite
http.method_not_implemented=Le méthode {0} n''est pas définie dans la RFC 2068 et
n''est pas supportée par l''API Servlet
http.method_get_not_supported=La méthode HTTP GET n''est pas supportée par cette URL
http.method_post_not_supported=La méthode HTTP POST n''est pas supportée par cette URL
http.method_put_not_supported=La méthode HTTP PUT n''est pas supportée par cette URL
http.method_delete_not_supported=La méthode HTTP DELETE n''est pas supportée par cette
URL
# Default localized string information
# Localized for Locale fr_FR
err.not_iso8859_1={0} n''est pas un caractère ISO 8859-1
value.true=true
value.false=false
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
french translation for servletapi5
Ditto than previous for servletapi5
# Default localized string information
# Localized for Locale fr_FR
err.not_iso8859_1={0} n''est pas un caractère ISO 8859-1
value.true=true
value.false=false
# Default localized string information
# Localized for Locale fr_FR
err.cookie_name_is_token=Le nom de cookie {0} est un token réservé
err.io.negativelength=Taille négative donnée dans la méthode write
err.io.short_read=Lecture réduite
http.method_not_implemented=Le méthode {0} n''est pas définie dans la RFC 2068 et
n''est pas supportée par l''API Servlet
http.method_get_not_supported=La méthode HTTP GET n''est pas supportée par cette URL
http.method_post_not_supported=La méthode HTTP POST n''est pas supportée par cette URL
http.method_put_not_supported=La méthode HTTP PUT n''est pas supportée par cette URL
http.method_delete_not_supported=La méthode HTTP DELETE n''est pas supportée par cette
URL
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/users LocalStrings_fr.properties
hgomez 2002/11/05 01:35:13
Added: catalina/src/share/org/apache/catalina/users
LocalStrings_fr.properties
Log:
Add french translations
Revision ChangesPath
1.1
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/users/LocalStrings_fr.properties
Index: LocalStrings_fr.properties
===
memoryUserDatabase.invalidGroup=Nom de groupe invalide {0}
memoryUserDatabase.renameOld=Impossible de renommer le fichier original en {0}
memoryUserDatabase.renameNew=Impossible de renommer le nouveau fichier en {0}
memoryUserDatabase.writeException=IOException lors de l''écriture vers {0}
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/util LocalStrings_fr.properties
hgomez 2002/11/05 01:35:19
Added: catalina/src/share/org/apache/catalina/util
LocalStrings_fr.properties
Log:
Add french translations
Revision ChangesPath
1.1
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/util/LocalStrings_fr.properties
Index: LocalStrings_fr.properties
===
propertyMap.locked=Aucune modification n''est authorisée sur un ParameterMap
vérrouillé
resourceSet.locked=Aucune modification n''est authorisée sur un ResourceSet
vérrouillé
hexUtil.bad=Mauvais digit hexadecimal
hexUtil.odd=Nombre impair de digits hexadecimaux
#Default Messages Utilized by the ExtensionValidator
extensionValidator.web-application-manifest=Web Application Manifest
extensionValidator.extension-not-found-error=ExtensionValidator[{0}][{1}]:
L''extension requise {2} est introuvable.
extensionValidator.extension-validation-error=ExtensionValidator[{0}]: Impossible de
trouver {1} extension(s) requise(s).
SecurityUtil.doAsPrivilege=Une exception s''est produite lors de l''execution du
bloc PrivilegedExceptionAction.
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/valves LocalStrings_fr.properties
hgomez 2002/11/05 01:35:31
Added: catalina/src/share/org/apache/catalina/valves
LocalStrings_fr.properties
Log:
Add french translations
Revision ChangesPath
1.1
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/valves/LocalStrings_fr.properties
Index: LocalStrings_fr.properties
===
accessLogValve.alreadyStarted=Le traceur d''accès a déjà été démarré
accessLogValve.notStarted=Le traceur d''accès n''a pas encore été démarré
certificatesValve.alreadyStarted=La Valve de Certificats a déjà été démarrée
certificatesValve.notStarted=La Valve de Certificats n''a pas encore été démarrée
interceptorValve.alreadyStarted=La Valve d''Interception a déjà été démarré
interceptorValve.notStarted=La Valve d''Interception n''a pas encore été démarrée
requestFilterValve.next=Aucune Valve 'suivante' n''a été configurée
requestFilterValve.syntax=Erreur de synthaxe dans le pattern de filtre de requête {0}
requestListenerValve.requestInit=Une exception lors de l''envoi de requête a initié
un évènement cycle de vie (lifecycle event) pour l''instance de classe à l'écoute
(listener) {0}
requestListenerValve.requestDestroy=Une exception lors de l''envoi de requête a
détruit un évènement cycle de vie (lifecycle event) pour l''instance de classe à
l'écoute (listener) {0}
valveBase.noNext=Erreur de configuration error: Aucune Valve 'suivante' n''a été
configurée
# Error report valve
errorReportValve.errorReport=Rapport d''erreur
errorReportValve.statusHeader=Etat HTTP {0} - {1}
errorReportValve.exceptionReport=Rapport d''exception
errorReportValve.statusReport=Rapport d''état
errorReportValve.message=message
errorReportValve.description=description
errorReportValve.exception=exception
errorReportValve.rootCause=cause mère
# HTTP status reports
http.100=Le client peut continuer ({0}).
http.101=Le serveur change de protocoles suivant la directive Upgrade de l''entête
({0}).
http.201=La requête a réussi et une nouvelle ressource ({0}) a été créee sur le
serveur.
http.202=La requête a été accepté pour traitement, mais n''a pas été terminée ({0}).
http.203=L''information meta présentée par le client n''a pas pour origine ce server
({0}).
http.204=La requête a réussi mais il n''y a aucune information à retourner ({0}).
http.205=Le client doit remettre à zéro la vue de document qui a causée l''envoi de
cette requête ({0}).
http.206=Le serveur a satisfait une requête GET partielle pour cette ressource ({0}).
http.207=Plusieurs valeurs d''états ont été retournées ({0}).
http.300=La ressource demandée ({0}) correspond à plusieurs représentations, chacune
avec sa propre localisation.
http.301=La ressource demandée ({0}) a été déplacée de façon permanente vers une
nouvelle localisation.
http.302=La ressource demandée ({0}) a été déplacée de façon temporaire vers une
nouvelle localisation.
http.303=La réponse à cette requête peut être trouvée à une URI différente ({0}).
http.304=La ressource demandée ({0}) est disponible et n''a pas été modifiée.
http.305=La ressource demandée ({0}) doit être accédée au travers du relais indiqué
par la directive Location de l''entête.
http.400=La requête envoyée par le client était syntaxiquement incorrecte ({0}).
http.401=La requête nécessite une authentification HTTP ({0}).
http.402=Un paiement est demandé pour accéder à cette ressource ({0}).
http.403=L''accès à la ressource demandée ({0}) a été interdit.
http.404=La ressource demandée ({0}) n''est pas disponible.
http.405=La méthode HTTP spécifiée n''est pas autorisée pour la ressource demandée
({0}).
http.406=La ressource identifiée par cette requête n''est capable de générer des
réponses qu''avec des caractéristiques incompatible avec la directive accept
présente dans l''entête de requête ({0}).
http.407=Le client doit d''abord s''authentifier auprès du relais ({0}).
http.408=Le client n''a pas produit de requête pendant le temps d''attente du
serveur ({0}).
http.409=La requête ne peut être finalisée suite à un conflit lié à l''état de la
ressource ({0}).
http.410=La ressource demandée ({0}) n''est pas disponible, et aucune addresse de
rebond (forwarding) n''est connue.
http.411=La requête ne peut être traitée sans définition d''une taille de contenu
(content length) ({0}).
http.412=Une condition préalable demandée a échouée pour cette requête ({0}).
http.413=L'entité de requête est plus importante que ce que le serveur veut ou peut
traiter.
http.414=Le serveur a refusé cette requête car URI de requête est trop longue ({0}).
http.415=Le serveur a refusé cette requête car l''entité de requête est dans un
format non supporté par la ressource demandée avec la méthode spécifiée ({0}).
http.416=La place d'octets (byte range) ne peut être satisfaite ({0}).
http.417=L''attente
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/naming LocalStrings_fr.properties
hgomez 2002/11/05 01:35:48
Added: catalina/src/share/org/apache/naming/resources
LocalStrings_fr.properties
catalina/src/share/org/apache/naming
LocalStrings_fr.properties
Log:
Add french translations
Revision ChangesPath
1.1
jakarta-tomcat-catalina/catalina/src/share/org/apache/naming/resources/LocalStrings_fr.properties
Index: LocalStrings_fr.properties
===
fileResources.base=Le document base {0} n''existe pas ou n''est pas un répertoire
lisible
warResources.notWar=Doc base doit pointé vers un fichier WAR
warResources.invalidWar=Fichier WAR invalide ou illisible : {0}
jarResources.syntax=Le document base {0} doit commencé par 'jar:' et finir avec '!/'
resources.alreadyStarted=Les Ressources ont déjà été démarrées
resources.connect=Impossible de se connecter au document base {0}
resources.input=Impossible de créer l'input stream pour la ressource {0}
resources.notStarted=Les ressources n''ont pas encore été démarrées
resources.null=Le document base ne peut être nul
resources.notFound=La ressource {0} est introuvable
resources.path=Le chemin relatif de context {0} doit commencé par '/'
resources.alreadyBound=Le nom {0} est déjà référencé par ce contexte
resources.bindFailed=Le liage a échoué: {0}
resources.unbindFailed=Le déliage a échoué: {0}
standardResources.alreadyStarted=Les ressources ont déja été démarrées
standardResources.directory=Le file base {0} n''est pas un répertoire
standardResources.exists=Le file base {0} n''existe pas
standardResources.notStarted=Les ressources n''ont pas encore été démarrées
standardResources.null=Le document base ne peut être nul
standardResources.slash=Le document base {0} ne doit pas se terminer par un '/'
1.1
jakarta-tomcat-catalina/catalina/src/share/org/apache/naming/LocalStrings_fr.properties
Index: LocalStrings_fr.properties
===
contextBindings.unknownContext=Nom de Contexte inconnu : {0}
contextBindings.noContextBoundToThread=Aucun Contexte de nommage lié à ce thread
contextBindings.noContextBoundToCL=Aucun Contexte de nommage lié à ce chargeur de
classes
selectorContext.noJavaUrl=Ce Contexte doit être accédé par une java: URL
namingContext.contextExpected=Le Nom n''est pas lié à un Contexte
namingContext.nameNotBound=Le Nom {0} n''est pas lié à ce Contexte
namingContext.readOnly=Le Contexte est en lecture seule
namingContext.invalidName=Le Nom est invalide
namingContext.alreadyBound=Le Nom {0} est déjà lié à ce Contexte
namingContext.noAbsoluteName=Impossible de générer un nom absolu pour cet espace de
nommage (namespace)
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat4 LocalStrings_fr.properties
hgomez 2002/11/05 01:37:35
Modified:http11/src/java/org/apache/coyote/http11
LocalStrings.properties
Added: http11/src/java/org/apache/coyote/http11
LocalStrings_fr.properties
coyote/src/java/org/apache/coyote/tomcat5
LocalStrings_fr.properties
util/java/org/apache/tomcat/util/net/res
LocalStrings_fr.properties
coyote/src/java/org/apache/coyote/tomcat4
LocalStrings_fr.properties
Log:
Add french translations
Revision ChangesPath
1.5 +2 -2
jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/LocalStrings.properties
Index: LocalStrings.properties
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/LocalStrings.properties,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- LocalStrings.properties 29 May 2002 03:12:04 - 1.4
+++ LocalStrings.properties 5 Nov 2002 09:37:34 - 1.5
-2,7 +2,7
# language
-# package org.apache.catalina.connector.http
+# package org.apache.coyote.http11
#
# Http11Protocol
1.1
jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/LocalStrings_fr.properties
Index: LocalStrings_fr.properties
===
# $Id: LocalStrings_fr.properties,v 1.1 2002/11/05 09:37:34 hgomez Exp $
# language fr
# package org.apache.coyote.http11
#
# Http11Protocol
#
http11protocol.endpoint.initerror=Erreur à l''initialisation du point de contact
http11protocol.endpoint.starterror=Erreur au démarrage du point de contact
http11protocol.init=Initialisation de Coyote HTTP/1.1 sur le port {0}
http11protocol.proto.error=Erreur à la lecture de la requête, ignoré
http11protocol.proto.ioexception.debug=Exception d''entrée/sortie (IOException) à la
lecture de la requête
http11protocol.proto.ioexception.info=Exception d''entrée/sortie à la lecture de la
requête, ignoré
http11protocol.proto.socketexception.debug=Exception Socket (SocketException) à la
lecture de la requête
http11protocol.proto.socketexception.info=Exception Socket (SocketException) à la
lecture de la requête, ignoré
http11protocol.setattribute=Attribut {0}: {1}
http11protocol.socketfactory.initerror=Erreur à l''initialisation du créateur de
socket (socket factory)
http11protocol.start=Démarrage de Coyote HTTP/1.1 sur le port {0}
#
# Http11Processor
#
#
# InternalInputBuffer
#
iib.eof.error=Fin de flux (EOF) inattendue à la lecture sur la socket
iib.requestheadertoolarge.error=L''entête de requête est trop important
1.1
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/LocalStrings_fr.properties
Index: LocalStrings_fr.properties
===
#
# CoyoteConnector
#
coyoteConnector.alreadyInitialized=Le connecteur a déjà été initialisé
coyoteConnector.alreadyStarted=Le connecteur a déjà été démarré
coyoteConnector.notStarted=Le connecteur Coyote n''a pas été démarré
coyoteConnector.protocolHandlerDestroyFailed=La destruction du gestionnaire de
protocole a échoué: {0}
coyoteConnector.protocolHandlerInitializationFailed=L''initialisation du
gestionnaire de protocole a échoué: {0}
coyoteConnector.protocolHandlerInstantiationFailed=L''instantiation du gestionnaire
de protocole a échoué: {0}
coyoteConnector.protocolHandlerStartFailed=Le démarrage du gestionnaire de protocole
a échoué: {0}
#
# CoyoteAdapter
#
coyoteAdapter.service=Une exception ou une erreur s''est produite dans le conteneur
durant le traitement de la requête
#
# CoyoteResponse
#
coyoteResponse.getOutputStream.ise=getWriter() a déjà été appelé pour cette réponse
coyoteResponse.getWriter.ise=getOutputStream() a déjà été appelé pour cette réponse
coyoteResponse.resetBuffer.ise=Impossible de remettre à zéro le tampon après que la
réponse ait été envoyée
coyoteResponse.sendError.ise=Impossible d''appeler sendError() après que la
réponse ait été envoyée
coyoteResponse.sendRedirect.ise=Impossible d''appeler sendRedirect() après que la
réponse ait été envoyée
coyoteResponse.setBufferSize.ise=Impossible de changer la taille du tampon après que
les données aient été écrites
#
# CoyoteRequest
#
coyoteRequest.getInputStream.ise=getReader() a déjà été appelé pour cette requête
coyoteRequest.getReader.ise=getInputStream() a déjà été appelé pour cette requête
coyoteRequest.sessionCreateCommitted=Impossible de créer une sessionaprès que la
réponse ait été envoyée
coyoteRequest.setAttribute.namenull=Impossible
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector LocalStrings_fr.properties
hgomez 2002/11/05 01:40:04 Added: catalina/src/share/org/apache/catalina/connector LocalStrings_fr.properties Log: Add french translations Revision ChangesPath 1.1 jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/LocalStrings_fr.properties Index: LocalStrings_fr.properties === httpRequestBase.createCommitted=Impossible de créer une session après que la réponse ait été envoyée httpRequestBase.contentLengthMismatch=La lecture des paramêtres POST de la requête HTTP a échoué: lecture taille du contenu httpRequestBase.contentReadFail=La lecture des paramêtres POST de la requête HTTP a échoué: httpResponseBase.sendError.ise=Impossible d''appeler sendError() après que la réponse ait été envoyée httpResponseBase.sendRedirect.ise=Impossible d''appeler sendRedirect() après que la réponse ait été envoyée requestBase.getInputStream.ise=getReader() a déjà été appelé pour cette requête requestBase.getReader.ise=getInputStream() a déjà été appelé pour cette requête requestStream.close.closed=Impossible de fermer deux fois le même flux d''entrée (input stream) requestStream.close.skip=skip() a retourné zero octets sauté (skipped) requestStream.read.closed=Ce flux d''entrée (input stream) a été fermé responseBase.getOutputStream.ise=getWriter() a déjà été appelé pour cette réponse responseBase.getWriter.ise=getOutputStream() a déjà été appelé pour cette réponse responseBase.reset.ise=Impossible de remettre à zéro après que la réponse ait été envoyée responseBase.resetBuffer.ise=Impossible de remettre à zéro le tampon après que la réponse ait été envoyée requestBase.setAttribute.namenull=Le nom ne peut être nul responseBase.setBufferSize.ise=La taille du tampon ne peut être changée après que les données aient été écrites responseStream.close.closed=Ce flux de sortie (output stream) a déjà été fermé responseStream.flush.closed=Impossible de vidanger (flush) un flux de sortie (output stream) fermé responseStream.suspended=le flux (stream) a été fermé responseStream.write.closed=Impossible d''écrire sur un flux de sortie (output stream) fermé responseStream.write.count=Impossible d''écrire plus d''octets que la taille de contenu (content length) pour ce flux de sortie (output stream) -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/servlets LocalStrings_fr.properties
hgomez 2002/11/05 01:40:20
Added: catalina/src/share/org/apache/catalina/servlets
LocalStrings_fr.properties
Log:
Add french translations
Revision ChangesPath
1.1
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/servlets/LocalStrings_fr.properties
Index: LocalStrings_fr.properties
===
defaultservlet.directorylistingfor=Liste du répertoire pour :
defaultservlet.upto=Jusqu''à:
defaultservlet.subdirectories=Sous-répertoires:
defaultservlet.files=Fichiers:
htmlManagerServlet.appsAvailable=Fonctionnant
htmlManagerServlet.appsName=Nom d''affichage
htmlManagerServlet.appsPath=Chemin
htmlManagerServlet.appsReload=Recharger
htmlManagerServlet.appsRemove=Retirer
htmlManagerServlet.appsSessions=Sessions
htmlManagerServlet.appsStart=Démarrer
htmlManagerServlet.appsStop=Arréter
htmlManagerServlet.appsTitle=Applications
htmlManagerServlet.installButton=Installation
htmlManagerServlet.installConfig=URL de configuration:
htmlManagerServlet.installPath=Chemin:
htmlManagerServlet.installTitle=Installation
htmlManagerServlet.installWar=URL du WAR:
htmlManagerServlet.messageLabel=Message:
htmlManagerServlet.serverJVMVendor=Fournisseur de la JVM
htmlManagerServlet.serverJVMVersion=Version de la JVM
htmlManagerServlet.serverOSArch=Architecture d''OS
htmlManagerServlet.serverOSName=Nom d''OS
htmlManagerServlet.serverOSVersion=Version d''OS
htmlManagerServlet.serverTitle=Serveur
htmlManagerServlet.serverVersion=Version de serveur
htmlManagerServlet.title=Gestionnaire d''applications WEB Tomcat
invokerServlet.allocate=Impossible d''allouer une instance de servlet pour le chemin
{0}
invokerServlet.cannotCreate=Impossible de créer un enrobeur (wrapper) de servlet
pour le chemin {0}
invokerServlet.deallocate=Impossible de désallouer une instance de servlet pour le
chemin {0}
invokerServlet.invalidPath=Aucun nom de servlet ou de classe n''a été spécifié pour
le chemin
{0}
invokerServlet.notNamed=Impossible d'appeler le délégué (invoker) de servlet avec un
aiguilleur (dispatcher) nommé
invokerServlet.noWrapper=Le conteneur n''a pas appelé setWrapper() pour cette
servlet
managerServlet.alreadyContext=ECHEC - l''application existe déjà dans le chemin {0}
managerServlet.alreadyDocBase=ECHEC - Le répertoire {0} est déjà utilisé
managerServlet.cannotInvoke=Impossible d'utiliser le gestionnaire de servlet au
travers du délégué (invoker)
managerServlet.configured=OK - Application configurée depuis le fichier contexte {0}
managerServlet.deployed=OK - Application déployée pour le chemin de contexte {0}
managerServlet.exception=ECHEC - L''exception {0} a été rencontrée
managerServlet.installed=OK - Application installée pour le chemin de contexte {0}
managerServlet.invalidPath=ECHEC - Un chemin de contexte invalide {0} a été spécifié
managerServlet.invalidWar=ECHEC - Une URL d''application invalide {0} a été spécifiée
managerServlet.listed=OK - Applications listées pour l''hôte virtuel (virtual host)
{0}
managerServlet.listitem={0}:{1}:{2}:{3}
managerServlet.noAppBase=ECHEC - Impossible d''identifier la base de l''application
base pour le chemin de
context {0}
managerServlet.noCommand=ECHEC - Aucune commande n''a été spécifiée
managerServlet.noContext=ECHEC - Aucune contexte n''existe pour le chemin {0}
managerServlet.noDirectory=ECHEC - La base de document n''est pas un répertoire pour
le chemin {0}
managerServlet.noDocBase=ECHEC - Impossible de retirer la base de document pour le
chemin {0}
managerServlet.noGlobal=ECHEC - Aucune ressource JNDI globale n''est disponible
managerServlet.noPath=ECHEC - Aucun chemin de contexte n''a été spécifié
managerServlet.noReload=ECHEC - Rechargement non supporté par le WAR déployé au
chemin
{0}
managerServlet.noRename=ECHEC - Impossible de déployer un WAR téléchargé pour le
chemin {0}
managerServlet.noRole=ECHEC - L''utilisateur ne possède pas le rôle {0}
managerServlet.noSelf=ECHEC - Le gestionnaire ne peut recharger, retirer, arréter,
ou se déployer lui-même
managerServlet.noWrapper=Le conteneur n''a pas appelé setWrapper() pour cette
servlet
managerServlet.reloaded=OK - Application rechargée au chemin de contexte {0}
managerServlet.removed=OK - Application retirée au chemin de contexte {0}
managerServlet.resourcesAll=OK - Liste des ressources globales de tout type
managerServlet.resourcesType=OK - Liste des ressources globales de type {0}
managerServlet.rolesList=OK - Liste de rôles de securité
managerServlet.saveFail=ECHEC - La sauvegarde de la configuration a échoué: {0}
managerServlet.sessiondefaultmax=Interval par défaut de maximum de session inactive
{0} minutes
managerServlet.sessiontimeout={0} minutes:{1} sessions
managerServlet.sessions=OK - Information de session pour l''application au chemin
Remy?
Remy, since you were the one arguing against me, I would like you to reply to my two postings on the 30th of November, 13040, and ServletContext.getContext() and error code 200 when doing error-page. Sorry to hassle you, I know you've been away. Martin -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 13759] - Tomcat Coyote hangs at fill() spending 100% CPU
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13759. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13759 Tomcat Coyote hangs at fill() spending 100% CPU [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2002-11-05 11:33 --- On JDK Api Docs, about InputStream.read(): If len is zero, then no bytes are read and 0 is returned; otherwise, there is an attempt to read at least one byte. If no byte is available because the stream is at end of file, the value -1 is returned; otherwise, at least one byte is read and stored into b. So a 0 and a -1 can be returned by read() and it means that there is not more data available, so I think we just should disconnect. Surelly this is causing the bug, because if 0 or -1 is returned, then lastValid variable is not updated and doRead stands calling fill() forever. Now I will reopen the bug... If you don't agree, feel free to resolve it again!!! -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core LocalStrings.properties
hgomez 2002/11/05 03:36:16
Modified:catalina/src/share/org/apache/catalina/core
LocalStrings.properties
Log:
Fix typo
Revision ChangesPath
1.47 +1 -1
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/LocalStrings.properties
Index: LocalStrings.properties
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/LocalStrings.properties,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- LocalStrings.properties 26 Sep 2002 10:25:03 - 1.46
+++ LocalStrings.properties 5 Nov 2002 11:36:16 - 1.47
-63,7 +63,7
standardContext.reloadingStarted=Reloading this Context has started
standardContext.resources.started=Cannot change resources while context is started
standardContext.resourcesStart=Resources start failed:
-standardContext.resourcesStop=Resources start failed:
+standardContext.resourcesStop=Resources stop failed:
standardContext.securityConstraint.pattern=Invalid url-pattern {0} in security
constraint
standardContext.servletMap.name=Servlet mapping specifies an unknown servlet name
{0}
standardContext.servletMap.pattern=Invalid url-pattern {0} in servlet mapping
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-4.0/catalina/src/conf server.xml
jfclere 2002/11/05 03:41:49 Modified:catalina/src/conf server.xml Log: Arrange the explainations about maxActiveSessions and minIdleSwap. Revision ChangesPath 1.64 +7 -6 jakarta-tomcat-4.0/catalina/src/conf/server.xml Index: server.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/conf/server.xml,v retrieving revision 1.63 retrieving revision 1.64 diff -u -r1.63 -r1.64 --- server.xml22 Oct 2002 09:45:34 - 1.63 +++ server.xml5 Nov 2002 11:41:49 - 1.64 -307,14 +307,15 ignored in both cases. maxActiveSessions: If 0 or greater, having too many active sessions will result in some being swapped out. minIdleSwap - limits this. -1 means unlimited sessions are allowed. - 0 means sessions will almost always be swapped out after - use - this will be noticeably slow for your users. + limits this. -1 or 0 means unlimited sessions are allowed. + If it is not possible to swap sessions new sessions will + be rejected. + This avoids thrashing when the site is highly active. minIdleSwap: Sessions must be idle for at least this long (in seconds) before they will be swapped out due to - maxActiveSessions. This avoids thrashing when the site is - highly active. -1 or 0 means there is no minimum - sessions - can be swapped out at any time. + activity. + 0 means sessions will almost always be swapped out after + use - this will be noticeably slow for your users. maxIdleSwap: Sessions will be swapped out if idle for this long (in seconds). If minIdleSwap is higher, then it will override this. This isn't exact: it is checked periodically. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 13759] - Tomcat Coyote hangs at fill() spending 100% CPU
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13759. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13759 Tomcat Coyote hangs at fill() spending 100% CPU --- Additional Comments From [EMAIL PROTECTED] 2002-11-05 11:45 --- That's incorrect, as len is never 0. The javadocs explicitely said that the call will block until at least one byte is read. Also, I'm not convinced there's a problem, as the only major problem reported with Coyote HTTP/1.1 has been the sever socket dying (apparently because of bugs in the VM network code; workarounds similar to those in 4.0.x were added in 4.1.14 to fix that). -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: PersistentManager
Clere, Jean-Frederic wrote: Hi, I am trying to use the PersistentManager. But it seems it is not working: - maxActiveSessions=0: No session are possible. (That is not what says the server.xml ). - saveOnRestart=true: A part creating the file it seems it is doing nothing. Has someone already use it? I need a more complex FileStore: - I need to have an absolut directory. That is the directory directive of FileStore and it works. But I have noted that a swapped session dispairs after beeing swapped. - I want to add some locking (to be able to share the sessions between Tomcat's). Should I create a new FileStore or improve the existing one? I have to write a new one. Because I need a piece of native code. Cheers Jean-frederic -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core LocalStrings_fr.properties
hgomez 2002/11/05 04:20:54
Added: catalina/src/share/org/apache/catalina/core
LocalStrings_fr.properties
Log:
Add french translation :
notes to quebecians readers ;)
wrapper = enrobeur
Revision ChangesPath
1.1
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/LocalStrings_fr.properties
Index: LocalStrings_fr.properties
===
applicationContext.attributeEvent=Exception lancée par l''écouteur (listener)
d''évènement attributs
applicationContext.requestDispatcher.iae=Le chemin {0} ne commence pas par le
caractère /
applicationContext.setAttribute.namenull=le nom ne peut être nul
applicationDispatcher.allocateException=Exception d''allocation pour la servlet {0}
applicationDispatcher.deallocateException=Exception de désallocation pour la servlet
{0}
applicationDispatcher.forward.ise=Impossible d''utiliser faire-suivre (forward)
après que la réponse ait été envoyée
applicationDispatcher.forward.throw=La ressource faire-suivre (forwarded) a lancé
une exception
applicationDispatcher.include.throw=La ressource incluse (included) a lancé une
exception
applicationDispatcher.isUnavailable=La servlet {0} est actuellement indisponible
applicationDispatcher.serviceException=Servlet.service() pour la servlet {0} a
lancé une exception
applicationRequest.badParent=Impossible de trouver l''implementation requête
apparentée (parent request)
applicationRequest.badRequest=La requête n''est pas une
javax.servlet.ServletRequestWrapper
applicationResponse.badParent=Impossible de trouver une implémentation réponse
apparentée (parent response)
applicationResponse.badResponse=La réponse n''est pas une
javax.servlet.ServletResponseWrapper
containerBase.addDefaultMapper=Exception lors de la configuration du routeur par
défaut (default mapper) pour la classe {0}
containerBase.alreadyStarted=Le conteneur {0} a déjà été démarré
containerBase.notConfigured=Aucune Valve basique (basic valve) n''a été configurée
containerBase.notStarted=Le conteneur {0} n''a pas été démarré
fastEngineMapper.alreadyStarted=le FastEngineMapper {0} a déjà été démarré
fastEngineMapper.notStarted=Le FastEngineMapper {0} n''a pas encore été démarré
filterChain.filter=L''exécution du filtre (Filter) a lancé une exception
filterChain.servlet=L''exécution de la servlet a lancé une exception
httpContextMapper.container=Ce conteneur n''est pas un StandardContext
httpEngineMapper.container=Ce conteneur n''est pas un StandardEngine
httpHostMapper.container=Ce conteneur n''est pas un StandardHost
interceptorValve.alreadyStarted=La valve d''interception (InterceptorValve) a déjà
été démarrée
interceptorValve.notStarted=La valve d''interception (InterceptorValve) n''a pas
encore été démarrée
naming.bindFailed=Echec lors du liage à l''objet: {0}
naming.unbindFailed=Echec lors du déliage à l'objet : {0}
naming.invalidEnvEntryType=L''entrée environnement {0} a un type invalide
naming.invalidEnvEntryValue=L''entrée environnement {0} a une valeur invalide
naming.namingContextCreationFailed=La création du context de nommage (naming
context) a échoué : {0}
standardContext.alreadyStarted=Le contexte a déjà été démarré
standardContext.applicationListener=Erreur lors de la configuration de la classe
d''écoute de l''application (application listener) {0}
standardContext.applicationSkipped=L'installation des écouteurs (listeners) de
l''application a été sautée suite aux erreurs précédentes
standardContext.badRequest=Chemin de requête invalide ({0}).
standardContext.errorPage.error=La position de la page d''erreur (ErrorPage) {0}
doit commencer par un '/'
standardContext.errorPage.required=La page d''erreur (ErrorPage) ne peut être nulle
standardContext.errorPage.warning=ATTENTION: La position de la page d''erreur
(ErrorPage) {0} doit commencer par un '/' dans l''API Servlet 2.3
standardContext.filterMap.either=L''association de filtre (filter mapping) doit
indiqué soit une url-pattern ou une servlet-name
standardContext.filterMap.name=L''association de filtre (filter mapping) indique un
nom de filtre inconnu {0}
standardContext.filterMap.pattern=url-pattern {0} invalide dans l''association de
filtre (filter mapping)
standardContext.filterStart=Exception au démarrage du filtre {0}
standardContext.filterStartFailed=Echec du démarrage des filtres d''application
standardContext.isUnavailable=Cette application n''est pas disponible actuellement
standardContext.listenerStart=Exception lors de l''envoi de l''évènement contexte
initialisé (context initialized) à l''instance de classe d''écoute (listener) {0}
standardContext.listenerStartFailed=Echec du démarrage des écouteurs (listeners)
d''application
standardContext.listenerStop=Exception lors de l''envoi de l''évènement contexte
détruit (context
french translation for servletapi (2.2)
Could it be commited ?
Thanks
# Default localized string information
# Localized for Locale fr_FR
err.not_iso8859_1={0} n''est pas un caractère ISO 8859-1
value.true=true
value.false=false
# Default localized string information
# Localized for Locale fr_FR
err.cookie_name_is_token=Le nom de cookie {0} est un token réservé
err.io.negativelength=Taille négative donnée dans la méthode write
err.io.short_read=Lecture réduite
http.method_not_implemented=Le méthode {0} n''est pas définie dans la RFC 2068 et
n''est pas supportée par l''API Servlet
http.method_get_not_supported=La méthode HTTP GET n''est pas supportée par cette URL
http.method_post_not_supported=La méthode HTTP POST n''est pas supportée par cette URL
http.method_put_not_supported=La méthode HTTP PUT n''est pas supportée par cette URL
http.method_delete_not_supported=La méthode HTTP DELETE n''est pas supportée par cette
URL
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: french translation for servletapi (2.2)
Henri Gomez wrote:
Could it be commited ?
Thanks
# Default localized string information
# Localized for Locale fr_FR
err.not_iso8859_1={0} n''est pas un caractère ISO 8859-1
value.true=true
value.false=false
# Default localized string information
# Localized for Locale fr_FR
err.cookie_name_is_token=Le nom de cookie {0} est un token réservé
err.io.negativelength=Taille négative donnée dans la méthode write
err.io.short_read=Lecture réduite
Non. partielle. (That sounds better according to the java sources).
http.method_not_implemented=Le méthode {0} n''est pas définie dans la RFC 2068 et n''est pas supportée par l''API Servlet
http.method_get_not_supported=La méthode HTTP GET n''est pas supportée par cette URL
http.method_post_not_supported=La méthode HTTP POST n''est pas supportée par cette URL
http.method_put_not_supported=La méthode HTTP PUT n''est pas supportée par cette URL
http.method_delete_not_supported=La méthode HTTP DELETE n''est pas supportée par cette URL
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: french translation for servletapi (2.2)
err.cookie_name_is_token=Le nom de cookie {0} est un token réservé
err.io.negativelength=Taille négative donnée dans la méthode write
err.io.short_read=Lecture réduite
Non. partielle. (That sounds better according to the java sources).
Exact so replace :
err.io.short_read=Lecture réduite
by
err.io.short_read=Lecture partielle
Should be done for 2.2/2.3 and 2.4 apis...
Who ?
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 14257] New: - jsp will execute 2 times
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14257. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14257 jsp will execute 2 times Summary: jsp will execute 2 times Product: Tomcat 4 Version: 4.1.12 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When I link to a jsp page ,the jsp page will execute 2 times this is my log: 2002-11-05 22:44:44,696 DEBUG [querykeyword.jsp] querykeyword.jsp start. 2002-11-05 22:44:44,696 DEBUG [querykeyword.jsp] arrKeyword is null 2002-11-05 22:44:44,696 DEBUG [querykeyword.jsp] querykeyword.jsp end. 2002-11-05 22:44:44,774 DEBUG [querykeyword.jsp] querykeyword.jsp start. 2002-11-05 22:44:44,774 DEBUG [querykeyword.jsp] arrKeyword is null 2002-11-05 22:44:44,775 DEBUG [querykeyword.jsp] querykeyword.jsp end. I don't know why. Can you help me? -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Tomcat 4.1.12 root context index.jsp bug
I have posted this in several different ways on the user list and had virtually no responses, and I believe it's a real live bug, so I'll post it here and then prepare to duck flames... Running Tomcat 4.1.12 with Sun JDK 1.4.1 on Win2K, if I change the root context to point someplace other than webapps/ROOT, I still get the default index.jsp if I request http://localhost:8080/index.jsp -- if that sounds sketchy and weird, get a load of this: I have also zipped up (removed the files from) webapps/ROOT completely (actually, webapps is completely empty), cleared my browser cache, etc. etc. and I still get the default index.jsp, but without the graphics (remember, the files are not anywhere on my drive). Further, I can successfully request any files OTHER than index.jsp (e.g. main.jsp, logon.jsp, etc. etc.) from the directory containing the new root context. Weird, eh? Is there a newer build I should try? I didn't see anything beyond 4.1.12 available. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: costin: fix reverted
I'll work on this ( I'm in the middle of something - as soon as I get some time, this is on the top of my list ). I reverted tc5 for my own convenience. I didn't revert tomcat_4_branch becuase I thought that you may want hack more there. :-) Yes, but if it brakes something... I'll revert it today - hopefully 4.1.15 is not yet built. I think the main question is if releasePageContext is required by the spec to flush() ( i.e. commit the message ) or not. The spec is not specific about this. So it is up to the implementation. :-) Good, then we *have to* avoid flushing. (better performance from the client side - Coyote makes chunking almost free already, so no gain on the server -, plus we comply better with the spirit of the specification). Performance is the secondary issue here - if the spec doesn't define it then it's a compliance bug. Side effects ( like flushing the out stream ) must be defined in the method documentation. Flushing/commiting/closing the stream is too important. Kin-Man - if you have some quick way to get a confirmation from some jsp spec people - it could save us some time :-) It seems like an unwanted Jasper limitation. We should fix it. I'll do it ASAP. Sorry I couldn't yesterday. Costin -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: costin: fix reverted
Costin Manolache wrote: I'll work on this ( I'm in the middle of something - as soon as I get some time, this is on the top of my list ). I reverted tc5 for my own convenience. I didn't revert tomcat_4_branch becuase I thought that you may want hack more there. :-) Yes, but if it brakes something... I'll revert it today - hopefully 4.1.15 is not yet built. I didn't plan to tag 4.1.15 right now. At least not before that flushing issue is resolved (ie, the flush is gone, unless it implies some major refactoring in Jasper). Performance is the secondary issue here - if the spec doesn't define it then it's a compliance bug. Side effects ( like flushing the out stream ) must be defined in the method documentation. Flushing/commiting/closing the stream is too important. Yes, I agree it could have some problematic side effects. Remy -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
RE: Tomcat 4.1.12 root context index.jsp bug
Did you make sure that the work director has been cleaned out? The compiled JSP will otherwise still sit around in there. Delete everything you find under CATALINA_BASE/work (or CATALINA_HOME/work). Martin -Original Message- From: Ian Hunter [mailto:ihunter;hunterweb.net] Sent: 05 November 2002 15:33 To: [EMAIL PROTECTED] Subject: Tomcat 4.1.12 root context index.jsp bug I have posted this in several different ways on the user list and had virtually no responses, and I believe it's a real live bug, so I'll post it here and then prepare to duck flames... Running Tomcat 4.1.12 with Sun JDK 1.4.1 on Win2K, if I change the root context to point someplace other than webapps/ROOT, I still get the default index.jsp if I request http://localhost:8080/index.jsp -- if that sounds sketchy and weird, get a load of this: I have also zipped up (removed the files from) webapps/ROOT completely (actually, webapps is completely empty), cleared my browser cache, etc. etc. and I still get the default index.jsp, but without the graphics (remember, the files are not anywhere on my drive). Further, I can successfully request any files OTHER than index.jsp (e.g. main.jsp, logon.jsp, etc. etc.) from the directory containing the new root context. Weird, eh? Is there a newer build I should try? I didn't see anything beyond 4.1.12 available. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 14059] - HTP Response does not respond correctly to flush()
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14059. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14059 HTP Response does not respond correctly to flush() --- Additional Comments From [EMAIL PROTECTED] 2002-11-05 16:03 --- Remy, In Summary: There is a difference in behavior of when TC4.0.x and Tc4.1.12 sends the end of chunk message for a response. TC4.0.x sends an end of chunk immediately following the stream close() in a servlet response. TC4.1.12 does not send the end of chunk message until the servlet exits its DoPost method. On the client side, the sun java.net implementation does not return a stream from the getInputStream() method until it receives the end of chunk message on the wire. Hence, my issues. It looks like the browsers have access to intermediate chunks. Which is why you don't see any issue. In conclusion, TC behavior HAS changed; Is it a bug? Depends on who you ask... I think the behavior change should be at least clearly documented on the TC docs if it is NOT determined to be a bug. However, I do not think the close() is being handled correctly. It is not being handled in the manner it has been in previous TC releases. I would like to hear your view on this issue. Thanks, -j.p. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-servletapi-5/jsr154/src/share/javax/servlet LocalStrings_fr.properties
jfarcand2002/11/05 08:04:36
Added: jsr154/src/share/javax/servlet LocalStrings_fr.properties
Log:
Add french translation.
Submitted by: Henry Gomez
Revision ChangesPath
1.1
jakarta-servletapi-5/jsr154/src/share/javax/servlet/LocalStrings_fr.properties
Index: LocalStrings_fr.properties
===
# Default localized string information
# Localized for Locale fr_FR
err.not_iso8859_1={0} n''est pas un caractère ISO 8859-1
value.true=true
value.false=false
# Default localized string information
# Localized for Locale fr_FR
err.cookie_name_is_token=Le nom de cookie {0} est un token réservé
err.io.negativelength=Taille négative donnée dans la méthode write
err.io.short_read=Lecture réduite
http.method_not_implemented=Le méthode {0} n''est pas définie dans la RFC 2068 et
n''est pas supportée par l''API Servlet
http.method_get_not_supported=La méthode HTTP GET n''est pas supportée par cette URL
http.method_post_not_supported=La méthode HTTP POST n''est pas supportée par cette
URL
http.method_put_not_supported=La méthode HTTP PUT n''est pas supportée par cette URL
http.method_delete_not_supported=La méthode HTTP DELETE n''est pas supportée par
cette URL
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: cvs commit: jakarta-servletapi-5/jsr154/src/share/javax/servletLocalStrings_fr.properties
err.io.short_read=Lecture réduite Could you replace by : err.io.short_read=Lecture partielle -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: french translation for servletapi (2.2)
OK c'est fait (Done :-) ) -- Jeanfrancois -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-servletapi-5/jsr154/src/share/javax/servlet LocalStrings_fr.properties
jfarcand2002/11/05 08:08:55
Modified:jsr154/src/share/javax/servlet LocalStrings_fr.properties
Log:
Minor change
Revision ChangesPath
1.2 +1 -1
jakarta-servletapi-5/jsr154/src/share/javax/servlet/LocalStrings_fr.properties
Index: LocalStrings_fr.properties
===
RCS file:
/home/cvs/jakarta-servletapi-5/jsr154/src/share/javax/servlet/LocalStrings_fr.properties,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- LocalStrings_fr.properties5 Nov 2002 16:04:36 - 1.1
+++ LocalStrings_fr.properties5 Nov 2002 16:08:54 - 1.2
-10,7 +10,7
err.cookie_name_is_token=Le nom de cookie {0} est un token réservé
err.io.negativelength=Taille négative donnée dans la méthode write
-err.io.short_read=Lecture réduite
+err.io.short_read=Lecture partielle
http.method_not_implemented=Le méthode {0} n''est pas définie dans la RFC 2068 et
n''est pas supportée par l''API Servlet
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: french translation for servletapi (2.2)
Jeanfrancois Arcand wrote: OK c'est fait (Done :-) ) Thanks to update to use partielle instead of réduite ... -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: cvs commit: jakarta-servletapi-5/jsr154/src/share/javax/servletLocalStrings_fr.properties
Don't forget also to update the second LocalString_fr.properties,
the one in javax.servlet with :
# Default localized string information
# Localized for Locale fr_FR
err.not_iso8859_1={0} n''est pas un caractère ISO 8859-1
value.true=true
value.false=false
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
French translations - who's interested ?
There is still some works to finish french translation in TC4+CATALINA2+JASPER. Who's planning to make some works ? (JFC/JFA/REMM ?) Regards -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: French translations - who's interested ?
Dispatch the files, and I will do some tonight. -- Jeanfrancois Henri Gomez wrote: There is still some works to finish french translation in TC4+CATALINA2+JASPER. Who's planning to make some works ? (JFC/JFA/REMM ?) Regards -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: French translations - who's interested ?
Henri Gomez wrote: There is still some works to finish french translation in TC4+CATALINA2+JASPER. Who's planning to make some works ? (JFC/JFA/REMM ?) Sorry I have not enough time fro the moment but I will review everything you will propose (at least I will try). Regards -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 InternalInputBuffer.java
remm2002/11/05 08:26:38 Modified:http11/src/java/org/apache/coyote/http11 InternalInputBuffer.java Log: - I think a 0 result is an error according to the JVM javadocs (we are using InputStream.read(byte[], int, int)). Revision ChangesPath 1.16 +4 -4 jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/InternalInputBuffer.java Index: InternalInputBuffer.java === RCS file: /home/cvs/jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/InternalInputBuffer.java,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- InternalInputBuffer.java 9 Apr 2002 18:35:54 - 1.15 +++ InternalInputBuffer.java 5 Nov 2002 16:26:38 - 1.16 -781,7 +781,7 } -return (nRead = 0); +return (nRead 0); } -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11InternalInputBuffer.java
[EMAIL PROTECTED] wrote: remm2002/11/05 08:26:38 Modified:http11/src/java/org/apache/coyote/http11 InternalInputBuffer.java Log: - I think a 0 result is an error according to the JVM javadocs (we are using InputStream.read(byte[], int, int)). Under unix it means that the connection was closed by remote side... -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Client-cert authentication.
I´ve a small (or big) problem configuring Tomcat 4.1.12. Does anyone know how to configure the client side of the matter? What I have done is : 1) Create a selfsigned certificate (master certificate). 2) With the master create another one intemediate for localhost (signed with the private key of the master one) - Import the chain into a keystore: server.keystore ( the master and localhost, this last one with the private key) 3) With the localhost certificate create a user certificate (signed with the private key of localhost). - Import the user certificate into the server.keystore. 4) Import the chain into a keystore: server.keystore - At this point all must be ok because the server authentication works perfectly, when a client try to connect to localhost. 5) Configure the server.xml: - Define a SSL Coyote HTTP/1.1 Connector on port 8443: Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8443 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=3 scheme=https secure=true useURIValidationHack=false - Locate the keystore inside the factory, CoyoteServerSocketFactory, with clientAuth=false. Factory className=org.apache.coyote.tomcat4.CoyoteServerSocketFactory clientAuth=false keystoreFile=C:\Documents and Settings\mserrano\.jbuilder4\Claves\CA_almacen\ca\server.keystore keystorePass=396947j protocol=TLS algorithm=SunX509 keystoreType=JKS/ 6) Configure the web.xml, if the auth.method selected is BASIC everything works fine, the problem begins when I try that a context works with client authentication. ?xml version=1.0 encoding=UTF-8? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN http://java.sun.com/j2ee/dtds/web-app_2_2.dtd; web-app display-nameadminWeb/display-name welcome-file-list welcome-fileadminWeb.jsp/welcome-file /welcome-file-list security-constraint web-resource-collection web-resource-nameadminWeb/web-resource-name url-pattern/*/url-pattern /web-resource-collection auth-constraint role-nameadmin/role-name /auth-constraint user-data-constraint transport-guaranteeCONFIDENTIAL/transport-guarantee /user-data-constraint /security-constraint login-config auth-methodCLIENT-CERT/auth-method /login-config security-role descriptionAn example role defined in conf/tomcat-users.xml/description role-nameadmin/role-name /security-role /web-app 7) In the client side: - Generate a p12 keystore in order to import the user certificate and his private key. - Import in the Client (browser) the master, the intermediate (localhost) and the user certificates. - The user certificate in the p12 format (with the private key) and the other ones with the X509 format: localhost.cer and master.cer. At the end, the result is: type Status report message No hay cadena de certificados del cliente en esta peticion description The request sent by the client was syntactically incorrect (No hay cadena de certificados del cliente en esta peticion). Using CATALINA_BASE: .. Using CATALINA_HOME: .. Using CATALINA_TMPDIR: ..\temp Using JAVA_HOME: C:\jbuilder5\jdk1.3 [INFO] Registry - -Loading registry information [INFO] Registry - -Creating new Registry instance [INFO] Registry - -Creating MBeanServer [INFO] Http11Protocol - -Initializing Coyote HTTP/1.1 on port 8080 [INFO] Http11Protocol - -Initializing Coyote HTTP/1.1 on port 8443 Starting service Tomcat-Standalone Apache Tomcat/4.1.12 [INFO] Http11Protocol - -Starting Coyote HTTP/1.1 on port 8080 [INFO] Http11Protocol - -Starting Coyote HTTP/1.1 on port 8443 javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated at com.sun.net.ssl.internal.ssl.SSLSessionImpl.getPeerCertificateChain(DashoA6275) at org.apache.tomcat.util.net.JSSESupport.getPeerCertificateChain(JSSESupport.java:118) at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:543) at org.apache.coyote.Response.action(Response.java:216) at org.apache.coyote.tomcat4.CoyoteAdapter.postParseRequest(CoyoteAdapter.java:314) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:221) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:405) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:380) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:508) at
Re: cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11InternalInputBuffer.java
Henri Gomez wrote: [EMAIL PROTECTED] wrote: remm2002/11/05 08:26:38 Modified:http11/src/java/org/apache/coyote/http11 InternalInputBuffer.java Log: - I think a 0 result is an error according to the JVM javadocs (we are using InputStream.read(byte[], int, int)). Under unix it means that the connection was closed by remote side... You're not getting an IOE in that case ? That would have caused a loop. The javadocs are very explicit on this, and 0 shouldn't even happen (I've never seen it on Windows, BTW) :-( Remy -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-servletapi-5/jsr154/src/share/javax/servlet/http LocalStrings_fr.properties
jfarcand2002/11/05 08:40:22
Added: jsr154/src/share/javax/servlet/http
LocalStrings_fr.properties
Log:
Add french translation.
Submitted by: Henry Gomez
Revision ChangesPath
1.1
jakarta-servletapi-5/jsr154/src/share/javax/servlet/http/LocalStrings_fr.properties
Index: LocalStrings_fr.properties
===
# Default localized string information
# Localized for Locale fr_FR
err.cookie_name_is_token=Le nom de cookie {0} est un token réservé
err.io.negativelength=Taille négative donnée dans la méthode write
err.io.short_read=Lecture partielle
http.method_not_implemented=Le méthode {0} n''est pas définie dans la RFC 2068 et
n''est pas supportée par l''API Servlet
http.method_get_not_supported=La méthode HTTP GET n''est pas supportée par cette URL
http.method_post_not_supported=La méthode HTTP POST n''est pas supportée par cette
URL
http.method_put_not_supported=La méthode HTTP PUT n''est pas supportée par cette URL
http.method_delete_not_supported=La méthode HTTP DELETE n''est pas supportée par
cette URL
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11InternalInputBuffer.java
Remy Maucherat wrote: Henri Gomez wrote: [EMAIL PROTECTED] wrote: remm2002/11/05 08:26:38 Modified:http11/src/java/org/apache/coyote/http11 InternalInputBuffer.java Log: - I think a 0 result is an error according to the JVM javadocs (we are using InputStream.read(byte[], int, int)). Under unix it means that the connection was closed by remote side... You're not getting an IOE in that case ? That would have caused a loop. The javadocs are very explicit on this, and 0 shouldn't even happen (I've never seen it on Windows, BTW) :-( From my experience under Unix, I could say that it happends I got a 0 from a read in a socket connection because the remote closed the connection. I don't know JVM implementators handle the case since man pages say that many 'others error could occurs depending on the object which is read' What I do usually when I read from a socket is to loop until I got a -1 (native/java) or IOE (java). So a Java read() should be valid until you got -1 or IOE. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-servletapi-5/jsr154/src/share/javax/servlet/http LocalStrings_fr.properties
jfarcand2002/11/05 08:57:36 Modified:jsr154/src/share/javax/servlet/http LocalStrings_fr.properties Log: Rrr. Commit the proper file. Revision ChangesPath 1.2 +1 -1 jakarta-servletapi-5/jsr154/src/share/javax/servlet/http/LocalStrings_fr.properties Index: LocalStrings_fr.properties === RCS file: /home/cvs/jakarta-servletapi-5/jsr154/src/share/javax/servlet/http/LocalStrings_fr.properties,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- LocalStrings_fr.properties5 Nov 2002 16:40:22 - 1.1 +++ LocalStrings_fr.properties5 Nov 2002 16:57:35 - 1.2 -10,4 +10,4 http.method_get_not_supported=La méthode HTTP GET n''est pas supportée par cette URL http.method_post_not_supported=La méthode HTTP POST n''est pas supportée par cette URL http.method_put_not_supported=La méthode HTTP PUT n''est pas supportée par cette URL -http.method_delete_not_supported=La méthode HTTP DELETE n''est pas supportée par cette URL +http.method_delete_not_supported=La méthode HTTP DELETE n''est pas supportée par cette URL -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-servletapi-5/jsr154/src/share/javax/servlet LocalStrings_fr.properties
jfarcand2002/11/05 08:57:50
Modified:jsr154/src/share/javax/servlet LocalStrings_fr.properties
Log:
idem. Commit the proper file.
Revision ChangesPath
1.3 +1 -14
jakarta-servletapi-5/jsr154/src/share/javax/servlet/LocalStrings_fr.properties
Index: LocalStrings_fr.properties
===
RCS file:
/home/cvs/jakarta-servletapi-5/jsr154/src/share/javax/servlet/LocalStrings_fr.properties,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- LocalStrings_fr.properties5 Nov 2002 16:08:54 - 1.2
+++ LocalStrings_fr.properties5 Nov 2002 16:57:50 - 1.3
-3,19 +3,6
err.not_iso8859_1={0} n''est pas un caractère ISO 8859-1
value.true=true
-value.false=false
+value.false=false
-# Default localized string information
-# Localized for Locale fr_FR
-
-err.cookie_name_is_token=Le nom de cookie {0} est un token réservé
-err.io.negativelength=Taille négative donnée dans la méthode write
-err.io.short_read=Lecture partielle
-
-http.method_not_implemented=Le méthode {0} n''est pas définie dans la RFC 2068 et
n''est pas supportée par l''API Servlet
-
-http.method_get_not_supported=La méthode HTTP GET n''est pas supportée par cette URL
-http.method_post_not_supported=La méthode HTTP POST n''est pas supportée par cette
URL
-http.method_put_not_supported=La méthode HTTP PUT n''est pas supportée par cette URL
-http.method_delete_not_supported=La méthode HTTP DELETE n''est pas supportée par
cette URL
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 14261] New: - JNDI data source not configured correctly.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14261. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14261 JNDI data source not configured correctly. Summary: JNDI data source not configured correctly. Product: Tomcat 4 Version: 4.1.12 Platform: Other OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I followed the direction on the site http://jakarta.apache.org/tomcat/tomcat- 4.1-doc/jndi-datasource-examples-howto.html and I am unable to get a connection to the datasource. I put code in the commons-dbcp code to print what is happening: On startup, I see that all of the values are set and a datasource is created. When I call lookup in my servlet, I see that only the following RefAddr's are passed in. Type: description Content: Storms Connection Type: scope Content: Shareable Type: auth Content: Container This means that no values are set in the BasicDataSource class, and when I call getConnection, it throws an error because driverClassName is null. I am specifying the datasource in the global naming section of server.xml, and am requesting it in a self deploying web application. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: Possible bug in RequestDispatcher?
I looked into this a little further. I think the resource the URL points to has a Content-Length of 234 bytes. The Filter uses RequestDispatcher.forward() to return a document that is longer, and that document is getting truncated at about 234 bytes. Could TC be setting the Content-Length header based on the originally requested document but returning the data from the forwarded one? -- Ryan Hoegg ISIS Networks http://www.isisnetworks.net Ryan Hoegg wrote: OK, that clarifies things a little bit. If the problem isn't with RequestDispatcher, I am even more puzzled. I have narrowed the problem down to a particular use case: I have a single filter that calls getFilterContext().getServletContext().getRequestDispatcher(/WEB-INF/templates/form.html).forward(request, response) in the absence of a particular session variable on the request. This filter is mapped to /* and I have a single servlet mapped to /Display Pointing my browser at /webapp/Display : things work as expected. Pointing my browser at /webapp/ : things work as expected Pointing my browser at /webapp/staticfile.html : problem. View Source in my browser shows this: - !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; html head title/title /head body form action=j_security_check method=POST pU -- That is the beginning of the html file I am trying to forward() to. It seems like my HttpServletResponse's OutputStream is getting closed prematurely in the exact same place in my forwarded file. So what could it be?! -- Ryan Hoegg ISIS Networks http://www.isisnetworks.net Craig R. McClanahan wrote: In Servlet 2.3 (i.e. Tomcat 4.x), filters are *not* invoked on request dispatcher calls -- only on the original request. In Servlet 2.4 (i.e. Tomcat 5.x) you can optionally configure which filters should be used on forwards, includes, or both, with suitable settings in web.xml. Craig -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 14261] - JNDI data source not configured correctly.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14261. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14261 JNDI data source not configured correctly. [EMAIL PROTECTED] changed: What|Removed |Added Summary|JNDI data source not|JNDI data source not |configured correctly. |configured correctly. --- Additional Comments From [EMAIL PROTECTED] 2002-11-05 17:53 --- I also tried the testing 4.1.14 release, this doesn't seem to fix the problem. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5 CoyoteOutputStream.java CoyoteResponse.java OutputBuffer.java
remm2002/11/05 10:44:55
Modified:coyote/src/java/org/apache/coyote/tomcat5
CoyoteOutputStream.java CoyoteResponse.java
OutputBuffer.java
Log:
- Clean up writer and output stream handling. close will now finish the response
on both the output stream and the writer.
- This is relatively experimental, but appears to be working fine.
Revision ChangesPath
1.2 +2 -6
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteOutputStream.java
Index: CoyoteOutputStream.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteOutputStream.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- CoyoteOutputStream.java 4 Aug 2002 19:39:49 - 1.1
+++ CoyoteOutputStream.java 5 Nov 2002 18:44:55 - 1.2
-116,17 +116,13
*/
public void flush()
throws IOException {
-if (ob.flushCharsNeeded())
-ob.flushChars();
-ob.flushBytes();
+ob.flush();
}
public void close()
throws IOException {
-if (ob.flushCharsNeeded())
-ob.flushChars();
-ob.flushBytes();
+ob.close();
}
1.10 +4 -5
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteResponse.java
Index: CoyoteResponse.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteResponse.java,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- CoyoteResponse.java 10 Oct 2002 09:45:30 - 1.9
+++ CoyoteResponse.java 5 Nov 2002 18:44:55 - 1.10
-501,7 +501,6
} catch(Throwable t) {
t.printStackTrace();
}
-coyoteResponse.finish();
}
1.2 +4 -0
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/OutputBuffer.java
Index: OutputBuffer.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/OutputBuffer.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- OutputBuffer.java 4 Aug 2002 19:39:49 - 1.1
+++ OutputBuffer.java 5 Nov 2002 18:44:55 - 1.2
-301,6 +301,8
public void close()
throws IOException {
+if (closed)
+return;
if (suspended)
return;
-320,6 +322,8
flush();
closed = true;
+
+coyoteResponse.finish();
}
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-connectors/naming/src/org/apache/naming/core ServerBinding.java NamingContextEnumeration.java
costin 2002/11/05 11:03:14
Modified:naming/src/org/apache/naming/core
NamingContextEnumeration.java
Added: naming/src/org/apache/naming/core ServerBinding.java
Log:
Delay the evaluation of getClassName and getValue until it is
needed ( in most cases it won't ).
Also allow any kind of enumerations ( including Strings ) to be used.
Revision ChangesPath
1.3 +49 -24
jakarta-tomcat-connectors/naming/src/org/apache/naming/core/NamingContextEnumeration.java
Index: NamingContextEnumeration.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/naming/src/org/apache/naming/core/NamingContextEnumeration.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- NamingContextEnumeration.java 8 Oct 2002 18:46:42 - 1.2
+++ NamingContextEnumeration.java 5 Nov 2002 19:03:14 - 1.3
-63,43 +63,50
import java.util.Hashtable;
import java.util.Vector;
import java.util.Enumeration;
-import javax.naming.NamingException;
-import javax.naming.NamingEnumeration;
-import javax.naming.NameClassPair;
+import javax.naming.*;
/**
* Naming enumeration implementation.
*
+ * TODO: implement 'throw exceptions on close' part of the spec.
+ * TODO: implement recycling ( for example on close )
+ *
* author Remy Maucherat
- * version $Revision$ $Date$
+ * author Costin Manolache
*/
-
public class NamingContextEnumeration
implements NamingEnumeration
{
-
-
-// --- Constructors
-
-
-public NamingContextEnumeration(Vector entries) {
-enum = entries.elements();
-}
-
-
-public NamingContextEnumeration(Enumeration enum) {
+/** Constructor.
+ *
+ * param enum base enumeration. Elements can be Strings, NameClassPair,
+ * Bindings or Entries, we'll provide the wrapping if needed. For String
+ * the Class and value will be lazy-loaded.
+ *
+ * param ctx. The context where this enum belongs. Used to lazy-eval
+ * the class and value
+ *
+ * param bindings If true, we'll wrap things as Binding ( true for
+ * listBindings, false for list ).
+ */
+public NamingContextEnumeration( Enumeration enum, Context ctx,
+ boolean bindings )
+{
+this.ctx = ctx;
+this.bindings=bindings;
this.enum = enum;
}
-
// -- Variables
-
+// return bindings instead of NameClassPair
+protected boolean bindings;
/**
* Underlying enumeration.
*/
protected Enumeration enum;
+protected Context ctx;
// - Public Methods
-108,7 +115,8
* Retrieves the next element in the enumeration.
*/
public Object next()
-throws NamingException {
+throws NamingException
+{
return nextElement();
}
-117,7 +125,8
* Determines whether there are any more elements in the enumeration.
*/
public boolean hasMore()
-throws NamingException {
+throws NamingException
+{
return enum.hasMoreElements();
}
-126,7 +135,9
* Closes this enumeration.
*/
public void close()
-throws NamingException {
+throws NamingException
+{
+// XXX all exceptions should be thrown on close ( AFAIK )
}
-134,10 +145,24
return enum.hasMoreElements();
}
-
public Object nextElement() {
-NamingEntry entry = (NamingEntry) enum.nextElement();
-return new NameClassPair(entry.name, entry.value.getClass().getName());
+Object next=enum.nextElement();
+if( next instanceof NamingEntry ) {
+NamingEntry entry = (NamingEntry) next;
+return new ServerBinding(entry.name, ctx, true);
+} else if( next instanceof NameClassPair ) {
+NameClassPair ncp=(NameClassPair)next;
+if( bindings )
+return new ServerBinding(ncp.getName(), ctx, true);
+return next;
+} else if( next instanceof Binding ) {
+return next;
+} else if( next instanceof String ) {
+String name=(String)next;
+return new ServerBinding( name, ctx, true );
+}
+return null;
}
+
}
1.1
jakarta-tomcat-connectors/naming/src/org/apache/naming/core/ServerBinding.java
Index: ServerBinding.java
cvs commit: jakarta-tomcat-connectors/naming/src/org/apache/naming/core BaseNaming.java
costin 2002/11/05 11:05:19
Modified:naming/src/org/apache/naming/core BaseNaming.java
Log:
Fix the child access - use Enumerations ( of something ).
Changed attribute handling.
The goal is to make it as simple as possible to write contexts
and dir contexts with the minimal ammount of methods.
( more methods could be overriden, of course )
Revision ChangesPath
1.3 +44 -34
jakarta-tomcat-connectors/naming/src/org/apache/naming/core/BaseNaming.java
Index: BaseNaming.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/naming/src/org/apache/naming/core/BaseNaming.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- BaseNaming.java 17 Oct 2002 17:32:23 - 1.2
+++ BaseNaming.java 5 Nov 2002 19:05:19 - 1.3
-240,12 +240,12
// nothing yet.
}
-// Abstract methods
+// Not so Abstract methods
// This is what a subclass should implement.
// XXX Base resolveLinks() method ?? And then use lookup without resolveLinks
flag
-/** The lookup method.
+/** The lookup method. This is the main method you should implement.
*
* param Name
* param resolveLinks. If false, this is a lookupLink call.
-256,9 +256,13
throw new OperationNotSupportedException();
}
-/** This is the main bind operation to support.
+/** The setter method. Implement it if the context is read/write.
*
- *
+ * param name
+ * param obj The object to be bound.
+ * param attrs Attributes - if this is a dir context, null otherwise
+ * param rebind What to do if the name is already bound.
+ * XXX can be further simplified - do a lookup and implement it.
*/
public void bind(Name name, Object obj, Attributes attrs, boolean rebind )
throws NamingException
-266,7 +270,7
throw new OperationNotSupportedException();
}
-/** Remove a binding
+/** Remove a binding. XXX do we need the isContext case ?
*/
public void unbind(Name name, boolean isContext)
throws NamingException
-274,21 +278,26
throw new OperationNotSupportedException();
}
-public int size() throws NamingException
-{
-return 0;
-}
+/* XXX There are 2 ways to list the childs: array ( size/elementAt ) or
+ iterator/Enumeration. Since the JNDI interface uses iteration -
+ that's what we should use.
+ */
-public Name childNameAt( int i ) throws NamingException
-{
+/** Return the child elements, if any.
+ *
+ * This is a String or Name or Binding or NameClassPari enumeration -
+ * the Context implementation will wrap it as a NamingEnumeration and
+ * construct the right information.
+ *
+ * XXX name is all we need - all other info can be extracted - with some
+ * penalty. It's easy to do some instanceof tricks to avoid it, if possible,
+ * but the goal is to make it easy to write contexts, and name should be
+ * enough.
+ */
+public Enumeration getChildren() throws NamingException {
return null;
}
-public Object childAt( int i ) throws NamingException
-{
-return null;
-}
-
public DirContext createSubcontext(Name name, Attributes attrs)
throws NamingException
{
-303,14 +312,31
Object value = lookup(oldName, false);
bind(newName, value, null, false);
unbind(oldName, true);
+
}
-public Attributes getAttributes(Name name, String[] attrIds)
+/** Implement for directories
+ *
+ */
+public Object getAttribute( Name name, String attName )
throws NamingException
{
throw new OperationNotSupportedException();
}
-
+
+public void setAttribute( Name name, String attName, Object value )
+throws NamingException
+{
+throw new OperationNotSupportedException();
+}
+
+public String[] getAttributeNames(Name name )
+throws NamingException
+{
+throw new OperationNotSupportedException();
+}
+
+
// Utils
-344,22 +370,6
-/**
- * Closes this context. This method releases this context's resources
- * immediately, instead of waiting for them to be released automatically
- * by the garbage collector.
- * This method is idempotent: invoking it on a context that has already
- * been closed has no effect. Invoking any other
cvs commit: jakarta-tomcat-connectors/naming/src/org/apache/naming/core BaseDirContext.java
costin 2002/11/05 11:06:44
Modified:naming/src/org/apache/naming/core BaseDirContext.java
Log:
Changes in attribute handling, etc.
Sorry about the big diff - I'm trying different IDEs/editors ( idea, eclipse,
netbeans ) and they seem to have some bugs..
Revision ChangesPath
1.5 +237 -274
jakarta-tomcat-connectors/naming/src/org/apache/naming/core/BaseDirContext.java
Index: BaseDirContext.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/naming/src/org/apache/naming/core/BaseDirContext.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- BaseDirContext.java 17 Oct 2002 17:32:23 - 1.4
+++ BaseDirContext.java 5 Nov 2002 19:06:44 - 1.5
@@ -3,7 +3,7 @@
*
* The Apache Software License, Version 1.1
*
- * Copyright (c) 1999 The Apache Software Foundation. All rights
+ * Copyright (c) 1999 The Apache Software Foundation. All rights
* reserved.
*
* Redistribution and use in source and binary forms, with or without
@@ -11,7 +11,7 @@
* are met:
*
* 1. Redistributions of source code must retain the above copyright
- *notice, this list of conditions and the following disclaimer.
+ *notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
*notice, this list of conditions and the following disclaimer in
@@ -19,15 +19,15 @@
*distribution.
*
* 3. The end-user documentation included with the redistribution, if
- *any, must include the following acknowlegement:
- * This product includes software developed by the
+ *any, must include the following acknowlegement:
+ * This product includes software developed by the
*Apache Software Foundation (http://www.apache.org/).
*Alternately, this acknowlegement may appear in the software itself,
*if and wherever such third-party acknowlegements normally appear.
*
* 4. The names The Jakarta Project, Tomcat, and Apache Software
*Foundation must not be used to endorse or promote products derived
- *from this software without prior written permission. For written
+ *from this software without prior written permission. For written
*permission, please contact [EMAIL PROTECTED]
*
* 5. Products derived from this software may not be called Apache
@@ -55,7 +55,7 @@
*
* [Additional notices, if required by prior licensing conditions]
*
- */
+ */
package org.apache.naming.core;
@@ -67,6 +67,7 @@
import javax.naming.directory.Attribute;
import javax.naming.directory.ModificationItem;
import javax.naming.directory.SearchControls;
+
import org.apache.tomcat.util.res.StringManager;
//import org.apache.naming.NameParserImpl;
@@ -76,7 +77,7 @@
/**
* Base Directory Context implementation. All j-t-c/naming contexts should
- * extend it.
+ * extend it.
*
* Implements all JNDI methods - if you just extend it you'll get
UnsuportedOperation.
* XXX Should it also act as introspector proxy or should we use a separate context
?
@@ -103,72 +104,29 @@
*/
public class BaseDirContext extends BaseContext implements DirContext {
-public BaseDirContext() {
-super();
-}
-
-public BaseDirContext(Hashtable env) {
-super();
-}
-
-// Abstract methods
-// This is what a subclass should implement.
-
-/** The lookup method to implement
- */
-public Object lookup(Name name, boolean resolveLinks, Object o)
-throws NamingException
+public BaseDirContext()
{
-throw new OperationNotSupportedException();
+super();
}
-public void bind(Name name, Object obj, Attributes attrs, boolean rebind )
-throws NamingException
+public BaseDirContext(Hashtable env)
{
-throw new OperationNotSupportedException();
-}
-
-public void unbind(Name name, boolean isContext)
-throws NamingException
-{
-throw new OperationNotSupportedException();
+super(env);
}
-public DirContext createSubcontext(Name name, Attributes attrs)
-throws NamingException
-{
-// XXX We can implement a decent default using bind and the current class.
-throw new OperationNotSupportedException();
-}
-public void rename(Name oldName, Name newName)
-throws NamingException
-{
-// Override if needed
-Object value = lookup(oldName);
-bind(newName, value);
-unbind(oldName);
-}
-
-public Attributes getAttributes(Name name, String[]
cvs commit: jakarta-tomcat-connectors/naming/src/org/apache/naming/core NamingContextBindingsEnumeration.java
costin 2002/11/05 11:07:19 Removed: naming/src/org/apache/naming/core NamingContextBindingsEnumeration.java Log: No need for this. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-connectors/naming/src/org/apache/naming/core BaseContext.java
costin 2002/11/05 11:06:59
Modified:naming/src/org/apache/naming/core BaseContext.java
Log:
Similar changes for the base context
Revision ChangesPath
1.2 +226 -254
jakarta-tomcat-connectors/naming/src/org/apache/naming/core/BaseContext.java
Index: BaseContext.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/naming/src/org/apache/naming/core/BaseContext.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- BaseContext.java 17 Oct 2002 16:44:14 - 1.1
+++ BaseContext.java 5 Nov 2002 19:06:59 - 1.2
@@ -3,7 +3,7 @@
*
* The Apache Software License, Version 1.1
*
- * Copyright (c) 1999 The Apache Software Foundation. All rights
+ * Copyright (c) 1999 The Apache Software Foundation. All rights
* reserved.
*
* Redistribution and use in source and binary forms, with or without
@@ -11,7 +11,7 @@
* are met:
*
* 1. Redistributions of source code must retain the above copyright
- *notice, this list of conditions and the following disclaimer.
+ *notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
*notice, this list of conditions and the following disclaimer in
@@ -19,15 +19,15 @@
*distribution.
*
* 3. The end-user documentation included with the redistribution, if
- *any, must include the following acknowlegement:
- * This product includes software developed by the
+ *any, must include the following acknowlegement:
+ * This product includes software developed by the
*Apache Software Foundation (http://www.apache.org/).
*Alternately, this acknowlegement may appear in the software itself,
*if and wherever such third-party acknowlegements normally appear.
*
* 4. The names The Jakarta Project, Tomcat, and Apache Software
*Foundation must not be used to endorse or promote products derived
- *from this software without prior written permission. For written
+ *from this software without prior written permission. For written
*permission, please contact [EMAIL PROTECTED]
*
* 5. Products derived from this software may not be called Apache
@@ -55,7 +55,7 @@
*
* [Additional notices, if required by prior licensing conditions]
*
- */
+ */
package org.apache.naming.core;
@@ -67,6 +67,7 @@
import javax.naming.directory.Attribute;
import javax.naming.directory.ModificationItem;
import javax.naming.directory.SearchControls;
+
import org.apache.tomcat.util.res.StringManager;
// Based on a merge of various catalina naming contexts
@@ -99,334 +100,316 @@
}
-// Context impl
-
+// Context impl
+
/**
- * Retrieves the named object. If name is empty, returns a new instance
- * of this context (which represents the same naming context as this
- * context, but its environment may be modified independently and it may
+ * Retrieves the named object. If name is empty, returns a new instance
+ * of this context (which represents the same naming context as this
+ * context, but its environment may be modified independently and it may
* be accessed concurrently).
- *
+ *
* @param name the name of the object to look up
* @return the object bound to name
* @exception NamingException if a naming exception is encountered
*/
public Object lookup(Name name)
-throws NamingException
-{
-return lookup(name, true );
+throws NamingException {
+return lookup(name, true);
}
/**
* Retrieves the named object.
- *
+ *
* @param name the name of the object to look up
* @return the object bound to name
* @exception NamingException if a naming exception is encountered
*/
public Object lookup(String name)
-throws NamingException
-{
-return lookup( string2Name(name), true);
+throws NamingException {
+return lookup(string2Name(name), true);
}
/**
- * Binds a name to an object. All intermediate contexts and the target
- * context (that named by all but terminal atomic component of the name)
+ * Binds a name to an object. All intermediate contexts and the target
+ * context (that named by all but terminal atomic component of the name)
* must already exist.
- *
+ *
* @param name the name to bind; may not be empty
* @param obj the object to bind; possibly null
* @exception
cvs commit: jakarta-tomcat-connectors/naming/src/org/apache/naming/modules/memory MemoryNamingContext.java
costin 2002/11/05 11:07:59
Modified:naming/src/org/apache/naming/modules/fs FileDirContext.java
naming/src/org/apache/naming/modules/java
SelectorContext.java
naming/src/org/apache/naming/modules/memory
MemoryNamingContext.java
Log:
Small adjustments for the api changes.
Revision ChangesPath
1.4 +2 -2
jakarta-tomcat-connectors/naming/src/org/apache/naming/modules/fs/FileDirContext.java
Index: FileDirContext.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/naming/src/org/apache/naming/modules/fs/FileDirContext.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- FileDirContext.java 17 Oct 2002 16:49:03 - 1.3
+++ FileDirContext.java 5 Nov 2002 19:07:59 - 1.4
-362,7 +362,7
Vector entries = list(file);
-return new NamingContextEnumeration(entries);
+return new NamingContextEnumeration(entries.elements(), this, false);
}
-393,7 +393,7
Vector entries = list(file);
-return new NamingContextBindingsEnumeration(entries);
+return new NamingContextEnumeration(entries.elements(), this, true);
}
1.3 +3 -12
jakarta-tomcat-connectors/naming/src/org/apache/naming/modules/java/SelectorContext.java
Index: SelectorContext.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/naming/src/org/apache/naming/modules/java/SelectorContext.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- SelectorContext.java 8 Oct 2002 18:46:43 - 1.2
+++ SelectorContext.java 5 Nov 2002 19:07:59 - 1.3
-69,6 +69,7
import org.apache.tomcat.util.res.StringManager;
import org.apache.naming.modules.memory.*;
+import org.apache.naming.core.*;
/* This delegates to another context, removing a prefix.
XXX make it generic, move to core. The context thread can be
-80,7 +81,7
*
* author Remy Maucherat
*/
-public class SelectorContext implements Context {
+public class SelectorContext extends BaseContext {
// -- Constants
-110,7 +111,7
* Builds a Catalina selector context using the given environment.
*/
public SelectorContext(Hashtable env) {
-this.env = env;
+super( env );
}
-150,16 +151,6
// Context Methods
-/**
- * Retrieves the named object. If name is empty, returns a new instance
- * of this context (which represents the same naming context as this
- * context, but its environment may be modified independently and it may
- * be accessed concurrently).
- *
- * param name the name of the object to look up
- * return the object bound to name
- * exception NamingException if a naming exception is encountered
- */
public Object lookup(Name name)
throws NamingException {
// Strip the URL header
1.4 +3 -3
jakarta-tomcat-connectors/naming/src/org/apache/naming/modules/memory/MemoryNamingContext.java
Index: MemoryNamingContext.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/naming/src/org/apache/naming/modules/memory/MemoryNamingContext.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- MemoryNamingContext.java 17 Oct 2002 16:49:30 - 1.3
+++ MemoryNamingContext.java 5 Nov 2002 19:07:59 - 1.4
-188,7 +188,7
name = name.getSuffix(1);
if (name.isEmpty()) {
-return new NamingContextEnumeration(bindings.elements());
+return new NamingContextEnumeration(bindings.elements(), this, false);
}
NamingEntry entry = (NamingEntry) bindings.get(name.get(0));
-231,7 +231,7
name = name.getSuffix(1);
if (name.isEmpty()) {
-return new NamingContextBindingsEnumeration(bindings.elements());
+return new NamingContextEnumeration(bindings.elements(), this, true);
}
NamingEntry entry = (NamingEntry) bindings.get(name.get(0));
-313,7 +313,7
NamingEntry entry=findNamingEntry( name, resolveLinks );
if( entry.type == NamingEntry.CONTEXT ) {
-return ((BaseDirContext) entry.value).lookup(name.getSuffix(1),
resolveLinks, o);
+return ((BaseDirContext) entry.value).lookup(name.getSuffix(1),
cvs commit: jakarta-tomcat-5 build.xml build.properties.default
costin 2002/11/05 11:25:50
Modified:.build.xml build.properties.default
Log:
Get modeler from cvs ( for now )
Revision ChangesPath
1.56 +20 -0 jakarta-tomcat-5/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-5/build.xml,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -r1.55 -r1.56
--- build.xml 29 Oct 2002 18:07:37 - 1.55
+++ build.xml 5 Nov 2002 19:25:49 - 1.56
-248,9 +248,20
/ant
/target
+ target name=build-commons-modeler unless=commons-modeler.build.notrequired
+echo== Building: commons-modeler /echo
+
+ant dir=${cvs.base}/jakarta-commons/modeler target=compile-only
+property name=commons-logging.jar
location=${tomcat.build}/server/lib/commons-logging.jar /
+property name=commons-modeler.jar
location=${tomcat.build}/server/lib/commons-modeler.jar /
+property name=build.home value=${tomcat.build} /
+/ant
+ /target
+
target name=build-depends depends=init
description=Builds various dependent components
antcall target=build-commons-logging /
+antcall target=build-commons-modeler /
/target
-836,10 +847,19
param name=destdir value=${base.path}/
/antcall
+!--
antcall target=downloadgz
param name=sourcefile value=${commons-modeler.loc}/
param name=destfile value=${commons-modeler.jar}/
/antcall
+--
+
+antcall target=cvsbuild
+ param name=location value=${commons-modeler.cvs.loc}/
+ param name=subdir value=${commons-modeler.home}/
+ param name=destfile value=${commons-modeler.jar}/
+/antcall
+
antcall target=downloadzip
param name=sourcefile value=${javaservice.loc}/
param name=destfile value=${javaservice.exe}/
1.50 +6 -3 jakarta-tomcat-5/build.properties.default
Index: build.properties.default
===
RCS file: /home/cvs/jakarta-tomcat-5/build.properties.default,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -r1.49 -r1.50
--- build.properties.default 29 Oct 2002 18:07:37 - 1.49
+++ build.properties.default 5 Nov 2002 19:25:49 - 1.50
-134,10 +134,13
# - Commons Modeler, version 1.0 or later -
-commons-modeler.home=${base.path}/commons-modeler-1.0
-commons-modeler.lib=${commons-modeler.home}
+commons-modeler.home=${base.path}/commons-modeler-1.1dev
+#commons-modeler.home=${base.path}/commons-modeler-1.0
+#commons-modeler.lib=${commons-modeler.home}
+commons-modeler.lib=${commons-modeler.home}/dist
commons-modeler.jar=${commons-modeler.lib}/commons-modeler.jar
commons-modeler.loc=http://jakarta.apache.org/builds/jakarta-commons/release/commons-modeler/v1.0/commons-modeler-1.0.tar.gz
+commons-modeler.cvs.loc=jakarta-commons/modeler
# - Commons Pool, version 1.0.1 or later -
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 14270] New: - Jsp throws a an IOException Stream Closed when reading from a URLConnection
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14270. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14270 Jsp throws a an IOException Stream Closed when reading from a URLConnection Summary: Jsp throws a an IOException Stream Closed when reading from a URLConnection Product: Tomcat 4 Version: 4.0 Beta 1 Platform: Sun OS/Version: Solaris Status: NEW Severity: Critical Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hi, I have a JSP that creates a URLConnection to another jsp in a differet instance of Tomcat and posts the user inputs to it.Th other JSPreads the input and sends back a file to the requesting jsp.The requesting jsp should be able to read the stream and pass back the file to the user.Now when the first jsp tries to read the InputStream from the URLCOnnection, an IOException is thrown saying Stream closed.This occurs when I have the first jsp deployed under Tomcat in Solaris 2.6.The same JSP under Tomcat 4.0.1 in Windows NT Workstation works fine.I can also run a JUnit test case against the second JSP using a URLConnection and the file is downloaded fine.It is only when I use the first jsp to connect to the second jsp that I see the error and that too in Solaris.The Stack Trace I print out is ava.io.IOException: Stream closed. at java.net.PlainSocketImpl.available(PlainSocketImpl.java:387) at java.net.SocketInputStream.available(SocketInputStream.java:179) at java.io.BufferedInputStream.available(BufferedInputStream.java:337) at sun.net.www.http.ChunkedInputStream.readAheadNonBlocking (ChunkedInputStream.java:473) at sun.net.www.http.ChunkedInputStream.readAhead (ChunkedInputStream.java:586) at sun.net.www.http.ChunkedInputStream.available (ChunkedInputStream.java:694) at java.io.FilterInputStream.available(FilterInputStream.java:146) at org.apache.jsp.CertRetriever$jsp._jspService (CertRetriever$jsp.java:123) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service (JspServlet.java:202) at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:382) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:193) ... Please help. Thanks, Harini -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 14195] - NPE from dispatch() when no errCode
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14195. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14195 NPE from dispatch() when no errCode --- Additional Comments From [EMAIL PROTECTED] 2002-11-05 20:34 --- Sorry, Hans, I had forgotten to backport this fix. I just did, so it will be picked up by TC 4.1.15. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 14273] New: - Unable to invoke a fragment within a tag in a tag file
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14273. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14273 Unable to invoke a fragment within a tag in a tag file Summary: Unable to invoke a fragment within a tag in a tag file Product: Tomcat 5 Version: Unknown Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Jasper2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If there is a tag file that contains a tag( simple or classic), and within the body of the tag a fragment is invoked using the jsp:invoke action, the tag file throws a compilation error. e.g: !-- a.tag -- %@attribute name=frag fragment=true % ct:complexTag var=foo jsp:invoke fragment=frag / /ct:complexTag In this case the _jspx_out that is passed to the getFrag.invoke(...) creates the problem, as the compler finds that this is not defined in the helper class. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler DefaultErrorHandler.java ErrorDispatcher.java ErrorHandler.java
luehe 2002/11/05 12:30:25
Modified:jasper2/src/share/org/apache/jasper/compiler Tag:
tomcat_4_branch DefaultErrorHandler.java
ErrorDispatcher.java ErrorHandler.java
Log:
Fixed Bugzilla 14195: NPE from dispatch() when no errCode
Revision ChangesPath
No revision
No revision
1.1.1.1.2.1 +15 -5
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/DefaultErrorHandler.java
Index: DefaultErrorHandler.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/DefaultErrorHandler.java,v
retrieving revision 1.1.1.1
retrieving revision 1.1.1.1.2.1
diff -u -r1.1.1.1 -r1.1.1.1.2.1
--- DefaultErrorHandler.java 28 Mar 2002 18:46:18 - 1.1.1.1
+++ DefaultErrorHandler.java 5 Nov 2002 20:30:25 - 1.1.1.1.2.1
-90,9 +90,19
* param exception Parse exception
*/
public void jspError(String fname, int line, int column, String errMsg,
- Exception exception) throws JasperException {
+ Exception ex) throws JasperException {
throw new JasperException(fname + ( + line + , + column + )
- + + errMsg);
+ + + errMsg, ex);
+}
+
+/*
+ * Processes the given JSP parse error.
+ *
+ * param errMsg Parse error message
+ * param exception Parse exception
+ */
+public void jspError(String errMsg, Exception ex) throws JasperException {
+ throw new JasperException(errMsg, ex);
}
/*
1.2.2.1 +20 -6
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/ErrorDispatcher.java
Index: ErrorDispatcher.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/ErrorDispatcher.java,v
retrieving revision 1.2
retrieving revision 1.2.2.1
diff -u -r1.2 -r1.2.2.1
--- ErrorDispatcher.java 15 May 2002 20:42:03 - 1.2
+++ ErrorDispatcher.java 5 Nov 2002 20:30:25 - 1.2.2.1
-391,30 +391,44
private void dispatch(Mark where, String errCode, Object[] args,
Exception e) throws JasperException {
String file = null;
+ String errMsg = null;
int line = -1;
int column = -1;
+ boolean hasLocation = false;
// Localize
- String errMsg = getString(errCode, args);
+ if (errCode != null) {
+ errMsg = getString(errCode, args);
+ } else if (e != null) {
+ // give a hint about what's wrong
+ errMsg = e.getMessage();
+ }
// Get error location
if (where != null) {
file = where.getFile();
line = where.getLineNumber();
column = where.getColumnNumber();
+ hasLocation = true;
} else if (e instanceof SAXParseException) {
file = ((SAXParseException) e).getSystemId();
line = ((SAXParseException) e).getLineNumber();
column = ((SAXParseException) e).getColumnNumber();
+ hasLocation = true;
}
// Get nested exception
Exception nestedEx = e;
- if (e instanceof SAXException) {
+ if ((e instanceof SAXException)
+ (((SAXException) e).getException() != null)) {
nestedEx = ((SAXException) e).getException();
}
- errHandler.jspError(file, line, column, errMsg, nestedEx);
+ if (hasLocation) {
+ errHandler.jspError(file, line, column, errMsg, nestedEx);
+ } else {
+ errHandler.jspError(errMsg, nestedEx);
+ }
}
/*
1.1.1.1.2.1 +12 -3
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/ErrorHandler.java
Index: ErrorHandler.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/ErrorHandler.java,v
retrieving revision 1.1.1.1
retrieving revision 1.1.1.1.2.1
diff -u -r1.1.1.1 -r1.1.1.1.2.1
--- ErrorHandler.java 28 Mar 2002 18:46:18 - 1.1.1.1
+++ ErrorHandler.java 5 Nov 2002 20:30:25 - 1.1.1.1.2.1
-88,6 +88,15
Exception exception) throws JasperException;
/**
+ * Processes the given JSP parse error.
+ *
+ * param errMsg Parse error message
+ * param exception Parse exception
+ */
+public void jspError(String msg, Exception exception)
+ throws JasperException;
+
+/**
* Processes the given javac compilation errors.
*
* param details Array of JavacErrorDetail
Re: Client-cert authentication.
As someone else already pointed out, you need to configure the trust stores (Which tell tomcat what clients to trust.) You can do that by changing some config files, or like this on the command line (with redhat) export CATALINA_OPTS=-Djavax.net.ssl.trustStore=/home/bob/cacerts.jks -Djavax.net.ssl.trustStorePassword=changeit Cheers, -bob export CATALINA -Djavax.net.ssl.trustStore=/home/bob/issues/ssl/cacerts.jks -Djavax.net.ssl.trustStorePassword=changeit On Tue, 2002-11-05 at 11:35, Moisés Serrano Martínez wrote: I´ve a small (or big) problem configuring Tomcat 4.1.12. Does anyone know how to configure the client side of the matter? What I have done is : 1) Create a selfsigned certificate (master certificate). 2) With the master create another one intemediate for localhost (signed with the private key of the master one) - Import the chain into a keystore: server.keystore ( the master and localhost, this last one with the private key) 3) With the localhost certificate create a user certificate (signed with the private key of localhost). - Import the user certificate into the server.keystore. 4) Import the chain into a keystore: server.keystore - At this point all must be ok because the server authentication works perfectly, when a client try to connect to localhost. 5) Configure the server.xml: - Define a SSL Coyote HTTP/1.1 Connector on port 8443: Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8443 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=3 scheme=https secure=true useURIValidationHack=false - Locate the keystore inside the factory, CoyoteServerSocketFactory, with clientAuth=false. Factory className=org.apache.coyote.tomcat4.CoyoteServerSocketFactory clientAuth=false keystoreFile=C:\Documents and Settings\mserrano\.jbuilder4\Claves\CA_almacen\ca\server.keystore keystorePass=396947j protocol=TLS algorithm=SunX509 keystoreType=JKS/ 6) Configure the web.xml, if the auth.method selected is BASIC everything works fine, the problem begins when I try that a context works with client authentication. ?xml version=1.0 encoding=UTF-8? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN http://java.sun.com/j2ee/dtds/web-app_2_2.dtd; web-app display-nameadminWeb/display-name welcome-file-list welcome-fileadminWeb.jsp/welcome-file /welcome-file-list security-constraint web-resource-collection web-resource-nameadminWeb/web-resource-name url-pattern/*/url-pattern /web-resource-collection auth-constraint role-nameadmin/role-name /auth-constraint user-data-constraint transport-guaranteeCONFIDENTIAL/transport-guarantee /user-data-constraint /security-constraint login-config auth-methodCLIENT-CERT/auth-method /login-config security-role descriptionAn example role defined in conf/tomcat-users.xml/description role-nameadmin/role-name /security-role /web-app 7) In the client side: - Generate a p12 keystore in order to import the user certificate and his private key. - Import in the Client (browser) the master, the intermediate (localhost) and the user certificates. - The user certificate in the p12 format (with the private key) and the other ones with the X509 format: localhost.cer and master.cer. At the end, the result is: type Status report message No hay cadena de certificados del cliente en esta peticion description The request sent by the client was syntactically incorrect (No hay cadena de certificados del cliente en esta peticion). Using CATALINA_BASE: .. Using CATALINA_HOME: .. Using CATALINA_TMPDIR: ..\temp Using JAVA_HOME: C:\jbuilder5\jdk1.3 [INFO] Registry - -Loading registry information [INFO] Registry - -Creating new Registry instance [INFO] Registry - -Creating MBeanServer [INFO] Http11Protocol - -Initializing Coyote HTTP/1.1 on port 8080 [INFO] Http11Protocol - -Initializing Coyote HTTP/1.1 on port 8443 Starting service Tomcat-Standalone Apache Tomcat/4.1.12 [INFO] Http11Protocol - -Starting Coyote HTTP/1.1 on port 8080 [INFO] Http11Protocol - -Starting Coyote HTTP/1.1 on port 8443 javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated at com.sun.net.ssl.internal.ssl.SSLSessionImpl.getPeerCertificateChain(DashoA6275) at org.apache.tomcat.util.net.JSSESupport.getPeerCertificateChain(JSSESupport.java:118) at
DO NOT REPLY [Bug 14275] New: - Problems creating DataSource
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14275. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14275 Problems creating DataSource Summary: Problems creating DataSource Product: Tomcat 4 Version: 4.1.12 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The following exception is thrown by BasicDataSource while adding an entry to the MSSQL database. Here is the stack trace: java.sql.SQLException: Cannot load JDBC driver class 'null' at org.apache.commons.dbcp.BasicDataSource.createDataSource (BasicDataSource.java:529) at org.apache.commons.dbcp.BasicDataSource.getConnection (BasicDataSource.java:312) at administration.FaqRepository.init(Unknown Source) at administration.FaqRepository.getInstance(Unknown Source) at administration.AddCommand.execute(Unknown Source) at administration.FaqAdminServlet.service(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke (StandardWrapperValve.java:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke (StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke (StandardContext.java:2396) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke (ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service (CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process (Http11Processor.java:405) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnectio n(Http11Protocol.java:380) at org.apache.tomcat.util.net.TcpWorkerThread.runIt (PoolTcpEndpoint.java:508) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (ThreadPool.java:533) at java.lang.Thread.run(Thread.java:484) This happens when an entry is added to the database; Here is the section that pertains resource name jdbc/Questions: Resource name=jdbc/Questions scope=Shareable type=javax.sql.DataSource/ Resource name=UserDatabase scope=Shareable type=org.apache.catalina.UserDatabase auth=Container description=User database that can be updated and saved/ ResourceParams name=jdbc/Questions parameter namevalidationQuery/name value/value /parameter parameter namemaxWait/name value5000/value /parameter parameter namemaxActive/name value4/value /parameter parameter namepassword/name value/value /parameter parameter nameurl/name
Tomcat Architecture: XML
I am interested in a particular part of the Tomcat architecture, and NOT the relations between the containers, and the normal development stuff. The use of xml is what interests me, and I cannot find any stuff on how this works IN TOMCAT/CATALINA. I know how xml works. What I would like to know is how the xml works in relation to the applications IN TOMCAT/CATALINA. Is the xml in server.xml used as part of a design pattern using Java reflection? What about the web.xml? Is the way various xml files are used pretty standard, or are there great variations in Tomcat, struts, etc. across the jakarta platforms. I keep trying to find this stuff out, and have had little luck. I need to know the details before I understand something. I hope this is not too dumb of a question. Micael --- This electronic mail transmission and any accompanying documents contain information belonging to the sender which may be confidential and legally privileged. This information is intended only for the use of the individual or entity to whom this electronic mail transmission was sent as indicated above. If you are not the intended recipient, any disclosure, copying, distribution, or action taken in reliance on the contents of the information contained in this transmission is strictly prohibited. If you have received this transmission in error, please delete the message. Thank you -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: Tomcat Architecture: XML
Micael, all the magic reside under the Digester component used by Tomcat to parse xml file. http://jakarta.apache.org/commons/digester.html Enjoys! -- Jeanfrancois micael wrote: I am interested in a particular part of the Tomcat architecture, and NOT the relations between the containers, and the normal development stuff. The use of xml is what interests me, and I cannot find any stuff on how this works IN TOMCAT/CATALINA. I know how xml works. What I would like to know is how the xml works in relation to the applications IN TOMCAT/CATALINA. Is the xml in server.xml used as part of a design pattern using Java reflection? What about the web.xml? Is the way various xml files are used pretty standard, or are there great variations in Tomcat, struts, etc. across the jakarta platforms. I keep trying to find this stuff out, and have had little luck. I need to know the details before I understand something. I hope this is not too dumb of a question. Micael --- This electronic mail transmission and any accompanying documents contain information belonging to the sender which may be confidential and legally privileged. This information is intended only for the use of the individual or entity to whom this electronic mail transmission was sent as indicated above. If you are not the intended recipient, any disclosure, copying, distribution, or action taken in reliance on the contents of the information contained in this transmission is strictly prohibited. If you have received this transmission in error, please delete the message. Thank you -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Client-cert and POST
I have been snooping around this problem with client-cert and POSTs for
quite a while now. I have a patch that fixes it, but I really don't
like my own work.
This topic has raised it's ugly head a few times already here on
Tomcat-dev, but allow me to restate it (yet again... hopefully with more
clarity)
Clients can POST data to Tomcat. They can do this on a secure socket.
Tomcat can be configured to protect resources from the client based on
the clients Certificates. So, a client can be POSTing data to a secure
resource and tomcat may not yet have gotten the Certificates it needs.
HERE IS WHERE STUFF GETS TRICKY (could I be wrong?) The certificate
exchange can only happen once the POST data is removed from the socket.
I talked with someone who implemented an SSL stack and he said that this
is the way the protocol is. Boo. So in order to support work
correctly, Tomcat must hold onto this POST until it is done, then
certify the client, then proceed or bail. Messy messy.
I tweaked Tomcat5 Coyote to do this.
It works by changing CoyoteRequest to change the InputStream to a
Buffered InputStream when a POST and an SSL Certrequest happen.
What do you think?
Cheers,
-bob
Index: CoyoteRequest.java
===
RCS file: /home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteRequest.java,v
retrieving revision 1.6
diff -u -r1.6 CoyoteRequest.java
--- CoyoteRequest.java 18 Oct 2002 21:37:08 - 1.6
+++ CoyoteRequest.java 5 Nov 2002 21:25:45 -
@@ -377,7 +377,10 @@
pathInfo = null;
servletPath = null;
reader = null;
-inputStream.recycle();
+if (inputStream instanceof CoyoteBufferedInputStream )
+inputStream = new CoyoteInputStream();
+else
+inputStream.recycle();
userPrincipal = null;
sessionParsed = false;
authorization = null;
@@ -783,6 +786,22 @@
return attr;
// XXX Should move to Globals
if(Constants.SSL_CERTIFICATE_ATTR.equals(name)) {
+if ( POST.equalsIgnoreCase(getMethod()) ){
+String contentType = getContentType();
+if (contentType == null)
+contentType = ;
+int semicolon = contentType.indexOf(';');
+if (semicolon = 0) {
+contentType = contentType.substring(0, semicolon).trim();
+} else {
+contentType = contentType.trim();
+}
+
+if ((application/x-www-form-urlencoded.equals(contentType)))
+parseRequestParameters();
+else
+inputStream = new CoyoteBufferedInputStream( this );
+}
coyoteRequest.action(ActionCode.ACTION_REQ_SSL_CERTIFICATE, null);
attr = getAttribute(Globals.CERTIFICATES_ATTR);
if(attr != null)
/*
*
*
* The Apache Software License, Version 1.1
*
* Copyright (c) 1999 The Apache Software Foundation. All rights
* reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
*notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
*notice, this list of conditions and the following disclaimer in
*the documentation and/or other materials provided with the
*distribution.
*
* 3. The end-user documentation included with the redistribution, if
*any, must include the following acknowlegement:
* This product includes software developed by the
*Apache Software Foundation (http://www.apache.org/).
*Alternately, this acknowlegement may appear in the software itself,
*if and wherever such third-party acknowlegements normally appear.
*
* 4. The names The Jakarta Project, Tomcat, and Apache Software
*Foundation must not be used to endorse or promote products derived
*from this software without prior written permission. For written
*permission, please contact [EMAIL PROTECTED]
*
* 5. Products derived from this software may not be called Apache
*nor may Apache appear in their names without prior written
*permission of the Apache Group.
*
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
* WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
* LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core ContainerBase.java
costin 2002/11/05 13:31:14
Modified:catalina/src/share/org/apache/catalina/core
ContainerBase.java
Log:
Prevent stoping apps that are not started ( and the
associated traces )
Revision ChangesPath
1.2 +40 -34
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/ContainerBase.java
Index: ContainerBase.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/ContainerBase.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ContainerBase.java18 Jul 2002 16:48:12 - 1.1
+++ ContainerBase.java5 Nov 2002 21:31:14 - 1.2
-381,7 +381,7
try {
((Lifecycle) oldLoader).stop();
} catch (LifecycleException e) {
-log(ContainerBase.setLoader: stop: , e);
+log.error(ContainerBase.setLoader: stop: , e);
}
}
-393,7 +393,7
try {
((Lifecycle) loader).start();
} catch (LifecycleException e) {
-log(ContainerBase.setLoader: start: , e);
+log.error(ContainerBase.setLoader: start: , e);
}
}
-438,7 +438,7
try {
((Lifecycle) oldLogger).stop();
} catch (LifecycleException e) {
-log(ContainerBase.setLogger: stop: , e);
+log.error(ContainerBase.setLogger: stop: , e);
}
}
-450,7 +450,7
try {
((Lifecycle) logger).start();
} catch (LifecycleException e) {
-log(ContainerBase.setLogger: start: , e);
+log.error(ContainerBase.setLogger: start: , e);
}
}
-495,7 +495,7
try {
((Lifecycle) oldManager).stop();
} catch (LifecycleException e) {
-log(ContainerBase.setManager: stop: , e);
+log.error(ContainerBase.setManager: stop: , e);
}
}
-507,7 +507,7
try {
((Lifecycle) manager).start();
} catch (LifecycleException e) {
-log(ContainerBase.setManager: start: , e);
+log.error(ContainerBase.setManager: start: , e);
}
}
-535,7 +535,7
/**
* Set the Cluster with which this Container is associated.
*
- * param manager The newly associated Cluster
+ * param cluster The newly associated Cluster
*/
public synchronized void setCluster(Cluster cluster) {
// Change components if necessary
-550,7 +550,7
try {
((Lifecycle) oldCluster).stop();
} catch (LifecycleException e) {
-log(ContainerBase.setCluster: stop: , e);
+log.error(ContainerBase.setCluster: stop: , e);
}
}
-563,7 +563,7
try {
((Lifecycle) cluster).start();
} catch (LifecycleException e) {
-log(ContainerBase.setCluster: start: , e);
+log.error(ContainerBase.setCluster: start: , e);
}
}
-641,11 +641,11
* been configured.
*/
public ClassLoader getParentClassLoader() {
-
if (parentClassLoader != null)
return (parentClassLoader);
-if (parent != null)
+if (parent != null) {
return (parent.getParentClassLoader());
+}
return (ClassLoader.getSystemClassLoader());
}
-661,7 +661,6
* param parent The new parent class loader
*/
public void setParentClassLoader(ClassLoader parent) {
-
ClassLoader oldParentClassLoader = this.parentClassLoader;
this.parentClassLoader = parent;
support.firePropertyChange(parentClassLoader, oldParentClassLoader,
-716,7 +715,7
try {
((Lifecycle) oldRealm).stop();
} catch (LifecycleException e) {
-log(ContainerBase.setRealm: stop: , e);
+log.error(ContainerBase.setRealm: stop: , e);
}
}
-728,7 +727,7
try {
((Lifecycle) realm).start();
} catch (LifecycleException e) {
-log(ContainerBase.setRealm: start: , e);
+log.error(ContainerBase.setRealm: start: , e);
}
}
-745,7 +744,6
* return codenull/code.
*/
public DirContext getResources() {
-
if (resources != null)
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core StandardWrapper.java
costin 2002/11/05 13:35:00
Modified:catalina/src/share/org/apache/catalina/core
StandardWrapper.java
Log:
Use commons-logging.
Add a short message for servlets that take a long time to load
( right now it's 200 ms - we can increase it, but no need to
make it configurable, it's mostly do debug perf. ).
I used idea to edit the file - and it removed unused imports and
forced me to fix some name mismatches... Probably should go back
to emacs...
Revision ChangesPath
1.7 +40 -53
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardWrapper.java
Index: StandardWrapper.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardWrapper.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- StandardWrapper.java 16 Oct 2002 15:42:09 - 1.6
+++ StandardWrapper.java 5 Nov 2002 21:35:00 - 1.7
-65,43 +65,17
package org.apache.catalina.core;
-import java.io.File;
-import java.io.IOException;
-import java.io.PrintStream;
-import java.net.URL;
-import java.util.Enumeration;
-import java.util.HashMap;
-import java.util.Stack;
-import javax.servlet.Servlet;
-import javax.servlet.ServletConfig;
-import javax.servlet.ServletContext;
-import javax.servlet.ServletException;
-import javax.servlet.SingleThreadModel;
-import javax.servlet.UnavailableException;
-import javax.servlet.http.HttpServletResponse;
-import org.apache.catalina.Container;
-import org.apache.catalina.ContainerServlet;
-import org.apache.catalina.Context;
-import org.apache.catalina.InstanceEvent;
-import org.apache.catalina.InstanceListener;
-import org.apache.catalina.Lifecycle;
-import org.apache.catalina.LifecycleException;
-import org.apache.catalina.Loader;
-import org.apache.catalina.Logger;
-import org.apache.catalina.Request;
-import org.apache.catalina.Response;
-import org.apache.catalina.Wrapper;
-import javax.servlet.ServletRequest;
-import javax.servlet.ServletResponse;
-import org.apache.catalina.loader.StandardClassLoader;
+import org.apache.catalina.*;
+import org.apache.catalina.security.SecurityUtil;
import org.apache.catalina.util.Enumerator;
import org.apache.catalina.util.InstanceSupport;
-import org.apache.catalina.security.SecurityUtil;
import org.apache.tomcat.util.log.SystemLogHandler;
-import java.security.PrivilegedActionException;
-import java.security.PrivilegedExceptionAction;
-import javax.security.auth.Subject;
+import javax.servlet.*;
+import java.io.PrintStream;
+import java.util.Enumeration;
+import java.util.HashMap;
+import java.util.Stack;
/**
* Standard implementation of the bWrapper/b interface that represents
* an individual servlet definition. No child Containers are allowed, and
-116,7 +90,8
extends ContainerBase
implements ServletConfig, Wrapper {
-
+private static org.apache.commons.logging.Log log=
+org.apache.commons.logging.LogFactory.getLog( StandardWrapper.class );
// --- Constructors
-440,7 +415,7
* Set the maximum number of instances that will be allocated when a single
* thread model servlet is used.
*
- * param maxInstnces New value of maxInstances
+ * param maxInstances New value of maxInstances
*/
public void setMaxInstances(int maxInstances) {
-481,7 +456,7
/**
* Set the run-as identity for this servlet.
*
- * param value New run-as identity value
+ * param runAs New run-as identity value
*/
public void setRunAs(String runAs) {
-642,8 +617,8
*/
public Servlet allocate() throws ServletException {
-if (debug = 1)
-log(Allocating an instance);
+if (log.isDebugEnabled())
+log.debug(Allocating an instance);
// If we are currently unloading this servlet, throw an exception
if (unloading)
-670,8 +645,8
}
if (!singleThreadModel) {
-if (debug = 2)
-log( Returning non-STM instance);
+if (log.isTraceEnabled())
+log.trace( Returning non-STM instance);
countAllocated++;
return (instance);
}
-700,8 +675,8
}
}
}
-if (debug = 2)
-log( Returning allocated STM instance);
+if (log.isTraceEnabled())
+log.trace( Returning allocated STM instance);
countAllocated++;
return (Servlet)
DO NOT REPLY [Bug 12460] - Tomcat server hangs when getting datasource connection
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12460. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12460 Tomcat server hangs when getting datasource connection --- Additional Comments From [EMAIL PROTECTED] 2002-11-05 21:42 --- I don't know how you are coming along with the fix of this one, but I can supply a little more information... This is also apparent in Tomcat 4 and only affects Windows installs. I have tried tomcat 4.1.12 with a Win2k machine trying to connect to a Cloudscape db as well as an Oracle db. I have also tried tomcat 4.1.12 on WinXP connecting to MySQL and MS SQL Server. Both installs hung when trying to get a connection. The code I used is nearly identical to that referenced in 'JDBC DataSource HOW-TO'. Finally, I installed tomcat 4.1.12 on Mandrake and the exact code I ran on the WinXP machine succeeded, giving me a connection to the MySQL and MS SQL Server db's. I could not try the Oracle db because it is at another company. Hope this helps a little. Thanks, Chris Marks -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: Tomcat Architecture: XML
Merci monsieur aimable. Mes mercis! Micael At 04:26 PM 11/5/2002 -0500, you wrote: Micael, all the magic reside under the Digester component used by Tomcat to parse xml file. http://jakarta.apache.org/commons/digester.html Enjoys! -- Jeanfrancois micael wrote: I am interested in a particular part of the Tomcat architecture, and NOT the relations between the containers, and the normal development stuff. The use of xml is what interests me, and I cannot find any stuff on how this works IN TOMCAT/CATALINA. I know how xml works. What I would like to know is how the xml works in relation to the applications IN TOMCAT/CATALINA. Is the xml in server.xml used as part of a design pattern using Java reflection? What about the web.xml? Is the way various xml files are used pretty standard, or are there great variations in Tomcat, struts, etc. across the jakarta platforms. I keep trying to find this stuff out, and have had little luck. I need to know the details before I understand something. I hope this is not too dumb of a question. Micael --- This electronic mail transmission and any accompanying documents contain information belonging to the sender which may be confidential and legally privileged. This information is intended only for the use of the individual or entity to whom this electronic mail transmission was sent as indicated above. If you are not the intended recipient, any disclosure, copying, distribution, or action taken in reliance on the contents of the information contained in this transmission is strictly prohibited. If you have received this transmission in error, please delete the message. Thank you -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org Micael --- This electronic mail transmission and any accompanying documents contain information belonging to the sender which may be confidential and legally privileged. This information is intended only for the use of the individual or entity to whom this electronic mail transmission was sent as indicated above. If you are not the intended recipient, any disclosure, copying, distribution, or action taken in reliance on the contents of the information contained in this transmission is strictly prohibited. If you have received this transmission in error, please delete the message. Thank you -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 14246] - setclasspath.{sh,bat} require JDK's jdb and javac
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14246.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14246
setclasspath.{sh,bat} require JDK's jdb and javac
--- Additional Comments From [EMAIL PROTECTED] 2002-11-05 22:31 ---
Sure... but deployment environments often only have the JRE... And then some time
later you want to put in a JSP instead of a Servlet - guess what, JSPs need to be
compiled on the deployment only machine. Will you then be complaining that we need
JDK for that too? Or will you be too busy replacing the JRE with the JSDK at that
point? :-) But you're right, perhaps we should let you hang yourself by not
detecting this problem until you actually try to compile a JSP. This is known as
lazy evaluation. Please feel free to send patches to the batch file.
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 14281] New: - AccessLogValve doesn't export BytesSent info from servlets...
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14281. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14281 AccessLogValve doesn't export BytesSent info from servlets... Summary: AccessLogValve doesn't export BytesSent info from servlets... Product: Tomcat 4 Version: 4.1.12 Platform: PC OS/Version: Linux Status: NEW Severity: Major Priority: Other Component: Catalina:Modules AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I've configured the AccessLogValve in combined format and to invoke servlets seems to return - at the BytesSent position in the log file. Static content seems to fill ok this field. Ciao. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: cvs commit:jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/coreContainerBase.java
on 2002/11/5 1:31 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
protected void log(String message) {
-Logger logger = getLogger();
-if (logger != null)
-logger.log(logName() + : + message);
-else
-System.out.println(logName() + : + message);
-
+// Logger logger = getLogger();
+// if (logger != null)
+// logger.log(logName() + : + message);
+// else
+log.info(message);
}
What the heck is that? There are now two methods with the same name for
logging and one goes to info and the other goes to error based on the method
signature? Where is the logic in that?
And god forbid...maybe try formatting your code properly? The spaces are off
and you put the static log at the bottom of the file???
http://java.sun.com/docs/codeconv/html/CodeConventions.doc2.html#1852
-jon
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 14282] New: - mod_jk/ajp13 returns wrong response after bad chunk-encoding request
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14282. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14282 mod_jk/ajp13 returns wrong response after bad chunk-encoding request Summary: mod_jk/ajp13 returns wrong response after bad chunk- encoding request Product: Tomcat 4 Version: 4.0.4 Final Platform: PC OS/Version: Linux Status: NEW Severity: Major Priority: Other Component: Connector:JK/AJP (deprecated) AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] We currently are running Apache 1.3.26 which forwards requests to our tomcat 4.0.4 server using mod_jk/ajp13. After making the following request: GET /index.jsp HTTP/1.1\x0d\x0aHost: host1.foo.c om\x0d\x0aTransfer-Encoding: Chunked\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a which returns a 404, we begin to see an intermittent problem where valid request results in the response of another request being returned instead of the correct one. We have seen this problem in Tomcat 4.0.6 and 4.1.12. I've looked in the apache bug database and in the tomcat mailing list and seen similar issues, but most of those were in tomcat 3 and we do not see the same behavior in tomcat 3. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 14283] New: - StandardSession does not guard against Listener exceptions
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14283.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14283
StandardSession does not guard against Listener exceptions
Summary: StandardSession does not guard against Listener
exceptions
Product: Tomcat 4
Version: 4.1.12
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
(This bug also exists in the Tomcat 4.0.x code base.)
StandardSession should have try/catch(Throwable) blocks around calls to session
listeners (defined in a webapp) in case the listener logic throws an
exception/error during execution. Some listener calls are already guarded in
StandardSession but the remaining ones are:
public void passivate() {
:
:
try {
((HttpSessionActivationListener)
attribute).sessionWillPassivate(event);
} catch (Throwable t) {
; // do nothing
}
The same try/catch block should also be wrapped around the following calls in
StandardSession.java:
Line 716: ((HttpSessionActivationListener)attribute).sessionDidActivate(event);
Line 1143: ((HttpSessionBindingListener) value).valueUnbound(event);
Line 1252: ((HttpSessionBindingListener) unbound).valueUnbound
(new HttpSessionBindingEvent((HttpSession) this, name));
Line 1265: ((HttpSessionBindingListener) value).valueBound(event);
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 14246] - setclasspath.{sh,bat} require JDK's jdb and javac
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14246.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14246
setclasspath.{sh,bat} require JDK's jdb and javac
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID |
--- Additional Comments From [EMAIL PROTECTED] 2002-11-06 01:00 ---
At the very least, the error messages are wrong/misleading as they
stand.
Can I simply remove the check for javac sine none of the scripts
actually use it?
-Eric
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
BASIC authentication in Tomcat+IIS (PROBLEM SOLVED: ERRATA CORRIGE!!!)
Hello everybody! I wrote to notify you that some days ago I have posted a wrong solution to the problem of the basic authentication of Tomcat with IIS (below you can find my old post). In fact I believed that the reason why basic authentication of Tomcat didn't work was due to compatibility problems between tha jar files ajp.jar and tomcat-util.jar contained in tc4ntiis.zip and Tomcat 4.x. Anyway after some tests I discovered that this WAS NOT the cause of the problem: the REAL cause of the problem was that I had installed in Tomcat 4.x the jar files of tc4ntiis.zip but not the isapi filter isapi_redirect.dll provided with the same .zip package. The version of the ISAPI filter I had installed was that one you can find in the Jakarta web site (isapi_redirector.dll) that IS NOT FULLY compatible with the jar files ajp.jar and tomcat-util.jar of tc4ntiis.zip. All works correctly if you install with ajp.jar and tomcat-util.jar also the isapi_redirect.dll present in tc4ntiis.zip, or if you install ONLY the isapi_redirector.dll of Jakarta web site. I hope this can help someone else. Thanks everybody for the patience! Luca -Messaggio originale- Da: Luca Ventura [mailto:ventluca;tiscali.it] Inviato: giovedì 31 ottobre 2002 15.17 A: tomcat-dev; tomcat-user Oggetto: BASIC authentication in Tomcat+IIS (PROBLEM SOLVED!!!) Hello everybody! I would like to notify you that I have solved the problem described below after many days of hard work on it The solution is simple: to install Tomcat 4.x (I have installed Tomcat 4.0.4-b2) as plug-in of IIS to support JSP/Servlet you must download and install the package tc4ntiis.zip that you can find at URL: http://members.ozemail.com.au/~lampante/howto/tomcat/iisnt/#6 It contains the isapi filter isapi_redirect.dll that let IIS to redirect JSP/Servlets requests to Tomcat 4.x. Well...the package contains also two jar files: ajp.jar and tomcat-util.jar in the server\lib folder. If you install them in the same folder of Tomcat the basic authentication will not work any more when you use Tomcat with the ISAPI filter (not in standalone mode). In fact the original distribution of Tomcat 4.x contains two jar files, tomcat-util.jar and tomcat-ajp.jar, that performs the same operations of the two files described above but have different sizes and use different classes. These two files are built to work correctly with the version of Tomcat they are bundled with: so they MUST NOT REPLACED!!! Given that ajp.jar and tomcat-ajp.jar have different names you also must worry not to install both of them in the server\lib folder of Tomcat: because it can happen that the classes of the first file will be used from Tomcat instead of those of the second one. THIS MEANS THAT YOU HAVE TO IGNORE THE FILES ajp.jar and tomcat-util.jar OF THE PACKAGE tc4ntiis.zip and USE ONLY THE ISAPI FILTER. Maybe when the author of the zip file generated the jar files he didn't worry to test them with Tomcat 4.x: this means that he couldn't note that they have some compatibility problem with this version of Tomcat. In attach you can find the original jar files of Tomcat 4.0.4b2 that I have used and that work correctly: you can use them to restore the correct libs of Tomcat. I hope this solution can help all of you too! :-) Best regards, Luca -Messaggio originale- Da: Luca Ventura [mailto:ventluca;tiscali.it] Inviato: giovedì 31 ottobre 2002 12.32 A: tomcat-user Oggetto: BASIC authentication in Tomcat+IIS (second useful information) Hello! I have another useful information about this problem... The version of Tomcat I have is 4.0.4b3: is it possible that this beta release contains some bug that doesn't let Tomcat to support correctly BASIC authentication (when it is used as Servlet Container and not in standalone mode)?? Anyway in this case I don't understand why in the test environment the basic authentication of Tomcat works well in fact the problem is present only in production environment using Server 1! If someone has some idea or suggestion to solve this problem I pray him to let me know (I am spending many work-days to solve it without success)! Thanks. Luca -Messaggio originale- Da: Luca Ventura [mailto:ventluca;tiscali.it] Inviato: giovedì 31 ottobre 2002 11.12 A: tomcat-dev Oggetto: BASIC authentication in Tomcat+IIS (one useful information) Hello! I have another useful information about the problem described below that I have posted some day ago wihout receiving no solution for it :((( If I use Tomcat 4.x as Web Server (standalone mode), instead of IIS, the BASIC Authentication works well also on Server 1! This means there must be some strange setting in IIS or in Windows 2000 Advanced Server that forces the Tomcat's ISAPI filter (that is to say when Tomcat is used only as Servlet Container) not to ask for login and password to the user but to get their values
Re: costin: fix reverted
I get more info on the issue. The error page worked before because the forward() that was used to redirect to the error page did commit the buffer. Right now the control returns to the page with error, where the buffer seems to be overriden. I'm still debugging it - if I can't find any simple fix I'll just roll back in the 4.1 tree, and continue to try for 5.0 Costin -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 14257] - jsp will execute 2 times
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14257. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14257 jsp will execute 2 times --- Additional Comments From [EMAIL PROTECTED] 2002-11-06 04:34 --- I have found the node of problem. The problem is special character. TD background=#25497F if I remove background=#25497F, it only execute 1 times. The following is my test. 1. The jsp will execute 2 times. %@ page contentType=text/html;charset=GB2312 % % System.out.println(Test jsp start.); % !doctype html public -//w3c/dtd/HTML 4.0//en html !-- Copyright (c) 1999-2000 by BEA Systems, Inc. All Rights Reserved. -- head titleJSP DATE EXAMPLE/title /head body bgcolor=#ff font color=#DB1260 h1 /h1 FORM NAME=main id=main method=post action=QueryKeyword TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 width=85% TR background=#25497F color=#FF bgcolor=#99 TD background=#25497F color=#FF bgcolor=#99 div align=centerfont color=#FFSearch By Date/font/div /TD /TR /table /FORM /BODY /HTML % System.out.println(Test jsp start.); % 2. The following jsp will only execute 1 times. %@ page contentType=text/html;charset=GB2312 % % System.out.println(Test jsp start.); % !doctype html public -//w3c/dtd/HTML 4.0//en html !-- Copyright (c) 1999-2000 by BEA Systems, Inc. All Rights Reserved. -- head titleJSP DATE EXAMPLE/title /head body bgcolor=#ff font color=#DB1260 h1 /h1 FORM NAME=main id=main method=post action=QueryKeyword TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 width=85% TR background=#25497F color=#FF bgcolor=#99 TD background=green color=#FF bgcolor=#99 div align=centerfont color=#FFSearch By Date/font/div /TD /TR /table /FORM /BODY /HTML % System.out.println(Test jsp start.); % do you know why? -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: costin: fix reverted
I'm getting closer - Remy or Kin-Man, I need your help. As I expected, the flush() was hiding some other behaviors. Right now I'm looking at ApplicationDispatcher.doForward(). What happens is: - error happens - we forward to the error page - error page executes, put the data in the out buffer - BEFORE: the out buffer was commited - now we just return from servlet to doForward() - The commiting and closing response reached ( line 471 ) What happens here is response is a ResponseFacade, and finish is called. But the real flushing and closing doesn't actually happens. I changed the code to first flush/close, the call finish - and it now seems to work fine. But I'm not sure what else may be affected by this - or if it's safe to make the change ( well, for 5.0 it may be, but what about 4.1 ? ) In any case, I expect this to have caused some weird behavior for normal forward - since forward doesn't seem to really flush/close as it was supposed to do ( unless response is not facade - does this case ever happen ? ). A bit strange no other test detected that, normal servlets don't have flush/close that the jsp page had. Costin Costin Manolache wrote: I get more info on the issue. The error page worked before because the forward() that was used to redirect to the error page did commit the buffer. Right now the control returns to the page with error, where the buffer seems to be overriden. I'm still debugging it - if I can't find any simple fix I'll just roll back in the 4.1 tree, and continue to try for 5.0 Costin -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 14289] New: - Character Encodings Suggestion
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14289. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14289 Character Encodings Suggestion Summary: Character Encodings Suggestion Product: Tomcat 4 Version: 4.1.12 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Enhancement Priority: Other Component: Connector:Coyote HTTP/1.1 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I suggest that the default character encoding should be set as variable (may be in the server.xml configuration file) rather than being hard-coded in the source of the connector (in fact it is hard-coded in catalina source if you are using the old connector), and the catalina server itself. I am using Tomcat for a long time (may be 2 years) and this problem exists from the early versions. When I am setting up a new version I always have to modify the code and to set the encoding to a cyrillic one like windows-1251. Otherwise the url-decoding is not done properly and the cyrillic words that I send in a request appear corrupted. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 14275] - Problems creating DataSource
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14275. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14275 Problems creating DataSource [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-11-06 07:57 --- You also need a resource link definition in your server.xml. Otherwise, your lookup is picking up the blank resource ref. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
