We Keep Coding

503 Service Unavailable in Mule

I am getting 503 Service Unavailable when call in Mule application... Call is not reaching to HTTP Listener I think and beside of HTTP Listener there is Set Variable... to Set Variable also not reaching call... Till day before yesterday it was working in all work spaces but suddenly it is not reaching to listener when I was trying after putting debug mode. But for other developer is not having any issue and he is able to receive call to Listener and other components. Current configurations everything is good. Can you please suggest what needs to check.

I had the same problem when I added an autodiscovery configuration for my application. Adding this to VM arguments folved my issue.
-Danypoint.platform.gatekeeper=disabled

I faced the same problem.
Everything was working, and suddenly (don't know why) I received the same 503 response.
I tried a lot to figure out what was going on.
Added new listeners and tested existing flows, which all went well.
Only my particular listener with the APIKit was never getting reached anymore.
I also disabled 'the gatekeeper' as suggested in the following article :
API-returns-503-Service-Unavailable-error-to-clients
Run -> Run configurations -> tab Arguments
I exported the project to a deployable archive file, with the checkbox 'only export project sources' selected. Tested this application on different PC's which went well.
Created a new workspace on my PC, imported the file , and the application failed again.
After a few other try & errors, I enabled the 'clear application data' -> 'prompt' selection box, and I disabled the 'APIKit settings' -> 'Show APIKit consol'.
I'm not sure if that consol had something to do with it, but after restarting the application and select YES on Clear application data , it worked well again.
Run configurations
I re-enabled the 'show APIKit consol' again, and it still worked fine.
This should solve your problem as well.

This is basically the same answer as the answer provided by user15476634, but with a visual description, and reasons why this error may occur.
For those who are wondering where to find Clear Application Data, please see below screenshot.
Most usual suspects in these type of issues is corrupted Application data due to following issues:
Trying to open multiple test consoles at a time
Working on huge payload and not enough memory allocated
Accidentally selecting the multiple run configurations and/or debug configurations at once
when you try to re-run the same app while an instance is already
running by disregarding the prompt/warning window (Do you want to stop the running application and start ...?)

For me, I had the same experience, the 503s appeared out of nowhere. Clearing application data did not work for me, setting
-Danypoint.platform.gatekeeper=disabled
did not work for me. I had to remove this xml tag from my global config
<api-gateway:autodiscovery ... />

It happened to me after turning on autodiscovery in order to deploy, so i had to remove these lines (autodiscovery) temporary then test then return these lines back in order to deploy

Debugging web service with Intellij

I work with a web service (SOAP) that is installed on a remote server (Websphere). Since I do not fully understand its operation, I would like to use debugging to understand the code step by step. I want to use the local instance Intellij (ultimate). My problem is that due to little experience I do not know how to do it. I have questions:
to check the operation of WS I want to send queries to the server using SOAPUI. Is there a possibility for me to look at Intellij (using breakpoints) what values are returned at a given stage?
how to connect it all together?
is there a different, better way to check the code?

First, make sure that debug is enabled on your remote server. This can probably be configured in Websphere. Then, in IntelliJ select the "run configurations" dropdown and "Edit Configurations". Hit the "+" and select remote. Set the correct host and port, and click "OK". Then, start the run configuration in debug mode, add some breakpoints and debug away!

Azure deployment hanging in Eclipse

I previously did not have any issues with this, as I have been deploying Azure web app from Eclipse with no issue. Usually it takes a few minutes, but currently it is taking forever with no real progress from what I can tell. I have tried restarting Eclipse as well as deleting the Azure app and recreating a new one. None of those work. Are there some settings I need to reset ?
EDIT: Yes it is a Web App created in Azure, and I previously had no trouble deploying at regular intervals. Last time however I wanted to abort the deployment and attempted to do so in Eclipse but it kept running and it seemed to be hanging so I shut down Eclipse and tried to deploy again but instead of taking just a few minutes, now it is stuck at the beginning with no progress.
I then decided to delete the web app, create a new one, and deploy to the new web app from Eclipse, but it is still the same with no progress.
EDIT: Adding Screenshots of the general environment and Azure configuration.

Just summarize for the above comments, the issue seems that Azure WebApp waits timeout to recover or reset for a failed deployment connection, so a suggestion is that trying to restart the Azure WebApp to recover or reset all status of the current instance fastly, or wait awhile then try to reconnect again.
But for some similar cases, if the above action failed, it's necessary for considering some metadata files in the current workspace, a valid way may be to create a new workspace to try to reconnect.

GWT RPC call gets repeated after 30 seconds

I am experiencing a weird problem in a GWT application. I have multiple RPC calls which work correctly, however if one of them takes longer than 30 seconds on the server side (for example a database or web service call took a long time), the server side code gets repeated (literally; the code get executed again).
I do not experience this in my develompent environment, however when I deploy the application (container is Jetty 6.1.24 on Ubuntu 12.04 LTS) and connect to it from a browser (regardless of the type), the problem starts to exist.
Since I do not think this a designed GWT behaviour (but I might be wrong ofcourse) I am basically looking for ways to debug this and find out the reason for it. Thanks in advance!

Some more information would be great to understand what is going on, but I would start the investigation by first narrowing down whether the erroneous GWT-RPC call is triggered on the client or server.
To see if the extra GWT-RPC request originates from the browser, in Google Chrome, go to View->Developer->Developer Tools.. Click on the Network Tab.
As you reproduce your steps, the Network Tab will show you every request sent to the server.
If you see the erroneous GWT-RPC request logged in this Network Tab View, then the request is fired off from the GWT-compiled Javascript in the application. With SuperDevMode, you can then set debug breakpoints in the browser and see what is triggering the request.
If the erroneous GWT-RPC is not shown in the Network Tab View, then the server-side method is somehow triggered by your server code/configuration. Set some debug breakpoints on your server code, and drill down the call stack to see what is calling the method.
Hope that helps to get started on the investigation.

Run a Java class on Eclipse automatically without pressing the "run" button

I'm programing for a Socket(Client-Server) ,I want my client run automatically after turning on my Server without pressing the "run" button at the class of Client.
Can Anyone help me?

Although it doesn't directly entail using Eclipse, you can create a shell script that starts first your server (possibly checking that your server ran properly) and then your client. That is the simplest way to run the client upon starting the server.
Another approach is to create a Java class in Eclipse that successively starts the server and client modules.