Re: Multiple Class Loaders

[Rallavagu]

Chris,

Thanks for the response. As I have mentioned, there are bugs in 
application code that prevents WebAppClassLoader from GC collection. 
Wondering what happens when two instances are running one is pinned due 
to application bugs and one newly deployed. For instance, would the 
pinned instance be active?


On 4/4/16 8:03 PM, Christopher Schultz wrote:

Rallavagu,

On 4/4/16 8:13 PM, Rallavagu wrote:

Tomcat 7.0.47, JDK 7

When an app is hot deployed in-place by simply copying the .war file
into webapps directory, the old webappclassloader is not cleared
completely because of inefficient context shutdown from the app. In this
case, two instances of WebAppClassLoader are running for the same
context root (at least appears that way from heap dump). Wondering what
would be the expected behavior if there is any? I understand that this
is the problem with deployment and application that is written but
wondering how would Tomcat behave in this case.


Tomcat behaves correctly.

Your web application must have code in itself or one of its dependent
libraries which pins the context's ClassLoader in memory.

Have a look at
https://home.apache.org/~markt/presentations/2010-08-05-Memory-Leaks-JavaOne-60mins.pdf
for information about ClassLoader-pinning leaks, how to find them, and
how to fix them.

-chris

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



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

Re: Multiple Class Loaders

[Christopher Schultz]

Rallavagu,

On 4/4/16 8:13 PM, Rallavagu wrote:
> Tomcat 7.0.47, JDK 7
> 
> When an app is hot deployed in-place by simply copying the .war file
> into webapps directory, the old webappclassloader is not cleared
> completely because of inefficient context shutdown from the app. In this
> case, two instances of WebAppClassLoader are running for the same
> context root (at least appears that way from heap dump). Wondering what
> would be the expected behavior if there is any? I understand that this
> is the problem with deployment and application that is written but
> wondering how would Tomcat behave in this case.

Tomcat behaves correctly.

Your web application must have code in itself or one of its dependent
libraries which pins the context's ClassLoader in memory.

Have a look at
https://home.apache.org/~markt/presentations/2010-08-05-Memory-Leaks-JavaOne-60mins.pdf
for information about ClassLoader-pinning leaks, how to find them, and
how to fix them.

-chris

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

Re: Apache Tomcat 9.0.0-M4 and http/2 on Mac OS X 10.11.4

[Christopher Schultz]

Tobias,

On 4/4/16 4:49 AM, Tobias Soloschenko wrote:
> I just figured out that this issue might depend on the file names of APR
> 1.5.2 - if I create links in the lib folder that reflects the names of
> 1.4.8 - tomcat throws an exception that the version of APR can not be
> resolved:
> 
> ln -s libapr-1.0.dylib libtcnative-1.0.dylib
> 
> ln -s libapr-1.a libtcnative-1.a
> 
> ln -s libapr-1.dylib libtcnative-1.dylib
> 
> ln -s libapr-1.la libtcnative-1.la
> 
> 
> Exception:
> 
> 04-Apr-2016 10:42:39.579 WARNING [main]
> org.apache.catalina.core.AprLifecycleListener.init The APR based Apache
> Tomcat Native library failed to load. The error reported was
> [org.apache.tomcat.jni.Library.version(I)I]

That wasn't going to work.

APR and tcnative are different libraries. Copying one to the other is
about as useful as trying to load your /etc/passwd file as a shared library.

When you set JAVA_OPTS:

> "export
> JAVA_OPTS=-Djava.library.path=/usr/local/Cellar/apr/1.5.2/libexec/lib"
> 
> but Tomcat can not find it at this location.

How did you start Tomcat after that? What files are in
.../1.5.2/libexec/lib? What is in your "TCNATIVE_PRIV_INCLUDES"
directory? Where do you configure that for loading into Tomcat?

-chris

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

Re: Information about incident ID 2205106170494020972

[John D. Ament]

Is it at all possible that you have some network level security that's
blocking your access to this port?

On Mon, Apr 4, 2016 at 10:03 PM Yin, Ivan  wrote:

> Hi,
>
> I am sure this error message doesn't come from that webapp since there is
> no "incident ID" in the webapp.
> In addition, I searched this error in google and I found a lot of similar
> error messages coming from different webapps deployed on tomcat so I
> thought it might come from Tomcat.
>
> The original error is:
>
> This page can't be displayed. Contact support for additional information.
> The incident ID is: N/A.
>
> I found the following message in http trace:
>
> This page can't be displayed. Contact support for additional information.
> The incident ID is: 2205106170494020972.
>
> May I know if there is a concept called "incident ID" in tomcat?
>
> Regards,
> Ivan
>
> -邮件原件-
> 发件人: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
> 发送时间: 2016年4月5日 9:38
> 收件人: Tomcat Users List 
> 主题: RE: Information about incident ID 2205106170494020972
>
> > From: Yin, Ivan [mailto:ivan@sap.com]
> > Subject: Information about incident ID 2205106170494020972
>
> > When I tried to click one button in the web application deployed in
> Tomcat 7, it throws
> > an error message as below:
>
> > This page can't be displayed. Contact support for additional information.
> > The incident ID is: 2205106170494020972.
>
> > May I know what is the meaning of this incident ID and how I can solve
> this issue?
>
> The message does not come from Tomcat itself, but most likely a webapp
> deployed under Tomcat.  As the message says, you'll need to contact the
> support personnel for the webapp.
>
>  - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you
> received this in error, please contact the sender and delete the e-mail and
> its attachments from all computers.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

答复: Information about incident ID 2205106170494020972

[Yin, Ivan]

Hi,

I am sure this error message doesn't come from that webapp since there is no 
"incident ID" in the webapp.
In addition, I searched this error in google and I found a lot of similar error 
messages coming from different webapps deployed on tomcat so I thought it might 
come from Tomcat.

The original error is:

This page can't be displayed. Contact support for additional information.
The incident ID is: N/A.

I found the following message in http trace:

This page can't be displayed. Contact support for additional information.
The incident ID is: 2205106170494020972.

May I know if there is a concept called "incident ID" in tomcat?

Regards,
Ivan

-邮件原件-
发件人: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] 
发送时间: 2016年4月5日 9:38
收件人: Tomcat Users List 
主题: RE: Information about incident ID 2205106170494020972

> From: Yin, Ivan [mailto:ivan@sap.com] 
> Subject: Information about incident ID 2205106170494020972

> When I tried to click one button in the web application deployed in Tomcat 7, 
> it throws 
> an error message as below:

> This page can't be displayed. Contact support for additional information.
> The incident ID is: 2205106170494020972.

> May I know what is the meaning of this incident ID and how I can solve this 
> issue?

The message does not come from Tomcat itself, but most likely a webapp deployed 
under Tomcat.  As the message says, you'll need to contact the support 
personnel for the webapp.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


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

RE: Information about incident ID 2205106170494020972

[Caldarale, Charles R]

> From: Yin, Ivan [mailto:ivan@sap.com] 
> Subject: Information about incident ID 2205106170494020972

> When I tried to click one button in the web application deployed in Tomcat 7, 
> it throws 
> an error message as below:

> This page can't be displayed. Contact support for additional information.
> The incident ID is: 2205106170494020972.

> May I know what is the meaning of this incident ID and how I can solve this 
> issue?

The message does not come from Tomcat itself, but most likely a webapp deployed 
under Tomcat.  As the message says, you'll need to contact the support 
personnel for the webapp.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


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

Information about incident ID 2205106170494020972

[Yin, Ivan]

Hi  experts,

When I tried to click one button in the web application deployed in Tomcat 7, 
it throws an error message as below:

This page can't be displayed. Contact support for additional information.
The incident ID is: 2205106170494020972.

May I know what is the meaning of this incident ID and how I can solve this 
issue?

Thanks in advance.

Regards,
Ivan

Multiple Class Loaders

[Rallavagu]

Tomcat 7.0.47, JDK 7

When an app is hot deployed in-place by simply copying the .war file 
into webapps directory, the old webappclassloader is not cleared 
completely because of inefficient context shutdown from the app. In this 
case, two instances of WebAppClassLoader are running for the same 
context root (at least appears that way from heap dump). Wondering what 
would be the expected behavior if there is any? I understand that this 
is the problem with deployment and application that is written but 
wondering how would Tomcat behave in this case.


Thanks

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

Tomcat 8.5 documentation question

[Thad Humphries]

In docs/config/http.xml, lines #1430 and #1648 use "certificateValidation".
However when I go to "#SSL_Support_-_SSLHostConfig" I find the attribute
"certificateVerification", *not *"certificate*Validation*".  I think one or
the other is an error (and I think "certificateVerification" is the correct
attribute based on the "certificateVerificationDepth" attribute name).

-- 
"Hell hath no limits, nor is circumscrib'd In one self-place; but where we
are is hell, And where hell is, there must we ever be" --Christopher
Marlowe, *Doctor Faustus* (v. 121-24)

Tomcat 9.0.0M4 (and trunk) issue with Websockets (bug?)

[Francesco Bassi]

Hello everybody.

Tomcat 9 has a different behaviour than Tomcat 8, during the management of
MessageHandler.onMessage:

- in Tomcat 8:
  Thread.currentThread().getContextClassLoader() returns an instance of
org.apache.catalina.loader.WebappClassLoader

- in Tomcat 9
  Thread.currentThread().getContextClassLoader() returns an instance of
java.net.URLClassLoader
  (which doesn't resolve the WEB-INF/lib/* classes)

It seems to be related to the switch to ParallelWebappClassLoader.
Is it a bug or and intended behaviour?

Thanks,

--fb

Re: Tomcat does not log exceptions thrown by the valve chain

[Violeta Georgieva]

Hi,

2016-04-01 16:28 GMT+03:00 Svetlin Zarev :
>
> Hello,
>
>
>
> I have a custom authenticator valve which failed with an exception  that
> never got logged by tomcat.
>
> After a little bit of digging in tomcat’s source it turned out that there
> is no valve responsible for logging
>
> exceptions thrown by valves later in the chain. The closest error handling
> mechanism to what I’m looking
>
> for, is StandardHostValve’s try-catch around the valve chain, which
> unfortunately logs the exceptions
>
> only if someone has called setError() on the  response.  To be more clear
–
> StandardHostValve either
>
> sets the RequestDispatcher.ERROR_EXCEPTION or logs the exception.
>
>
>
> That logic was introduced with the fix for
> https://bz.apache.org/bugzilla/show_bug.cgi?id=54123 with
>
> (git) commit id: *cf4fae533cb303c97031b68ec652d6624207df21 *
>
> And was later modified a bit with the fix for
> https://bz.apache.org/bugzilla/show_bug.cgi?id=57252 with
>
> (git) commit id: *9807122abe9b95e1766d992314e661d9f9ed3634 *
>
>
>
> What do you think about always logging the caught throwable  (the rest of
> the logic remains unchanged) ?
>

Thanks for the report and the patch.
The fix will be available from 9.0.0.M5, 8.5.1, 8.0.34 and 7.0.69 onwards.

Regards,
Violeta

>
>
> diff --git a/java/org/apache/catalina/core/StandardHostValve.java
> b/java/org/apache/catalina/core/StandardHostValve.java
>
> index 48683f5..17f2dc5 100644
>
> --- a/java/org/apache/catalina/core/StandardHostValve.java
>
> +++ b/java/org/apache/catalina/core/StandardHostValve.java
>
> @@ -176,13 +176,12 @@ final class StandardHostValve extends ValveBase {
>
>  }
>
>  } catch (Throwable t) {
>
>  ExceptionUtils.handleThrowable(t);
>
> +container.getLogger().error("Exception Processing " +
>
> +request.getRequestURI(), t);
>
> +
>
>  // If a new error occurred while trying to report a
> previous
>
> -// error simply log the new error and allow the original
> error
>
> -// to be reported.
>
> -if (response.isErrorReportRequired()) {
>
> -container.getLogger().error("Exception Processing " +
>
> -request.getRequestURI(), t);
>
> -} else {
>
> +// error allow the original error to be reported.
>
> +if (!response.isErrorReportRequired()) {
>
>
 request.setAttribute(RequestDispatcher.ERROR_EXCEPTION,
> t);
>
>  throwable(request, response, t);
>
>  }
>
>
>
> Best regards,
>
> Svetlin

Re: Apache Tomcat 9.0.0-M4 and http/2 on Mac OS X 10.11.4

[Tobias Soloschenko]

Hi,

I just figured out that this issue might depend on the file names of APR
1.5.2 - if I create links in the lib folder that reflects the names of
1.4.8 - tomcat throws an exception that the version of APR can not be
resolved:

ln -s libapr-1.0.dylib libtcnative-1.0.dylib

ln -s libapr-1.a libtcnative-1.a

ln -s libapr-1.dylib libtcnative-1.dylib

ln -s libapr-1.la libtcnative-1.la


Exception:

04-Apr-2016 10:42:39.579 WARNING [main]
org.apache.catalina.core.AprLifecycleListener.init The APR based Apache
Tomcat Native library failed to load. The error reported was
[org.apache.tomcat.jni.Library.version(I)I]

 java.lang.UnsatisfiedLinkError: org.apache.tomcat.jni.Library.version(I)I

at org.apache.tomcat.jni.Library.version(Native Method)

at org.apache.tomcat.jni.Library.initialize(Library.java:181)

at
org.apache.catalina.core.AprLifecycleListener.init(AprLifecycleListener.java:198)

at
org.apache.catalina.core.AprLifecycleListener.isAprAvailable(AprLifecycleListener.java:107)

at org.apache.catalina.connector.Connector.setProtocol(Connector.java:587)

at org.apache.catalina.connector.Connector.(Connector.java:70)

at
org.apache.catalina.startup.ConnectorCreateRule.begin(ConnectorCreateRule.java:64)

at org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1188)

at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:509)

at
com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:182)

at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1344)

at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2787)

at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)

at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)

at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)

at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)

at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)

at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)

at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643)

at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1461)

at org.apache.catalina.startup.Catalina.load(Catalina.java:578)

at org.apache.catalina.startup.Catalina.load(Catalina.java:629)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:497)

at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:311)

at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:494)


kind regards

Tobias


2016-04-03 12:17 GMT+02:00 Mark Thomas :

> On 3 April 2016 04:29:40 BST, Tobias Soloschenko <
> tobiassolosche...@googlemail.com> wrote:
> >Hi,
> >
> >I am trying to get http/2 working on Mac OS X 10.11.4 - these are the
> >steps I used:
> >
> >1. Install Brew: http://brew.sh/
> >
> >2. Download Apache Tomcat 9 https://tomcat.apache.org/download-90.cgi
> >
> >3. Download Xcode command line tools by opening the terminal and
> >execute “xcode-select  —install”
> >
> >4. Download Xcode from the AppStore
> >
> >5. Create a symlink for the xctoolchain:
> >
> >sudo ln -s
>
> >/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain
> >/Applications/Xcode.app/Contents/Developer/Toolchains/OSX10.11.xctoolchain
> >
> >6. Install APR and OPENSSL with “brew install openssl” and “brew
> >install apr”
> >
> >7. Install tomcat native by extracting bin/tomcat-native.tar.gz and run
> >“./configure --with-ssl=/usr/local/Cellar/openssl/1.0.2g
> >--prefix=/Applications/apache-tomcat-9.0.0.M4
> >--with-apr=/usr/local/Cellar/apr/1.5.2 && make && make install” in
> >tomcat-native-1.2.5-src/native - see
> >
> >https://tomcat.apache.org/tomcat-9.0-doc/apr.html
>
>
> Do this one step at a time and check the results - particularly for
> configure. The start up messages suggest the wrong APR version was picked
> up and no OpenSSL version was found.
>
> Mark
>
>
> >8. export JAVA_OPTS=-Djava.library.path=/usr/local/apr/lib
> >
> >9. Create pem files in conf folder:
> >
> >/usr/local/Cellar/openssl/1.0.2g/bin/openssl genrsa -des3 -out
> >localhost-rsa-key 1024
> >
> >/usr/local/Cellar/openssl/1.0.2g/bin/openssl genrsa -out localhost-key
> >1024
> >
> >/usr/local/Cellar/openssl/1.0.2g/bin/openssl rsa -in localhost-rsa-key
> >-out localhost-key
> >
> 

Re: Exception Both the UrlPattern and value attribute were set for the WebServlet annotation on class ...

[Violeta Georgieva]

Hi,

2016-04-04 9:53 GMT+03:00 basilk :
>
> Hi.
>
> I try to start tomcat 8.0.33 in debug mode under Eclipse Mars.2.
> I get the following errors:
>
> SEVERE: A child container failed during start
> java.util.concurrent.ExecutionException:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/isogdquery]]
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:916)
> at
org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:871)
> at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
> at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
> at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.catalina.LifecycleException: Failed to start
component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/isogdquery]]
> at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:153)
> ... 6 more
> Caused by: java.lang.IllegalArgumentException: Both the UrlPattern and
value attribute were set for the WebServlet annotation on class
[test.org.apache.catalina.startup.DuplicateMappingParamFilter]
> at
org.apache.catalina.startup.ContextConfig.processAnnotationWebFilter(ContextConfig.java:2426)
> at
org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2057)
> at
org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:1940)
> at
org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:1934)
> at
org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:1934)
> at
org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:1934)
> at
org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:1934)
> at
org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:1934)
> at
org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1147)
> at
org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:779)
> at
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:306)
> at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:95)
> at
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
> at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5150)
> at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
> ... 6 more

This exception means that the filter with
class test.org.apache.catalina.startup.DuplicateMappingParamFilter has
wrong annotation i.e. the @WebFilter annotation is used with both "value"
and "urlPatterns" which is wrong.
If this filter is the one from Tomcat tests sources it is stated clearly in
the javadoc that this class is used for testing wrong annotations.

About the message itself, it needs some rewording because the problem is
not with @WebServlet but with @WebFilter.
I'll fix that.

Regards,
Violeta


> When i start tomcat as service in Windows everything is ok.
>
> What seems to be a problem?
>
> Thank you.
>
> Basil.
>
>
>
> ---
> Это сообщение проверено на вирусы антивирусом Avast.
> https://www.avast.com/antivirus

Tomcat Maven Plugin release?

[Magnus Skoglund]

I have found that the current release 2.2 is not working for me, and there
are two issues that have been fixed in trunk development, that fixes the
problems I encounter. I have built the trunk version (2.3-SNAPSHOT) plugin
locally, and that works fine for me.

I prefer not to use SNAPSHOT, and I would not like to do a local fork of
the project.

Has anyone knowledge of the upcoming release plan for the Tomcat Maven
Plugin project?

Re: Apache Tomcat 9.0.0-M4 and http/2 on Mac OS X 10.11.4

[Tobias Soloschenko]

One thing I made wrong was

"export JAVA_OPTS=-Djava.library.path=/usr/local/apr/lib" which is 1.4.8

the path to the new version installed with brew is

"export
JAVA_OPTS=-Djava.library.path=/usr/local/Cellar/apr/1.5.2/libexec/lib"

but Tomcat can not find it at this location.

I also tried to download APR 1.5.2 and install it by myself:

./configure.sh --prefix="/usr/local/apr_1.5.2"
make
make test
make install

but even if I use this folder in the library path Tomcat can't detect it:

"export JAVA_OPTS=-Djava.library.path=/usr/local/apr_1.5.2/lib"

Any idea what's the problem?

kind regards

Tobias



2016-04-03 12:17 GMT+02:00 Mark Thomas :

> On 3 April 2016 04:29:40 BST, Tobias Soloschenko <
> tobiassolosche...@googlemail.com> wrote:
> >Hi,
> >
> >I am trying to get http/2 working on Mac OS X 10.11.4 - these are the
> >steps I used:
> >
> >1. Install Brew: http://brew.sh/
> >
> >2. Download Apache Tomcat 9 https://tomcat.apache.org/download-90.cgi
> >
> >3. Download Xcode command line tools by opening the terminal and
> >execute “xcode-select  —install”
> >
> >4. Download Xcode from the AppStore
> >
> >5. Create a symlink for the xctoolchain:
> >
> >sudo ln -s
>
> >/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain
> >/Applications/Xcode.app/Contents/Developer/Toolchains/OSX10.11.xctoolchain
> >
> >6. Install APR and OPENSSL with “brew install openssl” and “brew
> >install apr”
> >
> >7. Install tomcat native by extracting bin/tomcat-native.tar.gz and run
> >“./configure --with-ssl=/usr/local/Cellar/openssl/1.0.2g
> >--prefix=/Applications/apache-tomcat-9.0.0.M4
> >--with-apr=/usr/local/Cellar/apr/1.5.2 && make && make install” in
> >tomcat-native-1.2.5-src/native - see
> >
> >https://tomcat.apache.org/tomcat-9.0-doc/apr.html
>
>
> Do this one step at a time and check the results - particularly for
> configure. The start up messages suggest the wrong APR version was picked
> up and no OpenSSL version was found.
>
> Mark
>
>
> >8. export JAVA_OPTS=-Djava.library.path=/usr/local/apr/lib
> >
> >9. Create pem files in conf folder:
> >
> >/usr/local/Cellar/openssl/1.0.2g/bin/openssl genrsa -des3 -out
> >localhost-rsa-key 1024
> >
> >/usr/local/Cellar/openssl/1.0.2g/bin/openssl genrsa -out localhost-key
> >1024
> >
> >/usr/local/Cellar/openssl/1.0.2g/bin/openssl rsa -in localhost-rsa-key
> >-out localhost-key
> >
> >/usr/local/Cellar/openssl/1.0.2g/bin/openssl req -new -key
> >localhost-key -out localhost-csr
> >
> >/usr/local/Cellar/openssl/1.0.2g/bin/openssl x509 -req -days 365 -in
> >localhost-csr -signkey localhost-key -out localhost-crt
> >
> >cat localhost-key localhost-crt > localhost-rsa-cert.pem
> >
> >cat localhost-rsa-cert.pem > localhost-rsa-chain.pem
> >
> >cat localhost-rsa-key > localhost-rsa-key.pem
> >
> >10. Uncomment the http/2 connector in the server.xml
> >
> >
> >
> >I am currently facing those issues (out of the log):
> >
> >
> >
> >02-Apr-2016 09:15:13.415 INFO [main]
> >org.apache.catalina.startup.VersionLoggerListener.log Command line
> >argument: -Djava.io.tmpdir=/Applications/apache-tomcat-9.0.0.M4/temp
> >
> >02-Apr-2016 09:15:13.415 INFO [main]
> >org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR
> >based Apache Tomcat Native library 1.2.5 using APR version 1.4.8.
> >
> >02-Apr-2016 09:15:13.415 INFO [main]
> >org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR
> >capabilities: IPv6 [true], sendfile [true], accept filters [false],
> >random [true].
> >
> >02-Apr-2016 09:15:13.418 SEVERE [main]
> >org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Failed to
> >initialize the SSLEngine.
> >
> >org.apache.tomcat.jni.Error: 70023: This function has not been
> >implemented on this platform
> >
> >at org.apache.tomcat.jni.SSL.initialize(Native Method)
> >
> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >
> >at
>
> >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> >
> >at
>
> >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >
> >at java.lang.reflect.Method.invoke(Method.java:497)
> >
> >at
>
> >org.apache.catalina.core.AprLifecycleListener.initializeSSL(AprLifecycleListener.java:284)
> >
> >at
>
> >org.apache.catalina.core.AprLifecycleListener.lifecycleEvent(AprLifecycleListener.java:136)
> >
> >at
>
> >org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
> >
> >at
>
> >org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:401)
> >
> >at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:104)
> >
> >at org.apache.catalina.startup.Catalina.load(Catalina.java:606)
> >
> >at org.apache.catalina.startup.Catalina.load(Catalina.java:629)
> >
> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >
> >at
>
> >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> >
> >at
>
> 

Exception Both the UrlPattern and value attribute were set for the WebServlet annotation on class ...

[basilk]

Hi.

I try to start tomcat 8.0.33 in debug mode under Eclipse Mars.2.
I get the following errors:

SEVERE: A child container failed during start
java.util.concurrent.ExecutionException: 
org.apache.catalina.LifecycleException: Failed to start component 
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/isogdquery]]
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at 
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:916)
at 
org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:871)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
at 
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
at 
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.catalina.LifecycleException: Failed to start component 
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/isogdquery]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:153)
... 6 more
Caused by: java.lang.IllegalArgumentException: Both the UrlPattern and value 
attribute were set for the WebServlet annotation on class 
[test.org.apache.catalina.startup.DuplicateMappingParamFilter]
at 
org.apache.catalina.startup.ContextConfig.processAnnotationWebFilter(ContextConfig.java:2426)
at 
org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2057)
at 
org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:1940)
at 
org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:1934)
at 
org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:1934)
at 
org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:1934)
at 
org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:1934)
at 
org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:1934)
at 
org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1147)
at 
org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:779)
at 
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:306)
at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:95)
at 
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5150)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
... 6 more

When i start tomcat as service in Windows everything is ok.

What seems to be a problem?

Thank you.

Basil.



---
Это сообщение проверено на вирусы антивирусом Avast.
https://www.avast.com/antivirus