I'm able to create a simple Web project in Eclipse that has a simple single HelloWorld servlet. I'm able to debug this fine with the local Tomcat (setting breakpoints in the index.jsp or in the servlet), which land when I try the sample URL:
http://localhost:8080/RemoteDebugTest/HelloWorld
However, when I try to use the Eclipse debug configuration for a remote java application, I am able to connect and see the server threads, but my application does not deploy, and the URL appears as if the web module never deployed. (There are 404 errors for the same URL above.) Help me StackOverflow, you're my only hope.
Things I have tried:
Set environment variables such as JPDA_ADDRESS to 8000, JPDA_TRANSPORT to dt_socket.
Set those in the catalina.sh (on a remote linux Tomcat7 server) or catalina.bat
Run the catalina startup script with jpda run, or with jpda start
I've extensively scoured online resources and noone else seems to have this problem, other than one article that simply recommended Jetty. (I came from a background of never having a problem with this using WAS.)
Other pieces of info:
OS: Windows 7 (64-bit)
Tomcat 7.0.0.28
MyEclipse 10 (based on Eclipse 3.7.2)
Related
I need to be able to "remotely debug" a Java/Jakarta EE servlet running under Wildfly 20 under Ubuntu 20 from Eclipse 2020-06 running on Windows 10 at a different IP.
My research has discovered what appears to be two different approaches: one is what I want and the other is a simpler "subset".
*** First the "simple" approach. This approach is supposed to let me debug from Eclipse an app that is already deployed and running on Wildfly. To do this I uncomment this line in standalone.conf:
JAVA_OPTS="$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"
Then I start Wildfly and ensure the app also starts.
In Eclipse I create in Debug Configuration a new Remote Java Application and ensure I use the same port 8787 as above. Then I just push "Debug".
I get this error:
Failed to connect to remote VM. Connection refused. Connection refused: connect
If I return to the Wildfly system and run the following I see that port 8787 is not being monitored so that sure looks like a problem:
ss -tp | grep 8787
(nothing is found)
*** The other approach appears to be what I want to do which is to have Eclipse deploy changed files to Wildfly and also allow me to debug remotely. That is how I worked with Eclipse Oxygen and Wildfly 10 when both were installed on the same Windows machine.
In this case I set up a new Remote Connection in Eclipse and then a new Server (and attach my Project to the Server) using that Connection. I then start the Server in Debug mode. In the Progress View I can see files being copied to a Path on the Wildfly server so that seems like progress but after 20 seconds I see the same error I got in the "simple" approach above.
Failed to connect to remote VM. Connection refused.
What's interesting is that if, in the Remote Systems View I open the Remote Connection I created, I am able to use the sftp item to see files on the remote Wildfly system. So it seems that I am able to connect to Wildfly.
I need help fixing both of these problems but especially the last one since I need to have Eclipse deploy changes to Wildfly as it did when Wildfly was local.
Thank you in advance.
I'm new to Jboss.
I tried everything: the Jboss documentation, YouTube videos, but I'm out of luck.
I'm using Redhat Developer to run quickstart examples like helloworld but I don't know why I am having this POM.xml error. I follow everything but still I'm getting this error.
As you can see the server is running good but I cannot see the option run as server.
I'm using Win 10 and Jboss eap 7.1 for runtime.
error
error
fullimage
progress
I am working on my own, learning about Java servlets and JSPs. My machine configuration as follows is from NetBeans' About page.
Product Version: NetBeans IDE 8.0.1 (Build 201408251540)
Updates: NetBeans IDE is updated to version NetBeans 8.0.1 Patch 1.1
Java: 1.8.0_20; Java HotSpot(TM) 64-Bit Server VM 25.20-b23
Runtime: Java(TM) SE Runtime Environment 1.8.0_20-b26
System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
Tomcat 8.0.14 for Windows x64 is also installed as the web server.
I created a tiny web app yesterday, which was working as expected. When I went to the next exercise in the book, it was necessary to install MySQL. That seemed pretty straightforward, but alas, the install ran into a couple of problems. Unfortunately, I had not created a restore point right before that attempt, so I went back to the restore point created before the Tomcat install.
I re-installed Tomcat, and as a sanity check, started it, started NetBeans, tried to the run the tiny web app and after removing the server and re-adding it (because I got an error about the server) in NetBeans, got a message that I needed to set the build.dir.
For a tiny app, this is just annoying, but when working on a large app, it would be nice to avoid this problem. Another book author supplied app was working before, and is still working so...
Here are my questions:
1) Why/how would simply re-installing Tomcat cause a break in something that was working?
2) It seems as if the build.dir is set in build-impl.dir (in the app that is working) with a statement like (the opening and closing tags are missing so the statements would appear):
property location="${build.dir}/empty" name="empty.dir"
One post I read somewhere said that the above statement should be before the:
fail unless="build.dir">Must set build.dir
3) How/where is this build.dir set during the creation of a NetBeans web app? Is there some dialog box that I'm not completing correctly? If I miss it, is there a way to get back to it after the app gets "confused"?
Thanks in advance for any help on this.
I have just installed Netbeans 7.3. Prepared a sample web application.
But Glassfish does not start.
Error message is "....\nbproject\build-impl.xml:1036: Deployment error: GlassFish Server 3+ Server start failed. Cant create start proccess.
See the server log for details."
Unfortunately nothing in the server log.
I deleted domains folder and server then recreated. Nothing changed. :(
Is it a bug related to http://netbeans.org/bugzilla/show_bug.cgi?id=217228 ?
Any solution?
My system is 64 Bit Windows 7 with Turkish locale.
Web application is Primefaces based, JSF 2.1
I think this is about language settings.
You can change localization settings in the netBeans configuration file($NETBEANSHOME/etc/netbeans.conf).
Just add "--locale en" to end of the "netbeans_default_options" line.
Also you can start glassfish with asaadmin tool with following these steps.
1- execute C:\Program Files\glassfish-3.1.2.2\bin\asaadmin.bat
2- start-domain
I'm able to start WebLogic Server 11gR1 PatchSet 2 on my local machine and my web application is accessible after starting up WLS, yet I'm getting errors in my Eclipse Galileo Error Log on startup. Here's the messages I'm getting in ascending order:
Started WebLogic Server Monitor [mydomain#localhost:7001, Version:10.3.3.0]
Unable to find tools.jar within Java VM associated with target WebLogic runtime; features dependent on tools.jar may not function
The server cannot be launched within timeout.
Server Oracle WebLogic Server 11gR1 PatchSet 2 at localhost was unable to start within 480 seconds. If the server requires more time, try increasing the timeout in the server editor.
I've increased the timeout setting to 480 seconds (8 minutes) and one would think that's sufficient enough time for the startup.
I am able to run my web application successfully and output is generated on the Console as well so the last three error messages in the bullets above aren't show stoppers.
Wondering if any of you have run across these errors and how you went about to resolve them.
Upgraded to latest version of Eclipse Java EE (Indigo SR2 for win32) and was able to launch it with no issues.