You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Weston M. Price (Commented) (JIRA)" <ji...@apache.org> on 2012/04/10 12:35:17 UTC

[jira] [Commented] (QPID-3941) Add the jms version of QpidSend and QpidReceive

    [ https://issues.apache.org/jira/browse/QPID-3941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250559#comment-13250559 ] 

Weston M. Price commented on QPID-3941:
---------------------------------------

There is a version of this in the JCA examples that could most likely be easily integrated to the JMS examples. Note, the JCA example doesn't use JCA per se, it is a non-managed JMS application that simply posts and receives messages to a destination. 

See
   java/jca/example/src/main/org/apache/qpid/jca/example/client/QpidRequestResponseClient.java

A few features include threaded sending/receiving as well as being able to control the message count, destination etc via system or command line properties.
                
> Add the jms version of QpidSend and QpidReceive
> -----------------------------------------------
>
>                 Key: QPID-3941
>                 URL: https://issues.apache.org/jira/browse/QPID-3941
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Client
>            Reporter: Rajith Attapattu
>            Assignee: Rajith Attapattu
>             Fix For: 0.17
>
>
> If we could come with near identical versions of the c++ QpidSend and QpidReceive we could do meaningful comparisons between the c++ and JMS clients.
> This can be very helpful when figuring out if a problem is on broker or client side. Ex if both the c++ and jms versions exibhit a similar behavior/trend/pattern we could make a reasonable conclusion that the issue might be on the broker side.
> This could also be very helpful in identifying weak points in a particular client if there is a huge difference in behavior for a given use case.
> The goal is to ensure that we use identical options and behavior to ensure they are as close as possible.
> This will allow us to turn qpid-cpp-benchmark into a generic benchmark tool, where we can use it for both clients or mix and match (ex JMS receiver with C++ sender).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org