DO NOT REPLY [Bug 21763] - Tomcat 4.1.24 hangs under heavy load using http connector.

2004-05-28 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=21763.
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=21763

Tomcat 4.1.24 hangs under heavy load using http connector.





--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 07:08 ---
We have the same problem on Tomcat 5.0.19 under Slackware 9.1.0 (2.6.5 kernel):

catalina.out-May 27, 2004 2:20:48 PM org.apache.tomcat.util.threads.ThreadPool
logFull
catalina.out:SEVERE: All threads (300) are currently busy, waiting. Increase
maxThreads (300) or check the servlet status

Our HTTP connector configuration is:
Connector port=8080
   maxThreads=300 minSpareThreads=30 maxSpareThreads=80
   enableLookups=false redirectPort=8443 acceptCount=100
   debug=0 connectionTimeout=2
   disableUploadTimeout=true /

We use big heavy-load web application with some dozens of JSPs with XML
transformation and MySQL storage.

We will try to find luck in Tomcat 5.0.25...

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



Re: DO NOT REPLY [Bug 21763] -

2004-05-28 Thread newstuff
=

EXTREME Funny Pictures Of The Day

=



Thank You For Emailing EXTREME Funny Pictures!





UNSUBSCRIBE INSTRUCTIONS





To stop our newsletter, click below and fill in your email address:

http://www.extremefunnypictures.com/unsubscribe.htm

a href=http://www.extremefunnypictures.com/unsubscribe.htm;Click/a





=

CONTACT INFORMATION

=



This is an autoresponder to let you know that in order to contact 

EXTREME Funny Pictures you must go to:

http://www.extremefunnypictures.com/feedback.htm

a href=http://www.extremefunnypictures.com/feedback.htm;Click/a



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



respuestas sobre el Chat

2004-05-28 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 29259] - Used MX4J 2.0.1 HttpAdpator

2004-05-28 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=29259.
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=29259

Used MX4J 2.0.1 HttpAdpator





--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 07:27 ---
Sorry but one problem exists:

The MX4J 2.0.1 not release the Jrmp and iiop adaptor any more.
The classes exists at src...

What we can do ?
Create and add a new adaptor to support the JSR160 Remote Interface  
Compile and bundle and bundle the old classes
 

regards,
Peter

Also the ServerLifecycleListener Options (MBeansUtils.createRMIAdaptor)
not working with MX4J 2.0.1 without compile the Adaptor classes by your self.

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



DO NOT REPLY [Bug 29266] New: - AJP13 - IOException: Broken pipe

2004-05-28 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=29266.
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=29266

AJP13 - IOException: Broken pipe

   Summary: AJP13 - IOException: Broken pipe
   Product: Tomcat 3
   Version: 3.3.1 Release Candidate 1
  Platform: Other
OS/Version: Linux
Status: NEW
  Severity: Major
  Priority: Other
 Component: Connectors
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


We have a web application running in Apache 1.3.2 and Tomcat 3.3.1a We get the 
following exception sometimes  and it makes the system unstable and we are 
forced to restart the server.

Exception java.io.IOException: Broken pipe
at java.net.SocketOutputStream.socketWrite(Native Method)
at java.net.SocketOutputStream.write(SocketOutputStream.java:91)
at org.apache.tomcat.modules.server.Ajp13.send(Ajp13.java:841)
at org.apache.tomcat.modules.server.Ajp13.doWrite(Ajp13.java:727)
at org.apache.tomcat.modules.server.Ajp13Response.doWrite(Ajp13Intercept
or.java:491)
at org.apache.tomcat.core.OutputBuffer.realWriteBytes(OutputBuffer.java:
188)
at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360)
at org.apache.tomcat.core.OutputBuffer.flush(OutputBuffer.java:315)
at org.apache.tomcat.core.Response.flushBuffer(Response.java:402)
at org.apache.tomcat.facade.HttpServletResponseFacade.flushBuffer(HttpSe
rvletResponseFacade.java:303)
at org.apache.jasper.runtime.JspWriterImpl.flush(JspWriterImpl.java:209
...

Please let us know why this is happening and how we can correct this problem?

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



DO NOT REPLY [Bug 29258] - Tomcat 5.0.24+ jmx.jar may not be in CLASSPATH

2004-05-28 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=29258.
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=29258

Tomcat 5.0.24+ jmx.jar may not be in CLASSPATH





--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 08:28 ---
I think originally this worked by having inside the manifest of bootstrap.jar
the line

Class-Path: jmx.jar commons-daemon.jar commons-logging-api.jar

and putting jmx.jar to the bin directory.

-
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-28 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-28 08:38 ---
 I'm not sure a fix to URLClassLoader to not lock jar files is that easy, even 
 if it's desirable.

Agreed. Also, it's desirable to support existing JDKs.

Adding fork attribute to JspC would be sufficient, although I'm not sure if it's
that easy, because:

- You would have to also specify a classpath attribute (or nested element) that
would tell the task what classpath to use when the separate JVM is run
- You would need to capture output from the separate process and somehow
redirect it to the original task's output (Ant output).
- You may want to allow all the attributes that the java task has that relate
to JVM parameters, such as jvm, maxmemory, jvmargs, failonerror, or nested
elements jvmarg, sysproperty

Is this (easily) doable?

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



DO NOT REPLY [Bug 29269] New: - Session in JSp not available to Servlet

2004-05-28 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=29269.
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=29269

Session in JSp not available to Servlet

   Summary: Session in JSp not available to Servlet
   Product: Tomcat 5
   Version: 5.0.25
  Platform: Other
OS/Version: Windows XP
Status: NEW
  Severity: Major
  Priority: Other
 Component: Servlet  JSP API
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Hi, 

Session in JSP is not accessible to servlet. Please could you have a look at it. 
Let me know if u need any more information

code in JSP
---

%
out.println(BRBR);
session.setAttribute(Test,Hello Test);
%
FORM METHOD=POST ACTION=/dvt/servlet/dvt.TestServlet

INPUT TYPE=text NAME=test value='%=(String) session.getAttribute(Test)%
'
INPUT TYPE=submit
/FORM


code in servlet
---

PrintWriter out = res.getWriter();
String test=Hello Fran;
HttpSession session = req.getSession();
session.setAttribute(From, From Session);
out.println(htmlbodyh1+(String)session.getAttribute(Test));


Tomcat version : 5.0.25
OS : Win XP professional


regards,
Fran

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



DO NOT REPLY [Bug 21763] - Tomcat 4.1.24 hangs under heavy load using http connector.

2004-05-28 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=21763.
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=21763

Tomcat 4.1.24 hangs under heavy load using http connector.

[EMAIL PROTECTED] changed:

   What|Removed |Added

Version|4.1.24  |4.1.30

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



DO NOT REPLY [Bug 29274] New: - WebAppClassLoader does not release loaded classes if webapp is reloaded

2004-05-28 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=29274.
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=29274

WebAppClassLoader does not release loaded classes if webapp is reloaded

   Summary: WebAppClassLoader does not release loaded classes if
webapp is reloaded
   Product: Tomcat 5
   Version: 5.0.19
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


If a wepapp is reloaded using the Tomcat manager, memory occupied by reference 
type static members from the webapp's classes is not released.

Memory is only released if the webapp is undeployed.

I guess this is a problem of the WebAppClassLoader. A class itself is only 
unloaded by the JVM if it's classloader was finalized. If after a reload from 
the manager the webapp still uses the same classloader, old classes will not 
get unloaded and so their memory will never be freed resulting in 
OutOfMemoryError`s.

Sample code:

class SomeServlet extends HttpServlet {
static byte[] bigData = new byte[5000];
protected void service(HttpServletRequest arg0, HttpServletResponse 
arg1)
throws ServletException, IOException {
}
}

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



DO NOT REPLY [Bug 28612] - configure script fails locating libapr

2004-05-28 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=28612.
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=28612

configure script fails locating libapr





--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 14:01 ---
Can you please suggest a patch and attach it to this bugzilla item?

-
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-28 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-28 14:15 ---
What I had in mind actually was either very simple or complex, depending on how 
you look at it: have org.apache.jasper.JspC extend 
org.apache.tools.ant.taskdefs.Java ;)  That way we get all the attributes of 
that task (classpath, jvmargs, sysproperty, forking, etc.) without having to 
write code for it.  We already have the ant.jar in common/lib, so we won't be 
adding any dependencies.

The complex part might be the testing: I don't know the JspC task well enought 
to comprehensively test it.

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



DO NOT REPLY [Bug 29269] - Session in JSp not available to Servlet

2004-05-28 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=29269.
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=29269

Session in JSp not available to Servlet





--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 14:23 ---
You need the %@ page session=true % directive in your JSP.  With that 
directive, I can successfully set session attributes in JSPs and see them in 
servlets.

Please attach your entire JSP and Servlet code, not snippets, preferably as one 
WAR file (with web.xml etc.) we can drop into our server to reproduce your 
results.

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



DO NOT REPLY [Bug 27222] - Jk2: error mmapping shm file leads to workerEnv.init() create slot epStat.0 failed on Apache 1.3

2004-05-28 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=27222.
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=27222

Jk2: error mmapping shm file leads to workerEnv.init() create slot epStat.0 failed on 
Apache 1.3





--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 14:29 ---
Set shm.disabled=1 where?  In the configuration file, right?  So this is not a 
code bug, but we should update our documentation to include your suggestion.  
Is my understanding correct?

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



DO NOT REPLY [Bug 28654] - Load balancer doesn't work for jk 2.0.4 with IIS

2004-05-28 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=28654.
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=28654

Load balancer doesn't work for jk 2.0.4 with IIS

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 14:39 ---
Please use the tomcat-user list for debugging, investigating configurations, 
inquiring about different load balancing options, etc.  This is not the place 
for a long discusssion, only exact bugs and test cases we can use to reproduce 
them.  Thanks.

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



DO NOT REPLY [Bug 28469] - stderr is closed when it is used by jk_logger_file.c

2004-05-28 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=28469.
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=28469

stderr is closed when it is used by jk_logger_file.c





--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 14:42 ---
This is an OK place to put the bug.  So we should modify the jk2_workerEnv_init 
method so that if it already has a handle on stderr, it won't close and reopen? 
Why doesn't it work actually, after all the second stderr handle should still 
be valid, no?

If you have an actual patch to jk_logger_file.c it'd be welcome.

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



DO NOT REPLY [Bug 29258] - Tomcat 5.0.24+ jmx.jar may not be in CLASSPATH

2004-05-28 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=29258.
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=29258

Tomcat 5.0.24+ jmx.jar may not be in CLASSPATH





--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 14:44 ---
The manifest for bootstrap.jar has not changed: it still contains jmx.jar 
before commons-logging in the classpath line.  Also, jmx.jar is still in the 
bin directory, so that hasn't changed either.

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



DO NOT REPLY [Bug 28654] - Load balancer doesn't work for jk 2.0.4 with IIS

2004-05-28 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=28654.
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=28654

Load balancer doesn't work for jk 2.0.4 with IIS

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |



--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 15:04 ---
I wasn't starting a discussion, this is a bug. Load balancing just doesn't 
work with IIS and JK2 2.0.4. If you try it you'll see.
I use the same workers2.properties and Tomcat config for both Apache2 and IIS 
(I just switch between using Apache or IIS depending on what our customer 
wants), but I also have to comment out the group=lb and set a worker to get 
around this bug at the moment.
What sort of test case do you want? Just set up load balancing in JK2 with IIS 
and it doesn't work!!!

-
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-28 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)

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED



--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 15:30 ---
must have been a classloader problem, i.e. it may have found some of the jars
twice. 
When I only take the classpath:
WEB-INF/classes:tomcat/common/lib:struts.jar:displaytag-1.0-b2.jar

or Jan's 
javac -classpath jsp-api.jar:servlet-api.jar:jasper-runtime.jar:struts.jar:.
java-filename

it does compile!
Thx!

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



DO NOT REPLY [Bug 29258] - Tomcat 5.0.24+ jmx.jar may not be in CLASSPATH

2004-05-28 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=29258.
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=29258

Tomcat 5.0.24+ jmx.jar may not be in CLASSPATH





--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 15:36 ---
I would update the change logs to add a more explicit comment about
jmx.jar residing in bin instead of common/lib.  Anything more than
that is probably overkill since you only get this problem when you
do something odd to the install (like moving the jmx.jar file into
common/lib again, etc.).

Adding jmx.jar to the startup scripts might help make it clear that
the startup has JMX dependencies.

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



DO NOT REPLY [Bug 29258] - Tomcat 5.0.24+ jmx.jar may not be in CLASSPATH

2004-05-28 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=29258.
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=29258

Tomcat 5.0.24+ jmx.jar may not be in CLASSPATH

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 15:45 ---
It was already in the changelog (v5.0.20), but I don't think that's visible 
enough, so I've added the following to the RELEASE NOTES file, in the standard 
APIs section:

Please note that the JMX API is available to applications as well.  The jmx.jar
file used to be located in the common/lib directory, but was moved to the bin
directory as part of the Tomcat 5.0.20 release.  The jmx.jar is in Tomcat's
bootstrap classpath (included via the Class Path line in bootstrap.jar's 
manifest).

This will of course be visible and available starting with the next release, 
5.0.26.

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



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

2004-05-28 Thread yoavs
yoavs   2004/05/28 08:57:33

  Modified:webapps/docs changelog.xml
  Log:
  Added release notes note about jmx.jar in bootstrap classpath.
  
  Revision  ChangesPath
  1.59  +3 -0  jakarta-tomcat-catalina/webapps/docs/changelog.xml
  
  Index: changelog.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/changelog.xml,v
  retrieving revision 1.58
  retrieving revision 1.59
  diff -u -r1.58 -r1.59
  --- changelog.xml 28 May 2004 00:04:31 -  1.58
  +++ changelog.xml 28 May 2004 15:57:33 -  1.59
  @@ -33,6 +33,9 @@
 fix
   bug24723/bug: Corrected JNDI DataSources documentation and added 
explicit notes about a couple of common problems. (yoavs)
 /fix
  +  fix
  +bug29258/bug: Added explanation about jmx.jar bootstrap classpath setup 
to release notes. (yoavs)
  +  /fix
   /changelog
 /subsection
 
  
  
  

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



cvs commit: jakarta-tomcat-5 RELEASE-NOTES

2004-05-28 Thread yoavs
yoavs   2004/05/28 08:57:44

  Modified:.RELEASE-NOTES
  Log:
  Added release notes note about jmx.jar in bootstrap classpath.
  
  Revision  ChangesPath
  1.17  +6 -1  jakarta-tomcat-5/RELEASE-NOTES
  
  Index: RELEASE-NOTES
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- RELEASE-NOTES 26 May 2004 13:02:44 -  1.16
  +++ RELEASE-NOTES 28 May 2004 15:57:44 -  1.17
  @@ -75,6 +75,11 @@
   Tomcat 5.0 also makes Xerces 2 and the Commons Logging API (release 1.0.3)
   available to web applications.
   
  +Please note that the JMX API is available to applications as well.  The jmx.jar
  +file used to be located in the common/lib directory, but was moved to the bin
  +directory as part of the Tomcat 5.0.20 release.  The jmx.jar is in Tomcat's
  +bootstrap classpath (included via the Class Path line in bootstrap.jar's manifest).
  +
   
   --
   Tomcat 5.0 and XML Parsers:
  
  
  

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



DO NOT REPLY [Bug 28654] - Load balancer doesn't work for jk 2.0.4 with IIS

2004-05-28 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=28654.
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=28654

Load balancer doesn't work for jk 2.0.4 with IIS





--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 16:56 ---
I wasn't entering into a discussion about how configure load-balancing. 
 
I was giving work-around details about how to disable load-balancing 
which, as written, doesn't work. 
 
Sorry to pollute the purity of this bug log, but when something doesn't 
work for me, I check the documentation, and then the bug reports. So it 
seems to me that this is exactly the right place for this discussion. 
 
Excuse me while I write up a documentation bug ;^}

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



respuestas sobre el Chat

2004-05-28 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 28234] - uri: worker property does not exist any more

2004-05-28 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=28234.
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=28234

uri: worker property does not exist any more





--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 17:49 ---
On what page does the URL read tomcat-4.1 BTW if I browse the 5.0 
documentation ?

Please submit clarified and/or enhanced text for those documentation areas you 
feel are lacking.

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



DO NOT REPLY [Bug 29283] New: - Exception: StandardSession.invalidate

2004-05-28 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=29283.
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=29283

Exception: StandardSession.invalidate

   Summary: Exception: StandardSession.invalidate
   Product: Tomcat 4
   Version: 4.1.29
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: Critical
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Tomcat appears to be expiring sessions prematurely and gives an exception in 
the StandardManager during session invalidation.

java.lang.IllegalStateException: invalidate: Session already invalidated
at org.apache.catalina.session.StandardSession.invalidate
(StandardSession.java:1033)
at com.audium.server.controller.Controller.invalidateSession(Unknown 
Source)
at com.audium.server.session.c.valueUnbound(Unknown Source)
at org.apache.catalina.session.StandardSession.removeAttribute
(StandardSession.java:1155)
at org.apache.catalina.session.StandardSession.expire
(StandardSession.java:635)
at org.apache.catalina.session.StandardSession.expire
(StandardSession.java:608)
at org.apache.catalina.session.StandardManager.processExpires
(StandardManager.java:793)
at org.apache.catalina.session.StandardManager.run
(StandardManager.java:870)
at java.lang.Thread.run(Thread.java:536)

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



DO NOT REPLY [Bug 28961] - loggers shift files but don't roll (not deleting oldest files by prescribes file count)

2004-05-28 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=28961.
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=28961

loggers shift files but don't roll (not deleting oldest files by prescribes file count)





--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 18:09 ---
The Remy I'm referring to is Remy Maucherat, another Tomcat developer.  Please 
ignore that reference, though, as it is too long to explain and not a big deal 
anyways ;)

I understand that to you rolling implies also deleting files as configured by 
the deployer/integrator/administrator.  My concept of rolling is different, and 
includes only the rolling itself, not removal or archival of any kind.  Those 
are separate concerns which merit separate policies, as we're doing for example 
in log4j 1.3.  

So yes, we ARE saying to tomcat deployers / integrators / administrators that 
they're responsible for assuring their server logs don't run out of space.  
Just like we tell application developers on the tomcat-user list to NOT use the 
Loggers, and use a logging toolkit like log4j if at all possible, because of 
the enhanced features those toolkits provides.

Though Loggers are required by the Servlet Specification, not even simple 
rolling is required, and so tomcat would be perfectly in line to just dump all 
output to System.out.

That said, I can see the value in log4j/java.util.logging proxies, so if you 
submit code for them, I'll be glad to review/comment/commit it as needed.

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



DO NOT REPLY [Bug 28966] - JSP pages with UTF-8 characters always displays as ISO-8859-1

2004-05-28 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=28966.
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=28966

JSP pages with UTF-8 characters always displays as ISO-8859-1





--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 18:12 ---
I'm not familiar enough with the relevant code to offer a solution, but I do 
have a suggestion: send your query to the tomcat-user list and see if others 
can provide feedback.  If they do, maybe we can narrow this down to a specific 
location in the code, and then amend this bug report to include that specific 
information.

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



cvs commit: jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session ReplicatedSession.java SimpleTcpReplicationManager.java

2004-05-28 Thread fhanik
fhanik  2004/05/28 11:49:37

  Modified:modules/cluster/src/share/org/apache/catalina/cluster/session
ReplicatedSession.java
SimpleTcpReplicationManager.java
  Log:
  using the logger instead of the old debug flag
  
  Revision  ChangesPath
  1.14  +2 -2  
jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session/ReplicatedSession.java
  
  Index: ReplicatedSession.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session/ReplicatedSession.java,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- ReplicatedSession.java27 May 2004 15:11:21 -  1.13
  +++ ReplicatedSession.java28 May 2004 18:49:37 -  1.14
  @@ -239,7 +239,7 @@
   protected void log(String message) {
   
   if ((mManager != null)  (mManager instanceof 
SimpleTcpReplicationManager)) {
  -((SimpleTcpReplicationManager) mManager).log(message);
  +((SimpleTcpReplicationManager) mManager).log.debug(ReplicatedSession: 
 + message);
   } else {
   System.out.println(ReplicatedSession:  + message);
   }
  @@ -249,7 +249,7 @@
   protected void log(String message, Throwable x) {
   
   if ((mManager != null)  (mManager instanceof 
SimpleTcpReplicationManager)) {
  -((SimpleTcpReplicationManager) mManager).log(message,x);
  +((SimpleTcpReplicationManager) mManager).log.error(ReplicatedSession: 
 + message,x);
   } else {
   System.out.println(ReplicatedSession:  + message);
   x.printStackTrace();
  
  
  
  1.25  +16 -52
jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session/SimpleTcpReplicationManager.java
  
  Index: SimpleTcpReplicationManager.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session/SimpleTcpReplicationManager.java,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- SimpleTcpReplicationManager.java  27 May 2004 15:11:21 -  1.24
  +++ SimpleTcpReplicationManager.java  28 May 2004 18:49:37 -  1.25
  @@ -97,8 +97,6 @@
   
   protected String name;
   
  -protected int debug = 0;
  -
   protected boolean distributable = true;
   
   protected CatalinaCluster cluster;
  @@ -137,7 +135,7 @@
   }
   
   public void setCluster(CatalinaCluster cluster) {
  -this.log(Cluster associated with SimpleTcpReplicationManager);
  +this.log.debug(Cluster associated with SimpleTcpReplicationManager);
   this.cluster = cluster;
   }
   
  @@ -148,7 +146,7 @@
   
   public void setPrintToScreen(boolean printtoscreen)
   {
  -log(Setting screen debug to:+printtoscreen);
  +log.debug(Setting screen debug to:+printtoscreen);
   mPrintToScreen = printtoscreen;
   }
   
  @@ -166,15 +164,6 @@
   }
   }
   
  -public int getDebug()
  -{
  -return this.debug;
  -}
  -
  -public void setDebug(int debug) {
  -this.debug = debug;
  -//super.setDebug(debug);
  -}
   /**
* Creates a HTTP session.
* Most of the code in here is copied from the StandardManager.
  @@ -314,7 +303,7 @@
   }
   
   session.setIsDirty(false);
  -if (getDebug()  5) {
  +if (log.isDebugEnabled()) {
   try {
   log.debug(Sending session to cluster= + session);
   }
  @@ -330,7 +319,7 @@
   }
   catch (Exception x )
   {
  -log(Unable to replicate session,x);
  +log.error(Unable to replicate session,x);
   }
   return null;
   }
  @@ -361,7 +350,7 @@
   }
   catch ( Exception x )
   {
  -log(Failed to serialize the session!,x,1);
  +log.error(Failed to serialize the session!,x);
   }
   return null;
   }
  @@ -422,7 +411,7 @@
   }
   catch ( Exception x )
   {
  -log(Failed to deserialize the session!,x,1);
  +log.error(Failed to deserialize the session!,x);
   }
   return null;
   }
  @@ -448,9 +437,9 @@
   try {
   //the channel is already running
   if ( mChannelStarted ) return;
  -log(Starting clustering manager...:+getName(),1);
  +log.error(Starting clustering manager...:+getName());
   if ( cluster == null ) {
  -log(Starting... no cluster associated with this 

DO NOT REPLY [Bug 29283] - Exception: StandardSession.invalidate

2004-05-28 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=29283.
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=29283

Exception: StandardSession.invalidate

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 19:25 ---
The servlet spec specifies that if an BindingListener is unbound from a 
session because the session expired, then the event occurs after the session 
is invalidated.

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



DO NOT REPLY [Bug 29283] - Exception: StandardSession.invalidate

2004-05-28 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=29283.
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=29283

Exception: StandardSession.invalidate

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |



--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 19:37 ---
What exactly does this mean?  

The servlet spec specifies that if an BindingListener is unbound from a 
session because the session expired, then the event occurs after the session 
is invalidated.

I am running a vendor supplied application and the session associated with this 
error is not receiving the session timeout and therefore is retaining the 
session as active.

It would appear that the exception interrupted the process whereby the 
application is notified of the session termination.

If this is not a problem, then why is the exception thrown?  Why isn't the 
application notified of the session termination?

If the BindingListener is unbound as you say from the session, why would this 
subsequently cause a Tomcat exception?  Wouldn't it invalidate the session and 
continue normally?

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



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

2004-05-28 Thread bobh
To whom it may engage...

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-5 has an issue affecting its community integration, and has 
been outstanding for 5 runs.
Project State : 'Failed', Reason 'Build Failed'

Full details are available at:

http://brutus.apache.org:8080/gump/jakarta-tomcat-5/jakarta-tomcat-5/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 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-el exists, no need to add for property commons-el.jar.
 -INFO- Dependency on commons-logging exists, no need to add for property 
commons-logging-api.jar.
 -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 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 jmx exists, no need to add for property jmx-tools.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 jakarta-tomcat-jasper_tc5 exists, no need to add for property 
jasper.home.
 -INFO- Dependency on jaf exists, no need to add for property activation.home.
 -INFO- Dependency on commons-modeler exists, no need to add for property 
commons-modeler.home.
 -INFO- Dependency on commons-daemon exists, no need to add for property 
commons-daemon.jsvc.tar.gz.
 -INFO- Dependency on jakarta-struts exists, no need to add for property struts.home.
 -INFO- Enable verbose output, due to 4 previous error(s).
 -INFO- Failed with reason build failed
 -INFO- Enable debug output, due to build failure.


The following work was performed:
http://brutus.apache.org:8080/gump/jakarta-tomcat-5/jakarta-tomcat-5/gump_work/build_jakarta-tomcat-5_jakarta-tomcat-5.html
Work Name: build_jakarta-tomcat-5_jakarta-tomcat-5 (Type: Build)
State: Failed
Elapsed: 0 hours, 0 minutes, 29 seconds
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main -verbose 
-Dgump.merge=/usr/local/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only 
-Dtomcat33.home=*Unset* 
-Djsp-api.jar=/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr152/dist/lib/jsp-api.jar
 -Djmx.jar=/usr/local/gump/packages/jmx-1_2-ri/lib/jmxri.jar 
-Djmx.home=/usr/local/gump/packages/jmx-1_2-ri 
-Djdbc20ext.jar=/usr/local/gump/packages/jdbc2_0/jdbc2_0-stdext.jar 
-Dregexp.jar=/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-20040528.jar
 -Dmail.home=/usr/local/gump/packages/javamail-1.3 
-Dant.home=/usr/local/gump/public/workspace/ant/dist 
-Dsite2.home=/usr/local/gump/public/workspace/jakarta-site2 
-Dcommons-collections.jar=/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-20040528.jar
 -Dldap.jar=/usr/local/gump/packages/ldap-1_2_4/lib/ldap.jar 
-DxercesImpl.jar=/usr/local/gump/public/workspace/xml

DO NOT REPLY [Bug 29283] - Exception: StandardSession.invalidate

2004-05-28 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=29283.
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=29283

Exception: StandardSession.invalidate

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||DUPLICATE



--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 21:39 ---


*** This bug has been marked as a duplicate of 14283 ***

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



DO NOT REPLY [Bug 14283] - StandardSession does not guard against Listener exceptions

2004-05-28 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=14283.
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=14283

StandardSession does not guard against Listener exceptions

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]



--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 21:39 ---
*** Bug 29283 has been marked as a duplicate of this bug. ***

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



DO NOT REPLY [Bug 29286] New: - Undeploy App does not delete WAR file

2004-05-28 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=29286.
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=29286

Undeploy App does not delete WAR file

   Summary: Undeploy App does not delete WAR file
   Product: Tomcat 5
   Version: 5.0.25
  Platform: PC
OS/Version: Windows XP
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Webapps:Manager
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Actions:

1 - Bring up HTML manager app page
2 - Click Undeploy link next to desired application
3 - Status message indicates success, expanded directory under webapps is
removed, WAR file under same directory is NOT removed

This prevents re-deployment of the app as Tomcat refuses to overwrite the WAR.

Text from your documentation:

WARNING - This command will delete the contents of the web application directory
if it exists within the appBase directory (typically webapps) for this virtual
host . **This will also delete the source .WAR** if expanding occurred, as well
as the XML Context definition. If you simply want to take an application out of
service, you should use the /stop command instead.

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



DO NOT REPLY [Bug 29286] - Undeploy App does not delete WAR file

2004-05-28 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=29286.
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=29286

Undeploy App does not delete WAR file





--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 21:50 ---
This is not a problem in 5.0.19

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



DO NOT REPLY [Bug 29283] - Exception: StandardSession.invalidate

2004-05-28 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=29283.
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=29283

Exception: StandardSession.invalidate





--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 21:56 ---
Thank you.  This does not resolve the my current situation, but at least I 
better understand the issue.  This problem did not occur at our site(s) with 
version 4.0.6, but then we were also using a previous version of the 
application.

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



DO NOT REPLY [Bug 28961] - loggers shift files but don't roll (not deleting oldest files by prescribes file count)

2004-05-28 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=28961.
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=28961

loggers shift files but don't roll (not deleting oldest files by prescribes file count)





--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 22:21 ---
Precision:

We don't log to tomcat, we don't use tomcat nor servlet loggers.
We don't even write to system out. We do use log4j since the beginning.

But tomcat is logging by itself. And we want it to log whatever goes wrong with
it. Only we can't tell it to roll-and-delete.

Hope this makes more sense now.

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



DO NOT REPLY [Bug 28961] - loggers shift files but don't roll (not deleting oldest files by prescribes file count)

2004-05-28 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=28961.
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=28961

loggers shift files but don't roll (not deleting oldest files by prescribes file count)





--- Additional Comments From [EMAIL PROTECTED]  2004-05-28 23:38 ---
package company.util;

import java.beans.PropertyChangeListener;
import java.beans.PropertyChangeSupport;

import org.apache.catalina.Container;
import org.apache.catalina.Logger;

/**
 * in logging properties:
 * 
 * log4j.category.tomcatlog=INFO, tomcat
 * 
 * log4j.appender.tomcat=org.apache.log4j.RollingFileAppender
 * log4j.appender.tomcat.MaxFileSize=1000KB
 * log4j.appender.tomcat.MaxBackupIndex=9
 * log4j.appender.tomcat.Append=true
 * log4j.appender.tomcat.File=tomcat.log
 * log4j.appender.tomcat.layout=org.apache.log4j.PatternLayout
 * log4j.appender.tomcat.layout.ConversionPattern=%d %-5p [%t] %c - %m%n
 * 
 * 
 * In server.xml:
 * 
 * Logger verbosity=4 className=company.util.Log4JLogger
log4JLoggerName=tomcatlog/
 *
 * Drop log4j jar in tomcat's common/lib
 * 
 * Drop this Log4JLogger class under proper tree under server/classes
 * 
 */
public class Log4JLogger implements Logger {

static final String info = Log4JLogger.class.getName()+/1.0;

PropertyChangeSupport support = new PropertyChangeSupport(this);
Container container = null;
int debug = 0;
int verbosity = ERROR;
String loggerName;

org.apache.log4j.Logger log4jLogger = null;


public Log4JLogger() {
log4jLogger = org.apache.log4j.Logger.getLogger(Log4JLogger.class);
}

public void setLog4JLoggerName(String loggerName) {
if(loggerName!=null) {
org.apache.log4j.Logger l = 
org.apache.log4j.Logger.getLogger(loggerName);
if(l!=null) {
log4jLogger = l;
this.loggerName = loggerName;
}
} else {
this.loggerName = null;
log4jLogger = 
org.apache.log4j.Logger.getLogger(Log4JLogger.class);
}
}

public String getLog4JLoggerName() {
return loggerName;
}

//--

public void log(Exception exception, String msg) {
log4jLogger.error(msg, exception);
}

public void log(String message, int verbosity) {
if (this.verbosity = verbosity) {
switch(verbosity) {
case FATAL: log4jLogger.fatal(message); break;
case ERROR: log4jLogger.error(message); break;
case WARNING: log4jLogger.warn(message); break;
case INFORMATION: log4jLogger.info(message); break;
case DEBUG: log4jLogger.debug(message); break;
}
}
}
public void log(String message, Throwable throwable, int verbosity) {
if (this.verbosity = verbosity) {
switch(verbosity) {
case FATAL: log4jLogger.fatal(message, throwable); 
break;
case ERROR: log4jLogger.error(message, throwable); 
break;
case WARNING: log4jLogger.warn(message, throwable); 
break;
case INFORMATION: log4jLogger.info(message, 
throwable); break;
case DEBUG: log4jLogger.debug(message, throwable); 
break;
}
}
}
public void log(String message, Throwable throwable) {
log4jLogger.error(message, throwable);
}

public void log(String message) {
log4jLogger.info(message);
}

//--

public Container getContainer() {
return (container);
}

public void setContainer(Container container) {
Container oldContainer = this.container;
this.container = container;
support.firePropertyChange(container, oldContainer, this.container);
}


public String getInfo() {
return (info);
}

public int getVerbosity() {
return (this.verbosity);
}

public void setVerbosity(int verbosity) {
this.verbosity = verbosity;
}

public void addPropertyChangeListener(PropertyChangeListener listener) {
   

cvs commit: jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/tcp SimpleTcpCluster.java

2004-05-28 Thread fhanik
fhanik  2004/05/28 19:36:12

  Modified:modules/cluster/src/share/org/apache/catalina/cluster
CatalinaCluster.java SessionMessage.java
   modules/cluster/src/share/org/apache/catalina/cluster/tcp
SimpleTcpCluster.java
  Added:   modules/cluster/src/share/org/apache/catalina/cluster
ClusterMessage.java MessageListener.java
  Log:
  Refactored a little bit more.
  Extending the catalina cluster to handle more than session messages.
  The next step is to implement farm deployment, hence I am expanding the
  cluster to use a message callback model instead of invoking the objects
  directly. this allows you to plug in as many callback objects as possible.
  The first call back object will be the cluster farm object. Coming soon... :)
  
  Revision  ChangesPath
  1.5   +7 -3  
jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/CatalinaCluster.java
  
  Index: CatalinaCluster.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/CatalinaCluster.java,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- CatalinaCluster.java  27 Feb 2004 14:58:55 -  1.4
  +++ CatalinaCluster.java  29 May 2004 02:36:12 -  1.5
  @@ -63,14 +63,14 @@
* Sends a message to all the members in the cluster
* @param msg SessionMessage
*/
  -public void send(SessionMessage msg);
  +public void send(ClusterMessage msg);
   
   /**
* Sends a message to a specific member in the cluster
* @param msg SessionMessage
* @param dest Member
*/
  -public void send(SessionMessage msg, Member dest);
  +public void send(ClusterMessage msg, Member dest);
   
   /**
* returns all the members currently participating in the cluster
  @@ -91,5 +91,9 @@
   public MembershipService getMembershipService();
   
   public void addValve(Valve valve);
  +
  +public void addClusterListener(MessageListener listener);
  +
  +public void removeClusterListener(MessageListener listener);
   
   }
  
  
  
  1.10  +2 -31 
jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/SessionMessage.java
  
  Index: SessionMessage.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/SessionMessage.java,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- SessionMessage.java   5 May 2004 16:42:22 -   1.9
  +++ SessionMessage.java   29 May 2004 02:36:12 -  1.10
  @@ -38,7 +38,7 @@
*/
import java.security.Principal;
import org.apache.catalina.cluster.Member;
  -public interface SessionMessage extends java.io.Serializable
  +public interface SessionMessage extends ClusterMessage, java.io.Serializable
   {
   
   /**
  @@ -73,18 +73,7 @@
*/
   public static final int EVT_ALL_SESSION_DATA = 12;
   
  -/**
  - * Get the address that this message originated from.  This would be set
  - * if the message was being relayed from a host other than the one
  - * that originally sent it.
  - */
  -public Member getAddress();
  -/**
  - * Called by the cluster before sending it to the other
  - * nodes
  - * @param member Member
  - */
  -public void setAddress(Member member);
  +
   
   public String getContextName();
   
  @@ -104,24 +93,6 @@
*/
   public String getSessionID();
   
  -/**
  - * Timestamp message 
  - * @return long
  - */
  -public long getTimestamp();
  -/**
  - * Called by the cluster before sending out 
  - * the message
  - * @param timestamp long
  - */
  -public void setTimestamp(long timestamp);
  -
  -/**
  - * Each message must have a unique ID, in case of using async replication,
  - * and a smart queue, this id is used to replace messages not yet sent 
  - * @return String
  - */
  -public String getUniqueId();
   
   
   }//SessionMessage
  
  
  
  1.1  
jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/ClusterMessage.java
  
  Index: ClusterMessage.java
  ===
  /*
   * Copyright 1999,2004 The Apache Software Foundation.
   *
   * Licensed under the Apache License, Version 2.0 (the License);
   * you may not use this file except in compliance with the License.
   * You may obtain a copy of the License at
   *
   *  http://www.apache.org/licenses/LICENSE-2.0
   *
   * Unless required by applicable law or agreed to in writing, software
   * distributed 

respuestas sobre el Chat

2004-05-28 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




cvs commit: jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session DeltaManager.java SessionMessageImpl.java SimpleTcpReplicationManager.java

2004-05-28 Thread fhanik
fhanik  2004/05/28 19:43:58

  Modified:modules/cluster/src/share/org/apache/catalina/cluster/session
DeltaManager.java SessionMessageImpl.java
SimpleTcpReplicationManager.java
  Log:
  Make sure we enforce the use of unique message Ids, even though they dont have to be
  we should use the right field
  
  Revision  ChangesPath
  1.26  +9 -5  
jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session/DeltaManager.java
  
  Index: DeltaManager.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session/DeltaManager.java,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- DeltaManager.java 26 May 2004 16:37:41 -  1.25
  +++ DeltaManager.java 29 May 2004 02:43:58 -  1.26
  @@ -343,7 +343,8 @@
 getName(),
 SessionMessage.EVT_SESSION_CREATED,
 null,
  -  sessionId);
  +  sessionId,
  +  sessionId+System.currentTimeMillis());
 cluster.send(msg);
 session.resetDeltaRequest();
 }
  @@ -634,7 +635,8 @@
   new SessionMessageImpl(this.getName(),
  SessionMessage.EVT_GET_ALL_SESSIONS,
  null,
  -   GET-ALL);
  +   GET-ALL,
  +   GET-ALL-+getName());
   //just to make sure the other server has the context started
   //long timetowait = 2-mbr.getMemberAliveTime();
   //if ( timetowait  0 ) {
  @@ -796,6 +798,7 @@
  msg = new SessionMessageImpl(getName(),
SessionMessage.EVT_SESSION_ACCESSED,
null,
  + sessionId,
sessionId+System.currentTimeMillis());
  }
  
  @@ -816,7 +819,8 @@
  SessionMessage msg = new SessionMessageImpl(getName(), 
  
SessionMessage.EVT_SESSION_EXPIRED,
  null,
  -   id);
  +   id,
  +   id+-EXPIRED-MSG);
  cluster.send(msg);
  }
  
  @@ -850,7 +854,7 @@
  log.debug(Manager (+name+) unloading sessions complete);
  SessionMessage newmsg = new SessionMessageImpl(name,
  SessionMessage.EVT_ALL_SESSION_DATA,
  -   data, );
  +   data, SESSION-STATE,SESSION-STATE-+getName());
  cluster.send(newmsg, sender);
  break;
  }
  
  
  
  1.2   +1 -1  
jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session/SessionMessageImpl.java
  
  Index: SessionMessageImpl.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session/SessionMessageImpl.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- SessionMessageImpl.java   5 May 2004 16:36:13 -   1.1
  +++ SessionMessageImpl.java   29 May 2004 02:43:58 -  1.2
  @@ -58,7 +58,7 @@
* @param attrValue - the value of the attribute added
   
*/
  -public SessionMessageImpl( String contextName,
  +private SessionMessageImpl( String contextName,
  int eventtype,
  byte[] session,
  String sessionID)
  
  
  
  1.26  +6 -2  
jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session/SimpleTcpReplicationManager.java
  
  Index: SimpleTcpReplicationManager.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session/SimpleTcpReplicationManager.java,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- SimpleTcpReplicationManager.java  28 May 2004 18:49:37 -  1.25
  +++ SimpleTcpReplicationManager.java  29 May 2004 02:43:58 -  1.26
  @@ -275,6 +275,7 @@
   SessionMessage msg = new SessionMessageImpl(name,
   SessionMessage.EVT_SESSION_EXPIRED,
   null,
  +

cvs commit: jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session SimpleTcpReplicationManager.java

2004-05-28 Thread fhanik
fhanik  2004/05/28 19:48:16

  Modified:modules/cluster/src/share/org/apache/catalina/cluster/session
SimpleTcpReplicationManager.java
  Log:
  removed not needed comments
  
  Revision  ChangesPath
  1.27  +1 -16 
jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session/SimpleTcpReplicationManager.java
  
  Index: SimpleTcpReplicationManager.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session/SimpleTcpReplicationManager.java,v
  retrieving revision 1.26
  retrieving revision 1.27
  diff -u -r1.26 -r1.27
  --- SimpleTcpReplicationManager.java  29 May 2004 02:43:58 -  1.26
  +++ SimpleTcpReplicationManager.java  29 May 2004 02:48:16 -  1.27
  @@ -200,23 +200,8 @@
   if (jvmRoute != null) {
   sessionId += '.' + jvmRoute;
   }
  -/*
  -synchronized (sessions) {
  -while (sessions.get(sessionId) != null)// Guarantee uniqueness
  -sessionId = generateSessionId();
  -}
  -*/
   if ( setId ) session.setId(sessionId);
  -
  -if ( notify  (cluster!=null) )
  -{
  -//notify javagroups
  -
  -//SessionMessage msg = new SessionMessage(this.name,
  -//
SessionMessage.EVT_SESSION_CREATED,
  -//writeSession(session),
  -//session.getId());
  -//cluster.send(msg);
  +if ( notify  (cluster!=null) ) {
   ((ReplicatedSession)session).setIsDirty(true);
   }
   return (session);
  
  
  

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