Re: tomcat v 9.0 crashing in Eclipse IDE Version: 2020-09 (4.17.0)

2020-12-08 Thread Mark Thomas 
On 08/12/2020 19:51, Jim Anderson wrote:
> 
> I am trying to run Tomcat v 9.0 in Eclipse on a linux PC and the server
> is crashing before if fully starts up. At this point, I do not consider
> this a user error,

It is clearly user error.

> but possibly my configuration of Eclipse is a bad
> one. But even if it is, there should be error message not a crash with a
> stack trace.

That isn't a crash. That is Tomcat deliberately not starting because of
the user error.

You have been provided with an error message and a stack trace to show
you exactly where the error occurred.


The servlets named [bfs.hyp.SCCS.AjaxHandler] and [bfs.hyp.AjaxHandler]
are both mapped to the url-pattern [/AjaxHandler] which is not permitted


In this instance there is no way for Tomcat to determine which Servlet
should be enabled and which one ignored so Tomcat fails the start.

> For now, I am simply including the error file showing the stack trace.
> Should I submit this to the developers mailing list?

No.

Mark

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

tomcat v 9.0 crashing in Eclipse IDE Version: 2020-09 (4.17.0)

2020-12-08 Thread Jim Anderson 


I am trying to run Tomcat v 9.0 in Eclipse on a linux PC and the server 
is crashing before if fully starts up. At this point, I do not consider 
this a user error, but possibly my configuration of Eclipse is a bad 
one. But even if it is, there should be error message not a crash with a 
stack trace.


For now, I am simply including the error file showing the stack trace. 
Should I submit this to the developers mailing list?


--
Jim Anderson
cell - 908-329-0586

Dec 08, 2020 2:17:24 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server version name:   Apache Tomcat/9.0.38
Dec 08, 2020 2:17:25 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server built:  Sep 10 2020 08:20:30 UTC
Dec 08, 2020 2:17:25 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server version number: 9.0.38.0
Dec 08, 2020 2:17:25 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Name:   Linux
Dec 08, 2020 2:17:25 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Version:5.4.0-56-generic
Dec 08, 2020 2:17:25 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Architecture:  amd64
Dec 08, 2020 2:17:25 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Java Home: /usr/lib/jvm/java-11-openjdk-amd64
Dec 08, 2020 2:17:25 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Version:   11.0.9.1+1-Ubuntu-0ubuntu1.20.04
Dec 08, 2020 2:17:25 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Vendor:Ubuntu
Dec 08, 2020 2:17:25 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_BASE: 
/home/jja/eclipse/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0
Dec 08, 2020 2:17:25 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_HOME: /usr/share/apache-tomcat-9.0.38
Dec 08, 2020 2:17:25 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: 
-Dcatalina.base=/home/jja/eclipse/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0
Dec 08, 2020 2:17:25 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dcatalina.home=/usr/share/apache-tomcat-9.0.38
Dec 08, 2020 2:17:25 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: 
-Dwtp.deploy=/home/jja/eclipse/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps
Dec 08, 2020 2:17:25 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dfile.encoding=UTF-8
Dec 08, 2020 2:17:25 PM org.apache.catalina.core.AprLifecycleListener 
lifecycleEvent
INFO: The Apache Tomcat Native library which allows using OpenSSL was not found 
on the java.library.path: 
[/usr/java/packages/lib:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib]
Dec 08, 2020 2:17:27 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-nio-8080"]
Dec 08, 2020 2:17:27 PM org.apache.catalina.startup.Catalina load
INFO: Server initialization in [3411] milliseconds
Dec 08, 2020 2:17:27 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service [Catalina]
Dec 08, 2020 2:17:27 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet engine: [Apache Tomcat/9.0.38]
Dec 08, 2020 2:17:29 PM org.apache.catalina.core.ContainerBase startInternal
SEVERE: A child container failed during start
java.util.concurrent.ExecutionException: 
org.apache.catalina.LifecycleException: Failed to start component 
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/testProj]]
at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
at 
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:916)
at 
org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:843)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at 
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)
at 
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at 
org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at 
java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:140)
at 
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
at 
org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at 
org.apache.catalina.core.StandardService.startInternal(StandardService.java:421)
at org.apache.ca

tomcat 9.0 cache warning errors

2020-12-08 Thread Jim Anderson 


While writing this post, I managed to fix my own problem with help from 
the internet. The solution is for anyone running tomcat v 9.0 inside 
eclipse.


Tomcat v9.0 in eclipse gave me a large number of cache warning errors 
and eventually crashed.  While verifying the problem, I discovered a fix 
discussed at the following url:


https://stackoverflow.com/questions/14771710/how-to-solve-javax-servlet-servletexception-java-lang-unsupportedclassversioner

That site recommended adding the following line to the tomcat path 
.../config/context.xml.


| I added that 
line to context.xml and after several iterations of trying, the |||cacheMaxSize value was 60 (i.e. 600M-bytes in size). The website I 
am working on only contains 22 M-bytes so cache size should not have 
been an issue, but the warnings kept coming. Then I thought, maybe 
Eclipse has its own version of tomcat 9.0 and sure enough I found there 
is a tomcat v 9.0 sub-directory in eclipse/workspace/Servers directory. 
I added the 'Resources' line shown above to the the conf/context.xml 
file in the eclipse tomcat v 9.0 sub-directory and that fixed my 
problem. |So the 2 step fix for cache error messages is: 1) locate the 
correct version of tomcat in your eclipse workspace 2) add "|||" to your 
context.xml file. I will update the stackoverflow.com URL with a 
comment. I'm not sure if this is worth mentioning anywhere in the tomcat 
documentation. I will leave that to others.||


--
Jim Anderson

Re: Open SSL with Custom Session Resumption

2020-12-08 Thread Christopher Schultz 

Anil,

On 12/7/20 14:01, Anil Gursel wrote:

Is there any documentation/example of using Open SSL (via Tomcat APR) with
custom session resumption?


Can you explain a little further? Not just triggering renegotiation / 
resumption but ... something very specific and custom?


-chris

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

Updates to POEditor.com

2020-12-08 Thread Mark Thomas 
All,

As you are probably aware, the Apache Tomcat project uses POEditor.com
to manage the i18n translations used by the project.

The POEditor team have implemented a change that means it is no longer
necessary for us to escape single quotes when using them in translated
strings. The appropriate escaping is now added automatically when the
strings are exported. The current translations have been updated to
reflect this.

We have seen an immediate benefit of this change. I am currently in the
middle of re-exporting the translations from POEditor.coma and importing
them into the Tomcat source code to confirm that POEDitor's automatic
update didn't break anything. So far I have found no errors and a
handful of instances where we were not escaping correctly that have been
automatically corrected.

Remember, anyone can create a POEditor.com account and start helping
with the translations.

https://poeditor.com/projects/view?id=221603

Thanks,

Mark

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