- This topic has 8 replies, 3 voices, and was last updated 8 years, 9 months ago by
.
-
Posts
-
Hi,
When we are starting the server in Debug Mode; code execution doesn’t stops at the breakpoints.
Configuration is Myeclipse 2014 with WAS 8.5.
Please let me know if you need any other detailRaichu,
Sorry that you are seeing this issue.
1. Are you doing a remote debug?
2. If you are debugging on a local WAS, then can you please verify if the ‘Skip All Breakpints’ is enabled ? Also make sure no other process is taking up the Debug port.
3. Can you check if clean-build-republish of the project fixes the issue?
4. If possible, switch to a new workspace, import the project, configure the server and check if the issue persists.
5. If you are still seeing issues, please share with us the exact version of WAS along with the deployment mode (Classic/In-Workspace). If possible, please also share with us the sample project which exhibits the issue to help us replicate the issue at our end.
6. Please check the .log file located at workspace dir>/.metadata/.log for any errors of interest. If any errors are logged, then please send us the .log file.Let us know how it works for you.
–Swapna
MyEclipse SupportHi Swapna,
Thanks for the reply. Please find my replies inline with your queries:
1. Are you doing a remote debug? — No
2. If you are debugging on a local WAS, then can you please verify if the ‘Skip All Breakpints’ is enabled ? Also make sure no other process is taking up the Debug port. – Skip All BreakPoints was not enabled..But when I enabled it & tried ; that didn’t help. For debug port i have placed log at last of all replies.
3. Can you check if clean-build-republish of the project fixes the issue? — Tried didn’t solve
4. If possible, switch to a new workspace, import the project, configure the server and check if the issue persists. — No doesn’t helps
5. If you are still seeing issues, please share with us the exact version of WAS along with the deployment mode (Classic/In-Workspace). If possible, please also share with us the sample project which exhibits the issue to help us replicate the issue at our end. — I will try on that
6. Please check the .log file located at workspace dir>/.metadata/.log for any errors of interest. If any errors are logged, then please send us the .log file. — Please see below log lines!MESSAGE Cannot connect to debug port
!STACK 1
org.eclipse.core.runtime.CoreException: Failed to connect to remote VM
at org.eclipse.jdt.internal.launching.SocketAttachConnector.abort(SocketAttachConnector.java:96)
at org.eclipse.jdt.internal.launching.SocketAttachConnector.connect(SocketAttachConnector.java:154)
at com.genuitec.eclipse.core.JavaVMUtility.launch(JavaVMUtility.java:723)
at com.genuitec.eclipse.blue.websphere8.WSPingThread.execute(WSPingThread.java:142)
at com.genuitec.eclipse.blue.websphere8.WSPingThread.waitForServerToStart(WSPingThread.java:111)
at com.genuitec.eclipse.blue.websphere8.WSPingThread.run(WSPingThread.java:51)
Caused by: java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:152)
at java.net.SocketInputStream.read(SocketInputStream.java:122)
at java.io.DataInputStream.readFully(DataInputStream.java:195)
at java.io.DataInputStream.readFully(DataInputStream.java:169)
at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:216)
at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:212)
at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:183)
at java.lang.Thread.run(Thread.java:744)Please let me know if through this log you are able to give some suggestions.
raichu,
Are you behind a firewall? If yes, then can you please turn off the firewall and see if it fixes the issue?
It might be possible that the firewall is closing the connection.Can you also try starting MyEclipse as admin and see if the issue persists? Right click on myeclipse.exe > Run as administrator.
–Swapna
MyEclipse SupportRaichu,
Sorry you are still seeing the issue. There seems to be an issue in MyEclipse Blue 2014, whereby the software is trying to connect to the debug port before it is open. If you have this problem, there are two possible ways to address it.
Firstly, this is not an issue in MyEclipse 2015. Can you install 2015 and see if this solves the problem? Server connectors have changed in 2015. There is a large amount of information about the new server connectors, in our learning center but this FAQ would be a good place to start. Here is a Learning Center article specifically for WebSphere connectors.
Alternatively, there is a workaround for MyEclipse 2014, though this would be less convenient. You can create a Debug Launch Configuration. Go to Run->Debug Configurations then double click on “Remote Java Application”. Now enter a name for the configuration and fill in the project name, for the project you want to debug on the server, the host (“localhost”, usually) and the port number (this will be 7777, by default but you can check in the WAS console). See the attached screenshot for reference. Click Apply and then Debug to start the debugging session. Thereafter, this debug configuration should be in your Debug history (Run->Debug History) and in the drop down of the Debug button on the toolbar. Use this debug configuration together with the server connector, in the Servers view. Start the server in debug mode, wait for it to complete initialization, and then run the debug configuration.
Please let us know if this helps and apologies for the inconvenience.
