This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
I am using the dm server's application level trace mechanism. No matter what I try, the method name comes as "unknown" in the trace. I am probably missing something too obvious. Any pointer or a bang in the head would be much appreciated.
No bang in the head needed This is working as (currently) designed.
In dm Server 1.0, dm Server's code is weaved with an aspect that makes the method name and line number for a trace call available in a way that is very inexpensive. When a 'normal' tracing API is used this information isn't available, and determining it is very expensive as it requires taking a snapshot of the thread's stack. As a result of this expense, dm Server opts to track unknown for the method name.
This is an area that we will improve in dm Server 2.0. We plan to replace dm Server's tracing support with a LogBack-based implementation. This will make all of the power of LogBack available to your applications, e.g. you'll be able to configure an appender with a pattern that includes the method name if you so chose.