[ 
https://issues.apache.org/jira/browse/QPID-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908076#comment-14908076
 ] 

ASF subversion and git services commented on QPID-6695:
-------------------------------------------------------

Commit 1705311 from [email protected] in branch 'java/trunk'
[ https://svn.apache.org/r1705311 ]

QPID-6695: Log sensible information for tasks in TaskExecutor

           work by Lorenz Quack <[email protected]> and Alex Rudyy 
<[email protected]>

> Make model tasks have useful toStrings so that task submit/completion debug 
> logs are useful
> -------------------------------------------------------------------------------------------
>
>                 Key: QPID-6695
>                 URL: https://issues.apache.org/jira/browse/QPID-6695
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Keith Wall
>            Assignee: Keith Wall
>         Attachments: 
> 0001-QPID-6695-Sensible-information-should-be-logged-for-.patch
>
>
> At the moment, when running the Broker at debug, we currently write the 
> following as each task is submitted to the task executor:
> {noformat}
> 2015-07-31 15:29:45,096 DEBUG [VirtualHostNode-bdb-Config] 
> (o.a.q.s.c.u.TaskExecutorImpl) - Task 
> org.apache.qpid.server.model.AbstractConfiguredObject$2@201982d
> is performed successfully with result: null
> 2015-07-31 15:29:45,116 DEBUG [VirtualHostNode-bdb-Config] 
> (o.a.q.s.c.u.TaskExecutorImpl) - Task 
> org.apache.qpid.server.model.AbstractConfiguredObject$2@73dc353
> 4 is performed successfully with result: null
> {noformat}
> The ability to diagnose errors would be improved if the logging were improved 
> to include the details of the operation and the action being performed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to