1
0
-1

Hi.

After migrate from previous TM version (like 5.x) you should update your logger implementation to take advantage of the TM fix that avoid loosing some groovy service logs when you have embedded calls to other groovy services.

This is an snippet from previous TM versions:

import com.avoka.core.groovy.GroovyLogger as logger
import com.avoka.tm.vo.*
import javax.servlet.http.*

class FluentGroovyService {
Object invoke(SvcDef svcDef, HttpServletRequest request, User user, Map params) {
logger.debug "..."
}

This is an snippet on TM 17.10 and later:

import com.avoka.tm.util.*
import com.avoka.tm.vo.*
import javax.servlet.http.*
class FluentGroovyService {
public Logger logger
Object invoke(SvcDef svcDef, HttpServletRequest request, User user, Map params) {
logger.debug "..."
}

The com.avoka.core.groovy.GroovyLogger as logger works on TM 17.10 but it has the same problem that on previous TM versions.


    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      Hi Salvador,

      I would recommend using:

           logger.info(  ) 

      instead of

           logger.debug "..."




        CommentAdd your comment...