Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
V1Alpha, V1Beta, v1m1
-
None
-
None
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.