DO NOT REPLY [Bug 29166] New: - Expect: 100-Continue fails after 401 Unauthorized

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29166.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

Expect: 100-Continue fails after 401 Unauthorized

   Summary: Expect: 100-Continue fails after 401 Unauthorized
   Product: Tomcat 5
   Version: 5.0.16
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Connector:HTTP
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


A POST to a protected servlet using Expect: 100-continue results in a 401 
Unauthorized return. If that same connection is held open and the POST is 
resubmitted again using the Expect: 100-continue along with appropriate 
Authorization credentials the 100 Continue is never sent. Timing out on waiting 
for the 100 Continue and sending the entity body anyways results in a 505 HTTP 
Version Not Supported.

In the following senario I am not using a front end web server nor the jk2 
connector. I am using tomcat 5.0.16 with a basic HTTP Connector running as a 
service on Windows2000 with the latest service packs. There are no reported 
errors in the logs.

java version 1.4.1
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-b21)
Java HotSpot(TM) Client VM (build 1.4.1-b21, mixed mode)


** REQUEST **
POST /client/servlet/EchoExample HTTP/1.1
Host: localhost:8000
User-Agent: NetLib/1.0
Accept: text/html, text/xml, text/plain, image/gif, image/png, image/jpeg, */*
Accept-Language: en-us
Accept-Charset: ISO-8859-1;q=0.8, UTF-8;q=0.6, *;q=0.3
Content-Type: multipart/form-data; 
boundary==_Part_0_27379847.1085374393407
Content-Length: 727
TE: gzip;q=0.8, deflate;q=0.2
Expect: 100-continue
Connection: keep-alive
Pragma: no-cache
Cache-Control: no-cache

** RESPONSE **
HTTP/1.1 401 Unauthorized
WWW-Authenticate: Basic realm=Realm 1
Content-Type: text/html;charset=ISO-8859-1
Content-Language: en-US
Content-Length: 911
Date: Mon, 24 May 2004 04:53:18 GMT
Server: Apache-Coyote/1.1

bunch of stuff here.


** RE REQUEST **
POST /client/servlet/EchoExample HTTP/1.1
Host: localhost:8000
User-Agent: NetLib/1.0
Accept: text/html, text/xml, text/plain, image/gif, image/png, image/jpeg, */*
Accept-Language: en-us
Accept-Charset: ISO-8859-1;q=0.8, UTF-8;q=0.6, *;q=0.3
Authorization: Basic dG9tY2F0MTp0b21jYXQ=
Content-Type: multipart/form-data; 
boundary==_Part_0_27379847.1085374393407
Content-Length: 727
TE: gzip;q=0.8, deflate;q=0.2
Expect: 100-continue
Connection: keep-alive
Pragma: no-cache
Cache-Control: no-cache


= THIS IS WHERE THE 100 Continue is never sent and my client code timeouts =
= I attempt to send entity body anyway assuming HTTP/1.0 client as per RFC =

** FINAL RESULT **
HTTP/1.1 505 HTTP Version Not Supported
Date: Mon, 24 May 2004 04:53:25 GMT
Server: Apache-Coyote/1.1
Connection: close



The work around on the client is to close the connection and get a new 
connection before retrying. Obviously this defeats the point of using the 
Expect: 100-continue in the first place.

It seems that the same senario without the intermediary 401 Unauthorized works 
without issue.

After some testing I have found that as long as the Content-Length  5 it seems 
to work properly. But if the Content-Length = 5 it never returns 100 Continue.

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

DO NOT REPLY [Bug 29166] - Expect: 100-Continue fails after 401 Unauthorized

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29166.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

Expect: 100-Continue fails after 401 Unauthorized





--- Additional Comments From [EMAIL PROTECTED]  2004-05-24 07:13 ---
Created an attachment (id=11638)
Simple test case.. Needs a protected (basic auth) servlet

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

AutoReply: Ihre Anfrage!

2004-05-24 Thread service 

Sehr geehrter freenet.de Interessent,
 
vielen Dank für Ihr Interesse an unseren Diensten und Produkten!
 
Bitte beachten Sie, dass Sie eine automatische Antwort erhalten haben 
und auf diese E-Mail nicht geantwortet werden kann.
Eine gesonderte weitere Antwort auf Ihre E-Mail Anfrage erhalten Sie nicht.
 
Haben Sie Fragen zu unseren Tarifen, so besuchen Sie uns unter: http://tarif.freenet.de
 
Möchten Sie in Einrichtungshilfestellungen stöbern, so öffnen Sie bitte: 
http://hilfe.freenet.de
 
Wenn Sie nicht die gewünschte Hilfe in den zur Verfügung gestellten Informationen 
auffinden konnten, nutzen Sie unseren für Kunden kosten- freien E-Mail Service über 
unser Kontakt-Formular.
 
Um eine hochwertige, qualifizierte und schnelle Bearbeitung Ihrer Anfrage 
sicherzustellen, haben wir unseren E-Mail Service für Sie optimiert. 
Nutzen Sie einfach unser Kundenkontakt-Formular unter: http://online-hilfe.freenet.de
 
Bitte beachten Sie, dass Sie über ein kostenfreien freenet.de Mitglieds- namen 
verfügen müssen, um unseren kostenlosen E-Mail Service in 
Anspruch nehmen zu können. 
 
Noch nicht kostenfrei registriert bei freenet.de? 
Einfach schnell und kostenfrei anmelden unter my.freenet.de
 
Viel Spaß bei freenet.de 
Ihr freenet.de Serviceteam
 
Kontakt unter:
http://service.freenet.de

DO NOT REPLY [Bug 13040] - can't retrieve external context who's uri is a sub-dir of current context

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=13040.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

can't retrieve external context who's uri is a sub-dir of current context





--- Additional Comments From [EMAIL PROTECTED]  2004-05-24 12:26 ---
 Is this bug solved?

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

DO NOT REPLY [Bug 29174] New: - complain about liveDeploy tags and enhance documentation of deployOnStartup

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29174.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

complain about liveDeploy tags and enhance documentation of deployOnStartup

   Summary: complain about liveDeploy tags and enhance documentation
of deployOnStartup
   Product: Tomcat 5
   Version: 5.0.24
  Platform: Other
   URL: http://jakarta.apache.org/tomcat/tomcat-5.0-
doc/config/host.html#Attributes
OS/Version: Other
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


coming from 4.1.27, my server.xml had a 3 host tags with each an
unpackWARs=false autoDeploy=false liveDeploy=false setting and each a .war
file. All war files in the same directory.
With 5.0.24, it started to deploy 3*3, i.e. 9 times instead of only 3 like before.

It appears that liveDeploy is not longer used and now called autoDeploy?
If so, shouldn't the server.xml parser complain about this unknown attribute?

Similarly, autoDeploy appears now to be deployOnStartup? If so, it might be
useful to add a note in this respect in the description box for each of the two!

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

DO NOT REPLY [Bug 29174] - complain about liveDeploy tags and enhance documentation of deployOnStartup

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29174.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

complain about liveDeploy tags and enhance documentation of deployOnStartup





--- Additional Comments From [EMAIL PROTECTED]  2004-05-24 12:34 ---
and now, even that I have deployOnStartup=false unpackWARs=false
autoDeploy=false liveDeploy=false
for each Host element, it still seems to deploy on startup.sh .
I assume the reason for this is that in the web.xml, I use the tag
load-on-startup . If this is correct, I assume this should be mentioned as well!

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

DO NOT REPLY [Bug 28904] - Multipart form problem lost when request is passed to code.

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28904.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

Multipart form problem lost when request is passed to code.





--- Additional Comments From [EMAIL PROTECTED]  2004-05-24 14:19 ---
I am working around this by using a servlet to handle multipart requests, which 
appears to work correctly and implies a problem with the JSP compilation even 
more strongly. I took a look at the source code, but I don't really understand 
tomcat well enough to be able to find anything.

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

DO NOT REPLY [Bug 29180] New: - Tag attributes with array type don't work

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29180.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

Tag attributes with array type don't work

   Summary: Tag attributes with array type don't work
   Product: Tomcat 4
   Version: 4.0 Beta 1
  Platform: All
OS/Version: All
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Jasper
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


If the type of an attribute is an array type, like java.lang.Object[], the
generated java code will contain casts to the name of the array type, e.g.
something like this:

   
_jspx_th_stat_arrayiter_0.setArray(([Ljava.lang.Object;)JspRuntimeLibrary.getValueFromPropertyEditorManager([Ljava.lang.Object;.class,
array, %= context.filterReports(context.getReports(), 1) %));

which is not valid Java, because the name of an array type isn't a valid identifier.

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

respuestas sobre el Chat

2004-05-24 Thread ayudachat 


Algunas preguntas frecuentes sobre inconvenientes al ingresar al chat son:



Si puede ingresar su Nick en el recuadro de texto pero no inicia la sesión de chat 
pueder ser por que dicho Nick se encuentre registrado por otra persona en tal caso 
pruebe cambiarlo o agregarle algún numero.

También puede ser que su ip se encuentre prohibida por el moderador en este caso hay 
que esperar algunas horas hasta que se libere, observe el recuadro blanco de reportes 
cada vez que intenta ingresar para saber cual es el caso. Si sólo lee un mensaje de 
error puede ser necesario reiniciar su computadora.



FALTA DE MAQUINA VIRTUAL DE JAVA

Para Windows XP, WinNT, WinME, Win98

Si por alguna razón su navegador le avisa que NO tiene instalada la compatibilidad con 
JAVA, la mejor alternativa es bajar la Maquina virtual de Java desde el sitio oficial 
de Sun

http://www.java.com/en/index.jsp  En esta página clickeando en Download Java 
Software, automaticamentte le va a detectar e instalar la version necesaria para su 
PC.

 

Luego de un par de minutos que se complete el proceso ya lo puede probar

www.paysandu.com/chat



OTRAS RAZONES POSIBLES

Cuando aparece un recuadro gris en la pantalla y luego de varios segundos no aparece 
el acceso al Chat. Las razones pueden ser las siguientes, que en ese momento la 
conexión esté muy lenta y demora más de lo habitual; si es este el caso y esperando no 
se soluciona puede desconectarse/conectarse de Internet para volver a intentarlo. 

Si no se soluciona o nota que esto es frecuente, entonces puede ser que tenga muchos 
archivos temporales en el cache de su maquina.



Como Limpiar la memoria caché?

Si el caché está lleno, las páginas nuevas se abrirán muy lentamente o no se abrirán. 
Es posible que la memoria caché esté llena de páginas desfasadas o inútiles; por ello 
es buena idea limpiarla de vez en cuando. A continuación explicamos cómo limpiar la 
memoria caché dependiendo del navegador que tenga:



*

LIMPIAR CACHE EN INTERNET EXPLORER, instrucciones:



Haga clic en Herramientas (Tools) en la parte superior de la ventana de su navegador 
y luego seleccione Opciones de Internet (Internet Options).



Cuando emerja la ventana, haga clic en el cuadro eliminar archivos (delete files).



Marque la opción eliminar contenido fuera de línea (delete offline content) y haga 
clic en Aceptar (OK).



Haga también clic en el botón limpiar historial (clear history).



Haga clic en Aceptar (OK) hasta salir del cuadro de preferencias. 

Después de haber vaciado el caché, y estando conectado a Internet vaya a 
www.paysandu.com/chat.html oprima las teclas Ctrl y Shift y pulse el botón 
Actualizar (refresh) o (Reload) en su navegador a la misma vez luego de algunos 
segundos deberá aparecer el recuadro del nombre y boton login de acceso al Chat





LIMPIAR CACHE EN NETSCAPE, instrucciones:



Haga clic en edición (edit) en la parte superior de la ventana de su navegador y a 
continuación en preferencias (preferences).



Cuando emerja la ventana, haga clic en las opciones limpiar historial (clear 
history) y en limpiar barra de localización (clear location bar).



A continuación haga clic en el signo + que se encuentra junto a la opción avanzado 
(advanced).



Seleccione la opción caché.



Haga clic en las opciones limpiar memoria caché (clear memory cache) y en limpiar 
disco caché (clear disk cache).



Haga clic en Aceptar (OK) hasta salir de la ventana.





LIMPIAR CACHE EN AOL, siga los siguientes pasos:



Busque preferencias (preferences) en el menú mi aol (my aol).



Luego haga clic en www.



Haga clic en el botón eliminar archivos (delete files). Aparecerá una ventana 
preguntándole si desea borrar los archivos temporales de Internet.



Marque el cuadro de la opción eliminar contenido fuera de línea (delete offline 
content) y haga clic en el botón Aceptar (OK).



A continuación haga clic en el botón eliminar historial (delete history).



Haga clic en Aceptar (OK) hasta que salga del menú de preferencias.

Después de haber vaciado el caché, vaya a www.paysandu.com/chat.html y pulse el botón 
Actualizar (refresh) o Volver a cargar (Reload) en su navegador



**

Si usted es usuario de WebTv no podrá acceder al Chat, esta es una limitacion del 
proveedor de este tipo de servicio que no admite Java. Tampoco se pueden conectar en 
una red interna a través de un Fire Wall sin que el administrador del mismo lo 
autorice previamente.



En este chat al igual que en el foro de encuentros, los enlaces entre usuarios y o 
canales se producen 100% en la web de www.paysandu.com es decir no exiten accesos a 
través de servidores IRC u de otro tipo.



  





COMANDOS DE USO EN EL CHAT DE ENCUENTROS SANDUCEROS



Los siguientes comandos se pueden ejecutar en la línea de diálogo seguidos del 
caractér / 



algunos de ellos se han simplificado incorporándolos al botón derecho del mouse

DO NOT REPLY [Bug 29182] New: - Jasper locks jar files when compiling JSPs through Ant

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29182.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

Jasper locks jar files when compiling JSPs through Ant

   Summary: Jasper locks jar files when compiling JSPs through Ant
   Product: Tomcat 5
   Version: 5.0.24
  Platform: PC
OS/Version: Windows XP
Status: NEW
  Severity: Major
  Priority: Other
 Component: Jasper
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


When using Ant to compile JSPs, Jasper locks jar files, so they can not be
deleted on Windows. I am attaching an application that reproduces this issue. To
use it, do the following:

1. Unpack the zip archive
2. Edit the build.properties file to point to your Tomcat installation
(reproduced with 5.0.24)
3. Run ant (reproduced with 1.6.1) in the root directory of the application

The ant script compiles pages in the application and then tried to delete the
jar files used by the app. Deletion fails.

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

DO NOT REPLY [Bug 29182] - Jasper locks jar files when compiling JSPs through Ant

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29182.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

Jasper locks jar files when compiling JSPs through Ant





--- Additional Comments From [EMAIL PROTECTED]  2004-05-24 16:55 ---
Created an attachment (id=11640)
Test case for this issue

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

DO NOT REPLY [Bug 13040] - can't retrieve external context who's uri is a sub-dir of current context

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=13040.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

can't retrieve external context who's uri is a sub-dir of current context





--- Additional Comments From [EMAIL PROTECTED]  2004-05-24 18:18 ---
Not completely no. The most recent debate on this is here:
http://marc.theaimsgroup.com/?l=tomcat-devm=108109687130165w=2

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

Tomas Milacek/YR Inc is out of the office.

2004-05-24 Thread Tomas . Milacek 
I will be out of the office starting  24.05.2004 and will not return until
03.06.2004.

Od 24.5.04 do 3.6.2004 jsem mimo kancelar. V pripade nutnosti prosim,
kontaktujte meho kolegu Jardu Hasmana 227 177 437 nebo recepci 227 177 400.
Dekuji.


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

Alain Hirtz/136/DCAG/DCX est absent(e). ist außer Haus

2004-05-24 Thread Alain.Hirtz 




Je serai absent(e) du  24/05/2004 au 28/05/2004.

For price requests please mail to [EMAIL PROTECTED]


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

Session Unbound

2004-05-24 Thread Ravindra Gupta 
 I have 2 problems

1) I am keeping connection into session . My requirement is that i have to release  
this  connection once Session is inactivated/expired .I have given an
implementation where the unbound method of class implementing 
HttpSessionBindingListener  is getting called , but it is called after the session is 
made invalid and since session is already invalidated i can't access Connection Object 
kept into session .

My understanding was that Once a Session is expired , unbound methos is called and 
than only session becomes inactive . This is not happening in Tomcat while in weblogic 
its working correctly ?Any suggestions how to ensure that unbound method gets called 
before Session is invalidated.


2) When i take connection from DataSource , sometimes i am getting following excepting 
when trying to set AutoCommit on DB2 environment

 com.ibm.db2.jcc.c.SqlException: invalid operation: connection closed
 at com.ibm.db2.jcc.c.o.bk(o.java:2708)
 at com.ibm.db2.jcc.c.o.setAutoCommit(o.java:681)

Any suggestions ??


thanks,
ravi



--

This e-mail may contain confidential and/or privileged information. If you are not the 
intended recipient (or have received this e-mail in error) please notify the sender 
immediately and destroy this e-mail. Any unauthorized copying, disclosure or 
distribution of the material in this e-mail is strictly forbidden.



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

RE: Session Unbound

2004-05-24 Thread Shapira, Yoav 

Hi,
Post to the tomcat-user list, not the tomcat-dev list.  Keeping a
connection with the session is horrible from the scalability
perspective.

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Ravindra Gupta [mailto:[EMAIL PROTECTED]
Sent: Monday, May 24, 2004 4:35 PM
To: [EMAIL PROTECTED]
Subject: Session Unbound

 I have 2 problems

1) I am keeping connection into session . My requirement is that i have
to
release  this  connection once Session is inactivated/expired .I have
given
an
implementation where the unbound method of class implementing
HttpSessionBindingListener  is getting called , but it is called after
the
session is made invalid and since session is already invalidated i
can't
access Connection Object kept into session .

My understanding was that Once a Session is expired , unbound methos is
called and than only session becomes inactive . This is not happening
in
Tomcat while in weblogic its working correctly ?Any suggestions how to
ensure that unbound method gets called before Session is invalidated.


2) When i take connection from DataSource , sometimes i am getting
following excepting when trying to set AutoCommit on DB2 environment

 com.ibm.db2.jcc.c.SqlException: invalid operation: connection closed
 at com.ibm.db2.jcc.c.o.bk(o.java:2708)
 at com.ibm.db2.jcc.c.o.setAutoCommit(o.java:681)

Any suggestions ??


thanks,
ravi



--

This e-mail may contain confidential and/or privileged information. If
you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in
this e-
mail is strictly forbidden.



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




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


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

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper JspCompilationContext.java

2004-05-24 Thread luehe 
luehe   2004/05/24 14:17:27

  Modified:jasper2/src/share/org/apache/jasper
JspCompilationContext.java
  Log:
  Added comments
  
  Revision  ChangesPath
  1.48  +2 -0  
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/JspCompilationContext.java
  
  Index: JspCompilationContext.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/JspCompilationContext.java,v
  retrieving revision 1.47
  retrieving revision 1.48
  diff -u -r1.47 -r1.48
  --- JspCompilationContext.java6 May 2004 22:55:23 -   1.47
  +++ JspCompilationContext.java24 May 2004 21:17:27 -  1.48
  @@ -512,6 +512,7 @@
   jsw.setReload(true);
   jsw.setCompilationException(null);
   } catch (JasperException ex) {
  +// Cache compilation exception
   jsw.setCompilationException(ex);
   throw ex;
   } catch (Exception ex) {
  @@ -519,6 +520,7 @@
   JasperException je = new JasperException(
   Localizer.getMessage(jsp.error.unable.compile),
   ex);
  +// Cache compilation exception
   jsw.setCompilationException(je);
   throw je;
   }
  
  
  

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

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet JspServletWrapper.java

2004-05-24 Thread luehe 
luehe   2004/05/24 14:22:00

  Modified:jasper2/src/share/org/apache/jasper/servlet
JspServletWrapper.java
  Log:
  - Added comments
  - Removed redundant if (reload) prior to calling getServlet()
(reload flag is already being checked inside getServlet())
  
  Revision  ChangesPath
  1.36  +14 -6 
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet/JspServletWrapper.java
  
  Index: JspServletWrapper.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet/JspServletWrapper.java,v
  retrieving revision 1.35
  retrieving revision 1.36
  diff -u -r1.35 -r1.36
  --- JspServletWrapper.java20 Apr 2004 00:05:09 -  1.35
  +++ JspServletWrapper.java24 May 2004 21:22:00 -  1.36
  @@ -157,7 +157,7 @@
   return config.getServletContext();
   }
   
  -/*
  +/**
* Sets the compilation exception for this JspServletWrapper.
*
* @param je The compilation exception
  @@ -166,7 +166,6 @@
   this.compileException = je;
   }
   
  -
   /**
* Compile (if needed) and load a tag file
*/
  @@ -266,28 +265,37 @@
Localizer.getMessage(jsp.error.unavailable));
   }
   
  +/*
  + * (1) Compile
  + */
   if (options.getDevelopment() || firstTime ) {
   synchronized (this) {
   if (firstTime) {
   firstTime = false;
   }
  +// The following sets reload to true, if necessary
   ctxt.compile();
   }
   } else {
   if (compileException != null) {
  +// Throw cached compilation exception
   throw compileException;
   }
   }
   
  -if (reload) {
  -getServlet();
  -}
  +/*
  + * (2) (Re)load servlet class file
  + */
  +getServlet();
   
  -// If a page is to only to be precompiled return.
  +// If a page is to be precompiled only, return.
   if (precompile) {
   return;
   }
   
  +/*
  + * (3) Service request
  + */
   if (theServlet instanceof SingleThreadModel) {
  // sync on the wrapper so that the freshness
  // of the page is determined right before servicing
  
  
  

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

DO NOT REPLY [Bug 29182] - Jasper locks jar files when compiling JSPs through Ant

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29182.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

Jasper locks jar files when compiling JSPs through Ant





--- Additional Comments From [EMAIL PROTECTED]  2004-05-24 21:25 ---
Did you check that it's not an Ant or javac issue ? Do you use fork=true ?

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

DO NOT REPLY [Bug 29174] - complain about liveDeploy tags and enhance documentation of deployOnStartup

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29174.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

complain about liveDeploy tags and enhance documentation of deployOnStartup

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2004-05-24 21:26 ---
I think the documentation is good enough (and I really hate whines ...).

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

DO NOT REPLY [Bug 29166] - Expect: 100-Continue fails after 401 Unauthorized

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29166.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

Expect: 100-Continue fails after 401 Unauthorized





--- Additional Comments From [EMAIL PROTECTED]  2004-05-24 21:32 ---
100s are optional anyway. BTW, putting comments which look like science fiction
doesn't help the credibility of your bug report.
I also think the code which handles 100s to be obvious enough. I recommend you
look into this further.

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

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet JspServletWrapper.java

2004-05-24 Thread luehe 
luehe   2004/05/24 14:33:48

  Modified:jasper2/src/share/org/apache/jasper/compiler Compiler.java
   jasper2/src/share/org/apache/jasper/servlet
JspServletWrapper.java
  Log:
  Added support for JSP compilations in a clustered env, where one
  server instance may use JSPs compiled by another server instance.
  
  Assume a JSP named foo.jsp, along with these timestamps:
  
t1= Timestamp of foo.jsp
t2= Timestamp of foo.class
  
SI_1  = ServerInstance_1
SI_2  = ServerInstance_2
  
  Problem description:
  
  - Suppose SI_1 compiles foo.jsp and loads corresponding class file.
  
  - foo.jsp is subsequently modified and recompiled by SI_2.
  
  - SI_1 accesses foo.jsp: Since t2t1, it determines that no
recompilation is necessary, and services the cached (outdated) class
file
  
  With this commit, SI_1 will reload foo.class and service its updated contents.
  
  Revision  ChangesPath
  1.87  +3 -0  
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Compiler.java
  
  Index: Compiler.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Compiler.java,v
  retrieving revision 1.86
  retrieving revision 1.87
  diff -u -r1.86 -r1.87
  --- Compiler.java 21 May 2004 17:52:59 -  1.86
  +++ Compiler.java 24 May 2004 21:33:48 -  1.87
  @@ -543,6 +543,9 @@
   outDated = true;
   } else {
   targetLastModified = targetFile.lastModified();
  +if (checkClass) {
  +jsw.setServletClassLastModifiedTime(targetLastModified);
  +}   
   if (targetLastModified  jspRealLastModified) {
   if( log.isDebugEnabled() ) {
   log.debug(Compiler: outdated:  + targetFile +   +
  
  
  
  1.37  +18 -0 
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet/JspServletWrapper.java
  
  Index: JspServletWrapper.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet/JspServletWrapper.java,v
  retrieving revision 1.36
  retrieving revision 1.37
  diff -u -r1.36 -r1.37
  --- JspServletWrapper.java24 May 2004 21:22:00 -  1.36
  +++ JspServletWrapper.java24 May 2004 21:33:48 -  1.37
  @@ -74,6 +74,7 @@
   private boolean isTagFile;
   private int tripCount;
   private JasperException compileException;
  +private long servletClassLastModifiedTime;
   
   /*
* JspServletWrapper for JSP pages.
  @@ -164,6 +165,23 @@
*/
   public void setCompilationException(JasperException je) {
   this.compileException = je;
  +}
  +
  +/**
  + * Sets the last-modified time of the servlet class file associated with
  + * this JspServletWrapper.
  + *
  + * @param lastModified Last-modified time of servlet class
  + */
  +public void setServletClassLastModifiedTime(long lastModified) {
  +if (this.servletClassLastModifiedTime  lastModified) {
  +synchronized (this) {
  +if (this.servletClassLastModifiedTime  lastModified) {
  +this.servletClassLastModifiedTime = lastModified;
  +reload = true;
  +}
  +}
  +}
   }
   
   /**
  
  
  

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

[GUMP@brutus]: jakarta-tomcat/jakarta-tomcat prerequisite failed

2004-05-24 Thread Stefan Bodewig 
To whom it may satisfy...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact folk at [EMAIL PROTECTED]

Project jakarta-tomcat *no longer* has an issue.
Project State : 'Prerequisite Failed', Reason 'Build Failed'

Full details are available at:

http://brutus.apache.org:8080/gump/jakarta-tomcat/jakarta-tomcat/index.html

That said, some snippets follow:


The following annotations were provided:
 -INFO- Jar [tomcat-util.jar] identifier set to jar basename: [tomcat-util]
 -INFO- Jar [tomcat_core.jar] identifier set to jar basename: [tomcat_core]
 -INFO- Jar [tomcat_modules.jar] identifier set to jar basename: [tomcat_modules]
 -INFO- Jar [facade22.jar] identifier set to jar basename: [facade22]
 -INFO- Jar [core_util.jar] identifier set to jar basename: [core_util]
 -INFO- Jar [jasper.jar] identifier set to jar basename: [jasper]
 -INFO- Jar [container_util.jar] identifier set to jar basename: [container_util]
 -INFO- Jar [tomcat.jar] identifier set to jar basename: [tomcat]
 -INFO- Dependency on commons-modeler exists, no need to add for property 
commons-modeler.jar.
 -INFO- Dependency on ant exists, no need to add for property ant.home.
 -INFO- Dependency on jsse exists, no need to add for property jsse.home.
 -INFO- Dependency on commons-logging exists, no need to add for property 
commons-logging.home.
 -INFO- Dependency on commons-modeler exists, no need to add for property 
commons-modeler.home.
 -INFO- Optional dependency logging-log4j prerequisite failed with reason build failed
 -INFO- Prerequisite failed with reason build failed



To subscribe to this information via syndicated feeds:
 RSS: http://brutus.apache.org:8080/gump/jakarta-tomcat/jakarta-tomcat/rss.xml
 Atom: http://brutus.apache.org:8080/gump/jakarta-tomcat/jakarta-tomcat/atom.xml


--
Produced by Gump 2.0.3-alpha-0002.
[Run (20040524 15:00:12, brutus:brutus-public:20040524 15:00:12)]
http://brutus.apache.org:8080/gump/index.html
http://brutus.apache.org:8080/gump/options.html

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

[GUMP@brutus]: jakarta-tomcat-catalina/jakarta-tomcat-catalina prerequisite failed

2004-05-24 Thread bobh 
To whom it may satisfy...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact folk at [EMAIL PROTECTED]

Project jakarta-tomcat-catalina *no longer* has an issue.
Project State : 'Prerequisite Failed', Reason 'Build Failed'

Full details are available at:


http://brutus.apache.org:8080/gump/jakarta-tomcat-catalina/jakarta-tomcat-catalina/index.html

That said, some snippets follow:


The following annotations were provided:
 -INFO- Jar [naming-resources.jar] identifier set to jar basename: [naming-resources]
 -INFO- Jar [servlets-default.jar] identifier set to jar basename: [servlets-default]
 -INFO- Jar [naming-common.jar] identifier set to jar basename: [naming-common]
 -INFO- Jar [catalina.jar] identifier set to jar basename: [catalina]
 -INFO- Jar [bootstrap.jar] identifier set to jar basename: [bootstrap]
 -INFO- Jar [servlets-common.jar] identifier set to jar basename: [servlets-common]
 -INFO- Jar [servlets-invoker.jar] identifier set to jar basename: [servlets-invoker]
 -ERROR- No such project [commons-beanutils] for property
 -ERROR- Cannot resolve jar/jarpath of *unknown* [commons-beanutils]
 -INFO- Dependency on javamail exists, no need to add for property mail.jar.
 -INFO- Dependency on jaf exists, no need to add for property activation.jar.
 -INFO- Dependency on jmx exists, no need to add for property jmx.jar.
 -INFO- Dependency on jakarta-servletapi-5-servlet exists, no need to add for property 
servlet-api.jar.
 -INFO- Dependency on jakarta-servletapi-5-jsp exists, no need to add for property 
jsp-api.jar.
 -INFO- Dependency on xml-xerces exists, no need to add for property xercesImpl.jar.
 -INFO- Dependency on xml-xerces exists, no need to add for property xmlParserAPIs.jar.
 -INFO- Dependency on jakarta-tomcat-util exists, no need to add for property 
tomcat-util.jar.
 -INFO- Dependency on commons-logging exists, no need to add for property 
commons-logging-api.jar.
 -INFO- Dependency on ant exists, no need to add for property ant.home.
 -INFO- Dependency on jsse exists, no need to add for property jsse.home.
 -INFO- Dependency on jmx exists, no need to add for property jmx.home.
 -INFO- Dependency on jmx exists, no need to add for property jmxtools.jar.
 -INFO- Dependency on jndi exists, no need to add for property jndi.home.
 -INFO- Dependency on jakarta-regexp exists, no need to add for property regexp.home.
 -INFO- Dependency on jakarta-regexp exists, no need to add for property regexp.jar.
 -INFO- Dependency on javamail exists, no need to add for property mail.home.
 -INFO- Dependency on jaf exists, no need to add for property activation.home.
 -INFO- Dependency on jakarta-tomcat-coyote exists, no need to add for property 
tomcat-coyote.home.
 -INFO- Prerequisite failed with reason build failed
 -INFO- Optional dependency junit prerequisite failed with reason build failed



To subscribe to this information via syndicated feeds:
 RSS: 
http://brutus.apache.org:8080/gump/jakarta-tomcat-catalina/jakarta-tomcat-catalina/rss.xml
 Atom: 
http://brutus.apache.org:8080/gump/jakarta-tomcat-catalina/jakarta-tomcat-catalina/atom.xml


--
Produced by Gump 2.0.3-alpha-0002.
[Run (20040524 15:00:12, brutus:brutus-public:20040524 15:00:12)]
http://brutus.apache.org:8080/gump/index.html
http://brutus.apache.org:8080/gump/options.html

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

[GUMP@brutus]: jakarta-tomcat-connectors-coyote_10/jakarta-tomcat-util-coyote_10 prerequisite failed

2004-05-24 Thread Stefan Bodewig 
To whom it may satisfy...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact folk at [EMAIL PROTECTED]

Project jakarta-tomcat-util-coyote_10 *no longer* has an issue.
Project State : 'Prerequisite Failed', Reason 'Build Failed'

Full details are available at:


http://brutus.apache.org:8080/gump/jakarta-tomcat-connectors-coyote_10/jakarta-tomcat-util-coyote_10/index.html

That said, some snippets follow:


The following annotations were provided:
 -INFO- Sole jar [tomcat-util.jar] identifier set to project name
 -INFO- Dependency on jmx exists, no need to add for property jmx.home.
 -INFO- Dependency on jmx exists, no need to add for property jmx.jar.
 -INFO- Dependency on jsse exists, no need to add for property jsse.home.
 -INFO- Prerequisite failed with reason build failed



To subscribe to this information via syndicated feeds:
 RSS: 
http://brutus.apache.org:8080/gump/jakarta-tomcat-connectors-coyote_10/jakarta-tomcat-util-coyote_10/rss.xml
 Atom: 
http://brutus.apache.org:8080/gump/jakarta-tomcat-connectors-coyote_10/jakarta-tomcat-util-coyote_10/atom.xml


--
Produced by Gump 2.0.3-alpha-0002.
[Run (20040524 15:00:12, brutus:brutus-public:20040524 15:00:12)]
http://brutus.apache.org:8080/gump/index.html
http://brutus.apache.org:8080/gump/options.html

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

[GUMP@brutus]: jakarta-tomcat-connectors-coyote_10/jakarta-tomcat-coyote_10 prerequisite failed

2004-05-24 Thread Stefan Bodewig 
To whom it may satisfy...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact folk at [EMAIL PROTECTED]

Project jakarta-tomcat-coyote_10 *no longer* has an issue.
Project State : 'Prerequisite Failed', Reason 'Build Failed'

Full details are available at:


http://brutus.apache.org:8080/gump/jakarta-tomcat-connectors-coyote_10/jakarta-tomcat-coyote_10/index.html

That said, some snippets follow:


The following annotations were provided:
 -INFO- Sole jar [tomcat-coyote.jar] identifier set to project name
 -INFO- Dependency on jmx exists, no need to add for property jmx.home.
 -INFO- Dependency on jmx exists, no need to add for property jmx.jar.
 -INFO- Dependency on tomcat-catalina exists, no need to add for property 
catalina.home.
 -INFO- Prerequisite failed with reason build failed



To subscribe to this information via syndicated feeds:
 RSS: 
http://brutus.apache.org:8080/gump/jakarta-tomcat-connectors-coyote_10/jakarta-tomcat-coyote_10/rss.xml
 Atom: 
http://brutus.apache.org:8080/gump/jakarta-tomcat-connectors-coyote_10/jakarta-tomcat-coyote_10/atom.xml


--
Produced by Gump 2.0.3-alpha-0002.
[Run (20040524 15:00:12, brutus:brutus-public:20040524 15:00:12)]
http://brutus.apache.org:8080/gump/index.html
http://brutus.apache.org:8080/gump/options.html

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

[GUMP@brutus]: jakarta-tomcat-4.0/jakarta-tomcat-4.0 prerequisite failed

2004-05-24 Thread Stefan Bodewig 
To whom it may satisfy...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact folk at [EMAIL PROTECTED]

Project jakarta-tomcat-4.0 *no longer* has an issue.
Project State : 'Prerequisite Failed', Reason 'Build Failed'

Full details are available at:

http://brutus.apache.org:8080/gump/jakarta-tomcat-4.0/jakarta-tomcat-4.0/index.html

That said, some snippets follow:


The following annotations were provided:
 -INFO- Jar [naming-resources.jar] identifier set to jar basename: [naming-resources]
 -INFO- Jar [servlets-default.jar] identifier set to jar basename: [servlets-default]
 -INFO- Jar [naming-common.jar] identifier set to jar basename: [naming-common]
 -INFO- Jar [catalina.jar] identifier set to jar basename: [catalina]
 -INFO- Jar [bootstrap.jar] identifier set to jar basename: [bootstrap]
 -INFO- Jar [servlets-common.jar] identifier set to jar basename: [servlets-common]
 -INFO- Jar [servlets-invoker.jar] identifier set to jar basename: [servlets-invoker]
 -INFO- Dependency on javamail exists, no need to add for property mail.jar.
 -INFO- Dependency on jaf exists, no need to add for property activation.jar.
 -INFO- Dependency on jmx exists, no need to add for property jmx.jar.
 -INFO- Dependency on jakarta-servletapi-4 exists, no need to add for property 
servlet.jar.
 -INFO- Dependency on xml-xerces exists, no need to add for property xerces.jar.
 -INFO- Dependency on jakarta-tomcat-util exists, no need to add for property 
tomcat-util.jar.
 -INFO- Dependency on commons-logging exists, no need to add for property 
commons-logging-api.jar.
 -INFO- Dependency on ant exists, no need to add for property ant.home.
 -INFO- Dependency on jakarta-servletapi-4 exists, no need to add for property 
servlet.home.
 -INFO- Dependency on jsse exists, no need to add for property jsse.home.
 -INFO- Dependency on jmx exists, no need to add for property jmx.home.
 -INFO- Dependency on jmx exists, no need to add for property jmxtools.jar.
 -INFO- Dependency on jndi exists, no need to add for property jndi.home.
 -INFO- Dependency on jakarta-regexp exists, no need to add for property regexp.home.
 -INFO- Dependency on jakarta-regexp exists, no need to add for property regexp.jar.
 -INFO- Dependency on javamail exists, no need to add for property mail.home.
 -INFO- Dependency on jakarta-tomcat-coyote exists, no need to add for property 
tomcat-coyote.home.
 -INFO- Dependency on jaf exists, no need to add for property activation.home.
 -INFO- Prerequisite failed with reason build failed
 -INFO- Optional dependency avalon-phoenix prerequisite failed with reason build failed
 -INFO- Optional dependency avalon prerequisite failed with reason build failed
 -INFO- Optional dependency junit prerequisite failed with reason build failed



To subscribe to this information via syndicated feeds:
 RSS: http://brutus.apache.org:8080/gump/jakarta-tomcat-4.0/jakarta-tomcat-4.0/rss.xml
 Atom: 
http://brutus.apache.org:8080/gump/jakarta-tomcat-4.0/jakarta-tomcat-4.0/atom.xml


--
Produced by Gump 2.0.3-alpha-0002.
[Run (20040524 15:00:12, brutus:brutus-public:20040524 15:00:12)]
http://brutus.apache.org:8080/gump/index.html
http://brutus.apache.org:8080/gump/options.html

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

[GUMP@brutus]: jakarta-tomcat-4.0/tomcat-catalina prerequisite failed

2004-05-24 Thread Stefan Bodewig 
To whom it may satisfy...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact folk at [EMAIL PROTECTED]

Project tomcat-catalina *no longer* has an issue.
Project State : 'Prerequisite Failed', Reason 'Build Failed'

Full details are available at:

http://brutus.apache.org:8080/gump/jakarta-tomcat-4.0/tomcat-catalina/index.html

That said, some snippets follow:


The following annotations were provided:
 -INFO- Sole jar [catalina.jar] identifier set to project name
 -INFO- Dependency on jakarta-servletapi-4 exists, no need to add for property 
servlet.jar.
 -INFO- Dependency on commons-logging exists, no need to add for property 
commons-logging-api.jar.
 -INFO- Dependency on jakarta-regexp exists, no need to add for property regexp.jar.
 -INFO- Prerequisite failed with reason build failed



To subscribe to this information via syndicated feeds:
 RSS: http://brutus.apache.org:8080/gump/jakarta-tomcat-4.0/tomcat-catalina/rss.xml
 Atom: http://brutus.apache.org:8080/gump/jakarta-tomcat-4.0/tomcat-catalina/atom.xml


--
Produced by Gump 2.0.3-alpha-0002.
[Run (20040524 15:00:12, brutus:brutus-public:20040524 15:00:12)]
http://brutus.apache.org:8080/gump/index.html
http://brutus.apache.org:8080/gump/options.html

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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

respuestas sobre el Chat

2004-05-24 Thread ayudachat 


Algunas preguntas frecuentes sobre inconvenientes al ingresar al chat son:



Si puede ingresar su Nick en el recuadro de texto pero no inicia la sesión de chat 
pueder ser por que dicho Nick se encuentre registrado por otra persona en tal caso 
pruebe cambiarlo o agregarle algún numero.

También puede ser que su ip se encuentre prohibida por el moderador en este caso hay 
que esperar algunas horas hasta que se libere, observe el recuadro blanco de reportes 
cada vez que intenta ingresar para saber cual es el caso. Si sólo lee un mensaje de 
error puede ser necesario reiniciar su computadora.



FALTA DE MAQUINA VIRTUAL DE JAVA

Para Windows XP, WinNT, WinME, Win98

Si por alguna razón su navegador le avisa que NO tiene instalada la compatibilidad con 
JAVA, la mejor alternativa es bajar la Maquina virtual de Java desde el sitio oficial 
de Sun

http://www.java.com/en/index.jsp  En esta página clickeando en Download Java 
Software, automaticamentte le va a detectar e instalar la version necesaria para su 
PC.

 

Luego de un par de minutos que se complete el proceso ya lo puede probar

www.paysandu.com/chat



OTRAS RAZONES POSIBLES

Cuando aparece un recuadro gris en la pantalla y luego de varios segundos no aparece 
el acceso al Chat. Las razones pueden ser las siguientes, que en ese momento la 
conexión esté muy lenta y demora más de lo habitual; si es este el caso y esperando no 
se soluciona puede desconectarse/conectarse de Internet para volver a intentarlo. 

Si no se soluciona o nota que esto es frecuente, entonces puede ser que tenga muchos 
archivos temporales en el cache de su maquina.



Como Limpiar la memoria caché?

Si el caché está lleno, las páginas nuevas se abrirán muy lentamente o no se abrirán. 
Es posible que la memoria caché esté llena de páginas desfasadas o inútiles; por ello 
es buena idea limpiarla de vez en cuando. A continuación explicamos cómo limpiar la 
memoria caché dependiendo del navegador que tenga:



*

LIMPIAR CACHE EN INTERNET EXPLORER, instrucciones:



Haga clic en Herramientas (Tools) en la parte superior de la ventana de su navegador 
y luego seleccione Opciones de Internet (Internet Options).



Cuando emerja la ventana, haga clic en el cuadro eliminar archivos (delete files).



Marque la opción eliminar contenido fuera de línea (delete offline content) y haga 
clic en Aceptar (OK).



Haga también clic en el botón limpiar historial (clear history).



Haga clic en Aceptar (OK) hasta salir del cuadro de preferencias. 

Después de haber vaciado el caché, y estando conectado a Internet vaya a 
www.paysandu.com/chat.html oprima las teclas Ctrl y Shift y pulse el botón 
Actualizar (refresh) o (Reload) en su navegador a la misma vez luego de algunos 
segundos deberá aparecer el recuadro del nombre y boton login de acceso al Chat





LIMPIAR CACHE EN NETSCAPE, instrucciones:



Haga clic en edición (edit) en la parte superior de la ventana de su navegador y a 
continuación en preferencias (preferences).



Cuando emerja la ventana, haga clic en las opciones limpiar historial (clear 
history) y en limpiar barra de localización (clear location bar).



A continuación haga clic en el signo + que se encuentra junto a la opción avanzado 
(advanced).



Seleccione la opción caché.



Haga clic en las opciones limpiar memoria caché (clear memory cache) y en limpiar 
disco caché (clear disk cache).



Haga clic en Aceptar (OK) hasta salir de la ventana.





LIMPIAR CACHE EN AOL, siga los siguientes pasos:



Busque preferencias (preferences) en el menú mi aol (my aol).



Luego haga clic en www.



Haga clic en el botón eliminar archivos (delete files). Aparecerá una ventana 
preguntándole si desea borrar los archivos temporales de Internet.



Marque el cuadro de la opción eliminar contenido fuera de línea (delete offline 
content) y haga clic en el botón Aceptar (OK).



A continuación haga clic en el botón eliminar historial (delete history).



Haga clic en Aceptar (OK) hasta que salga del menú de preferencias.

Después de haber vaciado el caché, vaya a www.paysandu.com/chat.html y pulse el botón 
Actualizar (refresh) o Volver a cargar (Reload) en su navegador



**

Si usted es usuario de WebTv no podrá acceder al Chat, esta es una limitacion del 
proveedor de este tipo de servicio que no admite Java. Tampoco se pueden conectar en 
una red interna a través de un Fire Wall sin que el administrador del mismo lo 
autorice previamente.



En este chat al igual que en el foro de encuentros, los enlaces entre usuarios y o 
canales se producen 100% en la web de www.paysandu.com es decir no exiten accesos a 
través de servidores IRC u de otro tipo.



  





COMANDOS DE USO EN EL CHAT DE ENCUENTROS SANDUCEROS



Los siguientes comandos se pueden ejecutar en la línea de diálogo seguidos del 
caractér / 



algunos de ellos se han simplificado incorporándolos al botón derecho del mouse

DO NOT REPLY [Bug 29056] - java.util.ConcurrentModificationException

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29056.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

java.util.ConcurrentModificationException





--- Additional Comments From [EMAIL PROTECTED]  2004-05-25 02:46 ---
Upon further investigation I found my config file (brought forward from TC4) 
was explicitly referring to the connector class:

Connector  className=org.apache.coyote.tomcat4.CoyoteConnector ...

Removing this has resolved the issue.

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

DO NOT REPLY [Bug 29160] - precompile problem: _jspx_meth_* (javax.servlet.jsp.tagext.JspTag,javax.servlet.jsp.PageContext) cannot be applied to (org.apache.struts.taglib.*.*Tag,javax.servlet.jsp.PageContext)

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29160.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

precompile problem: _jspx_meth_* 
(javax.servlet.jsp.tagext.JspTag,javax.servlet.jsp.PageContext) cannot be applied to 
(org.apache.struts.taglib.*.*Tag,javax.servlet.jsp.PageContext)





--- Additional Comments From [EMAIL PROTECTED]  2004-05-25 04:17 ---
 From: Jan Luehe [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, May 25, 2004 1:35 AM
 To: [EMAIL PROTECTED]
 Subject: Re: DO NOT REPLY [Bug 29160] New: - precompile problem:
 
 Any chance you could attach your webapp to the bugreport, or
 send me a copy?
hope you can already reproduce it with the attached one sample.tgz file that is
created by my jspc.
When doing the target compile(jsp), I get
[javac] 27 errors
[javac] 10 warnings

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

DO NOT REPLY [Bug 29160] - precompile problem: _jspx_meth_* (javax.servlet.jsp.tagext.JspTag,javax.servlet.jsp.PageContext) cannot be applied to (org.apache.struts.taglib.*.*Tag,javax.servlet.jsp.PageContext)

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29160.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

precompile problem: _jspx_meth_* 
(javax.servlet.jsp.tagext.JspTag,javax.servlet.jsp.PageContext) cannot be applied to 
(org.apache.struts.taglib.*.*Tag,javax.servlet.jsp.PageContext)





--- Additional Comments From [EMAIL PROTECTED]  2004-05-25 04:10 ---
Created an attachment (id=11644)
one sample jsp.java that causes these errors

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

DO NOT REPLY [Bug 29160] - precompile problem: _jspx_meth_* (javax.servlet.jsp.tagext.JspTag,javax.servlet.jsp.PageContext) cannot be applied to (org.apache.struts.taglib.*.*Tag,javax.servlet.jsp.PageContext)

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29160.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

precompile problem: _jspx_meth_* 
(javax.servlet.jsp.tagext.JspTag,javax.servlet.jsp.PageContext) cannot be applied to 
(org.apache.struts.taglib.*.*Tag,javax.servlet.jsp.PageContext)





--- Additional Comments From [EMAIL PROTECTED]  2004-05-25 04:23 ---
Created an attachment (id=11645)
sample_jsp.tgz - this time the correct one, pls discard the previous

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

DO NOT REPLY [Bug 29174] - complain about liveDeploy tags and enhance documentation of deployOnStartup

2004-05-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29174.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

complain about liveDeploy tags and enhance documentation of deployOnStartup

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |



--- Additional Comments From [EMAIL PROTECTED]  2004-05-25 04:47 ---
Since there is no DTD for the server.xml as per the faq
http://jakarta.apache.org/tomcat/faq/misc.html#dtd i.e. is there a way other
than going through the source code where I can see whether the liveDeploy is
still valid and what it would do under tomcat 5?

http://www.onjava.com/pub/a/onjava/2004/01/28/tomcat5.html?page=last appears to
suggest that liveDeploy no longer exists, but then I would expect a stackdump
complaining about this when doing bin/startup.sh

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