Re: [Carbon-dev] Qpid Frustration

[Danushka Menikkumbura]

> As I believe adding configuration files into a product is the
>> responsibility of the product team. Not yours.
>
>
Sumedha,

Let me rephrase.

You do not have to do anything extra to get Qpid to work in your product. In
fact it is installable as a feature.

What I meant was when we pack our products, we manually copy qpid
configuration files from the Carbon distribution that is built in the middle
to the pack. Do you know why we do that?. I said the product team was
responsible for copying files into this distribution.

I hope it is little better this time :-(.

Thanks,
Danushka
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Sumedha Rubasinghe]

On Fri, Apr 1, 2011 at 12:51 PM, Danushka Menikkumbura wrote:

> As I believe adding configuration files into a product is the
> responsibility of the product team. Not yours.



Dhanushka,
I don't understand your statement. What we build is small pieces of a
platform. The products we have are simply a collection of specific set of
selected features.
If the component(qpid) you built cannot act as an independent feature (I am
not talking about compile time or run time dependencies),  that is that
component's problem.

True, I understand that there could be product specific configurations. But
if the component in the default mode breaks other members of the platform,
that's the wrong way to move ahead & think as well..

/sumedha





> In fact what we do is to add an entry into the bin.xml to copy qpid
> configuration files into the product distribution from the carbon core
> distribution that is built in the middle (which is wrong as I believe). I
> could have blindly modified all bin.xml files to copy configuration. But if
> a product did not need qpid/event then having the config files alone in the
> dist is pointless.
>
> As I mentioned earlier as well, the issue in this particular case is not
> using the correct qpid libs. That is why the issue went away when you built
> event which eventually installed the latest qpid libs.
>
> It used to look for configuration files in conf/qpid/ and that is what I
> saw in your error message. So if you had built event feature, you would not
> have got this error.
>
> Thanks,
> Danushka
>
>
> On Fri, Apr 1, 2011 at 12:21 PM, Dimuthu Leelarathne wrote:
>
>> Hi,
>>
>> On Fri, Apr 1, 2011 at 11:12 AM, Pradeep Fernando wrote:
>>
>>> +1 agreed with danushka. Adding default configuration is not the
>>> solution for what dimuthu has encountered. In this case dimuthu is
>>> responsible for making the stratos distribution. Anybody working on
>>> wso2 product distribution should know what should be done in order to
>>> get the product running. No excuses.
>>
>>
>>
>> There is something very wrong here. Either technology or the process. Let
>> me ask the simple question. How did Qpid config files get copied to all
>> products and not services? How come services got second hand treatment?
>> AFAIK Qpid config files were added products by someone from Qpid team.
>>
>> So lets speculate,
>>
>> 1) Should someone from Stratos team do it?
>> 2) Should the feature be developed as self contained?
>> 3) Should technology be developed to handle this situation? Automatic
>> copying of config files?
>> 3) Should the RM of each product check the service? At minimum check
>> whether it starts?
>>
>> Copying something to 13 products is not an easy task if you want to build
>> them all check whether anything breaks (speaking by experience because I
>> have done it). If someone told me adding Qpid config files was my
>> responsibility I would create time to do it. I fixed it for manager. I
>> wasn't even aware of it until each server started hanging - one after other.
>>
>>
>>
>>> If we rely on default configs, then wso2 products will go in to
>>> production with default configs in the future. (by mistake)
>>>
>>>
>> -1. What about the config files we already ship? Don't they have default
>> configs?
>>
>> thanks,
>> dimuthu
>>
>>
>>  But having a default config will serve a different scenario. If a user
>>> deletes the qpid config files after installing the features, and we
>>> still want the server to be started then we should have default
>>> configs.
>>>
>>> --Pradeep
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Srinath Perera]

Hi Danushka,

We have to agree what is the unit of sharing in our platform. I am
think that is the component, and if so, adding the component should be
good enough to install something. If feature is the unit of sharing,
what you say do make sense.

--Srinath

On Fri, Apr 1, 2011 at 10:47 AM, Danushka Menikkumbura
 wrote:
>> a) it is your responsibility!
>> b) we have to fix this. Installing means adding the component, nothing
>> else.
>
> OK. Let me give you an example.
>
> If you use an installer that comes with a piece of software to install it,
> you do not have to worry about copying libraries or configuration files,
> adding registry entries, etc as it takes care of all that. But if you are
> smart enough you can go do all that yourself but you are responsible for
> mistakes made in any of those steps.
>
> Similarly in Carbon, if you get the feature manager to install a feature, it
> takes care of all that. If you happened to do it yourself you should do what
> it takes without making any mistakes. In fact in this particular case, it
> had nothing to do with configuration files but the latest qpid libraries
> were not used.
>
> I can continued to argue on this but it will not help anybody whatsoever. So
> if everybody thinks embedding configuration files is the way to go then I
> will look into it.
>
> But I think we have a fundamental issue in the way we build products. We
> manually copy stuff (mostly configuration files) from the generated carbon
> distribution to the product pack we build. As I learned from Pradeep the
> generated carbon distribution contains all that should go into the product.
>
> Thanks,
> Danushka
>
>
>



-- 

Srinath Perera, Ph.D.
  Senior Software Architect, WSO2 Inc.
  Visiting Faculty, University of Moratuwa
  Member, Apache Software Foundation
  Research Scientist, Lanka Software Foundation
  Blog: http://srinathsview.blogspot.com/
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Manjula Rathnayake]

On Fri, Apr 1, 2011 at 12:49 PM, Manjula Rathnayake wrote:

>
>
> On Fri, Apr 1, 2011 at 12:21 PM, Dimuthu Leelarathne wrote:
>
>> Hi,
>>
>> On Fri, Apr 1, 2011 at 11:12 AM, Pradeep Fernando wrote:
>>
>>> +1 agreed with danushka. Adding default configuration is not the
>>> solution for what dimuthu has encountered. In this case dimuthu is
>>> responsible for making the stratos distribution. Anybody working on
>>> wso2 product distribution should know what should be done in order to
>>> get the product running. No excuses.
>>
>>
>>
>> There is something very wrong here. Either technology or the process. Let
>> me ask the simple question. How did Qpid config files get copied to all
>> products and not services? How come services got second hand treatment?
>> AFAIK Qpid config files were added products by someone from Qpid team.
>>
>
> Well, I copied all Qpid config files to products with the build I had. I
> was in trouble having a proper build on all products. So I copied to esb and
> bam products. And regarding services, I could not up services even after
> adding Qpid config files. So I avoided committing changes. And I gave
> patches for services in a discussion thread regarding this.
>
> And I agree, copying to all products and services take so time, And I could
> not apply one patch for all products since all products had changes such as,
> bin.xml resides in different folder paths, hard coded product name and
> version, some uses pom.version and some build.version.
>
>
And good thing is, now all products and services are having Qpid config
files and server get started :)

> Thank you.
>
>
>> So lets speculate,
>>
>> 1) Should someone from Stratos team do it?
>> 2) Should the feature be developed as self contained?
>> 3) Should technology be developed to handle this situation? Automatic
>> copying of config files?
>> 3) Should the RM of each product check the service? At minimum check
>> whether it starts?
>>
>> Copying something to 13 products is not an easy task if you want to build
>> them all check whether anything breaks (speaking by experience because I
>> have done it). If someone told me adding Qpid config files was my
>> responsibility I would create time to do it. I fixed it for manager. I
>> wasn't even aware of it until each server started hanging - one after other.
>>
>>
>>
>>> If we rely on default configs, then wso2 products will go in to
>>> production with default configs in the future. (by mistake)
>>>
>>>
>> -1. What about the config files we already ship? Don't they have default
>> configs?
>>
>> thanks,
>> dimuthu
>>
>>
>> But having a default config will serve a different scenario. If a user
>>> deletes the qpid config files after installing the features, and we
>>> still want the server to be started then we should have default
>>> configs.
>>>
>>> --Pradeep
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Manjula Rathnayaka
> Software Engineer
> WSO2, Inc.
> Mobile:+94 77 743 1987
>



-- 
Manjula Rathnayaka
Software Engineer
WSO2, Inc.
Mobile:+94 77 743 1987
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Danushka Menikkumbura]

As I believe adding configuration files into a product is the responsibility
of the product team. Not yours. In fact what we do is to add an entry into
the bin.xml to copy qpid configuration files into the product distribution
from the carbon core distribution that is built in the middle (which is
wrong as I believe). I could have blindly modified all bin.xml files to copy
configuration. But if a product did not need qpid/event then having the
config files alone in the dist is pointless.

As I mentioned earlier as well, the issue in this particular case is not
using the correct qpid libs. That is why the issue went away when you built
event which eventually installed the latest qpid libs.

It used to look for configuration files in conf/qpid/ and that is what I saw
in your error message. So if you had built event feature, you would not have
got this error.

Thanks,
Danushka

On Fri, Apr 1, 2011 at 12:21 PM, Dimuthu Leelarathne wrote:

> Hi,
>
> On Fri, Apr 1, 2011 at 11:12 AM, Pradeep Fernando wrote:
>
>> +1 agreed with danushka. Adding default configuration is not the
>> solution for what dimuthu has encountered. In this case dimuthu is
>> responsible for making the stratos distribution. Anybody working on
>> wso2 product distribution should know what should be done in order to
>> get the product running. No excuses.
>
>
>
> There is something very wrong here. Either technology or the process. Let
> me ask the simple question. How did Qpid config files get copied to all
> products and not services? How come services got second hand treatment?
> AFAIK Qpid config files were added products by someone from Qpid team.
>
> So lets speculate,
>
> 1) Should someone from Stratos team do it?
> 2) Should the feature be developed as self contained?
> 3) Should technology be developed to handle this situation? Automatic
> copying of config files?
> 3) Should the RM of each product check the service? At minimum check
> whether it starts?
>
> Copying something to 13 products is not an easy task if you want to build
> them all check whether anything breaks (speaking by experience because I
> have done it). If someone told me adding Qpid config files was my
> responsibility I would create time to do it. I fixed it for manager. I
> wasn't even aware of it until each server started hanging - one after other.
>
>
>
>> If we rely on default configs, then wso2 products will go in to
>> production with default configs in the future. (by mistake)
>>
>>
> -1. What about the config files we already ship? Don't they have default
> configs?
>
> thanks,
> dimuthu
>
>
>  But having a default config will serve a different scenario. If a user
>> deletes the qpid config files after installing the features, and we
>> still want the server to be started then we should have default
>> configs.
>>
>> --Pradeep
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Manjula Rathnayake]

On Fri, Apr 1, 2011 at 12:21 PM, Dimuthu Leelarathne wrote:

> Hi,
>
> On Fri, Apr 1, 2011 at 11:12 AM, Pradeep Fernando wrote:
>
>> +1 agreed with danushka. Adding default configuration is not the
>> solution for what dimuthu has encountered. In this case dimuthu is
>> responsible for making the stratos distribution. Anybody working on
>> wso2 product distribution should know what should be done in order to
>> get the product running. No excuses.
>
>
>
> There is something very wrong here. Either technology or the process. Let
> me ask the simple question. How did Qpid config files get copied to all
> products and not services? How come services got second hand treatment?
> AFAIK Qpid config files were added products by someone from Qpid team.
>

Well, I copied all Qpid config files to products with the build I had. I was
in trouble having a proper build on all products. So I copied to esb and bam
products. And regarding services, I could not up services even after adding
Qpid config files. So I avoided committing changes. And I gave patches for
services in a discussion thread regarding this.

And I agree, copying to all products and services take so time, And I could
not apply one patch for all products since all products had changes such as,
bin.xml resides in different folder paths, hard coded product name and
version, some uses pom.version and some build.version.

Thank you.


> So lets speculate,
>
> 1) Should someone from Stratos team do it?
> 2) Should the feature be developed as self contained?
> 3) Should technology be developed to handle this situation? Automatic
> copying of config files?
> 3) Should the RM of each product check the service? At minimum check
> whether it starts?
>
> Copying something to 13 products is not an easy task if you want to build
> them all check whether anything breaks (speaking by experience because I
> have done it). If someone told me adding Qpid config files was my
> responsibility I would create time to do it. I fixed it for manager. I
> wasn't even aware of it until each server started hanging - one after other.
>
>
>
>> If we rely on default configs, then wso2 products will go in to
>> production with default configs in the future. (by mistake)
>>
>>
> -1. What about the config files we already ship? Don't they have default
> configs?
>
> thanks,
> dimuthu
>
>
> But having a default config will serve a different scenario. If a user
>> deletes the qpid config files after installing the features, and we
>> still want the server to be started then we should have default
>> configs.
>>
>> --Pradeep
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Manjula Rathnayaka
Software Engineer
WSO2, Inc.
Mobile:+94 77 743 1987
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Pradeep Fernando]

hi,

On Fri, Apr 1, 2011 at 12:21 PM, Dimuthu Leelarathne  wrote:
> Hi,
>
> On Fri, Apr 1, 2011 at 11:12 AM, Pradeep Fernando  wrote:
>>
>> +1 agreed with danushka. Adding default configuration is not the
>> solution for what dimuthu has encountered. In this case dimuthu is
>> responsible for making the stratos distribution. Anybody working on
>> wso2 product distribution should know what should be done in order to
>> get the product running. No excuses.
>
> There is something very wrong here. Either technology or the process. Let me
> ask the simple question. How did Qpid config files get copied to all
> products and not services? How come services got second hand treatment?
> AFAIK Qpid config files were added products by someone from Qpid team.
>
> So lets speculate,
>
> 1) Should someone from Stratos team do it?
> 2) Should the feature be developed as self contained?
> 3) Should technology be developed to handle this situation? Automatic
> copying of config files?
> 3) Should the RM of each product check the service? At minimum check whether
> it starts?
>
> Copying something to 13 products is not an easy task if you want to build
> them all check whether anything breaks (speaking by experience because I
> have done it). If someone told me adding Qpid config files was my
> responsibility I would create time to do it. I fixed it for manager. I
> wasn't even aware of it until each server started hanging - one after other.


the person making the changes should make sure that other things are
not get broken due to that. simple. When there are changes in carbon
core we used to change all products + stratos services bin.xml, etc
files. :)

so the initial change should be done by Danushka. after that when
somebody adds the feature that contains the qpid in to their product
he/she should handle that.

--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Dimuthu Leelarathne]

Hi

On Fri, Apr 1, 2011 at 10:47 AM, Danushka Menikkumbura wrote:

> But I think we have a fundamental issue in the way we build products. We
> manually copy stuff (mostly configuration files) from the generated carbon
> distribution to the product pack we build. As I learned from Pradeep the
> generated carbon distribution contains all that should go into the product.
>
>
+1

thanks,
dimuthu



> Thanks,
> Danushka
>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Dimuthu Leelarathne]

Hi,

On Fri, Apr 1, 2011 at 11:12 AM, Pradeep Fernando  wrote:

> +1 agreed with danushka. Adding default configuration is not the
> solution for what dimuthu has encountered. In this case dimuthu is
> responsible for making the stratos distribution. Anybody working on
> wso2 product distribution should know what should be done in order to
> get the product running. No excuses.



There is something very wrong here. Either technology or the process. Let me
ask the simple question. How did Qpid config files get copied to all
products and not services? How come services got second hand treatment?
AFAIK Qpid config files were added products by someone from Qpid team.

So lets speculate,

1) Should someone from Stratos team do it?
2) Should the feature be developed as self contained?
3) Should technology be developed to handle this situation? Automatic
copying of config files?
3) Should the RM of each product check the service? At minimum check whether
it starts?

Copying something to 13 products is not an easy task if you want to build
them all check whether anything breaks (speaking by experience because I
have done it). If someone told me adding Qpid config files was my
responsibility I would create time to do it. I fixed it for manager. I
wasn't even aware of it until each server started hanging - one after other.



> If we rely on default configs, then wso2 products will go in to
> production with default configs in the future. (by mistake)
>
>
-1. What about the config files we already ship? Don't they have default
configs?

thanks,
dimuthu


But having a default config will serve a different scenario. If a user
> deletes the qpid config files after installing the features, and we
> still want the server to be started then we should have default
> configs.
>
> --Pradeep
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Pradeep Fernando]

On Fri, Apr 1, 2011 at 10:47 AM, Danushka Menikkumbura
 wrote:
>> a) it is your responsibility!
>> b) we have to fix this. Installing means adding the component, nothing
>> else.
>
> OK. Let me give you an example.
>
> If you use an installer that comes with a piece of software to install it,
> you do not have to worry about copying libraries or configuration files,
> adding registry entries, etc as it takes care of all that. But if you are
> smart enough you can go do all that yourself but you are responsible for
> mistakes made in any of those steps.
>
> Similarly in Carbon, if you get the feature manager to install a feature, it
> takes care of all that. If you happened to do it yourself you should do what
> it takes without making any mistakes.
+1 agreed with danushka. Adding default configuration is not the
solution for what dimuthu has encountered. In this case dimuthu is
responsible for making the stratos distribution. Anybody working on
wso2 product distribution should know what should be done in order to
get the product running. No excuses.
If we rely on default configs, then wso2 products will go in to
production with default configs in the future. (by mistake)

But having a default config will serve a different scenario. If a user
deletes the qpid config files after installing the features, and we
still want the server to be started then we should have default
configs.

--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Danushka Menikkumbura]

>
> a) it is your responsibility!
> b) we have to fix this. Installing means adding the component, nothing
> else.
>

OK. Let me give you an example.

If you use an installer that comes with a piece of software to install it,
you do not have to worry about copying libraries or configuration files,
adding registry entries, etc as it takes care of all that. But if you are
smart enough you can go do all that yourself but you are responsible for
mistakes made in any of those steps.

Similarly in Carbon, if you get the feature manager to install a feature, it
takes care of all that. If you happened to do it yourself you should do what
it takes without making any mistakes. In fact in this particular case, it
had nothing to do with configuration files but the latest qpid libraries
were not used.

I can continued to argue on this but it will not help anybody whatsoever. So
if everybody thinks embedding configuration files is the way to go then I
will look into it.

But I think we have a fundamental issue in the way we build products. We
manually copy stuff (mostly configuration files) from the generated carbon
distribution to the product pack we build. As I learned from Pradeep the
generated carbon distribution contains all that should go into the product.

Thanks,
Danushka
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Afkham Azeez]

On Thu, Mar 31, 2011 at 11:58 AM, Paul Fremantle  wrote:

> Is there a way to hard-code defaults that the code uses when it can't find
> the conf files? I know a lot of systems do that (even Axis2 if I remember
> correctly). We could print a line to INFO log saying we are using built in
> defaults.


Yes, axis2 does not even require an axis2.xml. It has a built in
axis2_default.xml.


>
> Paul
>
>
> On 31 March 2011 07:25, Pradeep Fernando  wrote:
>
>> hi,
>>
>> it is working fine when it is installed as a feature. (they copu the
>> conf files using p2.inf). feature manager and the feature installation
>> during the product building uses the same strategy.
>>
>> --Pradeep
>>
>
>
>
> --
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>
> Office: +44 844 484 8143
> Cell: +44 798 447 4618
>
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> p...@wso2.com
>
> wso2.com Lean Enterprise Middleware
>
> Disclaimer: This communication may contain privileged or other confidential
> information and is intended exclusively for the addressee/s. If you are not
> the intended recipient/s, or believe that you may have received this
> communication in error, please reply to the sender indicating that fact and
> delete the copy you received and in addition, you should not print, copy,
> retransmit, disseminate, or otherwise use the information contained in this
> communication. Internet communications cannot be guaranteed to be timely,
> secure, error or virus-free. The sender does not accept liability for any
> errors or omissions.
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
*Afkham Azeez*
Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
*
*
*Member; Apache Software Foundation;
**http://www.apache.org/*
*
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Sameera Jayasoma]

On Thu, Mar 31, 2011 at 11:58 AM, Paul Fremantle  wrote:

> Is there a way to hard-code defaults that the code uses when it can't find
> the conf files? I know a lot of systems do that (even Axis2 if I remember
> correctly). We could print a line to INFO log saying we are using built in
> defaults.


Yes. We can pack the default configuration files inside qpid bundles. If
there are not external config files, code can use the embeded ones.

Thanks
Sameera

>
> Paul
>
>
> On 31 March 2011 07:25, Pradeep Fernando  wrote:
>
>> hi,
>>
>> it is working fine when it is installed as a feature. (they copu the
>> conf files using p2.inf). feature manager and the feature installation
>> during the product building uses the same strategy.
>>
>> --Pradeep
>>
>
>
>
> --
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>
> Office: +44 844 484 8143
> Cell: +44 798 447 4618
>
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> p...@wso2.com
>
> wso2.com Lean Enterprise Middleware
>
> Disclaimer: This communication may contain privileged or other confidential
> information and is intended exclusively for the addressee/s. If you are not
> the intended recipient/s, or believe that you may have received this
> communication in error, please reply to the sender indicating that fact and
> delete the copy you received and in addition, you should not print, copy,
> retransmit, disseminate, or otherwise use the information contained in this
> communication. Internet communications cannot be guaranteed to be timely,
> secure, error or virus-free. The sender does not accept liability for any
> errors or omissions.
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

Lean . Enterprise . Middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Paul Fremantle]

Is there a way to hard-code defaults that the code uses when it can't find
the conf files? I know a lot of systems do that (even Axis2 if I remember
correctly). We could print a line to INFO log saying we are using built in
defaults.

Paul

On 31 March 2011 07:25, Pradeep Fernando  wrote:

> hi,
>
> it is working fine when it is installed as a feature. (they copu the
> conf files using p2.inf). feature manager and the feature installation
> during the product building uses the same strategy.
>
> --Pradeep
>



-- 
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair, VP, Apache Synapse

Office: +44 844 484 8143
Cell: +44 798 447 4618

blog: http://pzf.fremantle.org
twitter.com/pzfreo
p...@wso2.com

wso2.com Lean Enterprise Middleware

Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Pradeep Fernando]

hi,

it is working fine when it is installed as a feature. (they copu the
conf files using p2.inf). feature manager and the feature installation
during the product building uses the same strategy.

--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Paul Fremantle]

Has anyone tested adding Qpid using p2 as a feature into a product that
doesn't have it? Does that work?

Paul

On 31 March 2011 06:59, Tharindu Mathew  wrote:

> I updated bam and built and I believe this is fixed now. All qpid configs
> are in place, so we are good.
>
> Also, as I showed you in my earlier mail, even if qpid can't find the
> configs the server does not fail, which is the proper thing that should
> happen.
>
> It would be good if everyone else also see if they can build and up the
> products without any qpid issue.
>
>
> On Thu, Mar 31, 2011 at 11:25 AM, Srinath Perera  wrote:
>
>> Danushka, to our carbon story to hold we have to be able to compose
>> components. That means defaults should be right, and Qpid  MUST work
>> out of the box (whether it is added) directly, through eventing, or
>> indirectly by something else.
>>
>> So
>>
>> a) it is your responsibility!
>> b) we have to fix this. Installing means adding the component, nothing
>> else.
>>
>> --Srinath
>>
>>
>>
>>
>>
>>
>>
>> On Wed, Mar 30, 2011 at 11:46 PM, Danushka Menikkumbura
>>  wrote:
>> > The event team has repeatedly pointed out that qpid gets installed as a
>> > result of installing event. No product does use qpid alone as far as I
>> know.
>> > Even in that case it is your responsibility to install what you need.
>> Also
>> > you guys not reading mails is your problem. I do not want to pay the
>> price
>> > for all that.
>> >
>> > Yes. This is indeed frustrating!
>> >
>> > Danushka
>> >
>> > On Wed, Mar 30, 2011 at 10:43 PM, Afkham Azeez  wrote:
>> >>
>> >> Danushka or whoever is responsible for creating these issues, please
>> fix
>> >> this asap. We don't want to see this tomorrow morning !
>> >>
>> >> On Mar 30, 2011 10:39 PM, "Dimuthu Leelarathne" 
>> wrote:
>> >> > Hi,
>> >> >
>> >> > I am having a really hard time coping with Qpid instability. I did an
>> >> > svn up
>> >> > yesterday and build everything. Since BAM didn't start up, I did an
>> svn
>> >> > up
>> >> > of all Qpid related artifacts and build them again.
>> >> >
>> >> > But still BAM doesn't start up because of Qpid config files !
>> >> > &#$%$^%^&%$#%
>> >> >
>> >> > Here are the the qpid related I build again.
>> >> >
>> >> > dependencies/qpid
>> >> > orbit/qpid
>> >> > orbit/qpid-client
>> >> > components/qpid
>> >> > features/qpid
>> >> >
>> >> > And finallly BAM. I cannot commit my GApp feature or test it with any
>> >> > product because of this.
>> >> >
>> >> > Here is the error I get.
>> >> >
>> >> > [2011-03-30 22:34:09,293] ERROR
>> >> > {org.wso2.carbon.qpid.service.QpidServiceImpl} -
>> >> >
>> >> >
>> /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/config.xml
>> >> > not found
>> >> > Initialisation Error : File
>> >> >
>> >> >
>> /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/etc/config.xml
>> >> > could not be found. Check the file exists and is readable.
>> >> >
>> >> > Please help.
>> >> >
>> >> > tx,
>> >> > dimuthu
>> >>
>> >> ___
>> >> Carbon-dev mailing list
>> >> Carbon-dev@wso2.org
>> >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >>
>> >
>> >
>> > ___
>> > Carbon-dev mailing list
>> > Carbon-dev@wso2.org
>> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>> >
>>
>>
>>
>> --
>> 
>> Srinath Perera, Ph.D.
>>http://www.cs.indiana.edu/~hperera/
>>http://srinathsview.blogspot.com/
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
>
> --
> Regards,
>
> Tharindu
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair, VP, Apache Synapse

Office: +44 844 484 8143
Cell: +44 798 447 4618

blog: http://pzf.fremantle.org
twitter.com/pzfreo
p...@wso2.com

wso2.com Lean Enterprise Middleware

Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/

Re: [Carbon-dev] Qpid Frustration

[Tharindu Mathew]

I updated bam and built and I believe this is fixed now. All qpid configs
are in place, so we are good.

Also, as I showed you in my earlier mail, even if qpid can't find the
configs the server does not fail, which is the proper thing that should
happen.

It would be good if everyone else also see if they can build and up the
products without any qpid issue.

On Thu, Mar 31, 2011 at 11:25 AM, Srinath Perera  wrote:

> Danushka, to our carbon story to hold we have to be able to compose
> components. That means defaults should be right, and Qpid  MUST work
> out of the box (whether it is added) directly, through eventing, or
> indirectly by something else.
>
> So
>
> a) it is your responsibility!
> b) we have to fix this. Installing means adding the component, nothing
> else.
>
> --Srinath
>
>
>
>
>
>
>
> On Wed, Mar 30, 2011 at 11:46 PM, Danushka Menikkumbura
>  wrote:
> > The event team has repeatedly pointed out that qpid gets installed as a
> > result of installing event. No product does use qpid alone as far as I
> know.
> > Even in that case it is your responsibility to install what you need.
> Also
> > you guys not reading mails is your problem. I do not want to pay the
> price
> > for all that.
> >
> > Yes. This is indeed frustrating!
> >
> > Danushka
> >
> > On Wed, Mar 30, 2011 at 10:43 PM, Afkham Azeez  wrote:
> >>
> >> Danushka or whoever is responsible for creating these issues, please fix
> >> this asap. We don't want to see this tomorrow morning !
> >>
> >> On Mar 30, 2011 10:39 PM, "Dimuthu Leelarathne" 
> wrote:
> >> > Hi,
> >> >
> >> > I am having a really hard time coping with Qpid instability. I did an
> >> > svn up
> >> > yesterday and build everything. Since BAM didn't start up, I did an
> svn
> >> > up
> >> > of all Qpid related artifacts and build them again.
> >> >
> >> > But still BAM doesn't start up because of Qpid config files !
> >> > &#$%$^%^&%$#%
> >> >
> >> > Here are the the qpid related I build again.
> >> >
> >> > dependencies/qpid
> >> > orbit/qpid
> >> > orbit/qpid-client
> >> > components/qpid
> >> > features/qpid
> >> >
> >> > And finallly BAM. I cannot commit my GApp feature or test it with any
> >> > product because of this.
> >> >
> >> > Here is the error I get.
> >> >
> >> > [2011-03-30 22:34:09,293] ERROR
> >> > {org.wso2.carbon.qpid.service.QpidServiceImpl} -
> >> >
> >> >
> /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/config.xml
> >> > not found
> >> > Initialisation Error : File
> >> >
> >> >
> /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/etc/config.xml
> >> > could not be found. Check the file exists and is readable.
> >> >
> >> > Please help.
> >> >
> >> > tx,
> >> > dimuthu
> >>
> >> ___
> >> Carbon-dev mailing list
> >> Carbon-dev@wso2.org
> >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>
> >
> >
> > ___
> > Carbon-dev mailing list
> > Carbon-dev@wso2.org
> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
>
>
>
> --
> 
> Srinath Perera, Ph.D.
>http://www.cs.indiana.edu/~hperera/
>http://srinathsview.blogspot.com/
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
Regards,

Tharindu
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Srinath Perera]

Danushka, to our carbon story to hold we have to be able to compose
components. That means defaults should be right, and Qpid  MUST work
out of the box (whether it is added) directly, through eventing, or
indirectly by something else.

So

a) it is your responsibility!
b) we have to fix this. Installing means adding the component, nothing else.

--Srinath







On Wed, Mar 30, 2011 at 11:46 PM, Danushka Menikkumbura
 wrote:
> The event team has repeatedly pointed out that qpid gets installed as a
> result of installing event. No product does use qpid alone as far as I know.
> Even in that case it is your responsibility to install what you need. Also
> you guys not reading mails is your problem. I do not want to pay the price
> for all that.
>
> Yes. This is indeed frustrating!
>
> Danushka
>
> On Wed, Mar 30, 2011 at 10:43 PM, Afkham Azeez  wrote:
>>
>> Danushka or whoever is responsible for creating these issues, please fix
>> this asap. We don't want to see this tomorrow morning !
>>
>> On Mar 30, 2011 10:39 PM, "Dimuthu Leelarathne"  wrote:
>> > Hi,
>> >
>> > I am having a really hard time coping with Qpid instability. I did an
>> > svn up
>> > yesterday and build everything. Since BAM didn't start up, I did an svn
>> > up
>> > of all Qpid related artifacts and build them again.
>> >
>> > But still BAM doesn't start up because of Qpid config files !
>> > &#$%$^%^&%$#%
>> >
>> > Here are the the qpid related I build again.
>> >
>> > dependencies/qpid
>> > orbit/qpid
>> > orbit/qpid-client
>> > components/qpid
>> > features/qpid
>> >
>> > And finallly BAM. I cannot commit my GApp feature or test it with any
>> > product because of this.
>> >
>> > Here is the error I get.
>> >
>> > [2011-03-30 22:34:09,293] ERROR
>> > {org.wso2.carbon.qpid.service.QpidServiceImpl} -
>> >
>> > /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/config.xml
>> > not found
>> > Initialisation Error : File
>> >
>> > /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/etc/config.xml
>> > could not be found. Check the file exists and is readable.
>> >
>> > Please help.
>> >
>> > tx,
>> > dimuthu
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>



-- 

Srinath Perera, Ph.D.
   http://www.cs.indiana.edu/~hperera/
   http://srinathsview.blogspot.com/
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Samisa Abeysinghe]

On Thu, Mar 31, 2011 at 6:52 AM, Danushka Menikkumbura wrote:

> Hi Samisa,
>
> I hope your meant self-containing configuration files. I tried that but
> failed as the root configuration file uses two other files in it which are
> compiled by the configuration builder when the configuration context is
> built.
>
> This was fixed across products. The issue was not building the event
> feature. When you build the event feature only it copes qpid configuration
> files into the product.
>

I hope people are building with product profiles? Was it not built when
building with product profiles.


>
> Thanks,
> Danushka
>
>
> On Thu, Mar 31, 2011 at 4:28 AM, Samisa Abeysinghe wrote:
>
>>
>>
>> On Wed, Mar 30, 2011 at 11:46 PM, Danushka Menikkumbura <
>> danus...@wso2.com> wrote:
>>
>>> The event team has repeatedly pointed out that qpid gets installed as a
>>> result of installing event. No product does use qpid alone as far as I know.
>>> Even in that case it is your responsibility to install what you need. Also
>>> you guys not reading mails is your problem. I do not want to pay the price
>>> for all that.
>>>
>>
>> That is not the point. The point is, the defaults expected by the whole
>> things is busted. Either you have to make it self contained, or fix
>> it across products if you are chaining the behavior.
>>
>>>
>>> Yes. This is indeed frustrating!
>>>
>>> Danushka
>>>
>>> On Wed, Mar 30, 2011 at 10:43 PM, Afkham Azeez  wrote:
>>>
 Danushka or whoever is responsible for creating these issues, please fix
 this asap. We don't want to see this tomorrow morning !
  On Mar 30, 2011 10:39 PM, "Dimuthu Leelarathne" 
 wrote:
 > Hi,
 >
 > I am having a really hard time coping with Qpid instability. I did an
 svn up
 > yesterday and build everything. Since BAM didn't start up, I did an
 svn up
 > of all Qpid related artifacts and build them again.
 >
 > But still BAM doesn't start up because of Qpid config files !
 > &#$%$^%^&%$#%
 >
 > Here are the the qpid related I build again.
 >
 > dependencies/qpid
 > orbit/qpid
 > orbit/qpid-client
 > components/qpid
 > features/qpid
 >
 > And finallly BAM. I cannot commit my GApp feature or test it with any
 > product because of this.
 >
 > Here is the error I get.
 >
 > [2011-03-30 22:34:09,293] ERROR
 > {org.wso2.carbon.qpid.service.QpidServiceImpl} -
 >
 /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/config.xml
 > not found
 > Initialisation Error : File
 >
 /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/etc/config.xml
 > could not be found. Check the file exists and is readable.
 >
 > Please help.
 >
 > tx,
 > dimuthu

 ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev


>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>> Thanks,
>> Samisa...
>>
>> Samisa Abeysinghe
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>>
>>
>>
>>
> Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Danushka Menikkumbura]

> copes qpid configuration files into the product.
>

I meant to say qpid libs.

Thanks,
Danushka
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Danushka Menikkumbura]

Hi Samisa,

I hope your meant self-containing configuration files. I tried that but
failed as the root configuration file uses two other files in it which are
compiled by the configuration builder when the configuration context is
built.

This was fixed across products. The issue was not building the event
feature. When you build the event feature only it copes qpid configuration
files into the product.

Thanks,
Danushka

On Thu, Mar 31, 2011 at 4:28 AM, Samisa Abeysinghe  wrote:

>
>
> On Wed, Mar 30, 2011 at 11:46 PM, Danushka Menikkumbura  > wrote:
>
>> The event team has repeatedly pointed out that qpid gets installed as a
>> result of installing event. No product does use qpid alone as far as I know.
>> Even in that case it is your responsibility to install what you need. Also
>> you guys not reading mails is your problem. I do not want to pay the price
>> for all that.
>>
>
> That is not the point. The point is, the defaults expected by the whole
> things is busted. Either you have to make it self contained, or fix
> it across products if you are chaining the behavior.
>
>>
>> Yes. This is indeed frustrating!
>>
>> Danushka
>>
>> On Wed, Mar 30, 2011 at 10:43 PM, Afkham Azeez  wrote:
>>
>>> Danushka or whoever is responsible for creating these issues, please fix
>>> this asap. We don't want to see this tomorrow morning !
>>>  On Mar 30, 2011 10:39 PM, "Dimuthu Leelarathne" 
>>> wrote:
>>> > Hi,
>>> >
>>> > I am having a really hard time coping with Qpid instability. I did an
>>> svn up
>>> > yesterday and build everything. Since BAM didn't start up, I did an svn
>>> up
>>> > of all Qpid related artifacts and build them again.
>>> >
>>> > But still BAM doesn't start up because of Qpid config files !
>>> > &#$%$^%^&%$#%
>>> >
>>> > Here are the the qpid related I build again.
>>> >
>>> > dependencies/qpid
>>> > orbit/qpid
>>> > orbit/qpid-client
>>> > components/qpid
>>> > features/qpid
>>> >
>>> > And finallly BAM. I cannot commit my GApp feature or test it with any
>>> > product because of this.
>>> >
>>> > Here is the error I get.
>>> >
>>> > [2011-03-30 22:34:09,293] ERROR
>>> > {org.wso2.carbon.qpid.service.QpidServiceImpl} -
>>> >
>>> /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/config.xml
>>> > not found
>>> > Initialisation Error : File
>>> >
>>> /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/etc/config.xml
>>> > could not be found. Check the file exists and is readable.
>>> >
>>> > Please help.
>>> >
>>> > tx,
>>> > dimuthu
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Samisa Abeysinghe]

On Wed, Mar 30, 2011 at 11:46 PM, Danushka Menikkumbura
wrote:

> The event team has repeatedly pointed out that qpid gets installed as a
> result of installing event. No product does use qpid alone as far as I know.
> Even in that case it is your responsibility to install what you need. Also
> you guys not reading mails is your problem. I do not want to pay the price
> for all that.
>

That is not the point. The point is, the defaults expected by the whole
things is busted. Either you have to make it self contained, or fix
it across products if you are chaining the behavior.

>
> Yes. This is indeed frustrating!
>
> Danushka
>
> On Wed, Mar 30, 2011 at 10:43 PM, Afkham Azeez  wrote:
>
>> Danushka or whoever is responsible for creating these issues, please fix
>> this asap. We don't want to see this tomorrow morning !
>>  On Mar 30, 2011 10:39 PM, "Dimuthu Leelarathne" 
>> wrote:
>> > Hi,
>> >
>> > I am having a really hard time coping with Qpid instability. I did an
>> svn up
>> > yesterday and build everything. Since BAM didn't start up, I did an svn
>> up
>> > of all Qpid related artifacts and build them again.
>> >
>> > But still BAM doesn't start up because of Qpid config files !
>> > &#$%$^%^&%$#%
>> >
>> > Here are the the qpid related I build again.
>> >
>> > dependencies/qpid
>> > orbit/qpid
>> > orbit/qpid-client
>> > components/qpid
>> > features/qpid
>> >
>> > And finallly BAM. I cannot commit my GApp feature or test it with any
>> > product because of this.
>> >
>> > Here is the error I get.
>> >
>> > [2011-03-30 22:34:09,293] ERROR
>> > {org.wso2.carbon.qpid.service.QpidServiceImpl} -
>> >
>> /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/config.xml
>> > not found
>> > Initialisation Error : File
>> >
>> /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/etc/config.xml
>> > could not be found. Check the file exists and is readable.
>> >
>> > Please help.
>> >
>> > tx,
>> > dimuthu
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
> Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Dimuthu Leelarathne]

Hi,

On Wed, Mar 30, 2011 at 11:46 PM, Danushka Menikkumbura
wrote:

> The event team has repeatedly pointed out that qpid gets installed as a
> result of installing event. No product does use qpid alone as far as I know.
> Even in that case it is your responsibility to install what you need. Also
> you guys not reading mails is your problem. I do not want to pay the price
> for all that.
>
>
Today (at this moment) after a long time I was able to get the Stratos
services up and running. Since Carbon still can't copy the configuration
files with the feature at build time (I think people call it advanced
folder), I think best thing should have been to just let the server start if
these files are not present, just as it happens now.

Thanks a lot for fixing it.

Dimuthu



> Yes. This is indeed frustrating!
>
> Danushka
>
> On Wed, Mar 30, 2011 at 10:43 PM, Afkham Azeez  wrote:
>
>> Danushka or whoever is responsible for creating these issues, please fix
>> this asap. We don't want to see this tomorrow morning !
>>  On Mar 30, 2011 10:39 PM, "Dimuthu Leelarathne" 
>> wrote:
>> > Hi,
>> >
>> > I am having a really hard time coping with Qpid instability. I did an
>> svn up
>> > yesterday and build everything. Since BAM didn't start up, I did an svn
>> up
>> > of all Qpid related artifacts and build them again.
>> >
>> > But still BAM doesn't start up because of Qpid config files !
>> > &#$%$^%^&%$#%
>> >
>> > Here are the the qpid related I build again.
>> >
>> > dependencies/qpid
>> > orbit/qpid
>> > orbit/qpid-client
>> > components/qpid
>> > features/qpid
>> >
>> > And finallly BAM. I cannot commit my GApp feature or test it with any
>> > product because of this.
>> >
>> > Here is the error I get.
>> >
>> > [2011-03-30 22:34:09,293] ERROR
>> > {org.wso2.carbon.qpid.service.QpidServiceImpl} -
>> >
>> /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/config.xml
>> > not found
>> > Initialisation Error : File
>> >
>> /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/etc/config.xml
>> > could not be found. Check the file exists and is readable.
>> >
>> > Please help.
>> >
>> > tx,
>> > dimuthu
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Danushka Menikkumbura]

The event team has repeatedly pointed out that qpid gets installed as a
result of installing event. No product does use qpid alone as far as I know.
Even in that case it is your responsibility to install what you need. Also
you guys not reading mails is your problem. I do not want to pay the price
for all that.

Yes. This is indeed frustrating!

Danushka

On Wed, Mar 30, 2011 at 10:43 PM, Afkham Azeez  wrote:

> Danushka or whoever is responsible for creating these issues, please fix
> this asap. We don't want to see this tomorrow morning !
>  On Mar 30, 2011 10:39 PM, "Dimuthu Leelarathne" 
> wrote:
> > Hi,
> >
> > I am having a really hard time coping with Qpid instability. I did an svn
> up
> > yesterday and build everything. Since BAM didn't start up, I did an svn
> up
> > of all Qpid related artifacts and build them again.
> >
> > But still BAM doesn't start up because of Qpid config files !
> > &#$%$^%^&%$#%
> >
> > Here are the the qpid related I build again.
> >
> > dependencies/qpid
> > orbit/qpid
> > orbit/qpid-client
> > components/qpid
> > features/qpid
> >
> > And finallly BAM. I cannot commit my GApp feature or test it with any
> > product because of this.
> >
> > Here is the error I get.
> >
> > [2011-03-30 22:34:09,293] ERROR
> > {org.wso2.carbon.qpid.service.QpidServiceImpl} -
> >
> /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/config.xml
> > not found
> > Initialisation Error : File
> >
> /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/etc/config.xml
> > could not be found. Check the file exists and is readable.
> >
> > Please help.
> >
> > tx,
> > dimuthu
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Dimuthu Leelarathne]

Hi,

As Manjula pointed out (offline) I had to build "features/event" as well.
Now the server starts.

tx,
dimuthu

On Wed, Mar 30, 2011 at 10:46 PM, Tharindu Mathew  wrote:

> Even though qpid files are not present BAM starts up.
>
> [2011-03-30 22:44:47,554]  INFO
> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -  HTTPS
> port   : 9443
> [2011-03-30 22:44:47,555]  INFO
> {org.wso2.carbon.core.transports.http.HttpTransportListener} -  HTTP
> port: 9763
> [2011-03-30 22:44:47,631] ERROR
> {org.wso2.carbon.qpid.service.QpidServiceImpl} -
> /home/mackie/source-checkouts/carbon/products/bam/modules/distribution/product/target/wso2bam-1.3.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
> not found
> [2011-03-30 22:44:47,647] ERROR
> {org.wso2.carbon.qpid.internal.QpidServiceComponent} -  Failed to start Qpid
> broker : File
> /home/mackie/source-checkouts/carbon/products/bam/modules/distribution/product/target/wso2bam-1.3.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
> could not be found. Check the file exists and is readable.
> [2011-03-30 22:44:51,210]  INFO
> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console URL  :
> https://192.168.1.38:9443/carbon/
> [2011-03-30 22:44:51,241]  INFO
> {org.wso2.carbon.event.core.internal.builder.EventBrokerBuilderDS} -
> Successfully registered the event broker
> [2011-03-30 22:44:51,257]  INFO
> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  Started
> Transport Listener Manager
> [2011-03-30 22:44:51,258]  INFO
> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
> Server   :  WSO2 Business Activity Monitor-1.3.0-SNAPSHOT
> [2011-03-30 22:44:51,258]  INFO
> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  WSO2
> Carbon started in 45 sec
>
>
> On Wed, Mar 30, 2011 at 10:38 PM, Dimuthu Leelarathne 
> wrote:
>
>> Hi,
>>
>> I am having a really hard time coping with Qpid instability. I did an svn
>> up yesterday and build everything. Since BAM didn't start up, I did an svn
>> up of all Qpid related artifacts and build them again.
>>
>> But still BAM doesn't start up because of Qpid config files !
>> &#$%$^%^&%$#%
>>
>> Here are the the qpid related I build again.
>>
>> dependencies/qpid
>> orbit/qpid
>> orbit/qpid-client
>> components/qpid
>> features/qpid
>>
>> And finallly BAM. I cannot commit my GApp feature or test it with any
>> product because of this.
>>
>> Here is the error I get.
>>
>> [2011-03-30 22:34:09,293] ERROR
>> {org.wso2.carbon.qpid.service.QpidServiceImpl} -
>> /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/config.xml
>> not found
>> Initialisation Error : File
>> /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/etc/config.xml
>> could not be found. Check the file exists and is readable.
>>
>> Please help.
>>
>> tx,
>> dimuthu
>>
>>
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Regards,
>
> Tharindu
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Tharindu Mathew]

Even though qpid files are not present BAM starts up.

[2011-03-30 22:44:47,554]  INFO
{org.wso2.carbon.core.transports.http.HttpsTransportListener} -  HTTPS
port   : 9443
[2011-03-30 22:44:47,555]  INFO
{org.wso2.carbon.core.transports.http.HttpTransportListener} -  HTTP
port: 9763
[2011-03-30 22:44:47,631] ERROR
{org.wso2.carbon.qpid.service.QpidServiceImpl} -
/home/mackie/source-checkouts/carbon/products/bam/modules/distribution/product/target/wso2bam-1.3.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
not found
[2011-03-30 22:44:47,647] ERROR
{org.wso2.carbon.qpid.internal.QpidServiceComponent} -  Failed to start Qpid
broker : File
/home/mackie/source-checkouts/carbon/products/bam/modules/distribution/product/target/wso2bam-1.3.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
could not be found. Check the file exists and is readable.
[2011-03-30 22:44:51,210]  INFO
{org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console URL  :
https://192.168.1.38:9443/carbon/
[2011-03-30 22:44:51,241]  INFO
{org.wso2.carbon.event.core.internal.builder.EventBrokerBuilderDS} -
Successfully registered the event broker
[2011-03-30 22:44:51,257]  INFO
{org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  Started
Transport Listener Manager
[2011-03-30 22:44:51,258]  INFO
{org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
Server   :  WSO2 Business Activity Monitor-1.3.0-SNAPSHOT
[2011-03-30 22:44:51,258]  INFO
{org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  WSO2
Carbon started in 45 sec


On Wed, Mar 30, 2011 at 10:38 PM, Dimuthu Leelarathne wrote:

> Hi,
>
> I am having a really hard time coping with Qpid instability. I did an svn
> up yesterday and build everything. Since BAM didn't start up, I did an svn
> up of all Qpid related artifacts and build them again.
>
> But still BAM doesn't start up because of Qpid config files !
> &#$%$^%^&%$#%
>
> Here are the the qpid related I build again.
>
> dependencies/qpid
> orbit/qpid
> orbit/qpid-client
> components/qpid
> features/qpid
>
> And finallly BAM. I cannot commit my GApp feature or test it with any
> product because of this.
>
> Here is the error I get.
>
> [2011-03-30 22:34:09,293] ERROR
> {org.wso2.carbon.qpid.service.QpidServiceImpl} -
> /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/config.xml
> not found
> Initialisation Error : File
> /home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/etc/config.xml
> could not be found. Check the file exists and is readable.
>
> Please help.
>
> tx,
> dimuthu
>
>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Regards,

Tharindu
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Frustration

[Afkham Azeez]

Danushka or whoever is responsible for creating these issues, please fix
this asap. We don't want to see this tomorrow morning !
On Mar 30, 2011 10:39 PM, "Dimuthu Leelarathne"  wrote:
> Hi,
>
> I am having a really hard time coping with Qpid instability. I did an svn
up
> yesterday and build everything. Since BAM didn't start up, I did an svn up
> of all Qpid related artifacts and build them again.
>
> But still BAM doesn't start up because of Qpid config files !
> &#$%$^%^&%$#%
>
> Here are the the qpid related I build again.
>
> dependencies/qpid
> orbit/qpid
> orbit/qpid-client
> components/qpid
> features/qpid
>
> And finallly BAM. I cannot commit my GApp feature or test it with any
> product because of this.
>
> Here is the error I get.
>
> [2011-03-30 22:34:09,293] ERROR
> {org.wso2.carbon.qpid.service.QpidServiceImpl} -
>
/home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/config.xml
> not found
> Initialisation Error : File
>
/home/muthulee/work/tcarbon-platform/products/bam/modules/distribution/service/target/wso2stratos-bam-1.1.0-SNAPSHOT/repository/conf/qpid/etc/config.xml
> could not be found. Check the file exists and is readable.
>
> Please help.
>
> tx,
> dimuthu
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev