You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Rob Davies (JIRA)" <ji...@apache.org> on 2008/09/02 09:17:52 UTC
[jira] Resolved: (AMQ-1887) Wrap the debugging variables in
conditional expressions to enable them easier
[ https://issues.apache.org/activemq/browse/AMQ-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-1887.
-----------------------------
Resolution: Fixed
patch applied in SVN revision 691131
> Wrap the debugging variables in conditional expressions to enable them easier
> ------------------------------------------------------------------------------
>
> Key: AMQ-1887
> URL: https://issues.apache.org/activemq/browse/AMQ-1887
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.1.0
> Reporter: Bruce Snyder
> Assignee: Rob Davies
> Fix For: 5.2.0
>
> Attachments: AMQ-1887.diff.txt
>
>
> The activemq shell script for startup contains some variables for debugging, but they are commented out. This requires hand editing instead of just setting a variable on the command line to conditionally. So I wrapped the debug variables in conditionals to make it easier to enable debugging features. So now if I want to enable remote debugging on ActiveMQ, I do the following:
> {code}
> [apache-activemq-5.1.0] $ ACTIVEMQ_DEBUG=true ./bin/activemq
> Listening for transport dt_socket at address: 5005
> ACTIVEMQ_HOME: /Users/bsnyder/amq/apache-activemq-5.1.0
> ACTIVEMQ_BASE: /Users/bsnyder/amq/apache-activemq-5.1.0
> Loading message broker from: xbean:activemq.xml
> ...
> {code}
> Remote debugging and YourKit debugging can now be enabled easily without a requirement to edit the script.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.