I was a bug in at AbstractClassFinder.java:216
(com.ocpsoft.pretty.faces.config.annotation.AbstractClassFinder.processClass)
Sorry and thanks for your tips!
On Mon, Dec 20, 2021 at 4:53 PM Christopher Schultz
wrote:
>
> Daniela,
>
> On 12/20/21 13:15, Daniela Morais wrote:
> > I'm trying to upgr
On Sat, Dec 18, 2021 at 11:09 AM Mark Thomas wrote:
>
> On 15/12/2021 22:23, Samuel Cox wrote:
> > Hello,
> >
> > We are using tomcat-embedded 9.0.55. OS is mac 10.15.7. We have
> > quite a bit of config, but I'm guessing the most relevant is that we
> > use the NIO2 protocol.
> >
> > We have be
Daniela,
On 12/20/21 13:15, Daniela Morais wrote:
I'm trying to upgrade Log4j2 dependencies to 2.15.0 and I'm facing
this issue. Is there any workaround or the only option is to upgrade
Java?
Note that if you are trying to "upgrade to the latest log4j" due to
revent CVEs, you want 2.17.0 and
Jon,
On 12/19/21 12:19, Jonathan Yom-Tov wrote:
hi Chris,
Sorry for the late reply, I didn't see your reply for some reason. Here's
the relevant connector configuration:
You are allowing Tomcat to automatically-configure an "Executor" for
you, and that executor will never shed threads.
that is a class that is being loaded on java 8 and it wants java 9
but log4j as far as i know supports even java 7.. so i have a feeling that
can't be it (that it won't run on java 8)
On Mon, 20 Dec 2021 at 19:15, Daniela Morais wrote:
> I'm trying to upgrade Log4j2 dependencies to 2.15.0 and I'
We are running Tomcat 9 on Java 11 without any issues, but you probably want to
test it with your application.
> Am 20.12.2021 um 19:15 schrieb Daniela Morais :
>
> I'm trying to upgrade Log4j2 dependencies to 2.15.0 and I'm facing
> this issue. Is there any workaround or the only option is to u
I'm trying to upgrade Log4j2 dependencies to 2.15.0 and I'm facing
this issue. Is there any workaround or the only option is to upgrade
Java?
Configs
Java 8
Tomcat 9.0.56
Log
20-Dec-2021 15:10:45.177 SEVERE [RMI TCP Connection(2)-127.0.0.1]
org.apache.catalina.core.StandardContext.listenerStart E
You might try adding "RemainAfterExit=yes" to your service definition (in
the Service block). Also, try looking at the journald logs for catalina and
systemd; they might give you more clues as to what is happening (sudo
journalctl -t systemd and sudo journalctl -t catalina).
On Mon, Dec 20, 2021
Dear all,
sorry, I rarely work with tomcat, now I upgraded from 9 to 10 and I am having
troubles even before putting my .war applications in, I hope someone can point
me to my mistake.
I have installed tomcat with brew on Ubuntu 18. It was installed in
/home/linuxbrew/.linuxbrew/Cellar/tomcat/
On 20/12/2021 06:59, Jerry Malcolm wrote:
I'm adding a slight variation to the error I get at times (see bottom of
stack trace below)
This is the code that throws the root exception:
if (!Files.isDirectory(cryptoPolicyPath)
|| !Files.isReadable(cryptoPolicyPath)) {
throw new Securi
10 matches
Mail list logo
