DO NOT REPLY [Bug 52899] JMXProxy Servlet MBeanDumper exposing non-properties causing exceptions/memory leak

[bugzilla]

https://issues.apache.org/bugzilla/show_bug.cgi?id=52899

--- Comment #3 from Mark Thomas  2012-03-16 07:59:53 UTC ---
Because in that version, all exceptions are silently swallowed.

-- 
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 52926] New: NPE in processSocket

[bugzilla]

https://issues.apache.org/bugzilla/show_bug.cgi?id=52926

 Bug #: 52926
   Summary: NPE in processSocket
   Product: Tomcat 7
   Version: 7.0.25
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: critical
  Priority: P2
 Component: Connectors
AssignedTo: dev@tomcat.apache.org
ReportedBy: mor...@ethlo.com
Classification: Unclassified


We have sporadic issues triggering 502 proxy errors using the NIO connector
behind Nginx, caused by dropped connections/end of streams in Tomcat. The
Tomcat log shows:

SEVERE: Error allocating socket processor
java.lang.NullPointerException 
at org.apache.tomcat.util.net.NioEndpoint.processSocket(NioEndpoint.java:721)
at
org.apache.tomcat.util.net.NioEndpoint$Poller.cancelledKey(NioEndpoint.java:1048)
at org.apache.tomcat.util.net.NioEndpoint$Poller.timeout(NioEndpoint.java:1392)
at org.apache.tomcat.util.net.NioEndpoint$Poller.run(NioEndpoint.java:1174)
at java.lang.Thread.run(Thread.java:662)

Looking at the code in processSocket I see the line in NioEndpoint(721): 
attachment.setCometNotify(false); //will get reset upon next reg

Attachment is fetched in line 720:
KeyAttachment attachment = (KeyAttachment)socket.getAttachment(false);

Looking at socket.getAttachement() method I see that this method is indeed
capable of returning null, but no null-check for this is done (although it is
in multiple other locations, so it seems inconsistent).

-- 
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] [Created] (MTOMCAT-128) The plugin ignores and/or parses web.xml incorrectally when using tomcatWebXml option

[Gilberto C Andrade (Created) (JIRA)]

The plugin ignores and/or parses web.xml incorrectally when using tomcatWebXml 
option
-

 Key: MTOMCAT-128
 URL: https://issues.apache.org/jira/browse/MTOMCAT-128
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat6, tomcat7
Affects Versions: 2.0-beta-1
 Environment: openSUSE 12.1 32Bits
Reporter: Gilberto C Andrade
Assignee: Olivier Lamy
Priority: Trivial
 Fix For: 2.0


In our project(jpa-spring-wicket) we need to filter the web.xml file, changing 
some placeholder and putting it (the web.xml) in 
${project.build.directory}/${project.build.finalName}/WEB-INF/web.xml.
Using tomcat6-maven-plugin it find the correct file, but fail when parsing it:

Caused by: java.lang.IllegalArgumentException: Duplicate context initialization 
parameter contextConfigLocation
at 
org.apache.catalina.core.StandardContext.addParameter(StandardContext.java:2661)
... 52 more
Mar 16, 2012 11:49:12 AM org.apache.catalina.startup.ContextConfig 
applicationWebConfig
SEVERE: Parse error in application web.xml file at 
jndi:/localhost/a2p/WEB-INF/web.xml
org.xml.sax.SAXParseException; systemId: jndi:/localhost/a2p/WEB-INF/web.xml; 
lineNumber: 15; columnNumber: 21; Error at (15, 21: Duplicate context 
initialization parameter contextConfigLocation
at 
org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2806)


Using tomcat7-maven-plugin it find the correct file, but ignores it so using 
the original file which contain the ${placeholder}. Thus not initializing the 
application:

INFO  - ContextLoader  - Root WebApplicationContext: initialization 
completed in 7808 ms
INFO  - WebXmlFile - web.xml: url mapping found for filter with 
name A2P: [/*]
Mar 16, 2012 12:08:16 PM org.apache.catalina.core.StandardContext filterStart
SEVERE: Exception starting filter A2P
java.lang.IllegalArgumentException: Invalid configuration type: 
'${wicket.MODE}'.  Must be "development" or "deployment".
at 
org.apache.wicket.protocol.http.WebApplication.getConfigurationType(WebApplication.java:670)
at org.apache.wicket.Application.configure(Application.java:297)
at 
org.apache.wicket.protocol.http.WebApplication.internalInit(WebApplication.java:613)
at org.apache.wicket.Application.initApplication(Application.java:806)
at 
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:346)
at 
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:286)
at 
org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:277)
at 
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:258)

 

The plugin configuration:

  
org.apache.tomcat.maven
tomcat7-maven-plugin
2.0-beta-1

${project.build.finalName}

${project.build.directory}/${project.build.finalName}/WEB-INF/web.xml




I have the jetty plugin setup as well and working, so I would try with tomcat 
but without success until now.
Regards

--
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: WebSockets in Tomcat 6

[Filip Hanik Mailing Lists]

- Original Message -
> From: "Costin Manolache" 

> 
> I haven't looked at the tomcat6/tomcat7 interfaces, but I think the
> current
> hook mechanism used by spdy could be ported with minimal risk and
> could be
> used by websockets.

Tomcat 7 may be a candidate. Tomcat 6, If I was an administrator, I would not 
expect any code changes like that in a dot release. 

> 
> All we need in both cases is for the request to stop being processed
> by the
> original protocol, and to have direct access to the socket. Than spdy
> can
> do its multiplexing and websocket can keep the socket alive and let
> the
> original request headers go away.

Yes, I'd like to see some real numbers on the request header overhead. I doubt 
it will be an issue for Tomcat 6. For Tomcat 7 large refactorings and 
optimzations are happening all the time, so in there it makes sense.

> 
> The hard part for spdy backporting is getting the SpdyProcessor -
> i.e. the
> virtual/multiplexed  request/response, not associated with a real
> socket. (
> which still requires lots of work on trunk, to get the rest of the
> features
> - comet, websocket-over-spdy, etc ). Not sure how hard it'll be to
> backport, but still it shouldn't be very risky.

As I just got back into the code mode of Tomcat, I'll look forward to take a 
look and see how it progresses.

Filip

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

DO NOT REPLY [Bug 52929] New: New release of mod_jk preventing chaining with mod_fcgid

[bugzilla]

https://issues.apache.org/bugzilla/show_bug.cgi?id=52929

 Bug #: 52929
   Summary: New release of mod_jk preventing chaining with
mod_fcgid
   Product: Tomcat Connectors
   Version: 1.2.33
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: normal
  Priority: P2
 Component: mod_jk
AssignedTo: dev@tomcat.apache.org
ReportedBy: a...@corelius.net
Classification: Unclassified


On brand new CentOS 5.7 64 bits, using Apache 2.2.3 RPM from CentOS and fcgid
RPM from the EPEL repository (httpd-2.2.3-63.el5.centos.1 and
mod_fcgid-2.2-11.el5).

Compiled and deployed mod_jk 1.2.33. 

All requests for fcgis started failing. The mod_jk logs look like:
[Fri Mar 16 13:26:58 2012][20863:47421889860416] [debug]
map_uri_to_worker_ext::jk_uri_worker_map.c (1119): Attempting to map URI
'/fcgi-test' from 2 maps
[Fri Mar 16 13:26:58 2012][20863:47421889860416] [debug]
find_match::jk_uri_worker_map.c (933): Attempting to map context URI
'/test/*=test' source 'uriworkermap'
[Fri Mar 16 13:26:58 2012][20863:47421889860416] [debug]
find_match::jk_uri_worker_map.c (933): Attempting to map context URI
'/test=test' source 'uriworkermap'

the requests were then passed on to the fcgi but every request led to the fcgi
core dumping.

Compiled and deployed mod_jk 1.2.32 and all fcgi requests succeeded.

Note: I have a number of other servers with mod_jk 1.2.32 and fcgid, all
working fine, I've attempted to upgrade one of the test servers to mod_jk
1.2.33 and got the same error there.

-- 
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] [Created] (MTOMCAT-129) Regression of MTOMCAT-54 in tomcat7-maven-plugin

[Justin Wunderle (Created) (JIRA)]

Regression of MTOMCAT-54 in tomcat7-maven-plugin


 Key: MTOMCAT-129
 URL: https://issues.apache.org/jira/browse/MTOMCAT-129
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat7
Affects Versions: 2.0-beta-1
Reporter: Justin Wunderle
Assignee: Olivier Lamy


In r1180428, the code that fixed MTOMCAT-54 was removed, so inside a webapp 
that is deployed at "/", request.getContextPath() will return "/" when it 
should return "".

The bug is that, in general, trailing slashes on the path variable should be 
removed (it's not really a special case for "/", though it causes the worst 
effects in that case)

See this link for the rules for how the contextPath should look: 
http://tomcat.apache.org/tomcat-7.0-doc/servletapi/javax/servlet/http/HttpServletRequest.html#getContextPath()

--
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-129) Regression of MTOMCAT-54 in tomcat7-maven-plugin

[Justin Wunderle (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231525#comment-13231525
 ] 

Justin Wunderle commented on MTOMCAT-129:
-

A workaround is to run maven with -Dmaven.tomcat.path="" and don't set  
to something else in the plugin's configuration ( is ok)

> Regression of MTOMCAT-54 in tomcat7-maven-plugin
> 
>
> Key: MTOMCAT-129
> URL: https://issues.apache.org/jira/browse/MTOMCAT-129
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0-beta-1
>Reporter: Justin Wunderle
>Assignee: Olivier Lamy
>
> In r1180428, the code that fixed MTOMCAT-54 was removed, so inside a webapp 
> that is deployed at "/", request.getContextPath() will return "/" when it 
> should return "".
> The bug is that, in general, trailing slashes on the path variable should be 
> removed (it's not really a special case for "/", though it causes the worst 
> effects in that case)
> See this link for the rules for how the contextPath should look: 
> http://tomcat.apache.org/tomcat-7.0-doc/servletapi/javax/servlet/http/HttpServletRequest.html#getContextPath()

--
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: r1301284 - in /tomcat/tc7.0.x/trunk: ./ webapps/docs/ webapps/examples/WEB-INF/ webapps/examples/WEB-INF/classes/websocket/ webapps/examples/WEB-INF/classes/websocket/chat/ webapps/exa

[Johno Crawford]

On 16/03/2012 12:57 AM, ma...@apache.org wrote:

Author: markt
Date: Thu Mar 15 23:57:00 2012
New Revision: 1301284


Looks like chat.html missed the changeset?



URL: http://svn.apache.org/viewvc?rev=1301284&view=rev
Log:
Implement chat example
Plus some minor clean-up.
Patch provided by Johno Crawford

Added:
 tomcat/tc7.0.x/trunk/webapps/examples/WEB-INF/classes/websocket/chat/
   - copied from r1301280, 
tomcat/trunk/webapps/examples/WEB-INF/classes/websocket/chat/
 tomcat/tc7.0.x/trunk/webapps/examples/WEB-INF/classes/websocket/echo/
   - copied from r1301280, 
tomcat/trunk/webapps/examples/WEB-INF/classes/websocket/echo/
Removed:
 
tomcat/tc7.0.x/trunk/webapps/examples/WEB-INF/classes/websocket/EchoMessage.java
 
tomcat/tc7.0.x/trunk/webapps/examples/WEB-INF/classes/websocket/EchoStream.java
Modified:
 tomcat/tc7.0.x/trunk/   (props changed)
 tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml
 
tomcat/tc7.0.x/trunk/webapps/examples/WEB-INF/classes/websocket/snake/Snake.java
 
tomcat/tc7.0.x/trunk/webapps/examples/WEB-INF/classes/websocket/snake/SnakeWebSocketServlet.java
 tomcat/tc7.0.x/trunk/webapps/examples/WEB-INF/web.xml
 tomcat/tc7.0.x/trunk/webapps/examples/websocket/echo.html
 tomcat/tc7.0.x/trunk/webapps/examples/websocket/index.html
 tomcat/tc7.0.x/trunk/webapps/examples/websocket/snake.html

Propchange: tomcat/tc7.0.x/trunk/
--
--- svn:mergeinfo (original)
+++ svn:mergeinfo Thu Mar 15 23:57:00 2012
@@ -1 +1 @@
-/tomcat/trunk:1156115-1157160,1157162-1157859,1157862-1157942,1157945-1160347,1160349-1163716,1163718-1166689,1166691-1174340,1174342-1175596,1175598-1175611,1175613-1175932,1175934-1177783,1177785-1177980,1178006-1180720,1180722-1183094,1183096-1187753,1187755,1187775,1187801,1187806,1187809,1187826-1188312,1188314-1188401,1188646-1188840,1188842-1190176,1190178-1195223,1195225-1195953,1195955,1195957-1201238,1201240-1203345,1203347-1206623,1206625-1208046,1208073,1208096,1208114,1208145,1208772,1209194-1212125,1212127-1220291,1220293,1220295-1221321,1221323-1222328,1222332-1222401,1222405-1222795,1222850-1222950,1222969-1225326,1225328-1225463,1225465,1225627,1225629-1226534,1226536-1228908,1228911-1228923,1228927-1229532,1229534-1230766,1230768-1231625,1231627-1233414,1233419-1235207,1235209-1237425,1237427,1237429-1237977,1237981,1237985,1237995,1238070,1238073,1239024-1239048,1239050-1239062,1239135,1239256,1239258-1239485,1239785-1240046,1240101,1240106,1240109,1240112
  
,1240114,1240116,1240118,1240121,1240329,1240474-1240850,1240857,1241087,1241160,1241408-1241822,1241908-1241909,1241912-1242110,1242371-1292130,1292134-1292458,1292464-1292670,1292672-1292776,1292780-1293392,1293397-1297017,1297019-1297963,1297965-1299820,1300111-1300460,1300520-1300948
+/tomcat/trunk:1156115-1157160,1157162-1157859,1157862-1157942,1157945-1160347,1160349-1163716,1163718-1166689,1166691-1174340,1174342-1175596,1175598-1175611,1175613-1175932,1175934-1177783,1177785-1177980,1178006-1180720,1180722-1183094,1183096-1187753,1187755,1187775,1187801,1187806,1187809,1187826-1188312,1188314-1188401,1188646-1188840,1188842-1190176,1190178-1195223,1195225-1195953,1195955,1195957-1201238,1201240-1203345,1203347-1206623,1206625-1208046,1208073,1208096,1208114,1208145,1208772,1209194-1212125,1212127-1220291,1220293,1220295-1221321,1221323-1222328,1222332-1222401,1222405-1222795,1222850-1222950,1222969-1225326,1225328-1225463,1225465,1225627,1225629-1226534,1226536-1228908,1228911-1228923,1228927-1229532,1229534-1230766,1230768-1231625,1231627-1233414,1233419-1235207,1235209-1237425,1237427,1237429-1237977,1237981,1237985,1237995,1238070,1238073,1239024-1239048,1239050-1239062,1239135,1239256,1239258-1239485,1239785-1240046,1240101,1240106,1240109,1240112
  
,1240114,1240116,1240118,1240121,1240329,1240474-1240850,1240857,1241087,1241160,1241408-1241822,1241908-1241909,1241912-1242110,1242371-1292130,1292134-1292458,1292464-1292670,1292672-1292776,1292780-1293392,1293397-1297017,1297019-1297963,1297965-1299820,1300111-1300460,1300520-1300948,1301280

Modified: tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml
URL: 
http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml?rev=1301284&r1=1301283&r2=1301284&view=diff
==
--- tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml (original)
+++ tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml Thu Mar 15 23:57:00 2012
@@ -100,6 +100,14 @@
  work with IBM as well as Oracle JVMs. Patch provided by Rohit 
Kelapure.
  (markt)

+
+Add support for the WebSocket protocol (RFC6455). Both streaming and
+message based APIs are provided and the implementation currently fully
+passes the Autobahn test suite. Also included are several examples.
+A significant contribution to this new functionality was provi

DO NOT REPLY [Bug 52921] mod_jk 1.2.33 crashes Apache 2.2 when accessing HTML, GIF, etc.

[bugzilla]

https://issues.apache.org/bugzilla/show_bug.cgi?id=52921

--- Comment #3 from Christopher Schultz  
2012-03-16 20:33:05 UTC ---
Confirmed on Debian Linux, Apache 2.2.16, mod_jk 1.2.33, using JkMounts and all
other settings that have been in place for years in working configuration.

Some specifics of my configuration:

DocumentRoot /var/www/...
Alias /context /path/to/my/context
JkMount /context/*.jsp workerX
JkMount /context/...

Accessing files in DocumentRoot works.
Making a request to /context/a.jsp cores every time.
Making a request to /context/a.css (not JkMounted) cores every time.
Accessing a file in DocumentRoot (again) works. At first, I thought this wasn't
working because I was getting connection-resets for everything, but I was not
able to reproduce it.

I'll re-build with -g and get a stack trace.

-- 
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 52921] mod_jk 1.2.33 crashes Apache 2.2 when accessing HTML, GIF, etc.

[bugzilla]

https://issues.apache.org/bugzilla/show_bug.cgi?id=52921

--- Comment #4 from Christopher Schultz  
2012-03-16 20:54:18 UTC ---
Debian isn't making my life easy. I did build with debugging symbols:

$ grep CFLAGS Makefile
APXSCFLAGS = -DLINUX=2 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_REENTRANT
-I/usr/include/apr-1.0 -I/usr/include/openssl -I/usr/include/xmltok -pthread  
-DHAVE_APR  -I/usr/include/apr-1.0 -I/usr/include/apr-1.0 -g -DHAVE_CONFIG_H
CFLAGS = -g -DHAVE_CONFIG_H

My old 1.2.23:
$ ls -l /usr/lib/apache2/modules/mod_jk-1.2.32.so 
-rwxr-xr-x 1 root root 483286 Dec  7 11:28
/usr/lib/apache2/modules/mod_jk-1.2.32.so
$ file /usr/lib/apache2/modules/mod_jk-1.2.32.so 
/usr/lib/apache2/modules/mod_jk-1.2.32.so: ELF 64-bit LSB shared object,
x86-64, version 1 (SYSV), dynamically linked, not stripped

My new 1.2.33:
$ file /usr/lib/apache2/modules/mod_jk-1.2.33.so 
/usr/lib/apache2/modules/mod_jk-1.2.33.so: ELF 64-bit LSB shared object,
x86-64, version 1 (SYSV), dynamically linked, not stripped
$ ls -l /usr/lib/apache2/modules/mod_jk-1.2.33.so 
-rwxr-xr-x 1 root root 769392 Mar 16 16:35
/usr/lib/apache2/modules/mod_jk-1.2.33.so

The new version is nearly twice the size as the older one: I suspect that
debugging symbols *have* been compiled-in.

Yet:

 gdb /usr/sbin/apache2 core
GNU gdb (GDB) 7.0.1-debian
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
...

warning: The current binary is a PIE (Position Independent Executable), which
GDB does NOT currently support.  Most debugger features will fail if used
in this session.

Reading symbols from /usr/sbin/apache2...(no debugging symbols found)...done.
[New Thread ]
[New Thread 8899]
[New Thread 8900]
[New Thread 8901]
[New Thread 8903]
[New Thread 8905]
[New Thread 8892]
[New Thread 8907]
[New Thread 8894]
[New Thread 8909]
[New Thread 8896]
[New Thread 8912]
[New Thread 8914]
[New Thread 8916]
[New Thread 8918]
[New Thread 8920]
[New Thread 8934]
[New Thread 8922]
[New Thread 8895]
[New Thread 8893]
[New Thread 8924]
[New Thread 8891]
[New Thread 8926]
[New Thread 8932]
[New Thread 8928]
[New Thread 8930]
Core was generated by `/usr/sbin/apache2 -k start'.
Program terminated with signal 11, Segmentation fault.
#0  0x7f63638f56aa in ?? ()
(gdb) where
#0  0x7f63638f56aa in ?? ()
#1  0x0030 in ?? ()
#2  0x7f63657a6c61 in ?? ()
#3  0x7f636954cbc0 in ?? ()
#4  0x7f6369982a30 in ?? ()
#5  0x in ?? ()
(gdb) 

I guess this means that since httpd doesn't have debugging symbols, we can't
see anything. Also, it's using DSOs, so those probably don't get loaded by gdb
anyway. I'll see what I can do.

More environment information:
$ uname -a
Linux dev.chadis.com 2.6.32-312-ec2 #24-Ubuntu SMP Fri Jan 7 18:30:50 UTC 2011
x86_64 GNU/Linux


$ /usr/sbin/apache2 -V
Server version: Apache/2.2.16 (Debian)
Server built:   Feb  5 2012 21:35:44
Server's Module Magic Number: 20051115:24
Server loaded:  APR 1.4.2, APR-Util 1.3.9
Compiled using: APR 1.4.2, APR-Util 1.3.9
Architecture:   64-bit
Server MPM: Worker
  threaded: yes (fixed thread count)
forked: yes (variable process count)
Server compiled with
 -D APACHE_MPM_DIR="server/mpm/worker"
 -D APR_HAS_SENDFILE
 -D APR_HAS_MMAP
 -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
 -D APR_USE_SYSVSEM_SERIALIZE
 -D APR_USE_PTHREAD_SERIALIZE
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D APR_HAS_OTHER_CHILD
 -D AP_HAVE_RELIABLE_PIPED_LOGS
 -D DYNAMIC_MODULE_LIMIT=128
 -D HTTPD_ROOT="/etc/apache2"
 -D SUEXEC_BIN="/usr/lib/apache2/suexec"
 -D DEFAULT_PIDLOG="/var/run/apache2.pid"
 -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
 -D DEFAULT_ERRORLOG="logs/error_log"
 -D AP_TYPES_CONFIG_FILE="mime.types"
 -D SERVER_CONFIG_FILE="apache2.conf"

-- 
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 52930] New: java.lang.OutOfMemoryError: GC overhead limit exceeded

[bugzilla]

https://issues.apache.org/bugzilla/show_bug.cgi?id=52930

 Bug #: 52930
   Summary: java.lang.OutOfMemoryError: GC overhead limit exceeded
   Product: Tomcat 6
   Version: 6.0.20
  Platform: PC
OS/Version: Windows XP
Status: NEW
  Severity: normal
  Priority: P2
 Component: Catalina
AssignedTo: dev@tomcat.apache.org
ReportedBy: eraja...@rediffmail.com
Classification: Unclassified


Start up parameter:
Mar xx, 2012 2:18:57 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the java.library.path:
/appl/BMC/java/jdk1.6.0_29/jre/lib/amd64/server:/appl/BMC/java/jdk1.6.0_29/jre/lib/amd64:/appl/BMC/java/jdk1.6.0_29/jre/../lib/amd64:/appl/BMC/ARSystem/midtier/WEB-INF/lib:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
Mar xx, 2012 2:18:57 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Mar xx, 2012 2:18:57 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in xx75 ms
Mar xx, 2012 2:18:57 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Mar xx, 2012 2:18:57 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.20
- Root WebApplicationContext: initialization started
- Refreshing
org.springframework.web.context.support.XmlWebApplicationContext@xx8497f6:
display name [Root WebApplicationContext]; startup date [Fri Mar xx 14:19:11
NZDT 2012]; root of context hierarchy
- Loading XML bean definitions from class path resource
[META-INF/applicationContext.xml]
- Bean factory for application context
[org.springframework.web.context.support.XmlWebApplicationContext@xx8497f6]:
org.springframework.beans.factory.support.DefaultListableBeanFactory@4f2d26d2
- Pre-instantiating singletons in
org.springframework.beans.factory.support.DefaultListableBeanFactory@4f2d26d2:
defining beans
[proxyTemplate,configuration,formCache,fieldmapCache,formfieldCache,goatfieldMapCache,activelinkCache,fieldgraphCache,htmlDataCache,jsDataCache,arUserPreferencesCache,arUserSearchesCache,skinDefCache,skinsCache,IFormServiceCacheAspect,IFormFieldServiceCacheAspect,IFieldMapServiceCacheAspect,IGoatFieldMapServiceCacheAspect,IActiveLinkServiceCacheAspect,IFieldGraphServiceCacheAspect,IDHTMLServiceCacheAspect,IARUserPreferencesServiceCacheAspect,IARUserSearchesServiceCacheAspect,ISkinServiceCacheAspect,ControlFieldAspect,TrimFieldAspect,PanelFieldAspect,VertNavBarAspect,ViewInfoAspect,formService,fieldMapService,formFieldService,goatfieldFactory,goatfieldMapService,goatfieldService,emitterFactory,fieldgraphService,skinService,activelinkService,arUserPreferencesService,arUserSearchesService,dhtmlService,dhtmlRequestService,flexRequestService,com.remedy.arsys.goat.Form#0,com.remedy.arsys.goat.Form#1,com.remedy.arsys.goat.field.GoatField#0,com.remedy.arsys.goat.field.FieldGraph#0,com.remedy
 
.arsys.goat.ActiveLink#0,com.remedy.arsys.stubs.GoatServlet#0,com.remedy.arsys.stubs.GoatServlet#1];
root of factory hierarchy
- Trying to load configuration arsys_api.xml
- Could not load optional configuration arsys_api.xml
- Trying to load configuration default.xml
- jrpcMode: true
- jniLoadMode: 1
- apiRecordingMode: 0
- useConnectionPooling: true
- maxProxiesPerServer: 80
- idleConnectionsPerServer: 5
- connectionTimeout: 0
- connectionLifespan: 0
- timeUnit: MINUTES
- minimumSupportedServerRpcVersion: 12
- connectionMaxRetries: 1
- timeLagBetweenRetriesMillSec: 100
- stringizeFieldAssignments: false
- stringizeSetIfQualification: false
- useLegacyQualParser: false
- useLegacyAssignParser: false
- useLegacyQualFormatter: false
- useLegacyAssignFormatter: false
- UsePooling: true
- , Pool setting info: , # maxProxyPerServer- 80, # idleConnectionsPerServer-
5, connectionTimeout setting- 00:00:00, connectionLifespan setting- 00:00:00
- Currently, connection pooling true
- Client adjusts connection variables maximumPoolSize = 80 minIdleProxySize = 5
connectionTimeout = 0 timeUnit = null
- Client sets useConnectionPooling to : true
- Client set connectionLifespan = 24 timeUnit = null
- Root WebApplicationContext: initialization completed in 8619 ms
- Currently, connection pooling true
- Client sets connection limits per server to :80
- UsePooling: true
- , Pool setting info: , # maxProxyPerServer- 80, # idleConnectionsPerServer-
5, connectionTimeout setting- 00:00:00, connectionLifespan setting- 00:04:00
- Client sets useConnectionPooling to : true
- APITIMEOUT from system property : null
- APITIMEOUT from Environment : null
- AROVERLAYGROUPS from system property : null
- AROVERLAYGROUPS from Environment : null
- fipsProviderJsafeJCE installed = false
- set timer period 24 milliSec (00:04:00)


Java settings
java versi

DO NOT REPLY [Bug 52930] java.lang.OutOfMemoryError: GC overhead limit exceeded

[bugzilla]

https://issues.apache.org/bugzilla/show_bug.cgi?id=52930

--- Comment #1 from Raja  2012-03-16 22:40:04 UTC ---
Created attachment 28482
  --> https://issues.apache.org/bugzilla/attachment.cgi?id=28482
GC overhead exception

java.lang.OutOfMemoryError: GC overhead limit exceeded

-- 
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 52930] java.lang.OutOfMemoryError: GC overhead limit exceeded

[bugzilla]

https://issues.apache.org/bugzilla/show_bug.cgi?id=52930

Raja  changed:

   What|Removed |Added

   Platform|PC  |Other
 OS/Version|Windows XP  |Linux
   Severity|normal  |major

-- 
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 52930] java.lang.OutOfMemoryError: GC overhead limit exceeded

[bugzilla]

https://issues.apache.org/bugzilla/show_bug.cgi?id=52930

Chuck Caldarale  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID

--- Comment #2 from Chuck Caldarale  2012-03-16 
22:52:05 UTC ---
Bugzilla is not a support forum.  Post your issue on the Tomcat users mailing
list if you need help with your situation.

-- 
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 52931] New: When using TLDs for Tag Files and specifying the JSP version, EL is ignored by default and cannot be overriden with isELIgnored

[bugzilla]

https://issues.apache.org/bugzilla/show_bug.cgi?id=52931

 Bug #: 52931
   Summary: When using TLDs for Tag Files and specifying the JSP
version, EL is ignored by default and cannot be
overriden with isELIgnored
   Product: Tomcat 7
   Version: 7.0.26
  Platform: All
OS/Version: All
Status: NEW
  Severity: normal
  Priority: P2
 Component: Jasper
AssignedTo: dev@tomcat.apache.org
ReportedBy: thiagocdua...@yahoo.com.br
Classification: Unclassified


This is happening because org.apache.jasper.compiler.Compiler calls (in line
157) the method TagLibraryInfo.getRequiredVersion(), that returns the value of
the attribute "jspversion" from the TLD. What should be compared here is the
value of the attribute "tlib-version", but the class TagLibraryInfo doesn't
even has a method to return it.

Note that this error happens only with Tag Files.

-- 
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: r1301823 - in /tomcat/maven-plugin/trunk/common-tomcat-maven-plugin: ./ src/test/ src/test/java/ src/test/java/org/ src/test/java/org/apache/ src/test/java/org/apache/tomcat/ src/test/java

[olamy]

Author: olamy
Date: Fri Mar 16 23:35:00 2012
New Revision: 1301823

URL: http://svn.apache.org/viewvc?rev=1301823&view=rev
Log:
add an upload file unit test

Added:
tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/
tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/java/
tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/java/org/

tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/java/org/apache/

tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/java/org/apache/tomcat/

tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/java/org/apache/tomcat/maven/

tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/java/org/apache/tomcat/maven/common/

tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/java/org/apache/tomcat/maven/common/TomcatManagerTest.java
   (with props)
tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/resources/

tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/resources/test.txt
   (with props)
Modified:
tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/pom.xml

Modified: tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/pom.xml
URL: 
http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/pom.xml?rev=1301823&r1=1301822&r2=1301823&view=diff
==
--- tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/pom.xml (original)
+++ tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/pom.xml Fri Mar 16 
23:35:00 2012
@@ -77,6 +77,27 @@
 
 
 
+  org.apache.tomcat.embed
+  tomcat-embed-core
+  test
+
+
+  org.apache.tomcat
+  tomcat-juli
+  test
+
+
+  org.apache.tomcat.embed
+  tomcat-embed-logging-juli
+  test
+
+
+  org.apache.tomcat
+  tomcat-servlet-api
+  test
+
+
+
   org.codehaus.plexus
   plexus-component-annotations
   1.5.5
@@ -109,6 +130,15 @@
   
 
   
+  
+org.apache.maven.plugins
+maven-surefire-plugin
+
+  
+${basedir}
+  
+
+  
 
 
   

Added: 
tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/java/org/apache/tomcat/maven/common/TomcatManagerTest.java
URL: 
http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/java/org/apache/tomcat/maven/common/TomcatManagerTest.java?rev=1301823&view=auto
==
--- 
tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/java/org/apache/tomcat/maven/common/TomcatManagerTest.java
 (added)
+++ 
tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/java/org/apache/tomcat/maven/common/TomcatManagerTest.java
 Fri Mar 16 23:35:00 2012
@@ -0,0 +1,141 @@
+package org.apache.tomcat.maven.common;
+/*
+ * 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 junit.framework.TestCase;
+import org.apache.catalina.Context;
+import org.apache.catalina.startup.Tomcat;
+import org.apache.commons.io.IOUtils;
+import org.apache.tomcat.maven.common.deployer.TomcatManager;
+
+import javax.servlet.ServletException;
+import javax.servlet.http.HttpServlet;
+import javax.servlet.http.HttpServletRequest;
+import javax.servlet.http.HttpServletResponse;
+import java.io.File;
+import java.io.FileInputStream;
+import java.io.FileOutputStream;
+import java.io.IOException;
+import java.io.StringWriter;
+import java.net.URL;
+import java.util.ArrayList;
+import java.util.List;
+
+/**
+ * @author Olivier Lamy
+ */
+public class TomcatManagerTest
+extends TestCase
+{
+
+Tomcat tomcat;
+
+UploadServlet uploadServlet;
+
+int port;
+
+public static String getBasedir()
+{
+return System.getProperty( "basedir" );
+}
+
+@Override
+protected void setUp()
+throws Exception
+{
+super.setUp();
+tomcat = new Tomcat();
+tomcat.setBaseDir( System.getProperty( "java.io.tmpdir" ) );
+tomcat.setPort( 0 );
+
+Context context = tomcat.addContext( "", System.getProperty

svn commit: r1301824 - in /tomcat/maven-plugin/trunk: common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/deployer/ common-tomcat-maven-plugin/src/test/java/org/apache/tomcat/maven

[olamy]

Author: olamy
Date: Fri Mar 16 23:35:32 2012
New Revision: 1301824

URL: http://svn.apache.org/viewvc?rev=1301824&view=rev
Log:
[MTOMCAT-116] handle redirect response when deploying a war

Modified:

tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/deployer/TomcatManager.java

tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/java/org/apache/tomcat/maven/common/TomcatManagerTest.java

tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/resources/test.txt

tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractDeployWarMojo.java

tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/AbstractDeployWarMojo.java

Modified: 
tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/deployer/TomcatManager.java
URL: 
http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/deployer/TomcatManager.java?rev=1301824&r1=1301823&r2=1301824&view=diff
==
--- 
tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/deployer/TomcatManager.java
 (original)
+++ 
tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/deployer/TomcatManager.java
 Fri Mar 16 23:35:32 2012
@@ -22,8 +22,10 @@ package org.apache.tomcat.maven.common.d
 import org.apache.commons.codec.binary.Base64;
 import org.apache.commons.io.IOUtils;
 import org.apache.commons.lang.StringUtils;
+import org.apache.http.Header;
 import org.apache.http.HttpHost;
 import org.apache.http.HttpResponse;
+import org.apache.http.HttpStatus;
 import org.apache.http.auth.AuthScope;
 import org.apache.http.auth.Credentials;
 import org.apache.http.auth.UsernamePasswordCredentials;
@@ -36,10 +38,11 @@ import org.apache.http.entity.AbstractHt
 import org.apache.http.impl.auth.BasicScheme;
 import org.apache.http.impl.client.BasicAuthCache;
 import org.apache.http.impl.client.DefaultHttpClient;
-import org.apache.http.impl.conn.BasicClientConnectionManager;
+import org.apache.http.impl.conn.PoolingClientConnectionManager;
 import org.apache.http.protocol.BasicHttpContext;
-import org.apache.maven.plugin.logging.Log;
 
+import java.io.File;
+import java.io.FileInputStream;
 import java.io.IOException;
 import java.io.InputStream;
 import java.io.OutputStream;
@@ -162,7 +165,9 @@ public class TomcatManager
 this.password = password;
 this.charset = charset;
 
-this.httpClient = new DefaultHttpClient( new 
BasicClientConnectionManager() );
+PoolingClientConnectionManager poolingClientConnectionManager = new 
PoolingClientConnectionManager();
+poolingClientConnectionManager.setMaxTotal( 5 );
+this.httpClient = new DefaultHttpClient( 
poolingClientConnectionManager );
 if ( StringUtils.isNotEmpty( username ) && StringUtils.isNotEmpty( 
password ) )
 {
 Credentials creds = new UsernamePasswordCredentials( username, 
password );
@@ -305,7 +310,7 @@ public class TomcatManager
  * @throws TomcatManagerException if the Tomcat manager request fails
  * @throws IOExceptionif an i/o error occurs
  */
-public TomcatManagerResponse deploy( String path, InputStream war )
+public TomcatManagerResponse deploy( String path, File war )
 throws TomcatManagerException, IOException
 {
 return deploy( path, war, false );
@@ -322,7 +327,7 @@ public class TomcatManager
  * @throws TomcatManagerException if the Tomcat manager request fails
  * @throws IOExceptionif an i/o error occurs
  */
-public TomcatManagerResponse deploy( String path, InputStream war, boolean 
update )
+public TomcatManagerResponse deploy( String path, File war, boolean update 
)
 throws TomcatManagerException, IOException
 {
 return deploy( path, war, update, null );
@@ -340,7 +345,7 @@ public class TomcatManager
  * @throws TomcatManagerException if the Tomcat manager request fails
  * @throws IOExceptionif an i/o error occurs
  */
-public TomcatManagerResponse deploy( String path, InputStream war, boolean 
update, String tag )
+public TomcatManagerResponse deploy( String path, File war, boolean 
update, String tag )
 throws TomcatManagerException, IOException
 {
 return deployImpl( path, null, null, war, update, tag );
@@ -357,7 +362,7 @@ public class TomcatManager
  * @throws IOException
  * @since 2.0
  */
-public TomcatManagerResponse deploy( String path, InputStream war, boolean 
update, String tag, long length )
+public TomcatManagerResponse deploy( String path, File war, boolean 
update, String tag, long length )
   

[jira] [Updated] (MTOMCAT-129) Regression of MTOMCAT-54 in tomcat7-maven-plugin

[Olivier Lamy (Updated) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MTOMCAT-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy updated MTOMCAT-129:
-

Fix Version/s: 2.0

> Regression of MTOMCAT-54 in tomcat7-maven-plugin
> 
>
> Key: MTOMCAT-129
> URL: https://issues.apache.org/jira/browse/MTOMCAT-129
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0-beta-1
>Reporter: Justin Wunderle
>Assignee: Olivier Lamy
> Fix For: 2.0
>
>
> In r1180428, the code that fixed MTOMCAT-54 was removed, so inside a webapp 
> that is deployed at "/", request.getContextPath() will return "/" when it 
> should return "".
> The bug is that, in general, trailing slashes on the path variable should be 
> removed (it's not really a special case for "/", though it causes the worst 
> effects in that case)
> See this link for the rules for how the contextPath should look: 
> http://tomcat.apache.org/tomcat-7.0-doc/servletapi/javax/servlet/http/HttpServletRequest.html#getContextPath()

--
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-116) NonRepeatableRequestException when executing goal tomcat6:deploy

[Olivier Lamy (Closed) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MTOMCAT-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy closed MTOMCAT-116.


   Resolution: Fixed
Fix Version/s: 2.0

fixed and 2.0-SNAPSHOT deployed 
If you could test and confirm the fix works fine in your env that could be 
lovely :-)
Thanks!

> NonRepeatableRequestException when executing goal tomcat6:deploy
> 
>
> Key: MTOMCAT-116
> URL: https://issues.apache.org/jira/browse/MTOMCAT-116
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat6
>Affects Versions: 2.0-beta-1
> Environment: Client: Windows 7/Eclipse Indigo/Java 5/m2eclipse 
> (embedded mvn 3.0.2/1.0.100.20110804-1717)
> Server: Windows 2003 Server/Tomcat 6.0.32/Java 6/
>Reporter: Michael Yockey
>Assignee: Olivier Lamy
> Fix For: 2.0
>
>
> Deployment to Tomcat fails after war upload. The war file does not appear on 
> the server but the maven log marks the upload progess to completion. The 
> application is not successfully deployed. Here is the relevant stack trace 
> from the Maven debugging output:
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.tomcat.maven:tomcat6-maven-plugin:2.0-SNAPSHOT:deploy 
> (default-cli) on project web-integration: Cannot invoke Tomcat manager
>   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:319)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
>   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:592)
>   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: Cannot invoke 
> Tomcat manager
>   at 
> org.apache.tomcat.maven.plugin.tomcat6.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:152)
>   at 
> org.apache.tomcat.maven.plugin.tomcat6.AbstractWarCatalinaMojo.execute(AbstractWarCatalinaMojo.java:71)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>   ... 19 more
> Caused by: org.apache.http.client.ClientProtocolException
>   at 
> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:926)
>   at 
> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:822)
>   at 
> org.apache.tomcat.maven.common.deployer.TomcatManager.invoke(TomcatManager.java:718)
>   at 
> org.apache.tomcat.maven.common.deployer.TomcatManager.deployImpl(TomcatManager.java:681)
>   at 
> org.apache.tomcat.maven.common.deployer.TomcatManager.deploy(TomcatManager.java:363)
>   at 
> org.apache.tomcat.maven.plugin.tomcat6.AbstractDeployWarMojo.deployWar(AbstractDeployWarMojo.java:87)
>   at 
> org.apache.tomcat.maven.plugin.tomcat6.AbstractDeployMojo.invokeManager(AbstractDeployMojo.java:86)
>   at 
> org.apache.tomcat.maven.plugin.tomcat6.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:143)
>   ... 22 more
> Caused by: org.apache.http.client.NonRepeatableRequestException: Cannot retry 
> request with a non-repeatable request entity.
>   at 
> org.apache.http.impl.client.DefaultRequestDirector.tryExecute(D

DO NOT REPLY [Bug 52921] mod_jk 1.2.33 crashes Apache 2.2 when accessing HTML, GIF, etc.

[bugzilla]

https://issues.apache.org/bugzilla/show_bug.cgi?id=52921

--- Comment #5 from Konstantin Kolinko  2012-03-16 
23:41:19 UTC ---
Reviewing diff of current native/apache-2.0/mod_jk.c against r1142157 (aka
1.2.32 tag)

That is:
[1]
http://svn.apache.org/viewvc/tomcat/jk/trunk/native/apache-2.0/mod_jk.c?r1=1240904&r2=1142157&diff_format=h


The request-specific configuration structure was changed from (rule_extension_t
*) to new structure (jk_request_conf_t *). That was done in r1187906


Looking at the hook methods in mod_jk.c that access jk_request_conf_t:

1. jk_translate 

  Does palloc of new instance unconditionally

2. jk_map_to_storage

  Checks for NULL and conditionally does palloc of new instance.

3. request_log_transaction

  Checks for NULL and returns DECLINED if it is null

4. jk_handler
  and init_ws_service (supplementary method called from jk_handler)

  Access the structure without checking it for NULL.
  Those are lines @r1293818:
805, 807; 2575, 2577; 2603, 2605; 2625, 2627

I think that jk_handler method should get the jk_request_conf_t instance once
somewhere near the top of the method and check it for being NULL.
There are 3 possible ways to react if it is NULL:

  a) return DECLINED,
  b) palloc a new instance like jk_map_to_storage does.
  c) skip the code that accesses the structure

+jk_request_conf_t *rconf = ap_get_module_config(r->request_config,
&jk_module);
+if (rconf == NULL) {
+jk_request_conf_t *rconf = apr_palloc(r->pool,
sizeof(jk_request_conf_t));
+rconf->jk_handled = JK_FALSE;
+rconf->rule_extensions = NULL;
+ap_set_module_config(r->request_config, &jk_module, rconf);
+}
+

-- 
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] [Updated] (MTOMCAT-124) tomcat-maven-archetype unused generation parameters

[Olivier Lamy (Updated) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MTOMCAT-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy updated MTOMCAT-124:
-

Fix Version/s: 2.0
 Assignee: Olivier Lamy

> tomcat-maven-archetype unused generation parameters
> ---
>
> Key: MTOMCAT-124
> URL: https://issues.apache.org/jira/browse/MTOMCAT-124
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Improvement
>Affects Versions: 2.0-beta-1
>Reporter: patrick garcia
>Assignee: Olivier Lamy
>Priority: Trivial
>  Labels: archetype, maven, tomcat
> Fix For: 2.0
>
> Attachments: MTOMCAT-124-tomcat-maven-archetype.patch
>
>
> I found several problems on the superb and very useful 
> "tomcat-maven-archetype"
> The improvement I propos are the followings:
> 1/
> "groupId" and "version" can have default values but should be prompt for user 
> value the same way as for "version" of 
> "org.apache.maven.archetypes:maven-archetype-quickstart:1.1"
> "org.apache.maven.archetypes:maven-archetype-quickstart:1.1" proposes a 
> default "version" and prompt the user for modification at the same time. 
> Pressing enter validate the default value.
> 2/
> Following variables are not in used:
>   artifactId-api
>   artifactId-api-impl
>   artifactId-webapp
>   artifactId-webapp-exec
>   artifactId-webapp-it
> This variables should impact the "mvn archetype:generate" behaviour
> 3/
> I propos to change the default values of :
>   artifactId-api = ${artifactId}-api
>   artifactId-api-impl = ${artifactId}-api-impl
>   artifactId-webapp = ${artifactId}-webapp
>   artifactId-webapp-exec = ${artifactId}-webapp-exec
>   artifactId-webapp-it = ${artifactId}-webapp-it
> 4/
> rootArtifactId cat be renamed as artifactId with no default value
> I will propos patches for this later. I, first, have to understand 
> "archetype" framework.

--
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-121) Plugin gets 403 unauthorized errors after upgrading from SNAPSHOT

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231737#comment-13231737
 ] 

Olivier Lamy commented on MTOMCAT-121:
--

any logs ?

> Plugin gets 403 unauthorized errors after upgrading from SNAPSHOT
> -
>
> Key: MTOMCAT-121
> URL: https://issues.apache.org/jira/browse/MTOMCAT-121
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat6
>Affects Versions: 2.0-beta-1
> Environment: pache Maven 3.0.3 (r1075438; 2011-02-28 17:31:09+)
> Maven home: /usr/share/maven
> Java version: 1.6.0_29, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.7.3", arch: "x86_64", family: "mac"
> Tomcat: 6.0.35
>Reporter: Eamonn Linehan
>Assignee: Olivier Lamy
>
> I updated from 2.0-SNAPSHOT to 2.0-beta-1 and stopped being able to deploy 
> war files to tomcat. No changes were made to tomcat. The tomcat manager 
> application is configured to allow access using username 'admin' and no 
> password. The plugin configuration is:
> 
>   org.apache.tomcat.maven
>   tomcat6-maven-plugin
>   2.0-beta-1 
>   
>   /
>   
> ${project.build.directory}/${project.build.finalName}.war
>   
>   true
>   both
>   Britebill
>   
> ${project.build.directory}/${project.build.finalName}/META-INF/context.xml
>   
>   

--
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-119) tomcat7:run-war fails because it expects META-INF\context.xml

[Olivier Lamy (Updated) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MTOMCAT-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy updated MTOMCAT-119:
-

Fix Version/s: 2.0

> tomcat7:run-war fails because it expects META-INF\context.xml
> -
>
> Key: MTOMCAT-119
> URL: https://issues.apache.org/jira/browse/MTOMCAT-119
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0-beta-1
>Reporter: Samuel Langlois
>Assignee: Olivier Lamy
> Fix For: 2.0
>
>
> run-war and run-war-only goals fail on tomcat7 plugin, looking for the file 
> =META-INF\context.xml=
> How to reproduce:
> * Use the archetype to create a project
> mvn archetype:generate -DarchetypeGroupId=org.apache.tomcat.maven 
> -DarchetypeArtifactId=tomcat-maven-archetype -DarchetypeVersion=2.0-beta-1
> * Build it
> * cd basic-webapp
> * mvn org.apache.tomcat.maven:tomcat6-maven-plugin:run-war
> => works fine
> * mvn org.apache.tomcat.maven:tomcat7-maven-plugin:run
> => works fine
> * mvn org.apache.tomcat.maven:tomcat7-maven-plugin:run-war
> -> kaboom
> {code}
> [INFO] --- tomcat7-maven-plugin:2.0-beta-1:run-war (default-cli) @ 
> basic-webapp ---
> [INFO] Running war on http://localhost:9090/
> [INFO] Using existing Tomcat server configuration at 
> C:\Users\SAMUEL~1.LAN\AppData\Local\Temp\com.antelink.toto\basic-webapp\target\tomcat
> févr. 16, 2012 6:56:24 PM org.apache.coyote.AbstractProtocol init
> Infos: Initializing ProtocolHandler ["http-bio-9090"]
> févr. 16, 2012 6:56:24 PM org.apache.catalina.core.StandardService 
> startInternal
> Infos: Starting service Tomcat
> févr. 16, 2012 6:56:24 PM org.apache.catalina.core.StandardEngine 
> startInternal
> Infos: Starting Servlet Engine: Apache Tomcat/7.0.25
> févr. 16, 2012 6:56:24 PM org.apache.catalina.startup.ContextConfig 
> processContextConfig
> Grave: Missing context.xml: 
> file:/C:/Users/SAMUEL~1.LAN/AppData/Local/Temp/com.antelink.toto/basic-webapp/target/basic-webapp-1.0-SNAPSHOT/META-INF/context.xml
> java.io.FileNotFoundException: 
> C:\Users\SAMUEL~1.LAN\AppData\Local\Temp\com.antelink.toto\basic-webapp\target\basic-webapp-1.0-SNAPSHOT\META-INF\context.xml
>  (Le fichier spécifié est introuvable)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at java.io.FileInputStream.(FileInputStream.java:97)
> at 
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
> at 
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
> at java.net.URL.openStream(URL.java:1035)
> at 
> org.apache.catalina.startup.ContextConfig.processContextConfig(ContextConfig.java:565)
> at 
> org.apache.catalina.startup.ContextConfig.contextConfig(ContextConfig.java:546)
> at 
> org.apache.catalina.startup.ContextConfig.init(ContextConfig.java:784)
> at 
> org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:318)
> at 
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
> at 
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
> at 
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:401)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:110)
> at 
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
> {code}

--
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 52931] When using TLDs for Tag Files and specifying the JSP version, EL is ignored by default and cannot be overriden with isELIgnored

[bugzilla]

https://issues.apache.org/bugzilla/show_bug.cgi?id=52931

--- Comment #1 from Konstantin Kolinko  2012-03-17 
00:31:51 UTC ---
Can you provide small sample web application that demonstrates the issue?

>From your short description I do not understand what problem you are facing.
What problem the fix solves and how to reproduce it?

-- 
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-116) NonRepeatableRequestException when executing goal tomcat6:deploy

[Hudson (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231769#comment-13231769
 ] 

Hudson commented on MTOMCAT-116:


Integrated in TomcatMavenPlugin-mvn3.x #118 (See 
[https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/118/])
[MTOMCAT-116] handle redirect response when deploying a war (Revision 
1301824)

 Result = SUCCESS
olamy : http://svn.apache.org/viewvc/?view=rev&rev=1301824
Files : 
* 
/tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/deployer/TomcatManager.java
* 
/tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/java/org/apache/tomcat/maven/common/TomcatManagerTest.java
* 
/tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/test/resources/test.txt
* 
/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractDeployWarMojo.java
* 
/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/AbstractDeployWarMojo.java


> NonRepeatableRequestException when executing goal tomcat6:deploy
> 
>
> Key: MTOMCAT-116
> URL: https://issues.apache.org/jira/browse/MTOMCAT-116
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat6
>Affects Versions: 2.0-beta-1
> Environment: Client: Windows 7/Eclipse Indigo/Java 5/m2eclipse 
> (embedded mvn 3.0.2/1.0.100.20110804-1717)
> Server: Windows 2003 Server/Tomcat 6.0.32/Java 6/
>Reporter: Michael Yockey
>Assignee: Olivier Lamy
> Fix For: 2.0
>
>
> Deployment to Tomcat fails after war upload. The war file does not appear on 
> the server but the maven log marks the upload progess to completion. The 
> application is not successfully deployed. Here is the relevant stack trace 
> from the Maven debugging output:
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.tomcat.maven:tomcat6-maven-plugin:2.0-SNAPSHOT:deploy 
> (default-cli) on project web-integration: Cannot invoke Tomcat manager
>   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:319)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
>   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:592)
>   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: Cannot invoke 
> Tomcat manager
>   at 
> org.apache.tomcat.maven.plugin.tomcat6.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:152)
>   at 
> org.apache.tomcat.maven.plugin.tomcat6.AbstractWarCatalinaMojo.execute(AbstractWarCatalinaMojo.java:71)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>   ... 19 more
> Caused by: org.apache.http.client.ClientProtocolException
>   at 
> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:926)
>   at 
> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:822)
>   at 
> org.apache.tomcat.maven.common.deployer.TomcatManager.invoke(TomcatManager.java:718)
>