[
https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48809#action_48809
]
Darren Davison commented on CAMEL-1271:
---------------------------------------
Complete output when tracing is enabled and logging (for org.apache.camel only)
is set to DEBUG is shown below. The trace doesn't really seem to help much,
but the last 2 log messages at DEBUG look like they should be re-configured to
ERROR (or at least WARN).
Seems to confirm the original issue - Camel cannot deal with a StreamSource.
Whether it should be able to or not might be a different issue.
Cheers,
DEBUG - EndpointMessageListener - Endpoint[activemq:queue.testJms.in]
consumer receiving JMS message: ActiveMQTextMessage {commandId = 5,
responseRequired = false, messageId =
ID:davisond-laptop-57670-1232359825629-2:37:1:1:1, originalDestination = null,
originalTransactionId = null, producerId =
ID:davisond-laptop-57670-1232359825629-2:37:1:1, destination =
queue://queue.testJms.in, transactionId = null, expiration = 0, timestamp =
1232359865722, arrival = 0, brokerInTime = 1232359865723, brokerOutTime =
1232359865761, correlationId = null, replyTo = null, persistent = false, type =
null, priority = 0, groupID = null, groupSequence = 0, targetConsumerId = null,
compressed = false, userID = null, content =
org.apache.activemq.util.byteseque...@17c323d, marshalledProperties = null,
dataStructure = null, redeliveryCounter = 0, size = 0, properties = null,
readOnlyProperties = true, readOnlyBody = true, droppable = false, text = null}
INFO - TraceInterceptor -
ID-davisond-laptop/46122-1232359835725/2-0 ->
to(service:urn:oms:testHttp?mep=in-out) , Pattern:InOnly ,
Headers:{JMSXGroupID=null, JMSCorrelationID=null, JMSType=null,
JMSExpiration=0,
JMSMessageID=ID:davisond-laptop-57670-1232359825629-2:37:1:1:1,
JMSRedelivered=false, JMSDeliveryMode=1, JMSPriority=0, JMSReplyTo=null,
JMSTimestamp=1232359865722, JMSDestination=queue://queue.testJms.in} ,
BodyType:String , Body:<in><msg>foo4</msg></in>
DEBUG - Pipeline - Message exchange has failed so
breaking out of pipeline: Exchange[JmsMessage: ActiveMQTextMessage {commandId =
5, responseRequired = false, messageId =
ID:davisond-laptop-57670-1232359825629-2:37:1:1:1, originalDestination = null,
originalTransactionId = null, producerId =
ID:davisond-laptop-57670-1232359825629-2:37:1:1, destination =
queue://queue.testJms.in, transactionId = null, expiration = 0, timestamp =
1232359865722, arrival = 0, brokerInTime = 1232359865723, brokerOutTime =
1232359865761, correlationId = null, replyTo = null, persistent = false, type =
null, priority = 0, groupID = null, groupSequence = 0, targetConsumerId = null,
compressed = false, userID = null, content = null, marshalledProperties = null,
dataStructure = null, redeliveryCounter = 0, size = 0, properties = null,
readOnlyProperties = true, readOnlyBody = true, droppable = false, text =
<in><msg>foo4</msg></in>}] exception: null fault: JmsMessage:
javax.xml.transform.stream.streamsou...@19aed36
DEBUG - EndpointMessageListener - Cannot send reply message as there is
no replyDestination for: JmsMessage:
javax.xml.transform.stream.streamsou...@19aed36
> Can only interact with servicemix-http if logging is at DEBUG
> -------------------------------------------------------------
>
> Key: CAMEL-1271
> URL: https://issues.apache.org/activemq/browse/CAMEL-1271
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-jbi
> Affects Versions: 1.5.0
> Reporter: Darren Davison
> Assignee: Gert Vanthienen
> Fix For: 1.5.1, 2.0.0
>
>
> Given the following camel DSL:
> from("activemq:queue.testJms.in")
>
> .to("jbi:service:urn:oms:testHttp?mep=in-out")
> .to("activemq:queue.testJms.out");
> and the following xbean.xml for the smx (3.3) SU:
> <http:endpoint
>
> service="oms:testHttp"
> endpoint="testHttp"
> role="provider"
>
> locationURI="http://localhost:8080/testP1";>
>
> </http:endpoint>
> then Camel operates correctly (or at least as desired) only if DEBUG logging
> is enabled in the org.apache.servicemix.http package. This seems to be
> because a DOMSource is returned (which Camel can convert). If the log level
> is reduced (say to WARN) then a StreamSource object is returned instead which
> Camel appears unable to convert. This results in stack traces such as:
> ERROR - DeadLetterChannel - Failed delivery for exchangeId:
>
> ID-davisond-laptop/53380-1232099798317/0-0. On delivery attempt: 0
>
> caught: org.apache.camel.RuntimeCamelException:
>
> javax.xml.transform.TransformerException: java.io.IOException: Attempted
>
> read on closed stream.
>
> org.apache.camel.RuntimeCamelException:
>
> javax.xml.transform.TransformerException: java.io.IOException: Attempted
>
> read on closed stream.
>
> at
>
> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:441)
>
> at
>
> org.apache.camel.impl.converter.InstanceMethodTypeConverter.convertTo(InstanceMethodTypeCo
> +nverter.java:57)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
