It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×6,034
×5,946
×4,321

question asked: Oct 02 '15, 2:48 p.m.
question was seen: 5,777 times
last updated: Oct 03 '15, 12:05 p.m.

Related questions

Why am I running into Error 404: ProxyServlet: /jts/setup when the server started up fine?

0
Handika Handoko (11●1●1) | asked Oct 02 '15, 2:48 p.m.
The server was started up fine as shown by the last line of the startup log showing INFO: Server startup in 181657 ms; however, I am unable to access https://localhost:9443/jts/setup. 

I did notice the following SEVERE messages in tomcat's log: 
SEVERE: Failed to initialize end point associated with ProtocolHandler ["http-bio-9080"]
SEVERE: Failed to initialize connector [Connector[HTTP/1.1-9080]]
SEVERE: Failed to initialize end point associated with ProtocolHandler ["http-bio-9443"]
SEVERE: Failed to initialize connector [Connector[HTTP/1.1-9443]]

I do see a follow-up message INFO: Initializing ProtocolHandler ["ajp-bio-9009"]. Does that mean it's using port 9009? 

On Firefox, I get the "Error 404: ProxyServlet: /jts/setup" message while on IE, it's only a "HTTP 404 Not Found" message. 

Do I have to do what this post suggest? https://jazz.net/forum/questions/46651/error-404-no-target-servlet-configured-for-uri-jtssetup 


2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Marek Siekierski (817●5●10) | answered Oct 02 '15, 2:53 p.m.
Hello Handika,

Do you have a firewall in the mix? Can you check with your network admin to ensure communication is allowed through those ports?

By default, the ssl port Tomcat will use is 9443 as defined in the server.xml file:

    <Connector port="9080" protocol="HTTP/1.1" 
               connectionTimeout="20000" 
               redirectPort="9443" />

Check that 9080 and 9443 are not in use prior to starting Tomcat as well.
Comments
Handika Handoko commented Oct 02 '15, 3:36 p.m. | edited Oct 03 '15, 12:05 p.m.

 Hi Marek,


This is what I get from doing netstat -an which leads me to think that the ports are open...? 

  Proto  Local Address          Foreign Address        State
  ...
  TCP    0.0.0.0:9080           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:9100           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:9443           0.0.0.0:0              LISTENING
  ...
  TCP    [::]:9080              [::]:0                 LISTENING
  TCP    [::]:9100              [::]:0                 LISTENING
  TCP    [::]:9443              [::]:0                 LISTENING
  ...

Marek Siekierski commented Oct 02 '15, 8:47 p.m.

If you run a netstat -an when the server is down, and it shows that something is listening at those ports, you would run into a port conflict when starting Tomcat. Glad you were able to resolve your issue by changing the ports.
0
permanent link
Handika Handoko (11●1●1) | answered Oct 02 '15, 3:48 p.m.
 I ended up following the suggestions in the other post to change the port configuration for Apache and it seems to have solved the problem. Odd but oh well, it works now. 

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.