Re: Any synchronization issues with SMP?
TC clustering uses GZIP(In|Out)putStream in replication. I don't know, if there is buffering on top. Filip? Rainer Martin Schulz wrote: OT: The following is advice to servlet developers rather than container developers. For what it's worth, just be careful when you use GZIP(In|Out)putStream, since the native code uses a mutex (for no good reason, imho), to prevent garbage collection from interfering with the array being used. Bottleneck where I didn't expect one. In particular, never place a Object(In|Out)putStream directly on top of the GZIP streams, always use a buffer stream between the two. Reason is that the object stream reads/writes in very small chunks, causing four system calls per chunk. Or else interesting things are going to happen on larger SMP systems. Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.next] Progress
Jeanfrancois Arcand wrote: Remy Maucherat wrote: Remy Maucherat wrote: My upcoming change list: - Attempt to redo a bit the deployer: * remove the CL code which is there to avoid JAR locking (or at least allow disabling this feature for non-Windows OSes); when enabling anti locking code, move everything to a temp deploy folder where everything will be referenced from; controlled by a development flag on the Context to allow disabling this on Windows Speaking of which, does anyone know any OSes (besides Windows) which lock files ? NFS sometimes lock file (I did see a similar problem with Solaris) Thanks for the tip. I'll code in Windows by default, and add a flag to enable/disable then, since I don't think there's a way to determine if something is coming from NFS. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Any synchronization issues with SMP?
Clustering is using GZIP byte only with byte array, so it doesnt link to an actual stream, only a byte array stream. Don't think we have a problem Houston! :) Filip - Original Message - From: Rainer Jung [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Friday, July 02, 2004 3:59 AM Subject: Re: Any synchronization issues with SMP? TC clustering uses GZIP(In|Out)putStream in replication. I don't know, if there is buffering on top. Filip? Rainer Martin Schulz wrote: OT: The following is advice to servlet developers rather than container developers. For what it's worth, just be careful when you use GZIP(In|Out)putStream, since the native code uses a mutex (for no good reason, imho), to prevent garbage collection from interfering with the array being used. Bottleneck where I didn't expect one. In particular, never place a Object(In|Out)putStream directly on top of the GZIP streams, always use a buffer stream between the two. Reason is that the object stream reads/writes in very small chunks, causing four system calls per chunk. Or else interesting things are going to happen on larger SMP systems. Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Connector LifecycleListener not send Events
Hey,
I have find the following code at org.apache.catalina.connector.Connector:
/**
* Get the lifecycle listeners associated with this lifecycle. If this
* Lifecycle has no listeners registered, a zero-length array is
returned.
*/
public LifecycleListener[] findLifecycleListeners() {
return null ; // lifecycle.findLifecycleListeners();
}
Why we not emitt Events to the Listeners?
I think we can also send PAUSE and RESUME Events to the
lifecycleListener from Connector.
Alternativ: We delete the dead Lifecycle implementations and redesign
the code to JMX-notifcation...
Regards
Peter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
interesting article
http://www.webperformanceinc.com/library/ServletReport/ I'd like to thank all the developers for working so hard to improve tomcat. peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29887] New: - Recursive Tag files modification check causes StackOverflowError
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=29887. 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=29887 Recursive Tag files modification check causes StackOverflowError Summary: Recursive Tag files modification check causes StackOverflowError Product: Tomcat 5 Version: 5.0.25 Platform: All OS/Version: All Status: NEW Severity: Minor Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Recursive Tag files modification check causes StackOverflowError presumably because a tag file making use of itself is added to the list of its dependents, causing the modification check to loop infinitely. See attached test case. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29887] - Recursive Tag files modification check causes StackOverflowError
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=29887. 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=29887 Recursive Tag files modification check causes StackOverflowError --- Additional Comments From [EMAIL PROTECTED] 2004-07-02 15:00 --- Created an attachment (id=12014) test app with instructions to reproduce the bug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.next] Progress
Remy Maucherat wrote, On 7/2/2004 2:13 AM: Jeanfrancois Arcand wrote: Remy Maucherat wrote: Speaking of which, does anyone know any OSes (besides Windows) which lock files ? NFS sometimes lock file (I did see a similar problem with Solaris) Thanks for the tip. I'll code in Windows by default, and add a flag to enable/disable then, since I don't think there's a way to determine if something is coming from NFS. Although you can lock files over NFS on Unix systems, it should behave no differently than if you were to lock the file on any other filesystem. In other words, unless you explicitly lock the file and check that the file is locked (as locks are only advisory on Unix, they don't stop you from performing any operations if you really want to) you should not have any of the same file locking issues on Unix that you do on Windows. See the the flock and fcntl man pages for more information on Unix file locking. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29866] - JspReader#skipUntil may try to read beyond the end of the file
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=29866. 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=29866 JspReader#skipUntil may try to read beyond the end of the file --- Additional Comments From [EMAIL PROTECTED] 2004-07-02 15:37 --- Now that bugzilla notifications work again, I'll add a random comment to raise awareness ;-) The most simple JSP to demonstrate the bug consists of a single character, two characters : will work as well. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27806] - JspC creates blank files on failure
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=27806. 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=27806 JspC creates blank files on failure --- Additional Comments From [EMAIL PROTECTED] 2004-07-02 16:04 --- I had a similar issue in that I was missing my taglib entries in the web.xml, and a 0 byte file was generated. At least a more graceful message would help. I received this exception, which took me forever to figure out what was wrong: [jasperc] 2004-07-02 11:50:50 - ERROR-the file '\jsp\waa\web\analyzer\WAAClient.jsp' generated the following general exception: java.lang.NullPointerException [jasperc] error:org.apache.jasper.JasperException: Error compiling \jsp\waa\web\analyzer\WAAClient.jsp [jasperc] at org.apache.jasper.JspC.processFile(JspC.java:596) [jasperc] at org.apache.jasper.JspC.execute(JspC.java:801) [jasperc] at org.apache.jasper.JspC.main(JspC.java:823) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/naming/resources FileDirContext.java LocalStrings.properties
funkman 2004/07/02 09:25:31
Modified:catalina/src/share/org/apache/naming/resources
FileDirContext.java LocalStrings.properties
Log:
If the dir listing errors, return an empty array instead of ending up with
a NPE.
Occured when a non-readable dir appeared inside the classes dir and
TldLocationsCache was trying to init. An error was thrown and it said null.
Now it keeps going and logs a warning message stating a directory
could not be listed.
Revision ChangesPath
1.5 +278 -268
jakarta-tomcat-catalina/catalina/src/share/org/apache/naming/resources/FileDirContext.java
Index: FileDirContext.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/naming/resources/FileDirContext.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- FileDirContext.java 27 Feb 2004 14:58:54 - 1.4
+++ FileDirContext.java 2 Jul 2004 16:25:31 - 1.5
@@ -1,18 +1,18 @@
/*
* 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 under the License is distributed on an AS IS BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
- */
+ */
package org.apache.naming.resources;
@@ -49,6 +49,8 @@
public class FileDirContext extends BaseDirContext {
+private static org.apache.commons.logging.Log log=
+org.apache.commons.logging.LogFactory.getLog( FileDirContext.class );
// -- Constants
@@ -110,9 +112,9 @@
/**
* Set the document root.
- *
+ *
* @param docBase The new document root
- *
+ *
* @exception IllegalArgumentException if the specified value is not
* supported by this implementation
* @exception IllegalArgumentException if this would create a
@@ -120,23 +122,23 @@
*/
public void setDocBase(String docBase) {
- // Validate the format of the proposed document root
- if (docBase == null)
- throw new IllegalArgumentException
- (sm.getString(resources.null));
+// Validate the format of the proposed document root
+if (docBase == null)
+throw new IllegalArgumentException
+(sm.getString(resources.null));
- // Calculate a File object referencing this document base directory
- base = new File(docBase);
+// Calculate a File object referencing this document base directory
+base = new File(docBase);
try {
base = base.getCanonicalFile();
} catch (IOException e) {
// Ignore
}
- // Validate that the document base is an existing directory
- if (!base.exists() || !base.isDirectory() || !base.canRead())
- throw new IllegalArgumentException
- (sm.getString(fileResources.base, docBase));
+// Validate that the document base is an existing directory
+if (!base.exists() || !base.isDirectory() || !base.canRead())
+throw new IllegalArgumentException
+(sm.getString(fileResources.base, docBase));
this.absoluteBase = base.getAbsolutePath();
super.setDocBase(docBase);
@@ -197,7 +199,7 @@
/**
* Retrieves the named object.
- *
+ *
* @param name the name of the object to look up
* @return the object bound to name
* @exception NamingException if a naming exception is encountered
@@ -206,11 +208,11 @@
throws NamingException {
Object result = null;
File file = file(name);
-
+
if (file == null)
throw new NamingException
(sm.getString(resources.notFound, name));
-
+
if (file.isDirectory()) {
FileDirContext tempContext = new FileDirContext(env);
tempContext.setDocBase(file.getPath());
@@ -218,23 +220,23 @@
} else {
result = new FileResource(file);
}
-
+
return result;
-
+
}
/**
- * Unbinds the named object. Removes the terminal atomic name in name
- * from the target context--that named by all but the terminal atomic
+ * Unbinds the named object.
DO NOT REPLY [Bug 29890] New: - tomcat failed to serve static files having non-lating characters in their path
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=29890. 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=29890 tomcat failed to serve static files having non-lating characters in their path Summary: tomcat failed to serve static files having non-lating characters in their path Product: Tomcat 4 Version: 4.0.6 Final Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hi Developers, I use default configuration of the latest Apache Tomcat/4.1.30 running with Windows 2000 Server SP4 Russian edition. Default configuration allows to server static content like HTML pages and images via DefaultServlet of catalina class. It happened, that no resources with non-latin symbols in their path can be accessed. Server reply is: 404 - resource is not available. Specifically, if name of the file or directory contains any Cyrillic symbols (or non-lating in general, as I see in other postings), tomcat can’t find it any more. I checked the correctness of encoding by browser (IE and Opera) and found out, that they both give out perfect %-encoding of UTF-8 string. My suggestion is that there is some issue in URI decoder in DefaultServlet. Here extract from my default web.xml: web.xml: servlet servlet-namedefault/servlet-name servlet-class org.apache.catalina.servlets.DefaultServlet /servlet-class init-param param-namedebug/param-name param-value0/param-value /init-param init-param param-namelistings/param-name param-valuetrue/param-value /init-param load-on-startup1/load-on-startup /servlet I'll be happy to know, that it is not a bug, but my configuration mistake, if anybody gives me a clue. Sincerely, Anton Golubev ENGECON - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen
Hei ja kiitos yhteydenotostasi, Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen. Palautteen pääsette antamaan osoitteesta: https://self-service.canon-europe.com/fi/pages/ Voit vaihtaa kohdasta select language käyttökieleksi suomen. Uudessa palvelussa on mahdollisuus hakea ratkaisua yleisimpiin teknisiin kysymyksiin, sekä lähetettyjen kyselyiden seuranta. Palvelu edellyttää rekisteröintiä ja se on maksuton. Yllämainitun lisäksi puhelinpalvelumme vastaa numerossa 020 366 466 (ma-pe klo 9.00 - 17.30). Puhelun hinta on 0,0821 /puhelu + 0,0147 /min. Emme valitettavasti enää vastaa vanhaan tukipalveluosoitteeseen lähetettyihin viesteihin. Terveisin Canon Consumer Imaging -tuki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen
Hei ja kiitos yhteydenotostasi, Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen. Palautteen pääsette antamaan osoitteesta: https://self-service.canon-europe.com/fi/pages/ Voit vaihtaa kohdasta select language käyttökieleksi suomen. Uudessa palvelussa on mahdollisuus hakea ratkaisua yleisimpiin teknisiin kysymyksiin, sekä lähetettyjen kyselyiden seuranta. Palvelu edellyttää rekisteröintiä ja se on maksuton. Yllämainitun lisäksi puhelinpalvelumme vastaa numerossa 020 366 466 (ma-pe klo 9.00 - 17.30). Puhelun hinta on 0,0821 /puhelu + 0,0147 /min. Emme valitettavasti enää vastaa vanhaan tukipalveluosoitteeseen lähetettyihin viesteihin. Terveisin Canon Consumer Imaging -tuki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen
Hei ja kiitos yhteydenotostasi, Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen. Palautteen pääsette antamaan osoitteesta: https://self-service.canon-europe.com/fi/pages/ Voit vaihtaa kohdasta select language käyttökieleksi suomen. Uudessa palvelussa on mahdollisuus hakea ratkaisua yleisimpiin teknisiin kysymyksiin, sekä lähetettyjen kyselyiden seuranta. Palvelu edellyttää rekisteröintiä ja se on maksuton. Yllämainitun lisäksi puhelinpalvelumme vastaa numerossa 020 366 466 (ma-pe klo 9.00 - 17.30). Puhelun hinta on 0,0821 /puhelu + 0,0147 /min. Emme valitettavasti enää vastaa vanhaan tukipalveluosoitteeseen lähetettyihin viesteihin. Terveisin Canon Consumer Imaging -tuki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen
Hei ja kiitos yhteydenotostasi, Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen. Palautteen pääsette antamaan osoitteesta: https://self-service.canon-europe.com/fi/pages/ Voit vaihtaa kohdasta select language käyttökieleksi suomen. Uudessa palvelussa on mahdollisuus hakea ratkaisua yleisimpiin teknisiin kysymyksiin, sekä lähetettyjen kyselyiden seuranta. Palvelu edellyttää rekisteröintiä ja se on maksuton. Yllämainitun lisäksi puhelinpalvelumme vastaa numerossa 020 366 466 (ma-pe klo 9.00 - 17.30). Puhelun hinta on 0,0821 /puhelu + 0,0147 /min. Emme valitettavasti enää vastaa vanhaan tukipalveluosoitteeseen lähetettyihin viesteihin. Terveisin Canon Consumer Imaging -tuki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen
Hei ja kiitos yhteydenotostasi, Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen. Palautteen pääsette antamaan osoitteesta: https://self-service.canon-europe.com/fi/pages/ Voit vaihtaa kohdasta select language käyttökieleksi suomen. Uudessa palvelussa on mahdollisuus hakea ratkaisua yleisimpiin teknisiin kysymyksiin, sekä lähetettyjen kyselyiden seuranta. Palvelu edellyttää rekisteröintiä ja se on maksuton. Yllämainitun lisäksi puhelinpalvelumme vastaa numerossa 020 366 466 (ma-pe klo 9.00 - 17.30). Puhelun hinta on 0,0821 /puhelu + 0,0147 /min. Emme valitettavasti enää vastaa vanhaan tukipalveluosoitteeseen lähetettyihin viesteihin. Terveisin Canon Consumer Imaging -tuki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen
Hei ja kiitos yhteydenotostasi, Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen. Palautteen pääsette antamaan osoitteesta: https://self-service.canon-europe.com/fi/pages/ Voit vaihtaa kohdasta select language käyttökieleksi suomen. Uudessa palvelussa on mahdollisuus hakea ratkaisua yleisimpiin teknisiin kysymyksiin, sekä lähetettyjen kyselyiden seuranta. Palvelu edellyttää rekisteröintiä ja se on maksuton. Yllämainitun lisäksi puhelinpalvelumme vastaa numerossa 020 366 466 (ma-pe klo 9.00 - 17.30). Puhelun hinta on 0,0821 /puhelu + 0,0147 /min. Emme valitettavasti enää vastaa vanhaan tukipalveluosoitteeseen lähetettyihin viesteihin. Terveisin Canon Consumer Imaging -tuki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen
Hei ja kiitos yhteydenotostasi, Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen. Palautteen pääsette antamaan osoitteesta: https://self-service.canon-europe.com/fi/pages/ Voit vaihtaa kohdasta select language käyttökieleksi suomen. Uudessa palvelussa on mahdollisuus hakea ratkaisua yleisimpiin teknisiin kysymyksiin, sekä lähetettyjen kyselyiden seuranta. Palvelu edellyttää rekisteröintiä ja se on maksuton. Yllämainitun lisäksi puhelinpalvelumme vastaa numerossa 020 366 466 (ma-pe klo 9.00 - 17.30). Puhelun hinta on 0,0821 /puhelu + 0,0147 /min. Emme valitettavasti enää vastaa vanhaan tukipalveluosoitteeseen lähetettyihin viesteihin. Terveisin Canon Consumer Imaging -tuki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen
Hei ja kiitos yhteydenotostasi, Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen. Palautteen pääsette antamaan osoitteesta: https://self-service.canon-europe.com/fi/pages/ Voit vaihtaa kohdasta select language käyttökieleksi suomen. Uudessa palvelussa on mahdollisuus hakea ratkaisua yleisimpiin teknisiin kysymyksiin, sekä lähetettyjen kyselyiden seuranta. Palvelu edellyttää rekisteröintiä ja se on maksuton. Yllämainitun lisäksi puhelinpalvelumme vastaa numerossa 020 366 466 (ma-pe klo 9.00 - 17.30). Puhelun hinta on 0,0821 /puhelu + 0,0147 /min. Emme valitettavasti enää vastaa vanhaan tukipalveluosoitteeseen lähetettyihin viesteihin. Terveisin Canon Consumer Imaging -tuki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen
Hei ja kiitos yhteydenotostasi, Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen. Palautteen pääsette antamaan osoitteesta: https://self-service.canon-europe.com/fi/pages/ Voit vaihtaa kohdasta select language käyttökieleksi suomen. Uudessa palvelussa on mahdollisuus hakea ratkaisua yleisimpiin teknisiin kysymyksiin, sekä lähetettyjen kyselyiden seuranta. Palvelu edellyttää rekisteröintiä ja se on maksuton. Yllämainitun lisäksi puhelinpalvelumme vastaa numerossa 020 366 466 (ma-pe klo 9.00 - 17.30). Puhelun hinta on 0,0821 /puhelu + 0,0147 /min. Emme valitettavasti enää vastaa vanhaan tukipalveluosoitteeseen lähetettyihin viesteihin. Terveisin Canon Consumer Imaging -tuki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen
Hei ja kiitos yhteydenotostasi, Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen. Palautteen pääsette antamaan osoitteesta: https://self-service.canon-europe.com/fi/pages/ Voit vaihtaa kohdasta select language käyttökieleksi suomen. Uudessa palvelussa on mahdollisuus hakea ratkaisua yleisimpiin teknisiin kysymyksiin, sekä lähetettyjen kyselyiden seuranta. Palvelu edellyttää rekisteröintiä ja se on maksuton. Yllämainitun lisäksi puhelinpalvelumme vastaa numerossa 020 366 466 (ma-pe klo 9.00 - 17.30). Puhelun hinta on 0,0821 /puhelu + 0,0147 /min. Emme valitettavasti enää vastaa vanhaan tukipalveluosoitteeseen lähetettyihin viesteihin. Terveisin Canon Consumer Imaging -tuki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen
Hei ja kiitos yhteydenotostasi, Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen. Palautteen pääsette antamaan osoitteesta: https://self-service.canon-europe.com/fi/pages/ Voit vaihtaa kohdasta select language käyttökieleksi suomen. Uudessa palvelussa on mahdollisuus hakea ratkaisua yleisimpiin teknisiin kysymyksiin, sekä lähetettyjen kyselyiden seuranta. Palvelu edellyttää rekisteröintiä ja se on maksuton. Yllämainitun lisäksi puhelinpalvelumme vastaa numerossa 020 366 466 (ma-pe klo 9.00 - 17.30). Puhelun hinta on 0,0821 /puhelu + 0,0147 /min. Emme valitettavasti enää vastaa vanhaan tukipalveluosoitteeseen lähetettyihin viesteihin. Terveisin Canon Consumer Imaging -tuki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen
Hei ja kiitos yhteydenotostasi, Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen. Palautteen pääsette antamaan osoitteesta: https://self-service.canon-europe.com/fi/pages/ Voit vaihtaa kohdasta select language käyttökieleksi suomen. Uudessa palvelussa on mahdollisuus hakea ratkaisua yleisimpiin teknisiin kysymyksiin, sekä lähetettyjen kyselyiden seuranta. Palvelu edellyttää rekisteröintiä ja se on maksuton. Yllämainitun lisäksi puhelinpalvelumme vastaa numerossa 020 366 466 (ma-pe klo 9.00 - 17.30). Puhelun hinta on 0,0821 /puhelu + 0,0147 /min. Emme valitettavasti enää vastaa vanhaan tukipalveluosoitteeseen lähetettyihin viesteihin. Terveisin Canon Consumer Imaging -tuki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen
Hei ja kiitos yhteydenotostasi, Olemme siirtäneet Canon Helpdesk www-tukipalvelun toiseen osoitteeseen. Palautteen pääsette antamaan osoitteesta: https://self-service.canon-europe.com/fi/pages/ Voit vaihtaa kohdasta select language käyttökieleksi suomen. Uudessa palvelussa on mahdollisuus hakea ratkaisua yleisimpiin teknisiin kysymyksiin, sekä lähetettyjen kyselyiden seuranta. Palvelu edellyttää rekisteröintiä ja se on maksuton. Yllämainitun lisäksi puhelinpalvelumme vastaa numerossa 020 366 466 (ma-pe klo 9.00 - 17.30). Puhelun hinta on 0,0821 /puhelu + 0,0147 /min. Emme valitettavasti enää vastaa vanhaan tukipalveluosoitteeseen lähetettyihin viesteihin. Terveisin Canon Consumer Imaging -tuki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/startup CatalinaService.java
markt 2004/07/02 15:11:49
Modified:catalina/src/share/org/apache/catalina/startup
CatalinaService.java
Log:
Fix bug 26021. When running as a service, swallowOuput had no effect
Remove unused imports - Eclipse
Revision ChangesPath
1.11 +10 -14
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/startup/CatalinaService.java
Index: CatalinaService.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/startup/CatalinaService.java,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- CatalinaService.java 24 Oct 2002 02:42:03 - 1.10
+++ CatalinaService.java 2 Jul 2004 22:11:49 - 1.11
@@ -66,20 +66,11 @@
import java.io.File;
-import java.io.IOException;
-import java.io.OutputStream;
-import java.lang.reflect.InvocationTargetException;
-import java.lang.reflect.Constructor;
-import java.net.Socket;
import java.security.Security;
-import java.util.Stack;
-import org.apache.catalina.Container;
import org.apache.catalina.Lifecycle;
import org.apache.catalina.LifecycleException;
-import org.apache.catalina.LifecycleListener;
-import org.apache.catalina.Server;
-import org.apache.catalina.Loader;
import org.apache.commons.digester.Digester;
+import org.apache.tomcat.util.log.SystemLogHandler;
/**
@@ -266,6 +257,11 @@
* Start a new server instance.
*/
public void start() {
+
+// Replace System.out and System.err with a custom PrintStream
+SystemLogHandler log = new SystemLogHandler(System.out);
+System.setOut(log);
+System.setErr(log);
// Start the new server
if (server instanceof Lifecycle) {
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 26021] - swallowoutput not working
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=26021. 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=26021 swallowoutput not working [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-07-02 22:15 --- This has been fixed in CVS. The root cause was that CatalinaService wasn't capturing System.out on startup. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29895] New: - context.xml isn't read properly by Manager application.
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=29895. 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=29895 context.xml isn't read properly by Manager application. Summary: context.xml isn't read properly by Manager application. Product: Tomcat 5 Version: 5.0.25 Platform: PC OS/Version: Windows XP Status: NEW Severity: Blocker Priority: Other Component: Webapps:Administration AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I was trying to deploy an application using Manager from local file system, onto local server. Manager has two options: load by specifing XML file, or by specifing web directory or war. You can see my configuration below, but basically, deploying by specifying the folder does not read META-INF/context.xml properly. It read the context path=/ablogic value, but it doesn't read the Resource stuff. So, if I deploy by specifying XML file (and specifying context docBas=), everything works fine. However, if I use a folder, I get the following: Error message: Cannot create JDBC driver of class '' for connect URL 'null' org.apache.commons.dbcp.BasicDataSource.createDataSource (BasicDataSource.java:750) org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:518) org.ablogic.db.Manager.getConnection(Manager.java:41) org.ablogic.db.Manager.testQuery(Manager.java:85) org.apache.jsp.init._2_jsp._jspService(_2_jsp.java:78) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:298) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:237) org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:157) com.jspbook.GZIPFilter.doFilter(GZIPFilter.java:37) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:186) org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:157) org.ablogic.web.CacheFilter.doFilter(CacheFilter.java:130) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:186) org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:157) org.ablogic.web.IPBlockFilter.doFilter(IPBlockFilter.java:135) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:186) org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:157) org.ablogic.web.TraceFilter.doFilter(TraceFilter.java:69) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:186) org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:157) org.apache.catalina.core.StandardWrapperValve.invoke (StandardWrapperValve.java:214) org.apache.catalina.core.StandardValveContext.invokeNext (StandardValveContext.java:104) org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) org.apache.catalina.core.StandardContextValve.invokeInternal (StandardContextValve.java:198) org.apache.catalina.core.StandardContextValve.invoke (StandardContextValve.java:152) org.apache.catalina.core.StandardValveContext.invokeNext (StandardValveContext.java:104) org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) org.apache.catalina.core.StandardValveContext.invokeNext (StandardValveContext.java:104) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) org.apache.catalina.core.StandardValveContext.invokeNext (StandardValveContext.java:102) org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:109) org.apache.catalina.core.StandardValveContext.invokeNext (StandardValveContext.java:104) org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:793) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnecti on(Http11Protocol.java:702) org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:571)
[GUMP@brutus]: jakarta-tomcat-5/jakarta-tomcat-5 failed
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 16 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: -DEBUG- Jar [naming-resources.jar] identifier set to jar basename: [naming-resources] -DEBUG- Jar [servlets-default.jar] identifier set to jar basename: [servlets-default] -DEBUG- Jar [naming-common.jar] identifier set to jar basename: [naming-common] -DEBUG- Jar [catalina.jar] identifier set to jar basename: [catalina] -DEBUG- Jar [bootstrap.jar] identifier set to jar basename: [bootstrap] -DEBUG- Jar [servlets-common.jar] identifier set to jar basename: [servlets-common] -DEBUG- 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 xml-apis.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 debug output, due to a sequence of 15 previous errors. -INFO- Failed with reason build failed 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, 28 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 -debug -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-20040702.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-20040702.jar -Dxml-apis.jar=/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar -DxercesImpl.jar=/usr/local/gump/public/workspace/xml-xerces2/java/build
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm LocalStrings.properties LocalStrings_es.properties LocalStrings_fr.properties LocalStrings_ja.properties RealmBase.java UserDatabaseRealm.java
billbarker2004/07/02 21:16:41
Modified:catalina/src/share/org/apache/catalina/realm
LocalStrings.properties LocalStrings_es.properties
LocalStrings_fr.properties
LocalStrings_ja.properties RealmBase.java
UserDatabaseRealm.java
Log:
Fixing UDBRealm to work with Digest and Client-Cert.
Also fixing authenticate(String, String) in RealmBase to handle digested passwords
correctly.
Revision ChangesPath
1.6 +3 -3
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm/LocalStrings.properties
Index: LocalStrings.properties
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm/LocalStrings.properties,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- LocalStrings.properties 12 Dec 2003 22:37:58 - 1.5
+++ LocalStrings.properties 3 Jul 2004 04:16:41 - 1.6
@@ -33,9 +33,9 @@
realmBase.hasRoleSuccess=Username {0} has role {1}
realmBase.notAuthenticated=Configuration error: Cannot perform access control
without an authenticated principal
realmBase.notStarted=This Realm has not yet been started
+realmBase.authenticateFailure=Username {0} NOT successfully authenticated
+realmBase.authenticateSuccess=Username {0} successfully authenticated
userDatabaseRealm.authenticateError=Login configuration error authenticating
username {0}
-userDatabaseRealm.authenticateFailure=Username {0} NOT successfully authenticated
-userDatabaseRealm.authenticateSuccess=Username {0} successfully authenticated
userDatabaseRealm.lookup=Exception looking up UserDatabase under key {0}
userDatabaseRealm.noDatabase=No UserDatabase component found under key {0}
userDatabaseRealm.noEngine=No Engine component found in container hierarchy
1.6 +3 -3
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm/LocalStrings_es.properties
Index: LocalStrings_es.properties
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm/LocalStrings_es.properties,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- LocalStrings_es.properties17 Jan 2004 01:43:58 - 1.5
+++ LocalStrings_es.properties3 Jul 2004 04:16:41 - 1.6
@@ -33,9 +33,9 @@
realmBase.hasRoleSuccess=El usuario {0} desempeña el papel de {1}
realmBase.notAuthenticated=Error de Configuración: No se pueden realizar funciones
de control de acceso sin un principal autentificado
realmBase.notStarted=Este dominio aún no ha sido inicializado
+realmBase.authenticateFailure=Nombre de usuario {0} NO autenticado con éxito
+realmBase.authenticateSuccess=Nombre de usuario {0} autenticado con éxito
userDatabaseRealm.authenticateError=Error de configuración de Login autenticando
nombre de usuario {0}
-userDatabaseRealm.authenticateFailure=Nombre de usuario {0} NO autenticado con éxito
-userDatabaseRealm.authenticateSuccess=Nombre de usuario {0} autenticado con éxito
userDatabaseRealm.lookup=Excepción buscando en Base de datos de Usuario mediante la
clave {0}
userDatabaseRealm.noDatabase=No se ha hallado componente de Base de datos de
Usuario mediante la clave {0}
userDatabaseRealm.noEngine=No se ha hallado componente de Motor en jerarquía de
contenedor
1.3 +3 -3
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm/LocalStrings_fr.properties
Index: LocalStrings_fr.properties
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm/LocalStrings_fr.properties,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- LocalStrings_fr.properties12 Dec 2003 22:37:58 - 1.2
+++ LocalStrings_fr.properties3 Jul 2004 04:16:41 - 1.3
@@ -32,9 +32,9 @@
realmBase.hasRoleSuccess=Le nom d''utilisateur {0} a pour rôle {1}
realmBase.notAuthenticated=Erreur de configuration: Impossible de conduire un
contrôle d''accès sans un authentifié principal (authenticated principal)
realmBase.notStarted=Ce royaume (Realm) n''a pas encore été démarré
+realmBase.authenticateFailure=Le nom d''utilisateur {0} N''A PAS été authentifié
+realmBase.authenticateSuccess=Le nom d''utilisateur {0} a été authentifié avec
succès
userDatabaseRealm.authenticateError=Erreur de configuration du contrôle d''accès
(login) lors de l''authentification du nom d''utilisateur {0}
-userDatabaseRealm.authenticateFailure=Le nom d''utilisateur {0} N''A PAS été
authentifié
-userDatabaseRealm.authenticateSuccess=Le nom d''utilisateur {0} a été authentifié
Discuss: Why stopped StandardHost send check events?
hey,
I have see that a stopped Host send all 10 sec check events to
all LifecycleListeners.
A stop HostConfig can't reload or deploy new webapp really at a stopped
host.
StandardHost code
public void backgroundProcess() {
lifecycle.fireLifecycleEvent(check, null);
}
better
StandardHost emitted check event only on started host.
public void backgroundProcess() {
if(started)
lifecycle.fireLifecycleEvent(check, null);
}
regards
Peter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
