You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <de...@db.apache.org> on 2006/10/13 20:12:36 UTC
[jira] Commented: (DERBY-1275) Provide a way to enable client
tracing without changing the application
[ http://issues.apache.org/jira/browse/DERBY-1275?page=comments#action_12442076 ]
Mamta A. Satoor commented on DERBY-1275:
----------------------------------------
There have been discussion on this jira entry for 2 possible solutions.
1)One is to implement the way the server does, ie using something equivalent to derby.home on the client side.
2)The other is to explore JMX.
I don't have knowledge about JMX but seems like JMX could be used not just for the properties associated with this Jira entry but also for the properties in general supported by Derby. If that is the case, then may be it should be taken on as a feature by itself and for now implement this Jira entry in a fashion similar to what Derby server already does. Any thoughts on this, or other proposed solutions?
> Provide a way to enable client tracing without changing the application
> -----------------------------------------------------------------------
>
> Key: DERBY-1275
> URL: http://issues.apache.org/jira/browse/DERBY-1275
> Project: Derby
> Issue Type: Improvement
> Components: Network Client
> Affects Versions: 10.2.1.6, 10.1.3.1
> Reporter: Kathey Marsden
> Priority: Minor
> Fix For: 10.2.2.0
>
>
> Currently the client tracing can be enabled by setting attributes on the client url, setXXX methods on the DataSource or calling DriverManager.setLogWriter(), but it often cannot be enabled in a deployed client application because all of these API's require modification of the application or its configuration files.
> It would be good to have a global way to turn on client tracing. A system property pointing to a property file is one possibility but probably not ideal because of the impact in class loader contexts. I am not sure what the other possiblities are,
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira