I have installed tomcat server with java application in ubuntu 15.10. Tomcat server with Application is running in server (locally). But issue is that it is not running in other system browser (Remotely). I tried all ways like port changes, SSL config, server.xml config, web.xml. Please let me know what is the solution exactly.
I have attached the below remote tomcat web page error...
Firefox can't establish a connection to the server at
xxx.xxx.x.x:8080.
The site could be temporarily unavailable or too busy. Try again in a
few moments. If you are unable to load any pages, check your
computer's network connection. If your computer or network is
protected by a firewall or proxy, make sure that Firefox is permitted
to access the Web.
Related
Currently, I am using a virtual machine in Oracle cloud. I have successfully installed Tomcat and IdentityIQ. The server is deployed correctly, but when I try to access through Google Chrome with the credentials, I get the following error.
I have disabled the firewall and when I try to test the connection with ping it does not respond.
In the client environment tomcat is running as a service with logon account as Local System Account. I have deployed a java based REST API client application in that tomcat. Every time the client is running its not able to set up connection with the destination.
In the client environment tomcat is running as a service with logon account as Local System Account. I have deployed a java based REST API client application in that tomcat. Every time the client is running its not able to set up connection with the destination.
There is absolutely no issue with the destination endpoint and the java code, as in other environments, that client is running fine in the tomcat.
Error that we are seeing is -- ConnectionTimeOut.
Account that the tomcat is running under in the client environment is -- Local System Account.
This is a huge road blocker and if anybody can provide guidance will be extremely helpful.
Error that we are seeing is -- ConnectionTimeOut.
Definitely it might be firewall issue. Your client is not able to connect to server, where your service is running. You need to ping from client machine to server where service is running. That will tells you whether Connectivity established or not.
I have the problem. Let me describe the situation first.
I have setup the weblogic cluster in two machines on linux OS.
I have deployed the web application and web services on them.
In the web application, it will call "http://localhost:7201/BusinessLogic/services/AccountService?wsdl" web service. But it said connection refused in the log.
But if I change localhost to be ip address of one weblogic machine IP, it is working. e.g. "http://192.168.0.30:7201/BusinessLogic/services/AccountService?wsdl" where 192.168.0.30 is one of ip address of web application machine.
I have checked /etc/hosts, it has mapping 127.0.0.1 localhost.
I checked in my computer to use postman to call web service "http://192.168.0.30:7201/BusinessLogic/services/AccountService?wsdl", it is working. Of course, I cannot test localhost in my computer.
I also think is there a way to check localhost web service on linux machine. is there a way??
Where is the problem??
Please help!!!
I've seen a lot of posts on the build agent not being able to connect to the server, but in my case I can't connect to the server at all.
I'm using TeamCity 10, on CentOS 7 with the Oracle JDK installed. I've started the server using the runAll script and have not changed anything in the configuration. I opened port 8111 with FirewallD to access the setup screen.
The problem is, I can't access the setup screen. I open the page in Chrome and it just hangs "connecting". I tried Firefox too, and also CURL. It appears that the TCP connection is accepted, and the HTTP request is sent, but no response comes at all.
The logs do not show that anything is wrong. The build agent log fails to register to the server, however, saying it is in "maintenance mode". This is a fresh install.
I am currently implementing a single signon solution for a customer that is based on Java, Tomcat and Kerberos.
Users are to access the URL of an intranet Tomcat application from their client browsers, the Tomcat application acquires the users' credentials via Kerberos and redirects them to the actual web application.
Our customer's environment is a typical mixture of a Windows AD server acting as the KDC and Linux Tomcat application servers. The SSO functionality is supposed to be used from both Windows and Linux clients. This is what appears to be different from most answers I can find on the net where people have Linux web application servers but only use Windows clients.
Now, in my local setup I get some strange behaviour. My development environment is a Tomcat 7.0.26 running from MyEclipse 8.6 under Windows 7. My test environment is a Tomcat 7.0.26 or 7.0.53 behind an Apache web server on a Centos 6 machine. I have set up the AD server correctly, generated the necessary keytab files etc. and everything is running smoothly in the development environment. I can access the Tomcat application from both Linux and Windows clients using IE and Firefox, Kerberos authentication proceeds and I get redirected properly.
When deploying the Tomcat application on the test server this keeps working when trying to sign on from Windows clients. However, when I try to access the test server from a Linux client (I have tried from Linux Mint 13 and Ubuntu 13.10), I get the following error:
javax.servlet.ServletException: GSSException: No credential found for: 1.3.6.1.5.2.51.3.6.1.5.2.5 usage: Accept
net.sourceforge.spnego.SpnegoHttpFilter.doFilter(SpnegoHttpFilter.java:233)
I have to admit that I do not properly understand this message. Does it point to a problem with the credentials supplied by the client or a problem with the application server negotiating with the KDC? I have done some research on this problem and have found out that the indicated oid 1.3.6.1.5.2.5 stands for GSS_IAKERB_MECHANISM and not GSS_KRB5_MECHANISM or GSS_SPNEGO_MECHANISM which I find strange. Also, nobody else appears to have exactly the same problem.
I have tried switching from MIT Kerberos to Heimdal Kerberos and back. I have tried Firefox and Chromium, on the application server I have switched between Tomcat 7.0.26 and 7.0.53, the problem still persists. I am using the latest spnego.jar.
Now: Calls from Linux to the Tomcat running on the Windows development machine succeed and calls from Linux clients to the Linux application server fail with the same error message for both browsers tried.
Any ideas on this one?
GSS_IAKERB_MECHANISM means that the client is not able to determine the realm/kdc to create a service ticket and asks the server to serve as an intermediate to the target KDC. Check Wireshark traffic. Your task now is to analyze why the client is not able to create a service ticket for that SPN. I have observed this issue on Heimdal on FreeBSD with Microsoft KDC.
So the problem ist not your Tomcat instance.