You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Hans Zeller (JIRA)" <ji...@apache.org> on 2015/07/29 19:39:09 UTC
[jira] [Updated] (TRAFODION-35) Add a method that allows UDR
writers to debug their UDRs on a release build
[ https://issues.apache.org/jira/browse/TRAFODION-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hans Zeller updated TRAFODION-35:
---------------------------------
Issue Type: Sub-task (was: Improvement)
Parent: TRAFODION-38
> Add a method that allows UDR writers to debug their UDRs on a release build
> ---------------------------------------------------------------------------
>
> Key: TRAFODION-35
> URL: https://issues.apache.org/jira/browse/TRAFODION-35
> Project: Apache Trafodion
> Issue Type: Sub-task
> Environment: release build
> Reporter: Hans Zeller
> Assignee: Hans Zeller
>
> Today, we have various methods to put the JVM into debug. These are mostly based on environment variables. All these methods require a debug build. That won't work for a Trafodion user who wants to write a Java UDR, since setting up a debug build is not a trivial exercise. We need to allow UDR debugging on a sandbox VM or on a cluster, running a release build.
> Therefore I am proposing that we allow the DB__ROOT user to put JVMs into debug mode, even on a release build. Given the extensive power DB__ROOT already has, this is not a significant increase in what that user can do.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)