0 Replies Latest reply on Feb 23, 2009 5:37 AM by Martin Vecera

    Log level for action processing failures

    Martin Vecera Novice

      Hello,

      as I have LC_ALL=cs_CZ, I sometimes experience problems with parsing a date string. The same happened to me with a test based on bpm_orchestration4.

      I have a service like this:

      <service category="BPM_Orchestration4" name="IntakeService" description="IntakeService: transforms, massages, calculates priority">
       <listeners>
       <jms-listener name="ESB-Listener" busidref="intakeServiceEsbChannel" maxThreads="1" />
       </listeners>
       <actions>
       <action name="dump1" class="org.jboss.soa.esb.actions.SystemPrintln">
       <property name="message" value="INTAKE START" />
       <property name="printfull" value="true"/>
       </action>
      ...
       <action name="transform" class="org.jboss.soa.esb.actions.converters.SmooksTransformer">
       <property name="resource-config" value="/smooks-config.xml" />
       </action>
       <action name="testReport4" class="org.jboss.soa.esb.qa.framework.ReportAction">
       <property name="originator" value="smooksTransform" />
       </action>
      ...
      


      And I wondered why the action testReport4 is never called. I was using SOA-P 4.3 CP01 with log4j configuration from the 'all' configuration. I saw no exception at all.

      When I switched log4j to debug level I revealed this problem:
      Caused by: org.milyn.javabean.DataDecodeException: Error decoding Date data value 'Wed Nov 15 13:45:28 EST 2006' with decode format 'EEE MMM dd HH:mm:ss z yyyy'.
      

      It took me some time to localise the issue in the Smooks transformer and find the root cause. It would be much easier if ActionProcessingPipeline showed the problem at INFO level at least. Now it is shown at DEBUG level and it optimistically supposes that there is no error second time. Way too optimistic I'd say ;-)