I was using Apache tomcat 9.0.44 earlier and due to some security vulnerabilities I've upgraded it to 9.0.62 now.
/bin/Version.bat shows correct version now 9.0.62
Also checked registry keys and it also shows correct version
Still on security dashboard we are getting "Vulnerable version of Apache Tomcat is installed 9.0.44"
All the applications are working fine.
I am not sure if during upgrade I've missed anything.
During upgrade from 9.0.44 to 9.0.62 these were the steps that I'd followed:-
From this URL https://tomcat.apache.org/migration-9.html#Upgrading_9.0.x checked the configuration file changes from Apache tomcat 9.0.44 to apache tomcat 9.0.62 and perform these changes in the configuration files as applicable.
Replaced all jar files from
Downloads\apache-tomcat-9.0.62-windows-x64\apache-tomcat-9.0.62\lib to
Tomcat9/lib directory
Updated Bootstrap.jar , Tomcat-juli jar , Tomcat9.exe , Tomcat9w.exe files from
Downloads\apache-tomcat-9.0.62-windows-x64\apache-tomcat-9.0.62\bin to
Tomcat9/bin
Also java -cp "catalina.jar" org.apache.catalina.util.ServerInfo shows :-
could anyone please suggest what is incorrect in this case?
Related
I have one remote test server, I want to upgrade the Sentry and Log4j to the latest version. I built my java project and on my local machine both Sentry and Log4j where now latest. But, when I upload the jar file to test server(remote server) and run the service it still shows the old version.
The jar is having the latest version of Sentry and Log4j.
Can anyone help me know why I am not able to upgrade these tools on my remote server.
Below is the latest version showing in the jar -
I have downloaded the newest version of apache tomcat and I want to connect tomcat with eclipse .
When I try to I get
I have seen many answers about this but in ubuntu not windows 10 . My eclipse version is 2020-09 (4.17.0) I don't know maybe that's the problem
I also saw that Apache Tomcat version 9 supports JAVA EE , 5,6,7 ,8 Web modules and I have jdk 14.02 as my path . Maybe this is the problem
Using a version installed to be run by your O.S. means an unpredictable file and jar layout, and the server tools need to know the layout to gather the right libraries to run Tomcat properly with full control of the created process for debugging. Use a zip file or tarball straight from tomcat.apache.org instead.
I am exporting a war file in eclipse and trying to deploy that in weblogic 8.1 but not able to do so. JDK version provided by weblogic is 1.4 but in my path variable jdk is 1.6. However I am using compiler compliance level as 1.3 but no luck. Can anyone please tell me what is the issue here. Is there any way to create war from eclipse and deploy it to weblogic 8.1???
I am trying to deploy a spring .war into jboss but am getting 404 errors. I know this has been asked before:
springBoot application on Jboss EAP, servlet context not lodaed
Spring Java Config vs Jboss 7
Cannot deploy Spring Boot on jBoss EAP 6.3.3
But I am very new (this week) to maven/spring/jboss, so may well have messed up. I tried what I understood from the various solutions above and none of them worked for me. Probably me messing up or missing something. So I thought I'd get the problem as simple as I can.
I took the code from:
https://github.com/spring-guides/gs-rest-service.git
And then work in the complete folder.
cd complete
mvn package
java -jar .\target\gs-rest-service-0.1.0.jar
And that all worked as you'd expect.
So then I followed the instructions here (http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#howto-create-a-deployable-war-file) to modify my code and pom.xml to produce a war file.
pom.xml http://pastebin.com/BiLWDskd
Application.java http://pastebin.com/par7rftz
I then mvn clean package and load the resulting .war file into EAP using the UI (http://i.stack.imgur.com/N7zxG.png).
So then in theory this should be the URL right
http://localhost:8080/gs-rest-service-0.1.0/greeting
I also tried
http://localhost:8080/greeting
But am getting the 404 error (http://i.stack.imgur.com/T6J6z.png) as described in the other questions. Nothing appears in the jboss console log at all after the .war is loaded.
So am I missing something? Do I need to write a jboss #WebServelet class to wrap around the spring stuff? Changes to my pom.xml? Should I not be using springboot, and just just pring framework modules directly? I note that in the EAP screen it does not show the class in the third column like it did with the jboss sample .war.
Remember I am new to this, so please explain stuff as if I'm a complete dummy (which I am).
Details of my setup:
OS Windows7 x64
java version "1.8.0_91"
Apache Maven 3.3.9
Springboot 1.3.3
JBOSS EAP 6.4.0
No IDE, using vim and command line
I encountered the same problem on JBoss EAP 6.4 / spring boot 1.5 and what fixed it was to add this property to application.properties
server.servlet-path=/*
as explained in this post : Deploying spring boot on JBOSS EAP 6.1
A simple tutorial you can follow (though he miswrote the property server.servlet.path )
http://code-adda.com/2018/06/how-to-deploy-spring-boot-war-in-jboss/
I am working on a big project that requires massive financial calculations, I am using
Netbeans IDE 7.3 with a default web application of Java EE 5 (not a maven application)
,My application server is tomcat 7 I am using jsps and servlets my OS is windows 7.
I downloaded and added the jquantlib binary to my application, but when I run it keeps saying that it needs the slf4j-api extension that is not found so i download it also and added its jar to my project but still the error persists.
How can I solve this ? and can anyone give me some guidelines on how to do it ?
The key here is that jquantlib requires slf4j-api version 1.4.0 in the jar manifest:
(from MANIFEST.MF in jquantlib.jar)
Implementation-Vendor-Id: org.jquantlib
Extension-List: slf4j-api
slf4j-api-Extension-Name: slf4j-api
slf4j-api-Implementation-Version: 1.4.0
Tomcat will try to use the version of slf4j-api that you're including in your app, but it's likely that what you've included isn't actually compatible. See http://grepcode.com/file/repo1.maven.org/maven2/org.apache.tomcat/tomcat-catalina/7.0.34/org/apache/catalina/util/Extension.java#Extension.isCompatibleWith%28org.apache.catalina.util.Extension%29 for details.
Bottom line - try to use slf4j-api version 1.4.0 in your application.
Try removing the lines from the MANIFEST.MF file that mention the sfl4j