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
Related
The service is running but I get a half corrupted page. I upgraded using the automatic update mechanism. Note that the teamcity is running behind an nginx server with the real service running at http://$hostname:8080/teamcity and nginx forwarding from http://$hostname/teamcity.
If I restart the service I get the following log in teamcity-server.log
https://gist.github.com/bradphelan/74ea8fa9c422c51a23820ee74cab72cc
linked as gist as SO will not allow pasting such a large file in.
Switch it off / switch it on. It works again. ( No idea why )
My problem is the opposite of many problems...
We have a WCF web service which works fine on our 'live' IIS server.
When I run the code in VS (even if running as admin) on the dev machine, I get nothing in the browser, and cannot request ?wsdl which also works on the server.
The web config files on both machines are identical.
What is wrong here, please?
EDIT:
I have added a new WCF project to the solution. That one DOES show the service, present the WSDL and allow browsing of the folder contents.
I copied the web config setting:
<directoryBrowse enabled="true"/>
into my existing web config, but it still won't allow directory browsing.
I’m having an issue with the spring boot dashboard. When I start an app the icon show the loading icon and never reaches the green up icon though the app does start and accepts requests. When I stop the app it takes a couple of minutes to stop.
I have access to another machine where the dashboard behaves as expected.
I’m using the getting started rest service app (gs-rest-service-complete) targeting spring boot 1.4.3.release with no modifications. I’m using sts 3.8.3.
I’m experiencing the issue on OSX El Capitan 10.11.6
My jdk version is 1.8.0_112
I've found a couple of similar questions but the suggestions don't resolve my issue.
This one relates to bad entry in hosts file - mine is ok (Spring Boot Dashboard projects never finish starting)
This one suggests switching life-cycle-bean support off, but I want to know how to use run the dashboard with it enabled. The response to this question also requests a sample app, as stated I'm using the gs-rest-service-complete sample app (STS Spring Boot Dashboard Doesn't Recognize Successful Start)
What might be causing this problem?
It sounds like the machine where it doesn't work might have some kind of firewall stopping the JMX connections. These connections are made via sockets. Firewall type software sometimes prevents the connections. If you know of firewall type software running on your machine you could try disabling it or (less drastically) trying to reconfigure it so it allows connections between different processes running on your machine.
I got a Glassfish 4.1.1 copy with two domains on Win2012R2 (no clusters, no instances). I've set a windows service for each of those.
Both services run regularly up until the moment when I restart either or both of them thru their admin web console (server (Admin Server) -> Restart). The following happens:
The domain-related service stops, but does not start again,
The allegedly stopped domain is perfectly functional (deployed apps and admin console are there) (!!!),
When I try to start the win service manually, I get Error 1067 (GF reports "something" is already listening on required ports and that's the domain itself that is now, somehow, NOT run as a service!),
I can start the service again only after I've stopped the domain thru server (Admin Server) -> Stop.
Why did I mention two domains? Because this does not happen when I have just one domain with its' service.
Domains do not share ports, only things in common are the JDK/JRE and general GF files.
Is this a bug in Glassfish or did I set something wrong?
This is a limitation, rather than a bug. The problem is that GlassFish has no way to tell whether or not it is running as a service (and, if it is, what the name of that service would be).
The restart command means that GlassFish is restarting itself, so Windows detects that the process it started has been terminated and shows the service as stopped, but GlassFish spawns a new JVM itself. It has no capability to tell Windows to start the service again.
Essentially, the behaviour you are seeing is expected.
After some more testing, I realized what was going on:
Glassfish is definitively capable of restarting its' own Windows service,
The thing that was happening is it takes GF a few seconds do this on its' own,
But, before GF domain could restart as a service, I clicked the URL to return to admin console, every time. That forced it to run as an ordinary executable.
It does seem like the restart happens faster with just one win service, but I won't claim that as an absolute truth without more testing, for which I have no time now.
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