I am trying to run GWT Junit tests in eclipse Juno (right-click on test case file and "run as GWT JUnit test case"). However, JUnit fails with an exception saying the connection refused on an IP address other than the one of my client machine.
(I'm manually inserting an extra space in the URLs to avoid stackoverflow blocking the post because of bad URLs).
Starting http://192.168.1.234:46278/org.me.MyProject.JUnit/junit-standards.html?gwt.codesvr=192.168.1.234:46971 on browser FF3
logging for HtmlUnit thread
[ERROR] I/O error on HTTP request
org.apache.http.conn.HttpHostConnectException: Connection to http://192.168.1.234:46278 refused
My machine's IP address is 192.168.1.3. I have no clue from where eclipse got the other IP. Where does eclipse get the erronous address and how can I change it, preferably to 127.0.0.1?
The answer to the above question was that there was a malconfigured DNS server involved. Eclipse read the hostname of the machine and resolved it to the wrong IP number.
Related
I installed Eclipse and the Jboss Tools plugin with Wildfly.
I can run Wildfly in Eclipse in non-debug mode with no problems. But when I start Wildfly in debug, I can use it for a few minutes, and then it suddenly stops processing, the server ends.
I checked the log and there's nothing. What could be wrong?
Please note the JBoss Tools 4.9.0 is validated against 2018-09 but not against 2018-12.
Do you see something in the server log when the server dies ?
We had this issue and it was because we changed our config to close the management port, which had been used to detect that the server had started. Eclipse could no longer detect that the server had started, so it shut down the process after a set time (450 seconds)
To resolve the issue, we did the following in the Eclipse's Overview panel for our JBoss Server:
Changed the Start Timeout to 30, so it would only fail if it actually couldn't start in 30 seconds rather than waiting for 450
Changed our "Server State Detectors" to detect a Web Port for Startup Poller and Process Terminated for Shutdown Poller.
Changed the Server Ports to match our new configuration
Excerpt from JBoss Community Archive
The tooling was unable to verify your server started. Our tooling has several methods to see if your server is up or not. The two most-often used methods are either "Web Port Poller" or "Management Poller".
You can see which your server is using by opening the server object (In Servers view, double-click your server) and on the right side you'll see a section on polling.
If your server adapter (fancy word for the tooling's representation of your server) is using the Management Port Poller, you should make sure your server is actually exposing the management port. For local servers this shouldn't be an issue, since local servers should automatically expose the management port. You may want to verify in the Ports section (also in the server editor) that the management port is correct. To check if the server is up, we run a management command against the server. If the server responds properly, we declare the server to be started.
If you're using the web port poller, then you may want to verify your web port is correct. To verify the server is up, the Web Port Poller opens a URL connection on {serverHost}:{webPort} and sees if we get a valid connection.
I'm attempting to debug a program running in WebSphere Liberty Profile, so I run this on the server:
./server debug
This prints out
Listening for transport dt_socket at address: 7777
In IntelliJ IDEA, version 13.1.3, I try:
Run > Edit Configurations > + > Remote.
I pick Socket, Attach, fill in the hostname, and enter the port number of 7777, give it a name, and then OK.
Run > Debug > Pick the name I just gave it.
It opens a debugger tab and after ~30 seconds it displays the message
Error running (debugger configuration name):
Unable to open debugger port:
java.net.ConnectException "Connection timed out: connect"
(Line breaks added to make it easier to read).
I can then launch Eclipse, Kepler Service Release 2, and do
Run > Debug Configurations... > Remote Java Application > New > give it a name, pick Socket Attach, give it the host name and port number of 7777, click Apply, and Debug.
And it works just fine.
The fact that I can run Eclipse and have it work fine and IntelliJ and have it fail at the same time indicates to me that the problem isn't anywhere on my server and it's not an issue with my network connection.
It seems to me that the problem must lie somewhere in how I've set up IntelliJ. So my question is: what could I have done right with Eclipse that I'm getting wrong with IntelliJ?
The error message shows that IntelliJ IDEA can't establish a network connection to the debuggee process. One common reason for this problem is a local firewall rule that blocks network connections from IntelliJ IDEA.
I am trying to debug server side code (running on Tomcat) using eclipse's remote debug option. This issues is showing up intermittently and rest of the times it works just fine. I have made sure
1) Server side has got the latest Jars - I copied the .war file and redeployed.
2) Tomcat is running on debug mode and firewall settings have been modified to allow connections on the debug port.
3) Verified that before the attempt to connect, on the server its listening on the debug port and afterwards it shows that connection has been established.
but Eclipse is throwing an error popup saying "Its unable to connect to the remote VM" and sometimes it times out waiting for a packet #
Should I be checking for some more things? Are there any more log files by eclipse that throws light on what went wrong? Please help
This is can be a solution sometimes if your debugger fails to connect to debugger with an error something like "timed out while waiting for a packet #packetnumber" then it could be because of the low timeout setting and slow network. One can increase the timeout value using debug setting in the eclipse preferences.
Ive been trying to get an example Web Service working using SpringWS and Tomcat5.5
Ive followed examples such as:
1)http://justcompiled.blogspot.com/2010/09/building-...eb-service-with-spring-ws.html
2)http://jamesbnuzzo.wordpress.com/2009/04/14/spring...s-with-jaxb-maven-amp-eclipse/
The latter has an ZIP file which includes the WAR to drop into Tomcat
In both examples the Web Service runs and I can view the WSDL file (eg:http://localhost:8080/eightball/eightball.wsdl)
However, when I startup SOAPUI version 3.6.1, import the WSDL, set the endpoint for example to http://localhost:8080/eightball/eightball, and then try to submit a request to that endpoint, I get the following error.
Fri Nov 05 19:49:05 GMT 2010:INFO:Error getting response for [eightballSoap11.eightBall:Request 1]; java.net.ConnectException: Connection refused: connect
With the 1st example I used Eclipse Helios to develop and publish the WebService to Tomcat. Using SOAPUI in this scenario worked and I got the expected Responses back.
When I exported the same project to a WAR file and deployed on Tomcat, I got the SOAPUI connection exception ?!?!
Can anybody please help....
Which SOAP-Version does the Tomcat/SpringWS use, there might be a discrepancy between SOAP 1.0 and 1.2
I resolved this problem by adding in address="0.0.0.0" to the Connector element in server.xml.
The problem identified also meant that Tomcat could not be reached on address 127.0.0.1:8080 and only by localhost:8080
I think its all down to how Windows was listening on the loopback address for IPv4 and IPv6.
I'm trying to write a Servlet in eclipse configured to use Tomcat 5.5 and I get the following error when I try to run it:
Several ports (8080, 8009) required by Tomcat v5.5 Server at localhost are already in use. The server may already be running in another process, or a system process may be using the port. To start this server you will need to stop the other process or change the port number(s)
As far as I know, Tomcat 5.5 is the one using port 8080, and when I go to http://localhost:8080 I do get the Tomcat success page, so it looks like eclipse tries to run another instance of Tomcat without shutting down the original and fails. How do I solve this?
like it says, something is using the port.
there are two solutions for your problem.
identify (on windows with netstat command) what is using the port (e.g. skype, ...) and stop it
change the port of your tomcat runtime in eclipse -> http://techteam.wordpress.com/2009/02/13/changing-the-tomcat-port-settings-in-eclipse/
hope this helps