Blocked JMS tests in 2.x

[andrew cooke-2]

Hi,

I am trying to understand the state of JMS in 2.x.  Several transaction
related tests are excluded - what is the associated JIRA issue?  If there
is no JIRA, can someone please describe the problem - is it config
related?

I've also asked for more info on issues 2065, 2071 and the related blocker
2011, in the issues themselves.

Finally, if anyone knows of issues related to these (excluded) tests in
2.x, I would appreciate knowing what they are:
org.mule.providers.jms.functional.MultipleJmsConnectorsTestCase
org.mule.providers.jms.functional.ActiveMQJmsTopicFunctionalTestCase
org.mule.providers.jms.functional.ActiveMQJmsQueueFunctionalTestCase

Thanks,
Andrew



---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[Anatoli Kuzmin-2]

Andrew,

 

I'll delete this tests in the near future,

I rewrote test for ActimeMQ (single tx) and topics
also test for MultipleJms connector exists

 

I'm rewriting the tests for XA transaction,  but there is a need to add support for resume/suspend operation

 

On 10/19/07, andrew cooke <acooke@...> wrote:

Hi,

I am trying to understand the state of JMS in 2.x.  Several transaction
related tests are excluded - what is the associated JIRA issue?  If there
is no JIRA, can someone please describe the problem - is it config
related?

I've also asked for more info on issues 2065, 2071 and the related blocker
2011, in the issues themselves.

Finally, if anyone knows of issues related to these (excluded) tests in
2.x, I would appreciate knowing what they are:
org.mule.providers.jms.functional.MultipleJmsConnectorsTestCase
org.mule.providers.jms.functional.ActiveMQJmsTopicFunctionalTestCase
org.mule.providers.jms.functional.ActiveMQJmsQueueFunctionalTestCase

Thanks,
Andrew



---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

--
Best regards,
Anatoli Kuzmin

[andrew cooke-2]

> Andrew,
>
> I'll delete this tests in the near future,
> I rewrote test for ActimeMQ (single tx) and topics
> also test for MultipleJms connector exists
>
> I'm rewriting the tests for XA transaction,  but there is a need to add
> support for resume/suspend operation

Thanks for the reply

(I am asking about this because we had a review of 2.x and none of us
understood what was happening with JMS - there's no real problem, I'm just
trying to collect information.).

So you will replace all these tests, and already have better tests working
elsewhere?  Can you estimate when this will be done?

If you are changing tests so that they use configuration files then you
may have problems with definition parsers etc - I think JMS is going to be
the hardest transport to configure.  Is there any way I can help?  Maybe
the best thing to do is make the configuration very simple at first and
then, once the tests are working, give me the job of improving the
configuration?

Thanks,
Andrew

> On 10/19/07, andrew cooke <acooke@...> wrote:
>
>>
>> Hi,
>>
>> I am trying to understand the state of JMS in 2.x.  Several transaction
>> related tests are excluded - what is the associated JIRA issue?  If
>> there
>> is no JIRA, can someone please describe the problem - is it config
>> related?
>>
>> I've also asked for more info on issues 2065, 2071 and the related
>> blocker
>> 2011, in the issues themselves.
>>
>> Finally, if anyone knows of issues related to these (excluded) tests in
>> 2.x, I would appreciate knowing what they are:
>> org.mule.providers.jms.functional.MultipleJmsConnectorsTestCase
>> org.mule.providers.jms.functional.ActiveMQJmsTopicFunctionalTestCase
>> org.mule.providers.jms.functional.ActiveMQJmsQueueFunctionalTestCase
>>
>> Thanks,
>> Andrew
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
>
> --
> Best regards,
> Anatoli Kuzmin
>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[Anatoli Kuzmin-2]

Andrew,

I have some tests for XA and jms in different places
but
1. I'm waiting "resume/suspend"
I can't do some test cases without this action
2. Only recently сritical bugs with jms and tx have been fixed

On 10/22/07, andrew cooke <acooke@...> wrote:

> Andrew,
>
> I'll delete this tests in the near future,
> I rewrote test for ActimeMQ (single tx) and topics
> also test for MultipleJms connector exists
>
> I'm rewriting the tests for XA transaction,  but there is a need to add
> support for resume/suspend operation

Thanks for the reply

(I am asking about this because we had a review of 2.x and none of us
understood what was happening with JMS - there's no real problem, I'm just
trying to collect information.).

So you will replace all these tests, and already have better tests working
elsewhere?  Can you estimate when this will be done?

If you are changing tests so that they use configuration files then you
may have problems with definition parsers etc - I think JMS is going to be
the hardest transport to configure.  Is there any way I can help?  Maybe
the best thing to do is make the configuration very simple at first and
then, once the tests are working, give me the job of improving the
configuration?

Thanks,
Andrew

> On 10/19/07, andrew cooke <acooke@...> wrote:
>
>>
>> Hi,
>>
>> I am trying to understand the state of JMS in 2.x.  Several transaction
>> related tests are excluded - what is the associated JIRA issue?  If
>> there
>> is no JIRA, can someone please describe the problem - is it config
>> related?
>>
>> I've also asked for more info on issues 2065, 2071 and the related
>> blocker
>> 2011, in the issues themselves.
>>
>> Finally, if anyone knows of issues related to these (excluded) tests in
>> 2.x, I would appreciate knowing what they are:
>> org.mule.providers.jms.functional.MultipleJmsConnectorsTestCase
>> org.mule.providers.jms.functional.ActiveMQJmsTopicFunctionalTestCase
>> org.mule.providers.jms.functional.ActiveMQJmsQueueFunctionalTestCase
>>
>> Thanks,
>> Andrew
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>
>
> --
> Best regards,
> Anatoli Kuzmin
>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

--
Best regards,
Anatoli Kuzmin

[Ross Mason-3]

Anatoli,

Who is dealing with suspend/resume functionality?

Cheers,

Ross Mason

MuleSource

 

Malta Tel: [phone]

UK Tel: [phone]

US Tel: [phone]

On 22 Oct 2007, at 22:43, Anatoli Kuzmin wrote:

Andrew,

I have some tests for XA and jms in different places
but
1. I'm waiting "resume/suspend"
I can't do some test cases without this action
2. Only recently сritical bugs with jms and tx have been fixed

On 10/22/07, andrew cooke <acooke@...> wrote:

> Andrew,
>
> I'll delete this tests in the near future,
> I rewrote test for ActimeMQ (single tx) and topics
> also test for MultipleJms connector exists
>
> I'm rewriting the tests for XA transaction,  but there is a need to add
> support for resume/suspend operation

Thanks for the reply

(I am asking about this because we had a review of 2.x and none of us
understood what was happening with JMS - there's no real problem, I'm just
trying to collect information.).

So you will replace all these tests, and already have better tests working
elsewhere?  Can you estimate when this will be done?

If you are changing tests so that they use configuration files then you
may have problems with definition parsers etc - I think JMS is going to be
the hardest transport to configure.  Is there any way I can help?  Maybe
the best thing to do is make the configuration very simple at first and
then, once the tests are working, give me the job of improving the
configuration?

Thanks,
Andrew

> On 10/19/07, andrew cooke <acooke@...> wrote:
>
>>
>> Hi,
>>
>> I am trying to understand the state of JMS in 2.x.  Several transaction
>> related tests are excluded - what is the associated JIRA issue?  If
>> there
>> is no JIRA, can someone please describe the problem - is it config
>> related?
>>
>> I've also asked for more info on issues 2065, 2071 and the related
>> blocker
>> 2011, in the issues themselves.
>>
>> Finally, if anyone knows of issues related to these (excluded) tests in
>> 2.x, I would appreciate knowing what they are:
>> org.mule.providers.jms.functional.MultipleJmsConnectorsTestCase
>> org.mule.providers.jms.functional.ActiveMQJmsTopicFunctionalTestCase
>> org.mule.providers.jms.functional.ActiveMQJmsQueueFunctionalTestCase
>>
>> Thanks,
>> Andrew
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>
>
> --
> Best regards,
> Anatoli Kuzmin
>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

--
Best regards,
Anatoli Kuzmin

[Andrew Perepelytsya]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Ross, nobody at the moment, but it was supposed to be me. Anatoli assists me here whenever possible. Current engagements pushed it back.

Andrew

On 10/22/07, Ross Mason <themuleman@...> wrote:

Anatoli,

Who is dealing with suspend/resume functionality?

Cheers,

Ross Mason

MuleSource

 

Malta Tel: [phone]

UK Tel: [phone]

US Tel: [phone]

On 22 Oct 2007, at 22:43, Anatoli Kuzmin wrote:

Andrew,

I have some tests for XA and jms in different places
but
1. I'm waiting "resume/suspend"
I can't do some test cases without this action
2. Only recently сritical bugs with jms and tx have been fixed

On 10/22/07, andrew cooke <acooke@...> wrote:

> Andrew,
>
> I'll delete this tests in the near future,
> I rewrote test for ActimeMQ (single tx) and topics
> also test for MultipleJms connector exists
>
> I'm rewriting the tests for XA transaction,  but there is a need to add
> support for resume/suspend operation

Thanks for the reply

(I am asking about this because we had a review of 2.x and none of us
understood what was happening with JMS - there's no real problem, I'm just
trying to collect information.).

So you will replace all these tests, and already have better tests working
elsewhere?  Can you estimate when this will be done?

If you are changing tests so that they use configuration files then you
may have problems with definition parsers etc - I think JMS is going to be
the hardest transport to configure.  Is there any way I can help?  Maybe
the best thing to do is make the configuration very simple at first and
then, once the tests are working, give me the job of improving the
configuration?

Thanks,
Andrew

> On 10/19/07, andrew cooke <acooke@...> wrote:
>
>>
>> Hi,
>>
>> I am trying to understand the state of JMS in 2.x.  Several transaction
>> related tests are excluded - what is the associated JIRA issue?  If
>> there
>> is no JIRA, can someone please describe the problem - is it config
>> related?
>>
>> I've also asked for more info on issues 2065, 2071 and the related
>> blocker
>> 2011, in the issues themselves.
>>
>> Finally, if anyone knows of issues related to these (excluded) tests in
>> 2.x, I would appreciate knowing what they are:
>> org.mule.providers.jms.functional.MultipleJmsConnectorsTestCase
>> org.mule.providers.jms.functional.ActiveMQJmsTopicFunctionalTestCase
>> org.mule.providers.jms.functional.ActiveMQJmsQueueFunctionalTestCase
>>
>> Thanks,
>> Andrew
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>
>
> --
> Best regards,
> Anatoli Kuzmin
>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

--
Best regards,
Anatoli Kuzmin