jmscts-user Mailing List for JMS CTS
Status: Alpha
Brought to you by:
tanderson
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(2) |
| 2007 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Tim A. <tm...@ne...> - 2012-05-06 01:56:36
|
It looks like the provider hasn't loaded successfully.
Try running it in a debugger and see whats going on.
On 3/05/2012 9:37 PM, Hasitha Abeykoon wrote:
> Hi,
>
> As you have suggested, I did the following,
>
> 1. Wrote provider and administrator classes, complied those to
> "src.jar" having same structure as "openjms-provider-0.5-b2.jar"
> 2. added all the jar paths required to run qpid to providers.xml.
> (but i did not add jars in {JMSCTS_HOME/lib})
> 3. set path to "src.jar" and put provider class between
> <class></class> in providers.xml file.
> 4. run JMS CTS.
>
> But unfortunately came across this error.
>
> 6:58:56 Time: 2.65
> 16:58:56 There was 1 error:
> 16:58:56 1) junit.framework.TestSuite@1389c036
> java.lang.NullPointerException
> at
> org.exolab.jmscts.core.ProviderTestRunner.setUp(ProviderTestRunner.java:118)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at
> org.exolab.jmscts.core.AbstractTestRunner.basicRun(AbstractTestRunner.java:303)
> at
> org.exolab.jmscts.core.JMSTestRunner.basicRun(JMSTestRunner.java:166)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at
> org.exolab.jmscts.core.JUnitTestRunner.doRun(JUnitTestRunner.java:144)
> at
> org.exolab.jmscts.core.JUnitTestRunner.run(JUnitTestRunner.java:271)
> at
> org.exolab.jmscts.test.ComplianceTestSuite.main(ComplianceTestSuite.java:83)
> 16:58:56 FAILURES!!!
> 16:58:56 Tests run: 0, Failures: 0, Errors: 1
>
> What am i missing here?
>
> On Thu, May 3, 2012 at 12:01 PM, Hasitha Abeykoon
> <hab...@gm... <mailto:hab...@gm...>> wrote:
>
> Hi,
>
> Thanks for your quick reply. To start Qpid number of config files
> are wanted. Do I need to put them in providers.xml too? And for
> openJMS I noted that there is a openJMS.xml file with following in.
>
> <?xml version="1.0"?>
> <configuration>
> <proxy provider="org.exolab.jmscts.openjms.OpenJMSProvider"
> start="true" stop="true">
> <property name="Path" type="java.lang.String"
> value="${openjms.home}/config/openjms.xml" />
> </proxy>
> </configuration>
>
> Is it something openJMS specific?
>
> On Mon, Apr 30, 2012 at 6:59 PM, Tim Anderson <tm...@ne...
> <mailto:tm...@ne...>> wrote:
>
> You need to implement the Provider and Administrator
> interfaces and then
> include the jar that implements these along with all the
> Apache Qpid jars in providers.xml.
>
> There are a number or provider implementations - take a look
> at
> http://www.koders.com/info.aspx?c=ProjectInfo&pid=ZZN8HT9AF31MW58R27KNAA1N3C&s=VectorIfc
> <http://www.koders.com/info.aspx?c=ProjectInfo&pid=ZZN8HT9AF31MW58R27KNAA1N3C&s=VectorIfc>
>
> -Tim
>
>
>
> On 29/04/2012 5:01 PM, Hasitha Abeykoon wrote:
>> Hi,
>>
>> I was trying to configure JMS CTS to check a redistribution
>> of Apache Qpid. As I understood from getting started
>> documentation, i need to
>>
>> 1. write a QpidJMSProvider class
>> 2. configure *$JMSCTS_HOME/config/providers.xml* to that class.
>>
>> What are the Dependant jars I have to use? also Can I follow
>> the way
>> http://www.koders.com/java/fid63868DF5110CD1652EE5F7E41796018B4373D2E0.aspx?s=VectorIfc
>> is written?
>>
>> appreciate your help very much.
>>
>> --
>> */Hasitha Abeykoon,/*
>> */Department of Computer Science & Engineering,/*
>> */University of Moratuwa. /*
>> */
>> /*
>> */Skype: foreverhasitha/*
>>
>>
>>
>>
>> -
>
>
|
|
From: Hasitha A. <hab...@gm...> - 2012-05-03 11:37:37
|
Hi,
As you have suggested, I did the following,
1. Wrote provider and administrator classes, complied those to "src.jar"
having same structure as "openjms-provider-0.5-b2.jar"
2. added all the jar paths required to run qpid to providers.xml. (but i
did not add jars in {JMSCTS_HOME/lib})
3. set path to "src.jar" and put provider class between <class></class>
in providers.xml file.
4. run JMS CTS.
But unfortunately came across this error.
6:58:56 Time: 2.65
16:58:56 There was 1 error:
16:58:56 1) junit.framework.TestSuite@1389c036
java.lang.NullPointerException
at
org.exolab.jmscts.core.ProviderTestRunner.setUp(ProviderTestRunner.java:118)
at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at
org.exolab.jmscts.core.AbstractTestRunner.basicRun(AbstractTestRunner.java:303)
at org.exolab.jmscts.core.JMSTestRunner.basicRun(JMSTestRunner.java:166)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at
org.exolab.jmscts.core.JUnitTestRunner.doRun(JUnitTestRunner.java:144)
at org.exolab.jmscts.core.JUnitTestRunner.run(JUnitTestRunner.java:271)
at
org.exolab.jmscts.test.ComplianceTestSuite.main(ComplianceTestSuite.java:83)
16:58:56 FAILURES!!!
16:58:56 Tests run: 0, Failures: 0, Errors: 1
What am i missing here?
On Thu, May 3, 2012 at 12:01 PM, Hasitha Abeykoon
<hab...@gm...>wrote:
> Hi,
>
> Thanks for your quick reply. To start Qpid number of config files are
> wanted. Do I need to put them in providers.xml too? And for openJMS I noted
> that there is a openJMS.xml file with following in.
>
> <?xml version="1.0"?>
> <configuration>
> <proxy provider="org.exolab.jmscts.openjms.OpenJMSProvider"
> start="true" stop="true">
> <property name="Path" type="java.lang.String"
> value="${openjms.home}/config/openjms.xml" />
> </proxy>
> </configuration>
>
> Is it something openJMS specific?
>
> On Mon, Apr 30, 2012 at 6:59 PM, Tim Anderson <tm...@ne...> wrote:
>
>> You need to implement the Provider and Administrator interfaces and then
>> include the jar that implements these along with all the Apache Qpid jars
>> in providers.xml.
>>
>> There are a number or provider implementations - take a look at
>> http://www.koders.com/info.aspx?c=ProjectInfo&pid=ZZN8HT9AF31MW58R27KNAA1N3C&s=VectorIfc
>>
>> -Tim
>>
>>
>>
>> On 29/04/2012 5:01 PM, Hasitha Abeykoon wrote:
>>
>> Hi,
>>
>> I was trying to configure JMS CTS to check a redistribution of Apache
>> Qpid. As I understood from getting started documentation, i need to
>>
>> 1. write a QpidJMSProvider class
>> 2. configure *$JMSCTS_HOME/config/providers.xml * to that class.
>>
>> What are the Dependant jars I have to use? also Can I follow the way
>> http://www.koders.com/java/fid63868DF5110CD1652EE5F7E41796018B4373D2E0.aspx?s=VectorIfcis written?
>>
>> appreciate your help very much.
>>
>> --
>> *Hasitha Abeykoon,*
>> *Department of Computer Science & Engineering,*
>> *University of Moratuwa. *
>> *
>> *
>> *Skype: foreverhasitha*
>>
>>
>>
>>
>> -
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> jmscts-user mailing list
>> jms...@li...
>> https://lists.sourceforge.net/lists/listinfo/jmscts-user
>>
>>
>
>
> --
> *Hasitha Abeykoon,*
> *Department of Computer Science & Engineering,*
> *University of Moratuwa. *
> *
> *
> *Skype: foreverhasitha*
>
>
>
--
*Hasitha Abeykoon,*
*Department of Computer Science & Engineering,*
*University of Moratuwa. *
*
*
*Skype: foreverhasitha*
|
|
From: Hasitha A. <hab...@gm...> - 2012-05-03 06:31:15
|
Hi,
Thanks for your quick reply. To start Qpid number of config files are
wanted. Do I need to put them in providers.xml too? And for openJMS I noted
that there is a openJMS.xml file with following in.
<?xml version="1.0"?>
<configuration>
<proxy provider="org.exolab.jmscts.openjms.OpenJMSProvider"
start="true" stop="true">
<property name="Path" type="java.lang.String"
value="${openjms.home}/config/openjms.xml" />
</proxy>
</configuration>
Is it something openJMS specific?
On Mon, Apr 30, 2012 at 6:59 PM, Tim Anderson <tm...@ne...> wrote:
> You need to implement the Provider and Administrator interfaces and then
> include the jar that implements these along with all the Apache Qpid jars
> in providers.xml.
>
> There are a number or provider implementations - take a look at
> http://www.koders.com/info.aspx?c=ProjectInfo&pid=ZZN8HT9AF31MW58R27KNAA1N3C&s=VectorIfc
>
> -Tim
>
>
>
> On 29/04/2012 5:01 PM, Hasitha Abeykoon wrote:
>
> Hi,
>
> I was trying to configure JMS CTS to check a redistribution of Apache
> Qpid. As I understood from getting started documentation, i need to
>
> 1. write a QpidJMSProvider class
> 2. configure *$JMSCTS_HOME/config/providers.xml * to that class.
>
> What are the Dependant jars I have to use? also Can I follow the way
> http://www.koders.com/java/fid63868DF5110CD1652EE5F7E41796018B4373D2E0.aspx?s=VectorIfcis written?
>
> appreciate your help very much.
>
> --
> *Hasitha Abeykoon,*
> *Department of Computer Science & Engineering,*
> *University of Moratuwa. *
> *
> *
> *Skype: foreverhasitha*
>
>
>
>
> -
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> jmscts-user mailing list
> jms...@li...
> https://lists.sourceforge.net/lists/listinfo/jmscts-user
>
>
--
*Hasitha Abeykoon,*
*Department of Computer Science & Engineering,*
*University of Moratuwa. *
*
*
*Skype: foreverhasitha*
|
|
From: Tim A. <tm...@ne...> - 2012-04-30 15:36:49
|
You need to implement the Provider and Administrator interfaces and then include the jar that implements these along with all the Apache Qpid jars in providers.xml. There are a number or provider implementations - take a look at http://www.koders.com/info.aspx?c=ProjectInfo&pid=ZZN8HT9AF31MW58R27KNAA1N3C&s=VectorIfc -Tim On 29/04/2012 5:01 PM, Hasitha Abeykoon wrote: > Hi, > > I was trying to configure JMS CTS to check a redistribution of Apache > Qpid. As I understood from getting started documentation, i need to > > 1. write a QpidJMSProvider class > 2. configure *$JMSCTS_HOME/config/providers.xml* to that class. > > What are the Dependant jars I have to use? also Can I follow the way > http://www.koders.com/java/fid63868DF5110CD1652EE5F7E41796018B4373D2E0.aspx?s=VectorIfc > is written? > > appreciate your help very much. > > -- > */Hasitha Abeykoon,/* > */Department of Computer Science & Engineering,/* > */University of Moratuwa. /* > */ > /* > */Skype: foreverhasitha/* > > > > > - |
|
From: Hasitha A. <hab...@gm...> - 2012-04-29 07:01:33
|
Hi, I was trying to configure JMS CTS to check a redistribution of Apache Qpid. As I understood from getting started documentation, i need to 1. write a QpidJMSProvider class 2. configure *$JMSCTS_HOME/config/providers.xml * to that class. What are the Dependant jars I have to use? also Can I follow the way http://www.koders.com/java/fid63868DF5110CD1652EE5F7E41796018B4373D2E0.aspx?s=VectorIfcis written? appreciate your help very much. -- *Hasitha Abeykoon,* *Department of Computer Science & Engineering,* *University of Moratuwa. * * * *Skype: foreverhasitha* |
|
From: Tim A. <tm...@ne...> - 2007-08-14 07:22:15
|
Yep, 1.02b is covered. Martin Ritchie wrote: > I'll see what I can do, problem is I've been tainted with Suns TCK > NDA. So does the current CTS cover JMS 1.02b? > > Regards > > Martin > > On 14/08/07, Tim Anderson <tm...@ne...> wrote: > >> Martin Ritchie wrote: >> >>> Hi, >>> >>> I notice that development appears to have slowed quite a lot here. Has >>> development stopped? Is there a final release or is beta 2 as good as >>> it gets? >>> >>> Is there work I can help on? >>> >>> >> Pretty much. I've had 2 kids since starting the project and no longer >> have much time >> to work on opensource. >> >> If you can help out, that would be fantastic. It pretty much works, >> although there's a few missing >> test cases, and it hasn't been updated for the JMS 1.1 API. The build >> environment could also do >> with conversion to maven 2. >> >> Regards, >> >> Tim >> |
|
From: Martin R. <rit...@ap...> - 2007-08-14 07:05:43
|
I'll see what I can do, problem is I've been tainted with Suns TCK NDA. So does the current CTS cover JMS 1.02b? Regards Martin On 14/08/07, Tim Anderson <tm...@ne...> wrote: > Martin Ritchie wrote: > > Hi, > > > > I notice that development appears to have slowed quite a lot here. Has > > development stopped? Is there a final release or is beta 2 as good as > > it gets? > > > > Is there work I can help on? > > > Pretty much. I've had 2 kids since starting the project and no longer > have much time > to work on opensource. > > If you can help out, that would be fantastic. It pretty much works, > although there's a few missing > test cases, and it hasn't been updated for the JMS 1.1 API. The build > environment could also do > with conversion to maven 2. > > Regards, > > Tim > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > jmscts-user mailing list > jms...@li... > https://lists.sourceforge.net/lists/listinfo/jmscts-user > |
|
From: Tim A. <tm...@ne...> - 2007-08-14 02:04:32
|
Martin Ritchie wrote: > Hi, > > I notice that development appears to have slowed quite a lot here. Has > development stopped? Is there a final release or is beta 2 as good as > it gets? > > Is there work I can help on? > Pretty much. I've had 2 kids since starting the project and no longer have much time to work on opensource. If you can help out, that would be fantastic. It pretty much works, although there's a few missing test cases, and it hasn't been updated for the JMS 1.1 API. The build environment could also do with conversion to maven 2. Regards, Tim |
|
From: Martin R. <rit...@ap...> - 2007-08-13 15:41:56
|
Hi, I notice that development appears to have slowed quite a lot here. Has development stopped? Is there a final release or is beta 2 as good as it gets? Is there work I can help on? -- Martin Ritchie |
|
From: Tim A. <tm...@ne...> - 2005-08-11 05:57:01
|
Did you refer to the coverage report to determine why the failures occured? It may be a configuration problem. See $JMSCTS_HOME/report/html/coverage.html If you are running against openjms-0.7.7-alpha-1 you need to build the version in CVS. The missing packages you are referring to are generated by castor as part of the build process. -Tim _____ From: jms...@li... [mailto:jms...@li...] On Behalf Of Aviad Lichtenstadt Sent: Thursday, 11 August 2005 12:28 AM To: jms...@li... Subject: [jmscts-user] Missing files at the CVS Hi There I am trying to use the JmsCts - I ran it on OpenJms and got a few thousands of tests to run but nearly all of them failed ? When I tried to run it on a different jms provider I got only 93 tests to run ? When I downloaded your source I saw that there are missing packages and when I looked at the CVS I saw there were missing there as well Packages missing for example: package meta package filter package types Waiting for your reply Thnx in advance Aviad -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.338 / Virus Database: 267.10.5/67 - Release Date: 8/9/2005 |
|
From: Aviad L. <av...@co...> - 2005-08-10 14:28:58
|
Hi There =20 I am trying to use the JmsCts =96 I ran it on OpenJms and got a few thousands of tests to run but nearly all of them failed ? When I tried to run it on a different jms provider I got only 93 tests to run ? =20 When I downloaded your source I saw that there are missing packages and when I looked at the CVS I saw there were missing there as well Packages missing for example:=20 package meta package filter package types =20 Waiting for your reply=20 Thnx in advance Aviad =20 --=20 No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.338 / Virus Database: 267.10.5/67 - Release Date: 8/9/2005 =20 |
|
From: Tim A. <tm...@ne...> - 2004-11-17 03:59:28
|
OK - now I see your point. Stick in a bug report, and I'll fix it for the next release. Thanks, Tim > -----Original Message----- > From: jms...@li... > [mailto:jms...@li...] On Behalf Of > Brent Petersen > Sent: Wednesday, 17 November 2004 4:20 AM > To: 'jms...@li...' > Subject: RE: [jmscts-user] Is > ClientAcknowledgeTest.testPartialClientAcknowledge correct? > > > Tim, > > I've done some more research and according to Sun: if I have > a message consumer that receives three messages by calling > MessageConsumer.receive three times and acknowledge the > second message by calling Message.acknowledge then all three > messages should be acknowledged. > > Brent > > > -----Original Message----- > From: jms...@li... > [mailto:jms...@li...]On Behalf Of > Tim Anderson > Sent: Sunday, November 14, 2004 4:19 AM > To: jms...@li... > Subject: RE: [jmscts-user] Is > ClientAcknowledgeTest.testPartialClientAcknowledge correct? > > > > Sent: Saturday, 13 November 2004 6:12 AM > > > > The > > org.exolab.jmscts.test.session.clientack.ClientAcknowledgeTest > > .testPartialCl > > ientAcknowledge test receives 10 messages, acknowledges the > > fifth message, calls Session.recover() and then expects to > > receive the last five messages. The thinking here seems to be > > that Message.acknowledge() acknowledges all received messages > > up to and including the message that was acknowledged. While > > I find this more logical than the JMS specification, I don't > > believe that this is the correct interpretation of the JMS > > specification. The JMS 1.1 specification has the following comment: > > > > "A possible misinterpretation of the existing Java API > > documentation for Message.acknowledge assumed that only > > messages received prior to "this" message should be > > acknowledged. The updated Java API documentation statement > > emphasizes that message acknowledgement is really a > > session-level activity and that this message is only being > > used to identify the session in order to acknowledge all > > messages consumed by the session. The acknowledge method was > > placed in the message object only to enable easy access to > > acknowledgement capability within a message listener's > > onMessage method. This change aligns the specification and > > Java API documentation to define Message.acknowledge in the > > same manner." > > > > > > I think it is. In the JMS 1.1 spec, section 4.4.11 "Message > Acknowledgment" talks about the behaviour of > Message.acknowledge with CLIENT_ACKNOWLEDGE and > Session.recover: "With this option, a client acknowledges a > message by calling the message's > > acknowledge method. Acknowledging a consumed message automatically > acknowledges the receipt of all messages that have been > delivered by its > session. > ... > A session's recover method is used to stop a session and > restart it with > its first unacknowledged message. In effect, the session's > series of > delivered messages is reset to the point after its last > acknowledged > message." > > I don't see any other way of interpreting the above. The > clarification in the specification may be allowing for the > fact that a MessageListener > may be registered with multiple Session instances, and that > invoking Message.acknowledge will only acknowledge messages > consumed by the Session that invoked the MessageListener - as > opposed to acknowledging messages consumed across all > Sessions that the MessageListener is registered. > > -Tim > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: InterSystems CACHE > FREE OODBMS DOWNLOAD - A multidimensional database that > combines robust object and relational technologies, making it > a perfect match for Java, C++,COM, XML, ODBC and JDBC. > www.intersystems.com/match8 > _______________________________________________ > jmscts-user mailing list > jms...@li... > https://lists.sourceforge.net/lists/listinfo/jmscts-user > > > ------------------------------------------------------- > This SF.Net email is sponsored by: InterSystems CACHE > FREE OODBMS DOWNLOAD - A multidimensional database that > combines robust object and relational technologies, making it > a perfect match for Java, C++,COM, XML, ODBC and JDBC. > www.intersystems.com/match8 > _______________________________________________ > jmscts-user mailing list > jms...@li... > https://lists.sourceforge.net/lists/listinfo/jmscts-user > |
|
From: Brent P. <bre...@we...> - 2004-11-16 17:19:53
|
Tim, I've done some more research and according to Sun: if I have a message consumer that receives three messages by calling MessageConsumer.receive three times and acknowledge the second message by calling Message.acknowledge then all three messages should be acknowledged. Brent -----Original Message----- From: jms...@li... [mailto:jms...@li...]On Behalf Of Tim Anderson Sent: Sunday, November 14, 2004 4:19 AM To: jms...@li... Subject: RE: [jmscts-user] Is ClientAcknowledgeTest.testPartialClientAcknowledge correct? > Sent: Saturday, 13 November 2004 6:12 AM > > The > org.exolab.jmscts.test.session.clientack.ClientAcknowledgeTest > .testPartialCl > ientAcknowledge test receives 10 messages, acknowledges the > fifth message, calls Session.recover() and then expects to > receive the last five messages. The thinking here seems to be > that Message.acknowledge() acknowledges all received messages > up to and including the message that was acknowledged. While > I find this more logical than the JMS specification, I don't > believe that this is the correct interpretation of the JMS > specification. The JMS 1.1 specification has the following comment: > > "A possible misinterpretation of the existing Java API > documentation for Message.acknowledge assumed that only > messages received prior to "this" message should be > acknowledged. The updated Java API documentation statement > emphasizes that message acknowledgement is really a > session-level activity and that this message is only being > used to identify the session in order to acknowledge all > messages consumed by the session. The acknowledge method was > placed in the message object only to enable easy access to > acknowledgement capability within a message listener's > onMessage method. This change aligns the specification and > Java API documentation to define Message.acknowledge in the > same manner." > > I think it is. In the JMS 1.1 spec, section 4.4.11 "Message Acknowledgment" talks about the behaviour of Message.acknowledge with CLIENT_ACKNOWLEDGE and Session.recover: "With this option, a client acknowledges a message by calling the message's acknowledge method. Acknowledging a consumed message automatically acknowledges the receipt of all messages that have been delivered by its session. ... A session's recover method is used to stop a session and restart it with its first unacknowledged message. In effect, the session's series of delivered messages is reset to the point after its last acknowledged message." I don't see any other way of interpreting the above. The clarification in the specification may be allowing for the fact that a MessageListener may be registered with multiple Session instances, and that invoking Message.acknowledge will only acknowledge messages consumed by the Session that invoked the MessageListener - as opposed to acknowledging messages consumed across all Sessions that the MessageListener is registered. -Tim ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ jmscts-user mailing list jms...@li... https://lists.sourceforge.net/lists/listinfo/jmscts-user |
|
From: Tim A. <tm...@ne...> - 2004-11-14 12:13:29
|
> Sent: Saturday, 13 November 2004 6:12 AM > > The=20 > org.exolab.jmscts.test.session.clientack.ClientAcknowledgeTest > .testPartialCl > ientAcknowledge test receives 10 messages, acknowledges the=20 > fifth message, calls Session.recover() and then expects to=20 > receive the last five messages. The thinking here seems to be=20 > that Message.acknowledge() acknowledges all received messages=20 > up to and including the message that was acknowledged. While=20 > I find this more logical than the JMS specification, I don't=20 > believe that this is the correct interpretation of the JMS=20 > specification. The JMS 1.1 specification has the following comment: >=20 > "A possible misinterpretation of the existing Java API=20 > documentation for Message.acknowledge assumed that only=20 > messages received prior to "this" message should be=20 > acknowledged. The updated Java API documentation statement=20 > emphasizes that message acknowledgement is really a=20 > session-level activity and that this message is only being=20 > used to identify the session in order to acknowledge all=20 > messages consumed by the session. The acknowledge method was=20 > placed in the message object only to enable easy access to=20 > acknowledgement capability within a message listener's=20 > onMessage method. This change aligns the specification and=20 > Java API documentation to define Message.acknowledge in the=20 > same manner." >=20 >=20 I think it is. In the JMS 1.1 spec, section 4.4.11 "Message = Acknowledgment" talks about the behaviour of Message.acknowledge with CLIENT_ACKNOWLEDGE and Session.recover: "With this option, a client acknowledges a message by calling the = message's acknowledge method. Acknowledging a consumed message automatically=20 acknowledges the receipt of all messages that have been delivered by = its=20 session. ... A session's recover method is used to stop a session and restart it = with=20 its first unacknowledged message. In effect, the session's series of=20 delivered messages is reset to the point after its last acknowledged=20 message." I don't see any other way of interpreting the above. The clarification in the specification may be allowing for the fact that a MessageListener = may be registered with multiple Session instances, and that invoking Message.acknowledge will only acknowledge messages consumed by the Session that invoked the MessageListener - as opposed to acknowledging messages consumed across all Sessions that the MessageListener is registered. -Tim |
|
From: Brent P. <bre...@we...> - 2004-11-12 19:11:49
|
The org.exolab.jmscts.test.session.clientack.ClientAcknowledgeTest.testPartialCl ientAcknowledge test receives 10 messages, acknowledges the fifth message, calls Session.recover() and then expects to receive the last five messages. The thinking here seems to be that Message.acknowledge() acknowledges all received messages up to and including the message that was acknowledged. While I find this more logical than the JMS specification, I don't believe that this is the correct interpretation of the JMS specification. The JMS 1.1 specification has the following comment: "A possible misinterpretation of the existing Java API documentation for Message.acknowledge assumed that only messages received prior to "this" message should be acknowledged. The updated Java API documentation statement emphasizes that message acknowledgement is really a session-level activity and that this message is only being used to identify the session in order to acknowledge all messages consumed by the session. The acknowledge method was placed in the message object only to enable easy access to acknowledgement capability within a message listener's onMessage method. This change aligns the specification and Java API documentation to define Message.acknowledge in the same manner." |
|
From: Tim A. <tm...@ne...> - 2004-02-04 07:09:27
|
JMS CTS 0.5-b2 is now available for download. Download the latest binary or source distributions from http://jmscts.sourceforge.net/downloads.html, or visit the JMS CTS homepage at http://jmscts.sourceforge.net/ The 0.5-b2 release includes the following changes since 0.5-b1: . Added coverage of MessageProducer.getTimeToLive() and MessageProducer.setTimeToLive(). . Added coverage of section 3.4.7 - JMSRedelivered . Added coverage of section 3.4.9 - JMSExpiration . Added coverage for message republication . Changed reporting for RFE 826562 - order requirements, test cases in coverage.html . Changed reporting to include stack traces in failure descriptions. . Added coverage of section 3.12 - Provider Implementations of JMS Message Interfaces. . Fixed bug 819193 - Can't filter tests on ack type . Fixed bug 818994 - Errors in test setUp() and tearDown() not reported . Fixed bug 887462 - QueueBrowser should be excluded from connection.stopped test . Fixed bug 879678 - StreamMessageTest.testIncrementalReadBytes() not compliant Regards, Tim |
|
From: Tim A. <tm...@ne...> - 2003-10-01 09:37:23
|
After a long period of incubation, JMS CTS v0.5-b1 is now available for download. JMS CTS is a free, open-source compliance test suite for Java Message Service (JMS) implementations. Download the latest binary or source distributions from http://jmscts.sourceforge.net/downloads.html, or visit the JMS CTS homepage at http://jmscts.sourceforge.net/ cheers, the JMS CTS team |