You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erik Hatcher (Updated) (JIRA)" <ji...@apache.org> on 2012/03/28 18:47:26 UTC

[jira] [Updated] (SOLR-3291) Update "ant run-example" JVM debugging command-line switches

     [ https://issues.apache.org/jira/browse/SOLR-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Erik Hatcher updated SOLR-3291:
-------------------------------

    Fix Version/s: 4.0
    
> Update "ant run-example" JVM debugging command-line switches
> ------------------------------------------------------------
>
>                 Key: SOLR-3291
>                 URL: https://issues.apache.org/jira/browse/SOLR-3291
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Erik Hatcher
>             Fix For: 4.0
>
>
> Our current run-example target uses {code}-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=${example.debug.suspend},address=5005{code}
> but I've heard that it can be done without -X arguments like this 
> {code}-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y{code}
> What's the most up-to-date best way to enable JVM debugging?  Are changes warranted?

--
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org