Bug 966356

Summary:	debug port in jbossas-7.0 and jbossews-1.0 , jbosseap-6.0 ,jbossews-2.0 doesn't work sometimes
Product:	OKD	Reporter:	yangmingzhi <miyang>
Component:	Containers	Assignee:	Dan Mace <dmace>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.x	CC:	mshao, twiest, wdecoste, xtian
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-06-11 03:59:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description yangmingzhi 2013-05-23 06:52:49 UTC

Description of problem:
debug port in jbossas-7.0 and jbossews-1.0 , jbosseap-6.0 ,jbossews-2.0  doesn't work sometimes

Version-Release number of selected component (if applicable):
devenv_3262
STG(2.0.27.2)
rhc 1.8.9

How reproducible:
sometimes

Steps to Reproduce:
1. rhc app create app1 jbossas-7
2. touch app1/.openshift/markers/enabled_jpda
3. git push
4. ssh <app>
5. env | grep 127,  get the <internal-127-ip-of-app>
6. jdb -attach <internal-127-ip-of-app>:8787

Actual results:
6. [app3-hcx.stg.rhcloud.com 519daa88dbd93c0eba00001c]\> jdb -attach 127.11.153.1:8787
java.net.ConnectException: Connection refused
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
	at java.net.Socket.connect(Socket.java:579)
	at com.sun.tools.jdi.SocketTransportService.attach(SocketTransportService.java:222)
	at com.sun.tools.jdi.GenericAttachingConnector.attach(GenericAttachingConnector.java:116)
	at com.sun.tools.jdi.SocketAttachingConnector.attach(SocketAttachingConnector.java:90)
	at com.sun.tools.example.debug.tty.VMConnection.attachTarget(VMConnection.java:519)
	at com.sun.tools.example.debug.tty.VMConnection.open(VMConnection.java:328)
	at com.sun.tools.example.debug.tty.Env.init(Env.java:63)
	at com.sun.tools.example.debug.tty.TTY.main(TTY.java:1066)

Fatal error:
Unable to attach to target VM.
[app3-hcx.stg.rhcloud.com 519daa88dbd93c0eba00001c]\>

Expected results:
can input some command(eg:suspend)

Additional info:

Comment 1 Thomas Wiest 2013-05-23 14:26:32 UTC

Between steps 2 and 3 shouldn't you have done a "git add" and a "git commit" for the enabled_jpda marker file?

Could this explain the problem?

Comment 2 Bill DeCoste 2013-05-23 20:41:01 UTC

The marker is "enable_jpda" not "enabled_jpda"

Comment 3 yangmingzhi 2013-05-24 01:28:46 UTC

(In reply to Thomas Wiest from comment #1)
> Between steps 2 and 3 shouldn't you have done a "git add" and a "git commit"
> for the enabled_jpda marker file?
> 
> Could this explain the problem?

I used "git add ." and “git comment -a -m 'my comments'" before "git push"

Comment 4 yangmingzhi 2013-05-24 01:33:38 UTC

(In reply to Bill DeCoste from comment #2)
> The marker is "enable_jpda" not "enabled_jpda"

I used "enable_jpda" when testing, but wrote "enabled_jpda" when filing a bug,
sorry for my mistake,but I use "enable_jpda" indeed.

Comment 5 yangmingzhi 2013-05-24 02:41:14 UTC

Verified in STG(2.0.27.2)