You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2010/11/30 15:44:13 UTC
[jira] Created: (CXF-3158) Support Streaming for the JMS transport
Support Streaming for the JMS transport
---------------------------------------
Key: CXF-3158
URL: https://issues.apache.org/jira/browse/CXF-3158
Project: CXF
Issue Type: New Feature
Components: Transports
Reporter: Christian Schneider
Assignee: Christian Schneider
Currently the JMS Transport reads or writes the full message body in one step. To do so it buffers the complete message in memory. For very large messages this consumes a lot of memory and slows down message processing.
The JMS API allows Streaming for StreamMessages and BytesMessages. So we should be able to easily support this as well.
If we use a buffer we could support configuring the buffer size.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CXF-3158) Support Streaming for the JMS transport
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider closed CXF-3158.
------------------------------------
Resolution: Won't Fix
As none of the current jms providers supports streaming over the standard jms interface I close the issue.
> Support Streaming for the JMS transport
> ---------------------------------------
>
> Key: CXF-3158
> URL: https://issues.apache.org/jira/browse/CXF-3158
> Project: CXF
> Issue Type: New Feature
> Components: Transports
> Reporter: Christian Schneider
> Assignee: Christian Schneider
>
> Currently the JMS Transport reads or writes the full message body in one step. To do so it buffers the complete message in memory. For very large messages this consumes a lot of memory and slows down message processing.
> The JMS API allows Streaming for StreamMessages and BytesMessages. So we should be able to easily support this as well.
> If we use a buffer we could support configuring the buffer size.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-3158) Support Streaming for the JMS
transport
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965275#action_12965275 ]
Daniel Kulp commented on CXF-3158:
----------------------------------
Christian,
Last time I checked (late in the ActiveMQ 4.x cycles so may have changed) the Active MQ BytesMessage and StreamMessage implementations just wrote everything into a ByteArrayOutputStream and sent it all in one go anyway. Thus, using the streaming stuff wouldn't have bought us anything at all which is why we didn't pursue the changes at that time.
Of course, other JMS providers may be different.
Dan
> Support Streaming for the JMS transport
> ---------------------------------------
>
> Key: CXF-3158
> URL: https://issues.apache.org/jira/browse/CXF-3158
> Project: CXF
> Issue Type: New Feature
> Components: Transports
> Reporter: Christian Schneider
> Assignee: Christian Schneider
>
> Currently the JMS Transport reads or writes the full message body in one step. To do so it buffers the complete message in memory. For very large messages this consumes a lot of memory and slows down message processing.
> The JMS API allows Streaming for StreamMessages and BytesMessages. So we should be able to easily support this as well.
> If we use a buffer we could support configuring the buffer size.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-3158) Support Streaming for the JMS
transport
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965308#action_12965308 ]
Christian Schneider commented on CXF-3158:
------------------------------------------
I also did some tests with tibco ems 4.4.1. At least at this version they also seem to hold the message in memory. So I think if we do not find at least one big implementation that really streams we should not implement streaming for jms in cxf as it would only increase complexity then. On the other hand supporting streaming for messages would be a nice differentiating feature for ActiveMQ.
> Support Streaming for the JMS transport
> ---------------------------------------
>
> Key: CXF-3158
> URL: https://issues.apache.org/jira/browse/CXF-3158
> Project: CXF
> Issue Type: New Feature
> Components: Transports
> Reporter: Christian Schneider
> Assignee: Christian Schneider
>
> Currently the JMS Transport reads or writes the full message body in one step. To do so it buffers the complete message in memory. For very large messages this consumes a lot of memory and slows down message processing.
> The JMS API allows Streaming for StreamMessages and BytesMessages. So we should be able to easily support this as well.
> If we use a buffer we could support configuring the buffer size.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.