[
https://issues.apache.org/jira/browse/QPID-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Greig resolved QPID-301.
-------------------------------
Resolution: Invalid
Fix Version/s: (was: M3)
Turning a 100k bytes message into a string is not going to a particularly cheap
operation.
No idea why the user thinks that should be a "sub ms" operation.
Closing as invalid since it's not really a qpid issue - we provide access to
the raw bytes so if someone can do better than the Sun string converter (which
is very likely if all their data is ASCII for example) they can go ahead.
> Tune performance when reading message content from client
> ---------------------------------------------------------
>
> Key: QPID-301
> URL: https://issues.apache.org/jira/browse/QPID-301
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: M1
> Reporter: Marnie McCormack
>
> The following code:
> public void onMessage(Message message)
> {
> sLog.info("message received");
>
> if (message instanceof JMSBytesMessage)
> {
> String correlationId = "unknown";
> try
> {
> JMSBytesMessage requestMessage = (JMSBytesMessage) message;
> // Read and deserialise message
> String requestMessageString = requestMessage.toBodyString();
> correlationId = requestMessage.getJMSCorrelationID();
> takes 5ms to execute on an opteron Linux server, with a 100K message. User
> expected sub ms performance from this test. Auto acknowledge mode.
> Note that bytes message sent from C++ client publisher.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
