> Have any one tested swiftmq with JMS Test Suite that are offered by
> Fiorano, How accruate and reliable the test results are? Fiorano
> mentions that the test suite checks line by line JMS specifications
> that are defined by sun microsystems.
A while ago a customer of us (a German bank) does this test. The result
was - you know it - bad. Similar to the results they use for pestering
SonicMQ. Our customer has forwarded the results to me and I have checked
it. The test suite is quite buggy. You will find my reply below. The
StreamMessage bug has been fixed in the meantime. Their selector issues
are also quite strange (for example: SwiftMQ does not support <ID>
"between" "NULL" and <INTEGER_LITERAL>)...
Bye, leaving for vacation now...
--
Andreas Mueller, IIT GmbH, Bremen/Germany, http://www.iit.de
SwiftMQ - JMS Enterprise Messaging System, http://www.swiftmq.com
----- My Reply -----
Date: Thu, 29 Mar 2001 11:23:40 +0200
From: "Andreas Mueller" <[EMAIL PROTECTED]>
To: **************
Subject: Re: Details of SwiftMQ failures - for your convenience - Fwd:
SwiftMQ vs JMS++
Hi ******,
thanks for forwarding me the results! It seems bad at the first look but
let me comment it:
> Here are the results of JMS++ versus SwiftMQ:
>
> PubSub JMS++ test results
>
> 1) SwiftMQ does not support "_" character in the client-id.
The JMS spec states that the client id contains a provider specific
value. SwiftMQ does allow letters & digits only. JMS++ failed here, not a
SwiftMQ bug.
> 2) SwiftMQ throws an exception saying can not be converted to short.
> StreamMessage.writeByte ((byte)1);
> StreamMessage.reset () and
> StreamMessage.readShort ()
Will be checked.
> 3) SwiftMQ does not support <ID> "between" "NULL" and <INTEGER_LITERAL>
> 4) SwiftMQ does not support <ID> "between" "-" <INTEGER_LITERAL> "and"
> "+" ...
> 5) SwiftMQ does not support "JMSDeliveryMode" <comparision>
Will be checked.
> 6) Can not set null value using message.setObjectProperty api.
That's true. JMS spec states there can only be object primitive values.
JMS++ failed, SwiftMQ ok.
> 7) Can not install message listner on a session.
Session.setMessageListener is part of application server facilities (ASF)
which is optional for a vendor. SwiftMQ doesn't support ASFs. JMS++
failed, SwiftMQ ok.
> Queuing JMS++ test results
>
> 1) SwiftMQ does not support "_" character in the client-id.
See above, not a bug.
> 2) SwiftMQ does not support <ID> "between" "NULL" and <INTEGER_LITERAL>
> 3) SwiftMQ does not support <ID> "between" "-" <INTEGER_LITERAL> "and"
> "+" ...
Will be checked.
> 4) SwiftMQ does not allow to commit the non-transacted sessions.
> Session is not transacted - commit not allowed
That's right. JMS spec states to throw an InvalidStateException when
using commit/rollback on a non-transacted session. JMS++ bug, SwiftMQ ok.
> 5) SwiftMQ does not support "JMSDeliveryMode" IS
> 6) SwiftMQ does not support "JMSDeliveryMode" <comparision>
> 7) SwiftMQ does not support "setMessageListener" on session.
Will be checked.
As you see, there are only some open selector issues where it is not
clear if JMS++ failes or SwiftMQ. We'll check that. The other things are
bugs in the JMS++ test suite. So be careful which test suite you use for
what. AFAIK a JMS compliance test suite is provided from Sun along with
the J2EE 1.3. That's much more serious than using 'compliance tests' from
another vendor, especially Fiorano. ;-)
Cheers,
Andreas
--
Andreas Mueller, IIT GmbH, Bremen/Germany, http://www.iit.de
SwiftMQ - JMS Enterprise Messaging System, http://www.swiftmq.com
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
