Re: [VOTE] Release Apache Tomcat 7.0.28
On 17.06.2012 22:08, Mark Thomas wrote: On 16/06/2012 10:04, Rainer Jung wrote: Most noteable observation: File conf/web.xml now is open 9 times in parallel (9 file descriptors), was 4 times in 7.0.27. I see 9 open file handle in Windows but this drops to zero once I force a full GC. On this basis, I'm not concerned but it would be good if you could confirm the same behaviour. Confirmed, closed after full GC, so likely a Finalizer run. Nothing to worry. I suspect my getResourceAsStream() changes might be responsible for this. I believe we are doing everything we should to close the streams so I don't think there is anything we can do about these. I guess you can't get down to the native FD and closing the files is postponed until the Finalizer runs. - src consistent with svn tag, except for the following minor points (no regression) - line ends of modules/jdbc-pool/resources/MANIFEST.MF differ between svn and gz although eol-style is set correctly. *.MF is not in the list of text file types. I'll fix that in a sec. OK. - the files we copy before building, e.g. catalina.properties and jdbc-pool.xml are of course not in svn for the cp target location, but they are in the src bundles. I have fixed this for trunk and 7.0.x. Cool - JMX MBean-Comparison - tldScanTime went up for /docs from 7 to 53 (maybe not significant) and for /examples from 275 to 470 (but varies between 280 and 750) Hmm. getResoureAsStream() again? As I wrote the times are varying a lot between runs. Retrying with 7.0.27 it seems it is a bit faster, but I only tried a few times and it's not enough for real statistics. I might do some more serious check with lots of starts and stops this evening. Regards, Rainer - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Tomcat 7 parallel deployment viability
2012/6/18 Cloud Works : > Hello, > > The parallel deployment feature is potentiality awesome but memory > limitation makes it very problematic for production environments. > There is no way to control the memory consumption under a single JVM. > (between apps) > If you have an app running you can't know that Tomcat will have enough > memory to parallel deploy the update. > > This feature falls between being feasible but unnecessary in dev and test > environments and highly relevant yet not feasible for production. > Has anyone figured out a way to make this feature relevant? > Your question is offtopic on dev@. It belongs to the users list. There exist a number of ways to monitor memory consumption and to ensure that you have enough memory for your job. If you do not like the feature, you are free not to use it. If you are asking for others' experience in using the feature, search/ask on the users mailing list. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [GUMP@vmgump]: Project tomcat-trunk-validate (in module tomcat-trunk) failed
2012/6/18 Bill Barker : > - tomcat-trunk-validate : Tomcat 8.x, a web server implementing Java > Servlet 3.1, > > validate: > [mkdir] Created dir: > /srv/gump/public/workspace/tomcat-trunk/output/res/checkstyle > [checkstyle] Running Checkstyle 5.6-SNAPSHOT on 2282 files > [checkstyle] > /srv/gump/public/workspace/tomcat-trunk/modules/jdbc-pool/resources/MANIFEST.MF:2: > Line matches the illegal pattern '\s+$'. > [checkstyle] > /srv/gump/public/workspace/tomcat-trunk/modules/jdbc-pool/resources/MANIFEST.MF:17: > Line matches the illegal pattern '\s+$'. > > BUILD FAILED > /srv/gump/public/workspace/tomcat-trunk/build.xml:461: Got 2 errors and 0 > warnings. > The file: http://svn.apache.org/viewvc/tomcat/trunk/modules/jdbc-pool/resources/MANIFEST.MF?revision=1144964&view=markup [[[ Manifest-Version: 1.0 Export-Package: org.apache.tomcat.jdbc.pool;version="@VERSION@"; uses:="javax.management,javax.naming,javax.naming.spi,javax.sql, org.apache.tomcat.jdbc.pool.jmx", org.apache.tomcat.jdbc.pool.interceptor;version="@VERSION@"; uses:="javax.management.openmbean,org.apache.tomcat.jdbc.pool", org.apache.tomcat.jdbc.pool.jmx;version="@VERSION@"; uses:="javax.management,org.apache.tomcat.jdbc.pool" Ant-Version: Apache Ant 1.7.0 Bundle-Vendor: Apache Software Foundation Bundle-Version: @VERSION@ Bundle-Name: Apache Tomcat JDBC Connection Pool Bundle-ManifestVersion: 2 Created-By: 11.0-b16 (Sun Microsystems Inc.) Bundle-SymbolicName: org.apache.tomcat.jdbc Import-Package: javax.management;version="0", javax.management.openmbean;version="0", javax.naming;version="0", javax.sql;version="0", org.apache.juli.logging;version="[6.0.18, 7.0.0)" ]]] There is whitespace after "Export-Package:" and after "Import-Package:" which is required, because according to grammar [1] a value always starts with a space. (value: SPACE *otherchar newline *continuation) (continuation: SPACE *otherchar newline) [1] http://docs.oracle.com/javase/7/docs/technotes/guides/jar/jar.html I am OK to disable the validation for this file, but I I think it would be better to unwrap the first line of those values. It will be a bit more ugly but it will avoid problems if there is someone whose editor is configured to auto-trim the lines. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1351259 - /tomcat/trunk/build.xml
Author: markt Date: Mon Jun 18 10:02:34 2012 New Revision: 1351259 URL: http://svn.apache.org/viewvc?rev=1351259&view=rev Log: Exclude manifest files from checkstyle Modified: tomcat/trunk/build.xml Modified: tomcat/trunk/build.xml URL: http://svn.apache.org/viewvc/tomcat/trunk/build.xml?rev=1351259&r1=1351258&r2=1351259&view=diff == --- tomcat/trunk/build.xml (original) +++ tomcat/trunk/build.xml Mon Jun 18 10:02:34 2012 @@ -468,6 +468,7 @@ + - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1351261 - in /tomcat/tc7.0.x/trunk: ./ build.xml
Author: markt Date: Mon Jun 18 10:03:59 2012 New Revision: 1351261 URL: http://svn.apache.org/viewvc?rev=1351261&view=rev Log: Exclude manifest files from checkstyle Modified: tomcat/tc7.0.x/trunk/ (props changed) tomcat/tc7.0.x/trunk/build.xml Propchange: tomcat/tc7.0.x/trunk/ -- Merged /tomcat/trunk:r1351259 Modified: tomcat/tc7.0.x/trunk/build.xml URL: http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/build.xml?rev=1351261&r1=1351260&r2=1351261&view=diff == --- tomcat/tc7.0.x/trunk/build.xml (original) +++ tomcat/tc7.0.x/trunk/build.xml Mon Jun 18 10:03:59 2012 @@ -457,6 +457,7 @@ + - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [GUMP@vmgump]: Project tomcat-trunk-validate (in module tomcat-trunk) failed
On 18/06/2012 09:27, Konstantin Kolinko wrote: > I am OK to disable the validation for this file, but I I think it > would be better to unwrap the first line of those values. It will be a > bit more ugly but it will avoid problems if there is someone whose > editor is configured to auto-trim the lines. I think disabling validation is simpler since they may well fail other tests as well. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1351269 - /tomcat/tc6.0.x/trunk/STATUS.txt
Author: kkolinko Date: Mon Jun 18 10:21:01 2012 New Revision: 1351269 URL: http://svn.apache.org/viewvc?rev=1351269&view=rev Log: Propose updated patch Modified: tomcat/tc6.0.x/trunk/STATUS.txt Modified: tomcat/tc6.0.x/trunk/STATUS.txt URL: http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=1351269&r1=1351268&r2=1351269&view=diff == --- tomcat/tc6.0.x/trunk/STATUS.txt (original) +++ tomcat/tc6.0.x/trunk/STATUS.txt Mon Jun 18 10:21:01 2012 @@ -234,13 +234,15 @@ PATCHES PROPOSED TO BACKPORT: * Implement maxHeaderCount attribute on Connector. It is equivalent of LimitRequestFields directive of Apache HTTPD (backport of r1350295) + In JkMain.setProperty(): Fix setting of properties when connector has + already started for properties that have aliases. E.g. changing + maxHeaderCount attribute on Connector MBean via JMX. Patch: - http://people.apache.org/~kkolinko/patches/2012-06-18_tc6_maxHeaderCount_v1.patch + http://people.apache.org/~kkolinko/patches/2012-06-18_tc6_maxHeaderCount_v2.patch Eol-Style: svn propset svn:eol-style native java/org/apache/coyote/AbstractProtocol.java svn propset svn:eol-style native java/org/apache/tomcat/util/net/AbstractEndpoint.java - +0: kkolinko (I have not tested it yet. Esp. whether JkCoyoteHandler impl. works) - +1: + +1: kkolinko -1: PATCHES/ISSUES THAT ARE STALLED - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Created] (MTOMCAT-162) SaxException when deploying multiple WARs
Neale Upstone created MTOMCAT-162: - Summary: SaxException when deploying multiple WARs Key: MTOMCAT-162 URL: https://issues.apache.org/jira/browse/MTOMCAT-162 Project: Apache Tomcat Maven Plugin Issue Type: Bug Affects Versions: 2.0-beta-1 Reporter: Neale Upstone Priority: Critical When deploying multiple WARs, a file is created in /tmp by the plugin, but is empty when tomcat starts, thus causing a parsing exception. -- 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-60) Multiple-War-Deployment in configuration section.
[
https://issues.apache.org/jira/browse/MTOMCAT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395798#comment-13395798
]
Neale Upstone commented on MTOMCAT-60:
--
I've created https://issues.apache.org/jira/browse/MTOMCAT-162 to separately
track the sax exception and will move the patch to there.
> Multiple-War-Deployment in configuration section.
> -
>
> Key: MTOMCAT-60
> URL: https://issues.apache.org/jira/browse/MTOMCAT-60
> Project: Apache Tomcat Maven Plugin
> Issue Type: Improvement
>Reporter: Joerg Bellmann
>Priority: Minor
> Attachments: SaxExceptionFix.patch, maven-tomcat-plugin.patch.txt,
> patch-for-tomcat6.patch
>
>
> When a user want to deploy multiple webapps with the plugin it uses all
> project-war-dependencies with scope 'tomcat'. Maven 3 shows the following
> message at project-processing:
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for de.jbellmann.failsafe:de.jbellmann.failsafe.web:war:0.0.1-SNAPSHOT
> [WARNING] 'dependencies.dependency.scope' for
> org.springframework.samples:mvc-showcase:war must be one of [provided,
> compile, runtime, test, system] but is 'tomcat'. @
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> {code}
> Configuring the additional webapps in the configuration section like this for
> example :
> {code}
>
> org.codehaus.mojo
> tomcat-maven-plugin
> 1.1-SNAPSHOT
>
>
>
> start-tomcat-integration-tests
>
> run
>
>
> pre-integration-test
>
> true
>
> true
>
>
>
>
> org.springframework.samples
>
> mvc-showcase
>
> 1.0.0-BUILD-SNAPSHOT
>
> /mvc-showcase2
>
>
>
>
>
>
>
>
> {code}
> avoids the warnings and makes maven 3 happy.
> As a plus you can configure an contextPath different from the artifactId.
> This solution was inspired by the 'maven-dependency-plugin' and uses some
> code-snippets from it.
> Jörg Bellmann
--
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] [Updated] (MTOMCAT-162) SaxException when deploying multiple WARs
[ https://issues.apache.org/jira/browse/MTOMCAT-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neale Upstone updated MTOMCAT-162: -- Attachment: SaxExceptionFix.patch Attached patch resolves this issue by not attempting to re-use the generated context file. > SaxException when deploying multiple WARs > - > > Key: MTOMCAT-162 > URL: https://issues.apache.org/jira/browse/MTOMCAT-162 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 >Reporter: Neale Upstone >Priority: Critical > Attachments: SaxExceptionFix.patch > > > When deploying multiple WARs, a file is created in /tmp by the plugin, but is > empty when tomcat starts, thus causing a parsing exception. -- 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] [Updated] (MTOMCAT-60) Multiple-War-Deployment in configuration section.
[
https://issues.apache.org/jira/browse/MTOMCAT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neale Upstone updated MTOMCAT-60:
-
Attachment: (was: SaxExceptionFix.patch)
> Multiple-War-Deployment in configuration section.
> -
>
> Key: MTOMCAT-60
> URL: https://issues.apache.org/jira/browse/MTOMCAT-60
> Project: Apache Tomcat Maven Plugin
> Issue Type: Improvement
>Reporter: Joerg Bellmann
>Priority: Minor
> Attachments: maven-tomcat-plugin.patch.txt, patch-for-tomcat6.patch
>
>
> When a user want to deploy multiple webapps with the plugin it uses all
> project-war-dependencies with scope 'tomcat'. Maven 3 shows the following
> message at project-processing:
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for de.jbellmann.failsafe:de.jbellmann.failsafe.web:war:0.0.1-SNAPSHOT
> [WARNING] 'dependencies.dependency.scope' for
> org.springframework.samples:mvc-showcase:war must be one of [provided,
> compile, runtime, test, system] but is 'tomcat'. @
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> {code}
> Configuring the additional webapps in the configuration section like this for
> example :
> {code}
>
> org.codehaus.mojo
> tomcat-maven-plugin
> 1.1-SNAPSHOT
>
>
>
> start-tomcat-integration-tests
>
> run
>
>
> pre-integration-test
>
> true
>
> true
>
>
>
>
> org.springframework.samples
>
> mvc-showcase
>
> 1.0.0-BUILD-SNAPSHOT
>
> /mvc-showcase2
>
>
>
>
>
>
>
>
> {code}
> avoids the warnings and makes maven 3 happy.
> As a plus you can configure an contextPath different from the artifactId.
> This solution was inspired by the 'maven-dependency-plugin' and uses some
> code-snippets from it.
> Jörg Bellmann
--
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: svn commit: r1351269 - /tomcat/tc6.0.x/trunk/STATUS.txt
2012/6/18 : > Author: kkolinko > Date: Mon Jun 18 10:21:01 2012 > New Revision: 1351269 > > URL: http://svn.apache.org/viewvc?rev=1351269&view=rev > Log: > Propose updated patch > > Modified: > tomcat/tc6.0.x/trunk/STATUS.txt > > * Implement maxHeaderCount attribute on Connector. > It is equivalent of LimitRequestFields directive of Apache HTTPD > (backport of r1350295) > In JkMain.setProperty(): Fix setting of properties when connector has > already started for properties that have aliases. E.g. changing > maxHeaderCount attribute on Connector MBean via JMX. > Patch: > > http://people.apache.org/~kkolinko/patches/2012-06-18_tc6_maxHeaderCount_v2.patch > Eol-Style: > svn propset svn:eol-style native > java/org/apache/coyote/AbstractProtocol.java > svn propset svn:eol-style native > java/org/apache/tomcat/util/net/AbstractEndpoint.java Several comments on the proposed patch. 1. I tested HTTP connectors using RequestHeaderExample servlet + JMX 2. I have not tested request handling by AJP connectors, but tested that the maxHeaderCount setting is manageable via JMX. 3. I am introducing new base classes, AbstractProtocol and AbstractEndpoint. 4. JkCoyoteHandler AJP connector differs a lot. The maxHeaderCount property was added to HandlerRequest class. 5. Connector.getMaxHeaderCount() slightly differs with its implementation in Tomcat 7. This is to handle JkCoyoteHandler connector. 6. The patch includes a fix for JkMain.setProperty(). This is so that replacement of "maxHeaderCount" -> "request.maxHeaderCount" happened not only at startup but also when changing this attribute on Connector MBean. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[RESULT][VOTE] Release Apache Tomcat 7.0.28
The result of the vote was as follows: Binding +1: markt, mturk, rjung, olamy, kkolinko, pero No other votes were cast. The vote therefore passes. I'll proceed as follows: - move release to dist - wait for mirrors to sync - update website - wait for website changes to sync - announce the release Given that most mirrors sync in 4-6 hours, I should be able to complete this today. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r696 - /dev/tomcat/tomcat-7/v7.0.28/ /release/tomcat/tomcat-7/v7.0.28/
Author: markt Date: Mon Jun 18 12:01:34 2012 New Revision: 696 Log: Release Tomcat 7.0.28 Added: release/tomcat/tomcat-7/v7.0.28/ - copied from r695, dev/tomcat/tomcat-7/v7.0.28/ Removed: dev/tomcat/tomcat-7/v7.0.28/ - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r696 - /dev/tomcat/tomcat-7/v7.0.28/ /release/tomcat/tomcat-7/v7.0.28/
Author: markt Date: Mon Jun 18 12:01:34 2012 New Revision: 696 Log: Release Tomcat 7.0.28 Added: release/tomcat/tomcat-7/v7.0.28/ - copied from r695, dev/tomcat/tomcat-7/v7.0.28/ Removed: dev/tomcat/tomcat-7/v7.0.28/ - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53422] iPlanet (7.0.11) Instance crashes frequently when using Status Worker in (mod_jk/1.2.32)
https://issues.apache.org/bugzilla/show_bug.cgi?id=53422 --- Comment #2 from Kiran --- Created attachment 28954 --> https://issues.apache.org/bugzilla/attachment.cgi?id=28954&action=edit Data gathered upon crash Attached are the details that I've gathered upon crash. The nsapi and the webserver logs does not have any more information. Let me know if you need me to gather anything more. -- 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
[Bug 53393] tomcat-connectors-1.2.37-src Crashing web server segmentation fault
https://issues.apache.org/bugzilla/show_bug.cgi?id=53393 --- Comment #3 from satyapal --- Created attachment 28955 --> https://issues.apache.org/bugzilla/attachment.cgi?id=28955&action=edit Core dump image file Core dump image file -- 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
[Bug 53393] tomcat-connectors-1.2.37-src Crashing web server segmentation fault
https://issues.apache.org/bugzilla/show_bug.cgi?id=53393 --- Comment #4 from satyapal --- [Mon Jun 18 23:12:51 2012] [notice] Apache/2.2.22 (Ubuntu) mod_jk/1.2.37 mod_ssl/2.2.22 OpenSSL/1.0.1 configured -- resuming normal operations [Mon Jun 18 23:13:01 2012] [notice] child pid 4949 exit signal Segmentation fault (11), possible coredump in /tmp/apache2-gdb-dump [Mon Jun 18 23:13:15 2012] [notice] child pid 4948 exit signal Segmentation fault (11), possible coredump in /tmp/apache2-gdb-dump [Mon Jun 18 23:13:15 2012] [notice] child pid 5016 exit signal Segmentation fault (11), possible coredump in /tmp/apache2-gdb-dump [Mon Jun 18 23:13:17 2012] [notice] child pid 5053 exit signal Segmentation fault (11), possible coredump in /tmp/apache2-gdb-dump [Mon Jun 18 23:13:18 2012] [notice] child pid 5083 exit signal Segmentation fault (11), possible coredump in /tmp/apache2-gdb-dump [Mon Jun 18 23:13:18 2012] [notice] child pid 5084 exit signal Segmentation fault (11), possible coredump in /tmp/apache2-gdb-dump [Mon Jun 18 23:13:20 2012] [notice] child pid 5143 exit signal Segmentation fault (11), possible coredump in /tmp/apache2-gdb-dump [Mon Jun 18 23:13:21 2012] [notice] child pid 5173 exit signal Segmentation fault (11), possible coredump in /tmp/apache2-gdb-dump [Mon Jun 18 23:13:21 2012] [notice] child pid 5174 exit signal Segmentation fault (11), possible coredump in /tmp/apache2-gdb-dump I changed /etc/apache2/apache2.conf added following at the end CoreDumpDirectory /tmp/apache2-gdb-dump But nothing is there -- 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
[Tomcat Wiki] Update of "PoweredBy" by Borneosoft
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change
notification.
The "PoweredBy" page has been changed by Borneosoft:
http://wiki.apache.org/tomcat/PoweredBy?action=diff&rev1=429&rev2=430
=== BlogScope.net ===
[[http://www.blogscope.net/|{{http://www.blogscope.net/images/blogscope-white-logo.png|http://www.blogscope.net/}}]]
[[http://www.blogscope.net/|BlogScope]] is a search and analysis tool for
blogosphere. Developed as research project at U of Toronto, built upon many
open source applications including Tomcat.
[[http://www.blogscope.net/about/|Read more about it]].
+
+ === Borneosoft ===
+ {{http://www.borneosoft.com/Borneosoft/_images/borneosoft4.png}}
[[http://www.borneosoft.com|Borneosoft]] - Easy-to-use Web-based CRM with Form
Builder and Admin Tools.
=== BreakBIT ===
[[http://www.breakbit.com|BreakBIT]] Fairwizard - an integrated enterprise
management system for Fair and Exhibitions.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [RESULT][VOTE] Release Apache Tomcat 7.0.28
2012/6/18 Mark Thomas : > The result of the vote was as follows: > > Binding +1: > markt, mturk, rjung, olamy, kkolinko, pero > > No other votes were cast. > > The vote therefore passes. > > I'll proceed as follows: > - move release to dist > - wait for mirrors to sync > - update website > - wait for website changes to sync > - announce the release Cool. Just checked repository.a.o, you missed to finish this part. Intentional ? > > Given that most mirrors sync in 4-6 hours, I should be able to complete > this today. > > Mark > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [RESULT][VOTE] Release Apache Tomcat 7.0.28
On 18/06/2012 14:16, Olivier Lamy wrote: > 2012/6/18 Mark Thomas : >> The result of the vote was as follows: >> >> Binding +1: >> markt, mturk, rjung, olamy, kkolinko, pero >> >> No other votes were cast. >> >> The vote therefore passes. >> >> I'll proceed as follows: >> - move release to dist >> - wait for mirrors to sync >> - update website >> - wait for website changes to sync >> - announce the release > > Cool. > > Just checked repository.a.o, you missed to finish this part. Intentional ? Just haven't got around to it yet. I can do it now. Mark > >> >> Given that most mirrors sync in 4-6 hours, I should be able to complete >> this today. >> >> Mark >> >> - >> 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
[Bug 53422] iPlanet (7.0.11) Instance crashes frequently when using Status Worker in (mod_jk/1.2.32)
https://issues.apache.org/bugzilla/show_bug.cgi?id=53422 --- Comment #3 from Kiran --- Please ignore this bug, It was to do with the way we built the shared object file from the source. There don't seem to be binary distribution for recent versions of JK on Solaris platform, Perhaps I may not be looking at the right place? -- 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-153) align all Maven dependency versions to 2.0.11
[ https://issues.apache.org/jira/browse/MTOMCAT-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395929#comment-13395929 ] Neale Upstone commented on MTOMCAT-153: --- Would it not be saner for the effort going in to move forward to at least maven 2.2.1, if not 3.0? > align all Maven dependency versions to 2.0.11 > - > > Key: MTOMCAT-153 > URL: https://issues.apache.org/jira/browse/MTOMCAT-153 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Peter lynch >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > Attachments: align-maven-versions.patch > > > There are several different, old versions of Maven artifact dependencies in > use. > Attached patch align's all of these to 2.0.11 -- 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: r1351368 - in /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6: AbstractRunMojo.java Webapp.java
Author: olamy
Date: Mon Jun 18 14:49:43 2012
New Revision: 1351368
URL: http://svn.apache.org/viewvc?rev=1351368&view=rev
Log:
[MTOMCAT-60] Multiple-War-Deployment in configuration section.
Added:
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/Webapp.java
(with props)
Modified:
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/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=1351368&r1=1351367&r2=1351368&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
Mon Jun 18 14:49:43 2012
@@ -32,7 +32,11 @@ import org.apache.catalina.servlets.Defa
import org.apache.catalina.startup.Catalina;
import org.apache.catalina.startup.Embedded;
import org.apache.maven.artifact.Artifact;
+import org.apache.maven.artifact.resolver.ArtifactNotFoundException;
+import org.apache.maven.artifact.resolver.ArtifactResolutionException;
import org.apache.maven.artifact.resolver.filter.ScopeArtifactFilter;
+import
org.apache.maven.artifact.versioning.InvalidVersionSpecificationException;
+import org.apache.maven.artifact.versioning.VersionRange;
import org.apache.maven.plugin.MojoExecutionException;
import org.apache.maven.plugin.MojoFailureException;
import org.apache.maven.project.MavenProject;
@@ -46,6 +50,7 @@ import org.codehaus.plexus.classworlds.r
import org.codehaus.plexus.classworlds.realm.DuplicateRealmException;
import org.codehaus.plexus.util.DirectoryScanner;
import org.codehaus.plexus.util.FileUtils;
+import org.codehaus.plexus.util.StringUtils;
import org.w3c.dom.Document;
import org.w3c.dom.NamedNodeMap;
import org.w3c.dom.Node;
@@ -60,9 +65,9 @@ import java.io.IOException;
import java.net.InetAddress;
import java.net.MalformedURLException;
import java.net.URL;
-import java.security.Principal;
import java.util.ArrayList;
import java.util.Collection;
+import java.util.Collections;
import java.util.Iterator;
import java.util.List;
import java.util.Map;
@@ -78,6 +83,33 @@ import java.util.Set;
public abstract class AbstractRunMojo
extends AbstractI18NTomcat6Mojo
{
+// -
+// Mojo Components
+// -
+
+/**
+ * Used to look up Artifacts in the remote repository.
+ *
+ * @component
+ */
+protected org.apache.maven.artifact.factory.ArtifactFactory factory;
+
+/**
+ * Location of the local repository.
+ *
+ * @parameter expression="${localRepository}"
+ * @readonly
+ * @required
+ */
+private org.apache.maven.artifact.repository.ArtifactRepository local;
+
+/**
+ * Used to look up Artifacts in the remote repository.
+ *
+ * @component
+ */
+protected org.apache.maven.artifact.resolver.ArtifactResolver resolver;
+
// --
// Mojo Parameters
// --
@@ -195,6 +227,7 @@ public abstract class AbstractRunMojo
*
* @parameter expression="${maven.tomcat.addContextWarDependencies}"
default-value="false"
* @since 1.0
+ * @deprecated use additionalWebapps instead
*/
private boolean addContextWarDependencies;
@@ -334,6 +367,12 @@ public abstract class AbstractRunMojo
*/
protected boolean skip;
+/**
+ * @parameter
+ * @since 2.0
+ */
+private List additionalWebapps;
+
// --
// Fields
// --
@@ -378,7 +417,8 @@ public abstract class AbstractRunMojo
public void execute()
throws MojoExecutionException, MojoFailureException
{
-if ( skip && !addContextWarDependencies )
+
+if ( skip && !addContextWarDependencies &&
getAdditionalWebapps().isEmpty() )
{
getLog().info( "skip execution" );
return;
@@ -758,7 +798,7 @@ public abstract class AbstractRunMojo
host.addChild( context );
createStaticContext( container, context, host );
-if ( addContextWarDependencies )
+if ( addContextWarDependencies ||
!getAdditionalWebapps().isEmpty() )
svn commit: r1351369 - /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/Webapp.java
Author: olamy Date: Mon Jun 18 14:49:56 2012 New Revision: 1351369 URL: http://svn.apache.org/viewvc?rev=1351369&view=rev Log: add missing license header Modified: tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/Webapp.java Modified: tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/Webapp.java URL: http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/Webapp.java?rev=1351369&r1=1351368&r2=1351369&view=diff == --- tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/Webapp.java (original) +++ tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/Webapp.java Mon Jun 18 14:49:56 2012 @@ -1,5 +1,24 @@ package org.apache.tomcat.maven.plugin.tomcat6; +/* + * 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. + */ + import org.apache.commons.lang.StringUtils; import org.apache.maven.artifact.Artifact; - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-60) Multiple-War-Deployment in configuration section.
[
https://issues.apache.org/jira/browse/MTOMCAT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395932#comment-13395932
]
Olivier Lamy (*$^¨%`£) commented on MTOMCAT-60:
---
Patch applied.
Thanks!
I won't close that until we get similar patch for tomcat7 mojo.
Do you have time to work on that ?
> Multiple-War-Deployment in configuration section.
> -
>
> Key: MTOMCAT-60
> URL: https://issues.apache.org/jira/browse/MTOMCAT-60
> Project: Apache Tomcat Maven Plugin
> Issue Type: Improvement
>Reporter: Joerg Bellmann
>Priority: Minor
> Attachments: maven-tomcat-plugin.patch.txt, patch-for-tomcat6.patch
>
>
> When a user want to deploy multiple webapps with the plugin it uses all
> project-war-dependencies with scope 'tomcat'. Maven 3 shows the following
> message at project-processing:
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for de.jbellmann.failsafe:de.jbellmann.failsafe.web:war:0.0.1-SNAPSHOT
> [WARNING] 'dependencies.dependency.scope' for
> org.springframework.samples:mvc-showcase:war must be one of [provided,
> compile, runtime, test, system] but is 'tomcat'. @
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> {code}
> Configuring the additional webapps in the configuration section like this for
> example :
> {code}
>
> org.codehaus.mojo
> tomcat-maven-plugin
> 1.1-SNAPSHOT
>
>
>
> start-tomcat-integration-tests
>
> run
>
>
> pre-integration-test
>
> true
>
> true
>
>
>
>
> org.springframework.samples
>
> mvc-showcase
>
> 1.0.0-BUILD-SNAPSHOT
>
> /mvc-showcase2
>
>
>
>
>
>
>
>
> {code}
> avoids the warnings and makes maven 3 happy.
> As a plus you can configure an contextPath different from the artifactId.
> This solution was inspired by the 'maven-dependency-plugin' and uses some
> code-snippets from it.
> Jörg Bellmann
--
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] [Assigned] (MTOMCAT-162) SaxException when deploying multiple WARs
[ https://issues.apache.org/jira/browse/MTOMCAT-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) reassigned MTOMCAT-162: -- Assignee: Olivier Lamy (*$^¨%`£) > SaxException when deploying multiple WARs > - > > Key: MTOMCAT-162 > URL: https://issues.apache.org/jira/browse/MTOMCAT-162 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 >Reporter: Neale Upstone >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Critical > Attachments: SaxExceptionFix.patch > > > When deploying multiple WARs, a file is created in /tmp by the plugin, but is > empty when tomcat starts, thus causing a parsing exception. -- 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-153) align all Maven dependency versions to 2.0.11
[ https://issues.apache.org/jira/browse/MTOMCAT-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395936#comment-13395936 ] Olivier Lamy (*$^¨%`£) commented on MTOMCAT-153: some people still use old maven versions. And it doesn't make real difference @runtime except preventing some users using this plugin. > align all Maven dependency versions to 2.0.11 > - > > Key: MTOMCAT-153 > URL: https://issues.apache.org/jira/browse/MTOMCAT-153 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Peter lynch >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > Attachments: align-maven-versions.patch > > > There are several different, old versions of Maven artifact dependencies in > use. > Attached patch align's all of these to 2.0.11 -- 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: r1351375 - /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java
Author: olamy
Date: Mon Jun 18 14:57:32 2012
New Revision: 1351375
URL: http://svn.apache.org/viewvc?rev=1351375&view=rev
Log:
[MTOMCAT-162] SaxException when deploying multiple WARs
Submitted by Neale Upstone.
Modified:
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java
Modified:
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java
URL:
http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java?rev=1351375&r1=1351374&r2=1351375&view=diff
==
---
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java
(original)
+++
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java
Mon Jun 18 14:57:32 2012
@@ -86,7 +86,7 @@ public class RunMojo
* @see
http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/catalina/loader/WebappLoader.html#setDelegate(boolean)
* @since 1.0
*/
-private boolean delegate = true;
+private final boolean delegate = true;
/**
* represents the delay in seconds between each classPathScanning change
invocation
@@ -127,8 +127,6 @@ public class RunMojo
*/
private List additionalClasspathDirs;
-private File temporaryContextFile = null;
-
// --
// AbstractRunMojo Implementation
// --
@@ -205,16 +203,16 @@ public class RunMojo
{
for ( String additionalClasspathDir : additionalClasspathDirs )
{
- if( StringUtils.isNotBlank(additionalClasspathDir))
- {
- File file = new File( additionalClasspathDir );
- if ( file.exists() )
- {
- String fileUri = file.toURI().toString();
- getLog().debug( "add file:" + fileUri + " as a
additionalClasspathDir" );
- loader.addRepository( fileUri );
- }
- }
+if ( StringUtils.isNotBlank( additionalClasspathDir ) )
+{
+File file = new File( additionalClasspathDir );
+if ( file.exists() )
+{
+String fileUri = file.toURI().toString();
+getLog().debug( "add file:" + fileUri + " as a
additionalClasspathDir" );
+loader.addRepository( fileUri );
+}
+}
}
}
}
@@ -243,10 +241,8 @@ public class RunMojo
protected File getContextFile()
throws MojoExecutionException
{
-if ( temporaryContextFile != null )
-{
-return temporaryContextFile;
-}
+File temporaryContextFile = null;
+
//
// context attributes backgroundProcessorDelay reloadable cannot be
modified at runtime.
// It looks only values from the file ared used
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1351376 - /tomcat/maven-plugin/trunk/pom.xml
Author: olamy Date: Mon Jun 18 14:57:39 2012 New Revision: 1351376 URL: http://svn.apache.org/viewvc?rev=1351376&view=rev Log: add Neale Upstone in contributor section Modified: tomcat/maven-plugin/trunk/pom.xml Modified: tomcat/maven-plugin/trunk/pom.xml URL: http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/pom.xml?rev=1351376&r1=1351375&r2=1351376&view=diff == --- tomcat/maven-plugin/trunk/pom.xml (original) +++ tomcat/maven-plugin/trunk/pom.xml Mon Jun 18 14:57:39 2012 @@ -104,6 +104,9 @@ Peter Lynch + + Neale Upstone + - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1351377 - /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java
Author: olamy
Date: Mon Jun 18 14:57:54 2012
New Revision: 1351377
URL: http://svn.apache.org/viewvc?rev=1351377&view=rev
Log:
javadoc @link to the class
Modified:
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/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=1351377&r1=1351376&r2=1351377&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
Mon Jun 18 14:57:54 2012
@@ -368,6 +368,7 @@ public abstract class AbstractRunMojo
protected boolean skip;
/**
+ * @see {@link Webapp}
* @parameter
* @since 2.0
*/
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-162) SaxException when deploying multiple WARs
[ https://issues.apache.org/jira/browse/MTOMCAT-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395939#comment-13395939 ] Olivier Lamy (*$^¨%`£) commented on MTOMCAT-162: Thanks. I won't close that until having a similar patch for tomcat7 mojo. > SaxException when deploying multiple WARs > - > > Key: MTOMCAT-162 > URL: https://issues.apache.org/jira/browse/MTOMCAT-162 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 >Reporter: Neale Upstone >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Critical > Attachments: SaxExceptionFix.patch > > > When deploying multiple WARs, a file is created in /tmp by the plugin, but is > empty when tomcat starts, thus causing a parsing exception. -- 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-162) SaxException when deploying multiple WARs
[ https://issues.apache.org/jira/browse/MTOMCAT-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395947#comment-13395947 ] Hudson commented on MTOMCAT-162: Integrated in TomcatMavenPlugin-mvn3.x #161 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/161/]) [MTOMCAT-162] SaxException when deploying multiple WARs Submitted by Neale Upstone. (Revision 1351375) Result = FAILURE olamy : http://svn.apache.org/viewvc/?view=rev&rev=1351375 Files : * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java > SaxException when deploying multiple WARs > - > > Key: MTOMCAT-162 > URL: https://issues.apache.org/jira/browse/MTOMCAT-162 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 >Reporter: Neale Upstone >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Critical > Attachments: SaxExceptionFix.patch > > > When deploying multiple WARs, a file is created in /tmp by the plugin, but is > empty when tomcat starts, thus causing a parsing exception. -- 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-60) Multiple-War-Deployment in configuration section.
[
https://issues.apache.org/jira/browse/MTOMCAT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395946#comment-13395946
]
Hudson commented on MTOMCAT-60:
---
Integrated in TomcatMavenPlugin-mvn3.x #161 (See
[https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/161/])
[MTOMCAT-60] Multiple-War-Deployment in configuration section. (Revision
1351368)
Result = FAILURE
olamy : http://svn.apache.org/viewvc/?view=rev&rev=1351368
Files :
*
/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java
*
/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/Webapp.java
> Multiple-War-Deployment in configuration section.
> -
>
> Key: MTOMCAT-60
> URL: https://issues.apache.org/jira/browse/MTOMCAT-60
> Project: Apache Tomcat Maven Plugin
> Issue Type: Improvement
>Reporter: Joerg Bellmann
>Priority: Minor
> Attachments: maven-tomcat-plugin.patch.txt, patch-for-tomcat6.patch
>
>
> When a user want to deploy multiple webapps with the plugin it uses all
> project-war-dependencies with scope 'tomcat'. Maven 3 shows the following
> message at project-processing:
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for de.jbellmann.failsafe:de.jbellmann.failsafe.web:war:0.0.1-SNAPSHOT
> [WARNING] 'dependencies.dependency.scope' for
> org.springframework.samples:mvc-showcase:war must be one of [provided,
> compile, runtime, test, system] but is 'tomcat'. @
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> {code}
> Configuring the additional webapps in the configuration section like this for
> example :
> {code}
>
> org.codehaus.mojo
> tomcat-maven-plugin
> 1.1-SNAPSHOT
>
>
>
> start-tomcat-integration-tests
>
> run
>
>
> pre-integration-test
>
> true
>
> true
>
>
>
>
> org.springframework.samples
>
> mvc-showcase
>
> 1.0.0-BUILD-SNAPSHOT
>
> /mvc-showcase2
>
>
>
>
>
>
>
>
> {code}
> avoids the warnings and makes maven 3 happy.
> As a plus you can configure an contextPath different from the artifactId.
> This solution was inspired by the 'maven-dependency-plugin' and uses some
> code-snippets from it.
> Jörg Bellmann
--
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-160) "Skipping non-war project" should not happen if using
[
https://issues.apache.org/jira/browse/MTOMCAT-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395958#comment-13395958
]
Neale Upstone commented on MTOMCAT-160:
---
Shouldn't it be the !isWar() test that gets the extra condition added?
if ( skip && !addContextWarDependencies )
{
getLog().info( "skip execution" );
return;
}
// ensure project is a web application
if ( !isWar() )
{
getLog().info( messagesProvider.getMessage(
"AbstractRunMojo.nonWar" ) );
return;
}
should read:
if ( skip )
{
getLog().info( "skip execution" );
return;
}
// ensure project is a web application
if ( !isWar() && !addContextWarDependencies )
{
getLog().info( messagesProvider.getMessage(
"AbstractRunMojo.nonWar" ) );
return;
}
> "Skipping non-war project" should not happen if using
>
> -
>
> Key: MTOMCAT-160
> URL: https://issues.apache.org/jira/browse/MTOMCAT-160
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
>Affects Versions: 1.1, 2.0-beta-1
>Reporter: Neale Upstone
>Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 2.0
>
>
> For build pipelines,
> true is often used in
> projects which contain just the acceptance tests.
> If the project packaging is set as JAR, we get:
> [INFO] [tomcat:run {execution: start-tomcat}]
> [INFO] Skipping non-war project
> I can see reasons why the skip logic is there, but this should not happen
> when addContextWarDependencies (or any cleaner successor) is enabled.
> Any chance of this getting tweaked for beta2/rc1 ?
--
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: r1351394 - /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
Author: olamy
Date: Mon Jun 18 15:48:28 2012
New Revision: 1351394
URL: http://svn.apache.org/viewvc?rev=1351394&view=rev
Log:
[MTOMCAT-160] "Skipping non-war project" should not happen if using
fix logic.
Modified:
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
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=1351394&r1=1351393&r2=1351394&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
Mon Jun 18 15:48:28 2012
@@ -412,13 +412,13 @@ public abstract class AbstractRunMojo
public void execute()
throws MojoExecutionException, MojoFailureException
{
-if ( skip && !addContextWarDependencies )
+if ( skip )
{
getLog().info( "skip execution" );
return;
}
// ensure project is a web application
-if ( !isWar() )
+if ( !isWar() && !addContextWarDependencies )
{
getLog().info( messagesProvider.getMessage(
"AbstractRunMojo.nonWar" ) );
return;
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-160) "Skipping non-war project" should not happen if using
[
https://issues.apache.org/jira/browse/MTOMCAT-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395971#comment-13395971
]
Olivier Lamy (*$^¨%`£) commented on MTOMCAT-160:
correct!. I have just fixed that.
Thanks!
> "Skipping non-war project" should not happen if using
>
> -
>
> Key: MTOMCAT-160
> URL: https://issues.apache.org/jira/browse/MTOMCAT-160
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
>Affects Versions: 1.1, 2.0-beta-1
>Reporter: Neale Upstone
>Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 2.0
>
>
> For build pipelines,
> true is often used in
> projects which contain just the acceptance tests.
> If the project packaging is set as JAR, we get:
> [INFO] [tomcat:run {execution: start-tomcat}]
> [INFO] Skipping non-war project
> I can see reasons why the skip logic is there, but this should not happen
> when addContextWarDependencies (or any cleaner successor) is enabled.
> Any chance of this getting tweaked for beta2/rc1 ?
--
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
[Bug 53422] iPlanet (7.0.11) Instance crashes frequently when using Status Worker in (mod_jk/1.2.32)
https://issues.apache.org/bugzilla/show_bug.cgi?id=53422 Rainer Jung changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #4 from Rainer Jung --- I can see whether I can provide some Solaris Sparc binaries for 1.2.32 and 1.2.37 during the next days.They will be built against relative old versions of the Sun Wweb server though, similar to the binaries you can find at http://archive.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/solaris/jk-1.2.31/sparc/ Just cusious: what did you have to change in your build process? I'm closing this issue here, since you say you find the cause of the crashes. Feel free to reopen if I have misunderstood you. Regards, Rainer -- 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-160) "Skipping non-war project" should not happen if using
[
https://issues.apache.org/jira/browse/MTOMCAT-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395987#comment-13395987
]
Hudson commented on MTOMCAT-160:
Integrated in TomcatMavenPlugin-mvn3.x #162 (See
[https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/162/])
[MTOMCAT-160] "Skipping non-war project" should not happen if using
fix logic. (Revision 1351394)
Result = FAILURE
olamy : http://svn.apache.org/viewvc/?view=rev&rev=1351394
Files :
*
/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
> "Skipping non-war project" should not happen if using
>
> -
>
> Key: MTOMCAT-160
> URL: https://issues.apache.org/jira/browse/MTOMCAT-160
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
>Affects Versions: 1.1, 2.0-beta-1
>Reporter: Neale Upstone
>Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 2.0
>
>
> For build pipelines,
> true is often used in
> projects which contain just the acceptance tests.
> If the project packaging is set as JAR, we get:
> [INFO] [tomcat:run {execution: start-tomcat}]
> [INFO] Skipping non-war project
> I can see reasons why the skip logic is there, but this should not happen
> when addContextWarDependencies (or any cleaner successor) is enabled.
> Any chance of this getting tweaked for beta2/rc1 ?
--
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
[GUMP@vmgump]: Project tomcat-trunk-validate (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-validate 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: - tomcat-trunk-validate : 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-validate/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on checkstyle exists, no need to add for property checkstyle.jar. -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-validate/gump_work/build_tomcat-trunk_tomcat-trunk-validate.html Work Name: build_tomcat-trunk_tomcat-trunk-validate (Type: Build) Work ended in a state of : Failed Elapsed: 31 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 -Dcheckstyle.jar=/srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar -Dexecute.validate=true validate [Working Directory: /srv/gump/public/workspace/tomcat-trunk] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/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/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-18062012.jar:/srv/gump/public/workspace/apache-commons/cli/target/commons-cli-1.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/exec/target/commons-exec-1.1.1-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/validator/dist/commons-validator-18062012.jar:/srv/gump/public/workspace/junit/dist/junit-18062012.jar:/srv/gump /public/workspace/junit/dist/junit-dep-18062012.jar:/srv/gump/public/workspace/google-guava/guava/target/guava-12.0-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-18062012.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-18062012.jar:/srv/gump/public/workspace/commons-collections-3.x/target/commons-collections-3.3-SNAPSHOT.jar:/srv/gump/packages/antlr/antlr-3.1.3.jar:/srv/gump/public/workspace/jdom/build/jdom.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-18062012.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-18062012-dep.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 - Buildfile: /srv/gump/public/workspace/tomcat-trunk/build.xml build-prepare: [delete] Deleting directory /srv/gump/public/workspace/tomcat-trunk/output/build/temp [mkdir] Created dir: /srv/gump/public/workspace/tomcat-trunk/output/build/temp compile-prepare: download-validate: proxyflags: setproxy: testexist: [echo] Testing for /srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar downloadzip: validate: [mkdir] Created dir: /srv/gump/public/workspace/tomcat-trunk/output/res/checkstyle [checkstyle] Running Checkstyle 5.6-SNAPSHOT on 2282 files [checkstyle] /srv/gump/public/workspace/tomcat-trunk/modules/jdbc-pool/resources/MANIFEST.MF:2: Line matches the illegal pattern '\s+$'. [checkstyle] /srv/gump/public/workspace/tomcat-trunk/modules/jdbc-pool/resources/MANIFEST.MF:17: Line matches the illegal pattern '\s+$'. BUILD FAILED /srv/gump/public/workspace/tomcat-trunk/build.xml:461: Got 2 errors and 0 warnings. Total time: 30 seconds - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-validate/rss.xml - Atom: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-validate/atom.xml == Gump Tracking Only === Produced by Apache Gump(TM) version 2.3. Gump Run 06001218062012, vmgump.apache.org:vmgump:06001218062012 Gump E-mail Identifier (unique within run) #2. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
svn commit: r1351476 - /tomcat/maven-plugin/trunk/pom.xml
Author: olamy Date: Mon Jun 18 20:20:44 2012 New Revision: 1351476 URL: http://svn.apache.org/viewvc?rev=1351476&view=rev Log: use tomcat artifacts 7.0.28 Modified: tomcat/maven-plugin/trunk/pom.xml Modified: tomcat/maven-plugin/trunk/pom.xml URL: http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/pom.xml?rev=1351476&r1=1351475&r2=1351476&view=diff == --- tomcat/maven-plugin/trunk/pom.xml (original) +++ tomcat/maven-plugin/trunk/pom.xml Mon Jun 18 20:20:44 2012 @@ -66,7 +66,7 @@ 2001 2008 -7.0.27 +7.0.28 - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [Proposal] Preparatory refactoring for Resource handling refactoring
Mark, On 6/15/12 1:00 PM, Mark Thomas wrote: > Since this is fairly major work, any objections before I start? I like the unification of all these things. Would this be a good time to consider making Tomcat 7 RTC with such a significant change to the core of the trunk? -chris signature.asc Description: OpenPGP digital signature
tldScanTimes TC 7.0.20-7.0.28 Was: Re: [VOTE] Release Apache Tomcat 7.0.28
On 18.06.2012 09:28, Rainer Jung wrote: On 17.06.2012 22:08, Mark Thomas wrote: On 16/06/2012 10:04, Rainer Jung wrote: - JMX MBean-Comparison - tldScanTime went up for /docs from 7 to 53 (maybe not significant) and for /examples from 275 to 470 (but varies between 280 and 750) Hmm. getResoureAsStream() again? As I wrote the times are varying a lot between runs. Retrying with 7.0.27 it seems it is a bit faster, but I only tried a few times and it's not enough for real statistics. I might do some more serious check with lots of starts and stops this evening. I started TC 7.0.20 to 7.0.28 50 times each and did some trivial statistics on the tldScanTimes: version avg median min max ROOT 7.0.20 9.4 5 4 209 7.0.21 10.95 4 159 7.0.22 15.75 4 199 7.0.23 22.85 4 56 7.0.24 22.35 4 204 7.0.25 23.516 4 203 7.0.26 36.340 4 256 7.0.27 34.842 4 162 7.0.28 26.222 4 83 manager 7.0.20 10.67 5 34 7.0.21 11.77 5 42 7.0.22 6.8 6 5 18 7.0.23 11.07 5 187 7.0.24 12.77 5 197 7.0.25 7.8 7 6 44 7.0.26 11.47 5 128 7.0.27 10.27 6 127 7.0.28 7.0 7 5 13 host-manager 7.0.20 6.6 6 6 12 7.0.21 6.7 7 6 8 7.0.22 7.9 7 6 47 7.0.23 6.8 7 6 14 7.0.24 7.9 7 6 67 7.0.25 6.8 7 6 7 7.0.26 7.4 7 6 37 7.0.27 10.37 6 89 7.0.28 10.36 5 147 docs 7.0.20 32.126 7 86 7.0.21 34.228 6 126 7.0.22 30.024 6 70 7.0.23 38.144 6 122 7.0.24 40.345 7 56 7.0.25 42.744 6 164 7.0.26 46.248 7 85 7.0.27 45.847 7 91 7.0.28 56.148 6 299 examples 7.0.20 357.7 314 208 712 7.0.21 386.9 352 194 750 7.0.22 362.4 313 218 707 7.0.23 564.3 531 279 918 7.0.24 556.7 555 289 1044 7.0.25 540.4 514 315 1146 7.0.26 457.9 450 239 842 7.0.27 419.4 404 232 720 7.0.28 414.4 388 234 922 I don't see a regression for 7.0.28 here. There was a slowdown between 22 and 23, but we got faster since then and are not far away from 22. Regards, Rainer - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[GUMP@vmgump]: Project tomcat-trunk-validate (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-validate has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 2 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-validate : 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-validate/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on checkstyle exists, no need to add for property checkstyle.jar. -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-validate/gump_work/build_tomcat-trunk_tomcat-trunk-validate.html Work Name: build_tomcat-trunk_tomcat-trunk-validate (Type: Build) Work ended in a state of : Failed Elapsed: 33 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 -Dcheckstyle.jar=/srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar -Dexecute.validate=true validate [Working Directory: /srv/gump/public/workspace/tomcat-trunk] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/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/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-19062012.jar:/srv/gump/public/workspace/apache-commons/cli/target/commons-cli-1.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/exec/target/commons-exec-1.1.1-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/validator/dist/commons-validator-19062012.jar:/srv/gump/public/workspace/junit/dist/junit-19062012.jar:/srv/gump /public/workspace/junit/dist/junit-dep-19062012.jar:/srv/gump/public/workspace/google-guava/guava/target/guava-12.0-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-19062012.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-19062012.jar:/srv/gump/public/workspace/commons-collections-3.x/target/commons-collections-3.3-SNAPSHOT.jar:/srv/gump/packages/antlr/antlr-3.1.3.jar:/srv/gump/public/workspace/jdom/build/jdom.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-19062012.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-19062012-dep.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 - Buildfile: /srv/gump/public/workspace/tomcat-trunk/build.xml build-prepare: [delete] Deleting directory /srv/gump/public/workspace/tomcat-trunk/output/build/temp [mkdir] Created dir: /srv/gump/public/workspace/tomcat-trunk/output/build/temp compile-prepare: download-validate: proxyflags: setproxy: testexist: [echo] Testing for /srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar downloadzip: validate: [mkdir] Created dir: /srv/gump/public/workspace/tomcat-trunk/output/res/checkstyle [checkstyle] Running Checkstyle 5.6-SNAPSHOT on 2282 files [checkstyle] /srv/gump/public/workspace/tomcat-trunk/modules/jdbc-pool/resources/MANIFEST.MF:2: Line matches the illegal pattern '\s+$'. [checkstyle] /srv/gump/public/workspace/tomcat-trunk/modules/jdbc-pool/resources/MANIFEST.MF:17: Line matches the illegal pattern '\s+$'. BUILD FAILED /srv/gump/public/workspace/tomcat-trunk/build.xml:461: Got 2 errors and 0 warnings. Total time: 32 seconds - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-validate/rss.xml - Atom: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-validate/atom.xml == Gump Tracking Only === Produced by Apache Gump(TM) version 2.3. Gump Run 1219062012, vmgump.apache.org:vmgump:1219062012 Gump E-mail Identifier (unique within run) #30. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] -
WebSocketServlet (and chat example) comments
Hi, I have been playing with the web sockets support in 7.0.27. I have some comments and, as requested in the readme, am sending them to the dev list. Caveat: it's been a while since .27, so perhaps some of these issues are addressed in the nightly builds. Anyhow, here we go: 1) In the createWebSocketInbound method implemented by the chat example's subclass of WebSocketServlet, there is seemingly no way to interrogate the incoming request for information like post/get parms as in a conventional servlet. Since these can be sent later via a message, so this is only a slight problem. However, a more serious problem is that I can't get at the IP address of the incoming request when the connection is being created. This means I can't implement something like a block list (common in games) to remove annoying things like DOS attacks and misbehaving players from hitting my server at the point where a connection is created (and hence resources used). Access to some form of parms would allow me to do additional validation (like user name and login) at this stage as well. 2) MessageInbound is oddly named. Really this is a persistent connection, so likely it should likely be named something like WebSocketConnection. The chat example hints at this, and maintains a list of "connections", which are instances of the subclass of MessageInbound. Since you have onTextMessage and onBinaryMessage methods from which to hang actual message processing, this rename would be consistent. 3) As mentioned, the chat example maintains a list of connections. Connections (MessageInbound instances) are added to this list when connections are established. However, they are never removed when the connection is closed, so the list grows. The broadcast method silently ignores the IOException presumably caused by writing to these connections. 4) I get what look like a timeout (and the connection closes) in case of inactivity in the chat example. However, I can't see a way to adjust this, or turn the behavior off. See previous comment about the non-removal from the list of connections. Previously, in comet, we dealt with things like this by doing an immediate reconnect from the javascript side of networking code, but it would be nice to have control over this during this time around the wheel. best regards MR
[Bug 53393] tomcat-connectors-1.2.37-src Crashing web server segmentation fault
https://issues.apache.org/bugzilla/show_bug.cgi?id=53393 --- Comment #5 from satyapal --- Created attachment 28960 --> https://issues.apache.org/bugzilla/attachment.cgi?id=28960&action=edit Output of starce Output of starce -- 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
[Bug 53393] tomcat-connectors-1.2.37-src Crashing web server segmentation fault
https://issues.apache.org/bugzilla/show_bug.cgi?id=53393 satyapal changed: What|Removed |Added OS|other |Linux --- Comment #6 from satyapal --- this is attached output of strace strace -p 7475 -f 2>&1 >/home/optimus/strace.out -- 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
