java.lang.RuntimeException: Method code too large [Transformation – script map]

    • Dhanasekar
      2 years, 9 months ago #3511

      Is there any limit in the lines of code in our ebonding Tranformation Script mapping (preblock / param mapping) ?
      If so what is the limit ? and how to handle such scenarios ?

      we observe this exception,

      com.digitate.ignio.log.LogAspect:?|?|Error in service Map com.digitate.ignio.platform.actionmapper.service.ActionMappingService.getCatalogMapping(Map, String, String, String) com.digitate.ignio.utils.exception.IgnioInvalidRequestExeception: Exception Context: [1:INTERACTION_ID=93ca2cb1-3867-412c-a953-ebc847aa1c3a] [2:USER_ID=null] --------------------------------- 422startup failed: General error during class generation: <strong>Method code too large! java.lang.RuntimeException: Method code too large!</strong> at groovyjarjarasm.asm.MethodWriter.getSize( at groovyjarjarasm.asm.ClassWriter.toByteArray( at org.codehaus.groovy.control.CompilationUnit$ at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes( at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation( at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(

    • santoshk
      2 years, 9 months ago #3513

      In groovy mapping section – It is recommended to keep the code smaller and readable – 20-30 lines.
      You can use the library to refactor the larger code in multiple methods, classes.

Viewing 1 reply thread

You must be logged in to reply to this topic.