You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Darren Davison (JIRA)" <ji...@apache.org> on 2009/01/18 21:32:59 UTC
[jira] Created: (CAMEL-1271) Can only interact with servicemix-http
if logging is at DEBUG
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
Affects Versions: 1.5.0
Reporter: Darren Davison
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.
[jira] Commented: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Darren Davison (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48802#action_48802 ]
Darren Davison commented on CAMEL-1271:
---------------------------------------
sorry, I should have mentioned.. we're using Camel 1.5.0. As we needed unrelated fixes made since 1.4, we re-packaged the servicemix-camel SU to use 1.5. So I guess this should work but still doesn't.
We had already tried several variants of the streamCaching() DSL snippet to no avail anyway. Here are the results with the 2 you mentioned:
{code}from("activemq:queue.testJms.in")
.streamCaching()
.to("jbi:service:urn:oms:testHttp?mep=in-out")
.to("activemq:queue.testJms.out"); {code}
in the above change, no excpetions or log messages from servicemix. The target webservice is called and responds correctly. The .in queue shows messages enqueued and dequeued correctly, the .out queue is empty (no message ever appears on it). With this change, we simply lose our response messages completely and without apparent warning.
{code}streamCaching();
from("activemq:queue.testJms.in")
.to("jbi:service:urn:oms:testHttp?mep=in-out")
.to("activemq:queue.testJms.out"); {code}
with this change, I see exactly the same results as above.
So even with Camel 1.5, the explicit streamCaching() *does* appear to cause different behaviour. But it looks worse to me :(
I'm not convinced by the unit tests in this instance since they don't involve HTTP connections that are likely to be closed before the StreamSource that wraps them has been read. I may be wrong though.
<joke>
Should I turn the logging up to see what's happening? :)
</joke>
> 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
> Affects Versions: 1.5.0
> Reporter: Darren Davison
> Assignee: Willem Jiang
>
> 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.
[jira] Commented: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48797#action_48797 ]
Gert Vanthienen commented on CAMEL-1271:
----------------------------------------
Shouldn't the stream caching be done automatically now since CAMEL-520 got resolved?
> 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
> Affects Versions: 1.5.0
> Reporter: Darren Davison
> Assignee: Willem Jiang
>
> 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.
[jira] Commented: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48788#action_48788 ]
Willem Jiang commented on CAMEL-1271:
-------------------------------------
You need to cache the stream when routing the message in camel. Because Camel will cache the stream when it's logging level is set to be DEBUG.
Here is the code snippet of enable the SteamCaching interceptor in your router.
{code}
//Stream caching for a single route...
from("direct:a").streamCaching().to("mock:a");
//... or for all the following routes in this builder
streamCaching();
from("direct:b").to("mock:b");
{code}
> 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
> Affects Versions: 1.5.0
> Reporter: Darren Davison
> Assignee: Willem Jiang
>
> 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.
[jira] Commented: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48798#action_48798 ]
Claus Ibsen commented on CAMEL-1271:
------------------------------------
@Darren
Which version of Camel are you using? As Gert pointed out the stream caching should have been default enabled in Camel 1.5.0.
> 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
> Affects Versions: 1.5.0
> Reporter: Darren Davison
> Assignee: Willem Jiang
>
> 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.
[jira] Issue Comment Edited: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Darren Davison (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48988#action_48988 ]
davisond edited comment on CAMEL-1271 at 1/28/09 4:23 AM:
----------------------------------------------------------------
tried with the 2008.2 snapshot as requested; now getting what looks like an odd low level parsing issue:
{noformat}org.apache.camel.RuntimeCamelException: javax.xml.transform.TransformerException: java.io.IOException:
CRLF expected at end of chunk: 48/13{noformat}
I can send you the log file for the whole in/out route if you like, but it has some proprietary info in there that I don't want to post here.
was (Author: davisond):
tried with the 2008.2 snapshot as requested; now getting what looks like an odd low level parsing issue:
{{org.apache.camel.RuntimeCamelException: javax.xml.transform.TransformerException: java.io.IOException:
CRLF expected at end of chunk: 48/13}}
I can send you the log file for the whole in/out route if you like, but it has some proprietary info in there that I don't want to post here.
> 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.
[jira] Commented: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Darren Davison (JIRA)" <ji...@apache.org>.
[ 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.ByteSequence@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.StreamSource@19aed36
DEBUG - EndpointMessageListener - Cannot send reply message as there is no replyDestination for: JmsMessage: javax.xml.transform.stream.StreamSource@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.
[jira] Commented: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48805#action_48805 ]
Claus Ibsen commented on CAMEL-1271:
------------------------------------
I guess the issue is in SMX http since it returns different objects depending on logging level.
It should return a payload that Camel at least once can read.
> 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
> Affects Versions: 1.5.0
> Reporter: Darren Davison
> Assignee: Willem Jiang
>
> 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.
[jira] Commented: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49103#action_49103 ]
Claus Ibsen commented on CAMEL-1271:
------------------------------------
Thanks to get we got the camel-jaxb fixed
> 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.
[jira] Assigned: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CAMEL-1271:
-----------------------------------
Assignee: Willem Jiang
> 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
> Affects Versions: 1.5.0
> Reporter: Darren Davison
> Assignee: Willem Jiang
>
> 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.
[jira] Commented: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49100#action_49100 ]
Claus Ibsen commented on CAMEL-1271:
------------------------------------
Gertv there is a bug with disabling the stream cache
noStreamCaching();
Can not disable it
So you get String wrapped as a: org.apache.camel.converter.stream.StreamCacheConverter$SourceCache
> 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.
[jira] Commented: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Darren Davison (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48988#action_48988 ]
Darren Davison commented on CAMEL-1271:
---------------------------------------
tried with the 2008.2 snapshot as requested; now getting what looks like an odd low level parsing issue:
{{org.apache.camel.RuntimeCamelException: javax.xml.transform.TransformerException: java.io.IOException:
CRLF expected at end of chunk: 48/13}}
I can send you the log file for the whole in/out route if you like, but it has some proprietary info in there that I don't want to post here.
> 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.
[jira] Updated: (CAMEL-1271) Can only interact with servicemix-http
if logging is at DEBUG
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-1271:
-------------------------------
Component/s: camel-jbi
Fix Version/s: 2.0.0
1.5.1
> 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.
[jira] Commented: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Darren Davison (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48810#action_48810 ]
Darren Davison commented on CAMEL-1271:
---------------------------------------
hmm.. just noticed something from the trace output that I missed.. is this relevant?
INFO - TraceInterceptor - ID-davisond-laptop/46122-1232359835725/2-0 -> to(service:urn:oms:testHttp?*mep=in-out*) , *Pattern:InOnly*
> 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.
[jira] Assigned: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-1271:
----------------------------------
Assignee: Gert Vanthienen (was: Willem Jiang)
Gertv will look at this from SMX and Camel point of view, as he have a hand in both teams
> 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.
[jira] Commented: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49101#action_49101 ]
Gert Vanthienen commented on CAMEL-1271:
----------------------------------------
Claus: Do we want noStreamCaching() to disable stream caching for the DeadLetterChannel? Sending a stream through the DeadLetterChannel without caching it won't work anyhow.
I agree we should at least make the streamCaching options behave the same in the DLC and in the RouteBuilder though -- right now the first one uses an InterceptStrategy and the latter one uses a plain Interceptor.
> 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.
[jira] Commented: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48804#action_48804 ]
Claus Ibsen commented on CAMEL-1271:
------------------------------------
Can you try the TRACE to see if that helps logging what is going on?
http://activemq.apache.org/camel/tracer.html
> 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
> Affects Versions: 1.5.0
> Reporter: Darren Davison
> Assignee: Willem Jiang
>
> 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.
[jira] Commented: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48799#action_48799 ]
Gert Vanthienen commented on CAMEL-1271:
----------------------------------------
Right, sorry about the confusion! servicemix-camel 2008.01 does use Camel 1.4.0 instead of Camel 1.5.0 so the call to streamCaching() is necessary.
> 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
> Affects Versions: 1.5.0
> Reporter: Darren Davison
> Assignee: Willem Jiang
>
> 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.
[jira] Resolved: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen resolved CAMEL-1271.
------------------------------------
Resolution: Fixed
This should be fixed now -- there are a few follow-up issues (CAMEL-1310 and CAMEL-1332)
> 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.6.0, 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.
[jira] Resolved: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-1271.
---------------------------------
Resolution: Won't Fix
> 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
> Affects Versions: 1.5.0
> Reporter: Darren Davison
> Assignee: Willem Jiang
>
> 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.
[jira] Commented: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49099#action_49099 ]
Gert Vanthienen commented on CAMEL-1271:
----------------------------------------
Fixed for trunk in http://svn.eu.apache.org/viewvc?view=rev&revision=740251
and backported to branch in http://svn.eu.apache.org/viewvc?view=rev&revision=740263
Darren, could you give it another go with a local build of both Camel and servicemix-camel?
> 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.
[jira] Issue Comment Edited: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49103#action_49103 ]
davsclaus edited comment on CAMEL-1271 at 2/3/09 6:39 AM:
------------------------------------------------------------
Thanks to gertv we got the camel-jaxb fixed
was (Author: davsclaus):
Thanks to get we got the camel-jaxb fixed
> 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.
[jira] Commented: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Darren Davison (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48803#action_48803 ]
Darren Davison commented on CAMEL-1271:
---------------------------------------
for completeness, I've also tried amending the DSL as follows with no difference in results already noted:
{code}from("activemq:queue.testJms.in")
.streamCaching() // or without..
.to("jbi:service:urn:oms:testHttp?mep=in-out")
.convertBodyTo(String.class)
.to("activemq:queue.testJms.out");{code}
Cheers,
> 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
> Affects Versions: 1.5.0
> Reporter: Darren Davison
> Assignee: Willem Jiang
>
> 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.
[jira] Commented: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48794#action_48794 ]
Claus Ibsen commented on CAMEL-1271:
------------------------------------
I updated the JBI component page with a hint about this streamCaching
> 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
> Affects Versions: 1.5.0
> Reporter: Darren Davison
> Assignee: Willem Jiang
>
> 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.
[jira] Commented: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48806#action_48806 ]
Claus Ibsen commented on CAMEL-1271:
------------------------------------
@Darren
Can you show us some more of the stacktrace please?
> 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: Willem Jiang
> 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.
[jira] Reopened: (CAMEL-1271) Can only interact with
servicemix-http if logging is at DEBUG
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reopened CAMEL-1271:
--------------------------------
> 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.