ApacheCon slides with .odp extension

2017-06-15 Thread Huxing Zhang
Hi

I have noticed that some of the ApacheCon slides are in .odp format:

http://people.apache.org/~schultz/ApacheCon%20NA%202017/Seamless%20Upgrades%20for%20Credential%20Security%20in%20Apache%20Tomcat.odp
http://people.apache.org/~schultz/ApacheCon%20NA%202017/Let's%20Encrypt%20Apache%20Tomcat.odp

The .odp format does not work for me because it is for OpenOffice (I don't have 
OpenOffice installed on my Mac OS), and neither Pages and Microsoft PowerPoint 
could open it.

I am wondering that should it be convert it to a more universal format like 
pdf, so that more people can open it without any confusion.

Thanks,
Huxing

[jira] [Commented] (MTOMCAT-234) Tomcat8 Maven Plugin

2017-06-15 Thread Alan Czajkowski (JIRA)

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

Alan Czajkowski commented on MTOMCAT-234:
-

I am a big fan of this plugin and I am very eager to get this working for 
Tomcat 8.5 and I am willing to contribute time to make it happen. Is this 
project still alive?

> Tomcat8 Maven Plugin
> 
>
> Key: MTOMCAT-234
> URL: https://issues.apache.org/jira/browse/MTOMCAT-234
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 2.0, 2.1, 2.2
> Environment: Maven 3.1, Tomcat8.0RC1, Oracle JDK7u25
>Reporter: Petr Novak
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Blocker
> Fix For: 3.0
>
>
> Please provide initial version of Tomcat8 Maven Plugin. 
> I tried the recommendations in 
> http://tomcat.10.x6.nabble.com/Tomcat-8-Tomcat-Maven-Plugin-2-2-Tomcat8-Maven-Plugin-td4995858.html#none
> but the guideline 
> http://tomcat.apache.org/maven-plugin-trunk/tomcat7-maven-plugin/adjust-embedded-tomcat-version.html
> does not work for Tomcat8 .
> The problem is in changed Tomcat 8 API, the maven throws folloving exception:
>  at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:142)
>  ... 20 more
> by: java.lang.NoSuchMethodError: 
> org.apache.catalina.startup.Tomcat.setDefaultRealm(Lorg/apache/catalina/Realm;)V
>  at 
> org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.startContainer(AbstractRunMojo.java:999)
>  at 
> org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.execute(AbstractRunMojo.java:514)
>  at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
>  ... 20 more
>  The method setDefaultRealm is deprecated in Tomcat7 and was removed in 
> Tomcat8 as described in documentation:
> http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/startup/Tomcat.html#setDefaultRealm(org.apache.catalina.Realm)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[GUMP@vmgump-vm3]: Project tomcat-trunk-test-apr (in module tomcat-trunk) failed

2017-06-15 Thread Bill Barker
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at gene...@gump.apache.org.

Project tomcat-trunk-test-apr has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 62 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- tomcat-trunk-test-apr :  Tomcat 9.x, a web server implementing the Java 
Servlet 4.0,
...


Full details are available at:
http://vmgump-vm3.apache.org/tomcat-trunk/tomcat-trunk-test-apr/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on commons-daemon exists, no need to add for property 
commons-daemon.native.src.tgz.
 -DEBUG- Dependency on commons-daemon exists, no need to add for property 
tomcat-native.tar.gz.
 -INFO- Failed with reason build failed
 -INFO- Project Reports in: 
/srv/gump/public/workspace/tomcat-trunk/output/logs-APR
 -INFO- Project Reports in: 
/srv/gump/public/workspace/tomcat-trunk/output/test-tmp-APR/logs
 -WARNING- No directory 
[/srv/gump/public/workspace/tomcat-trunk/output/test-tmp-APR/logs]



The following work was performed:
http://vmgump-vm3.apache.org/tomcat-trunk/tomcat-trunk-test-apr/gump_work/build_tomcat-trunk_tomcat-trunk-test-apr.html
Work Name: build_tomcat-trunk_tomcat-trunk-test-apr (Type: Build)
Work ended in a state of : Failed
Elapsed: 17 mins 15 secs
Command Line: /usr/lib/jvm/java-8-oracle/bin/java -Djava.awt.headless=true 
-Dbuild.sysclasspath=only org.apache.tools.ant.Main 
-Dgump.merge=/srv/gump/public/gump/work/merge.xml 
-Dbase.path=/srv/gump/public/workspace/tomcat-trunk/tomcat-build-libs 
-Dtest.temp=output/test-tmp-APR 
-Djunit.jar=/srv/gump/public/workspace/junit/target/junit-4.13-SNAPSHOT.jar 
-Dtest.accesslog=true 
-Dobjenesis.jar=/srv/gump/public/workspace/objenesis/main/target/objenesis-2.6-SNAPSHOT.jar
 -Dexamples.sources.skip=true 
-Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-20170616.jar
 
-Dtest.openssl.path=/srv/gump/public/workspace/openssl-master/dest-20170616/bin/openssl
 -Dexecute.test.nio=false 
-Dhamcrest.jar=/srv/gump/packages/hamcrest/hamcrest-core-1.3.jar 
-Dexecute.test.apr=true -Dexecute.test.nio2=false 
-Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-20170616-native-src.tar.gz
 -Dtest.reports=output/logs-APR -Dtomc
 
at-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-20170616-native-src.tar.gz
 -Djdt.jar=/srv/gump/packages/eclipse/plugins/R-4.5-201506032000/ecj-4.5.jar 
-Dtest.apr.loc=/srv/gump/public/workspace/tomcat-native-trunk/dest-20170616/lib 
-Dtest.relaxTiming=true -Dtest.excludePerformance=true 
-Djava.net.preferIPv4Stack=/srv/gump/public/workspace/tomcat-trunk/true 
-Deasymock.jar=/srv/gump/public/workspace/easymock/core/target/easymock-3.5-SNAPSHOT.jar
 -Dcglib.jar=/srv/gump/packages/cglib/cglib-nodep-2.2.jar test 
[Working Directory: /srv/gump/public/workspace/tomcat-trunk]
CLASSPATH: 
/usr/lib/jvm/java-8-oracle/lib/tools.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-trunk/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit4.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/servlet-api.ja
 

[Bug 61180] Change log level of sessionIdGeneratorBase.createRandom to warn rather than info

2017-06-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61180

--- Comment #3 from Coty Sutherland  ---
Taking another look at the code around the info message I think we may need to
add another check to see if the delay time is larger than 100 ms. If we make
this a warning message as-is I think that everyone's log may have a warning in
it. Should we print an info message if the delay is less than some number (like
30 seconds) and a warning if the delay is greater?

-- 
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 61180] Change log level of sessionIdGeneratorBase.createRandom to warn rather than info

2017-06-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61180

--- Comment #2 from Piotr Chlebda  ---
Hi,
I'm newby as a tomcat contributor and I'd like to take this issue.

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



[GitHub] tomcat pull request #64: Fix Bug 61180

2017-06-15 Thread pchlebda
GitHub user pchlebda opened a pull request:

https://github.com/apache/tomcat/pull/64

Fix Bug 61180

Hi,
I'm newby and this is my first tomcat contribution.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/pchlebda/tomcat trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/tomcat/pull/64.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #64


commit 6e636cac58a943e35d06e75e5b0c41a8da9feabf
Author: pchlebda 
Date:   2017-06-15T20:49:22Z

Fix Bug 61180




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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



[Bug 61191] CGIServlet puts too much of the path in the SCRIPT_NAME environment variable

2017-06-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61191

Mark Thomas  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Mark Thomas  ---
PATH_INFO refers to path segments in the URI that appear after the script. For
example:

/cgi-bin/printenv.pl/this/is/the/path/info

The SCRIPT_NAME provided by Tomcat correctly excludes this.

-- 
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 61191] New: CGIServlet puts too much of the path in the SCRIPT_NAME environment variable

2017-06-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61191

Bug ID: 61191
   Summary: CGIServlet puts too much of the path in the
SCRIPT_NAME environment variable
   Product: Tomcat 9
   Version: 9.0.0.M21
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P2
 Component: Catalina
  Assignee: dev@tomcat.apache.org
  Reporter: jan0mich...@yahoo.com
  Target Milestone: -

The environment variable SCRIPT_NAME should be

/cgi-bin/printenv.pl

but is

/var/www/foo/bar/cgi-bin/printenv.pl

See http://www.ietf.org/rfc/rfc3875:
"No PATH_INFO segment (see section 4.1.5) is included in the SCRIPT_NAME
value."

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



Semantic Versioning

2017-06-15 Thread Igal @ Lucee.org

Hi everyone,

I have recently realized that Tomcat does not follow Semantic 
Versioning, and even minor upgrades can break existing setups.


Most users today expect Semantic Versioning, which specifies the 
following (from [1]):


Given a version number MAJOR.MINOR.PATCH, increment the:

1. MAJOR version when you make incompatible API changes,
2. MINOR version when you add functionality in a backwards-compatible
   manner, and
3. PATCH version when you make backwards-compatible bug fixes.

Additional labels for pre-release and build metadata are available as 
extensions to the MAJOR.MINOR.PATCH format.


I think that it's important to adopt such a policy, so that minor 
updates are easier to do, e.g. updating only the /lib directory without 
worrying about the /bin or other directories.


[1] http://semver.org/

Thank you,

Igal Sapir
Lucee Core Developer
Lucee.org 



[Bug 61189] New: CGIServlet should be able to set specific environment variables

2017-06-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61189

Bug ID: 61189
   Summary: CGIServlet should be able to set specific environment
variables
   Product: Tomcat 9
   Version: 9.0.0.M21
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P2
 Component: Catalina
  Assignee: dev@tomcat.apache.org
  Reporter: jan0mich...@yahoo.com
  Target Milestone: -

org.apache.catalina.servlets.CGIServlet has a param 'passShellEnvironment'.
It would give more flexibility to allow for different environment variables per
CGI.

Examples:

- set HOME and HTTP_HOME to the nextcloud directory
- set SQWEBMAIL_MAXMSGSIZE for sqwebmail


For the sqwebmail example this could look for example like

  
 EnvironmentVariables

SQWEBMAIL_MAXARGSIZE=2000|SQWEBMAIL_MAXATTSIZE=2000|SQWEBMAIL_MAXMSGSIZE=2000
  

I wrote my own CGI executor servlet for sqwebmail.
And today I need environment variables for Nextcloud.

I don't like to put them in /etc/init.d/tomcat or catalina.sh, because they may
be lost after a Tomcat update.

-- 
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 61187] Problem with tomcat 7.0.52 version

2017-06-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61187

Mark Thomas  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #4 from Mark Thomas  ---
There is not enough information in this report to enable the problem to be
replicated for investigation.

As previously suggested, please test with the latest stable release and if you
still experience problems please follow up on the users mailing list.

If the mailing list discussion concludes that there is a Tomcat bug, feel free
to re-open this issue. You'll need to provide the information that demonstrates
that there is a bug. For example, a test case that demonstrates it, code
analysis that shows there is a problem etc.

-- 
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 61187] Problem with tomcat 7.0.52 version

2017-06-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61187

--- Comment #3 from mgrigorov  ---
Please consult with the changelog to see what changes there are since .52.
Please try 7.0.78!
7.0.52 cannot be fixed! Any fixes will go in 7.0.79+.

-- 
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 61187] Problem with tomcat 7.0.52 version

2017-06-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61187

--- Comment #2 from Dillesh  ---
(In reply to mgrigorov from comment #1)
> Comment on attachment 35057 [details]
> Please find the attached screenshot for more details
> 
> Please update to latest 7.x and try test again. It might have been fixed
> since .52.

Hi Team,
Thank you for your quick response. So this issue is existed with 7.0.52
version.
And please let us know what are the issues existed in 7.0.52 version.

Thank you in advance.

Thanks
Dillesh

-- 
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 61187] Problem with tomcat 7.0.52 version

2017-06-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61187

--- Comment #1 from mgrigorov  ---
Comment on attachment 35057
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=35057
Please find the attached screenshot for more details

Please update to latest 7.x and try test again. It might have been fixed since
.52.

-- 
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 61187] New: Problem with tomcat 7.0.52 version

2017-06-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61187

Bug ID: 61187
   Summary: Problem with tomcat 7.0.52 version
   Product: Tomcat 7
   Version: 7.0.52
  Hardware: Other
OS: Linux
Status: NEW
  Severity: major
  Priority: P2
 Component: Catalina
  Assignee: dev@tomcat.apache.org
  Reporter: dillus...@gmail.com
  Target Milestone: ---

Created attachment 35057
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=35057=edit
Please find the attached screenshot for more details

Hi Team,
We are using following tomcat version Apache Tomcat/7.0.52   Server number: 
7.0.52.0 and currently we are facing a problem with this one.
We have an issue with connection pool. Actually we are using specific
connections but some how all the connections are utilized. If any new request
come then it is unable to fetch a connection because pool is empty. But in real
case there is no chance of using that much of connections parallel
So as per our analysis following are our observations.
We are using max idle connections are 30 , but if we do the operations and
calculate the connections using Jconsle then IDLE connections are more than 30.
Please find attached screenshot for your reference.
And Please let us know is there any solution for this issue.

Thank you in advance.

Thanks
Dillesh

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