JNLP server returned 503 error - server

I found some posts on this error but i can't get my JNLP to work.
I try to access a JNLP located on server by the command :
javaws http://:8081/jnlp/Composer.jnlp
The problem is that the server keeps returning 503 error even though my collegue is accessing it with not problem.
I understood that 503 error is a temporary unavailability of the server, but the previous point shows that the server is running fine (we tried several times).
The exact encapsulated error is :
java.io.IOException: Server returned HTTP response code: 503 for URL: http:///jnlp/Composer.jnlp
What i tried to do is
allow the adress of the server in the exception sites
use the option to use IPV4 adress by default for JVM (i saw a post saying that there can be a bug using jre7 if u dont set the option -Djava.net.preferIPv4Stack=true)
restart server
disable firewall.
My problem is that as my collegue can access it, it looks like a client configuration bug, not server.
Does somebody have an idea?
Thanks for your support.

Related

Connect to C++ REST sdk SERVER on Windows from LAN

I have a server written on C++ REST SDK.
There's http_listener which listens to "http://localhost:34568".
When I try to send a request in browser or from the client to localhost it works fine and I get the responses from my server. But the point is to use the application in network. And here where the problem comes.
When I try to request the server from the other PC using IP(192.168.1.103:34568) I get "HTTP Error 400. The request hostname is invalid."
I'm aware that that could be some firewall issues but it's turned off. Also I tried to set port rules in brandmauer and it didn't help.
And even more! I got XAMPP running Apache server and when I do the same thing but with (192.168.1.103:80) I do get the response from Apache and have an access.
Anybody had something similar or somebody knows what the problem is about?
Listen to local ip address or to your network name (dns):
"http://xxx.xxx.xxx.xxx:34568" or
"http://your_network_name:34568"
So, if you have multiple network adapters, you can choose which one.

SoapClient can not open local WSDL (nginx, php7-fpm)

I'm running nginx and php7-fpm and have problems with the SoapClient accepting local wsdl files. I use a local file (like /api/backend/server/reservation/reservation_v012.wsdl) but I get a 502 Bad Gateway error. When I use "file:/" I get an error "failed to load external entity".
__getTypes() is not delivering any types. The 502 Bad Gateway error occurs exactly at this position, when __getTypes() is called.
Any idea why it's not running like it does with PHP 5.3 before?

HTTP error 508 from PERL script during redirection of requests from secure to non-secure server

I am getting a strange error in my file upload application.
1) Server 1: It is secure web server on port 443, which is accessible to public hosting a perl script
2) When this server get a request for cgi-bin directory, it will simple redirect the request to other web server (Server 2) running on port 80
3) The perl script in Server 2 will save the file in disk
Issue:
Above mechanism worked for a couple of hours later it has thrown Http error code:508
Observations:
If I directly hit Server2 on port 80, perl script successfully saving the files to disk. But If I directly hit Server1 on port 443, I am getting 508 error
When I first got the issue, I have restarted both webservers and it worked. But when I get the same issue second time, restart of servers did not help. The call to Server1 is throwing 508 error and requests are getting timed out.
ulimits and open files are in control.
If you experience this type of issue, please share your thoughts.
This strange issue has been resolved after moving dynamic service to other Virtual machine. This issue is no longer reproducible after changing the node.

I can access 127.0.0.1, but not http://localhost:8080

I have a problem. I am trying to run a simple JSP page from Eclipse:
http://postimg.org/image/z268cl1s3/
But when I run this page i get a 404 error:
http://postimg.org/image/h0rosix4z/
When I put in:
localhost
127.0.0.1
in the browser it works fine:
http://postimg.org/image/8js6hlsg3/
I can see eclipse is running it from localhost:8080, but when i type that in at the browser it gives me this error:
http://postimg.org/image/7lbtfbf43/
Does anyone know how I can activate localhost on my mac. I looked up several tutorials, but i didnt find the answer. MySQL is also running fine on the computer, so I guess there is something that dont let me access [http://localhost:8080?]
Hope someone can help me?
Best Regards
Mads
There are two issues you are having:
There is a difference between http://localhost/ (and its equivalent http://127.0.0.1) and http://localhost:8080 - the first uses port 80, the second 8080. The Tomcat server listens only to the latter, that is shown by the servers error messages, and not generic 404 messages. In other words, do not forget to add the 8080 port numbers to the end of the localhost url
The Tomcat error messages show that the resources are not available, so I would look at what Java web applications are installed - e.g. the root web application is missing (the localhost:8080 url) for sure, and I am not sure whether your MySQL connector is.
Search google for how adding an entry to the hosts file on your mac.
You'll basically link localhost to 127.0.0.1 there

Git Problem in Mac (Fatal Error)

I am setting up one git client on Mac (Using Source Tree). While committing the code it is showing the following error(please check the screen-shot). Any idea to solve this error ?
ERROR :
That generally happens when your server denies your connection. There are a number of causes for getting denied:
No/wrong SSH key (if the server uses SSH authentication)
Wrong port set up (the server doesn't expect connections from port 22, for example)
No/wrong username/password stored for the connection
Server set up wrong and still denying where it should be accepting
Check all your settings to make sure everything is right.
HTTP code 501 stands for "not implemented". If the git server works over http using another client, the configuration on the client side is incorrect, so make sure you have configured the correct server address, user name and password. (If the git server doesn't work over http on any clients, the server configuration is incorrect.)