[ http://issues.apache.org/jira/browse/BEEHIVE-791?page=all ]
Chad Schoettger updated BEEHIVE-791:
------------------------------------
Component: System Controls
(was: Controls)
Description:
Currently, the jms control doesn't log anything. Add some logging and use
commons-logging to do it.
Points that debug logging would be helpful:
- session created was transacted or not
- message type used
- destination type used
The JMS control does lots of magic and the debug logging would be helpful. My
definition of magic is the 'Auto' resolution for message type and destination
type.
was:
Currently, the jms control doesn't log anything. Add some logging and use
commons-logging to do it.
Points that debug logging would be helpful:
- session created was transacted or not
- message type used
- destination type used
The JMS control does lots of magic and the debug logging would be helpful. My
definition of magic is the 'Auto' resolution for message type and destination
type.
Environment:
> add commons logging to jms control
> ----------------------------------
>
> Key: BEEHIVE-791
> URL: http://issues.apache.org/jira/browse/BEEHIVE-791
> Project: Beehive
> Type: Improvement
> Components: System Controls
> Versions: V1Alpha, V1Beta, v1m1
> Reporter: Jeremiah Johnson
>
> Currently, the jms control doesn't log anything. Add some logging and use
> commons-logging to do it.
> Points that debug logging would be helpful:
> - session created was transacted or not
> - message type used
> - destination type used
> The JMS control does lots of magic and the debug logging would be helpful.
> My definition of magic is the 'Auto' resolution for message type and
> destination type.
--
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
