Hi Christian
Thanks - and sorry for the somewhat rough tests. Currently I'm trying to
solve multiple problems at the same time
And I tried it on 1.12.0 yesterday and there it works as you say. There
seems to be another problem with tracing on 1.12.0 though. When you activate
tracing using jmx
Hi
Read the release notes
http://camel.apache.org/camel-2120-release.html
See section: Changes that may affect end users
On Wed, Sep 11, 2013 at 10:50 AM, Preben.Asmussen p...@dr.dk wrote:
Hi Christian
Thanks - and sorry for the somewhat rough tests. Currently I'm trying to
solve multiple
Ahh - thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/org-xml-sax-SAXParseException-Premature-end-of-file-in-split-tp5738675p5739106.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I logged a ticket: https://issues.apache.org/jira/browse/CAMEL-6735
Best,
Christian
-
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member:
Did 2 tests that shows the problem with enabling the tracer.
If you run RouteWithoutTracerTest it runs ok
The other RouteWithTracerTest fails with org.xml.sax.SAXParseException:
Premature end of file.
The tracer seems to break stuff somewhere.
tracerbug.zip
Well It didn't work as expected.
After I added convertBody to byte[] the error persists when enabling
tracing.
Changed route -
inOut uri=cxfrs:bean:playlist?synchronous=true id=playws/
convertBodyTo type=byte[]/
split
Just tested it on 2.11.1 with the same result
--
View this message in context:
http://camel.465427.n5.nabble.com/org-xml-sax-SAXParseException-Premature-end-of-file-in-split-tp5738675p5738841.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi Willem
No the tracing was enabled using jmx to trubleshot.
Thinking of it I recall some bug in Camel with a toString method and
streaming. It might be that when tracing is enabled it consumes the stream
when calling toString in camel version 2.10.0 ??
What would be the best approach here to
Yeah converting to a String is a good idea if the data is in-memory
only, eg not a 500mb file you read from the file system etc.
A side note:
Also the xpath engine from JDK is purely in-memory only. It cannot
split / evaluate in streaming mode.
You can find some links about splitting big xml
Hi
I'm running into a error in production, but not in test while using a
splitter with a xpath expression.
The route is receiving messages from a jms queue and is calling a rest
service on anoter tomcat box.
The response should be splittet and send to an activemq topic -
In production I get an
Hi,
Do you always enable to camel tracing in your production environment?
SaxParseException: Premature end of file. It looks like a stream consuming
issue.
We need to know if the message is consumed before routing the splitter for
processing.
Willem Jiang
Red Hat, Inc.
FuseSource is now
11 matches
Mail list logo
