[Carbon-dev] Source code links broken on OT

[Danushka Menikkumbura]

Hi,

Just wanted to find out the link for app server source code.

I do not see a link for source code on product home page (i.e.
http://wso2.com/products/application-server/)
I get a 404 for the link (
https://svn.wso2.org/repos/wso2/trunk/carbon/products/appserver) on
http://wso2.org/library/application-server
The link on the Projects tab directs me to some other page.

Please take a look.

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

Re: [Carbon-dev] [Bamboo-Build] Carbon-Kernel > Carbon-Kernel > #11 was SUCCESSFUL (with 2733 tests). Change made by kishanthan and pradeep.

[Danushka Menikkumbura]

I thought Bamboo had a dashboard (and could send notifications out?). Maybe
you can have it on a widescreen at the lounge so that everybody sees how
the builder is doing? ;-)

On Thu, Feb 16, 2012 at 10:13 AM, Afkham Azeez  wrote:

>
>
> On Thu, Feb 16, 2012 at 10:07 AM, Shammi Jayasinghe wrote:
>
>> Hi,
>>
>>  Configured the notifications to : Failed Builds And First Successful
>> State.
>>
>
> I don't think this is a good thing. How would we know that the Bamboo
> process is still running? In the past we have experienced Bamboo itself not
> running, and we realized this because we didn't get Build Successful mails
> over a few days.
>
>
>> Thanks
>> Shammi
>>
>> Ta
>>
>> On Thu, Feb 16, 2012 at 9:44 AM, Shelan Perera  wrote:
>>
>>>
>>>
>>> On Thu, Feb 16, 2012 at 9:07 AM, Sameera Jayasoma wrote:
>>>


 On Thu, Feb 16, 2012 at 8:33 AM, Shelan Perera  wrote:

> Hi,
>
> On Thu, Feb 16, 2012 at 7:35 AM, Samisa Abeysinghe wrote:
>
>> Would it be a good idea to NOT send the mail if it was successful?
>>
>
> Sometimes we are confident to take a SVN update if we see a successful
> message from the build. Otherwise there may not be a clue to track whether
> a broken build is
> fixed or not.
>

 Bottom line is until you see the build failure email, trunk is stable.
 So you can safely update and build.  Following should be the algorithm :)

 function notifyBuildStatus(curStatus, prevStatus) {

 if( curStatus == "Failed" ) {
  notifyBuildFailure();

  } else if( curStatus == "Successful" && prevStatus == "Failed" )
 notifyBuildSuccess();

 }
 }

>>>
>>> +1 . We need at least one success notification after a build failure.
>>>



> Thank
>
>>
>> On Wed, Feb 15, 2012 at 6:32 PM, Bamboo  wrote:
>>
>>>  [image: Successful]  
>>> Carbon-Kernel›
>>> Carbon-Kernel›
>>> #11
>>>  was
>>> successful
>>>
>>> Code has been updated by 
>>> kishanthan,
>>> pradeep
>>> .
>>>
>>> *2733* tests in total.
>>>Code 
>>> Changes
>>>   View
>>> full change 
>>> details
>>> kishanthan
>>> moving jboss-transaction jar to endorsed as the packages are
>>> provided by the jvm and removing lib/api from bin.xml  120809
>>> pradeep
>>> remvoing some more jars from lib/api  120802
>>> pradeep
>>> removing caching core, securevault from lib/api  120801 View
>>> Online
>>> | Add 
>>> Comments
>>>
>>> This message was sent by Atlassian 
>>> Bamboo
>>> .
>>>
>>> If you wish to stop receiving these emails edit your user 
>>> profileor
>>>  notify
>>> your 
>>> administrator
>>> .
>>>
>>> ___
>>> 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
>>
>>
>
>
> --
> *Shelan Perera*
>
> Software Engineer
> **
> *WSO2, Inc. : wso2.com*
> lean.enterprise.middleware.
>
> *Home Page*  :shelan.org
> *Blog* : blog.shelan.org
> *Linked-i*n  :http://www.linkedin.com/pub/shelan-perera/a/194/465
> *Twitter* :https://twitter.com/#!/shelan
>
> *Mobile*  : +94 772 604 402
>
>
>
> _

Re: [Carbon-dev] [Bamboo-Build] Carbon-Kernel > Carbon-Kernel > #11 was SUCCESSFUL (with 2733 tests). Change made by kishanthan and pradeep.

[Danushka Menikkumbura]

I think the general practice it to send a success mail for the first
successful build after a build break.

On Thu, Feb 16, 2012 at 7:35 AM, Samisa Abeysinghe  wrote:

> Would it be a good idea to NOT send the mail if it was successful?
>
> On Wed, Feb 15, 2012 at 6:32 PM, Bamboo  wrote:
>
>>  [image: Successful]  
>> Carbon-Kernel›
>> Carbon-Kernel›
>> #11
>>  was
>> successful
>>
>> Code has been updated by 
>> kishanthan,
>> pradeep .
>>
>> *2733* tests in total.
>>Code 
>> Changes
>>   View
>> full change 
>> details
>> kishanthan
>> moving jboss-transaction jar to endorsed as the packages are provided by
>> the jvm and removing lib/api from bin.xml  120809
>> pradeep
>> remvoing some more jars from lib/api  120802
>> pradeep
>> removing caching core, securevault from lib/api  120801 View 
>> Online
>> | Add 
>> Comments
>>
>> This message was sent by Atlassian 
>> Bamboo
>> .
>>
>> If you wish to stop receiving these emails edit your user 
>> profileor
>>  notify
>> your 
>> administrator
>> .
>>
>> ___
>> 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
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Enabling Broker component to support all JMS brokers

[Danushka Menikkumbura]

Correct!. In fact we opted for Qpid taking lot of things into consideration
leaving ActiveMQ behind.

Danushka

On Mon, Feb 6, 2012 at 6:24 PM, Paul Fremantle  wrote:

> Suho
>
> What is the use case for this? Users can already use ActiveMQ with the ESB
> and other products via the JMS transport. There was (I think) a lot more
> work involved in adding QPid as a broker including tying into the Identity
> / User Manager as well as support for Multi-tenancy.
>
> Paul
>
> On 6 February 2012 07:04, Suhothayan Sriskandarajah  wrote:
>
>>
>> Currently Broker component only supports Qpid broker and it doesn't have
>> the ability to send messages to other JMS brokers.
>> This is because the provider url used to create the connection is
>> programmatically build using the username, password, ip address, port and
>> virtual machine name.
>>
>> Now I'm is the process of extending Broker's functionality to support
>> ActiveMQ.
>> In this process I can either programmatically build the provider url of
>> the ActiveMQ or I can generalize the process by asking the user to add the
>> provider url itself.
>> In both cases users need to add the relevant broker jars (activemq or
>> other ) to the libs.
>>
>> Here since we are shipping Qpid I thought it will be appropriate for the
>> user to have two UIs, one Qpid specific and the other a general JMS UI
>> which will ask for prover url and JNDI class name.
>>
>> Please give your ideas on this approach
>>
>> Thanks
>> Suho
>>
>>
>> --
>> *S. Suhothayan
>> *
>> Software Engineer
>>  *WSO2, Inc. *http://wso2.com
>> lean.enterprise.middleware.
>>
>> *email: **s...@wso2.com* * cell: (+94) 779 756 757
>> blog: **http://suhothayan.blogspot.com/*
>> *
>> twitter: **http://twitter.com/suhothayan* 
>> *
>> linked-in: **http://lk.linkedin.com/in/suhothayan*
>> *
>> *
>>
>>
>> ___
>> 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
>
> UK: +44 207 096 0336
> US: +1 646 595 7614
>
> 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
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Why committing JARs to SVN repo?

[Danushka Menikkumbura]

You can get rid of most of these jars even though they are just there on
the Qpid trunk. We used to have the minimum set of jars before. Ideally we
should have maven dependency plugin downloading jars from Maven repo into
the lib dir. Please take a look at [1].

[1] -
http://stackoverflow.com/questions/1580562/maven-antrun-and-dependencies

Danushka

On Mon, Jan 30, 2012 at 7:17 AM, Srinath Perera  wrote:

> Wathsala and Charith .. I think answer is we do not need to commit the
> jars .. just we have to fix the builds.
>
> Lets get them removed
>
> On Sun, Jan 29, 2012 at 7:44 PM, Nirmal Fernando  wrote:
> > Hi,
> >
> > Do we really need to commit jar files to SVN? Can't we add them as
> > dependencies in the pom? I've noticed many jars been committed to
> > dependencies. See [1] for few.
> >
> > Thanks.
> >
> > [1]
> > Abroker2/java/lib/org.eclipse.swt_3.4.1.v3449c.jar
> > Abroker2/java/lib/zookeeper-3.4.1.jar
> > A
> broker2/java/lib/org.eclipse.core.contenttype_3.3.0.v20080604-1400.jar
> > Abroker2/java/lib/org.apache.felix.framework-2.0.5.jar
> > Abroker2/java/lib/org.eclipse.jface_3.4.1.M20080827-2000.jar
> > Abroker2/java/lib/guava-r08.jar
> > Abroker2/java/lib/mina-core-1.1.7.jar
> > Abroker2/java/lib/perf4j-0.9.12.wso2v1.jar
> >
> >
> >
> >
> > --
> >
> > regards,
> > Nirmal
> >
> > Software Engineer, WSO2 Inc.
> > mobile: +94715779733
> >
> >
> > ___
> > 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
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Displaying 'Qpid Port' in MB Admin Console

[Danushka Menikkumbura]

I think it should go in to the Configure pane. Also I think you need to
list down other connection-url-related details like vhosts, etc too.

Danushka

On Wed, Jan 11, 2012 at 9:27 AM, Dimuthu Leelarathne wrote:

> Hi Nirmal,
>
> Please see my comments inline.
>
> On Fri, Jan 6, 2012 at 12:11 AM, Nirmal Fernando  wrote:
>
>> Hi,
>>
>> $Subject is related to a JIRA issue [1].
>>
>> I have two questions.
>>
>> 1) Would it be okay to display qpid port as in the attached image?  If
>> not please suggest a suitable position.
>>
>
> What if do the same on Queue list page?
>
>>
>> 2) Is the following way of reading qpid port is encouraged?
>>
>>QpidServiceImpl qpidServiceImpl = new QpidServiceImpl(null);
>>String qpidPort = qpidServiceImpl.getPort();
>>
>>
> You have to use QpidService interface.
>
> thanks,
> dimuthu
>
>>  [1] https://wso2.org/jira/browse/STRATOS-1166
>>
>> Thanks
>> --
>> regards,
>> Nirmal
>>
>> Software Engineer, WSO2 Inc.
>> mobile: +94715779733
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Dimuthu Leelarathne
> Technical Lead and Product Manager, WSO2 Stratos
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
>
> Lean . Enterprise . Middleware
>
>
> ___
> 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] Bamboo builds continuously breaking

[Danushka Menikkumbura]

Are you guys planning to graduate possible components after the
stabilization effort?.

Danushka

On Tue, Jan 3, 2012 at 3:15 PM, Afkham Azeez  wrote:

> -1. That breaks the one-checkout & one-build concept. The building by
> parts is fine, but building from the root pom level is also essential. If
> we don't do that, we will never know when the one-checkout one-build fails.
> Basically, once this stabilization is done, there can be no failures at
> product level, and if new failures are introduced, they should be fixed
> ASAP.
>
> On Tue, Jan 3, 2012 at 3:09 PM, Pradeep Fernando  wrote:
>
>> Hi all,
>>
>> Had a chat with Dushan. Now we are building the carbon source from the
>> root pom. The build is almost woking fine. (it fails at the product level).
>>
>> The problem with this setup is, even though some products are building
>> fine, it has dependencies among product builds.
>>
>> Ex. due to a docGen issue in ESB product, all the subsequent product
>> builds get failed. (no packs)
>>
>> IMHO, correct way to do this is,
>>
>> *build carbon-source up-to features using a one build job
>> *create individual build jobs per each product.
>> * Once the first job finishes all the product jobs starts running.
>> (parallel)
>>
>> Dushan is trying this out in the Bamboos server.
>>
>>
>> we can use a bamboo profile to build carbon up to features (first-job). -
>> (so we dont have to comment out product builds from root pom)
>>
>> thanks,
>> --Pradeep
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; 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
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Discussion about changes to Carbon test framework in trunk

[Danushka Menikkumbura]

Also I think you need to have some startup/teardown impl in
CarbonTestRunner so that common init/cleanup work can be done in there. For
an example inserting a database entry at the beginning and deleting at the
end.

On Tue, Dec 13, 2011 at 10:44 AM, Afkham Azeez  wrote:

>
>
> On Tue, Dec 13, 2011 at 6:28 AM, Srinath Perera  wrote:
>
>> +1 .. Azeez talked to Krishantha as well, and we did some related work
>> for automation framework
>>
>
> The plan is to come up with a single framework which will reside in
> org.wso2.carbon.integration.core, which will be used by all the integration
> tests in the products as well as the automation tests. Something like the
> following.
>
>
> public class CarbonTestRunner extends TestSuite {
>
> public static Test suite() throws Exception {
> //copyArtifacts();
>
> TestSuite testSuite = new TestSuite();
>
> testSuite.addTestSuite(StartCarbonServerTest.class);
> testSuite.addTestSuite(LoginTest.class);
> testSuite.addTestSuite(SecurityVerificationTest.class);
>
> return testSuite;
> }
>
> public void copyArtifacts(){
>
> }
>
> public void startServers(){
>
> }
>
> public void runTests(){
>
> }
>
> public void shutdownServers(){
>
> }
> }
>
>
>> --Srinath
>>
>> On Tue, Dec 13, 2011 at 12:11 AM, Charith Wickramarachchi
>>  wrote:
>> >
>> >
>> > On Mon, Dec 12, 2011 at 11:41 PM, Afkham Azeez  wrote:
>> >>
>> >> Folks,
>> >> I would like to review & make changes to the current Carbon integration
>> >> test framework we have in carbon core. It is a bit of a mess now with
>> people
>> >> doing artifact copying in various ways. I would like to introduce a
>> >> CarbonTestRunner. A server will be started per CarbonTestRunner
>> instance.
>> >> CarbonTestRunner is a TestSuite. In your Carbon test cases you will
>> >> implement the copyArtifacts method. CarbonTestRunner will first call
>> >> copyArtifacts on all test cases, start the server, and run the tests.
>> >> Different product teams are doing this in various hacky ways now, but
>> we
>> >> need to have a proper way of doing this.
>> >>
>> >> In addition, we have also think about starting up multiple Carbon
>> servers
>> >> per CarbonTestRunner.
>> >>
>> >> Can we have a short design discussion about this tomorrow at 10AM?
>> >
>> >
>> >
>> > +1
>> >
>> > For come up with a Unified  Framework.
>> >
>> > cheers,
>> > Charith
>> >
>> >
>> >>
>> >>
>> >>
>> >> --
>> >> Afkham Azeez
>> >> Director of Architecture; 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
>> >>
>> >
>> >
>> >
>> > --
>> > Charith Dhanushka Wickramarachchi
>> > Software Engineer
>> > WSO2 Inc
>> > http://wso2.com/
>> > http://wso2.org/
>> >
>> > blog
>> > http://charithwiki.blogspot.com/
>> >
>> > twitter
>> > http://twitter.com/charithwiki
>> >
>> > Mobile : 0776706568
>> >
>> >
>>
>>
>>
>> --
>> 
>> 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/
>>   Photos: http://www.flickr.com/photos/hemapani/
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; 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
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Trunk build [ was Re: [Architecture] Running Tomcat within OSGi]

[Danushka Menikkumbura]

And you might find [1] quite useful too ;-).

[1] - http://www.papercut.com/blog/chris/2011/08/19/who-broke-the-build/

On Fri, Nov 4, 2011 at 9:42 AM, Pradeep Fernando  wrote:

>
>
> On Thu, Nov 3, 2011 at 9:34 PM, Danushka Menikkumbura <
> danushka.menikkumb...@gmail.com> wrote:
>
>> Pradeep,
>>
>> It is really worthwhile having a CIS (Jenkins) set up so that you can
>> have integration tests, coverage checks, find bugs, doc generation, etc
>> integrated. If you can host it publicly, then all Carbon committers can
>> have access to it's dashboard and visualize various patterns. It will also
>> help you detect all sorts of issues early preventing you from wasting time
>> on build breaks, etc when a release is around the corner.
>>
>
>
> yes you are right. we are gonna have a CI server this time. Actually we
> had a working one. But for some other reason, we had to shut it down.
>
> thanks,
> --Pradeep
>
>
>>
>> If you already have something like that set up please ignore this mail.
>>
>> Thanks,
>> Danushka
>>
>> On Wed, Nov 2, 2011 at 11:55 PM, Pradeep Fernando wrote:
>>
>>> Hi,
>>>
>>> looks like hackathon is going well. Its better if we can achieve the
>>> following items in this hackathon. (I think some of the things are already
>>> underway).
>>>
>>> * trunk build from the root pom without errors. - (i guess this is
>>> working)
>>> * moving all products to maven3 build (carbon, as, gs are done as of now)
>>> * create a new profile for greg doc generation process since it takes a
>>> lot of time, and we dont want the doc generation in our day to day build.
>>> (or else we should find a solution for that blacklisting thing)
>>> * upgrade the trunk version, 3.2.0-SNAPSHOT to 4.0.0-SNAPSHOT (this is a
>>> grep/sed)
>>> * branch out new dependencies and make sure they don't break the current
>>> build (right now we are pointing to 3.2.0 branch)
>>> *Set up a CI server
>>>
>>>
>>> thanks,
>>> --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
>>
>>
>
>
> --
> Pradeep Fernando
> Software Engineer
> WSO2 Inc; http://wso2.com/
>
> blog: http://pradeepfernando.blogspot.com/
> m: +94776603662
>
> ___
> 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] Trunk build [ was Re: [Architecture] Running Tomcat within OSGi]

[Danushka Menikkumbura]

Pradeep,

It is really worthwhile having a CIS (Jenkins) set up so that you can have
integration tests, coverage checks, find bugs, doc generation, etc
integrated. If you can host it publicly, then all Carbon committers can
have access to it's dashboard and visualize various patterns. It will also
help you detect all sorts of issues early preventing you from wasting time
on build breaks, etc when a release is around the corner.

If you already have something like that set up please ignore this mail.

Thanks,
Danushka

On Wed, Nov 2, 2011 at 11:55 PM, Pradeep Fernando  wrote:

> Hi,
>
> looks like hackathon is going well. Its better if we can achieve the
> following items in this hackathon. (I think some of the things are already
> underway).
>
> * trunk build from the root pom without errors. - (i guess this is working)
> * moving all products to maven3 build (carbon, as, gs are done as of now)
> * create a new profile for greg doc generation process since it takes a
> lot of time, and we dont want the doc generation in our day to day build.
> (or else we should find a solution for that blacklisting thing)
> * upgrade the trunk version, 3.2.0-SNAPSHOT to 4.0.0-SNAPSHOT (this is a
> grep/sed)
> * branch out new dependencies and make sure they don't break the current
> build (right now we are pointing to 3.2.0 branch)
> *Set up a CI server
>
>
> thanks,
> --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 Java broker recent changes

[Danushka Menikkumbura]

+1.

In fact even now the broker architecture is neat but having to support
multiple protocol versions has made it little sloppy. On a side note I
suggest you involve personally in 1.0 design/review work to get it right.

Danushka

On Mon, Oct 31, 2011 at 5:22 PM, Paul Fremantle  wrote:

> Danushka
>
> My main thought right now is that we need to move to 1.0 support for the
> standard. I think one of the issues with Qpid - and I may  be wrong - is
> that the changing set of specs has meant too many updates to the core. I'd
> love to see some stability around 1.0 and maybe even a plan to deprecate
> and remove old spec versions. What do you think?
>
> Paul
>
>
> On 31 October 2011 11:37, Danushka Menikkumbura <
> danushka.menikkumb...@gmail.com> wrote:
>
>> Hi Paul,
>>
>> Yes that I've heard.
>>
>> My concern was OOM issues. The ones we identified and submitted patches
>> for were mainly at the transport/session layer and had nothing to do with
>> the underlying data store. Also as I understand the Cassandra store is for
>> broker scaling (?).
>>
>> Robbie has done lots of changes to the broker code in recent past
>> invalidating bulk of the patches that we submitted. My gut feeling is that
>> the broker is better of in terms of memory usage with these changes. I can
>> give it a try too at least with the standalone broker.
>>
>> Thanks,
>> Danushka
>>
>>
>> On Mon, Oct 31, 2011 at 3:41 PM, Paul Fremantle  wrote:
>>
>>> Danushka
>>>
>>> Thanks! We'll take a look. We have also been trying out a Cassandra
>>> store if you are interested.
>>>
>>> Paul
>>>
>>> On 31 October 2011 06:01, Danushka Menikkumbura <
>>> danushka.menikkumb...@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> Apparently Robbie has done certain changes to the broker which claim to
>>>> have fixed some serious OOM issues. Specially [1] looks appealing. Can
>>>> someone working on Qpid bits please check?.
>>>>
>>>> [1] -
>>>> http://apache-qpid-users.2158936.n2.nabble.com/What-is-the-memory-footprint-of-an-Apache-qpid-queue-td6893642.html
>>>>
>>>> Danushka
>>>>
>>>> ___
>>>> 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
>>>
>>> UK: +44 207 096 0336
>>> US: +1 646 595 7614
>>>
>>> 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
>>>
>>>
>>
>> ___
>> 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
>
> UK: +44 207 096 0336
> US: +1 646 595 7614
>
> 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
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Java broker recent changes

[Danushka Menikkumbura]

Hi Paul,

Yes that I've heard.

My concern was OOM issues. The ones we identified and submitted patches for
were mainly at the transport/session layer and had nothing to do with the
underlying data store. Also as I understand the Cassandra store is for
broker scaling (?).

Robbie has done lots of changes to the broker code in recent past
invalidating bulk of the patches that we submitted. My gut feeling is that
the broker is better of in terms of memory usage with these changes. I can
give it a try too at least with the standalone broker.

Thanks,
Danushka

On Mon, Oct 31, 2011 at 3:41 PM, Paul Fremantle  wrote:

> Danushka
>
> Thanks! We'll take a look. We have also been trying out a Cassandra store
> if you are interested.
>
> Paul
>
> On 31 October 2011 06:01, Danushka Menikkumbura <
> danushka.menikkumb...@gmail.com> wrote:
>
>> Hi,
>>
>> Apparently Robbie has done certain changes to the broker which claim to
>> have fixed some serious OOM issues. Specially [1] looks appealing. Can
>> someone working on Qpid bits please check?.
>>
>> [1] -
>> http://apache-qpid-users.2158936.n2.nabble.com/What-is-the-memory-footprint-of-an-Apache-qpid-queue-td6893642.html
>>
>> Danushka
>>
>> ___
>> 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
>
> UK: +44 207 096 0336
> US: +1 646 595 7614
>
> 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
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Qpid Java broker recent changes

[Danushka Menikkumbura]

Hi,

Apparently Robbie has done certain changes to the broker which claim to
have fixed some serious OOM issues. Specially [1] looks appealing. Can
someone working on Qpid bits please check?.

[1] -
http://apache-qpid-users.2158936.n2.nabble.com/What-is-the-memory-footprint-of-an-Apache-qpid-queue-td6893642.html

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

[Carbon-dev] Fwd: Java Broker - creating and closing too many connections causes memory leak?

[Danushka Menikkumbura]

FYA.

-- Forwarded message --
From: Praveen M 
Date: Sat, Oct 29, 2011 at 12:31 AM
Subject: Java Broker - creating and closing too many connections causes
memory leak?
To: us...@qpid.apache.org


Hi,

 I ran the following test a few times and I ran into a OOM exception. Can
someone please tell me if i'm doing something wrong or if this could
potentially be a bug? Thanks.

1) Create 1000 queues.
2) Create 4 consumers -> each consumer uses it's own connection
3) In a loop do the following,

for each queues 1..1000 {
   create producer(create new connection) for queue |i|
   produce 1 message for that queue.
   close producer (close connection)
}

4) Wait till all messages are consumed by the 4 consumers and then close all
4 consumers.
5) Re-Run the test without a broker restart

Each time the test ran, it created and closed 1004 connections (with at most
5 connections living in parallel...we close the earlier queue's producer's
connection before creating a producer for the next queue).

Also, I checked for any stray threads on the client side due to any unclosed
connection, and it looks like everything was closed fine (I didn't see any
stray threads).

On the broker side, I saw that the memory usage creeps up each time i re-run
the test, and eventually hits a OOM. (Running the above test about 5 times
causes a OOM )

I tried profiling the broker to see what's holding on to all that memory and
saw a certain class's(org.apache.qpid.transport.Method[]) instance count
grow up each time my test was run and it was holding the maximum memory in
the broker.

The number of instances of org.apache.qpid.transport.Method[] were trending
as follows:

After first test - 2008
After second test - 4016
... and so on.

There seems to be a direct relation between the number of those objects and
the connections created and closed. ~ Why are these objects not freed on
closing the connection??
I'm using the Java Broker out of trunk and using it with a DerbyMessageStore
for the test.

Or is there something fundamentally wrong by the way I run the test, I guess
opening and closing so many connections isn't a great idea (maybe I should
be dealing with sessions). But still, I see that this can be a potential
problem in a really long running broker system(where we cannot afford to
restart the broker periodically) which can have clients joining/leaving at
regular intervals.


Thank you for all the effort answering our questions,
--
-Praveen
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Fwd: [ANNOUNCE] Qpid 0.12 released

[Danushka Menikkumbura]

-- Forwarded message --
From: Justin Ross 
Date: Wed, Aug 24, 2011 at 11:21 PM
Subject: [ANNOUNCE] Qpid 0.12 released
To: annou...@apache.org, d...@qpid.apache.org, us...@qpid.apache.org


The Apache Qpid community is pleased to announce the immediate
availability of Apache Qpid 0.12.

Apache Qpid (http://qpid.apache.org) is a cross-platform enterprise
messaging solution which implements the Advanced Message Queuing
Protocol (AMQP, http://www.amqp.org).  It provides brokers written in
C++ and Java, along with clients for C++, Java JMS, .Net, and Python.

Qpid 0.12 is available from our website:

 http://qpid.apache.org/download.cgi

The 0.12 release includes many bug fixes and improvements.  We
recommend that all users upgrade.  A comprehensive list of changes in
the 0.12 release is available here:

 http://qpid.apache.org/release_notes_0.12.html

Thanks to all the users and contributors who have helped to improve
Apache Qpid.

-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] SSL is broken on the Qpid broker

[Danushka Menikkumbura]

FYA [1].

Might have an impact on the CSG.

[1] - https://issues.apache.org/jira/browse/QPID-3429

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

[Carbon-dev] Having Carbon build mails on a separate list

[Danushka Menikkumbura]

Hi,

Is $subject possible?

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

Re: [Carbon-dev] Qpid Patches

[Danushka Menikkumbura]

Please find the doc at [1].

[1] -
https://docs.google.com/a/wso2.com/document/d/1WfaGLInDM-CpFnYeBxwUQyw0jab9BarkG_teuKSVYMc/edit?hl=en_US

Danushka

On Wed, Jun 29, 2011 at 12:45 PM, Danushka Menikkumbura
wrote:

> Yes. I was planning to add that as a separate task under the JIRA.
>
> Danushka
>
>
> On Wed, Jun 29, 2011 at 11:50 AM, Amila Suriarachchi wrote:
>
>> Can you please prepare and document that lists all the steps required to
>> add the Apache Qpid to the wso2 branch. This help us in future.
>>
>> thanks,
>> Amila.
>>
>> On Wed, Jun 29, 2011 at 11:30 AM, Danushka Menikkumbura <
>> danus...@wso2.com> wrote:
>>
>>> I have forked the latest Qpid trunk (r1138752) into Carbon dependencies
>>> with the version 0.11-wso2v2. I have also patched it and changed orbit and
>>> features/qpid modules on the trunk and 3.2.1 branch accordingly too, have
>>> not changed Qpid version in products/services, though.
>>>
>>> Please find the set of patches that we need to push into Apache at [1].
>>>
>>> Srinath, I have prepared and attached patches for your fixes to sub tasks
>>> assigned to you. Please attach them to corresponding Qpid JIRA's that I have
>>> mentioned.
>>>
>>> Charith, I have created a sub task to track the class loading issue that
>>> you have raised. Please create sub tasks for other fixes that you are
>>> working on.
>>>
>>> Rajika, please check if the SSL changes have made it into the latest
>>> version.
>>>
>>> I ran the performance test that we used to check OOM against the latest
>>> Qpid broker and could see some improvements. In fact they have changed the
>>> connection handling logic too. Someone from the MB team please verify.
>>>
>>> I have also created patches that are Carbon-specific at [2]. Robbie
>>> Gemmell has started to refactor broker start up code. So, we might be able
>>> to push some of them in too based on his changes.
>>>
>>> *** I will continue to follow up on the patches submitted by me.
>>>
>>> [1] - https://wso2.org/jira/browse/CARBON-10891
>>> [2] - https://wso2.org/jira/browse/CARBON-10905
>>>
>>> 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
>>
>>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid Patches

[Danushka Menikkumbura]

Yes. I was planning to add that as a separate task under the JIRA.

Danushka

On Wed, Jun 29, 2011 at 11:50 AM, Amila Suriarachchi  wrote:

> Can you please prepare and document that lists all the steps required to
> add the Apache Qpid to the wso2 branch. This help us in future.
>
> thanks,
> Amila.
>
> On Wed, Jun 29, 2011 at 11:30 AM, Danushka Menikkumbura  > wrote:
>
>> I have forked the latest Qpid trunk (r1138752) into Carbon dependencies
>> with the version 0.11-wso2v2. I have also patched it and changed orbit and
>> features/qpid modules on the trunk and 3.2.1 branch accordingly too, have
>> not changed Qpid version in products/services, though.
>>
>> Please find the set of patches that we need to push into Apache at [1].
>>
>> Srinath, I have prepared and attached patches for your fixes to sub tasks
>> assigned to you. Please attach them to corresponding Qpid JIRA's that I have
>> mentioned.
>>
>> Charith, I have created a sub task to track the class loading issue that
>> you have raised. Please create sub tasks for other fixes that you are
>> working on.
>>
>> Rajika, please check if the SSL changes have made it into the latest
>> version.
>>
>> I ran the performance test that we used to check OOM against the latest
>> Qpid broker and could see some improvements. In fact they have changed the
>> connection handling logic too. Someone from the MB team please verify.
>>
>> I have also created patches that are Carbon-specific at [2]. Robbie
>> Gemmell has started to refactor broker start up code. So, we might be able
>> to push some of them in too based on his changes.
>>
>> *** I will continue to follow up on the patches submitted by me.
>>
>> [1] - https://wso2.org/jira/browse/CARBON-10891
>> [2] - https://wso2.org/jira/browse/CARBON-10905
>>
>> 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
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Qpid Patches

[Danushka Menikkumbura]

I have forked the latest Qpid trunk (r1138752) into Carbon dependencies with
the version 0.11-wso2v2. I have also patched it and changed orbit and
features/qpid modules on the trunk and 3.2.1 branch accordingly too, have
not changed Qpid version in products/services, though.

Please find the set of patches that we need to push into Apache at [1].

Srinath, I have prepared and attached patches for your fixes to sub tasks
assigned to you. Please attach them to corresponding Qpid JIRA's that I have
mentioned.

Charith, I have created a sub task to track the class loading issue that you
have raised. Please create sub tasks for other fixes that you are working
on.

Rajika, please check if the SSL changes have made it into the latest
version.

I ran the performance test that we used to check OOM against the latest Qpid
broker and could see some improvements. In fact they have changed the
connection handling logic too. Someone from the MB team please verify.

I have also created patches that are Carbon-specific at [2]. Robbie Gemmell
has started to refactor broker start up code. So, we might be able to push
some of them in too based on his changes.

*** I will continue to follow up on the patches submitted by me.

[1] - https://wso2.org/jira/browse/CARBON-10891
[2] - https://wso2.org/jira/browse/CARBON-10905

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

[Carbon-dev] 3.2.1 stuff on 3.2.0 branch

[Danushka Menikkumbura]

components/logging/org.wso2.carbon.logging.view.ui for an instance.

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

Re: [Carbon-dev] Patches for L1 issues in 3.2.0 branch

[Danushka Menikkumbura]

The Qpid memory leak fix is being tested right now.

Danushka

On Mon, May 30, 2011 at 9:55 AM, Denis Weerasiri  wrote:

> Hi,
> If you have patches for L1 issues which should be shipped with 3.2.0
> branch, please reply to this thread.
>
> --
> Thanks,
> Denis
> --
> *Denis Weerasiri*
> Software Engineer; WSO2 Inc.; http://wso2.com,
> *email: denis ** [AT] wso2.com* 
> *
> blog: **http://ddweerasiri.blogspot.com*
> *
> twitter: **http://twitter.com/ddweerasiri*
> *
> linked-in: 
> **http://lk.linkedin.com/in/ddweerasiri*
>
>
> ___
> 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] Carbon 3.2.0 code freeze - 10 PM IST - Today

[Danushka Menikkumbura]

We have hit an OOM again. Need to look at the heap dump.

Danushka

On Wed, May 25, 2011 at 5:32 PM, Afkham Azeez  wrote:

> Manjula, Danushka, Rajika, Ruchira,
> Can we resolve your L1s today?
>
> On Wed, May 25, 2011 at 4:25 PM, Prabath Siriwardena wrote:
>
>> $subject
>>
>> We have only 5 L1s.. The owners of those L1s please update this thread
>> with the status...
>>
>> --
>> Thanks & Regards,
>> Prabath
>>
>> http://blog.facilelogin.com
>> http://RampartFAQ.com
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; 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] Build failure in orbit in branch

[Danushka Menikkumbura]

Just finished building the orbit w/o issue.

Danushka

On Wed, May 25, 2011 at 11:26 AM, Rajika Kumarasiri  wrote:

>
> [INFO] Installing
> /home/rajika/projects/carbon/3.2.0/orbit/httpcore/4.1.0-wso2v1/target/httpcore-4.1.0-wso2v1.jar
> to
> /home/rajika/.m2/repository/org/apache/httpcomponents/wso2/httpcore/4.1.0-wso2v1/httpcore-4.1.0-wso2v1.jar
> [INFO] [bundle:install {execution: default-install}]
> [INFO] Local OBR update disabled (enable with -DobrRepository)
> [INFO]
> 
> [INFO] Building axis2.client.wso2
> [INFO]task-segment: [clean, install]
> [INFO]
> 
> [INFO] [clean:clean {execution: default-clean}]
> [INFO]
> 
> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] Failed to resolve artifact.
>
> Missing:
> --
> 1) org.apache.ws.commons.schema.wso2:XmlSchema:jar:1.4.7.wso2v1
>
>   Try downloading the file manually from the project website.
>
>   Then, install it using the command:
>   mvn install:install-file -DgroupId=org.apache.ws.commons.schema.wso2
> -DartifactId=XmlSchema -Dversion=1.4.7.wso2v1 -Dpackaging=jar
> -Dfile=/path/to/file
>
>   Alternatively, if you host your own repository you can deploy the file
> there:
>   mvn deploy:deploy-file -DgroupId=org.apache.ws.commons.schema.wso2
> -DartifactId=XmlSchema -Dversion=1.4.7.wso2v1 -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>   Path to dependency:
>1) org.apache.axis2.wso2:axis2-client:bundle:1.6.1.wso2v1
>2) org.apache.ws.commons.schema.wso2:XmlSchema:jar:1.4.7.wso2v1
>
> --
> 1 required artifact is missing.
>
> for artifact:
>   org.apache.axis2.wso2:axis2-client:bundle:1.6.1.wso2v1
>
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2),
>   wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
>
>
>
> NOTE: Maven is executing in offline mode. Any artifacts not already in your
> local
> repository will be inaccessible.
>
>
> [INFO] ---
>
> ___
> 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] components/eventing and features/eventing still there on the branch

[Danushka Menikkumbura]

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

Re: [Carbon-dev] What is the status of the branch?

[Danushka Menikkumbura]

I was able to build dependencies with a clean repo. Now building the rest.

Danushka

On Tue, May 24, 2011 at 8:53 PM, Afkham Azeez  wrote:

> When I try to build the branch from the top, I get the following error
>
> [INFO]
> NOTE: Maven is executing in offline mode. Any artifacts not already in your
> local
> repository will be inaccessible.
>
> [INFO] Scanning for projects...
> [INFO]
> 
> [ERROR] BUILD FAILURE
> [INFO]
> 
> [INFO] Project 'org.wso2.carbon:org.wso2.carbon.logging.ext' is duplicated
> in the reactor
> [INFO]
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> 
> [INFO] Total time: 36 seconds
> [INFO] Finished at: Tue May 24 20:53:39 IST 2011
> [INFO] Final Memory: 342M/641M
> [INFO]
> 
>
>
> On Tue, May 24, 2011 at 8:51 PM, Supun Kamburugamuva wrote:
>
>> The initial work on the branch is done. We have to build the products
>> and fix the issues if there are any. ESB build is successful and we
>> have done some smoke testing as well. We are building the products
>> locally. Also Denis has triggered a build in the builder machine as
>> well.
>>
>> Thanks,
>> Supun..
>>
>> On Tue, May 24, 2011 at 8:47 PM, Afkham Azeez  wrote:
>> > Please provide an update.
>> >
>> > --
>> > Afkham Azeez
>> > Director of Architecture; 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
>> >
>>
>>
>>
>> --
>> Supun Kamburugamuva
>> Technical Lead &  Product Manager, WSO2 Inc.; http://wso2.com
>> Member, Apache Software Foundation; http://www.apache.org
>> WSO2 Inc.;  http://wso2.org
>> E-mail: su...@wso2.com;  Mobile: +94 77 431 3585
>> Blog: http://supunk.blogspot.com
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; 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
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Only 13 L1s left!

[Danushka Menikkumbura]

We need to rerun the Qpid long-runing test before resolving the Qpid issue.

Danushka

On Tue, May 24, 2011 at 7:52 PM, Afkham Azeez  wrote:

> We've just got 13 L1 issues left. Good effort team.
>
> Can we have the remaining issues resolved today?
>
> --
> *Afkham Azeez*
> Director of Architecture; 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] 3.2.0 Branch

[Danushka Menikkumbura]

On it for the MB.

Danushka

On Tue, May 24, 2011 at 2:41 PM, Supun Kamburugamuva  wrote:

> We have fixed the versions in the 3.2.0 branch. We could build the ESB
> successfully. Still in the process of building other products.
> Products teams please try to build your products and fix the issues if
> there are any.
>
> Thanks,
> --
> Supun Kamburugamuva
> Technical Lead &  Product Manager, WSO2 Inc.; http://wso2.com
> Member, Apache Software Foundation; http://www.apache.org
> WSO2 Inc.;  http://wso2.org
> E-mail: su...@wso2.com;  Mobile: +94 77 431 3585
> Blog: http://supunk.blogspot.com
> ___
> 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] Configuring Axis2 JMS transport listener to work with Qpid

[Danushka Menikkumbura]

You need to have your connection factories, queues and topic defined in your
jndi properties file.

Danushka


axis2-jms-transport-listener-config-for-qpid
Description: Binary data


jndi.properties
Description: Binary data
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] What should be the correct version for QPid

[Danushka Menikkumbura]

It is 0.11-wso2v1.

Danushka

On Sat, May 21, 2011 at 11:03 PM, Milinda Pathirage wrote:

> Current version of QPid dependency is 0.11. I think we should differentiate
> our code base version from normal Apache versions.
>
> Thanks
> Milinda
>
> --
> Milinda Pathirage
> Technical Lead and Product Manager, Business Process Server - WSO2 Inc;
> http://wso2.com
> Blog: http://blog.mpathirage.com
>
> Lean Enterprise Middleware
>
> ___
> 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 errors when running on WAS 7.0.0.11

[Danushka Menikkumbura]

Excellent!

On Fri, May 20, 2011 at 7:59 PM, Ajith Vitharana  wrote:

>
>
> On Fri, May 20, 2011 at 3:26 PM, Danushka Menikkumbura 
> wrote:
>
>> Hi Ajith,
>>
>> Any update on this?
>>
>
> Hi Danushka,
>
> I have verified with latest build (20-May-2011) and registry eventing
> working fine on WAS 7.0.11 . :)
> Plz check with new log file(SystemOut-new.log).
>
> Thanks
> Ajithn
>
>>
>> Danushka
>>
>> On Thu, May 19, 2011 at 9:02 PM, Danushka Menikkumbura > > wrote:
>>
>>> Fixed on the trunk.
>>>
>>> Danushka
>>>
>>> On Thu, May 19, 2011 at 6:03 AM, Ajith Vitharana wrote:
>>>
>>>>  Hi all,
>>>>
>>>> I'm testing latest wso2greg-4.0.0-SNAPSHOT on WAS 7.0.0.11. (java
>>>> version "1.6.0_24" , WindowsXp).
>>>> I did not not encountered any broken pages, but when i trying to
>>>> subscribe for a resource, following exception occurred.
>>>> I noted that qpid start failed , because of the * 
>>>> java.lang.NoClassDefFoundError:
>>>> com/sun/security/auth/UserPrincipal*
>>>> Plz check this with SystemOut.log.
>>>>
>>>>
>>>> [5/16/11 16:32:27:687 IST] 0054 EventPublishe E
>>>> org.wso2.carbon.event.core.internal.EventPublisher run Can not publish the
>>>> message
>>>>
>>>> org.wso2.carbon.event.core.exception.EventBrokerException: Can not create
>>>> topic connection
>>>> at
>>>> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.getTopicConnection(JMSDeliveryManager.java:76)
>>>> at
>>>> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.publish(JMSDeliveryManager.java:133)
>>>> at
>>>> org.wso2.carbon.event.core.internal.EventPublisher.run(EventPublisher.java:56)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>> at java.lang.Thread.run(Thread.java:736)
>>>> Caused by: javax.jms.JMSException: Error creating connection: Connection
>>>> refused: connect
>>>> at
>>>> org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:286)
>>>> at
>>>> org.apache.qpid.client.AMQConnectionFactory.createTopicConnection(AMQConnectionFactory.java:345)
>>>> at
>>>> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.getTopicConnection(JMSDeliveryManager.java:70)
>>>> ... 5 more
>>>> Caused by: org.apache.qpid.AMQConnectionFailureException: Connection
>>>> refused: connect
>>>> at
>>>> org.apache.qpid.AMQConnectionFailureException.(AMQConnectionFailureException.java:43)
>>>> at
>>>> org.apache.qpid.client.AMQConnection.(AMQConnection.java:472)
>>>> at
>>>> org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:276)
>>>> ... 7 more
>>>> Caused by: org.apache.qpid.transport.TransportException: Error
>>>> connecting to broker
>>>> at
>>>> org.apache.qpid.transport.network.io.IoNetworkTransport.init(IoNetworkTransport.java:78)
>>>> at
>>>> org.apache.qpid.transport.TransportBuilder.init(TransportBuilder.java:44)
>>>> at org.apache.qpid.transport.Connection.connect(Connection.java:240)
>>>> at
>>>> org.apache.qpid.client.AMQConnectionDelegate_0_10.makeBrokerConnection(AMQConnectionDelegate_0_10.java:184)
>>>> at
>>>> org.apache.qpid.client.AMQConnection.makeBrokerConnection(AMQConnection.java:617)
>>>> at
>>>> org.apache.qpid.client.AMQConnection.(AMQConnection.java:396)
>>>> ... 8 more
>>>> Caused by: java.net.ConnectException: Connection refused: connect
>>>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>>>> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:352)
>>>> at
>>>> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:214)
>>>> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:201)
>>>> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:378)
>>>> at java.net.Socket.connect(Socket.java:537)
>>>> at java.net.Socket.connect(Socket.java:487)
>>>> at
>>>> org.apache.qpid.transport.network.io.IoNetworkTransport.init(IoNetworkTransport.java:74)
>>>> ... 13 more
>>>>
>>>> Thanks
>>>> Ajithn
>>>>
>>>> ___
>>>> 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] 56 L1s still open!

[Danushka Menikkumbura]

I have 5 L1's assigned to myself.

[1] - https://wso2.org/jira/browse/CARBON-10154
[2] - https://wso2.org/jira/browse/CARBON-9916
[3] - https://wso2.org/jira/browse/CARBON-9897
[4] - https://wso2.org/jira/browse/CARBON-9515
[5] - https://wso2.org/jira/browse/CARBON-9996

[6] - https://issues.apache.org/jira/browse/QPID-3259
[7] - https://issues.apache.org/jira/browse/QPID-3234

[1] and [2] I can resolve today. [3] and [4] can be resolved Monday. The
long-running had been running when I checked last evening. I would rather
that we waited until Monday.

[5] is actually does not affect our products as we never reuse sessions in
MB/Event. It only occurs if someone uses Qpid client libraries with a JMS
client. Fixing that even is not trivial [6]. I am concerned about fixing
something of this nature at this point. To me it is just tip of the iceberg.
There are certain other fundamental issues that we need to fix in Qpid [7].
Therefore shall we leave it out for now and revisit after the release?

Danushka

On Fri, May 20, 2011 at 2:59 PM, Prabath Siriwardena wrote:

> Is it possible to see whether we can distribute the L1 issues assigned
> to Pradeep/Kalpanie/Senaka/Dhanushka/Shammi and Fazlan..? PMs can you
> please have a look..
>
> Pradeep - 4
> Kalpanie - 4
> Senaka - 4
> Dhanushka - 4
> Shammi - 4
> Fazlan - 3
>
> Thanks & regards,
> -Prabath
>
> On Fri, May 20, 2011 at 12:42 PM, Afkham Azeez  wrote:
> > Not a single person has updated the issues yet?
> >
> > On Fri, May 20, 2011 at 11:49 AM, Afkham Azeez  wrote:
> >>
> >> All folks who have L1s assigned to them,
> >> Please take some time immediately to update the due date in each of your
> >> issues. We want to get a clear idea of how long it will take to fix the
> >> existing L1s. Please do this immediately. I will review these at 2PM.
> >> Thanks
> >> Azeez
> >>
> >> On Fri, May 20, 2011 at 11:34 AM, Afkham Azeez  wrote:
> >>>
> >>> Folks,
> >>> What is the plan to address these? Are people working on these L1s?
> After
> >>> the branching, you have to make sure that the fixes are committed to
> the
> >>> trunk as well as the branch. The proper process is, to fix this in the
> >>> trunk, create a patch and attach it to the Jira, and then commit that
> patch
> >>> to the trunk. Please follow that process.
> >>> Thanks
> >>> Azeez
> >>>
> >>> --
> >>> Afkham Azeez
> >>> Director of Architecture; 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
> >>
> >>
> >>
> >> --
> >> Afkham Azeez
> >> Director of Architecture; 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
> >
> >
> >
> > --
> > Afkham Azeez
> > Director of Architecture; 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
> >
> >
>
>
>
> --
> Thanks & Regards,
> Prabath
>
> http://blog.facilelogin.com
> http://RampartFAQ.com
> ___
> 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 errors when running on WAS 7.0.0.11

[Danushka Menikkumbura]

Hi Ajith,

Any update on this?

Danushka

On Thu, May 19, 2011 at 9:02 PM, Danushka Menikkumbura wrote:

> Fixed on the trunk.
>
> Danushka
>
> On Thu, May 19, 2011 at 6:03 AM, Ajith Vitharana  wrote:
>
>>  Hi all,
>>
>> I'm testing latest wso2greg-4.0.0-SNAPSHOT on WAS 7.0.0.11. (java version
>> "1.6.0_24" , WindowsXp).
>> I did not not encountered any broken pages, but when i trying to subscribe
>> for a resource, following exception occurred.
>> I noted that qpid start failed , because of the * 
>> java.lang.NoClassDefFoundError:
>> com/sun/security/auth/UserPrincipal*
>> Plz check this with SystemOut.log.
>>
>>
>> [5/16/11 16:32:27:687 IST] 0054 EventPublishe E
>> org.wso2.carbon.event.core.internal.EventPublisher run Can not publish the
>> message
>>
>> org.wso2.carbon.event.core.exception.EventBrokerException: Can not create
>> topic connection
>> at
>> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.getTopicConnection(JMSDeliveryManager.java:76)
>> at
>> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.publish(JMSDeliveryManager.java:133)
>> at
>> org.wso2.carbon.event.core.internal.EventPublisher.run(EventPublisher.java:56)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:736)
>> Caused by: javax.jms.JMSException: Error creating connection: Connection
>> refused: connect
>> at
>> org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:286)
>> at
>> org.apache.qpid.client.AMQConnectionFactory.createTopicConnection(AMQConnectionFactory.java:345)
>> at
>> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.getTopicConnection(JMSDeliveryManager.java:70)
>> ... 5 more
>> Caused by: org.apache.qpid.AMQConnectionFailureException: Connection
>> refused: connect
>> at
>> org.apache.qpid.AMQConnectionFailureException.(AMQConnectionFailureException.java:43)
>> at org.apache.qpid.client.AMQConnection.(AMQConnection.java:472)
>> at
>> org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:276)
>> ... 7 more
>> Caused by: org.apache.qpid.transport.TransportException: Error connecting
>> to broker
>> at
>> org.apache.qpid.transport.network.io.IoNetworkTransport.init(IoNetworkTransport.java:78)
>> at
>> org.apache.qpid.transport.TransportBuilder.init(TransportBuilder.java:44)
>> at org.apache.qpid.transport.Connection.connect(Connection.java:240)
>> at
>> org.apache.qpid.client.AMQConnectionDelegate_0_10.makeBrokerConnection(AMQConnectionDelegate_0_10.java:184)
>> at
>> org.apache.qpid.client.AMQConnection.makeBrokerConnection(AMQConnection.java:617)
>> at org.apache.qpid.client.AMQConnection.(AMQConnection.java:396)
>> ... 8 more
>> Caused by: java.net.ConnectException: Connection refused: connect
>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:352)
>> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:214)
>> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:201)
>> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:378)
>> at java.net.Socket.connect(Socket.java:537)
>> at java.net.Socket.connect(Socket.java:487)
>> at
>> org.apache.qpid.transport.network.io.IoNetworkTransport.init(IoNetworkTransport.java:74)
>> ... 13 more
>>
>> Thanks
>> Ajithn
>>
>> ___
>> 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] Can't send/receive JMS Object Messages to/from Qpid broker from Carbon Environment.

[Danushka Menikkumbura]

Also the class-loading issues in JMS transport and this particular issue
that Charith is having are results of that.

Danushka

On Fri, May 20, 2011 at 11:01 AM, Afkham Azeez  wrote:

> Of course we can go for a very clean OSGi based solution if we drop
> supports for Carbon webapp deployment support. We have major limitations
> because of this. Even HTTP session replication cannot be done because the
> classes placed into the HTTP session in the OSGi container are not visible
> to Tomcat.
>
>
> On Fri, May 20, 2011 at 10:15 AM, Sameera Jayasoma wrote:
>
>> Again, this happens due to duplication qpid jars inside the
>> $CARBON_HOME/repository/components/plugins and $CARBON_HOME/lib folder. We
>> had a look at this issue couple of times, but unable to find a proper
>> solution.
>>
>> The deserialized Object is loaded inside the OSGi environment, but the
>> deserialization happens inside the system app classloader space. Hence the
>> Class is not visible.
>>
>> One option is to put the classes to the lib folder. But thats ugly.
>>
>> Thanks,
>> Sameera
>>
>> On Fri, May 20, 2011 at 9:22 AM, Charith Wickramarachchi <
>> char...@wso2.com> wrote:
>>
>>> Hi ,
>>>
>>> In the ESB Message Store we have an option where users can point to any
>>> JMS broker as the underlying message storage. Here we store the Message as a
>>> serializable Object Message.
>>> Problem is when i try to connect to a Qpid broker using our qpid client
>>> libs in the Carbon environment  it gives a Class not found Error when we try
>>> to de serialize the message back to the Original format.
>>>
>>> Here the problem is at the point where it de serialize the message. The
>>> the serializable object type we used is not visible to that class loader.
>>> I tried using the ActiveMQ broker with its client libs. but did not face
>>> this issue.
>>>
>>> We need to solve this Problem and this a blocker. One possible work
>>> around i can think of is change the way i serialize the message to use JMS
>>> TextMessages instead and use Message headers to keep the context
>>> information. That will resolve issue i m facing.
>>>
>>> But we mush fix this in a proper way to support sending JMSObject
>>> messages from the Carbon Environment since otherwise it implies that
>>> we can't filly utilize the functionality of our Message broker inside the
>>> carbon Environment.
>>>
>>> Help or directions for resolving this is highly appreciated.
>>>
>>> thanks,
>>> Charith
>>>
>>>
>>> --
>>> Charith Dhanushka Wickramarachchi
>>> Software Engineer
>>> WSO2 Inc
>>> http://wso2.com/
>>> http://wso2.org/
>>>
>>> blog
>>> http://charithwiki.blogspot.com/
>>>
>>> twitter
>>> http://twitter.com/charithwiki
>>>
>>>
>>>
>>>
>>> ___
>>> 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
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; 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
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Can't send/receive JMS Object Messages to/from Qpid broker from Carbon Environment.

[Danushka Menikkumbura]

I should look at the ESB Message Store right?


On Fri, May 20, 2011 at 9:46 AM, Charith Wickramarachchi
wrote:

>
>
> On Fri, May 20, 2011 at 9:34 AM, Danushka Menikkumbura 
> wrote:
>
>> Problem is when i try to connect to a Qpid broker using our qpid client
>>> libs in the Carbon environment  it gives a Class not found Error when we try
>>> to de serialize the message back to the Original format.
>>>
>>
>> What is the class that it complains about?
>>
>
> Its an Internal Serializable class named JMSPersistentMessage which holds
> the persistent format of the message. And its the Object type that we set in
> the jms ObjectMessage
>
> thanks,
> Charith
>
>>
>> Danushka
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Charith Dhanushka Wickramarachchi
> Software Engineer
> WSO2 Inc
> http://wso2.com/
> http://wso2.org/
>
> blog
> http://charithwiki.blogspot.com/
>
> twitter
> http://twitter.com/charithwiki
>
>
>
>
> ___
> 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] What is sqsAuthentication module?

[Danushka Menikkumbura]

Amila,

The question is why event has a compile-time dependency to the MessageBox.
It is because we support MessageBox as an event sink right?.

Danushka


On Fri, May 20, 2011 at 9:39 AM, Amila Suriarachchi  wrote:

>
>
> On Fri, May 20, 2011 at 7:34 AM, Sameera Jayasoma wrote:
>
>> It this module is optional let's remove it. Can make it available as an
>> feature.
>>
>
> This module is there with the AS and ESB and what any product which uses
> event because of an P2 issue.
>
> event has an compile time dependency to message box. Because of this when
> some one install event using P2 it copies the messagebox core jar file to
> plugins folder. This gives exceptions when event install to other products
> using P2.
>
> In order to fix this we have put a feature dependency (which copies the
> config files as well) from event to message box.
>
> other than this requirement there is no need to add message box to AS.
>
> thanks,
>  Amila.
>
>
>>
>> Thanks,
>> Sameera
>>
>> On Friday, May 20, 2011, Afkham Azeez  wrote:
>> > Which clearly shows that sqsAuth shud be removed from event
>> > On May 20, 2011 12:05 AM, "Danushka Menikkumbura" 
>> wrote:> This gets added as a result of installing event.
>> >>
>> >> On Fri, May 20, 2011 at 12:02 AM, Afkham Azeez  wrote:
>> >>
>> >>> Why do we need this in AS?
>> >>> On May 19, 2011 9:37 PM, "Charitha Kankanamge" 
>> wrote:
>> >>> > Hi,
>> >>> >it
>> >>> > I noticed a new module. "sqsAuthentication" in the module list i
>> >>> AppServer.
>> >>> > What is the purpose of this module? How are we supposed to use it?
>> >>> >
>> >>> > [image: module.png]
>> >>> >
>> >>> > /Charitha
>> >>>
>> >>> ___
>> >>> 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
>>
>
>
> ___
> 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] Using Sun proprietary APIs in carbon

[Danushka Menikkumbura]

>
> When using some application servers (i.e WebSphere, WebLogic), won't this be 
> an issue?
>
>
It should be an issue. I fixed a similar issue in Qpid last night.

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

Re: [Carbon-dev] Can't send/receive JMS Object Messages to/from Qpid broker from Carbon Environment.

[Danushka Menikkumbura]

>
> Problem is when i try to connect to a Qpid broker using our qpid client
> libs in the Carbon environment  it gives a Class not found Error when we try
> to de serialize the message back to the Original format.
>

What is the class that it complains about?

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

Re: [Carbon-dev] What is sqsAuthentication module?

[Danushka Menikkumbura]

The thing is you can also specify an SQS queue as an event sink.

On Fri, May 20, 2011 at 6:52 AM, Afkham Azeez  wrote:

> Which clearly shows that sqsAuth shud be removed from event
> On May 20, 2011 12:05 AM, "Danushka Menikkumbura" 
> wrote:
> > This gets added as a result of installing event.
> >
> > On Fri, May 20, 2011 at 12:02 AM, Afkham Azeez  wrote:
> >
> >> Why do we need this in AS?
> >> On May 19, 2011 9:37 PM, "Charitha Kankanamge" 
> wrote:
> >> > Hi,
> >> >
> >> > I noticed a new module. "sqsAuthentication" in the module list in
> >> AppServer.
> >> > What is the purpose of this module? How are we supposed to use it?
> >> >
> >> > [image: module.png]
> >> >
> >> > /Charitha
> >>
> >> ___
> >> 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] What is sqsAuthentication module?

[Danushka Menikkumbura]

This gets added as a result of installing event.

On Fri, May 20, 2011 at 12:02 AM, Afkham Azeez  wrote:

> Why do we need this in AS?
> On May 19, 2011 9:37 PM, "Charitha Kankanamge"  wrote:
> > Hi,
> >
> > I noticed a new module. "sqsAuthentication" in the module list in
> AppServer.
> > What is the purpose of this module? How are we supposed to use it?
> >
> > [image: module.png]
> >
> > /Charitha
>
> ___
> 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 errors when running on WAS 7.0.0.11

[Danushka Menikkumbura]

Fixed on the trunk.

Danushka

On Thu, May 19, 2011 at 6:03 AM, Ajith Vitharana  wrote:

> Hi all,
>
> I'm testing latest wso2greg-4.0.0-SNAPSHOT on WAS 7.0.0.11. (java version
> "1.6.0_24" , WindowsXp).
> I did not not encountered any broken pages, but when i trying to subscribe
> for a resource, following exception occurred.
> I noted that qpid start failed , because of the * 
> java.lang.NoClassDefFoundError:
> com/sun/security/auth/UserPrincipal*
> Plz check this with SystemOut.log.
>
>
> [5/16/11 16:32:27:687 IST] 0054 EventPublishe E
> org.wso2.carbon.event.core.internal.EventPublisher run Can not publish the
> message
>
> org.wso2.carbon.event.core.exception.EventBrokerException: Can not create
> topic connection
> at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.getTopicConnection(JMSDeliveryManager.java:76)
> at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.publish(JMSDeliveryManager.java:133)
> at
> org.wso2.carbon.event.core.internal.EventPublisher.run(EventPublisher.java:56)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:736)
> Caused by: javax.jms.JMSException: Error creating connection: Connection
> refused: connect
> at
> org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:286)
> at
> org.apache.qpid.client.AMQConnectionFactory.createTopicConnection(AMQConnectionFactory.java:345)
> at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.getTopicConnection(JMSDeliveryManager.java:70)
> ... 5 more
> Caused by: org.apache.qpid.AMQConnectionFailureException: Connection
> refused: connect
> at
> org.apache.qpid.AMQConnectionFailureException.(AMQConnectionFailureException.java:43)
> at org.apache.qpid.client.AMQConnection.(AMQConnection.java:472)
> at
> org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:276)
> ... 7 more
> Caused by: org.apache.qpid.transport.TransportException: Error connecting
> to broker
> at
> org.apache.qpid.transport.network.io.IoNetworkTransport.init(IoNetworkTransport.java:78)
> at
> org.apache.qpid.transport.TransportBuilder.init(TransportBuilder.java:44)
> at org.apache.qpid.transport.Connection.connect(Connection.java:240)
> at
> org.apache.qpid.client.AMQConnectionDelegate_0_10.makeBrokerConnection(AMQConnectionDelegate_0_10.java:184)
> at
> org.apache.qpid.client.AMQConnection.makeBrokerConnection(AMQConnection.java:617)
> at org.apache.qpid.client.AMQConnection.(AMQConnection.java:396)
> ... 8 more
> Caused by: java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:352)
> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:214)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:201)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:378)
> at java.net.Socket.connect(Socket.java:537)
> at java.net.Socket.connect(Socket.java:487)
> at
> org.apache.qpid.transport.network.io.IoNetworkTransport.init(IoNetworkTransport.java:74)
> ... 13 more
>
> Thanks
> Ajithn
>
> ___
> 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] One feature to install all ESB related features

[Danushka Menikkumbura]

Should not the feature manager take care of installing dependencies?

Danushka

On Thu, May 19, 2011 at 1:46 PM, Kasun Indrasiri  wrote:

> Hi devs,
>
> We came across couple of issues while we were installing ESB features on a
> raw carbon server. Most of the esb features currently available are unusable
> with out installing  some other related feature. For instance:
>
> - proxyadmin-feature requires service hosting, sequence admin, mediator,
> template features to get the proxy service working.
> - sequence-feature editor requires template feature. Also its useless with
> out the endpoint feature.
>
> Likewise there are couple of cases where we need to install some related
> features to get the thing done. To overcome these issues, we have created a
> single feature(ESB Mediation : features/esb-mediation) to install all esb
> related features on a carbon server. This feature basically includes all the
> related esb features. Ideally, we have to get rid of all the features that
> cannot function alone.
>
> Thanks.
> --
> Kasun Indrasiri
> Senior Software Engineer
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/
>
> ___
> 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] Console message while using WSDL Validator

[Danushka Menikkumbura]

Any idea why this message is printed?

Retrieving document at
'file:/home/danushka/development/carbon/trunk/products/mb/modules/distribution/product/target/wso2mb-1.0.0-SNAPSHOT/tmp/temp2840560090810745821.txt'.
Retrieving schema at 'http://schemas.xmlsoap.org/soap/envelope/', relative
to
'file:/home/danushka/development/carbon/trunk/products/mb/modules/distribution/product/target/wso2mb-1.0.0-SNAPSHOT/tmp/temp2840560090810745821.txt'.

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

Re: [Carbon-dev] Context root disappearing in Websphere

[Danushka Menikkumbura]

This should be a Carbon-core level fix right?.

Danushka

On Mon, May 16, 2011 at 3:16 AM, Ranga Siriwardena  wrote:

> Hi all,
>
> I was able to reproduce the issue for GS. Will work with Milinda to sorted
> out the issue.
>
> Thanks.
>
> On Thu, May 12, 2011 at 3:38 PM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi all,
>>
>> The same issue [1] has been raised sometime back and it has been resolved
>> without doing a proper fix.
>>
>> Thanks
>> Krishantha
>>
>> [1] https://wso2.org/jira/browse/CARBON-7371
>>
>>
>> On Thu, May 12, 2011 at 2:21 PM, Nuwan Bandara  wrote:
>>
>>> Surprisingly this does not happen in other app servers (Tomcat etc),
>>> according to pradeep he has seen this when there are relative URLs, But
>>> there are many places in our UI bundles that we do redirection to relative
>>> URLs.
>>>
>>> Regards,
>>> /Nuwan
>>>
>>>
>>> On Thu, May 12, 2011 at 2:15 PM, Milinda Pathirage wrote:
>>>
 This could be due to recent changes we done to facilitate custom home
 page URLs. Will look into this.

 Thanks
 Milinda

 On Thu, May 12, 2011 at 1:56 PM, Chamara Ariyarathne >>> > wrote:

> Following are the places which Browser redirect with wrong context root
> when server deployed in Websphere. I'm sending this for the request made 
> by
> Pradeep and Nuwan, and according to the offline chat I had with them, 
> there
> will be a similar solution for this.
>
> *Mashup Server;*
> Home button
> Upload Module; Modules -> Add Modules -> Upoload
> Upload JavaScript services -> Upload
> *
> Gadget Server;*
> Add Gadgets
>
>
> *Chamara Ariyarathne*
> Software Engineer - QA;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; *0772786766*
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


 --
 Milinda Pathirage
 Technical Lead and Product Manager, Business Process Server - WSO2 Inc;
 http://wso2.com
 Blog: http://blog.mpathirage.com

 Lean Enterprise Middleware

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


>>>
>>>
>>> --
>>> *Thanks & Regards,
>>>
>>> Nuwan Bandara
>>> Senior Software Engineer
>>>
>>> WSO2 Inc. | http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> http://nuwan.bandara.co
>>> *
>>> 
>>>
>>> ___
>>> 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
>>
>>
>
>
> --
> Ranga Siriwardena
> Software Engineer
> WSO2 Inc.
>
> Blog: http://rangasiriwardena.blogspot.com/
>
>
> ___
> 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] Please assign issues to relevant products/components/people

[Danushka Menikkumbura]

I just ran through open JIRA's that were created during last couple of days
and assigned ones which should be looked into by the Event team. Respective
PM's please assign issues that are not intended to be handled by your team
as soon as you see them so that relevant teams can act on them quickly.

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

Re: [Carbon-dev] Eventing Core has no any source-code

[Danushka Menikkumbura]

Eventing is no more.

Danushka

On Sat, May 14, 2011 at 4:18 PM, Denis Weerasiri  wrote:

> Hi,
> FYI, This component[1] export org.wso2.eventing.* but it has no any source
> code.
>
> [1] -
> http://svn.wso2.org/repos/wso2/trunk/carbon/components/eventing/org.wso2.carbon.eventing.core/
>
> --
> Thanks,
> Denis
> --
> *Denis Weerasiri*
> Software Engineer; WSO2 Inc.; http://wso2.com,
> *email: denis ** [AT] wso2.com* 
> *
> blog: **http://ddweerasiri.blogspot.com*
> *
> twitter: **http://twitter.com/ddweerasiri*
> *
> linked-in: 
> **http://lk.linkedin.com/in/ddweerasiri*
>
>
> ___
> 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 compilation error

[Danushka Menikkumbura]

I can compile without any issue. What is the JDK version that you are
compiling with?

Danushka

On Fri, May 13, 2011 at 1:43 AM, Afkham Azeez  wrote:

> compile:
>  [echo] Targeting : 1.5
> [javac] Compiling 7 source files to
> /Users/azeez/projects/wso2/org/trunk/carbon/dependencies/qpid/java/build/scratch/broker/classes
> [javac]
> /Users/azeez/projects/wso2/org/trunk/carbon/dependencies/qpid/java/broker/src/main/java/org/apache/qpid/server/transport/ServerConnection.java:352:
> closed() is already defined in
> org.apache.qpid.server.transport.ServerConnection
> [javac] public void closed() {
> [javac] ^
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 1 error
> [INFO]
> 
> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] An Ant BuildException has occured: The following error occurred
> while executing this line:
> /Users/azeez/projects/wso2/org/trunk/carbon/dependencies/qpid/java/build.xml:159:
> The following error occurred while executing this line:
> /Users/azeez/projects/wso2/org/trunk/carbon/dependencies/qpid/java/build.xml:58:
> The following error occurred while executing this line:
> /Users/azeez/projects/wso2/org/trunk/carbon/dependencies/qpid/java/module.xml:259:
> Compile failed; see the compiler error output for details.
>
>
> --
> *Afkham Azeez*
> Director of Architecture; 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
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Found another critical issue in Qpid

[Danushka Menikkumbura]

Figured it out.

So the connection has a root mutex that is held by it's child objects such
as sessions, producers and consumers. When a session closes in this our
case, it locks the root mutex and then notifies the connection that an
exception (i.e. unauthorized operation) has occurred. Following that, the
connection tries to carry out some tasks (see next para) and for that it
needs to lock the same mutex and hence the deadlock.

What the connection tries to do upon exception notification is to decide if
the error is a "hard error" which always returns true (ironically) and then
tries to close all sessions and eventually the connection. Now that is a
different bug as what we get is a session-level exception (i.e. a publisher
in a session is not authorized to do some operation) and it is wrong to
close all other sessions and subsequently the connection as a result of
that.

I am going to check on this on the dev list. Will keep this thread updated.

Danushka

On Wed, May 11, 2011 at 4:34 PM, Danushka Menikkumbura wrote:

> Qpid client hangs while trying to close JMS session when its operation
> (publish/subscribe) is unauthorised on server side. The issue is that it
> does not receive connection close commands (AMQP frames) in this case and
> hence goes into a wait state.
>
> It was found while fixing [1].
>
> I am looking into the issue and will keep updated.
>
> [1] - https://wso2.org/jira/browse/CARBON-8942
>
> Thanks,
> Danushka
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Unnecessary log messages when shutting down - MB

[Danushka Menikkumbura]

Removed two log4j logs and committed but yet to find where the other two
system outs are coming from.

Danushka

On Fri, May 13, 2011 at 1:12 AM, Afkham Azeez  wrote:

> [2011-05-13 01:16:47,997]  INFO
> {org.wso2.carbon.messagebox.internal.ds.MessageBoxServiceComponent} -
>  MessageBoxService bundle is activated successfully
>
>
>
> On Fri, May 13, 2011 at 1:11 AM, Afkham Azeez  wrote:
>
>> [2011-05-13 01:15:30,923]  INFO
>> {org.wso2.carbon.messagebox.internal.ds.MessageBoxServiceComponent} -
>>  MessageBoxService bundle is deactivated
>> ** Unregister subscription called
>> + Removed sub:
>> org.apache.qpid.server.subscription.Subscription_0_10@5182e1ac
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; 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*
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; 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
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Found another critical issue in Qpid

[Danushka Menikkumbura]

Qpid client hangs while trying to close JMS session when its operation
(publish/subscribe) is unauthorised on server side. The issue is that it
does not receive connection close commands (AMQP frames) in this case and
hence goes into a wait state.

It was found while fixing [1].

I am looking into the issue and will keep updated.

[1] - https://wso2.org/jira/browse/CARBON-8942

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

Re: [Carbon-dev] Issues when ESB is deployed behind an HTTP/HTTPS proxy

[Danushka Menikkumbura]

>
> - HTTPS tunneling does not work
>

If I am not mistaken this was raised as a support issue and was fixed. It
was Rajika IIRC.

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

Re: [Carbon-dev] Why print Carbon home and Java home at server start up?

[Danushka Menikkumbura]

I think we should have a start up option to display them rather than showing
them all the time.

Danushka

On Tue, May 10, 2011 at 5:38 PM, Afkham Azeez  wrote:

> Why not?
>
> This has been added because people have been coming to me from time to time
> showing various weird errors, which resulted in many wasted hours. The root
> cause was CARBON_HOME has been set to something else in their bash_profile
> files.
>
>
> On Tue, May 10, 2011 at 5:08 PM, Danushka Menikkumbura 
> wrote:
>
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * <http://www.apache.org/>**
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
> twitter: **http://twitter.com/afkham_azeez*<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
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Why print Carbon home and Java home at server start up?

[Danushka Menikkumbura]

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

Re: [Carbon-dev] "WSO2 Carbon Continuous Build has FAILED"

[Danushka Menikkumbura]

>
> SVN client can be really buggy. I have experienced the code not getting
> updated, despite the fact that the SVN client says the code is up to date.
> In such situations, I have had to get a new checkout.
>

+1.

I have similar experience too.

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

Re: [Carbon-dev] Use of CarbonJNDIContext with LDAP, JMS

[Danushka Menikkumbura]

Amila,

Shall we make the property name something generic?

org.wso2.carbon.context.RequestBaseContext instead of
org.wso2.carbon.ldap.RequestBaseContext?

Thanks,
Danushka

On Tue, May 10, 2011 at 11:26 AM, Amila Jayasekara  wrote:

> Hi All,
>
> As per yesterdays discussion on "CarbonJNDIContext" we came to
> following conclusion.
>
> If there is a JNDI provider which needs additional functionality than
> specified in CarbonInitialJNDIContext, we have to work with the base
> initial context. Inorder to make CarbonInitialJNDIContext to return
> base JNDI context, calling code has to set following property,
>
> "org.wso2.carbon.ldap.RequestBaseContext" - if this property is set in
> the environment properties given to InitialContext,
> CarbonInitialJNDIContext will return the base context. Property is
> also defined as a CarbonConstant.
>
> E.g :-
>
> environment = new Hashtable();
> 
> 
> environment.put(CarbonConstants.REQUEST_BASE_CONTEXT, "true");
> context = new InitialDirContext(environment);
>
> Changes are commited to trunk.
> Please let me know if you face any issues, with this regard.
>
> Thank you
> AmilaJ
> ___
> 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 and Derby Issues

[Danushka Menikkumbura]

Done.

https://wso2.org/jira/browse/CARBON-9751

Thanks,
Danushka

On Mon, May 9, 2011 at 1:58 PM, Paul Fremantle  wrote:

> Danushka
>
> Please raise a JIRA to make sure we fix this properly next release.
>
> Thanks
> Paul
>
>
> On 9 May 2011 09:20, Hiranya Jayathilaka  wrote:
>
>>
>>
>> On Mon, May 9, 2011 at 1:15 PM, Danushka Menikkumbura 
>> wrote:
>>
>>> Please update orbit/qpid/pom.xml and build. Replace your
>>> components/plugins/qpid-0.11.0.wso2v1.jar with the newly built qpid orbit
>>> bundle.
>>>
>>
>> Seems to be fine now. Thanks for looking into this.
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Danushka
>>>
>>>
>>> On Mon, May 9, 2011 at 1:06 PM, Hiranya Jayathilaka wrote:
>>>
>>>>
>>>>
>>>> On Mon, May 9, 2011 at 12:23 PM, Danushka Menikkumbura <
>>>> danus...@wso2.com> wrote:
>>>>
>>>>> Hi Hiranya,
>>>>>
>>>>> Just had a chat with Sameera. If the self-contained bundle has an
>>>>> explicit rule not to import whichever embedded, it should not get wired to
>>>>> external bundles. Shall we try that out and see?. Ideally we should have a
>>>>> single Derby bundle but I am little reluctant to do changes to Qpid due to
>>>>> obvious reasons ;-).
>>>>>
>>>>
>>>> Ok let's give this a try then. Let me know when the Orbit bundle is
>>>> updated.
>>>>
>>>> Thanks,
>>>> Hiranya
>>>>
>>>>
>>>>>
>>>>> Thanks,
>>>>> Danushka
>>>>>
>>>>>
>>>>> On Mon, May 9, 2011 at 11:55 AM, Hiranya Jayathilaka >>>> > wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, May 9, 2011 at 11:49 AM, Danushka Menikkumbura <
>>>>>> danus...@wso2.com> wrote:
>>>>>>
>>>>>>> Even when the self-contained bundle does not import packages that are
>>>>>>> embedded?
>>>>>>>
>>>>>>
>>>>>> Seems that's the case. May be Sameera can explain this better?
>>>>>>
>>>>>> Thanks,
>>>>>> Hiranya
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Danushka
>>>>>>>
>>>>>>>
>>>>>>> On Mon, May 9, 2011 at 11:44 AM, Hiranya Jayathilaka <
>>>>>>> hira...@wso2.com> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, May 9, 2011 at 11:42 AM, Danushka Menikkumbura <
>>>>>>>> danus...@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> +1.
>>>>>>>>>
>>>>>>>>> I wonder why the Qpid bundle gets wired to the other Derby lib
>>>>>>>>> instead of which is embedded?
>>>>>>>>>
>>>>>>>>
>>>>>>>> I had a chat with Sameera about this. Apparently that's the normal
>>>>>>>> OSGi behavior. Packages exported by other bundles get precedence over
>>>>>>>> private packages.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Hiranya
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Danushka
>>>>>>>>>
>>>>>>>>> On Mon, May 9, 2011 at 11:37 AM, Hiranya Jayathilaka <
>>>>>>>>> hira...@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> I think the right solution is to introduce a separate Derby bundle
>>>>>>>>>> (currently it's embedded in qpid). This bundle should contain 
>>>>>>>>>> everything
>>>>>>>>>> needed for Qpid and ESB samples.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Hiranya
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, May 9, 2011 at 11:35 AM, Hiranya Jayathilaka <
>>>>>>>>>&g

Re: [Carbon-dev] Qpid and Derby Issues

[Danushka Menikkumbura]

Please update orbit/qpid/pom.xml and build. Replace your
components/plugins/qpid-0.11.0.wso2v1.jar with the newly built qpid orbit
bundle.

Danushka

On Mon, May 9, 2011 at 1:06 PM, Hiranya Jayathilaka wrote:

>
>
> On Mon, May 9, 2011 at 12:23 PM, Danushka Menikkumbura 
> wrote:
>
>> Hi Hiranya,
>>
>> Just had a chat with Sameera. If the self-contained bundle has an explicit
>> rule not to import whichever embedded, it should not get wired to external
>> bundles. Shall we try that out and see?. Ideally we should have a single
>> Derby bundle but I am little reluctant to do changes to Qpid due to obvious
>> reasons ;-).
>>
>
> Ok let's give this a try then. Let me know when the Orbit bundle is
> updated.
>
> Thanks,
> Hiranya
>
>
>>
>> Thanks,
>> Danushka
>>
>>
>> On Mon, May 9, 2011 at 11:55 AM, Hiranya Jayathilaka wrote:
>>
>>>
>>>
>>> On Mon, May 9, 2011 at 11:49 AM, Danushka Menikkumbura <
>>> danus...@wso2.com> wrote:
>>>
>>>> Even when the self-contained bundle does not import packages that are
>>>> embedded?
>>>>
>>>
>>> Seems that's the case. May be Sameera can explain this better?
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>
>>>>
>>>> Danushka
>>>>
>>>>
>>>> On Mon, May 9, 2011 at 11:44 AM, Hiranya Jayathilaka 
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Mon, May 9, 2011 at 11:42 AM, Danushka Menikkumbura <
>>>>> danus...@wso2.com> wrote:
>>>>>
>>>>>> +1.
>>>>>>
>>>>>> I wonder why the Qpid bundle gets wired to the other Derby lib instead
>>>>>> of which is embedded?
>>>>>>
>>>>>
>>>>> I had a chat with Sameera about this. Apparently that's the normal OSGi
>>>>> behavior. Packages exported by other bundles get precedence over private
>>>>> packages.
>>>>>
>>>>> Thanks,
>>>>> Hiranya
>>>>>
>>>>>
>>>>>>
>>>>>> Danushka
>>>>>>
>>>>>> On Mon, May 9, 2011 at 11:37 AM, Hiranya Jayathilaka <
>>>>>> hira...@wso2.com> wrote:
>>>>>>
>>>>>>> I think the right solution is to introduce a separate Derby bundle
>>>>>>> (currently it's embedded in qpid). This bundle should contain everything
>>>>>>> needed for Qpid and ESB samples.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Hiranya
>>>>>>>
>>>>>>>
>>>>>>> On Mon, May 9, 2011 at 11:35 AM, Hiranya Jayathilaka <
>>>>>>> hira...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> We are having some issues testing the DB mediator samples in ESB
>>>>>>>> (with Derby). When we deploy derby client libraries to the ESB, Qpid
>>>>>>>> component fails. Reason is when we deploy derby libraries to the ESB, 
>>>>>>>> the
>>>>>>>> qpid component gets wired to that instead of the embedded derby 
>>>>>>>> binaries.
>>>>>>>> Any idea how to fix this?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> --
>>>>>>>> Hiranya Jayathilaka
>>>>>>>> Senior Software Engineer;
>>>>>>>> WSO2 Inc.;  http://wso2.org
>>>>>>>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>>>>>>>> Blog: http://techfeast-hiranya.blogspot.com
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Hiranya Jayathilaka
>>>>>>> Senior Software Engineer;
>>>>>>> WSO2 Inc.;  http://wso2.org
>>>>>>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>>>>>>> Blog: http://techfeast-hiranya.blogspot.com
>>>>>>>
>>>>>>> ___
>>>>>>> Carbon-dev mailing list
>>>>>>> Carbon-dev@wso2.org
>>>>>&g

Re: [Carbon-dev] Qpid and Derby Issues

[Danushka Menikkumbura]

Hi Hiranya,

Just had a chat with Sameera. If the self-contained bundle has an explicit
rule not to import whichever embedded, it should not get wired to external
bundles. Shall we try that out and see?. Ideally we should have a single
Derby bundle but I am little reluctant to do changes to Qpid due to obvious
reasons ;-).

Thanks,
Danushka

On Mon, May 9, 2011 at 11:55 AM, Hiranya Jayathilaka wrote:

>
>
> On Mon, May 9, 2011 at 11:49 AM, Danushka Menikkumbura 
> wrote:
>
>> Even when the self-contained bundle does not import packages that are
>> embedded?
>>
>
> Seems that's the case. May be Sameera can explain this better?
>
> Thanks,
> Hiranya
>
>
>>
>> Danushka
>>
>>
>> On Mon, May 9, 2011 at 11:44 AM, Hiranya Jayathilaka wrote:
>>
>>>
>>>
>>> On Mon, May 9, 2011 at 11:42 AM, Danushka Menikkumbura <
>>> danus...@wso2.com> wrote:
>>>
>>>> +1.
>>>>
>>>> I wonder why the Qpid bundle gets wired to the other Derby lib instead
>>>> of which is embedded?
>>>>
>>>
>>> I had a chat with Sameera about this. Apparently that's the normal OSGi
>>> behavior. Packages exported by other bundles get precedence over private
>>> packages.
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>
>>>>
>>>> Danushka
>>>>
>>>> On Mon, May 9, 2011 at 11:37 AM, Hiranya Jayathilaka 
>>>> wrote:
>>>>
>>>>> I think the right solution is to introduce a separate Derby bundle
>>>>> (currently it's embedded in qpid). This bundle should contain everything
>>>>> needed for Qpid and ESB samples.
>>>>>
>>>>> Thanks,
>>>>> Hiranya
>>>>>
>>>>>
>>>>> On Mon, May 9, 2011 at 11:35 AM, Hiranya Jayathilaka >>>> > wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> We are having some issues testing the DB mediator samples in ESB (with
>>>>>> Derby). When we deploy derby client libraries to the ESB, Qpid component
>>>>>> fails. Reason is when we deploy derby libraries to the ESB, the qpid
>>>>>> component gets wired to that instead of the embedded derby binaries. Any
>>>>>> idea how to fix this?
>>>>>>
>>>>>> Thanks
>>>>>> --
>>>>>> Hiranya Jayathilaka
>>>>>> Senior Software Engineer;
>>>>>> WSO2 Inc.;  http://wso2.org
>>>>>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>>>>>> Blog: http://techfeast-hiranya.blogspot.com
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Hiranya Jayathilaka
>>>>> Senior Software Engineer;
>>>>> WSO2 Inc.;  http://wso2.org
>>>>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>>>>> Blog: http://techfeast-hiranya.blogspot.com
>>>>>
>>>>> ___
>>>>> 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
>>>>
>>>>
>>>
>>>
>>> --
>>> Hiranya Jayathilaka
>>> Senior Software Engineer;
>>> WSO2 Inc.;  http://wso2.org
>>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>>> Blog: http://techfeast-hiranya.blogspot.com
>>>
>>> ___
>>> 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
>>
>>
>
>
> --
> Hiranya Jayathilaka
> Senior Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> ___
> 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 and Derby Issues

[Danushka Menikkumbura]

Even when the self-contained bundle does not import packages that are
embedded?

Danushka

On Mon, May 9, 2011 at 11:44 AM, Hiranya Jayathilaka wrote:

>
>
> On Mon, May 9, 2011 at 11:42 AM, Danushka Menikkumbura 
> wrote:
>
>> +1.
>>
>> I wonder why the Qpid bundle gets wired to the other Derby lib instead of
>> which is embedded?
>>
>
> I had a chat with Sameera about this. Apparently that's the normal OSGi
> behavior. Packages exported by other bundles get precedence over private
> packages.
>
> Thanks,
> Hiranya
>
>
>>
>> Danushka
>>
>> On Mon, May 9, 2011 at 11:37 AM, Hiranya Jayathilaka wrote:
>>
>>> I think the right solution is to introduce a separate Derby bundle
>>> (currently it's embedded in qpid). This bundle should contain everything
>>> needed for Qpid and ESB samples.
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>
>>> On Mon, May 9, 2011 at 11:35 AM, Hiranya Jayathilaka 
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> We are having some issues testing the DB mediator samples in ESB (with
>>>> Derby). When we deploy derby client libraries to the ESB, Qpid component
>>>> fails. Reason is when we deploy derby libraries to the ESB, the qpid
>>>> component gets wired to that instead of the embedded derby binaries. Any
>>>> idea how to fix this?
>>>>
>>>> Thanks
>>>> --
>>>> Hiranya Jayathilaka
>>>> Senior Software Engineer;
>>>> WSO2 Inc.;  http://wso2.org
>>>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>>>> Blog: http://techfeast-hiranya.blogspot.com
>>>>
>>>
>>>
>>>
>>> --
>>> Hiranya Jayathilaka
>>> Senior Software Engineer;
>>> WSO2 Inc.;  http://wso2.org
>>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>>> Blog: http://techfeast-hiranya.blogspot.com
>>>
>>> ___
>>> 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
>>
>>
>
>
> --
> Hiranya Jayathilaka
> Senior Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> ___
> 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 and Derby Issues

[Danushka Menikkumbura]

+1.

I wonder why the Qpid bundle gets wired to the other Derby lib instead of
which is embedded?

Danushka

On Mon, May 9, 2011 at 11:37 AM, Hiranya Jayathilaka wrote:

> I think the right solution is to introduce a separate Derby bundle
> (currently it's embedded in qpid). This bundle should contain everything
> needed for Qpid and ESB samples.
>
> Thanks,
> Hiranya
>
>
> On Mon, May 9, 2011 at 11:35 AM, Hiranya Jayathilaka wrote:
>
>> Hi,
>>
>> We are having some issues testing the DB mediator samples in ESB (with
>> Derby). When we deploy derby client libraries to the ESB, Qpid component
>> fails. Reason is when we deploy derby libraries to the ESB, the qpid
>> component gets wired to that instead of the embedded derby binaries. Any
>> idea how to fix this?
>>
>> Thanks
>> --
>> Hiranya Jayathilaka
>> Senior Software Engineer;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>
>
>
> --
> Hiranya Jayathilaka
> Senior Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> ___
> 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] Events are not getting published in latest packs due to qpid error

[Danushka Menikkumbura]

It still logs an error.

On Sat, May 7, 2011 at 8:02 AM, Amila Suriarachchi  wrote:

>
>
> On Sat, May 7, 2011 at 6:23 AM, Danushka Menikkumbura 
> wrote:
>
>> Hi Amila,
>>
>> I think there was some miscommunication. Supun, correct me if I am wrong.
>>
>> Anyway I have now handled NPE in the Qpid code too.
>>
>
> If the reason what I have given is correct please revert this change. This
> may lead to such wrong invocations gone undetected.
>
> thanks,
> Amila.
>
>
>>
>> But still I wonder how the Qpid call passes a -1. See the code snippet
>> given below. This was done last week when we tested MB Stratos version.
>>
>> // Get tenant ID
>> int tenantID = 0;
>> int domainNameSeparatorIndex =
>> username.indexOf(DOMAIN_NAME_SEPARATOR);
>> if (-1 != domainNameSeparatorIndex) { // Service case
>> String domainName =
>> username.substring(domainNameSeparatorIndex + 1);
>> tenantID =
>> realmService.getTenantManager().getTenantId(domainName);
>> }
>>
>> // Get Realm
>> userRealm = realmService.getTenantUserRealm(tenantID);
>>
>> Thanks,
>> Danushka
>>
>>
>> On Sat, May 7, 2011 at 2:32 AM, Amila Jayasekara  wrote:
>>
>>> Hi Danushka,
>>>
>>> I did bit of debugging with the ESB pack i got from Supun and found
>>> following.
>>>
>>> The tenant id passed to DefaultRealmService.getTenantUserRealm from
>>> QpidAuthorizationPlugin.getUserRealm is -1. Thus according to
>>> DefaultRealmService.getTenantUserRealm logic the tenant id -1 does not
>>> have a special meaning and also it is not representing a normal
>>> tenant. Since RealmService cannot find the appropriate tenant when
>>> trying to retrieve Realm it gives a null pointer exception.
>>>
>>> I believe what you actually need is super tenant realm (Since this is
>>> running in stand alone mode). You need to pass 0 instead of -1.
>>>
>>> I will add a null check to tenant, before getting RealmService; to
>>> give a descriptive error message.
>>>
>>> Thanks
>>> AmilaJ
>>>
>>>
>>> On Sat, May 7, 2011 at 2:05 AM, Amila Jayasekara 
>>> wrote:
>>> > On Fri, May 6, 2011 at 8:12 PM, Danushka Menikkumbura <
>>> danus...@wso2.com> wrote:
>>> > AmilaJ fixed the issue in DefaultRealmService as I heard.
>>> >
>>> > Hi Danushka,
>>> >
>>> > I didnt do any modifications to DefaultRealmService with this regard.
>>> > Similar error was reported in "[Carbon-dev] QPid exception when trying
>>> > to invoke an admin service" mail thread.
>>> > But later in the same thread you informed the issue was not
>>> > reproducible with a fresh installation.
>>> >
>>> > Let me again investigate the pack i got from Supun.
>>> >
>>> > Thanks
>>> > AmilaJ
>>> >
>>> >>
>>> >> Danushka
>>> >>
>>> >> On Fri, May 6, 2011 at 5:18 PM, Tharindu Mathew 
>>> wrote:
>>> >>>
>>> >>> Hi,
>>> >>> We came up with this during smoke tests. Events published by ESB are
>>> not
>>> >>> being received by BAM due to this. I believe it's due to the qpid
>>> error.
>>> >>> Please have a look.
>>> >>> Stacktrace:
>>> >>> [2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload
>>> >>> >> >>> xmlns:svrusrdata="
>>> http://wso2.org/ns/2009/09/bam/server/user-defined/data
>>> ">
>>> https://10.100.0.191:9444
>>> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>>> >>> [2011-05-06 17:04:35,518] DEBUG - BAMMediationStatisticsObserver
>>> >>> ComponentType.PROXYSERVICE >> >>> xmlns:svrusrdata="
>>> http://wso2.org/ns/2009/09/bam/server/user-defined/data
>>> ">
>>> https://10.100.0.191:9444
>>> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27Prox

Re: [Carbon-dev] Events are not getting published in latest packs due to qpid error

[Danushka Menikkumbura]

Hi Amila,

I think there was some miscommunication. Supun, correct me if I am wrong.

Anyway I have now handled NPE in the Qpid code too.

But still I wonder how the Qpid call passes a -1. See the code snippet given
below. This was done last week when we tested MB Stratos version.

// Get tenant ID
int tenantID = 0;
int domainNameSeparatorIndex =
username.indexOf(DOMAIN_NAME_SEPARATOR);
if (-1 != domainNameSeparatorIndex) { // Service case
String domainName =
username.substring(domainNameSeparatorIndex + 1);
tenantID =
realmService.getTenantManager().getTenantId(domainName);
}

// Get Realm
userRealm = realmService.getTenantUserRealm(tenantID);

Thanks,
Danushka

On Sat, May 7, 2011 at 2:32 AM, Amila Jayasekara  wrote:

> Hi Danushka,
>
> I did bit of debugging with the ESB pack i got from Supun and found
> following.
>
> The tenant id passed to DefaultRealmService.getTenantUserRealm from
> QpidAuthorizationPlugin.getUserRealm is -1. Thus according to
> DefaultRealmService.getTenantUserRealm logic the tenant id -1 does not
> have a special meaning and also it is not representing a normal
> tenant. Since RealmService cannot find the appropriate tenant when
> trying to retrieve Realm it gives a null pointer exception.
>
> I believe what you actually need is super tenant realm (Since this is
> running in stand alone mode). You need to pass 0 instead of -1.
>
> I will add a null check to tenant, before getting RealmService; to
> give a descriptive error message.
>
> Thanks
> AmilaJ
>
>
> On Sat, May 7, 2011 at 2:05 AM, Amila Jayasekara  wrote:
> > On Fri, May 6, 2011 at 8:12 PM, Danushka Menikkumbura 
> wrote:
> > AmilaJ fixed the issue in DefaultRealmService as I heard.
> >
> > Hi Danushka,
> >
> > I didnt do any modifications to DefaultRealmService with this regard.
> > Similar error was reported in "[Carbon-dev] QPid exception when trying
> > to invoke an admin service" mail thread.
> > But later in the same thread you informed the issue was not
> > reproducible with a fresh installation.
> >
> > Let me again investigate the pack i got from Supun.
> >
> > Thanks
> > AmilaJ
> >
> >>
> >> Danushka
> >>
> >> On Fri, May 6, 2011 at 5:18 PM, Tharindu Mathew 
> wrote:
> >>>
> >>> Hi,
> >>> We came up with this during smoke tests. Events published by ESB are
> not
> >>> being received by BAM due to this. I believe it's due to the qpid
> error.
> >>> Please have a look.
> >>> Stacktrace:
> >>> [2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload
> >>>  >>> xmlns:svrusrdata="
> http://wso2.org/ns/2009/09/bam/server/user-defined/data
> ">
> https://10.100.0.191:9444
> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
> >>> [2011-05-06 17:04:35,518] DEBUG - BAMMediationStatisticsObserver
> >>> ComponentType.PROXYSERVICE  >>> xmlns:svrusrdata="
> http://wso2.org/ns/2009/09/bam/server/user-defined/data
> ">
> https://10.100.0.191:9444
> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
> >>> [2011-05-06 17:04:35,528] DEBUG - BAMMediationStatisticsObserver Event
> is
> >>> published >>> xmlns:svrusrdata="
> http://wso2.org/ns/2009/09/bam/server/user-defined/data
> ">
> https://10.100.0.191:9444
> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
> >>> [2011-05-06 17:04:35,597] ERROR - DefaultRealmService
> >>> java.lang.NullPointerException
> >>> at
> >>>
> org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:157)
> >>> at
> >>>
> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.getUserRealm(QpidAuthorizationPlugin.java:184)
> >>> at
> >>>
> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:124)
> >>> at
> >>>
> org.apache.qpid.se

Re: [Carbon-dev] Events are not getting published in latest packs due to qpid error

[Danushka Menikkumbura]

I do not think event has anything to do with this error.

Danushka

On Fri, May 6, 2011 at 11:01 PM, Amila Suriarachchi  wrote:

> have you updated the event core with the current trunk or are you working
> with some old ESB build?
>
> thanks,
> Amila.
>
> On Fri, May 6, 2011 at 5:18 PM, Tharindu Mathew  wrote:
>
>> Hi,
>>
>> We came up with this during smoke tests. Events published by ESB are not
>> being received by BAM due to this. I believe it's due to the qpid error.
>> Please have a look.
>>
>> Stacktrace:
>>
>> [2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload
>> http://wso2.org/ns/2009/09/bam/server/user-defined/data
>> ">
>> https://10.100.0.191:9444
>> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>> [2011-05-06 17:04:35,518] DEBUG - BAMMediationStatisticsObserver
>> ComponentType.PROXYSERVICE http://wso2.org/ns/2009/09/bam/server/user-defined/data
>> ">
>> https://10.100.0.191:9444
>> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>> [2011-05-06 17:04:35,528] DEBUG - BAMMediationStatisticsObserver Event is
>> publishedhttp://wso2.org/ns/2009/09/bam/server/user-defined/data
>> ">
>> https://10.100.0.191:9444
>> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>> [2011-05-06 17:04:35,597] ERROR - DefaultRealmService
>> java.lang.NullPointerException
>> at
>> org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:157)
>>  at
>> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.getUserRealm(QpidAuthorizationPlugin.java:184)
>> at
>> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:124)
>>  at
>> org.apache.qpid.server.security.SecurityManager$11.allowed(SecurityManager.java:390)
>> at
>> org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245)
>>  at
>> org.apache.qpid.server.security.SecurityManager.authorisePublish(SecurityManager.java:386)
>> at
>> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:307)
>>  at
>> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:96)
>> at
>> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108)
>>  at
>> org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50)
>> at
>> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:112)
>>  at
>> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:96)
>> at org.apache.qpid.transport.Method.delegate(Method.java:159)
>>  at org.apache.qpid.transport.Session.received(Session.java:500)
>> at org.apache.qpid.transport.Connection.dispatch(Connection.java:404)
>>  at
>> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64)
>> at
>> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40)
>>  at
>> org.apache.qpid.transport.MethodDelegate.messageTransfer(MethodDelegate.java:113)
>> at
>> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108)
>>  at
>> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54)
>> at
>> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40)
>>  at org.apache.qpid.transport.Method.delegate(Method.java:159)
>> at org.apache.qpid.transport.Connection.received(Connection.java:369)
>>  at
>> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:196)
>> at
>> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:53)
>>  at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:95)
>> at
>> org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:217)
>>  at org.apache.qpid.transport.network.Assembler.frame(Assembler.java:129)
>> at org.apache.qpid.transport.network.Frame.delegate(Frame.java:133)
>>  at
>> org.apache.qpid.transport.network.Assembler.received(Assembler.java:100)
>> at org.apache.qpid.transport.network.Assembler.received(Assembler.java:42)
>>  at
>> org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:187)
>> at
>> org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:103)
>>  at
>> org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:42)
>> at
>> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngin

Re: [Carbon-dev] Events are not getting published in latest packs due to qpid error

[Danushka Menikkumbura]

Tharindu,

I just checked the DefaultDealmService.java but did not see any change.
Probably the fix went to some other place. Anyway the qpid authz plugin now
handles NPE. So, just update components/qpid and rebuild the BAM.

Thanks,
Danushka

On Fri, May 6, 2011 at 8:22 PM, Afkham Azeez  wrote:

> Tharindu, please do whatever it takes to get a BAM pack ready today.
>
> On Fri, May 6, 2011 at 5:18 PM, Tharindu Mathew  wrote:
>
>> Hi,
>>
>> We came up with this during smoke tests. Events published by ESB are not
>> being received by BAM due to this. I believe it's due to the qpid error.
>> Please have a look.
>>
>> Stacktrace:
>>
>> [2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload
>> http://wso2.org/ns/2009/09/bam/server/user-defined/data
>> ">
>> https://10.100.0.191:9444
>> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>> [2011-05-06 17:04:35,518] DEBUG - BAMMediationStatisticsObserver
>> ComponentType.PROXYSERVICE http://wso2.org/ns/2009/09/bam/server/user-defined/data
>> ">
>> https://10.100.0.191:9444
>> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>> [2011-05-06 17:04:35,528] DEBUG - BAMMediationStatisticsObserver Event is
>> publishedhttp://wso2.org/ns/2009/09/bam/server/user-defined/data
>> ">
>> https://10.100.0.191:9444
>> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
>> [2011-05-06 17:04:35,597] ERROR - DefaultRealmService
>> java.lang.NullPointerException
>> at
>> org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:157)
>>  at
>> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.getUserRealm(QpidAuthorizationPlugin.java:184)
>> at
>> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:124)
>>  at
>> org.apache.qpid.server.security.SecurityManager$11.allowed(SecurityManager.java:390)
>> at
>> org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245)
>>  at
>> org.apache.qpid.server.security.SecurityManager.authorisePublish(SecurityManager.java:386)
>> at
>> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:307)
>>  at
>> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:96)
>> at
>> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108)
>>  at
>> org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50)
>> at
>> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:112)
>>  at
>> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:96)
>> at org.apache.qpid.transport.Method.delegate(Method.java:159)
>>  at org.apache.qpid.transport.Session.received(Session.java:500)
>> at org.apache.qpid.transport.Connection.dispatch(Connection.java:404)
>>  at
>> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64)
>> at
>> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40)
>>  at
>> org.apache.qpid.transport.MethodDelegate.messageTransfer(MethodDelegate.java:113)
>> at
>> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108)
>>  at
>> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54)
>> at
>> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40)
>>  at org.apache.qpid.transport.Method.delegate(Method.java:159)
>> at org.apache.qpid.transport.Connection.received(Connection.java:369)
>>  at
>> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:196)
>> at
>> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:53)
>>  at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:95)
>> at
>> org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:217)
>>  at org.apache.qpid.transport.network.Assembler.frame(Assembler.java:129)
>> at org.apache.qpid.transport.network.Frame.delegate(Frame.java:133)
>>  at
>> org.apache.qpid.transport.network.Assembler.received(Assembler.java:100)
>> at org.apache.qpid.transport.network.Assembler.received(Assembler.java:42)
>>  at
>> org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:187)
>> at
>> org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:103)
>>  at
>> org.apache.qpid.transport.network.InputHandler.received(InputHan

Re: [Carbon-dev] Events are not getting published in latest packs due to qpid error

[Danushka Menikkumbura]

AmilaJ fixed the issue in DefaultRealmService as I heard.

Danushka

On Fri, May 6, 2011 at 5:18 PM, Tharindu Mathew  wrote:

> Hi,
>
> We came up with this during smoke tests. Events published by ESB are not
> being received by BAM due to this. I believe it's due to the qpid error.
> Please have a look.
>
> Stacktrace:
>
> [2011-05-06 17:04:35,518] DEBUG - PublisherUtils Event payload
> http://wso2.org/ns/2009/09/bam/server/user-defined/data
> ">
> https://10.100.0.191:9444
> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
> [2011-05-06 17:04:35,518] DEBUG - BAMMediationStatisticsObserver
> ComponentType.PROXYSERVICE http://wso2.org/ns/2009/09/bam/server/user-defined/data
> ">
> https://10.100.0.191:9444
> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
> [2011-05-06 17:04:35,528] DEBUG - BAMMediationStatisticsObserver Event is
> publishedhttp://wso2.org/ns/2009/09/bam/server/user-defined/data
> ">
> https://10.100.0.191:9444
> 0ProxyOutMaxProcessingTime-lafProxy1ProxyOutAvgProcessingTime-lafProxy0.ProxyOutMinProcessingTime-lafProxy0ProxyOutCount-lafProxy27ProxyOutCumulativeCount-lafProxy27ProxyOutFaultCount-lafProxy0ProxyOutIDlafProxy
> [2011-05-06 17:04:35,597] ERROR - DefaultRealmService
> java.lang.NullPointerException
> at
> org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:157)
>  at
> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.getUserRealm(QpidAuthorizationPlugin.java:184)
> at
> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:124)
>  at
> org.apache.qpid.server.security.SecurityManager$11.allowed(SecurityManager.java:390)
> at
> org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245)
>  at
> org.apache.qpid.server.security.SecurityManager.authorisePublish(SecurityManager.java:386)
> at
> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:307)
>  at
> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:96)
> at
> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108)
>  at
> org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50)
> at
> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:112)
>  at
> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:96)
> at org.apache.qpid.transport.Method.delegate(Method.java:159)
>  at org.apache.qpid.transport.Session.received(Session.java:500)
> at org.apache.qpid.transport.Connection.dispatch(Connection.java:404)
>  at
> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64)
> at
> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40)
>  at
> org.apache.qpid.transport.MethodDelegate.messageTransfer(MethodDelegate.java:113)
> at
> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108)
>  at
> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54)
> at
> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40)
>  at org.apache.qpid.transport.Method.delegate(Method.java:159)
> at org.apache.qpid.transport.Connection.received(Connection.java:369)
>  at
> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:196)
> at
> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:53)
>  at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:95)
> at org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:217)
>  at org.apache.qpid.transport.network.Assembler.frame(Assembler.java:129)
> at org.apache.qpid.transport.network.Frame.delegate(Frame.java:133)
>  at
> org.apache.qpid.transport.network.Assembler.received(Assembler.java:100)
> at org.apache.qpid.transport.network.Assembler.received(Assembler.java:42)
>  at
> org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:187)
> at
> org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:103)
>  at
> org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:42)
> at
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:102)
>  at
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:36)
> at
> org.apache.qpid.transport.network.mina.MINANetworkDriver.messageReceived(MINANetworkDriver.java:337)
>  at
> org.apache.mina.common.support.Abstra

Re: [Carbon-dev] QPid exception when trying to invoke an admin service

[Danushka Menikkumbura]

I just tried the same scenario that Supun tried with a fresh ESB build off
the latest trunk but could not reproduce the issue. I will handle NPE inside
the Qpid method anyway just to be on the safe side.

Danushka

On Fri, May 6, 2011 at 3:18 PM, Amila Suriarachchi  wrote:

> Did you get the latest packs?
>
> Can you please check with the pack Kasun has tested with out NPE.
>
> thanks,
> Amila.
>
> On Fri, May 6, 2011 at 2:57 PM, Supun Kamburugamuva wrote:
>
>> I'm using a build from yesterday and getting the following stack trace
>> while trying to update endpoints.
>>
>> [2011-05-06 14:56:21,458] ERROR - DefaultRealmService
>> java.lang.NullPointerException
>>at
>> org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:157)
>>at
>> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.getUserRealm(QpidAuthorizationPlugin.java:184)
>>at
>> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:124)
>>at
>> org.apache.qpid.server.security.SecurityManager$11.allowed(SecurityManager.java:390)
>>at
>> org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245)
>>at
>> org.apache.qpid.server.security.SecurityManager.authorisePublish(SecurityManager.java:386)
>>at
>> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:307)
>>at
>> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:96)
>>at
>> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108)
>>at
>> org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50)
>>at
>> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:112)
>>at
>> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:96)
>>at org.apache.qpid.transport.Method.delegate(Method.java:159)
>>at org.apache.qpid.transport.Session.received(Session.java:500)
>>at
>> org.apache.qpid.transport.Connection.dispatch(Connection.java:404)
>>at
>> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64)
>>at
>> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40)
>>at
>> org.apache.qpid.transport.MethodDelegate.messageTransfer(MethodDelegate.java:113)
>>at
>> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108)
>>at
>> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54)
>>at
>> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40)
>>at org.apache.qpid.transport.Method.delegate(Method.java:159)
>>at
>> org.apache.qpid.transport.Connection.received(Connection.java:369)
>>at
>> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:196)
>>at
>> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:53)
>>at
>> org.apache.qpid.transport.network.Assembler.emit(Assembler.java:95)
>>at
>> org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:217)
>>at
>> org.apache.qpid.transport.network.Assembler.frame(Assembler.java:129)
>>at org.apache.qpid.transport.network.Frame.delegate(Frame.java:133)
>>at
>> org.apache.qpid.transport.network.Assembler.received(Assembler.java:100)
>>at
>> org.apache.qpid.transport.network.Assembler.received(Assembler.java:42)
>>at
>> org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:187)
>>at
>> org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:103)
>>at
>> org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:42)
>>at
>> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:102)
>>at
>> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:36)
>>at
>> org.apache.qpid.transport.network.mina.MINANetworkDriver.messageReceived(MINANetworkDriver.java:337)
>>at
>> org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.messageReceived(AbstractIoFilterChain.java:703)
>>at
>> org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:362)
>>at
>> org.apache.mina.common.support.AbstractIoFilterChain.access$1200(AbstractIoFilterChain.java:54)
>>at
>> org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:800)
>>at
>> org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:243)
>>at
>> org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRun

Re: [Carbon-dev] QPid exception when trying to invoke an admin service

[Danushka Menikkumbura]

Actually the NPE is coming from inside DefaultRealmService.java from the
following segment.

RealmConfiguration tenantRealmConfig = (RealmConfiguration)
tenantManager.getTenant(
tenantId).getRealmConfig();

Most probably the returned tenant reference is null. I can handle NPE inside
Qpid but there is anything wrong here?. We expect the returned tenant
reference to be not-null?

Danushka

On Fri, May 6, 2011 at 2:57 PM, Supun Kamburugamuva  wrote:

> I'm using a build from yesterday and getting the following stack trace
> while trying to update endpoints.
>
> [2011-05-06 14:56:21,458] ERROR - DefaultRealmService
> java.lang.NullPointerException
>at
> org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:157)
>at
> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.getUserRealm(QpidAuthorizationPlugin.java:184)
>at
> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:124)
>at
> org.apache.qpid.server.security.SecurityManager$11.allowed(SecurityManager.java:390)
>at
> org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245)
>at
> org.apache.qpid.server.security.SecurityManager.authorisePublish(SecurityManager.java:386)
>at
> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:307)
>at
> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:96)
>at
> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108)
>at
> org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50)
>at
> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:112)
>at
> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:96)
>at org.apache.qpid.transport.Method.delegate(Method.java:159)
>at org.apache.qpid.transport.Session.received(Session.java:500)
>at
> org.apache.qpid.transport.Connection.dispatch(Connection.java:404)
>at
> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64)
>at
> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40)
>at
> org.apache.qpid.transport.MethodDelegate.messageTransfer(MethodDelegate.java:113)
>at
> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108)
>at
> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54)
>at
> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40)
>at org.apache.qpid.transport.Method.delegate(Method.java:159)
>at
> org.apache.qpid.transport.Connection.received(Connection.java:369)
>at
> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:196)
>at
> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:53)
>at
> org.apache.qpid.transport.network.Assembler.emit(Assembler.java:95)
>at
> org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:217)
>at
> org.apache.qpid.transport.network.Assembler.frame(Assembler.java:129)
>at org.apache.qpid.transport.network.Frame.delegate(Frame.java:133)
>at
> org.apache.qpid.transport.network.Assembler.received(Assembler.java:100)
>at
> org.apache.qpid.transport.network.Assembler.received(Assembler.java:42)
>at
> org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:187)
>at
> org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:103)
>at
> org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:42)
>at
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:102)
>at
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:36)
>at
> org.apache.qpid.transport.network.mina.MINANetworkDriver.messageReceived(MINANetworkDriver.java:337)
>at
> org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.messageReceived(AbstractIoFilterChain.java:703)
>at
> org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:362)
>at
> org.apache.mina.common.support.AbstractIoFilterChain.access$1200(AbstractIoFilterChain.java:54)
>at
> org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:800)
>at
> org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:243)
>at
> org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:305)
>at
> edu.emory.mathcs.backport.jav

[Carbon-dev] Where the syslogConfig.xml comes from?

[Danushka Menikkumbura]

I can not build the ESB because of missing syslogConfig.xml file. Most
probably I have not built a required feature, I can not locate it inside any
feature, though.

Any idea?

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

Re: [Carbon-dev] New set of packs are available for Smoke Tests

[Danushka Menikkumbura]

Amila,

Shall we give them a pack with the fix since the QA might not accept the ESB
pack with an NPE.

Thanks,
Danushka

On Fri, May 6, 2011 at 11:00 AM, Amila Suriarachchi  wrote:

>
>
> On Fri, May 6, 2011 at 10:50 AM, Kasun Indrasiri  wrote:
>
>> ESB packs are unusable due to a NPE comes from eventing core.
>>  - [Carbon-dev] Latest ESB packs are unusable : NPE from event core
>>
>
> I think this issue does not effect to any ESB functionality. there will be
> this exceptions in the console.
>
> QA should be able to continue with this exception taking it as a know
> issue.
>
> thanks,
> Amila.
>
>
>>
>> On Fri, May 6, 2011 at 10:47 AM, Manjula Rathnayake wrote:
>>
>>>
>>>
>>> On Fri, May 6, 2011 at 10:35 AM, Manjula Rathnayake 
>>> wrote:
>>>
 Hi,

 MB smoke test is done and ready for QA. There are two L2 issues. We are
 working on fixing them.

>>> Please note that wsclient sample is not working this pack. looking into
>>> this.
>>>
>>> Thank you.
>>>

 Thank you.


 On Fri, May 6, 2011 at 10:32 AM, Prabath Abeysekera 
 wrote:

> Hi Isuru,
>
> On Fri, May 6, 2011 at 10:28 AM, Isuru Suriarachchi wrote:
>
>>
>>
>> On Fri, May 6, 2011 at 9:59 AM, Prabath Abeysekera > > wrote:
>>
>>> Hi,
>>>
>>> We are done with the smoke tests against the latest DSS pack and it's
>>> ready
>>> to be used in the testing environment.
>>>
>>
>> Prabath, can you please help us to do the same DS smoke tests on AS?
>> SupunM is working on testing AS specific functionalities. If you can 
>> just do
>> the same set of tests on DS features, it'll be great.
>>
>
> Sure will do.
>
>
>>
>> Thanks,
>> ~Isuru
>>
>>
>>>
>>>
>>>
>>>
>>> Cheers,
>>>
>>> --
>>> Prabath Abeysekara
>>> Software Engineer
>>> WSO2 Inc.
>>> Email: praba...@wso2.com 
>>> Mobile: +94774171471
>>>
>>> 
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Isuru Suriarachchi
>> Technical Lead & Product Manager, WSO2 Application Server
>>
>> WSO2 Inc. http://wso2.com
>> email : is...@wso2.com
>> blog : http://isurues.wordpress.com/
>>
>> lean . enterprise . middleware
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Prabath Abeysekara
> Software Engineer
> WSO2 Inc.
> Email: praba...@wso2.com 
> Mobile: +94774171471
>
> 
>
>
> ___
> 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
>>>
>>>
>>
>>
>> --
>> Kasun Indrasiri
>> Senior Software Engineer
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 71 536 4128
>> Blog : http://kasunpanorama.blogspot.com/
>>
>> ___
>> 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] Latest ESB packs are unusable : NPE from event core

[Danushka Menikkumbura]

Kasun,

I think this is now fixed on the trunk. Shall we verify with a trunk
version?

Danushka

On Fri, May 6, 2011 at 10:43 AM, Kasun Indrasiri  wrote:

> Hi,
>
> Latest ESB build[1] throws NPE while saving the synapse config. Please have
> a look.
>
>
> [2011-05-06 10:37:47,073]  INFO - SynapseTaskManager Shutting down the task
> manager
> [2011-05-06 10:37:47,074]  INFO - XMLConfigurationBuilder Generating the
> Synapse configuration model by parsing the XML configuration
> Exception in thread "pool-20-thread-121" java.lang.NullPointerException
>  at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.getLoggedInUserName(JMSDeliveryManager.java:206)
> at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.publish(JMSDeliveryManager.java:126)
>  at
> org.wso2.carbon.event.core.internal.EventPublisher.run(EventPublisher.java:56)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> Exception in thread "pool-20-thread-122" java.lang.NullPointerException
> at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.getLoggedInUserName(JMSDeliveryManager.java:206)
>  at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.publish(JMSDeliveryManager.java:126)
> at
> org.wso2.carbon.event.core.internal.EventPublisher.run(EventPublisher.java:56)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>  at java.lang.Thread.run(Thread.java:619)
> Exception in thread "pool-20-thread-123" java.lang.NullPointerException
> at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.getLoggedInUserName(JMSDeliveryManager.java:206)
>  at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.publish(JMSDeliveryManager.java:126)
> at
> org.wso2.carbon.event.core.internal.EventPublisher.run(EventPublisher.java:56)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>  at java.lang.Thread.run(Thread.java:619)
> Exception in thread "pool-20-thread-127" java.lang.NullPointerException
> at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.getLoggedInUserName(JMSDeliveryManager.java:206)
>  at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.publish(JMSDeliveryManager.java:126)
> at
> org.wso2.carbon.event.core.internal.EventPublisher.run(EventPublisher.java:56)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>  at java.lang.Thread.run(Thread.java:619)
> Exception in thread "pool-20-thread-124" java.lang.NullPointerException
> at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.getLoggedInUserName(JMSDeliveryManager.java:206)
>  at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.publish(JMSDeliveryManager.java:126)
> at
> org.wso2.carbon.event.core.internal.EventPublisher.run(EventPublisher.java:56)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>  at java.lang.Thread.run(Thread.java:619)
> Exception in thread "pool-20-thread-125" java.lang.NullPointerException
> at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.getLoggedInUserName(JMSDeliveryManager.java:206)
>  at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.publish(JMSDeliveryManager.java:126)
> at
> org.wso2.carbon.event.core.internal.EventPublisher.run(EventPublisher.java:56)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>  at java.lang.Thread.run(Thread.java:619)
> Exception in thread "pool-20-thread-126" java.lang.NullPointerException
> at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.getLoggedInUserName(JMSDeliveryManager.java:206)
>  at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.publish(JMSDeliveryManager.java:126)
> at
> org.wso2.carbon.event.core.internal.EventPublisher.run(EventPublisher.java:56)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>  at java.lang.Thread.run(Thread.java:619)
> Exception in thread "pool-20-thread-128" java.lang.NullPointerException
> at
> org.wso2.carbon.event.core.internal.delivery.jms.JMSDeliveryManager.getLoggedInUserName(JMSDelive

Re: [Carbon-dev] ESB startup issue(latest build)

[Danushka Menikkumbura]

You need to build features/event.

Please note that qpid gets installed as a result of installing event
feature.

Danushka

On Thu, May 5, 2011 at 12:27 PM, Vijayaratha Vijayasingam
wrote:

> Nope still occurs..I got up from dependencies/qpid, orbit/qpid,
> components/qpid then build features/qpid..
> Can somebody look into this issue??
>
> Thanks
> -Ratha.
>
>
>
> On 5 May 2011 11:55, Manjula Rathnayake  wrote:
>
>> Hi,
>>
>> I got the same, after svn up of qpid from dependency to features, fixed
>> this.
>>
>> Thank you.
>>
>> On Thu, May 5, 2011 at 11:46 AM, Vijayaratha Vijayasingam <
>> rat...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> Today's ESB distribution is not starting properly...Im getting following
>>> error[1] (mediation-initializer component is active and has no issue..)
>>>
>>> -Ratha.
>>> [1]
>>>
>>> [2011-05-05 11:43:31,697]  INFO - CarbonServerManager Repository   :
>>> C:\Projects\trunk\products\esb\modules\DISTRI~1\product\target\WSO2ES~1.0-S\b
>>> in\../repository/deployment/server/
>>> [2011-05-05 11:43:31,963]  INFO - PermissionUpdater Permission cache
>>> updated for tenant 0
>>> [2011-05-05 11:43:31,964]  INFO - CarbonServerManager
>>> ConfigurationContextService registered in 267ms
>>> Error: Unrecognized option: -s8672
>>> usage: Qpid [-b ] [-c ] [--exclude-0-10 ]
>>>[--exclude-0-8 ] [--exclude-0-9 ]
>>>[--exclude-0-9-1 ] [-h] [-l ] [-m
>>>] [-p ] [-v] [-w ]
>>>  -b,--bind  bind to the specified address.
>>>   Overrides any value in the config
>>>   file
>>>  -c,--configuse given configuration file
>>> --exclude-0-10  when listening on the specified
>>> port
>>>   do not accept AMQP0-10 connections.
>>>   The specified port must be one
>>>   specified on the command line
>>> --exclude-0-8when listening on the specified
>>> port
>>>   do not accept AMQP0-8 connections.
>>>   The specified port must be one
>>>   specified on the command line
>>> --exclude-0-9when listening on the specified
>>> port
>>>   do not accept AMQP0-9 connections.
>>>   The specified port must be one
>>>   specified on the command line
>>> --exclude-0-9-1when listening on the specified
>>> port
>>>   do not accept AMQP0-9-1
>>> connections.
>>>   The specified port must be one
>>>   specified on the command line
>>>  -h,--helpprint this message
>>>  -l,--logconfiguse the specified log4j xml
>>>   configuration file. By default
>>> looks
>>>   for a file named log4j.xml in the
>>>   same directory as the configuration
>>>   file
>>>  -m,--mportlisten on the specified management
>>>   port. Overrides any value in the
>>>   config file
>>>  -p,--port  listen on the specified port.
>>>   Overrides any value in the config
>>>   file
>>>  -v,--version print the version information and
>>>   exit
>>>  -w,--logwatch  monitor the log file configuration
>>>   file for changes. Units are
>>> seconds.
>>>   Zero means do not check for
>>> changes.
>>> [2011-05-05 11:44:31,969]  WARN - StartupFinalizerServiceComponent
>>> Waiting for required OSGi services:
>>> org.wso2.carbon.mediation.initializer.services.
>>> SynapseEnvironmentService,
>>>
>>> ___
>>> 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
>>
>>
>
> ___
> 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] "Error obtaining connection" from LDAPConnectionContext

[Danushka Menikkumbura]

It is intermittent. Server runs fine for some time and then starts to gives
this error.

Danushka

On Thu, May 5, 2011 at 11:20 AM, Danushka Menikkumbura wrote:

> I see the port is open and directory service is on it.
>
> Danushka
>
>
> On Thu, May 5, 2011 at 11:17 AM, Danushka Menikkumbura 
> wrote:
>
>> I see this in the latest MB pack I just built.
>>
>> [2011-05-05 10:59:02,584] ERROR
>> {org.wso2.carbon.user.core.ldap.LDAPConnectionContext} -  Error obtaining
>> connection. localhost:10389
>> {org.wso2.carbon.user.core.ldap.LDAPConnectionContext}
>> javax.naming.CommunicationException: localhost:10389 [Root exception is
>> java.net.NoRouteToHostException: Cannot assign requested address]
>> at com.sun.jndi.ldap.Connection.(Connection.java:210)
>> at com.sun.jndi.ldap.LdapClient.(LdapClient.java:118)
>> at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1580)
>> at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2652)
>> at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:293)
>> at
>> com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
>> at
>> com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
>> at
>> com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
>> at
>> com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
>> at
>> org.wso2.carbon.utils.multitenancy.CarbonContextHolder$CarbonInitialJNDIContextFactory.getInitialContext(CarbonContextHolder.java:754)
>> at
>> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
>> at
>> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
>> at javax.naming.InitialContext.init(InitialContext.java:223)
>> at javax.naming.InitialContext.(InitialContext.java:197)
>> at
>> javax.naming.directory.InitialDirContext.(InitialDirContext.java:82)
>> at
>> org.wso2.carbon.user.core.ldap.LDAPConnectionContext.getContext(LDAPConnectionContext.java:86)
>> at
>> org.wso2.carbon.user.core.ldap.LDAPUserStoreManager.getListOfNames(LDAPUserStoreManager.java:679)
>> at
>> org.wso2.carbon.user.core.ldap.LDAPUserStoreManager.getRoleListOfUser(LDAPUserStoreManager.java:550)
>> at
>> org.wso2.carbon.qpid.authorization.qpid.QpidAuthorizationHandler.isAdminUser(QpidAuthorizationHandler.java:357)
>> at
>> org.wso2.carbon.qpid.authorization.qpid.QpidAuthorizationHandler.handleConsumeQueue(QpidAuthorizationHandler.java:115)
>> at
>> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:147)
>> at
>> org.apache.qpid.server.security.SecurityManager$5.allowed(SecurityManager.java:321)
>> at
>> org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245)
>> at
>> org.apache.qpid.server.security.SecurityManager.authoriseConsume(SecurityManager.java:317)
>> at
>> org.apache.qpid.server.queue.SimpleAMQQueue.registerSubscription(SimpleAMQQueue.java:407)
>> at
>> org.apache.qpid.server.transport.ServerSessionDelegate.messageSubscribe(ServerSessionDelegate.java:260)
>> at
>> org.apache.qpid.server.transport.ServerSessionDelegate.messageSubscribe(ServerSessionDelegate.java:96)
>> at
>> org.apache.qpid.transport.MessageSubscribe.dispatch(MessageSubscribe.java:119)
>> at
>> org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50)
>> at
>> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:112)
>> at
>> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:96)
>> at org.apache.qpid.transport.Method.delegate(Method.java:159)
>> at org.apache.qpid.transport.Session.received(Session.java:500)
>> at org.apache.qpid.transport.Connection.dispatch(Connection.java:404)
>> at
>> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64)
>> at
>> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40)
>> at
>> org.apache.qpid.transport.MethodDelegate.messageSubscribe(MethodDelegate.java:131)
>> at
>> org.apache.qpid.transport.MessageSubscribe.dispatch(MessageSubscribe.java:119)
>> at
>> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54)
>> at
>> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40)
>> at org.apache.qpid.transport.Method.delegate(Method.java:159)
&g

Re: [Carbon-dev] "Error obtaining connection" from LDAPConnectionContext

[Danushka Menikkumbura]

I see the port is open and directory service is on it.

Danushka

On Thu, May 5, 2011 at 11:17 AM, Danushka Menikkumbura wrote:

> I see this in the latest MB pack I just built.
>
> [2011-05-05 10:59:02,584] ERROR
> {org.wso2.carbon.user.core.ldap.LDAPConnectionContext} -  Error obtaining
> connection. localhost:10389
> {org.wso2.carbon.user.core.ldap.LDAPConnectionContext}
> javax.naming.CommunicationException: localhost:10389 [Root exception is
> java.net.NoRouteToHostException: Cannot assign requested address]
> at com.sun.jndi.ldap.Connection.(Connection.java:210)
> at com.sun.jndi.ldap.LdapClient.(LdapClient.java:118)
> at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1580)
> at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2652)
> at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:293)
> at
> com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
> at
> com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
> at
> com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
> at
> com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
> at
> org.wso2.carbon.utils.multitenancy.CarbonContextHolder$CarbonInitialJNDIContextFactory.getInitialContext(CarbonContextHolder.java:754)
> at
> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
> at
> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
> at javax.naming.InitialContext.init(InitialContext.java:223)
> at javax.naming.InitialContext.(InitialContext.java:197)
> at
> javax.naming.directory.InitialDirContext.(InitialDirContext.java:82)
> at
> org.wso2.carbon.user.core.ldap.LDAPConnectionContext.getContext(LDAPConnectionContext.java:86)
> at
> org.wso2.carbon.user.core.ldap.LDAPUserStoreManager.getListOfNames(LDAPUserStoreManager.java:679)
> at
> org.wso2.carbon.user.core.ldap.LDAPUserStoreManager.getRoleListOfUser(LDAPUserStoreManager.java:550)
> at
> org.wso2.carbon.qpid.authorization.qpid.QpidAuthorizationHandler.isAdminUser(QpidAuthorizationHandler.java:357)
> at
> org.wso2.carbon.qpid.authorization.qpid.QpidAuthorizationHandler.handleConsumeQueue(QpidAuthorizationHandler.java:115)
> at
> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:147)
> at
> org.apache.qpid.server.security.SecurityManager$5.allowed(SecurityManager.java:321)
> at
> org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245)
> at
> org.apache.qpid.server.security.SecurityManager.authoriseConsume(SecurityManager.java:317)
> at
> org.apache.qpid.server.queue.SimpleAMQQueue.registerSubscription(SimpleAMQQueue.java:407)
> at
> org.apache.qpid.server.transport.ServerSessionDelegate.messageSubscribe(ServerSessionDelegate.java:260)
> at
> org.apache.qpid.server.transport.ServerSessionDelegate.messageSubscribe(ServerSessionDelegate.java:96)
> at
> org.apache.qpid.transport.MessageSubscribe.dispatch(MessageSubscribe.java:119)
> at
> org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50)
> at
> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:112)
> at
> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:96)
> at org.apache.qpid.transport.Method.delegate(Method.java:159)
> at org.apache.qpid.transport.Session.received(Session.java:500)
> at org.apache.qpid.transport.Connection.dispatch(Connection.java:404)
> at
> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64)
> at
> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40)
> at
> org.apache.qpid.transport.MethodDelegate.messageSubscribe(MethodDelegate.java:131)
> at
> org.apache.qpid.transport.MessageSubscribe.dispatch(MessageSubscribe.java:119)
> at
> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54)
> at
> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40)
> at org.apache.qpid.transport.Method.delegate(Method.java:159)
> at org.apache.qpid.transport.Connection.received(Connection.java:369)
> at
> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:196)
> at
> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:53)
> at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:95)
> at
> org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:196)
> at
> org.apache.qpid.transport.network.Assemble

[Carbon-dev] "Error obtaining connection" from LDAPConnectionContext

[Danushka Menikkumbura]

I see this in the latest MB pack I just built.

[2011-05-05 10:59:02,584] ERROR
{org.wso2.carbon.user.core.ldap.LDAPConnectionContext} -  Error obtaining
connection. localhost:10389
{org.wso2.carbon.user.core.ldap.LDAPConnectionContext}
javax.naming.CommunicationException: localhost:10389 [Root exception is
java.net.NoRouteToHostException: Cannot assign requested address]
at com.sun.jndi.ldap.Connection.(Connection.java:210)
at com.sun.jndi.ldap.LdapClient.(LdapClient.java:118)
at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1580)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2652)
at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:293)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
at
com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
at
com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
at
com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
at
org.wso2.carbon.utils.multitenancy.CarbonContextHolder$CarbonInitialJNDIContextFactory.getInitialContext(CarbonContextHolder.java:754)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.(InitialContext.java:197)
at
javax.naming.directory.InitialDirContext.(InitialDirContext.java:82)
at
org.wso2.carbon.user.core.ldap.LDAPConnectionContext.getContext(LDAPConnectionContext.java:86)
at
org.wso2.carbon.user.core.ldap.LDAPUserStoreManager.getListOfNames(LDAPUserStoreManager.java:679)
at
org.wso2.carbon.user.core.ldap.LDAPUserStoreManager.getRoleListOfUser(LDAPUserStoreManager.java:550)
at
org.wso2.carbon.qpid.authorization.qpid.QpidAuthorizationHandler.isAdminUser(QpidAuthorizationHandler.java:357)
at
org.wso2.carbon.qpid.authorization.qpid.QpidAuthorizationHandler.handleConsumeQueue(QpidAuthorizationHandler.java:115)
at
org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:147)
at
org.apache.qpid.server.security.SecurityManager$5.allowed(SecurityManager.java:321)
at
org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245)
at
org.apache.qpid.server.security.SecurityManager.authoriseConsume(SecurityManager.java:317)
at
org.apache.qpid.server.queue.SimpleAMQQueue.registerSubscription(SimpleAMQQueue.java:407)
at
org.apache.qpid.server.transport.ServerSessionDelegate.messageSubscribe(ServerSessionDelegate.java:260)
at
org.apache.qpid.server.transport.ServerSessionDelegate.messageSubscribe(ServerSessionDelegate.java:96)
at
org.apache.qpid.transport.MessageSubscribe.dispatch(MessageSubscribe.java:119)
at
org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50)
at
org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:112)
at
org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:96)
at org.apache.qpid.transport.Method.delegate(Method.java:159)
at org.apache.qpid.transport.Session.received(Session.java:500)
at org.apache.qpid.transport.Connection.dispatch(Connection.java:404)
at
org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64)
at
org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40)
at
org.apache.qpid.transport.MethodDelegate.messageSubscribe(MethodDelegate.java:131)
at
org.apache.qpid.transport.MessageSubscribe.dispatch(MessageSubscribe.java:119)
at
org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54)
at
org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40)
at org.apache.qpid.transport.Method.delegate(Method.java:159)
at org.apache.qpid.transport.Connection.received(Connection.java:369)
at
org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:196)
at
org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:53)
at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:95)
at
org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:196)
at org.apache.qpid.transport.network.Assembler.frame(Assembler.java:129)
at org.apache.qpid.transport.network.Frame.delegate(Frame.java:133)
at
org.apache.qpid.transport.network.Assembler.received(Assembler.java:100)
at
org.apache.qpid.transport.network.Assembler.received(Assembler.java:42)
at
org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:187)
at
org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:103)
at
org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:42)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.rece

[Carbon-dev] Tune product JVM's for GC tuning

[Danushka Menikkumbura]

I see a notable difference in memory usage patterns when I run the MB with
GC-tuning parameters given by Azeez. He said Stratos already ran with those.
Shall we have them with products as well?

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

Re: [Carbon-dev] QPid warnings

[Danushka Menikkumbura]

It looks like the change in event has not taken effect. I will take a look.

Danushka

On Wed, May 4, 2011 at 7:15 PM, Kasun Indrasiri  wrote:

> Hi Danushka,
>
> The issue is continuously reproducible when we send some request to a proxy
> service and then restart the ESB.
>
>
> On Wed, May 4, 2011 at 11:44 AM, Danushka Menikkumbura 
> wrote:
>
>> Event has been modified to make messages non-persistent by default as I
>> know. I will check with Amila.
>>
>> Danushka
>>
>>
>> On Wed, May 4, 2011 at 11:32 AM, Kasun Indrasiri  wrote:
>>
>>> Still getting this error[1] on latest ESB local builds. This happens when
>>> we restart the ESB instance.
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-9596
>>>
>>>
>>> On Fri, Apr 29, 2011 at 11:28 AM, Danushka Menikkumbura <
>>> danus...@wso2.com> wrote:
>>>
>>>> The issue here is that the messages are durable (persistent) but not the
>>>> queues and Qpid discards them at restart. The event implementation has now
>>>> modified to make messages non-persistent by default. Therefore you should
>>>> not get this issue if you have the latest event in your product.
>>>>
>>>> Thanks,
>>>> Danushka
>>>>
>>>>
>>>> On Thu, Apr 28, 2011 at 6:44 PM, Supun Kamburugamuva wrote:
>>>>
>>>>> I'm getting the following warnings while running the ESB.
>>>>>
>>>>> [2011-04-28 18:43:48,914]  WARN
>>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>>>> -  Message id 79 in store, but not in any queue - removing
>>>>> [2011-04-28 18:43:48,967]  WARN
>>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>>>> -  Message id 85 in store, but not in any queue - removing
>>>>> [2011-04-28 18:43:48,991]  WARN
>>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>>>> -  Message id 84 in store, but not in any queue - removing
>>>>> [2011-04-28 18:43:48,994]  WARN
>>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>>>> -  Message id 87 in store, but not in any queue - removing
>>>>> [2011-04-28 18:43:48,997]  WARN
>>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>>>> -  Message id 86 in store, but not in any queue - removing
>>>>> [2011-04-28 18:43:48,999]  WARN
>>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>>>> -  Message id 81 in store, but not in any queue - removing
>>>>> [2011-04-28 18:43:49,002]  WARN
>>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>>>> -  Message id 80 in store, but not in any queue - removing
>>>>> [2011-04-28 18:43:49,008]  WARN
>>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>>>> -  Message id 83 in store, but not in any queue - removing
>>>>> [2011-04-28 18:43:49,015]  WARN
>>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>>>> -  Message id 82 in store, but not in any queue - removing
>>>>> [2011-04-28 18:43:49,019]  WARN
>>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>>>> -  Message id 93 in store, but not in any queue - removing
>>>>> [2011-04-28 18:43:49,022]  WARN
>>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>>>> -  Message id 92 in store, but not in any queue - removing
>>>>> [2011-04-28 18:43:49,026]  WARN
>>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>>>> -  Message id 95 in store, but not in any queue - removing
>>>>> [2011-04-28 18:43:49,030]  WARN
>>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>>>> -  Message id 94 in store, but not in any queue - removing
>>>>> [2011-04-28 18:43:49,033]  WARN
>>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>>>> -  Message id 89 in store, but not in any queue - removing
>>>>> [2011-04-28 18:43:49,036]  WARN
>>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>>>> -  Message id 

Re: [Carbon-dev] QPid warnings

[Danushka Menikkumbura]

Event has been modified to make messages non-persistent by default as I
know. I will check with Amila.

Danushka

On Wed, May 4, 2011 at 11:32 AM, Kasun Indrasiri  wrote:

> Still getting this error[1] on latest ESB local builds. This happens when
> we restart the ESB instance.
>
> [1] https://wso2.org/jira/browse/CARBON-9596
>
>
> On Fri, Apr 29, 2011 at 11:28 AM, Danushka Menikkumbura  > wrote:
>
>> The issue here is that the messages are durable (persistent) but not the
>> queues and Qpid discards them at restart. The event implementation has now
>> modified to make messages non-persistent by default. Therefore you should
>> not get this issue if you have the latest event in your product.
>>
>> Thanks,
>> Danushka
>>
>>
>> On Thu, Apr 28, 2011 at 6:44 PM, Supun Kamburugamuva wrote:
>>
>>> I'm getting the following warnings while running the ESB.
>>>
>>> [2011-04-28 18:43:48,914]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 79 in store, but not in any queue - removing
>>> [2011-04-28 18:43:48,967]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 85 in store, but not in any queue - removing
>>> [2011-04-28 18:43:48,991]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 84 in store, but not in any queue - removing
>>> [2011-04-28 18:43:48,994]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 87 in store, but not in any queue - removing
>>> [2011-04-28 18:43:48,997]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 86 in store, but not in any queue - removing
>>> [2011-04-28 18:43:48,999]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 81 in store, but not in any queue - removing
>>> [2011-04-28 18:43:49,002]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 80 in store, but not in any queue - removing
>>> [2011-04-28 18:43:49,008]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 83 in store, but not in any queue - removing
>>> [2011-04-28 18:43:49,015]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 82 in store, but not in any queue - removing
>>> [2011-04-28 18:43:49,019]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 93 in store, but not in any queue - removing
>>> [2011-04-28 18:43:49,022]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 92 in store, but not in any queue - removing
>>> [2011-04-28 18:43:49,026]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 95 in store, but not in any queue - removing
>>> [2011-04-28 18:43:49,030]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 94 in store, but not in any queue - removing
>>> [2011-04-28 18:43:49,033]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 89 in store, but not in any queue - removing
>>> [2011-04-28 18:43:49,036]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 88 in store, but not in any queue - removing
>>> [2011-04-28 18:43:49,039]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 91 in store, but not in any queue - removing
>>> [2011-04-28 18:43:49,042]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 90 in store, but not in any queue - removing
>>> [2011-04-28 18:43:49,045]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 102 in store, but not in any queue - removing
>>> [2011-04-28 18:43:49,047]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
>>> -  Message id 103 in store, but not in any queue - removing
>>> [2011-04-28 18:43:49,050]  WARN
>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecov

Re: [Carbon-dev] QPid warnings

[Danushka Menikkumbura]

The issue here is that the messages are durable (persistent) but not the
queues and Qpid discards them at restart. The event implementation has now
modified to make messages non-persistent by default. Therefore you should
not get this issue if you have the latest event in your product.

Thanks,
Danushka

On Thu, Apr 28, 2011 at 6:44 PM, Supun Kamburugamuva  wrote:

> I'm getting the following warnings while running the ESB.
>
> [2011-04-28 18:43:48,914]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 79 in store, but not in any queue - removing
> [2011-04-28 18:43:48,967]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 85 in store, but not in any queue - removing
> [2011-04-28 18:43:48,991]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 84 in store, but not in any queue - removing
> [2011-04-28 18:43:48,994]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 87 in store, but not in any queue - removing
> [2011-04-28 18:43:48,997]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 86 in store, but not in any queue - removing
> [2011-04-28 18:43:48,999]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 81 in store, but not in any queue - removing
> [2011-04-28 18:43:49,002]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 80 in store, but not in any queue - removing
> [2011-04-28 18:43:49,008]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 83 in store, but not in any queue - removing
> [2011-04-28 18:43:49,015]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 82 in store, but not in any queue - removing
> [2011-04-28 18:43:49,019]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 93 in store, but not in any queue - removing
> [2011-04-28 18:43:49,022]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 92 in store, but not in any queue - removing
> [2011-04-28 18:43:49,026]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 95 in store, but not in any queue - removing
> [2011-04-28 18:43:49,030]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 94 in store, but not in any queue - removing
> [2011-04-28 18:43:49,033]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 89 in store, but not in any queue - removing
> [2011-04-28 18:43:49,036]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 88 in store, but not in any queue - removing
> [2011-04-28 18:43:49,039]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 91 in store, but not in any queue - removing
> [2011-04-28 18:43:49,042]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 90 in store, but not in any queue - removing
> [2011-04-28 18:43:49,045]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 102 in store, but not in any queue - removing
> [2011-04-28 18:43:49,047]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 103 in store, but not in any queue - removing
> [2011-04-28 18:43:49,050]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 100 in store, but not in any queue - removing
> [2011-04-28 18:43:49,052]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 101 in store, but not in any queue - removing
> [2011-04-28 18:43:49,055]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 98 in store, but not in any queue - removing
> [2011-04-28 18:43:49,057]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 99 in store, but not in any queue - removing
> [2011-04-28 18:43:49,060]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 96 in store, but not in any queue - removing
> [2011-04-28 18:43:49,067]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 97 in store, but not in any queue - removing
> [2011-04-28 18:43:49,070]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message id 110 in store, but not in any queue - removing
> [2011-04-28 18:43:49,073]  WARN
> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler}
> -  Message

Re: [Carbon-dev] Latest ESB packs : class cast exceptions from Qpid

[Danushka Menikkumbura]

Rajika,

I meant this is a result of having the qpid-client-0.11.0.wso2v1.jar in
WEB-INF/lib that gets installed as a result of install the CSG agent. Is not
it so?

Danushka

On Thu, Apr 28, 2011 at 10:07 AM, Rajika Kumarasiri  wrote:

>
>
> On Thu, Apr 28, 2011 at 7:05 AM, Danushka Menikkumbura 
> wrote:
>
>> This is a result of adding the CSG agent into products.
>
>
> Can you explain ?
>
>
>> The SLF4J issue that Azeez mentioned is also a result of that.
>
>
> Yes, as I mentioned in that thread this is because AS distribute the
> helloworld app which also contains the slf4j jars and that causes the issue.
> Also as given by the docs it's a harmless error. I don't think I can remove
> slf4j config from qpid-client libraries because it's used by other products.
>
>
>
>> So, removing JMS jar from Qpid component is the right thing to do?
>>
>
> I removed the geranimo-jms jar from the Qpid component because it's already
> ship with carbon-core now. You don't have to bundle it again.
>
> Rajika
>
>
>>
>> Danushka
>>
>> On Thu, Apr 28, 2011 at 1:18 AM, Rajika Kumarasiri wrote:
>>
>>>
>>>
>>> On Wed, Apr 27, 2011 at 2:50 PM, Rajika Kumarasiri wrote:
>>>
>>>> I'll fix this.
>>>>
>>>
>>> This is fixed now. Please test qpid and eventing stuffs and do let me
>>> know if you come across any issues.
>>>
>>> Rajika
>>>
>>> ___
>>> 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 error while starting ESB - latest trunk

[Danushka Menikkumbura]

Hi Prabath,

You need to build features/event.

Thanks,
Danushka

On Thu, Apr 28, 2011 at 9:37 AM, Prabath Siriwardena wrote:

> Hi Dhanushka,
>
> I took an up of following and built the ESB..
>
> dependencies/qpid
> orbit/qpid
> features/qpid
>
> Still I am getting the same error.. Am I missing something...
>
> Thanks & regards,
> -Prabath
>
> On Tue, Apr 26, 2011 at 11:40 AM, Afkham Azeez  wrote:
> > I also reported this. Danushka mentioned that we have to build
> dependencies,
> > orbit etc from scratch. I have done this and am building the products
> now. I
> > will updated on the progress.
> >
> > On Tue, Apr 26, 2011 at 11:07 AM, Samisa Abeysinghe 
> wrote:
> >>
> >> NACK
> >>
> >> On Mon, Apr 25, 2011 at 10:14 PM, Prabath Siriwardena  >
> >> wrote:
> >>>
> >>>  [2011-04-25 22:13:12,740]  INFO - CarbonServerManager
> >>> ConfigurationContextService registered in 331ms
> >>> java.io.IOException: Unable to load the fallback internal
> >>> log4j.properties configuration file
> >>>at org.apache.qpid.server.Main.configureLogging(Main.java:627)
> >>>at org.apache.qpid.server.Main.startup(Main.java:305)
> >>>at org.apache.qpid.server.Main.execute(Main.java:231)
> >>>at org.apache.qpid.server.Main.(Main.java:101)
> >>>at org.apache.qpid.server.Main.main(Main.java:556)
> >>>at
> >>>
> org.wso2.carbon.qpid.internal.QpidServiceComponent.activate(QpidServiceComponent.java:83)
> >>>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>>at
> >>>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >>>at
> >>>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >>>at java.lang.reflect.Method.invoke(Method.java:597)
> >>>at
> >>>
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230)
> >>>at
> >>>
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
> >>>at
> >>>
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
> >>>at
> >>>
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
> >>>at
> >>>
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
> >>>at
> >>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)
> >>>at
> >>>
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226)
> >>>at
> >>>
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)
> >>>at
> >>>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930)
> >>>at
> >>>
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
> >>>at
> >>>
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
> >>>at
> >>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757)
> >>>at
> >>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712)
> >>>at
> >>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129)
> >>>at
> >>>
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206)
> >>>at
> >>>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:506)
> >>>at
> >>>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:524)
> >>>at
> >>>
> org.wso2.carbon.core.services.internal.CarbonServicesServiceComponent.activate(CarbonServicesServiceComponent.java:72)
> >>>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>>at
> >>>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >>>at
> >>>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >>>at java.lang.reflect.Method.invoke(Method.java:597)
> >>>at
> >>>
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230)
> >>>at
> >>>
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
> >>>at
> >>>
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
> >>>at
> >>>
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
> >>>at
> >>>
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
> >>>at
> >>> org.eclipse.equinox.internal.ds.Resolver.getEl

Re: [Carbon-dev] Latest ESB packs : class cast exceptions from Qpid

[Danushka Menikkumbura]

I am asking if what has been done is the right thing to do.

On Thu, Apr 28, 2011 at 7:09 AM, Samisa Abeysinghe  wrote:

>
>
> On Thu, Apr 28, 2011 at 7:05 AM, Danushka Menikkumbura 
> wrote:
>
>> This is a result of adding the CSG agent into products. The SLF4J issue
>> that Azeez mentioned is also a result of that. So, removing JMS jar from
>> Qpid component is the right thing to do?
>>
>
>  This is fixed now AFAIK
>
>>
>> Danushka
>>
>>  On Thu, Apr 28, 2011 at 1:18 AM, Rajika Kumarasiri wrote:
>>
>>>
>>>
>>> On Wed, Apr 27, 2011 at 2:50 PM, Rajika Kumarasiri wrote:
>>>
>>>> I'll fix this.
>>>>
>>>
>>> This is fixed now. Please test qpid and eventing stuffs and do let me
>>> know if you come across any issues.
>>>
>>> Rajika
>>>
>>> ___
>>> 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
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Latest ESB packs : class cast exceptions from Qpid

[Danushka Menikkumbura]

This is a result of adding the CSG agent into products. The SLF4J issue that
Azeez mentioned is also a result of that. So, removing JMS jar from Qpid
component is the right thing to do?

Danushka

On Thu, Apr 28, 2011 at 1:18 AM, Rajika Kumarasiri  wrote:

>
>
> On Wed, Apr 27, 2011 at 2:50 PM, Rajika Kumarasiri wrote:
>
>> I'll fix this.
>>
>
> This is fixed now. Please test qpid and eventing stuffs and do let me know
> if you come across any issues.
>
> Rajika
>
> ___
> 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] Lots of WARNINGs from qpid

[Danushka Menikkumbura]

Apparently these message should actually have been debug rather than warn.
Please refer to [1].

Fixed on the trunk.

Oh! Qpid, just gimme a break! :-(.

[1] -
http://mail-archives.apache.org/mod_mbox/qpid-dev/201104.mbox/%3cbanlktinl+gy2bx0c-qsy2_qsomskmtc...@mail.gmail.com%3E

Danushka

On Mon, Apr 25, 2011 at 3:52 PM, Danushka Menikkumbura wrote:

> This is due to a contradiction in the way the default values used in Qpid.
>
> The default heartbeat value in client properties is 120 whereas the default
> min and max heartbeat values of a connection are 0. And it checks if the
> heartbeat value lies between the min and max :-(.
>
> I will check on the Qpid list on this behaviour.
>
> Thanks,
> Danushka
>
>
> On Mon, Apr 25, 2011 at 1:33 PM, Danushka Menikkumbura 
> wrote:
>
>> I am looking into this as part of another issue.
>>
>> Danushka
>>
>>
>> On Mon, Apr 25, 2011 at 1:31 PM, Prabath Siriwardena wrote:
>>
>>> From a latest build of ESB... Please have a look..
>>>
>>>
>>> [2011-04-25 13:25:10,175]  WARN
>>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-25 13:25:10,177]  WARN
>>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-25 13:25:10,178]  WARN
>>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>>> [ssn:"10bbf39e-3676-4205-a713-789b3a377cf3"]
>>> [2011-04-25 13:25:10,179]  WARN
>>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-25 13:25:10,182]  WARN
>>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>>> [ssn:"d385f85a-d7bd-4994-b779-4df08160b2f7"]
>>> [2011-04-25 13:25:10,188]  WARN
>>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>>> [ssn:"9bdcf171-e2e7-41ce-8556-0a1f20e5c7c5"]
>>> [2011-04-25 13:25:10,206]  WARN
>>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-25 13:25:10,210]  WARN
>>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-25 13:25:10,211]  WARN
>>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>>> [ssn:"77914124-02ad-4705-bb63-413a03edb43a"]
>>> [2011-04-25 13:25:10,214]  WARN
>>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-25 13:25:10,217]  WARN
>>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>>> [ssn:"2c93167b-2e96-4bed-8466-1b99b6e87080"]
>>> [2011-04-25 13:25:10,221]  WARN
>>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-25 13:25:10,223]  WARN
>>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>>> [ssn:"dbbbf29c-2efc-45ef-95a0-1550136fa2cb"]
>>> [2011-04-25 13:25:10,226]  WARN
>>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-25 13:25:10,229]  WARN
>>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>>> [ssn:"25145440-189a-4a22-b585-04865fdd0150"]
>>> [2011-04-25 13:25:10,233]  WARN
>>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-25 13:25:10,240]  WARN
>>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-25 13:25:10,241]  WARN
>>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>>> [ssn:"706c9dab-92fc-4161-a601-a2f91a578d58"]
>>> [2011-04-25 13:25:10,249]  WARN
>>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>>> [ssn:"627de93a-2eaa-4859-8ed6-4840719cb6d6"]
>>> [2011-04-25 13:25:10,250]  WARN
>>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>>> [ssn:"e99dc63c-1004-4f82-8d72-2867b9fa91b7"]
>>> [2011-04-25 13:25:10,250]  WARN
>>> {org.apache.qpid.transp

Re: [Carbon-dev] qpid error while starting ESB - latest trunk

[Danushka Menikkumbura]

You need to update and build your dependencies/qpid.

Sorry that I missed this mail.

Thanks,
Danushka

On Tue, Apr 26, 2011 at 11:07 AM, Samisa Abeysinghe  wrote:

> NACK
>
>
> On Mon, Apr 25, 2011 at 10:14 PM, Prabath Siriwardena wrote:
>
>>  [2011-04-25 22:13:12,740]  INFO - CarbonServerManager
>> ConfigurationContextService registered in 331ms
>> java.io.IOException: Unable to load the fallback internal
>> log4j.properties configuration file
>>at org.apache.qpid.server.Main.configureLogging(Main.java:627)
>>at org.apache.qpid.server.Main.startup(Main.java:305)
>>at org.apache.qpid.server.Main.execute(Main.java:231)
>>at org.apache.qpid.server.Main.(Main.java:101)
>>at org.apache.qpid.server.Main.main(Main.java:556)
>>at
>> org.wso2.carbon.qpid.internal.QpidServiceComponent.activate(QpidServiceComponent.java:83)
>>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>at java.lang.reflect.Method.invoke(Method.java:597)
>>at
>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230)
>>at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
>>at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
>>at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
>>at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
>>at
>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)
>>at
>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226)
>>at
>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)
>>at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930)
>>at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
>>at
>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
>>at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757)
>>at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712)
>>at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129)
>>at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206)
>>at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:506)
>>at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:524)
>>at
>> org.wso2.carbon.core.services.internal.CarbonServicesServiceComponent.activate(CarbonServicesServiceComponent.java:72)
>>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>at java.lang.reflect.Method.invoke(Method.java:597)
>>at
>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230)
>>at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
>>at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
>>at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
>>at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
>>at
>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)
>>at
>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226)
>>at
>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)
>>at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930)
>>at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
>>at
>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
>>at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757)
>>at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishS

[Carbon-dev] CNF at the ESB startup

[Danushka Menikkumbura]

I have built the ESB using the latest trunk.

Caused by: java.lang.ClassNotFoundException:
org.apache.synapse.transport.nhttp.HttpCoreNIOSender
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:489)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:405)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:393)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at org.apache.axis2.util.Loader.loadClass(Loader.java:261)
at
org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:683)

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

Re: [Carbon-dev] Lots of WARNINGs from qpid

[Danushka Menikkumbura]

This is due to a contradiction in the way the default values used in Qpid.

The default heartbeat value in client properties is 120 whereas the default
min and max heartbeat values of a connection are 0. And it checks if the
heartbeat value lies between the min and max :-(.

I will check on the Qpid list on this behaviour.

Thanks,
Danushka

On Mon, Apr 25, 2011 at 1:33 PM, Danushka Menikkumbura wrote:

> I am looking into this as part of another issue.
>
> Danushka
>
>
> On Mon, Apr 25, 2011 at 1:31 PM, Prabath Siriwardena wrote:
>
>> From a latest build of ESB... Please have a look..
>>
>>
>> [2011-04-25 13:25:10,175]  WARN
>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>> timeout 120 set by the connection, using the brokers max value 0
>> [2011-04-25 13:25:10,177]  WARN
>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>> timeout 120 set by the connection, using the brokers max value 0
>> [2011-04-25 13:25:10,178]  WARN
>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>> [ssn:"10bbf39e-3676-4205-a713-789b3a377cf3"]
>> [2011-04-25 13:25:10,179]  WARN
>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>> timeout 120 set by the connection, using the brokers max value 0
>> [2011-04-25 13:25:10,182]  WARN
>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>> [ssn:"d385f85a-d7bd-4994-b779-4df08160b2f7"]
>> [2011-04-25 13:25:10,188]  WARN
>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>> [ssn:"9bdcf171-e2e7-41ce-8556-0a1f20e5c7c5"]
>> [2011-04-25 13:25:10,206]  WARN
>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>> timeout 120 set by the connection, using the brokers max value 0
>> [2011-04-25 13:25:10,210]  WARN
>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>> timeout 120 set by the connection, using the brokers max value 0
>> [2011-04-25 13:25:10,211]  WARN
>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>> [ssn:"77914124-02ad-4705-bb63-413a03edb43a"]
>> [2011-04-25 13:25:10,214]  WARN
>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>> timeout 120 set by the connection, using the brokers max value 0
>> [2011-04-25 13:25:10,217]  WARN
>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>> [ssn:"2c93167b-2e96-4bed-8466-1b99b6e87080"]
>> [2011-04-25 13:25:10,221]  WARN
>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>> timeout 120 set by the connection, using the brokers max value 0
>> [2011-04-25 13:25:10,223]  WARN
>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>> [ssn:"dbbbf29c-2efc-45ef-95a0-1550136fa2cb"]
>> [2011-04-25 13:25:10,226]  WARN
>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>> timeout 120 set by the connection, using the brokers max value 0
>> [2011-04-25 13:25:10,229]  WARN
>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>> [ssn:"25145440-189a-4a22-b585-04865fdd0150"]
>> [2011-04-25 13:25:10,233]  WARN
>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>> timeout 120 set by the connection, using the brokers max value 0
>> [2011-04-25 13:25:10,240]  WARN
>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>> timeout 120 set by the connection, using the brokers max value 0
>> [2011-04-25 13:25:10,241]  WARN
>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>> [ssn:"706c9dab-92fc-4161-a601-a2f91a578d58"]
>> [2011-04-25 13:25:10,249]  WARN
>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>> [ssn:"627de93a-2eaa-4859-8ed6-4840719cb6d6"]
>> [2011-04-25 13:25:10,250]  WARN
>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>> [ssn:"e99dc63c-1004-4f82-8d72-2867b9fa91b7"]
>> [2011-04-25 13:25:10,250]  WARN
>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>> [ssn:"e612a5ba-47a1-4be7-8415-9b80f0892711"]
>> [2011-04-25 13:25:10,263]  WARN
>> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
>> [ssn:"39f710d9-76cf-4491-a7c4-5123eb28dab0"]
>> [2011-04-25 13:25:13,303]  WARN
>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>> timeout 120 set by the connection, using the brokers max value 0
>> [2011-04-25 13:25:13,305]  WARN
>> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
>> timeout 120 set by the connection, using the brokers max value 0
>> [2011-04-25 13:25:13,305]  WARN
>> {org.apache.qpid.tra

Re: [Carbon-dev] Lots of WARNINGs from qpid

[Danushka Menikkumbura]

I am looking into this as part of another issue.

Danushka

On Mon, Apr 25, 2011 at 1:31 PM, Prabath Siriwardena wrote:

> From a latest build of ESB... Please have a look..
>
>
> [2011-04-25 13:25:10,175]  WARN
> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
> timeout 120 set by the connection, using the brokers max value 0
> [2011-04-25 13:25:10,177]  WARN
> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
> timeout 120 set by the connection, using the brokers max value 0
> [2011-04-25 13:25:10,178]  WARN
> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
> [ssn:"10bbf39e-3676-4205-a713-789b3a377cf3"]
> [2011-04-25 13:25:10,179]  WARN
> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
> timeout 120 set by the connection, using the brokers max value 0
> [2011-04-25 13:25:10,182]  WARN
> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
> [ssn:"d385f85a-d7bd-4994-b779-4df08160b2f7"]
> [2011-04-25 13:25:10,188]  WARN
> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
> [ssn:"9bdcf171-e2e7-41ce-8556-0a1f20e5c7c5"]
> [2011-04-25 13:25:10,206]  WARN
> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
> timeout 120 set by the connection, using the brokers max value 0
> [2011-04-25 13:25:10,210]  WARN
> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
> timeout 120 set by the connection, using the brokers max value 0
> [2011-04-25 13:25:10,211]  WARN
> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
> [ssn:"77914124-02ad-4705-bb63-413a03edb43a"]
> [2011-04-25 13:25:10,214]  WARN
> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
> timeout 120 set by the connection, using the brokers max value 0
> [2011-04-25 13:25:10,217]  WARN
> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
> [ssn:"2c93167b-2e96-4bed-8466-1b99b6e87080"]
> [2011-04-25 13:25:10,221]  WARN
> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
> timeout 120 set by the connection, using the brokers max value 0
> [2011-04-25 13:25:10,223]  WARN
> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
> [ssn:"dbbbf29c-2efc-45ef-95a0-1550136fa2cb"]
> [2011-04-25 13:25:10,226]  WARN
> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
> timeout 120 set by the connection, using the brokers max value 0
> [2011-04-25 13:25:10,229]  WARN
> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
> [ssn:"25145440-189a-4a22-b585-04865fdd0150"]
> [2011-04-25 13:25:10,233]  WARN
> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
> timeout 120 set by the connection, using the brokers max value 0
> [2011-04-25 13:25:10,240]  WARN
> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
> timeout 120 set by the connection, using the brokers max value 0
> [2011-04-25 13:25:10,241]  WARN
> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
> [ssn:"706c9dab-92fc-4161-a601-a2f91a578d58"]
> [2011-04-25 13:25:10,249]  WARN
> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
> [ssn:"627de93a-2eaa-4859-8ed6-4840719cb6d6"]
> [2011-04-25 13:25:10,250]  WARN
> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
> [ssn:"e99dc63c-1004-4f82-8d72-2867b9fa91b7"]
> [2011-04-25 13:25:10,250]  WARN
> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
> [ssn:"e612a5ba-47a1-4be7-8415-9b80f0892711"]
> [2011-04-25 13:25:10,263]  WARN
> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
> [ssn:"39f710d9-76cf-4491-a7c4-5123eb28dab0"]
> [2011-04-25 13:25:13,303]  WARN
> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
> timeout 120 set by the connection, using the brokers max value 0
> [2011-04-25 13:25:13,305]  WARN
> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
> timeout 120 set by the connection, using the brokers max value 0
> [2011-04-25 13:25:13,305]  WARN
> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
> timeout 120 set by the connection, using the brokers max value 0
> [2011-04-25 13:25:13,316]  WARN
> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
> [ssn:"99fcdf21-4acf-40eb-adb0-9085cccddd24"]
> [2011-04-25 13:25:13,317]  WARN
> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
> [ssn:"df8121db-33b4-4734-a28e-5ba1a5dafbfa"]
> [2011-04-25 13:25:13,317]  WARN
> {org.apache.qpid.transport.SessionDelegate} -  CLOSED:
> [ssn:"07984f4d-238c-4e5b-962b-98a58873b04a"]
> [2011-04-25 13:25:14,412]  INFO
> {org.apache.synapse.core.axis2.ProxyService} -  Building Axis service
> for Proxy service : test
> [2011-04-25 13:25:14,422]  INFO
> {org.apache.synapse.core.axis2.ProxyService} -  Adding service test to
> the Axis2 configuration
> [2011-04-25 13:25:14,473]  WARN
> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
> timeout 120 set by the connection, using the brokers max value 0
> [2011-04-25 13:25:14,476]  WARN
> {org.apache.qpid.transport.ClientDelegate} -  Ignoring the idle
> timeout 120 set by the connection, using the 

Re: [Carbon-dev] Event Broker issues after installing ESB features on raw carbon server

[Danushka Menikkumbura]

I will take a look when I switch to Linux.

I doubt there is an issue installing configuration files when a feature is
installed as a dependency.

Danushka

On Fri, Apr 22, 2011 at 5:05 PM, Kasun Indrasiri  wrote:

> mediators feature
>
>
> On Fri, Apr 22, 2011 at 5:04 PM, Danushka Menikkumbura 
> wrote:
>
>> Which features did you install?. Apparently event/qpid configuration files
>> have not been installed.
>>
>> Thanks,
>> Danushka
>>
>>
>> On Fri, Apr 22, 2011 at 4:56 PM, Kasun Indrasiri  wrote:
>>
>>> Hi devs,
>>>
>>> We have fixed the issues related to ESB feature installation failures on
>>> a carbon server. However, when we restart the server after installing the
>>> features, there are some exceptions thrown from the event-broker.
>>>
>>> [2011-04-22 15:40:53,063] ERROR
>>> {org.wso2.carbon.qpid.internal.QpidServiceComponent} -  Failed to start Qpid
>>> broker : File
>>> /home/kasun/development/wso2/wso2svn/trunk/trunk_apr21/products/carbon/modules/distribution/target/wso2carbon-3.2.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
>>> could not be found. Check the file exists and is readable.
>>> [2011-04-22 15:40:53,069] ERROR
>>> {org.wso2.carbon.event.core.internal.builder.EventBrokerBuilderDS} -  Can
>>> not create the event broker
>>> org.wso2.carbon.event.core.exception.EBConfigurationException:
>>> event-broker.xmlcannot be found in the path :
>>> /home/kasun/development/wso2/wso2svn/trunk/trunk_apr21/products/carbon/modules/distribution/target/wso2carbon-3.2.0-SNAPSHOT/repository/conf/event-broker.xml
>>>  at
>>> org.wso2.carbon.event.core.internal.builder.EventBrokerBuilder.loadConfigXML(EventBrokerBuilder.java:88)
>>> at
>>> org.wso2.carbon.event.core.internal.builder.EventBrokerBuilder.createEventBroker(EventBrokerBuilder.java:40)
>>>  at
>>> org.wso2.carbon.event.core.internal.builder.EventBrokerBuilderDS.activate(EventBrokerBuilderDS.java:58)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>  at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>  at java.lang.reflect.Method.invoke(Method.java:597)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230)
>>>  at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
>>>  at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
>>> at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
>>>  at
>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)
>>> at
>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226)
>>>  at
>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930)
>>>  at
>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
>>> at
>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
>>>  at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712)
>>>  at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206)
>>>  at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:506)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:524)
>>>  at
>>> org.wso2.carbon.qpid.internal.QpidServiceComponent.activate(QpidServiceComponent.java:98)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>  at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl

Re: [Carbon-dev] Event Broker issues after installing ESB features on raw carbon server

[Danushka Menikkumbura]

Which features did you install?. Apparently event/qpid configuration files
have not been installed.

Thanks,
Danushka

On Fri, Apr 22, 2011 at 4:56 PM, Kasun Indrasiri  wrote:

> Hi devs,
>
> We have fixed the issues related to ESB feature installation failures on a
> carbon server. However, when we restart the server after installing the
> features, there are some exceptions thrown from the event-broker.
>
> [2011-04-22 15:40:53,063] ERROR
> {org.wso2.carbon.qpid.internal.QpidServiceComponent} -  Failed to start Qpid
> broker : File
> /home/kasun/development/wso2/wso2svn/trunk/trunk_apr21/products/carbon/modules/distribution/target/wso2carbon-3.2.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
> could not be found. Check the file exists and is readable.
> [2011-04-22 15:40:53,069] ERROR
> {org.wso2.carbon.event.core.internal.builder.EventBrokerBuilderDS} -  Can
> not create the event broker
> org.wso2.carbon.event.core.exception.EBConfigurationException:
> event-broker.xmlcannot be found in the path :
> /home/kasun/development/wso2/wso2svn/trunk/trunk_apr21/products/carbon/modules/distribution/target/wso2carbon-3.2.0-SNAPSHOT/repository/conf/event-broker.xml
>  at
> org.wso2.carbon.event.core.internal.builder.EventBrokerBuilder.loadConfigXML(EventBrokerBuilder.java:88)
> at
> org.wso2.carbon.event.core.internal.builder.EventBrokerBuilder.createEventBroker(EventBrokerBuilder.java:40)
>  at
> org.wso2.carbon.event.core.internal.builder.EventBrokerBuilderDS.activate(EventBrokerBuilderDS.java:58)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>  at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230)
>  at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
>  at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
>  at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226)
>  at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930)
>  at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
> at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
>  at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712)
>  at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206)
>  at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:506)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:524)
>  at
> org.wso2.carbon.qpid.internal.QpidServiceComponent.activate(QpidServiceComponent.java:98)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>  at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230)
>  at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
>  at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
>  at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226)
>  at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930)
>  at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
> at
> org

Re: [Carbon-dev] Qpid/Eventing Errors at Shutdown

[Danushka Menikkumbura]

Or else bundles should have been deactivated in the right order?

Thanks,
Danushka

On Fri, Apr 22, 2011 at 1:45 PM, Hiranya Jayathilaka wrote:

>
>
> On Fri, Apr 22, 2011 at 1:39 PM, Danushka Menikkumbura 
> wrote:
>
>> It looks like the Qpid broker is already down when certain events get
>> fired at shutdown.
>>
>
> Perhaps the event component can check whether the Qpid component is active
> before trying to publish an event?
>
> Thanks,
> Hiranya
>
>
>>
>> On Fri, Apr 22, 2011 at 1:31 PM, Hiranya Jayathilaka wrote:
>>
>>> Hi,
>>>
>>> I get the following errors every now and then when shutting down the ESB.
>>> It doesn't happen consistently. But the problem seems to be linked with
>>> registry eventing. Any ideas?
>>>
>>> [2011-04-22 13:25:12,808] ERROR - AMQConnectionDelegate_0_10 connection
>>> exception: conn:33d9a5bb
>>> org.apache.qpid.transport.ConnectionException: connection aborted
>>> at org.apache.qpid.transport.Connection.closed(Connection.java:535)
>>>  at
>>> org.apache.qpid.transport.network.Assembler.closed(Assembler.java:110)
>>> at
>>> org.apache.qpid.transport.network.InputHandler.closed(InputHandler.java:202)
>>>  at
>>> org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:150)
>>> at java.lang.Thread.run(Thread.java:619)
>>> [2011-04-22 13:25:12,810] ERROR - EventPublisher Can not publish the
>>> message
>>> org.wso2.carbon.event.core.exception.EBRuntimeException: Can not create
>>> topic connection
>>> at
>>> org.wso2.carbon.event.core.internal.delivary.jms.JMSDelivaryManager.getTopicConnection(JMSDelivaryManager.java:75)
>>>  at
>>> org.wso2.carbon.event.core.internal.delivary.jms.JMSDelivaryManager.publish(JMSDelivaryManager.java:130)
>>> at
>>> org.wso2.carbon.event.core.internal.EventPublisher.run(EventPublisher.java:44)
>>>  at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>  at java.lang.Thread.run(Thread.java:619)
>>> Caused by: javax.jms.JMSException: Error creating connection: connect()
>>> aborted
>>> at
>>> org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:286)
>>>  at
>>> org.apache.qpid.client.AMQConnectionFactory.createTopicConnection(AMQConnectionFactory.java:345)
>>> at
>>> org.wso2.carbon.event.core.internal.delivary.jms.JMSDelivaryManager.getTopicConnection(JMSDelivaryManager.java:69)
>>>  ... 5 more
>>> Caused by: org.apache.qpid.AMQConnectionFailureException: connect()
>>> aborted [error code 200: reply success]
>>> at org.apache.qpid.client.AMQConnection.(AMQConnection.java:472)
>>>  at
>>> org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:276)
>>> ... 7 more
>>> Caused by: org.apache.qpid.AMQException: Cannot connect to broker:
>>> connect() aborted [error code 200: reply success]
>>> at
>>> org.apache.qpid.client.AMQConnectionDelegate_0_10.makeBrokerConnection(AMQConnectionDelegate_0_10.java:203)
>>>  at
>>> org.apache.qpid.client.AMQConnection.makeBrokerConnection(AMQConnection.java:617)
>>> at org.apache.qpid.client.AMQConnection.(AMQConnection.java:396)
>>>  ... 8 more
>>> Caused by: org.apache.qpid.transport.ConnectionException: connect()
>>> aborted
>>> at org.apache.qpid.transport.Connection.connect(Connection.java:281)
>>>  at
>>> org.apache.qpid.client.AMQConnectionDelegate_0_10.makeBrokerConnection(AMQConnectionDelegate_0_10.java:184)
>>> ... 10 more
>>> [2011-04-22 13:25:12,811]  WARN - SessionDelegate DETACHED:
>>> [ssn:"4f0e4307-2157-4f8f-8bc6-a69354042ae6"]
>>> [2011-04-22 13:25:12,813] ERROR - EventPublisher Can not publish the
>>> message
>>> org.wso2.carbon.event.core.exception.EBRuntimeException: Can not create
>>> topic connection
>>>  at
>>> org.wso2.carbon.event.core.internal.delivary.jms.JMSDelivaryManager.getTopicConnection(JMSDelivaryManager.java:75)
>>> at
>>> org.wso2.carbon.event.core.internal.delivary.jms.JMSDelivaryManager.publish(JMSDelivaryManager.java:130)
>>>  at
>>> org.wso2.carbon.event.core.internal.EventPublisher.run(EventPublisher.java:44)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Threa

Re: [Carbon-dev] Qpid/Eventing Errors at Shutdown

[Danushka Menikkumbura]

It looks like the Qpid broker is already down when certain events get fired
at shutdown.

On Fri, Apr 22, 2011 at 1:31 PM, Hiranya Jayathilaka wrote:

> Hi,
>
> I get the following errors every now and then when shutting down the ESB.
> It doesn't happen consistently. But the problem seems to be linked with
> registry eventing. Any ideas?
>
> [2011-04-22 13:25:12,808] ERROR - AMQConnectionDelegate_0_10 connection
> exception: conn:33d9a5bb
> org.apache.qpid.transport.ConnectionException: connection aborted
> at org.apache.qpid.transport.Connection.closed(Connection.java:535)
>  at org.apache.qpid.transport.network.Assembler.closed(Assembler.java:110)
> at
> org.apache.qpid.transport.network.InputHandler.closed(InputHandler.java:202)
>  at
> org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:150)
> at java.lang.Thread.run(Thread.java:619)
> [2011-04-22 13:25:12,810] ERROR - EventPublisher Can not publish the
> message
> org.wso2.carbon.event.core.exception.EBRuntimeException: Can not create
> topic connection
> at
> org.wso2.carbon.event.core.internal.delivary.jms.JMSDelivaryManager.getTopicConnection(JMSDelivaryManager.java:75)
>  at
> org.wso2.carbon.event.core.internal.delivary.jms.JMSDelivaryManager.publish(JMSDelivaryManager.java:130)
> at
> org.wso2.carbon.event.core.internal.EventPublisher.run(EventPublisher.java:44)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>  at java.lang.Thread.run(Thread.java:619)
> Caused by: javax.jms.JMSException: Error creating connection: connect()
> aborted
> at
> org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:286)
>  at
> org.apache.qpid.client.AMQConnectionFactory.createTopicConnection(AMQConnectionFactory.java:345)
> at
> org.wso2.carbon.event.core.internal.delivary.jms.JMSDelivaryManager.getTopicConnection(JMSDelivaryManager.java:69)
>  ... 5 more
> Caused by: org.apache.qpid.AMQConnectionFailureException: connect() aborted
> [error code 200: reply success]
> at org.apache.qpid.client.AMQConnection.(AMQConnection.java:472)
>  at
> org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:276)
> ... 7 more
> Caused by: org.apache.qpid.AMQException: Cannot connect to broker:
> connect() aborted [error code 200: reply success]
> at
> org.apache.qpid.client.AMQConnectionDelegate_0_10.makeBrokerConnection(AMQConnectionDelegate_0_10.java:203)
>  at
> org.apache.qpid.client.AMQConnection.makeBrokerConnection(AMQConnection.java:617)
> at org.apache.qpid.client.AMQConnection.(AMQConnection.java:396)
>  ... 8 more
> Caused by: org.apache.qpid.transport.ConnectionException: connect() aborted
> at org.apache.qpid.transport.Connection.connect(Connection.java:281)
>  at
> org.apache.qpid.client.AMQConnectionDelegate_0_10.makeBrokerConnection(AMQConnectionDelegate_0_10.java:184)
> ... 10 more
> [2011-04-22 13:25:12,811]  WARN - SessionDelegate DETACHED:
> [ssn:"4f0e4307-2157-4f8f-8bc6-a69354042ae6"]
> [2011-04-22 13:25:12,813] ERROR - EventPublisher Can not publish the
> message
> org.wso2.carbon.event.core.exception.EBRuntimeException: Can not create
> topic connection
>  at
> org.wso2.carbon.event.core.internal.delivary.jms.JMSDelivaryManager.getTopicConnection(JMSDelivaryManager.java:75)
> at
> org.wso2.carbon.event.core.internal.delivary.jms.JMSDelivaryManager.publish(JMSDelivaryManager.java:130)
>  at
> org.wso2.carbon.event.core.internal.EventPublisher.run(EventPublisher.java:44)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: javax.jms.JMSException: Error creating connection: Connection
> refused
> at
> org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:286)
>  at
> org.apache.qpid.client.AMQConnectionFactory.createTopicConnection(AMQConnectionFactory.java:345)
> at
> org.wso2.carbon.event.core.internal.delivary.jms.JMSDelivaryManager.getTopicConnection(JMSDelivaryManager.java:69)
>  ... 5 more
> Caused by: org.apache.qpid.AMQConnectionFailureException: Connection
> refused
> at org.apache.qpid.client.AMQConnection.(AMQConnection.java:472)
>  at
> org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:276)
> ... 7 more
> Caused by: org.apache.qpid.transport.TransportException: Error connecting
> to broker
> at
> org.apache.qpid.transport.network.io.IoNetworkTransport.init(IoNetworkTransport.java:78)
>  at
> org.apache.qpid.transport.TransportBuilder.init(TransportBuilder.java:44)
> at org.apache.qpid.transport.Connection.connect(Connection.java:240)
>  at
> org.apache.qpid.client.AMQConnectionDelegate_0_10.makeBrokerConnection(AMQConnectionDelegate_0_10.java:184)
> at
> org.apache.qpid.client.AMQConnection.ma

Re: [Carbon-dev] Two way JMS scenario is failing with Qpid

[Danushka Menikkumbura]

I will look into it. Please raise a JIRA.

Danushka

On Fri, Apr 22, 2011 at 11:13 AM, Rajika Kumarasiri  wrote:

> Also another problem is that once we invoked a one way scenario for the
> first time it works but when we try again the message doesn't reach the
> destination but only receive the set of logs that I pointed earlier.
>
> Rajika
>
> On Fri, Apr 22, 2011 at 11:04 AM, Danushka Menikkumbura  > wrote:
>
>> What does the transport receiver say?
>>
>> On Fri, Apr 22, 2011 at 11:01 AM, Rajika Kumarasiri wrote:
>>
>>> The request/response two way JMS scenario is failing with a trunk build
>>> of Qpid component when I tested with CSG. This was used to work earlier and
>>> also note that this is critical for CSG functionality. I see whole lot of
>>> following logs from Qpid. Back end is sending the response and place on a
>>> temp queue but due to some reason that message is not pick correctly by
>>> receiver.
>>>
>>> Rajika
>>>
>>> [2011-04-22 10:52:47,132]  WARN - ClientDelegate Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-22 10:52:47,179]  WARN - ClientDelegate Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-22 10:52:47,220]  WARN - ClientDelegate Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-22 10:52:47,221]  WARN - ClientDelegate Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-22 10:52:47,231]  WARN - ClientDelegate Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-22 10:52:47,233]  INFO - ProxyService Successfully created the
>>> Axis2 service for Proxy service : test
>>> [2011-04-22 10:52:47,233]  INFO - ProxyService Building Axis service for
>>> Proxy service : SimpleStockQuoteServiceProxy
>>> [2011-04-22 10:52:47,242]  WARN - ClientDelegate Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-22 10:52:47,292]  WARN - SessionDelegate CLOSED:
>>> [ssn:"6f1b84f7-175b-4f38-b20d-bea2d3754788"]
>>> [2011-04-22 10:52:47,295]  WARN - SessionDelegate CLOSED:
>>> [ssn:"d7cd86b9-2319-4a3b-ae68-bcab03a6aba4"]
>>> [2011-04-22 10:52:47,314]  WARN - ClientDelegate Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-22 10:52:47,316]  WARN - ClientDelegate Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-22 10:52:47,322]  WARN - SessionDelegate CLOSED:
>>> [ssn:"af654f75-88aa-46c9-aa79-4683a554676d"]
>>> [2011-04-22 10:52:47,389]  WARN - SessionDelegate CLOSED:
>>> [ssn:"1b4022da-61a1-457a-bc66-294671f7db38"]
>>> [2011-04-22 10:52:47,393]  WARN - SessionDelegate CLOSED:
>>> [ssn:"fab88d5d-8115-4f90-aadf-4bd8ae63198b"]
>>> [2011-04-22 10:52:47,419]  WARN - SessionDelegate CLOSED:
>>> [ssn:"8932e782-c0ee-4ded-b80a-5a725589b3d8"]
>>> [2011-04-22 10:52:47,421]  WARN - SessionDelegate CLOSED:
>>> [ssn:"8cbf6673-9dba-40c6-a461-bb49290622d4"]
>>> [2011-04-22 10:52:47,435]  WARN - SessionDelegate CLOSED:
>>> [ssn:"dbe9717c-ce22-4d49-aacf-e982e136431c"]
>>> [2011-04-22 10:52:47,506]  INFO - ProxyService Adding service
>>> SimpleStockQuoteServiceProxy to the Axis2 configuration
>>> [2011-04-22 10:52:47,511]  INFO - DeploymentInterceptor Deploying Axis2
>>> service: SimpleStockQuoteServiceProxy {super-tenant}
>>> [2011-04-22 10:52:47,678]  WARN - ClientDelegate Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-22 10:52:47,689]  WARN - ClientDelegate Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-22 10:52:47,755]  WARN - SessionDelegate CLOSED:
>>> [ssn:"a317a96c-c191-4282-8492-2ab4140a942a"]
>>> [2011-04-22 10:52:47,760]  WARN - ClientDelegate Ignoring the idle
>>> timeout 120 set by the connection, using the brokers max value 0
>>> [2011-04-22 10:52:47,771]  INFO - ProxyService Successfully created the
>>> Axis2 service for Proxy service : SimpleStockQuoteServiceProxy
>>> [2011-04-22 10:52:47,799]  WARN - SessionDelegate CLOSED:
>>> [ssn:"c4c63731-5137-474e-b526-b7a605b141a9"]
>>> [2011-04-22 10:52:47,943]  WARN - Ses

Re: [Carbon-dev] Two way JMS scenario is failing with Qpid

[Danushka Menikkumbura]

What does the transport receiver say?

On Fri, Apr 22, 2011 at 11:01 AM, Rajika Kumarasiri  wrote:

> The request/response two way JMS scenario is failing with a trunk build of
> Qpid component when I tested with CSG. This was used to work earlier and
> also note that this is critical for CSG functionality. I see whole lot of
> following logs from Qpid. Back end is sending the response and place on a
> temp queue but due to some reason that message is not pick correctly by
> receiver.
>
> Rajika
>
> [2011-04-22 10:52:47,132]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:47,179]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:47,220]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:47,221]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:47,231]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:47,233]  INFO - ProxyService Successfully created the
> Axis2 service for Proxy service : test
> [2011-04-22 10:52:47,233]  INFO - ProxyService Building Axis service for
> Proxy service : SimpleStockQuoteServiceProxy
> [2011-04-22 10:52:47,242]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:47,292]  WARN - SessionDelegate CLOSED:
> [ssn:"6f1b84f7-175b-4f38-b20d-bea2d3754788"]
> [2011-04-22 10:52:47,295]  WARN - SessionDelegate CLOSED:
> [ssn:"d7cd86b9-2319-4a3b-ae68-bcab03a6aba4"]
> [2011-04-22 10:52:47,314]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:47,316]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:47,322]  WARN - SessionDelegate CLOSED:
> [ssn:"af654f75-88aa-46c9-aa79-4683a554676d"]
> [2011-04-22 10:52:47,389]  WARN - SessionDelegate CLOSED:
> [ssn:"1b4022da-61a1-457a-bc66-294671f7db38"]
> [2011-04-22 10:52:47,393]  WARN - SessionDelegate CLOSED:
> [ssn:"fab88d5d-8115-4f90-aadf-4bd8ae63198b"]
> [2011-04-22 10:52:47,419]  WARN - SessionDelegate CLOSED:
> [ssn:"8932e782-c0ee-4ded-b80a-5a725589b3d8"]
> [2011-04-22 10:52:47,421]  WARN - SessionDelegate CLOSED:
> [ssn:"8cbf6673-9dba-40c6-a461-bb49290622d4"]
> [2011-04-22 10:52:47,435]  WARN - SessionDelegate CLOSED:
> [ssn:"dbe9717c-ce22-4d49-aacf-e982e136431c"]
> [2011-04-22 10:52:47,506]  INFO - ProxyService Adding service
> SimpleStockQuoteServiceProxy to the Axis2 configuration
> [2011-04-22 10:52:47,511]  INFO - DeploymentInterceptor Deploying Axis2
> service: SimpleStockQuoteServiceProxy {super-tenant}
> [2011-04-22 10:52:47,678]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:47,689]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:47,755]  WARN - SessionDelegate CLOSED:
> [ssn:"a317a96c-c191-4282-8492-2ab4140a942a"]
> [2011-04-22 10:52:47,760]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:47,771]  INFO - ProxyService Successfully created the
> Axis2 service for Proxy service : SimpleStockQuoteServiceProxy
> [2011-04-22 10:52:47,799]  WARN - SessionDelegate CLOSED:
> [ssn:"c4c63731-5137-474e-b526-b7a605b141a9"]
> [2011-04-22 10:52:47,943]  WARN - SessionDelegate CLOSED:
> [ssn:"7a8d9abc-8b36-4665-93d1-ced7e698730c"]
> [2011-04-22 10:52:52,110]  INFO - RegistryBasedSynapseConfigSerializer
> Persisting the SynapseConfiguration to the registry...
> [2011-04-22 10:52:52,210]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:52,211]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:52,211]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:52,279]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:52,293]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:52,302]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:52,304]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using the brokers max value 0
> [2011-04-22 10:52:52,304]  WARN - ClientDelegate Ignoring the idle timeout
> 120 set by the connection, using th

Re: [Carbon-dev] Exception during AppServer startup - QPid logging config failure

[Danushka Menikkumbura]

Azeez,

Qpid no longer maintains it's own log4j configuration. You are using an
updated qpid feature with an old qpid dependency. All these logging issues
were fixed a couple of days back. Please follow the thread "Logging Issues @
ESB startup" on carbon-dev@.

Thanks,
Danushka

On Fri, Apr 22, 2011 at 9:54 AM, Afkham Azeez  wrote:

> Broker] BRK-1006 : Using configuration :
> /Users/azeez/projects/wso2/org/trunk/carbon/products/appserver/modules/distribution/product/target/wso2appserver-4.1.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
>  Logging configuration error: unable to read file
> /Users/azeez/projects/wso2/org/trunk/carbon/products/appserver/modules/distribution/product/target/wso2appserver-4.1.0-SNAPSHOT/repository/conf/advanced/log4j.xml
> Using the fallback internal log4j.properties configuration
> java.io.IOException: Unable to load the fallback internal log4j.properties
> configuration file
> at org.apache.qpid.server.Main.configureLogging(Main.java:627)
>  at org.apache.qpid.server.Main.startup(Main.java:305)
> at org.apache.qpid.server.Main.execute(Main.java:231)
>  at org.apache.qpid.server.Main.(Main.java:101)
> at org.apache.qpid.server.Main.main(Main.java:556)
>  at
> org.wso2.carbon.qpid.internal.QpidServiceComponent.activate(QpidServiceComponent.java:83)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>  at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230)
>  at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
>  at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
>  at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226)
>  at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930)
>  at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
> at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
>  at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712)
>  at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206)
>  at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:506)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:524)
>  at
> org.wso2.carbon.discovery.DiscoveryComponent.activate(DiscoveryComponent.java:76)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>  at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230)
>  at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
>  at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
>  at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226)
>  at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930)
>  at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
> at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
>  at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757)
> at
> or

Re: [Carbon-dev] Unable to start two servers - Qpid bind exception

[Danushka Menikkumbura]

There was a bug in Qpid. It was trying to read the SSL port from
connector/ssl/port whereas it was defined under connector/sslport in
configuration and hence returning the default value 8672.

Please update your dependencies/qpid and build dependencies/qpid, orbit/qpid
and features/event before building the product.

Thanks,
Danushka

On Thu, Apr 21, 2011 at 11:47 AM, Danushka Menikkumbura
wrote:

> This is used by the CSG agent to get SSL port when creating connections.
> What you get is a bind exception. We need to fix this anyway if the broker
> reads the SSL port from configuration properly.
>
> Danushka
>
>
> On Thu, Apr 21, 2011 at 11:41 AM, Kasun Indrasiri  wrote:
>
>>
>> In
>> ./org.wso2.carbon.qpid/src/main/java/org/wso2/carbon/qpid/service/QpidServiceImpl.java
>> it says:
>>
>>  public String getSSLPort(){
>> // FIXME the ssl port is a configuration option, read it from
>> $CARBON_HOME/repository/conf/etc/config.xml
>> // for now just return the default SSL port
>> return QPID_DEFAULT_SSL_PORT;
>> }
>>
>> On Thu, Apr 21, 2011 at 11:37 AM, Danushka Menikkumbura <
>> danus...@wso2.com> wrote:
>>
>>> No it is not. The SSL port is read from the qpid-config.xml. The broker
>>> does not accept it as an argument at star up so that it is not included in
>>> carbon.xml. Let me check whats going wrong.
>>>
>>> Danushka
>>>
>>>
>>> On Thu, Apr 21, 2011 at 11:16 AM, Tharindu Mathew wrote:
>>>
>>>> Has qpid hardcoded port 8672 for ssl??
>>>>
>>>> On Thu, Apr 21, 2011 at 11:12 AM, Kasun Weranga wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> When I going to start appserver and BAM, i got the following bind
>>>>> exception from qpid.
>>>>>
>>>>> java.net.BindException: Could not bind to 0.0.0.0/0.0.0.0:8672
>>>>>  at
>>>>> org.apache.qpid.transport.network.mina.MINANetworkDriver.bind(MINANetworkDriver.java:173)
>>>>> at org.apache.qpid.server.Main.startup(Main.java:464)
>>>>>  at org.apache.qpid.server.Main.execute(Main.java:231)
>>>>> at org.apache.qpid.server.Main.(Main.java:101)
>>>>>  at org.apache.qpid.server.Main.main(Main.java:556)
>>>>> at
>>>>> org.wso2.carbon.qpid.internal.QpidServiceComponent.activate(QpidServiceComponent.java:83)
>>>>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>  at
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>  at
>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230)
>>>>> at
>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
>>>>>  at
>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
>>>>> at
>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
>>>>>  at
>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
>>>>> at
>>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)
>>>>>  at
>>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226)
>>>>> at
>>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)
>>>>>  at
>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930)
>>>>> at
>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
>>>>>  at
>>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
>>>>> at
>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757)
>>>>>  at
>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712)
>>>>> at
>>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationI

Re: [Carbon-dev] Unable to start two servers - Qpid bind exception

[Danushka Menikkumbura]

This is used by the CSG agent to get SSL port when creating connections.
What you get is a bind exception. We need to fix this anyway if the broker
reads the SSL port from configuration properly.

Danushka

On Thu, Apr 21, 2011 at 11:41 AM, Kasun Indrasiri  wrote:

>
> In
> ./org.wso2.carbon.qpid/src/main/java/org/wso2/carbon/qpid/service/QpidServiceImpl.java
> it says:
>
>  public String getSSLPort(){
> // FIXME the ssl port is a configuration option, read it from
> $CARBON_HOME/repository/conf/etc/config.xml
> // for now just return the default SSL port
> return QPID_DEFAULT_SSL_PORT;
> }
>
> On Thu, Apr 21, 2011 at 11:37 AM, Danushka Menikkumbura  > wrote:
>
>> No it is not. The SSL port is read from the qpid-config.xml. The broker
>> does not accept it as an argument at star up so that it is not included in
>> carbon.xml. Let me check whats going wrong.
>>
>> Danushka
>>
>>
>> On Thu, Apr 21, 2011 at 11:16 AM, Tharindu Mathew wrote:
>>
>>> Has qpid hardcoded port 8672 for ssl??
>>>
>>> On Thu, Apr 21, 2011 at 11:12 AM, Kasun Weranga  wrote:
>>>
>>>> Hi,
>>>>
>>>> When I going to start appserver and BAM, i got the following bind
>>>> exception from qpid.
>>>>
>>>> java.net.BindException: Could not bind to 0.0.0.0/0.0.0.0:8672
>>>>  at
>>>> org.apache.qpid.transport.network.mina.MINANetworkDriver.bind(MINANetworkDriver.java:173)
>>>> at org.apache.qpid.server.Main.startup(Main.java:464)
>>>>  at org.apache.qpid.server.Main.execute(Main.java:231)
>>>> at org.apache.qpid.server.Main.(Main.java:101)
>>>>  at org.apache.qpid.server.Main.main(Main.java:556)
>>>> at
>>>> org.wso2.carbon.qpid.internal.QpidServiceComponent.activate(QpidServiceComponent.java:83)
>>>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>  at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>  at
>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230)
>>>> at
>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
>>>>  at
>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
>>>> at
>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
>>>>  at
>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
>>>> at
>>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)
>>>>  at
>>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)
>>>>  at
>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930)
>>>> at
>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
>>>>  at
>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757)
>>>>  at
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129)
>>>>  at
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206)
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:506)
>>>>  at
>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:524)
>>>> at
>>>> org.wso2.carbon.core.services.internal.CarbonServicesServiceComponent.activate(CarbonServicesServiceComponent.java:72)
>>>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.Native

Re: [Carbon-dev] Unable to start two servers - Qpid bind exception

[Danushka Menikkumbura]

No it is not. The SSL port is read from the qpid-config.xml. The broker does
not accept it as an argument at star up so that it is not included in
carbon.xml. Let me check whats going wrong.

Danushka

On Thu, Apr 21, 2011 at 11:16 AM, Tharindu Mathew  wrote:

> Has qpid hardcoded port 8672 for ssl??
>
> On Thu, Apr 21, 2011 at 11:12 AM, Kasun Weranga  wrote:
>
>> Hi,
>>
>> When I going to start appserver and BAM, i got the following bind
>> exception from qpid.
>>
>> java.net.BindException: Could not bind to 0.0.0.0/0.0.0.0:8672
>>  at
>> org.apache.qpid.transport.network.mina.MINANetworkDriver.bind(MINANetworkDriver.java:173)
>> at org.apache.qpid.server.Main.startup(Main.java:464)
>>  at org.apache.qpid.server.Main.execute(Main.java:231)
>> at org.apache.qpid.server.Main.(Main.java:101)
>>  at org.apache.qpid.server.Main.main(Main.java:556)
>> at
>> org.wso2.carbon.qpid.internal.QpidServiceComponent.activate(QpidServiceComponent.java:83)
>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>  at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>>  at
>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
>>  at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
>>  at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)
>>  at
>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226)
>> at
>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)
>>  at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
>>  at
>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757)
>>  at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129)
>>  at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:506)
>>  at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:524)
>> at
>> org.wso2.carbon.core.services.internal.CarbonServicesServiceComponent.activate(CarbonServicesServiceComponent.java:72)
>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>  at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>>  at
>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
>>  at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
>>  at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)
>>  at
>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226)
>> at
>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)
>>  at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
>>  at
>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757)
>>  at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129)
>>  at
>> org.eclipse.o

Re: [Carbon-dev] Logging Issues @ ESB startup

[Danushka Menikkumbura]

Hiranya,

This is now fixed on the trunk. Please update your dependencies/qpid and
features/qpid. Then build the following modules in order before building the
ESB.

dependencies/qpid, orbit/qpid, features/qpid and features/event.

Thanks,
Danushka

On Mon, Apr 18, 2011 at 11:44 AM, Danushka Menikkumbura
wrote:

> As you said ESB uses its own log4j configuration right?. It looks like it
> gets overridden. I will take a look.
>
> Danushka
>
>
> On Mon, Apr 18, 2011 at 11:35 AM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Mon, Apr 18, 2011 at 5:47 AM, Danushka Menikkumbura > > wrote:
>>
>>> Could you please post the changes?. I do not notice anything like that
>>> with the MB.
>>>
>>
>> Here's an example:
>>
>> [2011-04-18 11:33:27,798]  INFO - DeploymentEngine Deploying Web service:
>> org.wso2.carbon.message.processor -
>> [2011-04-18 11:33:27,830]  INFO - DeploymentEngine Deploying Web service:
>> org.wso2.carbon.message.store -
>> [2011-04-18 11:33:29,408]  INFO - DeploymentInterceptor Deploying Axis2
>> service: wso2carbon-sts {super-tenant}
>> [2011-04-18 11:33:29,767]  INFO - DeploymentEngine Deploying Web service:
>> org.wso2.carbon.sts -
>> [2011-04-18 11:33:30,109]  INFO - DeploymentEngine Deploying Web service:
>> org.wso2.carbon.tryit -
>> [2011-04-18 11:33:30,353]  INFO - DeploymentInterceptor Deploying Axis2
>> service: XKMS {super-tenant}
>> [2011-04-18 11:33:30,997]  INFO - DeploymentEngine Deploying Web service:
>> org.wso2.carbon.xkms -
>> [2011-04-18 11:33:31,022]  INFO - DeploymentEngine Deploying Web service:
>> org.wso2.carbon.xkms.mgt -
>> [2011-04-18 11:33:31,325]  INFO - CarbonServerManager Repository   :
>> /home/hiranya/Projects/Java/carbon-platform/trunk/products/esb/modules/distribution/product/target/wso2esb-4.0.0-SNAPSHOT/repository/deployment/server/
>> [2011-04-18 11:33:31,821]  INFO - PermissionUpdater Permission cache
>> updated for tenant 0
>> [2011-04-18 11:33:31,822]  INFO - CarbonServerManager
>> ConfigurationContextService registered in 497ms
>> [Broker] BRK-1006 : Using configuration :
>> /home/hiranya/Projects/Java/carbon-platform/trunk/products/esb/modules/distribution/product/target/wso2esb-4.0.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
>> Logging configuration error: unable to read file
>> /home/hiranya/Projects/Java/carbon-platform/trunk/products/esb/modules/distribution/product/target/wso2esb-4.0.0-SNAPSHOT/repository/conf/advanced/log4j.xml
>> Using the fallback internal log4j.properties configuration
>> [Broker] BRK-1001 : Startup : Version: 0.11 Build: 90784:90849
>> [Broker] MNG-1001 : Startup
>> [Broker] MNG-1004 : Ready : Using the platform JMX Agent
>> [Broker] BRK-1002 : Starting : Listening on TCP port 5672
>> [Broker] BRK-1004 : Qpid Broker Ready
>> [2011-04-18 11:33:37,074]  INFO
>> {org.wso2.carbon.mediation.initializer.ServiceBusInitializer} -  Starting
>> ESB...
>> [2011-04-18 11:33:37,744]  INFO
>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console URL  :
>> https://10.100.0.160:9443/carbon/
>> [2011-04-18 11:33:37,843]  INFO
>> {org.wso2.carbon.mediation.initializer.ServiceBusInitializer} -
>>  Initializing Apache Synapse...
>> [2011-04-18 11:33:37,905]  INFO
>> {org.apache.synapse.SynapseControllerFactory} -  Using Synapse home :
>> /home/hiranya/Projects/Java/carbon-platform/trunk/products/esb/modules/distribution/product/target/wso2esb-4.0.0-SNAPSHOT/.
>> [2011-04-18 11:33:37,906]  INFO
>> {org.apache.synapse.SynapseControllerFactory} -  Using synapse.xml location
>> :
>> /home/hiranya/Projects/Java/carbon-platform/trunk/products/esb/modules/distribution/product/target/wso2esb-4.0.0-SNAPSHOT/././repository/deployment/server/synapse-configs/default
>> [2011-04-18 11:33:37,906]  INFO
>> {org.apache.synapse.SynapseControllerFactory} -  Using server name :
>> localhost
>> [2011-04-18 11:33:37,912]  INFO
>> {org.apache.synapse.SynapseControllerFactory} -  The timeout handler will
>> run every : 15s
>> [2011-04-18 11:33:38,072]  INFO
>> {org.apache.synapse.Axis2SynapseController} -  Initializing Synapse at : Mon
>> Apr 18 11:33:38 IST 2011
>> [2011-04-18 11:33:38,074]  INFO
>> {org.apache.synapse.Axis2SynapseController} -  Loading mediator
>> extensions...
>> [2011-04-18 11:33:38,086]  INFO
>> {org.wso2.carbon.mediation.initializer.CarbonSynapseController} -  Loading
>> the mediation configuration from the file system
>> [2011-04-18 11:33:38,089]  INFO
>> {org.apache.synapse.config.xml.MultiXMLConfigurationBuilder} -  Building
>>

Re: [Carbon-dev] JMS is broken again

[Danushka Menikkumbura]

As I remember the geronimo-jms jar has now been integrated into the core. So
it should be enough to have it inside lib/core. Sameera please correct me if
I am wrong.

Danushka

On Wed, Apr 20, 2011 at 9:51 PM, Afkham Azeez  wrote:

> Why was this jar in 2 locations? Why can't we have it only within the osgi
> framework?
>  On Apr 20, 2011 4:27 PM, "Rajika Kumarasiri"  wrote:
> > To resolve the issue we need to move the
> > geronimo-jms_1.1_spec-1.1.0.wso2v1.jar into lib/api from
> > lib/core/WEB-INF/lib/ and remove the same jar from
> > $CARBON_HOME/repository/component/plugins. We need to fix this in carbon
> > core. Removing from the plugin folder will cause troubles for samples,
> for
> > example ESB's JMS sample depends on that as a class path.
> >
> > Azeez why did you left behind the geronimo-jms_1.1_spec-1.1.0.wso2v1.jar
> > when moving the jars into api folder ?
> >
> > Rajika
> >
> > On Wed, Apr 20, 2011 at 3:15 PM, Rajika Kumarasiri 
> wrote:
> >
> >> When I try a JMS sample with a current ESB trunk build I ended up with
> the
> >> following error. It seems JMS is broken again in the trunk.
> >>
> >> Rajika
> >>
> >> 2011-04-20 15:13:00,848] ERROR
> {org.apache.synapse.core.axis2.Axis2Sender}
> >> - Unexpected error during sending message out
> >> org.apache.axis2.transport.base.BaseTransportException: JNDI lookup of
> name
> >> SimpleStockQuoteService returned a org.apache.qpid.client.AMQQueue while
> a
> >> interface javax.jms.Destination was expected
> >> at
> >>
> org.apache.axis2.transport.base.BaseUtils.handleException(BaseUtils.java:166)
> >> at org.apache.axis2.transport.jms.JMSUtils.lookup(JMSUtils.java:522)
> >> at
> >>
> org.apache.axis2.transport.jms.JMSUtils.lookupDestination(JMSUtils.java:708)
> >> at
> >>
> org.apache.axis2.transport.jms.JMSOutTransportInfo.getDestination(JMSOutTransportInfo.java:184)
> >> at
> >>
> org.apache.axis2.transport.jms.JMSOutTransportInfo.loadConnectionFactoryFromProperties(JMSOutTransportInfo.java:132)
> >> at
> >>
> org.apache.axis2.transport.jms.JMSOutTransportInfo.createJMSSender(JMSOutTransportInfo.java:330)
> >> at
> >> org.apache.axis2.transport.jms.JMSSender.sendMessage(JMSSender.java:124)
> >> at
> >>
> org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
> >> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
> >> at
> >>
> org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:278)
> >> at
> >>
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
> >> at
> >>
> org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:413)
> >> at
> >> org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:57)
> >> at
> >>
> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:270)
> >> at
> >>
> org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:278)
> >> at
> >>
> org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:59)
> >> at
> >>
> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:175)
> >> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
> >> at
> >>
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
> >> at
> >>
> org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:408)
> >> at
> >>
> org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:259)
> >> at
> >>
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:173)
> >> at
> >>
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> >> at
> >>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> >> at java.lang.Thread.run(Thread.java:619)
> >>
> >>
>
> ___
> 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 Warnings at ESB Startup

[Danushka Menikkumbura]

We are in the process of refactoring the event implementation to streamline
its API. This will be fixed as part of it.

Danushka

On Tue, Apr 19, 2011 at 1:48 PM, Tharindu Mathew  wrote:

> We have seen this happening with BAM as well.
>
> The event component should either make the queues persistent by default or
> provide any other suitable solution, so it "just works".
>
>
> On Tue, Apr 19, 2011 at 1:43 PM, Hiranya Jayathilaka wrote:
>
>> Danushka,
>>
>> On Tue, Apr 19, 2011 at 1:33 PM, Danushka Menikkumbura > > wrote:
>>
>>> This happens when Qpid recovers persisted messages at start up. The issue
>>> in this case is that your messages (JMS) are persistent but not your queues
>>> and hence it discards messages.
>>>
>>> FYI.
>>>
>>> JMS message are persistent by default but not queues. Therefore Qpid
>>> persists all messages by default. When it recovers, it tries to restore it's
>>> queues and when queues are not persistent, it discards the messages it has
>>> persisted.
>>>
>>> To avoid this, you should either make your messages persistent or make
>>> your queues durable.
>>>
>>
>> And how do we do that? Please note that I haven't created any queues in
>> Qpid. I haven't even tried to do any messaging stuff with the Qpid component
>> yet. This error happens on its own. It has been happening ever since the
>> Qpid component was included in the ESB product build.
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Thanks,
>>> Danushka
>>>
>>> On Tue, Apr 19, 2011 at 1:24 PM, Hiranya Jayathilaka 
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Sometimes when starting the ESB, it throws out a bunch of logs like
>>>> this:
>>>>
>>>> [2011-04-19 13:23:28,656]  WARN
>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler} -
>>>>  Message id 1 in store, but not in any queue - removing
>>>> [2011-04-19 13:23:28,765]  WARN
>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler} -
>>>>  Message id 2 in store, but not in any queue - removing
>>>> [2011-04-19 13:23:28,768]  WARN
>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler} -
>>>>  Message id 3 in store, but not in any queue - removing
>>>> [2011-04-19 13:23:28,770]  WARN
>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler} -
>>>>  Message id 4 in store, but not in any queue - removing
>>>> [2011-04-19 13:23:28,773]  WARN
>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler} -
>>>>  Message id 5 in store, but not in any queue - removing
>>>> [2011-04-19 13:23:28,780]  WARN
>>>> {org.apache.qpid.server.virtualhost.VirtualHostConfigRecoveryHandler} -
>>>>  Message id 6 in store, but not in any queue - removing
>>>>
>>>> Any idea what's going on here? Can we fix/get rid of it?
>>>>
>>>> Thanks
>>>> --
>>>> Hiranya Jayathilaka
>>>> Senior Software Engineer;
>>>> WSO2 Inc.;  http://wso2.org
>>>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>>>> Blog: http://techfeast-hiranya.blogspot.com
>>>>
>>>> ___
>>>> 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
>>>
>>>
>>
>>
>> --
>> Hiranya Jayathilaka
>> Senior Software Engineer;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.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
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev