Apache Tomcat 7 The Requested Resource Is Not Available - tomcat7

Newbie to Tomcat 7 and everything here so apologies if this is a simple error. I've looked through other questions and answers asking the same thing and nothing seems to pertain to my issue. I've updated Tomcat 5.5 to Tomcat 7. When accessing http://localhost:80 I see the Tomcat 7 page perfectly fine so I'm guessing it's something in the URL that's being accessed.
I've installed Tomcat 7 and am trying to navigate to the URL http://localhost/otcs/cs but I keep getting the Request Resource is not available error. Below is my server.xml file.
java.lang.NullPointerException
java.lang.String.getBytes(Unknown Source)
com.opentext.servlet.client.LLServletClient.sendErrorPage(LLServletClient.java:249)
com.opentext.servlet.client.LLServletClient.sendErrorPage(LLServletClient.java:208)
com.opentext.servlet.client.LLServletClient.doGet(LLServletClient.java:122)
javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
com.opentext.servlet.filter.CompressionFilter.doFilter(CompressionFilter.java:446)
Thanks for the help and I'm happy to give more information if needed.

Related

Tomcat on Windows, Chrome console: net::ERR_CONTENT_LENGTH_MISMATCH 200

After upgrading Tomcat on windows, Chrome is not able to pull some files. It seems to fail when running scripts using relative paths. Some small files return fine.
Chrome console:
net::ERR_CONTENT_LENGTH_MISMATCH 200
Problem persists when trying several newer versions of Apache Tomcat.
For the record, I have also changed my appBase. Problem seems to persist either way. Default Tomcat content serves fine.
This can be solved by opening the Tomcat Service
Properties
Log On
Select local system account
Allow service to interact with desktop (not sure this is needed?)
And is explained fully here Tomcat Service gets installed with “Local Service” account

Our GITBLIT/Jetty service has stopped working after new stringent network security at our company

The GitBlit service on one of our Windows Server 2012 R1 was working just fine until our company implemented hyper-stringent security corporate-wide.
The gitblit service is running, but when trying to reach the gitblit page via web browser results in Jetty error 503, service unavailable.
I've been unable to come up with a google query to find out how I can check to see if jetty is running or how to troubleshoot.
Any help would be very much appreciated.
It turns out that what I needed to do is check the gitblit logs where I found that a colleague across the pond left me with a corrupted config file. When I removed the problem, it started working again.

REST not working on Windows Server 2016

I have a simple WAR application offering a REST Service. I use RESTClient on the same Version of Firefox running on the same machine as the webservice.
This works fine locally on a Tomcat 9.0.10 on Windows 10 Enterprise.
When I start the same application on a Windows Server 2016, which has exactly the same Tomcat running, I get a 404.
Locally accessing the tomcat Management page (http://localhost:8080) works fine. On both machines the same Version on Java 8 is installed.
Any ideas, what could be the reason for this behaviours are welcome …
Regards Claus
I installed a version of TomCat, which initializes Tomcat as a Service. This miraculously solved the problem.
I don't understand, why this solved the Problem. But it did.
So this question is answered (somehow).

Web application is seemingly not running when deployed in websphere

I have a war file which I deployed and ran in tomcat. Then I deployed it in websphere from admin console. The status of the webapplication is seen as started along with the built-in web applications such as "ivtApp", "query", etc. Now from this link:
Heading
http://pic.dhe.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=%2Fcom.ibm.websphere.nd.doc%2Finfo%2Fae%2Fae%2Frins_portnumber.html
It looks like the port number for web application is 9080 for http. I tried to run the application using the link:
http://{localhost}:9080/spring3HibernateMaven/index
(I am using "{" because this website didn't allow typing localhost)
the context root being spring3HibernateMaven. And I get page not found error in the browser. So I thought there must be something wrong with my web application. Hence I tried to run their web application:
http://{localhost}:9080/ivtApp
Which gives the same error. Even
http://{localhost}:9080/
gives the same error. I assume it should show something for this url as is shown from tomcat.
So how can I run the/any web application in websphere? FYI, I downloaded the latest version of websphere from their website.
Thanks
ivtApp has context path "ivt", so you need to use host:9080/ivt
Btw, you can find context path setting in websphere\application control panel

Symfony2 Assetic files and Missing routes in Windows

I have a Linux machine, and a Windows 7 machine, each of which is using the exact same code (they are both using the same git repo). I am running the Symfony2 code on both servers in the dev environment.
The website loads and runs just great on the Linux server. On the Windows 7 server (my local laptop) the server seems to be missing all the routes it needs to render the site correctly. For example:
None of the CSS and JS files are loading on the site. They are throwing a 404 page not found error.
If I attempt to navigate to any other pages from the home or landing page, a 404 error is always thrown: The requested URL was not found on the server.
I've cleared the cache, and run through the app/check.php on the windows box, but to no avail. I'm wondering if the Windows server setup needs to be modified in some way so the routing works as expected? I'm thinking that the problem is the routing on the Windows server, as the requested URLs can't ever be found.
Any ideas on where I can go to find a solution or any tests I can perform to track down the issue?
Thanks,
Derrick
In the httpd.conf file, you must be sure that:
LoadModule rewrite_module modules/mod_rewrite.so
is active. In my windows distribution of apache 2.2, it was commented out. I'll suggest to Symfony2 that they add this module to their check.php file for future developers. I'm guessing they just assume that it will always be enabled in the apache distributions.

Resources