svn commit: r1325135 - in /tomcat/tc7.0.x/trunk/java/org/apache/catalina/ha/session: BackupManager.java LocalStrings.properties
Author: kfujino
Date: Thu Apr 12 06:45:48 2012
New Revision: 1325135
URL: http://svn.apache.org/viewvc?rev=1325135&view=rev
Log:
use StringManager.
Modified:
tomcat/tc7.0.x/trunk/java/org/apache/catalina/ha/session/BackupManager.java
tomcat/tc7.0.x/trunk/java/org/apache/catalina/ha/session/LocalStrings.properties
Modified:
tomcat/tc7.0.x/trunk/java/org/apache/catalina/ha/session/BackupManager.java
URL:
http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/java/org/apache/catalina/ha/session/BackupManager.java?rev=1325135&r1=1325134&r2=1325135&view=diff
==
--- tomcat/tc7.0.x/trunk/java/org/apache/catalina/ha/session/BackupManager.java
(original)
+++ tomcat/tc7.0.x/trunk/java/org/apache/catalina/ha/session/BackupManager.java
Thu Apr 12 06:45:48 2012
@@ -33,6 +33,7 @@ import org.apache.catalina.tribes.tipis.
import org.apache.catalina.tribes.tipis.LazyReplicatedMap;
import org.apache.juli.logging.Log;
import org.apache.juli.logging.LogFactory;
+import org.apache.tomcat.util.res.StringManager;
/**
*@author Filip Hanik
@@ -43,6 +44,11 @@ public class BackupManager extends Clust
private static final Log log = LogFactory.getLog(BackupManager.class);
+/**
+ * The string manager for this package.
+ */
+protected static final StringManager sm =
StringManager.getManager(Constants.Package);
+
protected static long DEFAULT_REPL_TIMEOUT = 15000;//15 seconds
/** Set to true if we don't want the sessions to expire on shutdown */
@@ -150,7 +156,7 @@ public class BackupManager extends Clust
setCluster((CatalinaCluster)cluster);
} else {
throw new LifecycleException(
-"no cluster associated with this context: " +
getName());
+sm.getString("backupManager.noCluster",
getName()));
}
}
cluster.registerManager(this);
@@ -162,8 +168,8 @@ public class BackupManager extends Clust
map.setChannelSendOptions(mapSendOptions);
this.sessions = map;
} catch ( Exception x ) {
-log.error("Unable to start BackupManager",x);
-throw new LifecycleException("Failed to start BackupManager",x);
+log.error(sm.getString("backupManager.startUnable", getName()),x);
+throw new
LifecycleException(sm.getString("backupManager.startFailed", getName()),x);
}
setState(LifecycleState.STARTING);
}
@@ -189,7 +195,7 @@ public class BackupManager extends Clust
protected synchronized void stopInternal() throws LifecycleException {
if (log.isDebugEnabled())
-log.debug("Stopping");
+log.debug(sm.getString("backupManager.stopped", getName()));
setState(LifecycleState.STOPPING);
Modified:
tomcat/tc7.0.x/trunk/java/org/apache/catalina/ha/session/LocalStrings.properties
URL:
http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/java/org/apache/catalina/ha/session/LocalStrings.properties?rev=1325135&r1=1325134&r2=1325135&view=diff
==
---
tomcat/tc7.0.x/trunk/java/org/apache/catalina/ha/session/LocalStrings.properties
(original)
+++
tomcat/tc7.0.x/trunk/java/org/apache/catalina/ha/session/LocalStrings.properties
Thu Apr 12 06:45:48 2012
@@ -92,3 +92,7 @@ standardSession.notSerializable=Cannot s
standardSession.removeAttribute.ise=removeAttribute: Session already
invalidated
standardSession.setAttribute.namenull=setAttribute: name parameter cannot be
null
serializablePrincipal.readPrincipal.cnfe=readPrincipal: Failed to recreate
user Principal
+backupManager.noCluster=no cluster associated with this context: [{0}]
+backupManager.startUnable=Unable to start BackupManager: [{0}]
+backupManager.startFailed=Failed to start BackupManager: [{0}]
+backupManager.stopped=Manager [{0}] is stopping
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1325134 - in /tomcat/trunk/java/org/apache/catalina/ha/session: BackupManager.java LocalStrings.properties
Author: kfujino
Date: Thu Apr 12 06:42:42 2012
New Revision: 1325134
URL: http://svn.apache.org/viewvc?rev=1325134&view=rev
Log:
use StringManager.
Modified:
tomcat/trunk/java/org/apache/catalina/ha/session/BackupManager.java
tomcat/trunk/java/org/apache/catalina/ha/session/LocalStrings.properties
Modified: tomcat/trunk/java/org/apache/catalina/ha/session/BackupManager.java
URL:
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/ha/session/BackupManager.java?rev=1325134&r1=1325133&r2=1325134&view=diff
==
--- tomcat/trunk/java/org/apache/catalina/ha/session/BackupManager.java
(original)
+++ tomcat/trunk/java/org/apache/catalina/ha/session/BackupManager.java Thu Apr
12 06:42:42 2012
@@ -33,6 +33,7 @@ import org.apache.catalina.tribes.tipis.
import org.apache.catalina.tribes.tipis.LazyReplicatedMap;
import org.apache.juli.logging.Log;
import org.apache.juli.logging.LogFactory;
+import org.apache.tomcat.util.res.StringManager;
/**
*@author Filip Hanik
@@ -43,6 +44,11 @@ public class BackupManager extends Clust
private static final Log log = LogFactory.getLog(BackupManager.class);
+/**
+ * The string manager for this package.
+ */
+protected static final StringManager sm =
StringManager.getManager(Constants.Package);
+
protected static long DEFAULT_REPL_TIMEOUT = 15000;//15 seconds
/** Set to true if we don't want the sessions to expire on shutdown */
@@ -151,7 +157,7 @@ public class BackupManager extends Clust
setCluster((CatalinaCluster)cluster);
} else {
throw new LifecycleException(
-"no cluster associated with this context: " +
getName());
+sm.getString("backupManager.noCluster",
getName()));
}
}
cluster.registerManager(this);
@@ -162,8 +168,8 @@ public class BackupManager extends Clust
map.setChannelSendOptions(mapSendOptions);
this.sessions = map;
} catch ( Exception x ) {
-log.error("Unable to start BackupManager",x);
-throw new LifecycleException("Failed to start BackupManager",x);
+log.error(sm.getString("backupManager.startUnable", getName()),x);
+throw new
LifecycleException(sm.getString("backupManager.startFailed", getName()),x);
}
setState(LifecycleState.STARTING);
}
@@ -189,7 +195,7 @@ public class BackupManager extends Clust
protected synchronized void stopInternal() throws LifecycleException {
if (log.isDebugEnabled())
-log.debug("Stopping");
+log.debug(sm.getString("backupManager.stopped", getName()));
setState(LifecycleState.STOPPING);
Modified:
tomcat/trunk/java/org/apache/catalina/ha/session/LocalStrings.properties
URL:
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/ha/session/LocalStrings.properties?rev=1325134&r1=1325133&r2=1325134&view=diff
==
--- tomcat/trunk/java/org/apache/catalina/ha/session/LocalStrings.properties
(original)
+++ tomcat/trunk/java/org/apache/catalina/ha/session/LocalStrings.properties
Thu Apr 12 06:42:42 2012
@@ -81,3 +81,7 @@ standardSession.notSerializable=Cannot s
standardSession.removeAttribute.ise=removeAttribute: Session already
invalidated
standardSession.setAttribute.namenull=setAttribute: name parameter cannot be
null
serializablePrincipal.readPrincipal.cnfe=readPrincipal: Failed to recreate
user Principal
+backupManager.noCluster=no cluster associated with this context: [{0}]
+backupManager.startUnable=Unable to start BackupManager: [{0}]
+backupManager.startFailed=Failed to start BackupManager: [{0}]
+backupManager.stopped=Manager [{0}] is stopping
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk) 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 the folk at gene...@gump.apache.org. Project tomcat-trunk-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 20 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-trunk-test : Tomcat 8.x, a web server implementing Java Servlet 3.1, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on tomcat-trunk-dbcp exists, no need to add for property tomcat-dbcp-src.jar. -DEBUG- Dependency on commons-daemon exists, no need to add for property commons-daemon.native.src.tgz. -DEBUG- Dependency on commons-daemon exists, no need to add for property tomcat-native.tar.gz. -DEBUG- Dependency on tomcat-trunk-dbcp exists, no need to add for property tomcat-dbcp.home. -INFO- Failed with reason build failed -INFO- Project Reports in: /srv/gump/public/workspace/tomcat-trunk/output/build/logs The following work was performed: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/gump_work/build_tomcat-trunk_tomcat-trunk-test.html Work Name: build_tomcat-trunk_tomcat-trunk-test (Type: Build) Work ended in a state of : Failed Elapsed: 22 mins 49 secs Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Djunit.jar=/srv/gump/public/workspace/junit/dist/junit-12042012.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-12042012-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-12042012-native-src.tar.gz -Dexamples.sources.skip=true -Dtomcat-dbcp.home=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps -Djdt.jar=/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar -Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-12042012.jar -Dtomcat-dbcp-src.jar=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-src.jar -Dtest.accesslog=true -Dcommons-pool.home=/srv/gump/public/workspace/commons-pool-1.x -Dcommons-dbcp.home=/ srv/gump/public/workspace/commons-dbcp-1.x -Dtomcat-dbcp.jar=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-12042012.jar test [Working Directory: /srv/gump/public/workspace/tomcat-trunk] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-trunk/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/servlet-api.jar:/srv/gump/public/workspace/tomcat-trunk/outp ut/build/lib/jsp-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/el-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-ant.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-coyote.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper-el.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-tribes.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-ha.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-jni.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-util.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jaf-1.1ea/activation.jar:/srv/gump/packages/eclipse/plugins/org .eclipse.jdt.core_3.4.2/jdtcore.jar:/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-12042012.jar:/srv/gump/public/workspac
[GUMP@vmgump]: Project tomcat-tc7.0.x-test (in module tomcat-7.0.x) 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 the folk at gene...@gump.apache.org. Project tomcat-tc7.0.x-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 10 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-tc7.0.x-test : Tomcat 7.x, a web server implementing Java Servlet 3.0, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on tomcat-tc7.0.x-dbcp exists, no need to add for property tomcat-dbcp-src.jar. -DEBUG- Dependency on commons-daemon exists, no need to add for property commons-daemon.native.src.tgz. -DEBUG- Dependency on commons-daemon exists, no need to add for property tomcat-native.tar.gz. -DEBUG- Dependency on tomcat-tc7.0.x-dbcp exists, no need to add for property tomcat-dbcp.home. -INFO- Failed with reason build failed -INFO- Project Reports in: /srv/gump/public/workspace/tomcat-7.0.x/output/build/logs The following work was performed: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-test/gump_work/build_tomcat-7.0.x_tomcat-tc7.0.x-test.html Work Name: build_tomcat-7.0.x_tomcat-tc7.0.x-test (Type: Build) Work ended in a state of : Failed Elapsed: 22 mins 44 secs Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Djunit.jar=/srv/gump/public/workspace/junit/dist/junit-12042012.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-12042012-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-12042012-native-src.tar.gz -Dexamples.sources.skip=true -Dtomcat-dbcp.home=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps -Djdt.jar=/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar -Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-12042012.jar -Dtomcat-dbcp-src.jar=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps/tomcat-dbcp-src.jar -Dtest.accesslog=true -Dcommons-pool.home=/srv/gump/public/workspace/commons-pool-1.x -Dcommons-dbcp.home=/ srv/gump/public/workspace/commons-dbcp-1.x -Dtomcat-dbcp.jar=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps/tomcat-dbcp-12042012.jar test [Working Directory: /srv/gump/public/workspace/tomcat-7.0.x] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-7.0.x/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/servlet-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/outp ut/build/lib/jsp-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/el-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-ant.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-coyote.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/jasper.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/jasper-el.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-tribes.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-ha.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-util.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jaf-1.1ea/activation.jar:/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar:/srv/gump/public/workspace/tomcat-7. 0.x/tomcat-deps/tomcat-dbcp-12042012.jar:/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-12042012.jar
[GUMP@vmgump]: Project jakarta-tomcat-catalina (in module jakarta-tomcat-catalina) 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 the folk at gene...@gump.apache.org. Project jakarta-tomcat-catalina has an issue affecting its community integration. This issue affects 2 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - jakarta-tomcat-catalina : Servlet 2.4 Reference Implementation - jakarta-tomcat-jk : Connectors to various web servers Full details are available at: http://vmgump.apache.org/gump/public/jakarta-tomcat-catalina/jakarta-tomcat-catalina/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on ant exists, no need to add for property ant.home. -DEBUG- Dependency on jmx exists, no need to add for property jmx.home. -DEBUG- Dependency on jaf exists, no need to add for property activation.home. -DEBUG- Dependency on jakarta-tomcat-coyote exists, no need to add for property tomcat-coyote.home. -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-tomcat-catalina/jakarta-tomcat-catalina/gump_work/build_jakarta-tomcat-catalina_jakarta-tomcat-catalina.html Work Name: build_jakarta-tomcat-catalina_jakarta-tomcat-catalina (Type: Build) Work ended in a state of : Failed Elapsed: 21 secs Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only -Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar:/srv/gump/public/workspace/xml-xalan/build/serializer.jar org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dtomcat33.home=--UnSet-- -Dcatalina.build=/srv/gump/public/workspace/jakarta-tomcat-catalina/build -Djmx.home=/srv/gump/packages/jmx-1_2_1-bin -Djdbc20ext.jar=/srv/gump/packages/jdbc2_0/jdbc2_0-stdext.jar -Djtc.home=/srv/gump/public/workspace/jakarta-tomcat-connectors -Djasper.home=/srv/gump/public/workspace/jakarta-tomcat-jasper_tc5 -Dant.home=/srv/gump/public/workspace/ant/dist -Dcommons-io.jar=/srv/gump/public/workspace/apache-commons/io/target/commons-io-*[0-9T].jar -Dcompile.source=1.4 -Dcommons-collections.jar=/srv/gump/public/w orkspace/commons-collections-3.x/target/commons-collections-3.3-SNAPSHOT.jar -Dcatalina.deploy=/srv/gump/public/workspace/jakarta-tomcat-catalina/build -Djaas.jar=/srv/gump/packages/jaas1_0/lib/jaas.jar -Dcommons-fileupload.jar=/srv/gump/public/workspace/apache-commons/fileupload/target/commons-fileupload-12042012.jar -Dcommons-digester.jar=/srv/gump/public/workspace/commons-digester-2.x/target/commons-digester-2.2-SNAPSHOT.jar -Dtomcat-http11.jar=/srv/gump/public/workspace/jakarta-tomcat-connectors/http11/build/lib/tomcat-http11.jar -Dactivation.home=/srv/gump/packages/jaf-1.1ea -Dcatalina.home=/srv/gump/public/workspace/jakarta-tomcat-catalina/build -Dcommons-launcher.jar=/srv/gump/public/workspace/apache-commons/launcher/dist/bin/commons-launcher-12042012.jar -Dtomcat.build=/srv/gump/public/workspace/jakarta-tomcat-catalina/build -Dcommons-beanutils.jar=/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-12042012.jar -Dcommons-modeler.jar=/srv/gump/ public/workspace/apache-commons/modeler/dist/commons-modeler-12042012.jar -Dtomcat-coyote.home=/srv/gump/public/workspace/jakarta-tomcat-connectors/coyote -Djmx-remote.jar=/srv/gump/packages/jmxremote-1_0_1-bin/lib/jmxremote.jar -Dcommons-logging-api.jar=/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-12042012.jar -Dtomcat-dbcp.jar=/srv/gump/public/workspace/jakarta-tomcat-5/tomcat-deps/naming-factory-dbcp.jar -Djta.jar=/srv/gump/packages/jta-spec1_0_1/jta-spec1_0_1.jar deploy-catalina [Working Directory: /srv/gump/public/workspace/jakarta-tomcat-catalina] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/jakarta-tomcat-catalina/build/server/classes:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/packages/jaf-1.1ea/activation.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jmx-1_2_1-b
[GUMP@vmgump]: Project jakarta-tomcat-4.0 (in module jakarta-tomcat-4.0) 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 the folk at gene...@gump.apache.org. Project jakarta-tomcat-4.0 has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - jakarta-tomcat-4.0 : Servlet 2.3 and JSP 1.2 Reference Implementation Full details are available at: http://vmgump.apache.org/gump/public/jakarta-tomcat-4.0/jakarta-tomcat-4.0/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Output [bootstrap.jar] identifier set to output basename: [bootstrap] -DEBUG- Output [catalina.jar] identifier set to output basename: [catalina] -DEBUG- Output [servlets-common.jar] identifier set to output basename: [servlets-common] -DEBUG- Output [servlets-default.jar] identifier set to output basename: [servlets-default] -DEBUG- Output [servlets-invoker.jar] identifier set to output basename: [servlets-invoker] -DEBUG- Output [naming-common.jar] identifier set to output basename: [naming-common] -DEBUG- Output [naming-resources.jar] identifier set to output basename: [naming-resources] -DEBUG- Dependency on javamail exists, no need to add for property mail.jar. -DEBUG- Dependency on jaf exists, no need to add for property activation.jar. -DEBUG- Dependency on jmx exists, no need to add for property jmx.jar. -DEBUG- Dependency on jakarta-servletapi-4 exists, no need to add for property servlet.jar. -DEBUG- Dependency on xml-xerces exists, no need to add for property xerces.jar. -DEBUG- Dependency on jakarta-tomcat-util exists, no need to add for property tomcat-util.jar. -DEBUG- Dependency on commons-logging exists, no need to add for property commons-logging-api.jar. -DEBUG- Dependency on ant exists, no need to add for property ant.home. -DEBUG- Dependency on jakarta-servletapi-4 exists, no need to add for property servlet.home. -DEBUG- Dependency on jsse exists, no need to add for property jsse.home. -DEBUG- Dependency on jmx exists, no need to add for property jmx.home. -DEBUG- Dependency on jmx exists, no need to add for property jmxtools.jar. -DEBUG- Dependency on jndi exists, no need to add for property jndi.home. -DEBUG- Dependency on javamail exists, no need to add for property mail.home. -DEBUG- Dependency on jakarta-regexp exists, no need to add for property regexp.home. -DEBUG- Dependency on jakarta-regexp exists, no need to add for property regexp.jar. -DEBUG- Dependency on jaf exists, no need to add for property activation.home. -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-tomcat-4.0/jakarta-tomcat-4.0/gump_work/build_jakarta-tomcat-4.0_jakarta-tomcat-4.0.html Work Name: build_jakarta-tomcat-4.0_jakarta-tomcat-4.0 (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only -Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar:/srv/gump/public/workspace/xml-xalan/build/serializer.jar org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Djmx.license=/srv/gump/public/workspace/jakarta-tomcat-4.0/RUNNING.txt -Djaas.jar=/srv/gump/packages/jaas1_0/lib/jaas.jar -Djmx.jar=/srv/gump/packages/jmx-1_2_1-bin/lib/jmxri.jar -Djmx.home=/srv/gump/packages/jmx-1_2_1-bin -Djdbc20ext.jar=/srv/gump/packages/jdbc2_0/jdbc2_0-stdext.jar -Dregexp.jar=/srv/gump/packages/apache-attic/jakarta-regexp-1.5.jar -Dmail.home=/srv/gump/packages/javamail-1.4 -Dant.home=/srv/gump/public/workspace/ant/dist -Dservlet.jar=/srv/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar -Dxerces.jar=/srv/ gump/public/workspace/xml-xerces2/build/xercesImpl.jar -Dcommons-collections.jar=/srv/gump/public/workspace/commons-collections-3.x/target/commons-collections-3.3-SNAPSHOT.jar -Dldap.jar=/srv/gump/packages/ldap-1_2_4/lib/ldap.jar -Djsse.home=/srv/gump/packages/jsse1.0.3 -Dtomcat-coyote.jar=/srv/gump/public/workspace/jakarta-tomcat-connectors/coyote/build/lib/tomcat-coyote.jar -Dmail.jar=/srv/gump/packages/javamail-1.4/mail.jar -Dcommons-digester.jar=/srv/gump/public/workspace/commons-digester-2.x/target/commons-digester-2.2-SNAPSHOT.jar -Djndi.jar=/srv/gump/packages/jndi1_2_1/lib/jndi.jar -Djmxtools.jar=/srv/gump/packages/jmx-1_2_1-bin/lib/jmxtools.jar -Dactivation.home=/srv/gump/packages/jaf-1.1ea -Dregexp.home=/srv/gump/packages/apache-attic
Re: svn commit: r1312006 - in /tomcat/trunk/java/org/apache/catalina/core: AprLifecycleListener.java LocalStrings.properties LocalStrings_es.properties
Konstantin,
On 4/10/12 7:27 PM, Konstantin Kolinko wrote:
> 2012/4/11 :
>> Author: schultz
>> Date: Tue Apr 10 21:38:35 2012
>> New Revision: 1312006
>>
>> URL: http://svn.apache.org/viewvc?rev=1312006&view=rev
>> Log:
>> Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=53057
>> Add OpenSSL version number to INFO log message when initializing
>> +aprListener.initializedOpenSSL=OpenSSL {0} successfully initialized
>> +aprListener.initializedOpenSSL=OpenSSL {0} inicializado correctamente
>
>
> It works. ;) Though it prints "OpenSSL OpenSSL".
Yeah, I noticed that... SSL.versionString() returns "OpenSSL" as part of
the version string itself.
> Maybe redefine the message to print the version at the end, like this:
> INFO: OpenSSL successfully initialized, using OpenSSL 1.0.0g 18 Jan 2012
Sure, I could do that.
> I do not know how that will be in Spanish.
I just used Google Translate for the Spanish. It seemed like the _es
bundle had most strings while the _jp and others didn't, so I followed suit.
> (Maybe there can be some better text. I wish it were more
> understandable that it is part of Tomcat-Native).
I'm open to suggestions.
-chris
signature.asc
Description: OpenPGP digital signature
RE: AccessLogValve enhancement
Ok, I have some more time to work on this. > Though the tricky part is to find out what to delete. I was just using anything that started with the 'prefix'. This doesn't seem too bad to me since if you want to delete old files, you just need to pick a good prefix. In my test case, I set the file format to have the minute and second in the file name. The rolling worked perfectly. > it is possible to use it to generate different directories for different > dates. This does put a damper on things. The valve could easily remember previous files, but files from previous executions would be forgotten, which doesn't seem right to me. Reliably getting a list of files to delete in all situations seems like a pretty complex task. However, if we force the idea of a good prefix selection, something similar could be done to what is in the patch code already, it would just have to be recursive. Then again, this is starting to have a few too many caveats. I had wondered about removing old files for a while, and had seen other people ask this as well, so I thought a simple solution might be possible. However, now I am rethinking this. Coming back to allowing the use of a standard logger. In my mini-benchmarks, it didn't seems like it made much of a difference time wise; the time spent in the logger took between 1-2 millis on my server. This seems like it would be dwarfed by the time to actually create and deliver the response. Still, maybe this is a problem that most people have solved their own way already and people don't want to have solved again. I don't want to make anything more complicated or harder to use. I can continue to work on this, but I am losing confidence that I can come up with something that will be worth of adoption. Comments? -Original Message- From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] Sent: Thursday, March 29, 2012 4:44 PM To: Tomcat Developers List Subject: Re: AccessLogValve enhancement 2012/3/29 Mark Claassen : > After thinking about this some more, and deliberating on the subtle > issues that were coming up, I decided to reduce the scope of my > enhancement. I still like the idea of using a standard logger for this > logging, but for now I thought I would focus more on my specific problem. I wrote more about this in the issue. > https://issues.apache.org/bugzilla/show_bug.cgi?id=52688 > > Is this something that could be adopted in a future 7.0 release? > To delete or otherwise rotate (move, compress, e-mail, etc.) old files - I think I would write a , or set up a shell script in cron. When logger starts to write a new file it has to do so quickly, because it happens in a synchronized block. Deleting is possible, because it is a quick operation as well. Though the tricky part is to find out what to delete. The files are named by date and they are not created unless necessary. The date format is configurable. E.g. it is possible to use it to generate different directories for different dates. IIRC JRE's java.util.logging.FileHandler can be configured to keep n old files, but it uses different naming scheme. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-138) Cannot define the embedded Tomcat version
[ https://issues.apache.org/jira/browse/MTOMCAT-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251733#comment-13251733 ] Olivier Lamy (*$^¨%`£) commented on MTOMCAT-138: SNAPSHOT doc deployed here http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/adjust-embedded-tomcat-version.html > Cannot define the embedded Tomcat version > -- > > Key: MTOMCAT-138 > URL: https://issues.apache.org/jira/browse/MTOMCAT-138 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.0-beta-1 > Environment: Ubuntu 11.10 > Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) > Maven home: /home/mha/progs/apache-maven-3.0.3 > Java version: 1.6.0_26, vendor: Sun Microsystems Inc. > Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.0.0-17-generic", arch: "amd64", family: "unix" >Reporter: Morten Haraldsen >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > > You have documented how to change the version of embedded Tomcat here: > http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat6-maven-plugin/examples/adjust-embedded-tomcat-version.html > However, using Maven 3, this is no longer possible as it is using static > evaluation of properties, i.e. cannot override. See > http://maven.40175.n5.nabble.com/Variables-interpolation-dynamic-in-Maven-2-static-in-Maven-3-td3360336.html > (This is currently a showstopper, as I need to use 7.0.27 because of a fix in > NIO connector of Tomcat) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
RE: have Re: MaxQueueSize for Executor and Tomcat 6
> -Original Message- > From: jean-frederic clere > Sent: Mittwoch, 11. April 2012 17:33 > To: Tomcat Developers List > Subject: Re: have Re: MaxQueueSize for Executor and Tomcat 6 > > On 04/11/2012 01:34 PM, Plüm, Rüdiger, Vodafone Group wrote: > > > > > >> -Original Message- > >> From: jean-frederic clere [mailto:jfcl...@gmail.com] > >> Sent: Mittwoch, 11. April 2012 12:56 > >> To: dev@tomcat.apache.org > >> Subject: Re: have Re: MaxQueueSize for Executor and Tomcat 6 > >> > >> On 04/11/2012 09:36 AM, Plüm, Rüdiger, Vodafone Group wrote: > >>> Ping? Some sponsor for the tc6.0 status file for the below? > >> > >> Won't break an application using their own executor that implements > the > >> StandardExecutor? > > > > You mean because of the changed Executor interface? > > Yep. Ok. As far as I can see the new method execute(Runnable command, long timeout, TimeUnit unit); of the Executor interface is implemented but not used. Would it still be an acceptable backport if 1. The changes to the Executor interface are removed from the patch 2. The implementation of execute(Runnable command, long timeout, TimeUnit unit); is removed from the patch. If yes I can update the patch. Regards Rüdiger - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: have Re: MaxQueueSize for Executor and Tomcat 6
On 04/11/2012 01:34 PM, Plüm, Rüdiger, Vodafone Group wrote: -Original Message- From: jean-frederic clere [mailto:jfcl...@gmail.com] Sent: Mittwoch, 11. April 2012 12:56 To: dev@tomcat.apache.org Subject: Re: have Re: MaxQueueSize for Executor and Tomcat 6 On 04/11/2012 09:36 AM, Plüm, Rüdiger, Vodafone Group wrote: Ping? Some sponsor for the tc6.0 status file for the below? Won't break an application using their own executor that implements the StandardExecutor? You mean because of the changed Executor interface? Yep. Cheers Jean-Frederic - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 52751] Optimized configuration of the system info displayed in the default error page
https://issues.apache.org/bugzilla/show_bug.cgi?id=52751
--- Comment #7 from polina.gen...@gmail.com 2012-04-11 14:41:25 UTC ---
(In reply to comment #6)
> (In reply to comment #5)
> > Maybe the "server" attribute should be exposed through AbstractProtocol or
> > Endpoint or elsewhere.
> I'll check that.
Thanks for the hint!
Indeed using
server = ((AbstractAjpProtocol)
response.getConnector().getProtocolHandler()).getProperty("server")
will right away do the job in the case of AJP connector (if there is server
attribute configured for it).
The problem is that the server attribute is currently not explicitly handled
for the AJP connector (unlike the HttpConnecor), meaning this attribute is not
documented and its value is not read or used anywhere in the AJP connector
implementation.
Do you think we should revise this behavior and add server attribute handling
for the AJP connector?
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53063] New: Inconsistency in documentation regarding Connector's maxConnections property
https://issues.apache.org/bugzilla/show_bug.cgi?id=53063 Bug #: 53063 Summary: Inconsistency in documentation regarding Connector's maxConnections property Product: Tomcat 7 Version: trunk Platform: PC OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: Connectors AssignedTo: dev@tomcat.apache.org ReportedBy: dmik...@vmware.com Classification: Unclassified According to the documentation, the "maxConnections" property of a BIO HTTP Connector defaults to the value of "maxThreads". Additionally, the documentation states that if the "executor" property is specified, any thread related properties on the Connector will be ignored. This includes "maxThreads". However, when a BIO HTTP Connector is defined with an executor, the default value for "maxConnections" does not take the "maxThreads" value from the Executor. In fact, it appears to take the "maxThreads" value from the Connector object, which is supposed to be ignored. https://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Standard_Implementation This can be confirmed with the following test. 1.) Download Tomcat 7.0.27. 2.) Edit "conf/server.xml", uncomment the "tomcatThreadPool" executor, comment out the default HTTP connector and uncomment the HTTP connector below it that uses the executor. 3.) Start Tomcat and connect with jconsole 4.) Look at the Catalina -> ProtocolHandler -> 8080 -> maxConnections. It will be set to 200 and not 150 (maxThreads on the executor). 5.) Now, stop Tomcat, edit "conf/server.xml", add a "maxThreads" attribute to the connector, set the value to 300 and start tomcat. 6.) Examine the Catalina -> ProtocolHandler -> 8080 -> maxConnections property again and it'll be set to 300. Suggestions: 1.) Update the documentation to indicate that "maxConnections" for a BIO HTTP Connector defaults to "maxThreads" on the Connector, regardless of the presence of an executor. 2.) Fix the "maxConnections" default so that it takes its value from "maxThreads" on the executor, when an executor is specified. My preferences would be for #2. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-139) All static resources gives error 404
[ https://issues.apache.org/jira/browse/MTOMCAT-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251516#comment-13251516 ] Hudson commented on MTOMCAT-139: Integrated in TomcatMavenPlugin-mvn3.x #126 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/126/]) [MTOMCAT-139] All static resources gives error 404 (Revision 1324717) Result = SUCCESS olamy : http://svn.apache.org/viewvc/?view=rev&rev=1324717 Files : * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java > All static resources gives error 404 > > > Key: MTOMCAT-139 > URL: https://issues.apache.org/jira/browse/MTOMCAT-139 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.0 >Reporter: Morten Haraldsen >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > > Using beta-1 it works fine, but using SNAPSHOT gives 404 for all static > resources. > Looking at https://issues.apache.org/jira/browse/MTOMCAT-137 and the code I > suspect this is the culprit. (I'm not using the static context feature) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-138) Cannot define the embedded Tomcat version
[ https://issues.apache.org/jira/browse/MTOMCAT-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251517#comment-13251517 ] Hudson commented on MTOMCAT-138: Integrated in TomcatMavenPlugin-mvn3.x #126 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/126/]) [MTOMCAT-138] Cannot define the embedded Tomcat version document how to adjust embedded tomcat version used with tomcat7 plugin. (Revision 1324715) Result = SUCCESS olamy : http://svn.apache.org/viewvc/?view=rev&rev=1324715 Files : * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/site/site.xml * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/site.xml > Cannot define the embedded Tomcat version > -- > > Key: MTOMCAT-138 > URL: https://issues.apache.org/jira/browse/MTOMCAT-138 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.0-beta-1 > Environment: Ubuntu 11.10 > Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) > Maven home: /home/mha/progs/apache-maven-3.0.3 > Java version: 1.6.0_26, vendor: Sun Microsystems Inc. > Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.0.0-17-generic", arch: "amd64", family: "unix" >Reporter: Morten Haraldsen >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > > You have documented how to change the version of embedded Tomcat here: > http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat6-maven-plugin/examples/adjust-embedded-tomcat-version.html > However, using Maven 3, this is no longer possible as it is using static > evaluation of properties, i.e. cannot override. See > http://maven.40175.n5.nabble.com/Variables-interpolation-dynamic-in-Maven-2-static-in-Maven-3-td3360336.html > (This is currently a showstopper, as I need to use 7.0.27 because of a fix in > NIO connector of Tomcat) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53062] Tomcat doesn't normalize absolute urls for redirect
https://issues.apache.org/bugzilla/show_bug.cgi?id=53062 mgrigorov changed: What|Removed |Added CC||mgrigo...@apache.org -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53062] Tomcat doesn't normalize absolute urls for redirect
https://issues.apache.org/bugzilla/show_bug.cgi?id=53062 --- Comment #1 from mgrigorov 2012-04-11 12:44:53 UTC --- The demo application provides a workaround by using a custom HttpServletResponseWrapper that solves the problem but I believe this should be handled by Tomcat itself. It uses the same approach as described in https://issues.apache.org/bugzilla/show_bug.cgi?id=51972 -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53062] New: Tomcat doesn't normalize absolute urls for redirect
https://issues.apache.org/bugzilla/show_bug.cgi?id=53062
Bug #: 53062
Summary: Tomcat doesn't normalize absolute urls for redirect
Product: Tomcat 7
Version: trunk
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Servlet & JSP API
AssignedTo: dev@tomcat.apache.org
ReportedBy: mgrigo...@apache.org
Classification: Unclassified
Created attachment 28582
--> https://issues.apache.org/bugzilla/attachment.cgi?id=28582
A demo app that demonstrates the problem. Issue a request to /serv1 and check
the produced 'Location' response header
Issuing a redirect like:
response.sendRedirect("./serv2");
will lead to a response header like:
Location:http://localhost:8080/./serv2
and this causes problems for some not that smart user agents like Internet
Explorer and JMeter.
The problem has been reported few times in Apache Wicket's Jira.
Wicket works only with relative urls and lets the web container to make them
absolute when a redirect is needed. But it seems only Tomcat produces absolute
urls with '../' and/or './' inside and let the user agent to normalize them.
Other web containers normalize the url at the server side and make user agents
life easier.
See
https://issues.apache.org/jira/browse/WICKET-2732
https://issues.apache.org/jira/browse/WICKET-4260
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1324721 - /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/apt/adjust-embedded-tomcat-version.apt.vm
Author: olamy Date: Wed Apr 11 12:06:30 2012 New Revision: 1324721 URL: http://svn.apache.org/viewvc?rev=1324721&view=rev Log: fix doc metadatas Modified: tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/apt/adjust-embedded-tomcat-version.apt.vm Modified: tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/apt/adjust-embedded-tomcat-version.apt.vm URL: http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/apt/adjust-embedded-tomcat-version.apt.vm?rev=1324721&r1=1324720&r2=1324721&view=diff == --- tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/apt/adjust-embedded-tomcat-version.apt.vm (original) +++ tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/apt/adjust-embedded-tomcat-version.apt.vm Wed Apr 11 12:06:30 2012 @@ -1,9 +1,9 @@ --- Adjust Tomcat Version --- - Mark Michaelis + Olivier Lamy --- - September 30, 2010 + 2012-04-11 --- ~~ Licensed to the Apache Software Foundation (ASF) under one - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Closed] (MTOMCAT-138) Cannot define the embedded Tomcat version
[ https://issues.apache.org/jira/browse/MTOMCAT-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MTOMCAT-138. -- Resolution: Fixed Fix Version/s: 2.0 artifactId has changed for tomcat7 see documentation added here http://svn.apache.org/viewvc?view=revision&revision=1324716 > Cannot define the embedded Tomcat version > -- > > Key: MTOMCAT-138 > URL: https://issues.apache.org/jira/browse/MTOMCAT-138 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.0-beta-1 > Environment: Ubuntu 11.10 > Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) > Maven home: /home/mha/progs/apache-maven-3.0.3 > Java version: 1.6.0_26, vendor: Sun Microsystems Inc. > Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.0.0-17-generic", arch: "amd64", family: "unix" >Reporter: Morten Haraldsen >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > > You have documented how to change the version of embedded Tomcat here: > http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat6-maven-plugin/examples/adjust-embedded-tomcat-version.html > However, using Maven 3, this is no longer possible as it is using static > evaluation of properties, i.e. cannot override. See > http://maven.40175.n5.nabble.com/Variables-interpolation-dynamic-in-Maven-2-static-in-Maven-3-td3360336.html > (This is currently a showstopper, as I need to use 7.0.27 because of a fix in > NIO connector of Tomcat) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Closed] (MTOMCAT-139) All static resources gives error 404
[ https://issues.apache.org/jira/browse/MTOMCAT-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MTOMCAT-139. -- Resolution: Fixed > All static resources gives error 404 > > > Key: MTOMCAT-139 > URL: https://issues.apache.org/jira/browse/MTOMCAT-139 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.0 >Reporter: Morten Haraldsen >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > > Using beta-1 it works fine, but using SNAPSHOT gives 404 for all static > resources. > Looking at https://issues.apache.org/jira/browse/MTOMCAT-137 and the code I > suspect this is the culprit. (I'm not using the static context feature) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1324717 - in /tomcat/maven-plugin/trunk: tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java tomcat7-maven-plugin/src/main/java/org/apache/tomca
Author: olamy
Date: Wed Apr 11 12:03:20 2012
New Revision: 1324717
URL: http://svn.apache.org/viewvc?rev=1324717&view=rev
Log:
[MTOMCAT-139] All static resources gives error 404
Modified:
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
Modified:
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java
URL:
http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java?rev=1324717&r1=1324716&r2=1324717&view=diff
==
---
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java
(original)
+++
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java
Wed Apr 11 12:03:20 2012
@@ -355,7 +355,7 @@ public abstract class AbstractRunMojo
* The static context docroot base fully qualified path.
* if null static context won't be added
*
- * @parameter expression="${maven.tomcat.staticContextPath}"
+ * @parameter expression="${maven.tomcat.staticContextDocbase}"
* @since 2.0
*/
private String staticContextDocbase;
Modified:
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
URL:
http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java?rev=1324717&r1=1324716&r2=1324717&view=diff
==
---
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
(original)
+++
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
Wed Apr 11 12:03:20 2012
@@ -349,7 +349,7 @@ public abstract class AbstractRunMojo
* The static context docroot base fully qualified path
* if null static context won't be added
*
- * @parameter expression="${maven.tomcat.staticContextPath}"
+ * @parameter expression="${maven.tomcat.staticContextDocbase}"
* @since 2.0
*/
private String staticContextDocbase;
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1324716 - /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/apt/adjust-embedded-tomcat-version.apt.vm
Author: olamy
Date: Wed Apr 11 12:02:55 2012
New Revision: 1324716
URL: http://svn.apache.org/viewvc?rev=1324716&view=rev
Log:
oups missed to add the file
Added:
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/apt/adjust-embedded-tomcat-version.apt.vm
(with props)
Added:
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/apt/adjust-embedded-tomcat-version.apt.vm
URL:
http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/apt/adjust-embedded-tomcat-version.apt.vm?rev=1324716&view=auto
==
---
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/apt/adjust-embedded-tomcat-version.apt.vm
(added)
+++
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/apt/adjust-embedded-tomcat-version.apt.vm
Wed Apr 11 12:02:55 2012
@@ -0,0 +1,162 @@
+ ---
+ Adjust Tomcat Version
+ ---
+ Mark Michaelis
+ ---
+ September 30, 2010
+ ---
+
+ ~~ Licensed to the Apache Software Foundation (ASF) under one
+ ~~ or more contributor license agreements. See the NOTICE file
+ ~~ distributed with this work for additional information
+ ~~ regarding copyright ownership. The ASF licenses this file
+ ~~ to you 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.
+
+ ~~ NOTE: For help with the syntax of this file, see:
+ ~~ http://maven.apache.org/doxia/references/apt-format.html
+
+Adjust Tomcat Version
+
+ In case you need to adjust the version of the embedded tomcat to run you can
do so by changing
+ the runtime-dependencies:
+
++--
+
+ [...]
+
+ 7.0.27
+ [...]
+
+ [...]
+
+
+
+
+ org.apache.tomcat.maven
+ tomcat7-maven-plugin
+ ${project.version}
+
+
+org.apache.tomcat.embed
+tomcat-embed-core
+${tomcat.version}
+
+
+org.apache.tomcat
+tomcat-util
+${tomcat.version}
+
+
+org.apache.tomcat
+tomcat-coyote
+${tomcat.version}
+
+
+org.apache.tomcat
+tomcat-api
+${tomcat.version}
+
+
+
+org.apache.tomcat
+tomcat-jdbc
+${tomcat.version}
+
+
+
+org.apache.tomcat
+tomcat-dbcp
+${tomcat.version}
+
+
+
+org.apache.tomcat
+tomcat-servlet-api
+${tomcat.version}
+
+
+
+org.apache.tomcat
+tomcat-jsp-api
+${tomcat.version}
+
+
+
+org.apache.tomcat
+tomcat-jasper
+${tomcat.version}
+
+
+
+org.apache.tomcat
+tomcat-jasper-el
+${tomcat.version}
+
+
+
+org.apache.tomcat
+tomcat-el-api
+${tomcat.version}
+
+
+
+org.apache.tomcat
+tomcat-catalina
+${tomcat.version}
+
+
+
+org.apache.tomcat
+tomcat-tribes
+${tomcat.version}
+
+
+
+org.apache.tomcat
+tomcat-catalina-ha
+${tomcat.version}
+
+
+
+org.apache.tomcat
+tomcat-annotations-api
+${tomcat.version}
+
+
+
+org.apache.tomcat
+tomcat-juli
+${tomcat.version}
+
+
+
+org.apache.tomcat.embed
+tomcat-embed-logging-juli
+${tomcat.version}
+
+
+org.apache.tomcat.embed
+tomcat-embed-logging-log4j
+${tomcat.version}
+
+
+
+[...]
+
+
+[...]
+
+ [...]
+
++--
Propchange:
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/apt/adjust-embedded-tomcat-version.apt.vm
--
svn:eol-style = native
Propchange:
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/apt/adjust-embedded-tomcat-version.apt.vm
--
svn:keywords = Author Date Id Revision
-
svn commit: r1324715 - in /tomcat/maven-plugin/trunk: tomcat6-maven-plugin/src/site/site.xml tomcat7-maven-plugin/src/site/site.xml
Author: olamy Date: Wed Apr 11 12:02:41 2012 New Revision: 1324715 URL: http://svn.apache.org/viewvc?rev=1324715&view=rev Log: [MTOMCAT-138] Cannot define the embedded Tomcat version document how to adjust embedded tomcat version used with tomcat7 plugin. Modified: tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/site/site.xml tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/site.xml Modified: tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/site/site.xml URL: http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/site/site.xml?rev=1324715&r1=1324714&r2=1324715&view=diff == --- tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/site/site.xml (original) +++ tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/site/site.xml Wed Apr 11 12:02:41 2012 @@ -22,25 +22,25 @@ - - - - + + + + - - - + + + - http://www.apache.org/foundation/how-it-works.html"/> - http://www.apache.org/foundation/"/> + http://www.apache.org/foundation/how-it-works.html"/> + http://www.apache.org/foundation/"/> http://www.apache.org/foundation/sponsorship.html"/> - http://www.apache.org/foundation/thanks.html"/> + http://www.apache.org/foundation/thanks.html"/> Modified: tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/site.xml URL: http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/site.xml?rev=1324715&r1=1324714&r2=1324715&view=diff == --- tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/site.xml (original) +++ tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/site/site.xml Wed Apr 11 12:02:41 2012 @@ -21,18 +21,19 @@ http://maven.apache.org/DECORATION/1.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/DECORATION/1.0.0 http://maven.apache.org/xsd/decoration-1.0.0.xsd";> - - - + + + + - http://www.apache.org/foundation/how-it-works.html"/> - http://www.apache.org/foundation/"/> + http://www.apache.org/foundation/how-it-works.html"/> + http://www.apache.org/foundation/"/> http://www.apache.org/foundation/sponsorship.html"/> - http://www.apache.org/foundation/thanks.html"/> + http://www.apache.org/foundation/thanks.html"/> - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Updated] (MTOMCAT-139) All static resources gives error 404
[ https://issues.apache.org/jira/browse/MTOMCAT-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) updated MTOMCAT-139: --- Fix Version/s: 2.0 > All static resources gives error 404 > > > Key: MTOMCAT-139 > URL: https://issues.apache.org/jira/browse/MTOMCAT-139 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.0 >Reporter: Morten Haraldsen >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > > Using beta-1 it works fine, but using SNAPSHOT gives 404 for all static > resources. > Looking at https://issues.apache.org/jira/browse/MTOMCAT-137 and the code I > suspect this is the culprit. (I'm not using the static context feature) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
RE: have Re: MaxQueueSize for Executor and Tomcat 6
> -Original Message- > From: jean-frederic clere [mailto:jfcl...@gmail.com] > Sent: Mittwoch, 11. April 2012 12:56 > To: dev@tomcat.apache.org > Subject: Re: have Re: MaxQueueSize for Executor and Tomcat 6 > > On 04/11/2012 09:36 AM, Plüm, Rüdiger, Vodafone Group wrote: > > Ping? Some sponsor for the tc6.0 status file for the below? > > Won't break an application using their own executor that implements the > StandardExecutor? You mean because of the changed Executor interface? Regards Rüdiger - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: have Re: MaxQueueSize for Executor and Tomcat 6
On 04/11/2012 09:36 AM, Plüm, Rüdiger, Vodafone Group wrote: Ping? Some sponsor for the tc6.0 status file for the below? Won't break an application using their own executor that implements the StandardExecutor? Cheers Jean-Frederic - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Issue Comment Edited] (MTOMCAT-139) All static resources gives error 404
[
https://issues.apache.org/jira/browse/MTOMCAT-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251465#comment-13251465
]
Morten Haraldsen edited comment on MTOMCAT-139 at 4/11/12 10:52 AM:
AbstractRunMojo.java (trunk):
/**
* The static context
*
* @parameter expression="${maven.tomcat.staticContextPath}"
default-value="/"
* @since 2.0
*/
private String staticContextPath;
/**
* The static context docroot base fully qualified path
* if null static context won't be added
*
* @parameter expression="${maven.tomcat.staticContextPath}"
* @since 2.0
*/
private String staticContextDocbase;
Looking at the above, the code shows parameter
expression="${maven.tomcat.staticContextPath} for both fields
staticContextDocbase and staticContextPath.
was (Author: xaer):
AbstractRunMojo.java (trunk):
/**
* The static context
*
* @parameter expression="${maven.tomcat.staticContextPath}"
default-value="/"
* @since 2.0
*/
private String staticContextPath;
/**
* The static context docroot base fully qualified path
* if null static context won't be added
*
* @parameter expression="${maven.tomcat.staticContextPath}"
* @since 2.0
*/
private String staticContextDocbase;
Looking at the above, the code shows parameter
expression="${maven.tomcat.staticContextPath} for both fields
staticContextDocbase and staticContextPath. Also, staticContextPath can never
be null, as it is set to default "/"
> All static resources gives error 404
>
>
> Key: MTOMCAT-139
> URL: https://issues.apache.org/jira/browse/MTOMCAT-139
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat7
>Affects Versions: 2.0
>Reporter: Morten Haraldsen
>Assignee: Olivier Lamy (*$^¨%`£)
>
> Using beta-1 it works fine, but using SNAPSHOT gives 404 for all static
> resources.
> Looking at https://issues.apache.org/jira/browse/MTOMCAT-137 and the code I
> suspect this is the culprit. (I'm not using the static context feature)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-139) All static resources gives error 404
[
https://issues.apache.org/jira/browse/MTOMCAT-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251465#comment-13251465
]
Morten Haraldsen commented on MTOMCAT-139:
--
AbstractRunMojo.java (trunk):
/**
* The static context
*
* @parameter expression="${maven.tomcat.staticContextPath}"
default-value="/"
* @since 2.0
*/
private String staticContextPath;
/**
* The static context docroot base fully qualified path
* if null static context won't be added
*
* @parameter expression="${maven.tomcat.staticContextPath}"
* @since 2.0
*/
private String staticContextDocbase;
Looking at the above, the code shows parameter
expression="${maven.tomcat.staticContextPath} for both fields
staticContextDocbase and staticContextPath. Also, staticContextPath can never
be null, as it is set to default "/"
> All static resources gives error 404
>
>
> Key: MTOMCAT-139
> URL: https://issues.apache.org/jira/browse/MTOMCAT-139
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat7
>Affects Versions: 2.0
>Reporter: Morten Haraldsen
>Assignee: Olivier Lamy (*$^¨%`£)
>
> Using beta-1 it works fine, but using SNAPSHOT gives 404 for all static
> resources.
> Looking at https://issues.apache.org/jira/browse/MTOMCAT-137 and the code I
> suspect this is the culprit. (I'm not using the static context feature)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Created] (MTOMCAT-139) All static resources gives error 404
All static resources gives error 404 Key: MTOMCAT-139 URL: https://issues.apache.org/jira/browse/MTOMCAT-139 Project: Apache Tomcat Maven Plugin Issue Type: Bug Components: tomcat7 Affects Versions: 2.0 Reporter: Morten Haraldsen Assignee: Olivier Lamy (*$^¨%`£) Using beta-1 it works fine, but using SNAPSHOT gives 404 for all static resources. Looking at https://issues.apache.org/jira/browse/MTOMCAT-137 and the code I suspect this is the culprit. (I'm not using the static context feature) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-136) Tomcat7-maven-plugin 2.0-beta1 and useSeparateTomcatClassloader fails with run goal
[ https://issues.apache.org/jira/browse/MTOMCAT-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251458#comment-13251458 ] Leigh Anderson commented on MTOMCAT-136: [ERROR] Failed to execute goal org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-beta-1:run (default-cli) on project mantis-test-web-app: No such archiver: 'jar'. -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-beta-1:run (default-cli) on project mantis-test-web-app: No such archiver: 'jar'. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: No such archiver: 'jar'. at org.apache.tomcat.maven.plugin.tomcat7.run.RunMojo.createWebappLoader(RunMojo.java:277) at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.createContext(AbstractRunMojo.java:415) at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.startContainer(AbstractRunMojo.java:719) at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.execute(AbstractRunMojo.java:353) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.tomcat.maven.common.run.TomcatRunException: No such archiver: 'jar'. at org.apache.tomcat.maven.common.run.DefaultClassLoaderEntriesCalculator.calculateClassPathEntries(DefaultClassLoaderEntriesCalculator.java:184) at org.apache.tomcat.maven.plugin.tomcat7.run.RunMojo.createWebappLoader(RunMojo.java:232) ... 24 more Caused by: org.codehaus.plexus.archiver.manager.NoSuchArchiverException: No such archiver: 'jar'. at org.codehaus.plexus.archiver.manager.DefaultArchiverManager.getUnArchiver(DefaultArchiverManager.java:77) at org.apache.tomcat.maven.common.run.DefaultClassLoaderEntriesCalculator.calculateClassPathEntries(DefaultClassLoaderEntriesCalculator.java:146) ... 25 more > Tomcat7-maven-plugin 2.0-beta1 and useSeparateTomcatClassloader fails with > run goal > --- > > Key: MTOMCAT-136 > URL: https://issues.apache.org/jira/browse/MTOMCAT-136 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.0-beta-1 > Environment: Java 1.6.0_26, Maven 3.0.4, OS X 10.7.3 >Reporter: Leigh Anderson >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > > I'm trying to start a web application with 'mvn tomcat7:run'. It seems > that with the configuration below it fails with the following error: > [INFO] > > [ERROR] Failed to execute goal > org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-beta-1:run (default-cli) on > project mantis-test-web-app: No such archiver: 'jar'. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace
[jira] [Created] (MTOMCAT-138) Cannot define the embedded Tomcat version
Cannot define the embedded Tomcat version -- Key: MTOMCAT-138 URL: https://issues.apache.org/jira/browse/MTOMCAT-138 Project: Apache Tomcat Maven Plugin Issue Type: Bug Components: tomcat7 Affects Versions: 2.0-beta-1 Environment: Ubuntu 11.10 Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: /home/mha/progs/apache-maven-3.0.3 Java version: 1.6.0_26, vendor: Sun Microsystems Inc. Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.0.0-17-generic", arch: "amd64", family: "unix" Reporter: Morten Haraldsen Assignee: Olivier Lamy (*$^¨%`£) You have documented how to change the version of embedded Tomcat here: http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat6-maven-plugin/examples/adjust-embedded-tomcat-version.html However, using Maven 3, this is no longer possible as it is using static evaluation of properties, i.e. cannot override. See http://maven.40175.n5.nabble.com/Variables-interpolation-dynamic-in-Maven-2-static-in-Maven-3-td3360336.html (This is currently a showstopper, as I need to use 7.0.27 because of a fix in NIO connector of Tomcat) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53061] tomcat asynchronous invocation problem
https://issues.apache.org/bugzilla/show_bug.cgi?id=53061 --- Comment #1 from Slava 2012-04-11 07:46:56 UTC --- Reproduced on: - tomcat-7.0.23, 7.0.25 and 7.0.26 - java 64 bit 1.6.0_18 and 1.6.0_29 - Linux CentOS release 5.6 (Final) 64 bit - NIO connector -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
RE: have Re: MaxQueueSize for Executor and Tomcat 6
Ping? Some sponsor for the tc6.0 status file for the below? Regards Rüdiger > -Original Message- > From: Plüm, Rüdiger, Vodafone Group > [mailto:] > Sent: Mittwoch, 28. März 2012 17:49 > To: Tomcat Developers List > Subject: RE: have Re: MaxQueueSize for Executor and Tomcat 6 > > > > > -Original Message- > > From: Konstantin Kolinko > > Sent: Mittwoch, 28. März 2012 17:05 > > To: Tomcat Developers List > > Subject: have Re: MaxQueueSize for Executor and Tomcat 6 > > > > 2012/3/28 Plüm, Rüdiger, Vodafone Group > > > Are there any plans to backport r723889 > > (http://svn.apache.org/viewvc?view=revision&revision=723889, > > > Add the ability to configure a job queue size, and a timeout for > how > > long we want to try to add something > > > to the queue.) to Tomcat 6? > > > > > > Having the MaxQueueSize attribute available for executors in Tomcat > 6 > > would be quite handy for me. > > > > > > > I do not see anything obvious against backporting it. > > > > > > If you really need it, I suggest you to create a patch against > current > > tc6.0.x code and attach it to a new Bugzilla issue. Instructions are > > at [1], but probably you already know them. > > Thanks. Done: > > https://issues.apache.org/bugzilla/show_bug.cgi?id=52996 > > Regards > > Rüdiger > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53061] tomcat asynchronous invocation problem
https://issues.apache.org/bugzilla/show_bug.cgi?id=53061 Slava changed: What|Removed |Added CC||vyacheslav.trainin@playtech ||.com -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53061] New: tomcat asynchronous invocation problem
https://issues.apache.org/bugzilla/show_bug.cgi?id=53061
Bug #: 53061
Summary: tomcat asynchronous invocation problem
Product: Tomcat 7
Version: 7.0.25
Platform: Other
OS/Version: Linux
Status: NEW
Severity: major
Priority: P2
Component: Catalina
AssignedTo: dev@tomcat.apache.org
ReportedBy: vyacheslav.trai...@playtech.com
Classification: Unclassified
Created attachment 28581
--> https://issues.apache.org/bugzilla/attachment.cgi?id=28581
a simple test reproducing the problem
We encountered a problem during asynchronous operations (tomcat7 with servlet
3).
Description:
One client continuously sends post requests to the server. On the server side
for each request created AsyncContext with timeout 20 seconds:
AsyncContext asyncContext = req.startAsync(req, resp);
asyncContext.setTimeout(2);
As expected after approximately 20 sec the requests are completed. Then another
client also begins to send requests to the server but in this case they are
explicitly completed after 500 milliseconds. Something like this:
AsyncContext asyncContext = req.startAsync(req, resp);
asyncContext.setTimeout(2);
try {
Thread.sleep(500);
} catch (Exception e) {
}
asyncContext.complete();
The problem is that after running the second client all requests that are
waiting for timeout (from the first client) are stuck and not released
(onTimeout method of AsyncEvent is not called) until the second client stops
sending requests.
It looks like the problem occurs on Linux but not on Windows.
I attached a simple test that may help to reproduce this issue. The following
servlet accepts URL parameter “complete”.
When “complete=1” the request will be completed after 500ms.
Otherwise the request will wait till timeout (20 seconds).
Run client that periodically sends requests to /servlet?complete=0. (I have
tested it with 10 parallel threads that run in a loop)
Then run another client that periodically sends requests to /servlet?complete=1
(This client can use only a single thread)
See that the first client does not receive any responses while the second
client is running.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
