Mule 2.x Stability

[Mike Cantrell]

How many of you are using Mule 2.x in a production environment? I see that the EE edition is still based off of the 1.x code. I've ran into enough major bugs in 2.x to make me consider reverting back to 1.x. What is the general concensus about 2.x stability in general?

[Daniel Feist]

Hi,

Just out of interest what blockers or major issue are you experiencing  
with 2.0.2?  Are there already JIRA issues for these?

thanks,
Dan

On Aug 18, 2008, at 12:40 PM, Mike Cantrell wrote:

> How many of you are using Mule 2.x in a production environment? I  
> see that the EE edition is still based off of the 1.x code. I've ran  
> into enough major bugs in 2.x to make me consider reverting back to  
> 1.x. What is the general concensus about 2.x stability in general?


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

    http://xircles.codehaus.org/manage_email

[Dimitar Dimitrov]

I am using Mule 2.0.1 in production environment for non-critical application. I find it stable in terms that it doesn't crash randomly, have memory leaks or drop messages. That said, there are some rough edges and non-critical bugs/undocumented behavior, which are usually easy enough to work around.

I would recommend that you use 2.0 and save yourself the migration (btw, 1.x code line is more mature, but still far from perfect ;-)

Dimitar

[Steve Olson]

We also do Mule 2.0.2 stuff in prod, about 35 different services.  We have some small issues with stuff (email connector, FTP connector, WebsphereMQ non-JMS recipient patch), and not-yet-fully-explored behavior with XA (transaction management) and WebsphereMQ, but other than that it's been stable.  Mule deployables (ours are wars deployed under Tomcat) run for months with no issues.

Dimitar Dimitrov wrote:

I am using Mule 2.0.1 in production environment for non-critical application. I find it stable in terms that it doesn't crash randomly, have memory leaks or drop messages. That said, there are some rough edges and non-critical bugs/undocumented behavior, which are usually easy enough to work around.

I would recommend that you use 2.0 and save yourself the migration (btw, 1.x code line is more mature, but still far from perfect ;-)

Dimitar

[PawanModi]

Hello List,

I am also using Mule2.0 in my work. I am using Mule JMS transport with OpenMQ JMS broker. My application  is running on build server with Mule ESB for more then 15 days now. I encounter no problem so far.
I dont know the performance of earlier version of Mule i.e. Mule1.4.3.

I will recommend to migrate to Mule2.x. I hope documentation will be ready soon for Mule2.x.

Cheer,
Pawan Modi



We also do Mule 2.0.2 stuff in prod, about 35 different services.  We have some small issues with stuff (email connector, FTP connector, WebsphereMQ non-JMS recipient patch), and not-yet-fully-explored behavior with XA (transaction management) and WebsphereMQ, but other than that it's been stable.  Mule deployables (ours are wars deployed under Tomcat) run for months with no issues.

Dimitar Dimitrov wrote:

I am using Mule 2.0.1 in production environment for non-critical application. I find it stable in terms that it doesn't crash randomly, have memory leaks or drop messages. That said, there are some rough edges and non-critical bugs/undocumented behavior, which are usually easy enough to work around.

I would recommend that you use 2.0 and save yourself the migration (btw, 1.x code line is more mature, but still far from perfect ;-)

Dimitar

[antoine.borg]

Hi Pawan,

This is great news - coupled with MuleSource's recent tests
(www.mulesource.com/solutions/Whitepaper_perf_test_results.pdf), it sounds
like those people who were hesitant to upgrade/use Mule 2 should be happy to
do so now.

Antoine


Antoine Borg, Senior Consultant | Tel: [phone]
ricston Ltd., BP 2, 1180 Uccle, Brussels, BELGIUM
email: antoine.borg@... | blog: blog.ricston.com | web: ricston.com

-----Original Message-----
From: PawanModi [mailto:modipawan8126@...]
Sent: Tuesday, August 26, 2008 8:49 AM
To: user@...
Subject: Re: [mule-user] Mule 2.x Stability


Hello List,

I am also using Mule2.0 in my work. I am using Mule JMS transport with
OpenMQ JMS broker. My application  is running on build server with Mule ESB
for more then 15 days now. I encounter no problem so far.
I dont know the performance of earlier version of Mule i.e. Mule1.4.3.

I will recommend to migrate to Mule2.x. I hope documentation will be ready
soon for Mule2.x.

Cheer,
Pawan Modi



Steve Olson wrote:

>
> We also do Mule 2.0.2 stuff in prod, about 35 different services.  We
> have some small issues with stuff (email connector, FTP connector,
> WebsphereMQ non-JMS recipient patch), and not-yet-fully-explored
> behavior with XA (transaction management) and WebsphereMQ, but other
> than that it's been stable.  Mule deployables (ours are wars deployed
> under Tomcat) run for months with no issues.
>
>
> Dimitar Dimitrov wrote:
>>
>> I am using Mule 2.0.1 in production environment for non-critical
>> application. I find it stable in terms that it doesn't crash
>> randomly, have memory leaks or drop messages. That said, there are
>> some rough edges and non-critical bugs/undocumented behavior, which
>> are usually easy enough to work around.
>>
>> I would recommend that you use 2.0 and save yourself the migration
>> (btw, 1.x code line is more mature, but still far from perfect ;-)
>>
>> Dimitar
>>
>
>

--
View this message in context:
http://www.nabble.com/Mule-2.x-Stability-tp19034298p19156706.html
Sent from the Mule - User mailing list archive at Nabble.com.


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

    http://xircles.codehaus.org/manage_email



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

    http://xircles.codehaus.org/manage_email

[Ross Mason-3]

Hi Mike,

We're getting very close to the 2.x EE release. The focus has been to  
iron out these wrinkles before we do the EE release.   Stability in  
terms of memory usage, leaks performance and general random exception  
is very good.  We're still rounding off the rough edges.

It would really help if you report any issues you are getting to  
ensure the knowledge is not lost.

Cheers,

Ross Mason
CTO, Co-Founder
MuleSource Inc.

http://mulesource.com | http://blog.rossmason.com





On 18 Aug 2008, at 08:40, Mike Cantrell wrote:

> How many of you are using Mule 2.x in a production environment? I  
> see that the EE edition is still based off of the 1.x code. I've ran  
> into enough major bugs in 2.x to make me consider reverting back to  
> 1.x. What is the general concensus about 2.x stability in general?


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

    http://xircles.codehaus.org/manage_email

[PawanModi]

Hello Antoine,

I saw the white paper your provided link for. Is there any way to publish information about the tests i performed?   I wish this information will be very useful for them who hesitate to use Mule in their environment. Many people drop their plans about using mule due to lack of documentation & information.

Let me know your thoughts.

With regards,
Pawan Modi

antoine.borg wrote:

Hi Pawan,

This is great news - coupled with MuleSource's recent tests
(www.mulesource.com/solutions/Whitepaper_perf_test_results.pdf), it sounds
like those people who were hesitant to upgrade/use Mule 2 should be happy to
do so now.

Antoine


Antoine Borg, Senior Consultant | Tel: [phone]
ricston Ltd., BP 2, 1180 Uccle, Brussels, BELGIUM
email: [e-mail] | blog: blog.ricston.com | web: ricston.com

-----Original Message-----
From: PawanModi [mailto:[e-mail]]
Sent: Tuesday, August 26, 2008 8:49 AM
To: [e-mail]
Subject: Re: [mule-user] Mule 2.x Stability


Hello List,

I am also using Mule2.0 in my work. I am using Mule JMS transport with
OpenMQ JMS broker. My application  is running on build server with Mule ESB
for more then 15 days now. I encounter no problem so far.
I dont know the performance of earlier version of Mule i.e. Mule1.4.3.

I will recommend to migrate to Mule2.x. I hope documentation will be ready
soon for Mule2.x.

Cheer,
Pawan Modi



Steve Olson wrote:
>
> We also do Mule 2.0.2 stuff in prod, about 35 different services.  We
> have some small issues with stuff (email connector, FTP connector,
> WebsphereMQ non-JMS recipient patch), and not-yet-fully-explored
> behavior with XA (transaction management) and WebsphereMQ, but other
> than that it's been stable.  Mule deployables (ours are wars deployed
> under Tomcat) run for months with no issues.
>
>
> Dimitar Dimitrov wrote:
>>
>> I am using Mule 2.0.1 in production environment for non-critical
>> application. I find it stable in terms that it doesn't crash
>> randomly, have memory leaks or drop messages. That said, there are
>> some rough edges and non-critical bugs/undocumented behavior, which
>> are usually easy enough to work around.
>>
>> I would recommend that you use 2.0 and save yourself the migration
>> (btw, 1.x code line is more mature, but still far from perfect ;-)
>>
>> Dimitar
>>
>
>

--
View this message in context:
http://www.nabble.com/Mule-2.x-Stability-tp19034298p19156706.html
Sent from the Mule - User mailing list archive at Nabble.com.


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

    http://xircles.codehaus.org/manage_email



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

    http://xircles.codehaus.org/manage_email

[antoine.borg]

Hello Pawan,

If you have run tests and wish to publish the information, I suggest the
following:

1) Post the results here. That way anyone who already uses Mule and this
list will see them.
2) If you like, I could put those figures into a blog post on my blog:
http://blog.ricston.com. If you have a blog of your own, perhaps that may be
a better place for them.
3) Another suitable location would be to write up a short article and
publish it through www.theserverside.com which would probably reach a wider
audience.

I suggest all 3 of the above to get the widest coverage of the good news.

A


Antoine Borg, Senior Consultant | Tel: [phone]
ricston Ltd., BP 2, 1180 Uccle, Brussels, BELGIUM
email: antoine.borg@... | blog: blog.ricston.com | web: ricston.com

-----Original Message-----
From: PawanModi [mailto:modipawan8126@...]
Sent: Thursday, September 04, 2008 5:32 AM
To: user@...
Subject: RE: [mule-user] Mule 2.x Stability


Hello Antoine,

I saw the white paper your provided link for. Is there any way to publish
information about the tests i performed?   I wish this information will be
very useful for them who hesitate to use Mule in their environment. Many
people drop their plans about using mule due to lack of documentation &
information.

Let me know your thoughts.

With regards,
Pawan Modi




antoine.borg wrote:

>
> Hi Pawan,
>
> This is great news - coupled with MuleSource's recent tests
> (www.mulesource.com/solutions/Whitepaper_perf_test_results.pdf), it
> sounds like those people who were hesitant to upgrade/use Mule 2
> should be happy to do so now.
>
> Antoine
>
>
> Antoine Borg, Senior Consultant | Tel: [phone] ricston Ltd., BP
> 2, 1180 Uccle, Brussels, BELGIUM
> email: antoine.borg@... | blog: blog.ricston.com | web:
> ricston.com
>
> -----Original Message-----
> From: PawanModi [mailto:modipawan8126@...]
> Sent: Tuesday, August 26, 2008 8:49 AM
> To: user@...
> Subject: Re: [mule-user] Mule 2.x Stability
>
>
> Hello List,
>
> I am also using Mule2.0 in my work. I am using Mule JMS transport with
> OpenMQ JMS broker. My application  is running on build server with
> Mule ESB for more then 15 days now. I encounter no problem so far.
> I dont know the performance of earlier version of Mule i.e. Mule1.4.3.
>
> I will recommend to migrate to Mule2.x. I hope documentation will be
> ready soon for Mule2.x.
>
> Cheer,
> Pawan Modi
>
>
>
> Steve Olson wrote:
>>
>> We also do Mule 2.0.2 stuff in prod, about 35 different services.  We
>> have some small issues with stuff (email connector, FTP connector,
>> WebsphereMQ non-JMS recipient patch), and not-yet-fully-explored
>> behavior with XA (transaction management) and WebsphereMQ, but other
>> than that it's been stable.  Mule deployables (ours are wars deployed
>> under Tomcat) run for months with no issues.
>>
>>
>> Dimitar Dimitrov wrote:
>>>
>>> I am using Mule 2.0.1 in production environment for non-critical
>>> application. I find it stable in terms that it doesn't crash
>>> randomly, have memory leaks or drop messages. That said, there are
>>> some rough edges and non-critical bugs/undocumented behavior, which
>>> are usually easy enough to work around.
>>>
>>> I would recommend that you use 2.0 and save yourself the migration
>>> (btw, 1.x code line is more mature, but still far from perfect ;-)
>>>
>>> Dimitar
>>>
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/Mule-2.x-Stability-tp19034298p19156706.html
> Sent from the Mule - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>
>

--
View this message in context:
http://www.nabble.com/Mule-2.x-Stability-tp19034298p19302737.html
Sent from the Mule - User mailing list archive at Nabble.com.


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

    http://xircles.codehaus.org/manage_email



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

    http://xircles.codehaus.org/manage_email

[Ross Mason-3]

Hi,

That would be great. I can put you in touch with someone from  
MuleSource to support you in getting your experience published. We can  
probably push out to theserverside or infoQ.

Cheers,

Ross Mason
CTO, Co-Founder
MuleSource Inc.

http://mulesource.com | http://blog.rossmason.com





On 3 Sep 2008, at 20:31, PawanModi wrote:

>
> Hello Antoine,
>
> I saw the white paper your provided link for. Is there any way to  
> publish
> information about the tests i performed?   I wish this information  
> will be
> very useful for them who hesitate to use Mule in their environment.  
> Many
> people drop their plans about using mule due to lack of  
> documentation &
> information.
>
> Let me know your thoughts.
>
> With regards,
> Pawan Modi
>
>
>
>
> antoine.borg wrote:
>>
>> Hi Pawan,
>>
>> This is great news - coupled with MuleSource's recent tests
>> (www.mulesource.com/solutions/Whitepaper_perf_test_results.pdf), it  
>> sounds
>> like those people who were hesitant to upgrade/use Mule 2 should be  
>> happy
>> to
>> do so now.
>>
>> Antoine
>>
>>
>> Antoine Borg, Senior Consultant | Tel: [phone]
>> ricston Ltd., BP 2, 1180 Uccle, Brussels, BELGIUM
>> email: antoine.borg@... | blog: blog.ricston.com | web:
>> ricston.com
>>
>> -----Original Message-----
>> From: PawanModi [mailto:modipawan8126@...]
>> Sent: Tuesday, August 26, 2008 8:49 AM
>> To: user@...
>> Subject: Re: [mule-user] Mule 2.x Stability
>>
>>
>> Hello List,
>>
>> I am also using Mule2.0 in my work. I am using Mule JMS transport  
>> with
>> OpenMQ JMS broker. My application  is running on build server with  
>> Mule
>> ESB
>> for more then 15 days now. I encounter no problem so far.
>> I dont know the performance of earlier version of Mule i.e.  
>> Mule1.4.3.
>>
>> I will recommend to migrate to Mule2.x. I hope documentation will  
>> be ready
>> soon for Mule2.x.
>>
>> Cheer,
>> Pawan Modi
>>
>>
>>
>> Steve Olson wrote:
>>>
>>> We also do Mule 2.0.2 stuff in prod, about 35 different services.  
>>> We
>>> have some small issues with stuff (email connector, FTP connector,
>>> WebsphereMQ non-JMS recipient patch), and not-yet-fully-explored
>>> behavior with XA (transaction management) and WebsphereMQ, but other
>>> than that it's been stable.  Mule deployables (ours are wars  
>>> deployed
>>> under Tomcat) run for months with no issues.
>>>
>>>
>>> Dimitar Dimitrov wrote:
>>>>
>>>> I am using Mule 2.0.1 in production environment for non-critical
>>>> application. I find it stable in terms that it doesn't crash
>>>> randomly, have memory leaks or drop messages. That said, there are
>>>> some rough edges and non-critical bugs/undocumented behavior, which
>>>> are usually easy enough to work around.
>>>>
>>>> I would recommend that you use 2.0 and save yourself the migration
>>>> (btw, 1.x code line is more mature, but still far from perfect ;-)
>>>>
>>>> Dimitar
>>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Mule-2.x-Stability-tp19034298p19156706.html
>> Sent from the Mule - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Mule-2.x-Stability-tp19034298p19302737.html
> Sent from the Mule - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

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

    http://xircles.codehaus.org/manage_email

[PawanModi]

Hello Ross,

I appreciate your support in this. I can share my exprecience about various mule versions.
I can also provide logs if needed. Let me know what all information do you expect from my side.

Thanks & regards,
Pawan Modi

Ross Mason-3 wrote:

Hi,

That would be great. I can put you in touch with someone from  
MuleSource to support you in getting your experience published. We can  
probably push out to theserverside or infoQ.

Cheers,

Ross Mason
CTO, Co-Founder
MuleSource Inc.

http://mulesource.com | http://blog.rossmason.com





On 3 Sep 2008, at 20:31, PawanModi wrote:

>
> Hello Antoine,
>
> I saw the white paper your provided link for. Is there any way to  
> publish
> information about the tests i performed?   I wish this information  
> will be
> very useful for them who hesitate to use Mule in their environment.  
> Many
> people drop their plans about using mule due to lack of  
> documentation &
> information.
>
> Let me know your thoughts.
>
> With regards,
> Pawan Modi
>
>
>
>
> antoine.borg wrote:
>>
>> Hi Pawan,
>>
>> This is great news - coupled with MuleSource's recent tests
>> (www.mulesource.com/solutions/Whitepaper_perf_test_results.pdf), it  
>> sounds
>> like those people who were hesitant to upgrade/use Mule 2 should be  
>> happy
>> to
>> do so now.
>>
>> Antoine
>>
>>
>> Antoine Borg, Senior Consultant | Tel: [phone]
>> ricston Ltd., BP 2, 1180 Uccle, Brussels, BELGIUM
>> email: [e-mail] | blog: blog.ricston.com | web:
>> ricston.com
>>
>> -----Original Message-----
>> From: PawanModi [mailto:[e-mail]]
>> Sent: Tuesday, August 26, 2008 8:49 AM
>> To: [e-mail]
>> Subject: Re: [mule-user] Mule 2.x Stability
>>
>>
>> Hello List,
>>
>> I am also using Mule2.0 in my work. I am using Mule JMS transport  
>> with
>> OpenMQ JMS broker. My application  is running on build server with  
>> Mule
>> ESB
>> for more then 15 days now. I encounter no problem so far.
>> I dont know the performance of earlier version of Mule i.e.  
>> Mule1.4.3.
>>
>> I will recommend to migrate to Mule2.x. I hope documentation will  
>> be ready
>> soon for Mule2.x.
>>
>> Cheer,
>> Pawan Modi
>>
>>
>>
>> Steve Olson wrote:
>>>
>>> We also do Mule 2.0.2 stuff in prod, about 35 different services.  
>>> We
>>> have some small issues with stuff (email connector, FTP connector,
>>> WebsphereMQ non-JMS recipient patch), and not-yet-fully-explored
>>> behavior with XA (transaction management) and WebsphereMQ, but other
>>> than that it's been stable.  Mule deployables (ours are wars  
>>> deployed
>>> under Tomcat) run for months with no issues.
>>>
>>>
>>> Dimitar Dimitrov wrote:
>>>>
>>>> I am using Mule 2.0.1 in production environment for non-critical
>>>> application. I find it stable in terms that it doesn't crash
>>>> randomly, have memory leaks or drop messages. That said, there are
>>>> some rough edges and non-critical bugs/undocumented behavior, which
>>>> are usually easy enough to work around.
>>>>
>>>> I would recommend that you use 2.0 and save yourself the migration
>>>> (btw, 1.x code line is more mature, but still far from perfect ;-)
>>>>
>>>> Dimitar
>>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Mule-2.x-Stability-tp19034298p19156706.html
>> Sent from the Mule - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Mule-2.x-Stability-tp19034298p19302737.html
> Sent from the Mule - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>


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

    http://xircles.codehaus.org/manage_email