[
https://issues.apache.org/jira/browse/DERBY-5819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405309#comment-13405309
]
Dag H. Wanvik commented on DERBY-5819:
--------------------------------------
Committed version d as svn 1356457. Commit log:
Adds options to allow this capability for Oracle Java (properties below
ignored for other implementations):
derby.test.debugPortBase=<int> default 8800
derby.test.debugSubProcesses=<boolean> default false
derby.test.debugSuspend=<y|n> default 'y'
If several subprocesses are created, the port for subprocess two will be
debugPortBase + 1 (i.e. 8801 by default) etc.
> Add logic to BaseTestCase to start subprocesses ready to be attached to from
> a Java debugger
> --------------------------------------------------------------------------------------------
>
> Key: DERBY-5819
> URL: https://issues.apache.org/jira/browse/DERBY-5819
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Priority: Minor
> Attachments: derby-5819.diff, derby-5819b.diff, derby-5819c.diff,
> derby-5819d.diff
>
>
> Sometimes it's useful to be able to attach to subprocesses of tests with a
> debugger.
> Now that we have centralized subprocess creation in BaseTestCase#execJavaCmd
> it would be easy and useful to have subprocesses start, but wait for a
> debugger to attach to them, i.e. with these options on an Oracle VM:
> -Xdebug -Xrunjdwp:transport=dt_socket,address=<port>,server=y,suspend=y
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
