[esb-issues] [JBoss JIRA] Created: (JBESB-3104) SmooksAction reports error when routing csv fragments via JMS

Edward Pilipczuk (JIRA) jira-events at lists.jboss.org
Thu Jan 7 20:07:30 EST 2010


SmooksAction reports error when routing csv fragments via JMS
-------------------------------------------------------------

                 Key: JBESB-3104
                 URL: https://jira.jboss.org/jira/browse/JBESB-3104
             Project: JBoss ESB
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Transformation Service
    Affects Versions: 4.7
         Environment: Linux FC12(32bit), JBossAS 5.1GA + ESB 4.7, Sun Java SDK 1.6.0_17
            Reporter: Edward Pilipczuk


When processing csv stream by smooks engine (SmooksAction) the following exception is thrown:

2010-01-08 01:31:43,293 ERROR [STDERR] (pool-20-thread-1) [Fatal Error] :1:1: Content is not allowed in prolog.
2010-01-08 01:31:43,295 DEBUG [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] (pool-20-thread-1) Unexpected exception caught while processing the action pipeline: header: [ To: InVMEpr [ PortReference < <wsa:Address invm://46696c6552656164657224242424242424242424242443535646696c65526561646572/false?false#10000/>, <wsa:ReferenceProperties jbossesb:passByValue : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/invm/> > ] MessageID: cd0498bd-578c-43d8-a3e2-d09b94e78a46 ]
org.milyn.SmooksException: Failed to filter source.
        at org.milyn.delivery.sax.SmooksSAXFilter.doFilter(SmooksSAXFilter.java:72)
        at org.milyn.delivery.sax.SmooksSAXFilter.doFilter(SmooksSAXFilter.java:55)
        at org.milyn.Smooks._filter(Smooks.java:470)
        at org.milyn.Smooks.filterSource(Smooks.java:448)
        at org.milyn.container.plugin.PayloadProcessor.process(PayloadProcessor.java:112)
        at org.jboss.soa.esb.smooks.SmooksAction.process(SmooksAction.java:218)
        at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:634)
        at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:586)
        at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:420)
        at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:540)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.milyn.delivery.sax.SAXParser.parse(SAXParser.java:50)
        at org.milyn.delivery.sax.SmooksSAXFilter.doFilter(SmooksSAXFilter.java:69)
        ... 12 more

Attached the whole tsm project created by JT3.1(H198-CR1). After solving this problem tsm can be also used to fix JESB-414 and JESB-1516

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the esb-issues mailing list