Re: [Dev] SSO enabling BAM dashboard

[Pradeep Fernando]

On Tue, May 28, 2013 at 6:14 AM, Pradeep Fernando  wrote:

> --Pradeep
> sent from my phone
>
> On May 28, 2013 10:33 AM, "Pradeep Fernando"  wrote:
> >
> >
> > On May 28, 2013 10:26 AM, "Nuwan Bandara"  wrote:
> > >
> > > Hi Suresh,
> > >
> > >
> > > On Tue, May 28, 2013 at 10:09 AM, Suresh Attanayaka 
> wrote:
> > >>
> > >> Hi,
> > >>
> > >> On Tue, May 28, 2013 at 1:29 AM, Pradeep Fernando 
> wrote:
> > >>>
> > >>> Hi All,
> > >>>
> > >>> Using Nuwans code pointer, I managed to create SSO session in the
> bamdashboard app. We should be able to check the session param and grant
> access to the pages in the app.
> > >>>
> > >>> However, the dashboard app calls in backend services to retrieve
> info. As per current code, this is done like below,
> > >>>
> > >>> get the admin cookie using logged in user credentials - > use the
> admin cookie for subsequent admin call requests.
> > >>>
> > >>> with SSO enablement we no longer have/need the user credentials
> within our app.
> > >>>
> > >>> The use case of getting admin info from carbon admin services, falls
> under server to server authentication category (jaggery application being
> the client here). The logged in user has nothing to do with api calling
> part.
> > >>>
> > >>>
> > >>> so,
> > >>>
> > >>> 1. user authenticate to the dashboard via SAML SSO
> > >>> 2 the dashboard app consumes admin services using pre-defined
> credentials (dashboard-user with admin credentials)
> > >>
> > >>
> > >> So with this approach the backend  admin services are not aware of
> which user consuming the services ? The permissions of the logged-in user
> are not taken into account ?
> > The permission model for logged in user should be handled by the
> webapp/jaggeryapp. For that purpose it can use CC.
> If the IDP and app dont share the same user store then we have to create a
> user and add permissions.
>
> >
> > Irrespective of the logged in user , the application has the credentials
> to log in to the back end. Forget about those being carbon admin services.
> How would you consume a secured third party service from your app if you
> had to.
> >
> > Then I think the model is not correct.
> > >> In the previous case we pass the admin service cookie, then the
> access to the admin services are allowed based on the permissions of the
> user. This should be implemented in the new model as well as I think.
> > >> @Nuwan, how this is handled in the UES ? Is there a way you have
> mapped the dashboard session and the backend session ?
> > >
> > >
> > > In UES, we don't have FE/BE, its only one session, and we directly use
> osgi services from jaggery. The only session we have is, JSESSION
> maintained by the browser and the application.
>
I think this suits for bam dashboard app as well.



> > >
> > > @Pradeep shall we review (chat on) the solution you built, even though
> I helped with figuring out the SSO part I am unclear of the big picture.
> >
> > Sure. @Chamath please note
> >
> > >
> > > Regards,
> > > /Nuwan
> > >
> > >>
> > >>
> > >>>
> > >>>
> > >>> would do i guess. Any concerns. ? Please correct me if I'm
> interpreting something wrong...
> > >>>
> > >>> --Pradeep
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> On Mon, May 27, 2013 at 6:48 AM, Buddhika Chamith <
> buddhi...@wso2.com> wrote:
> > 
> >  Hi Pradeep,
> > 
> >  We don't use SSO with our dashboard Jaggery app at the moment. User
> needs to log in to the BAM dashboard separately. There was
> some difficulty in sharing sessions between the management console and
> Jaggery applications at the time BAM dashboard was being done IIRC. Chamath
> would be able to fill in the specific details on that. Anyway I guess now
> we might be able to rethink this with above mentioned approach if it solves
> our problem.
> > 
> >  Regards
> >  Buddhika
> > 
> > 
> > 
> >  On Sun, May 26, 2013 at 11:58 AM, Nuwan Bandara 
> wrote:
> > >
> > > Hi pradeep,
> > >
> > > [1] are the apps with SSO, the portal app and store app
> are connected with SSO app.
> > >
> > > Regards,
> > > /Nuwan
> > >
> > > [1]
> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/products/ues/1.0.0/modules/apps/
> > >
> > >
> > > On Sun, May 26, 2013 at 11:41 AM, Pradeep Fernando <
> prad...@wso2.com> wrote:
> > >>
> > >> Hi All,
> > >>
> > >> I want to do the $subject. Since dashboard is a jaggery app, I
> believe it is all about SSO enabling a jaggery app. This post [1] suggest
> that It is done for UES.
> > >>
> > >> Is this functionality available OOTB in BAM dashbaords ? if not
> what it takes to make it work. Code pointers/references highly appreciated.
> > >>
> > >>
> > >> [1] http://architects.dzone.com/articles/enabling-sso-wso2-user
> > >>
> > >> Thanks,
> > >> --Pradeep
> > >>
> > >>
> > >> --
> > >> Pradeep Fernando
> > >> Member, Management Committee - Platform & Cloud Technolog

[Dev] Registry.uddi build failure

[Miyuru Wanninayaka]

Please fix ASP

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project org.wso2.carbon.registry.uddi: Compilation
failure: Compilation failure:
[ERROR]
/home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[27,0]
package org.uddi.api_v3 does not exist
[ERROR]
/home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[53,19]
cannot find symbol
[ERROR] symbol  : class AuthToken
[ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
[ERROR]
/home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[64,49]
cannot find symbol
[ERROR] symbol  : class BusinessEntity
[ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
[ERROR]
/home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[64,18]
cannot find symbol
[ERROR] symbol  : class BusinessDetail
[ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
[ERROR]
/home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[87,55]
cannot find symbol
[ERROR] symbol  : class BusinessService
[ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
[ERROR]
/home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[87,18]
cannot find symbol
[ERROR] symbol  : class ServiceDetail
[ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
[ERROR]
/home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[112,42]
cannot find symbol
[ERROR] symbol  : class TModel
[ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
[ERROR]
/home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[112,18]
cannot find symbol
[ERROR] symbol  : class TModelDetail
[ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
[ERROR]
/home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[136,44]
cannot find symbol
[ERROR] symbol  : class FindBusiness
[ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
[ERROR]
/home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[136,18]
cannot find symbol
[ERROR] symbol  : class BusinessList
[ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
[ERROR]
/home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[233,19]
cannot find symbol
[ERROR] symbol  : class AuthToken
[ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
[ERROR]
/home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/servlet/JUDDIRegistryServlet.java:[3,39]
package org.apache.commons.configuration does not exist
[ERROR]
/home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[27,0]
package org.uddi.api_v3 does not exist
[ERROR]
/home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[53,19]
cannot find symbol
[ERROR] symbol  : class AuthToken
[ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
[ERROR]
/home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[64,49]
cannot find symbol
[ERROR] symbol  : class BusinessEntity
[ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
[ERROR]
/home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[64,18]
cannot find symbol
[ERROR] symbol  : cla

Re: [Dev] Registry.uddi build failure

[Subash Chaturanga]

Did you build up to date platform/dependencies/juddi and
platform/dependencies/orbit/juddi ?

On Tue, May 28, 2013 at 1:13 PM, Miyuru Wanninayaka  wrote:

> Please fix ASP
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project org.wso2.carbon.registry.uddi: Compilation
> failure: Compilation failure:
> [ERROR]
> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[27,0]
> package org.uddi.api_v3 does not exist
> [ERROR]
> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[53,19]
> cannot find symbol
> [ERROR] symbol  : class AuthToken
> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
> [ERROR]
> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[64,49]
> cannot find symbol
> [ERROR] symbol  : class BusinessEntity
> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
> [ERROR]
> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[64,18]
> cannot find symbol
> [ERROR] symbol  : class BusinessDetail
> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
> [ERROR]
> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[87,55]
> cannot find symbol
> [ERROR] symbol  : class BusinessService
> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
> [ERROR]
> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[87,18]
> cannot find symbol
> [ERROR] symbol  : class ServiceDetail
> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
> [ERROR]
> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[112,42]
> cannot find symbol
> [ERROR] symbol  : class TModel
> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
> [ERROR]
> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[112,18]
> cannot find symbol
> [ERROR] symbol  : class TModelDetail
> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
> [ERROR]
> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[136,44]
> cannot find symbol
> [ERROR] symbol  : class FindBusiness
> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
> [ERROR]
> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[136,18]
> cannot find symbol
> [ERROR] symbol  : class BusinessList
> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
> [ERROR]
> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[233,19]
> cannot find symbol
> [ERROR] symbol  : class AuthToken
> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
> [ERROR]
> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/servlet/JUDDIRegistryServlet.java:[3,39]
> package org.apache.commons.configuration does not exist
> [ERROR]
> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[27,0]
> package org.uddi.api_v3 does not exist
> [ERROR]
> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[53,19]
> cannot find symbol
> [ERROR] symbol  : class AuthToken
> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
> [ERROR]
> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[64,49]
> cannot find symbol
> [ERROR] symbol  : class BusinessEntity
>

Re: [Dev] Concurrent Modification on executor phases (Seen on NIO as well as PT)

[Manjula Rathnayake]

Hi Dushan,

Have we committed these changes into wso2esb-4.6.0? I am getting this error
when load testing.

thank you.


On Thu, Nov 29, 2012 at 11:39 AM, Dushan Abeyruwan  wrote:

> Hi
>   During the iterator operation for larger message observed following
> error, this is repeatable for NIO as well as PT,  while investigating the
> issue found out its due to  Linked list modification happens at different
> phases [1] [2] the problem has resolved once we introduced 
> *ConcurrentLinkedQueue
>  instad LinkedQueue any thoughts on the changers?*
>
>
> At the AxisEngine
>
>   [1]   * @throws AxisFault
>  */
> private static InvocationResponse invoke(MessageContext msgContext,
> boolean resuming)
> throws AxisFault {
>
> if (msgContext.getCurrentHandlerIndex() == -1) {
> msgContext.setCurrentHandlerIndex(0);
> }
>
> InvocationResponse pi = InvocationResponse.CONTINUE;
>
> while (msgContext.getCurrentHandlerIndex() <
> msgContext.getExecutionChain().size()) {
> Handler currentHandler = (Handler)
> msgContext.getExecutionChain().
> get(msgContext.getCurrentHandlerIndex());
>
> try {
> if (!resuming) {
> msgContext.addExecutedPhase(currentHandler);
> } else {
> /* If we are resuming the flow, we don't want to add
> the phase
> * again, as it has already been added.
> */
> resuming = false;
> }
> pi = currentHandler.invoke(msgContext);
> }
>
>
> ---
>
> [2].private static void flowComplete(MessageContext msgContext) {
> Iterator invokedPhaseIterator =
> msgContext.getExecutedPhases();
>
> while (invokedPhaseIterator.hasNext()) {
> Handler currentHandler = ((Handler)
> invokedPhaseIterator.next());
> currentHandler.flowComplete(msgContext);
> }
>
> /*This is needed because the OutInAxisOperation currently invokes
> * receive() even when a fault occurs, and we will have already
> executed
> * the flowComplete on those before receiveFault() is called.
> */
> msgContext.resetExecutedPhases();
> }
>
>
>  a
>
>
> /**
>  * Add a Phase to the collection of executed phases for the path.
>  * Phases will be inserted in a LIFO data structure.
>  *
>  * @param phase The phase to add to the list.
>  */
> public void addExecutedPhase(Handler phase) {
> if (executedPhases == null) {
> executedPhases = new LinkedList();
> }
> executedPhases.addFirst(phase);
> }
>
> /**
>  * Remove the first Phase in the collection of executed phases
>  */
> public void removeFirstExecutedPhase() {
> if (executedPhases != null) {
> executedPhases.removeFirst();
> }
> }
>
> 43/carbon/
> [2012-11-29 10:55:45,570]  INFO - TimeoutHandler This engine will expire
> all callbacks after : 120 seconds, irrespective of the timeout action,
> after the specified or optional timeout
> Listening for transport dt_socket at address: 
> [2012-11-29 10:55:48,369] ERROR - NativeWorkerPool Uncaught exception
> java.util.ConcurrentModificationException
> at java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:761)
>  at java.util.LinkedList$ListItr.next(LinkedList.java:696)
> at org.apache.axis2.engine.AxisEngine.flowComplete(AxisEngine.java:293)
>  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:182)
> at
> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:217)
>  at
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
> 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:662)
> [2012-11-29 10:55:55,462] ERROR - NativeWorkerPool Uncaught exception
> java.util.ConcurrentModificationException
> at java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:761)
>  at java.util.LinkedList$ListItr.next(LinkedList.java:696)
> at org.apache.axis2.engine.AxisEngine.flowComplete(AxisEngine.java:293)
>  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:182)
> at
> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:217)
>  at
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
> 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:662)
> [2012-11-29 10:55:55,484] ERROR - NativeWorkerPool Uncaught exception
>

Re: [Dev] Registry.uddi build failure

[Miyuru Wanninayaka]

juddi tests also fails with same package is missing. So something is broken.

On Tue, May 28, 2013 at 1:23 PM, Subash Chaturanga  wrote:

> Did you build up to date platform/dependencies/juddi and
> platform/dependencies/orbit/juddi ?
>
>
> On Tue, May 28, 2013 at 1:13 PM, Miyuru Wanninayaka wrote:
>
>> Please fix ASP
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>> (default-compile) on project org.wso2.carbon.registry.uddi: Compilation
>> failure: Compilation failure:
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[27,0]
>> package org.uddi.api_v3 does not exist
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[53,19]
>> cannot find symbol
>> [ERROR] symbol  : class AuthToken
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[64,49]
>> cannot find symbol
>> [ERROR] symbol  : class BusinessEntity
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[64,18]
>> cannot find symbol
>> [ERROR] symbol  : class BusinessDetail
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[87,55]
>> cannot find symbol
>> [ERROR] symbol  : class BusinessService
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[87,18]
>> cannot find symbol
>> [ERROR] symbol  : class ServiceDetail
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[112,42]
>> cannot find symbol
>> [ERROR] symbol  : class TModel
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[112,18]
>> cannot find symbol
>> [ERROR] symbol  : class TModelDetail
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[136,44]
>> cannot find symbol
>> [ERROR] symbol  : class FindBusiness
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[136,18]
>> cannot find symbol
>> [ERROR] symbol  : class BusinessList
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[233,19]
>> cannot find symbol
>> [ERROR] symbol  : class AuthToken
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/servlet/JUDDIRegistryServlet.java:[3,39]
>> package org.apache.commons.configuration does not exist
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[27,0]
>> package org.uddi.api_v3 does not exist
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[53,19]
>> cannot find symbol
>> [ERROR] symbol  : class AuthToken
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/car

Re: [Dev] Concurrent Modification on executor phases (Seen on NIO as well as PT)

[Dushan Abeyruwan]

No this can not, since it has to fixed by axis2 kernel level, and required
JDK 7 dependency.


On Tue, May 28, 2013 at 2:02 PM, Manjula Rathnayake wrote:

> Hi Dushan,
>
> Have we committed these changes into wso2esb-4.6.0? I am getting this
> error when load testing.
>
> thank you.
>
>
> On Thu, Nov 29, 2012 at 11:39 AM, Dushan Abeyruwan wrote:
>
>>  Hi
>>   During the iterator operation for larger message observed following
>> error, this is repeatable for NIO as well as PT,  while investigating the
>> issue found out its due to  Linked list modification happens at different
>> phases [1] [2] the problem has resolved once we introduced 
>> *ConcurrentLinkedQueue
>>  instad LinkedQueue any thoughts on the changers?*
>>
>>
>> At the AxisEngine
>>
>>   [1]   * @throws AxisFault
>>  */
>> private static InvocationResponse invoke(MessageContext msgContext,
>> boolean resuming)
>> throws AxisFault {
>>
>> if (msgContext.getCurrentHandlerIndex() == -1) {
>> msgContext.setCurrentHandlerIndex(0);
>> }
>>
>> InvocationResponse pi = InvocationResponse.CONTINUE;
>>
>> while (msgContext.getCurrentHandlerIndex() <
>> msgContext.getExecutionChain().size()) {
>> Handler currentHandler = (Handler)
>> msgContext.getExecutionChain().
>> get(msgContext.getCurrentHandlerIndex());
>>
>> try {
>> if (!resuming) {
>> msgContext.addExecutedPhase(currentHandler);
>> } else {
>> /* If we are resuming the flow, we don't want to add
>> the phase
>> * again, as it has already been added.
>> */
>> resuming = false;
>> }
>> pi = currentHandler.invoke(msgContext);
>> }
>>
>>
>> ---
>>
>> [2].private static void flowComplete(MessageContext msgContext) {
>> Iterator invokedPhaseIterator =
>> msgContext.getExecutedPhases();
>>
>> while (invokedPhaseIterator.hasNext()) {
>> Handler currentHandler = ((Handler)
>> invokedPhaseIterator.next());
>> currentHandler.flowComplete(msgContext);
>> }
>>
>> /*This is needed because the OutInAxisOperation currently invokes
>> * receive() even when a fault occurs, and we will have already
>> executed
>> * the flowComplete on those before receiveFault() is called.
>> */
>> msgContext.resetExecutedPhases();
>> }
>>
>>
>>  a
>>
>>
>> /**
>>  * Add a Phase to the collection of executed phases for the path.
>>  * Phases will be inserted in a LIFO data structure.
>>  *
>>  * @param phase The phase to add to the list.
>>  */
>> public void addExecutedPhase(Handler phase) {
>> if (executedPhases == null) {
>> executedPhases = new LinkedList();
>> }
>> executedPhases.addFirst(phase);
>> }
>>
>> /**
>>  * Remove the first Phase in the collection of executed phases
>>  */
>> public void removeFirstExecutedPhase() {
>> if (executedPhases != null) {
>> executedPhases.removeFirst();
>> }
>> }
>>
>> 43/carbon/
>> [2012-11-29 10:55:45,570]  INFO - TimeoutHandler This engine will expire
>> all callbacks after : 120 seconds, irrespective of the timeout action,
>> after the specified or optional timeout
>> Listening for transport dt_socket at address: 
>> [2012-11-29 10:55:48,369] ERROR - NativeWorkerPool Uncaught exception
>> java.util.ConcurrentModificationException
>> at
>> java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:761)
>>  at java.util.LinkedList$ListItr.next(LinkedList.java:696)
>> at org.apache.axis2.engine.AxisEngine.flowComplete(AxisEngine.java:293)
>>  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:182)
>> at
>> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:217)
>>  at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>> 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:662)
>> [2012-11-29 10:55:55,462] ERROR - NativeWorkerPool Uncaught exception
>> java.util.ConcurrentModificationException
>> at
>> java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:761)
>>  at java.util.LinkedList$ListItr.next(LinkedList.java:696)
>> at org.apache.axis2.engine.AxisEngine.flowComplete(AxisEngine.java:293)
>>  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:182)
>> at
>> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:217)
>>  at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)

Re: [Dev] Registry.uddi build failure

[Kasun Indrasiri]

I'm also getting this while building the patch release.


On Tue, May 28, 2013 at 1:23 PM, Subash Chaturanga  wrote:

> Did you build up to date platform/dependencies/juddi and
> platform/dependencies/orbit/juddi ?
>
>
> On Tue, May 28, 2013 at 1:13 PM, Miyuru Wanninayaka wrote:
>
>> Please fix ASP
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>> (default-compile) on project org.wso2.carbon.registry.uddi: Compilation
>> failure: Compilation failure:
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[27,0]
>> package org.uddi.api_v3 does not exist
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[53,19]
>> cannot find symbol
>> [ERROR] symbol  : class AuthToken
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[64,49]
>> cannot find symbol
>> [ERROR] symbol  : class BusinessEntity
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[64,18]
>> cannot find symbol
>> [ERROR] symbol  : class BusinessDetail
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[87,55]
>> cannot find symbol
>> [ERROR] symbol  : class BusinessService
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[87,18]
>> cannot find symbol
>> [ERROR] symbol  : class ServiceDetail
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[112,42]
>> cannot find symbol
>> [ERROR] symbol  : class TModel
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[112,18]
>> cannot find symbol
>> [ERROR] symbol  : class TModelDetail
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[136,44]
>> cannot find symbol
>> [ERROR] symbol  : class FindBusiness
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[136,18]
>> cannot find symbol
>> [ERROR] symbol  : class BusinessList
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[233,19]
>> cannot find symbol
>> [ERROR] symbol  : class AuthToken
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/servlet/JUDDIRegistryServlet.java:[3,39]
>> package org.apache.commons.configuration does not exist
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[27,0]
>> package org.uddi.api_v3 does not exist
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[53,19]
>> cannot find symbol
>> [ERROR] symbol  : class AuthToken
>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> /home/miyuru/code/wso2/svn/carbon/platform/branche

Re: [Dev] Registry.uddi build failure

[Subash Chaturanga]

Hi
Can you now update org.wso2.carbon.registry.uddi/  and give it a try.

On Tue, May 28, 2013 at 2:21 PM, Kasun Indrasiri  wrote:

> I'm also getting this while building the patch release.
>
>
> On Tue, May 28, 2013 at 1:23 PM, Subash Chaturanga wrote:
>
>> Did you build up to date platform/dependencies/juddi and
>> platform/dependencies/orbit/juddi ?
>>
>>
>> On Tue, May 28, 2013 at 1:13 PM, Miyuru Wanninayaka wrote:
>>
>>> Please fix ASP
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>>> (default-compile) on project org.wso2.carbon.registry.uddi: Compilation
>>> failure: Compilation failure:
>>> [ERROR]
>>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[27,0]
>>> package org.uddi.api_v3 does not exist
>>> [ERROR]
>>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[53,19]
>>> cannot find symbol
>>> [ERROR] symbol  : class AuthToken
>>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>>> [ERROR]
>>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[64,49]
>>> cannot find symbol
>>> [ERROR] symbol  : class BusinessEntity
>>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>>> [ERROR]
>>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[64,18]
>>> cannot find symbol
>>> [ERROR] symbol  : class BusinessDetail
>>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>>> [ERROR]
>>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[87,55]
>>> cannot find symbol
>>> [ERROR] symbol  : class BusinessService
>>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>>> [ERROR]
>>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[87,18]
>>> cannot find symbol
>>> [ERROR] symbol  : class ServiceDetail
>>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>>> [ERROR]
>>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[112,42]
>>> cannot find symbol
>>> [ERROR] symbol  : class TModel
>>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>>> [ERROR]
>>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[112,18]
>>> cannot find symbol
>>> [ERROR] symbol  : class TModelDetail
>>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>>> [ERROR]
>>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[136,44]
>>> cannot find symbol
>>> [ERROR] symbol  : class FindBusiness
>>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>>> [ERROR]
>>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[136,18]
>>> cannot find symbol
>>> [ERROR] symbol  : class BusinessList
>>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>>> [ERROR]
>>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[233,19]
>>> cannot find symbol
>>> [ERROR] symbol  : class AuthToken
>>> [ERROR] location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>>> [ERROR]
>>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/servlet/JUDDIRegistryServlet.java:[3,39]
>>> package org.apache.commons.configuration does not exist
>>> [ERROR]
>>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUtil.java:[27,0]
>>> package org.uddi.api_v3 does not exist
>>> [ERROR]
>>> /home/miyuru/code/wso2/svn/carbon/platform/branches/4.1.0/components/registry/org.wso2.carbon.registry.uddi/4.1.3/src/main/java/org/wso2/carbon/registry/uddi/utils/UDDIUt

Re: [Dev] When unloaded tenant receives request session Id change in the second request.

[Kishanthan Thangarajah]

We use TanantLazyLoaderValve to load the tenant, if the first request is
coming for webapps. In here we catch the incoming request and load the
tenant and then do remap of request to let tomcat know about the new
contexts added, and the let the request reach the end point. So in here the
requestedSessionID may get change when doing the remap.

But as I verified, the session does not get change. You can do so by
invoking the Carbon Authentication Sample or Servlet Session sample in AS.
So the correct way here to use "request.getSession.getId()", which will
give you the correct result.

Please note that you have to put the this valve *after* CompositeValve in
the catalina-server.xml.

Thanks,
Kishanthan.


On Mon, May 27, 2013 at 4:42 PM, Geeth Munasinghe  wrote:

> Hi
>
> I am writing a component for AS to get web app requests statistics through
> BAM. This component publish requestSessionID in the  stream to BAM.
>
>
> I noticed the $subject few times. Tenant is unloaded after a certain time.
> But when I send a request to that tenant, it get loaded, and request is
> served with one session id. but for the next request, it gets a another
> session id. and all the other requests goes with the second session id.
>
>  Is this suppose happen or is there a bug in tenant loading ?
>
> thanks
> Geeth
>
>
>
>
>
> *G. K. S. Munasinghe
> *
> *Software Engineer,*
> *WSO2, Inc. http://wso2.com *
> *lean.enterprise.middleware.*
> *
> *
> email: ge...@wso2.com
> phone:(+94) 777911226
>



-- 
*Kishanthan Thangarajah*
Senior Software Engineer,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com*
Twitter - *http://twitter.com/kishanthan*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build failed in trunk - org.wso2.carbon:org.wso2.carbon.registry.extensions

[Hasini Gunasinghe]

Hi Vijitha,

I took svn up under both components/governance & components/registry. But
when trying to build platform/components, I still get the same error.

Thanks,
Hasini.


On Mon, May 27, 2013 at 11:05 PM, Vijitha Kumara  wrote:

> This is fixed, please update governance.registry.extensions component and
> build.
>
>
> On Mon, May 27, 2013 at 3:51 PM, Vijitha Kumara  wrote:
>
>> Running a new build in a clean repo, will check and update here.
>>
>>
>> On Mon, May 27, 2013 at 3:33 PM, Hasini Gunasinghe wrote:
>>
>>> Hi Vijitha,
>>>
>>> Still fails with the same error..
>>>
>>> Thanks,
>>>  Hasini.
>>>
>>>
>>> On Mon, May 27, 2013 at 3:10 PM, Vijitha Kumara wrote:
>>>
 There was an error in relative path, can you update and check now?


 On Mon, May 27, 2013 at 3:04 PM, Hasini Gunasinghe wrote:

> Same fails with following compilation error as well. Appreciate if
> this could be fixed.
>
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 2:30.573s
> [INFO] Finished at: Mon May 27 14:53:29 IST 2013
> [INFO] Final Memory: 682M/924M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project org.wso2.carbon.registry.extensions:
> Compilation failure: Compilation failure:
> [ERROR]
> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[433,14]
> cannot find symbol
> [ERROR] symbol  : class WADLProcessor
> [ERROR] location: class
> org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
> [ERROR]
> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[433,14]
> cannot find symbol
> [ERROR] symbol  : class WADLProcessor
> [ERROR] location: class
> org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
> [ERROR]
> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[265,20]
> cannot find symbol
> [ERROR] symbol  : class WADLProcessor
> [ERROR] location: class
> org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
> [ERROR]
> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[434,19]
> cannot find symbol
> [ERROR] symbol  : class WADLProcessor
> [ERROR] location: class
> org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
> [ERROR]
> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ZipWSDLMediaTypeHandler.java:[454,12]
> cannot find symbol
> [ERROR] symbol  : class WADLProcessor
> [ERROR] location: class
> org.wso2.carbon.registry.extensions.handlers.ZipWSDLMediaTypeHandler
> [ERROR]
> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ZipWSDLMediaTypeHandler.java:[454,46]
> cannot find symbol
> [ERROR] symbol  : class WADLProcessor
> [ERROR] location: class
> org.wso2.carbon.registry.extensions.handlers.ZipWSDLMediaTypeHandler
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
>  [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with
> the command
> [ERROR]   mvn  -rf :org.wso2.carbon.registry.extensions
>
> Thanks,
> Hasini.
>
> On Mon, May 27, 2013 at 2:49 PM, Hasini Gunasinghe wrote:
>
>> Hi,
>>
>> Trunk build failed with following error. Fixed with r173186. Please
>> verify.
>>
>> [INFO] Scanning for projects...
>> [ERROR] The build could not read 1 project -> [Help 1]
>> [ERROR]
>> [ERROR]   The project
>> org.wso2.carbon:org.wso2.carbon.registry.extensions:4.1.3
>> (/home/hasini/WSO2/CARBON_TRUNK/carbon/platfor

Re: [Dev] Build failed in trunk - org.wso2.carbon:org.wso2.carbon.registry.extensions

[Dulanja Liyanage]

Hi,

I'm also getting the same error.

Thanks
Dulanja


On Tue, May 28, 2013 at 2:43 PM, Hasini Gunasinghe  wrote:

> Hi Vijitha,
>
> I took svn up under both components/governance & components/registry. But
> when trying to build platform/components, I still get the same error.
>
> Thanks,
> Hasini.
>
>
> On Mon, May 27, 2013 at 11:05 PM, Vijitha Kumara  wrote:
>
>> This is fixed, please update governance.registry.extensions component and
>> build.
>>
>>
>> On Mon, May 27, 2013 at 3:51 PM, Vijitha Kumara  wrote:
>>
>>> Running a new build in a clean repo, will check and update here.
>>>
>>>
>>> On Mon, May 27, 2013 at 3:33 PM, Hasini Gunasinghe wrote:
>>>
 Hi Vijitha,

 Still fails with the same error..

 Thanks,
  Hasini.


 On Mon, May 27, 2013 at 3:10 PM, Vijitha Kumara wrote:

> There was an error in relative path, can you update and check now?
>
>
> On Mon, May 27, 2013 at 3:04 PM, Hasini Gunasinghe wrote:
>
>> Same fails with following compilation error as well. Appreciate if
>> this could be fixed.
>>
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 2:30.573s
>> [INFO] Finished at: Mon May 27 14:53:29 IST 2013
>> [INFO] Final Memory: 682M/924M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>> (default-compile) on project org.wso2.carbon.registry.extensions:
>> Compilation failure: Compilation failure:
>> [ERROR]
>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[433,14]
>> cannot find symbol
>> [ERROR] symbol  : class WADLProcessor
>> [ERROR] location: class
>> org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
>> [ERROR]
>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[433,14]
>> cannot find symbol
>> [ERROR] symbol  : class WADLProcessor
>> [ERROR] location: class
>> org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
>> [ERROR]
>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[265,20]
>> cannot find symbol
>> [ERROR] symbol  : class WADLProcessor
>> [ERROR] location: class
>> org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
>> [ERROR]
>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[434,19]
>> cannot find symbol
>> [ERROR] symbol  : class WADLProcessor
>> [ERROR] location: class
>> org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
>> [ERROR]
>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ZipWSDLMediaTypeHandler.java:[454,12]
>> cannot find symbol
>> [ERROR] symbol  : class WADLProcessor
>> [ERROR] location: class
>> org.wso2.carbon.registry.extensions.handlers.ZipWSDLMediaTypeHandler
>> [ERROR]
>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ZipWSDLMediaTypeHandler.java:[454,46]
>> cannot find symbol
>> [ERROR] symbol  : class WADLProcessor
>> [ERROR] location: class
>> org.wso2.carbon.registry.extensions.handlers.ZipWSDLMediaTypeHandler
>> [ERROR] -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>>  [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with
>> the command
>> [ERROR]   mvn  -rf :org.wso2.carbon.registry.extensions
>>
>> Thanks,
>> Hasini.
>>
>> On Mon, May 27, 2013 at 2:49 PM, Hasini Gunasinghe 
>> wrote:
>>
>>> Hi,
>>>
>>> Trunk build failed with following error. Fixed with r173186. Please
>>> verify.
>>>
>>> [INFO] Scann

Re: [Dev] When unloaded tenant receives request session Id change in the second request.

[Geeth Munasinghe]

Hi Kishanthan

Problem solved after using "request.getSession.getId()" to get the session
id.

Thanks

*G. K. S. Munasinghe
*
*Software Engineer,*
*WSO2, Inc. http://wso2.com *
*lean.enterprise.middleware.*
*
*
email: ge...@wso2.com
phone:(+94) 777911226


On Tue, May 28, 2013 at 2:40 PM, Kishanthan Thangarajah  wrote:

> We use TanantLazyLoaderValve to load the tenant, if the first request is
> coming for webapps. In here we catch the incoming request and load the
> tenant and then do remap of request to let tomcat know about the new
> contexts added, and the let the request reach the end point. So in here the
> requestedSessionID may get change when doing the remap.
>
> But as I verified, the session does not get change. You can do so by
> invoking the Carbon Authentication Sample or Servlet Session sample in AS.
> So the correct way here to use "request.getSession.getId()", which will
> give you the correct result.
>
> Please note that you have to put the this valve *after* CompositeValve in
> the catalina-server.xml.
>
> Thanks,
> Kishanthan.
>
>
> On Mon, May 27, 2013 at 4:42 PM, Geeth Munasinghe  wrote:
>
>> Hi
>>
>> I am writing a component for AS to get web app requests statistics
>> through BAM. This component publish requestSessionID in the  stream to BAM.
>>
>>
>> I noticed the $subject few times. Tenant is unloaded after a certain
>> time. But when I send a request to that tenant, it get loaded, and request
>> is served with one session id. but for the next request, it gets a another
>> session id. and all the other requests goes with the second session id.
>>
>>  Is this suppose happen or is there a bug in tenant loading ?
>>
>> thanks
>> Geeth
>>
>>
>>
>>
>>
>> *G. K. S. Munasinghe
>> *
>> *Software Engineer,*
>> *WSO2, Inc. http://wso2.com *
>> *lean.enterprise.middleware.*
>> *
>> *
>> email: ge...@wso2.com
>> phone:(+94) 777911226
>>
>
>
>
> --
> *Kishanthan Thangarajah*
> Senior Software Engineer,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com*
> Twitter - *http://twitter.com/kishanthan*
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [APPFAC][AS] upgrading appfac live with AS 5.1.0

[Asanka Dissanayake]

Hi All,
Appfactory staging is successfully upgraded with AS 5.1.0.We are about to
upgrade the Appfac live with the same.
Following Gdoc contains the steps to follow for the upgrade

https://docs.google.com/a/wso2.com/document/d/1xu1jEyZPbyzU5kmMGz6h_u42CYItM6F5kuOZe2nwl-4/edit?usp=sharing

Please find the required jars in the following link
https://svn.wso2.com/wso2/custom/projects/projects/afdeployment/weekly_patches/27May/AS-upgrade-502to510/

@manula.
Please suggest a feasible time


-- 

*Asanka Dissanayake
Software Engineer*
*WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
*
email: asan...@wso2.com ,   blog:
cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94 71
8373821*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Que about JSON Message builder and formatters.

[Vijayaratha Vijayasingam]

Hi,

We have JSONMessageFormatter/builder,JSONBadgerfishMessageFormatter/builder
and JSONStreamFormatter/builder.
In which case we need to use,"JSONStreamFormatter/builder" ?
If the answer is for complex/multiroot json, then how can we do mediation
with that?

tahnks
-Ratha
mobile: (+94)755906608
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] ESB 4.7.0 Alpha Pack for Testing (28/05/2013)

[Ravi Undupitiya]

Please find $subject at [1] - feature complete alpha pack.

[1]
https://svn.wso2.org/repos/wso2/people/ravi/packs/20130528-wso2esb-4.7.0.zip



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.7.0 Alpha Pack for Testing (28/05/2013)

[Shashika Ubhayaratne]

Hi,

Can you send us the fixed issue list to verify.

However, we'll start verifying new features.

Thanks,
Shashika

Shashika Ubhayaratne
Associate Technical Lead - QA
WSO2 Inc: http://www.wso2.com/
Mobile: *+94773383831*


On Tue, May 28, 2013 at 4:17 PM, Ravi Undupitiya  wrote:

> Please find $subject at [1] - feature complete alpha pack.
>
> [1]
> https://svn.wso2.org/repos/wso2/people/ravi/packs/20130528-wso2esb-4.7.0.zip
>
>
>
> --
> *Ravi Undupitiya*
> Software Engineer; WSO2 Inc.; http://wso2.com
> *
> *
> *E-mail: r...@wso2.com
> **M: **+94 772 930 712*
> *
> *Lean . Enterprise . Middleware
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Appfactory] Timeout occurred when a tenant is logged for the first time in ESB instance.

[Shamika Ariyawansa]

Hi

This timeout occurs when calling  creatingConfigurationContext method of
the the following class.


org.wso2.carbon.event.core.internal.builder.EventAxis2ConfigurationContextObserver

This call is one of 20 osgi calls. All the others returned with maximum of
1 s but this one takes about 2 mins.





On Tue, May 28, 2013 at 10:32 AM, Kishanthan Thangarajah <
kishant...@wso2.com> wrote:

>
>
>
> On Tue, May 28, 2013 at 5:05 AM, Dimuthu Leelarathne wrote:
>
>> Hi Shamika,
>>
>> Did we try to put logs in "private static ConfigurationContext
>> createTenantConfigurationContext" in TenantAxisUtils ? We need to put debug
>> logs along the path and see what takes all the time?
>>
>
> We did put some debug logs at there as-well. But that was not the issue
> when we investigated it. The issue is, it takes 2mins for the login action
> to return and then the call comes to this method. The issue should be
> before this. So I believe we should investigate on that path.
>
> @Shamika, can you share the latest logs which explains the
> above observation?
>
>
>
>> thanks,
>> dimuthu
>>
>>
>> On Tue, May 28, 2013 at 2:38 AM, Shamika Ariyawansa wrote:
>>
>>> Hi,
>>>
>>> Following observation was made wrt the ESB 4.6.0 instance which was
>>> spawned from the S2 ESB cartridge.
>>>
>>> 1. When the tenant user is logged for the first time the page keeps on
>>> loading and after few minutes the page gets timeout
>>> Refer the following log.
>>>
>>> TID: [0] [ESB] [2013-05-27 06:10:16,510]  INFO
>>> {org.wso2.carbon.appfactory.userstore.AppFactoryRealmConfigBuilder} -  Get
>>> the tenant ( tenant id=142) detlail.
>>> {org.wso2.carbon.appfactory.userstore.AppFactoryRealmConfigBuilder}
>>> TID: [0] [ESB] [2013-05-27 06:10:16,522]  INFO
>>> {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} -  LDAP
>>> connection created successfully in read-write mode
>>> {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager}
>>> TID: [0] [ESB] [2013-05-27 06:10:16,561]  INFO
>>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
>>> to mount at config in 3ms
>>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
>>> TID: [0] [ESB] [2013-05-27 06:10:16,690]  INFO
>>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
>>> to mount at governance in 2ms
>>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
>>> TID: [0] [ESB] [2013-05-27 06:10:16,819]  INFO
>>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
>>>  'ad...@admin.com@proximit_esb_1 [142]' logged in at [2013-05-27
>>> 06:10:16,818-0700]
>>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil}
>>> TID: [0] [ESB] [2013-05-27 06:12:17,207] DEBUG
>>> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSyncAxis2ConfigurationContextObserver}
>>> -  Initializing the deployment synchronizer for tenant: 142
>>> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSyncAxis2ConfigurationContextObserver}
>>> TID: [0] [ESB] [2013-05-27 06:12:17,456]  INFO
>>> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer} -
>>>  Doing initial sync up...
>>> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer}
>>> TID: [0] [ESB] [2013-05-27 06:12:17,456]  INFO
>>> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer} -
>>>  Checking out...
>>> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer}
>>> TID: [0] [ESB] [2013-05-27 06:12:17,456] DEBUG
>>> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer} -
>>>  Started checkout to /mnt/
>>> 10.98.175.203/wso2esb-4.6.0/repository/tenants/142 {org.w
>>>
>>>
>>> The time gap between the highlighted parts is more than two minutes.
>>>
>>> 2. After that first attempt (which was unsuccessful due to timeout) the
>>> second attempt for the same tenant logs into the
>>> system successfully without any delays. Deployment synchronization was also
>>> happened correctly.
>>>
>>> Any idea why this error happened in the first attempt?
>>>
>>> Thanks
>>> --
>>> Shamika Ariyawansa
>>> Senior Software Engineer
>>>
>>> Mob:+ 94 772929486
>>>
>>
>>
>>
>> --
>> Dimuthu Leelarathne
>> Architect & Chair of Solution Management Committee
>>
>> WSO2, Inc. (http://wso2.com)
>> email: dimut...@wso2.com
>> Mobile : 0773661935
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> *Kishanthan Thangarajah*
> Senior Software Engineer,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com*
> Twitter - *http://twitter.com/kishanthan*
>



-- 
Shamika Ariyawansa
Senior Software Engineer

Mob:+ 94 772929486
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.7.0 Alpha Pack for Testing (28/05/2013)

[Kasun Indrasiri]

Please verify the new features added to 4.7. All features contains
integration tests along with their documentation/samples.




On Tue, May 28, 2013 at 4:23 PM, Shashika Ubhayaratne wrote:

> Hi,
>
> Can you send us the fixed issue list to verify.
>
> However, we'll start verifying new features.
>
> Thanks,
> Shashika
>
> Shashika Ubhayaratne
> Associate Technical Lead - QA
> WSO2 Inc: http://www.wso2.com/
> Mobile: *+94773383831*
>
>
> On Tue, May 28, 2013 at 4:17 PM, Ravi Undupitiya  wrote:
>
>> Please find $subject at [1] - feature complete alpha pack.
>>
>> [1]
>> https://svn.wso2.org/repos/wso2/people/ravi/packs/20130528-wso2esb-4.7.0.zip
>>
>>
>>
>> --
>> *Ravi Undupitiya*
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> *
>> *
>> *E-mail: r...@wso2.com
>> **M: **+94 772 930 712*
>> *
>> *Lean . Enterprise . Middleware
>>
>
>


-- 
Kasun Indrasiri
Associate Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +94 71 536 4128
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.7.0 Alpha Pack for Testing (28/05/2013)

[Shashika Ubhayaratne]

Hi Kasun,

I couldn't find any documents/ samples for following features and have
raised jira.
1. Supporting POX messages with text/xml content type -
https://wso2.org/jira/browse/ESBJAVA-1929
2. Restore the default Main and Fault Sequences when a C-App is undeployed -
* **https://wso2.org/jira/browse/ESBJAVA-1930*
3.Stabilize Registry Based Deployment Synchronizer -
https://wso2.org/jira/browse/ESBJAVA-1931

Refer the "
https://docs.google.com/a/wso2.com/document/d/1YUUOPB-Xg58XmH5FcftA_rdcwONxy37WqyIOHOV1qRo/edit#";
for details.

Thanks,
Shashika

Shashika Ubhayaratne
Associate Technical Lead - QA
WSO2 Inc: http://www.wso2.com/
Mobile: *+94773383831*


On Tue, May 28, 2013 at 4:27 PM, Kasun Indrasiri  wrote:

> Please verify the new features added to 4.7. All features contains
> integration tests along with their documentation/samples.
>
>
>
>
> On Tue, May 28, 2013 at 4:23 PM, Shashika Ubhayaratne 
> wrote:
>
>> Hi,
>>
>> Can you send us the fixed issue list to verify.
>>
>> However, we'll start verifying new features.
>>
>> Thanks,
>> Shashika
>>
>> Shashika Ubhayaratne
>> Associate Technical Lead - QA
>> WSO2 Inc: http://www.wso2.com/
>> Mobile: *+94773383831*
>>
>>
>> On Tue, May 28, 2013 at 4:17 PM, Ravi Undupitiya  wrote:
>>
>>> Please find $subject at [1] - feature complete alpha pack.
>>>
>>> [1]
>>> https://svn.wso2.org/repos/wso2/people/ravi/packs/20130528-wso2esb-4.7.0.zip
>>>
>>>
>>>
>>> --
>>> *Ravi Undupitiya*
>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>> *
>>> *
>>> *E-mail: r...@wso2.com
>>> **M: **+94 772 930 712*
>>> *
>>> *Lean . Enterprise . Middleware
>>>
>>
>>
>
>
> --
> Kasun Indrasiri
> Associate Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.7.0 Alpha Pack for Testing (28/05/2013)

[Shashika Ubhayaratne]

Hi,

Also, Please update document/ sample for "Connection throttling of incoming
connections in PTT/NHTTP" - https://wso2.org/jira/browse/ESBJAVA-1942

Thanks,
Shashika

Shashika Ubhayaratne
Associate Technical Lead - QA
WSO2 Inc: http://www.wso2.com/
Mobile: *+94773383831*


On Tue, May 28, 2013 at 4:37 PM, Shashika Ubhayaratne wrote:

> Hi Kasun,
>
> I couldn't find any documents/ samples for following features and have
> raised jira.
> 1. Supporting POX messages with text/xml content type -
> https://wso2.org/jira/browse/ESBJAVA-1929
> 2. Restore the default Main and Fault Sequences when a C-App is
> undeployed -* **https://wso2.org/jira/browse/ESBJAVA-1930*
> 3.Stabilize Registry Based Deployment Synchronizer -
> https://wso2.org/jira/browse/ESBJAVA-1931
>
> Refer the "
> https://docs.google.com/a/wso2.com/document/d/1YUUOPB-Xg58XmH5FcftA_rdcwONxy37WqyIOHOV1qRo/edit#";
> for details.
>
> Thanks,
> Shashika
>
> Shashika Ubhayaratne
> Associate Technical Lead - QA
> WSO2 Inc: http://www.wso2.com/
> Mobile: *+94773383831*
>
>
> On Tue, May 28, 2013 at 4:27 PM, Kasun Indrasiri  wrote:
>
>> Please verify the new features added to 4.7. All features contains
>> integration tests along with their documentation/samples.
>>
>>
>>
>>
>> On Tue, May 28, 2013 at 4:23 PM, Shashika Ubhayaratne 
>> wrote:
>>
>>> Hi,
>>>
>>> Can you send us the fixed issue list to verify.
>>>
>>> However, we'll start verifying new features.
>>>
>>> Thanks,
>>> Shashika
>>>
>>> Shashika Ubhayaratne
>>> Associate Technical Lead - QA
>>> WSO2 Inc: http://www.wso2.com/
>>> Mobile: *+94773383831*
>>>
>>>
>>> On Tue, May 28, 2013 at 4:17 PM, Ravi Undupitiya  wrote:
>>>
>>>> Please find $subject at [1] - feature complete alpha pack.
>>>>
>>>> [1]
>>>> https://svn.wso2.org/repos/wso2/people/ravi/packs/20130528-wso2esb-4.7.0.zip
>>>>
>>>>
>>>>
>>>> --
>>>> *Ravi Undupitiya*
>>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>>> *
>>>> *
>>>> *E-mail: r...@wso2.com
>>>> **M: **+94 772 930 712*
>>>> *
>>>> *Lean . Enterprise . Middleware
>>>>
>>>
>>>
>>
>>
>> --
>> Kasun Indrasiri
>> Associate Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 71 536 4128
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.7.0 Alpha Pack for Testing (28/05/2013)

[Kasun Indrasiri]

Above changes won't affects the docs. Please refer those jiras for more
details.
Resolved.


On Tue, May 28, 2013 at 4:37 PM, Shashika Ubhayaratne wrote:

> Hi Kasun,
>
> I couldn't find any documents/ samples for following features and have
> raised jira.
> 1. Supporting POX messages with text/xml content type -
> https://wso2.org/jira/browse/ESBJAVA-1929
> 2. Restore the default Main and Fault Sequences when a C-App is
> undeployed -* **https://wso2.org/jira/browse/ESBJAVA-1930*
> 3.Stabilize Registry Based Deployment Synchronizer -
> https://wso2.org/jira/browse/ESBJAVA-1931
>
> Refer the "
> https://docs.google.com/a/wso2.com/document/d/1YUUOPB-Xg58XmH5FcftA_rdcwONxy37WqyIOHOV1qRo/edit#";
> for details.
>
> Thanks,
> Shashika
>
> Shashika Ubhayaratne
> Associate Technical Lead - QA
> WSO2 Inc: http://www.wso2.com/
> Mobile: *+94773383831*
>
>
> On Tue, May 28, 2013 at 4:27 PM, Kasun Indrasiri  wrote:
>
>> Please verify the new features added to 4.7. All features contains
>> integration tests along with their documentation/samples.
>>
>>
>>
>>
>> On Tue, May 28, 2013 at 4:23 PM, Shashika Ubhayaratne 
>> wrote:
>>
>>> Hi,
>>>
>>> Can you send us the fixed issue list to verify.
>>>
>>> However, we'll start verifying new features.
>>>
>>> Thanks,
>>> Shashika
>>>
>>> Shashika Ubhayaratne
>>> Associate Technical Lead - QA
>>> WSO2 Inc: http://www.wso2.com/
>>> Mobile: *+94773383831*
>>>
>>>
>>> On Tue, May 28, 2013 at 4:17 PM, Ravi Undupitiya  wrote:
>>>
>>>> Please find $subject at [1] - feature complete alpha pack.
>>>>
>>>> [1]
>>>> https://svn.wso2.org/repos/wso2/people/ravi/packs/20130528-wso2esb-4.7.0.zip
>>>>
>>>>
>>>>
>>>> --
>>>> *Ravi Undupitiya*
>>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>>> *
>>>> *
>>>> *E-mail: r...@wso2.com
>>>> **M: **+94 772 930 712*
>>>> *
>>>> *Lean . Enterprise . Middleware
>>>>
>>>
>>>
>>
>>
>> --
>> Kasun Indrasiri
>> Associate Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 71 536 4128
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>


-- 
Kasun Indrasiri
Associate Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +94 71 536 4128
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.7.0 Alpha Pack for Testing (28/05/2013)

[Shashika Ubhayaratne]

Hi,

We'll start verifying Highest Priority tests first.
1. Native Support for JSON & Improve RESTful service integration
*
*
Thanks
Shashika

Shashika Ubhayaratne
Associate Technical Lead - QA
WSO2 Inc: http://www.wso2.com/
Mobile: *+94773383831*


On Tue, May 28, 2013 at 5:06 PM, Kasun Indrasiri  wrote:

> Above changes won't affects the docs. Please refer those jiras for more
> details.
> Resolved.
>
>
> On Tue, May 28, 2013 at 4:37 PM, Shashika Ubhayaratne 
> wrote:
>
>> Hi Kasun,
>>
>> I couldn't find any documents/ samples for following features and have
>> raised jira.
>> 1. Supporting POX messages with text/xml content type -
>> https://wso2.org/jira/browse/ESBJAVA-1929
>> 2. Restore the default Main and Fault Sequences when a C-App is
>> undeployed -* **https://wso2.org/jira/browse/ESBJAVA-1930*
>> 3.Stabilize Registry Based Deployment Synchronizer -
>> https://wso2.org/jira/browse/ESBJAVA-1931
>>
>> Refer the "
>> https://docs.google.com/a/wso2.com/document/d/1YUUOPB-Xg58XmH5FcftA_rdcwONxy37WqyIOHOV1qRo/edit#";
>> for details.
>>
>> Thanks,
>> Shashika
>>
>> Shashika Ubhayaratne
>> Associate Technical Lead - QA
>> WSO2 Inc: http://www.wso2.com/
>> Mobile: *+94773383831*
>>
>>
>> On Tue, May 28, 2013 at 4:27 PM, Kasun Indrasiri  wrote:
>>
>>> Please verify the new features added to 4.7. All features contains
>>> integration tests along with their documentation/samples.
>>>
>>>
>>>
>>>
>>> On Tue, May 28, 2013 at 4:23 PM, Shashika Ubhayaratne >> > wrote:
>>>
>>>> Hi,
>>>>
>>>> Can you send us the fixed issue list to verify.
>>>>
>>>> However, we'll start verifying new features.
>>>>
>>>> Thanks,
>>>> Shashika
>>>>
>>>> Shashika Ubhayaratne
>>>> Associate Technical Lead - QA
>>>> WSO2 Inc: http://www.wso2.com/
>>>> Mobile: *+94773383831*
>>>>
>>>>
>>>> On Tue, May 28, 2013 at 4:17 PM, Ravi Undupitiya  wrote:
>>>>
>>>>> Please find $subject at [1] - feature complete alpha pack.
>>>>>
>>>>> [1]
>>>>> https://svn.wso2.org/repos/wso2/people/ravi/packs/20130528-wso2esb-4.7.0.zip
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Ravi Undupitiya*
>>>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>>>> *
>>>>> *
>>>>> *E-mail: r...@wso2.com
>>>>> **M: **+94 772 930 712*
>>>>> *
>>>>> *Lean . Enterprise . Middleware
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Kasun Indrasiri
>>> Associate Technical Lead
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 71 536 4128
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>
>>
>
>
> --
> Kasun Indrasiri
> Associate Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Que about JSON Message builder and formatters.

[Ishan Jayawardena]

Hi Ratha,
When to use;
(A) When you need to avoid these conversions,
 JSON->XML->JSON
 JSON<-XML<-JSON

ie. 1) when both client/backend consume JSON and you need to manipulate
the message as a JSON object (set, create, transform, query etc.) within
ESB with script mediator
2) when both client/backend consume JSON and you need to pass the
message through the ESB (supports Natural JSON, JSON array objects, JSON
objects with many keys)
3) when you need better performance than what you get with default
builder/formatter

(B) When client and backend consume different message types(XML, JSON) and
expect different message formats (see sample 441)

Under (1) and (B), to do mediation, use functions available in script
message context.
mc.getPayloadJSON()
mc.setPayloadJSON()
mc.getPayloadXML()
mc.setPayloadXML()

example:



On Tue, May 28, 2013 at 4:09 PM, Vijayaratha Vijayasingam
wrote:

> Hi,
>
> We
> have JSONMessageFormatter/builder,JSONBadgerfishMessageFormatter/builder
> and JSONStreamFormatter/builder.
> In which case we need to use,"JSONStreamFormatter/builder" ?
> If the answer is for complex/multiroot json, then how can we do mediation
> with that?
>
> tahnks
> -Ratha
> mobile: (+94)755906608
>

Thanks,
Ishan.


-- 
Ishan Jayawardena
Software Engineer
Mobile: +94 (77) 408 2330
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Appfactory] Timeout occurred when a tenant is logged for the first time in ESB instance.

[Dimuthu Leelarathne]

Hi Srinath,

Why would the following take so much time? Can ESB run without it?

thanks,
dimuthu

On Tue, May 28, 2013 at 4:25 PM, Shamika Ariyawansa wrote:

> Hi
>
> This timeout occurs when calling  creatingConfigurationContext method of
> the the following class.
>
>
> org.wso2.carbon.event.core.internal.builder.EventAxis2ConfigurationContextObserver
>
> This call is one of 20 osgi calls. All the others returned with maximum of
> 1 s but this one takes about 2 mins.
>
>
>
>
>
> On Tue, May 28, 2013 at 10:32 AM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>>
>>
>>
>> On Tue, May 28, 2013 at 5:05 AM, Dimuthu Leelarathne 
>> wrote:
>>
>>> Hi Shamika,
>>>
>>> Did we try to put logs in "private static ConfigurationContext
>>> createTenantConfigurationContext" in TenantAxisUtils ? We need to put debug
>>> logs along the path and see what takes all the time?
>>>
>>
>> We did put some debug logs at there as-well. But that was not the issue
>> when we investigated it. The issue is, it takes 2mins for the login action
>> to return and then the call comes to this method. The issue should be
>> before this. So I believe we should investigate on that path.
>>
>> @Shamika, can you share the latest logs which explains the
>> above observation?
>>
>>
>>
>>> thanks,
>>> dimuthu
>>>
>>>
>>> On Tue, May 28, 2013 at 2:38 AM, Shamika Ariyawansa wrote:
>>>
 Hi,

 Following observation was made wrt the ESB 4.6.0 instance which was
 spawned from the S2 ESB cartridge.

 1. When the tenant user is logged for the first time the page keeps on
 loading and after few minutes the page gets timeout
 Refer the following log.

 TID: [0] [ESB] [2013-05-27 06:10:16,510]  INFO
 {org.wso2.carbon.appfactory.userstore.AppFactoryRealmConfigBuilder} -  Get
 the tenant ( tenant id=142) detlail.
 {org.wso2.carbon.appfactory.userstore.AppFactoryRealmConfigBuilder}
 TID: [0] [ESB] [2013-05-27 06:10:16,522]  INFO
 {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} -  LDAP
 connection created successfully in read-write mode
 {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager}
 TID: [0] [ESB] [2013-05-27 06:10:16,561]  INFO
 {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
 to mount at config in 3ms
 {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
 TID: [0] [ESB] [2013-05-27 06:10:16,690]  INFO
 {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
 to mount at governance in 2ms
 {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
 TID: [0] [ESB] [2013-05-27 06:10:16,819]  INFO
 {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
  'ad...@admin.com@proximit_esb_1 [142]' logged in at [2013-05-27
 06:10:16,818-0700]
 {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil}
 TID: [0] [ESB] [2013-05-27 06:12:17,207] DEBUG
 {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSyncAxis2ConfigurationContextObserver}
 -  Initializing the deployment synchronizer for tenant: 142
 {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSyncAxis2ConfigurationContextObserver}
 TID: [0] [ESB] [2013-05-27 06:12:17,456]  INFO
 {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer} -
  Doing initial sync up...
 {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer}
 TID: [0] [ESB] [2013-05-27 06:12:17,456]  INFO
 {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer} -
  Checking out...
 {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer}
 TID: [0] [ESB] [2013-05-27 06:12:17,456] DEBUG
 {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer} -
  Started checkout to /mnt/
 10.98.175.203/wso2esb-4.6.0/repository/tenants/142 {org.w


 The time gap between the highlighted parts is more than two minutes.

 2. After that first attempt (which was unsuccessful due to timeout) the
 second attempt for the same tenant logs into the
 system successfully without any delays. Deployment synchronization was also
 happened correctly.

 Any idea why this error happened in the first attempt?

 Thanks
 --
 Shamika Ariyawansa
 Senior Software Engineer

 Mob:+ 94 772929486

>>>
>>>
>>>
>>> --
>>> Dimuthu Leelarathne
>>> Architect & Chair of Solution Management Committee
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: dimut...@wso2.com
>>> Mobile : 0773661935
>>>
>>> Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>> *Kishanthan Thangarajah*
>> Senior Software Engineer,
>> Platform Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com*
>> Twitter - *http://twitter.com/kishanthan*
>>
>
>
>
> --
> Shamika Ariyawansa
> Senior Software Eng

Re: [Dev] Que about JSON Message builder and formatters.

[Vijayaratha Vijayasingam]

Thanks ishan..


On 28 May 2013 17:12, Ishan Jayawardena  wrote:

> Hi Ratha,
> When to use;
> (A) When you need to avoid these conversions,
>  JSON->XML->JSON
>  JSON<-XML<-JSON
>
> ie. 1) when both client/backend consume JSON and you need to
> manipulate the message as a JSON object (set, create, transform, query
> etc.) within ESB with script mediator
> 2) when both client/backend consume JSON and you need to pass the
> message through the ESB (supports Natural JSON, JSON array objects, JSON
> objects with many keys)
> 3) when you need better performance than what you get with default
> builder/formatter
>
> (B) When client and backend consume different message types(XML, JSON) and
> expect different message formats (see sample 441)
>
> Under (1) and (B), to do mediation, use functions available in script
> message context.
> mc.getPayloadJSON()
> mc.setPayloadJSON()
> mc.getPayloadXML()
> mc.setPayloadXML()
>
> example:
>  var request = mc.getPayloadJSON();
>
> for (i = 0; i < request.length; ++i) {
> delete request[i].position.marketAnalysisAvailable;
> delete request[i].position.lockingDMAWOId;
> delete request[i].market.alertsAllowed;
> delete request[i].market.viewPermission;
> delete request[i].market.editable;
> }
>
> mc.setPayloadJSON(request);
>
> ]]>
>
>
> On Tue, May 28, 2013 at 4:09 PM, Vijayaratha Vijayasingam  > wrote:
>
>> Hi,
>>
>> We
>> have JSONMessageFormatter/builder,JSONBadgerfishMessageFormatter/builder
>> and JSONStreamFormatter/builder.
>> In which case we need to use,"JSONStreamFormatter/builder" ?
>> If the answer is for complex/multiroot json, then how can we do mediation
>> with that?
>>
>> tahnks
>> -Ratha
>> mobile: (+94)755906608
>>
>
> Thanks,
> Ishan.
>
>
> --
> Ishan Jayawardena
> Software Engineer
> Mobile: +94 (77) 408 2330
>



-- 
-Ratha
mobile: (+94)755906608
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Fwd: [Appfactory] Upgrade the jaggary version used in AF

[Ajanthan Balachandran]

All the problems are fixed now.Thanks Manuranga.

-- Forwarded message --
From: Ajanthan Balachandran 
Date: Tue, May 28, 2013 at 11:21 AM
Subject: Re: [Dev] [Appfactory] Upgrade the jaggary version used in AF
To: Nuwan Bandara 





On Tue, May 28, 2013 at 10:53 AM, Nuwan Bandara  wrote:

> why do you guys put Geronimo in endorsed ? will fix the pom version issues.
>
It is coming from  Kernel.We don't put.In previous jaggery version also it
is avoided by commenting out importBundleDef[0].
One more problem, In RegistryHostObject.java[1]

private static UserRegistry getRegistry(String username, String password)
throws ScriptException { UserRegistry registry; RegistryService
registryService = RegistryHostObjectContext.getRegistryService(); String
tDomain; try { tDomain = username.split("@")[1]; } catch
(ArrayIndexOutOfBoundsException e) { //if tenant domain is not present in
the username we treat is as a super user tDomain = "carbon.super"; } try {
int tId =
RegistryHostObjectContext.getRealmService().getTenantManager().getTenantId(tDomain);
registry = registryService.getGovernanceUserRegistry(username, password,
tId); } catch (Exception e) { log.error(e.getMessage(), e); throw new
ScriptException(e); } if (registry == null) { String msg = "User governance
registry cannot be retrieved"; throw new ScriptException(msg); } return
registry; }
This function is used to initialize the registry hostsObject.But above
method did not handle email username.(In AF we have ad...@admin.com,so for
this user registry access fails with "The tenant is not active. tenant id:
-1." )
Shall we fix this?
Thanks

>
> Regards,
> /Nuwan
>
>
> On Tue, May 28, 2013 at 10:38 AM, Ajanthan Balachandran  > wrote:
>
>> More problems ..
>> Through jaggery geronimo-stax-api_1.0_spec-1.0.1.wso2v2.jar
>> is coming into plugins folder but we have it already in endorsed
>> directory.We have to disable it in feature pom.xml.
>>
>>
>> On Tue, May 28, 2013 at 10:32 AM, Ajanthan Balachandran <
>> ajant...@wso2.com> wrote:
>>
>>> Hi
>>> Where did you guys  get the code? jaggery is looking for
>>> META-INF/scripts/xml.js while loading modules but in jaggery core package
>>>  only http.js is there xml.js is missing.
>>> Thanks
>>>
>>>
>>> On Tue, May 28, 2013 at 10:06 AM, Ajanthan Balachandran <
>>> ajant...@wso2.com> wrote:
>>>
 Hi,
 Is 
 0.9.0.ALPHA3-wso2v6
  correctly
 branched? I can see 0.9.0-SNAPSHOT inside all
 pom.xml.
 Thanks.


 On Tue, May 21, 2013 at 10:25 AM, Ramith Jayasinghe wrote:

> Corrected the folder structure.
>
>
> On Mon, May 20, 2013 at 11:37 AM, Ramith Jayasinghe 
> wrote:
>
>> Hi Manu,
>>
>> it seems
>>
>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/dependencies/jaggery/0.9.0.ALPHA2-wso2v6
>> contains pom.xml with a version : 0.9.0.ALPHA3-wso2v6
>> that seems incorrect.
>>
>> regards
>> Ramith.
>>
>>
>> On Fri, May 17, 2013 at 6:44 PM, Manuranga Perera wrote:
>>
>>> please update to latest version, which is wso2v6 when you do.
>>> if you are building this locally, you have to build patch releases
>>> [2] at orbit level first.
>>>
>>> [1]
>>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/dependencies/jaggery/0.9.0.ALPHA2-wso2v6
>>> [2]
>>> https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.1.0/patch-releases/4.1.2
>>>
>>>
>>> On Fri, May 17, 2013 at 3:40 PM, Ramith Jayasinghe 
>>> wrote:
>>>
 Nope. we will try this locally (with a pack) before putting it into
 staging.


 On Fri, May 17, 2013 at 3:30 PM, Manjula Rathnayake <
 manju...@wso2.com> wrote:

> Hi Ramith,
>
> +1,
> Have we tried this already in staging setup? I think it should be
> straight forward if no API changes are done.
>
> thank you.
>
>
> On Fri, May 17, 2013 at 3:26 PM, Ramith Jayasinghe <
> ram...@wso2.com> wrote:
>
>> correction:
>> from 0.9.0.ALPHA2-wso2v4 to 0.9.0.ALPHA2-wso2v5.
>>
>>
>> On Fri, May 17, 2013 at 3:25 PM, Ramith Jayasinghe <
>> ram...@wso2.com> wrote:
>>
>>> Hi,
>>> As the part of effort to improve the performance of AF UI we are
>>> going to upgrade the jaggery from version : 0.9.0.ALPHA2-wso2v3 to
>>> 0.9.0.ALPHA2-wso2v5.
>>> regards
>>> Ramith
>>>
>>
>>
>>
>> --
>> Ramith Jayasinghe
>> Technical Lead
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> E: ram...@wso2.com
>> P: +94 776715671
>>
>>
>> __

Re: [Dev] platform/branches/4.1.0/dependencies/orbit/juddi/3.1.5-wso2v1/pom.xml has 1 error

[Lahiru Sandaruwan]

Hi Subash,

"dependencies/orbit/juddi/3.1.5-wso2v1/pom.xml" points to a non-existing
parent pom.

Thanks.


On Mon, May 27, 2013 at 4:52 PM, Subash Chaturanga  wrote:

> Hi
> Have you updated dependencies/juddi and dependencies/orbit/juddi both. and
> try to build dependencies again.
>
> On Mon, May 27, 2013 at 12:32 PM, Punnadi Gunarathna wrote:
>
>> Hi,
>>
>> I cannot build
>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/dependencies/orbit/juddi/3.1.5-wso2v1as
>>  it gives the below error:
>>
>> The project org.apache.juddi.wso2:juddi:3.1.5.wso2v1
>> (/home/punnadi/wso2/source/platform/4.1.0/dependencies/orbit/juddi/3.1.5-wso2v1/pom.xml)
>> has 1 error
>> [ERROR] Non-resolvable parent POM: Could not find artifact
>> org.wso2.carbon:carbon-dependents:pom:4.1.0 in central (
>> http://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
>> wrong local POM @ line 22, column 13 -> [Help 2]
>>
>> I was able to correct it by replacing the below changes:
>>
>>  
>> org.wso2.carbon
>> carbon-dependents
>> 4.1.0
>> ../../../pom.xml
>>  
>>
>> --
>> Thanks and Regards,
>>
>> Punnadi Gunarathna
>> Senior Software Engineer, WSO2, Inc.; http://wso2.com 
>> email: punn...@wso2.com 
>>
>>  
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks
> /subash
>
> *Subash Chaturanga*
> Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com
>
> email: sub...@wso2.com
> blog:  http://subashsdm.blogspot.com/
> twitter: @subash89
> phone: +9477 2225922
> Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

email: lahi...@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Stratos2] 2.0.0 RC1 Fixes

[Nirmal Fernando]

Committed the modified patches and updated the JIRAs. IsuruP, please verify
and resolve the JIRAs.


On Tue, May 28, 2013 at 9:01 AM, Isuru Perera  wrote:

> Hi Nirmal,
>
> I have attached more patches to following JIRAs
>
>
> https://wso2.org/jira/browse/SPI-176
> https://wso2.org/jira/browse/SPI-179
> https://wso2.org/jira/browse/SPI-250
>
> The patches also fixes following JIRAs.
> https://wso2.org/jira/browse/SPI-236
> https://wso2.org/jira/browse/SPI-263
> https://wso2.org/jira/browse/SPI-255
> https://wso2.org/jira/browse/SPI-265
>
> As I have informed you earlier, could you also please delete following.
>
> *In org.wso2.carbon.adc.mgt/2.1.3:*
>
>
> src/main/java/org/wso2/carbon/adc/mgt/exception/ADCRegistryResourceException.java
>
> src/main/java/org/wso2/carbon/adc/mgt/internal/HostingManagementServiceComponent.java
> src/test/java/org/wso2/carbon/hosting
>
> *In org.wso2.carbon.adc.mgt.cli/2.1.3:
> *
> src/main/java/org/wso2/carbon/adc/mgt/cli/HelpPrinter.java
> src/main/java/org/wso2/carbon/adc/mgt/cli/ParsedCliCommandManager.java
>
> src/main/java/org/wso2/carbon/adc/mgt/cli/clients/BasicAuthApplicationManagementServiceClient.java
> src/main/java/org/wso2/carbon/adc/mgt/cli/parsers
> src/main/java/org/wso2/carbon/adc/mgt/cli/parsers/AbstractParser.java
> src/main/java/org/wso2/carbon/adc/mgt/cli/parsers/ArrayParser.java
> src/main/java/org/wso2/carbon/adc/mgt/cli/parsers/LineParser.java
>
>
> *In org.wso2.carbon.cartridge.mgt.ui/2.1.3:*
>
> src/main/java/org/wso2/carbon/cartridge/mgt/ui/CartridgeConstans.java
> src/main/resources/web/cartridge-mgt/list.jsp
>
> Thanks!
>
>
> On Thu, May 23, 2013 at 8:20 PM, Lakmal Warusawithana wrote:
>
>> Great wrok Isuru!!!
>>
>>
>> On Thu, May 23, 2013 at 8:16 PM, Nirmal Fernando  wrote:
>>
>>> Great work, IsuruP. Will commit the fixes soon.
>>>
>>> Sent via my mobile
>>> -- Nirmal --
>>> On May 23, 2013 6:34 PM, "Isuru Perera"  wrote:
>>>
>>> Hi Nirmal,
>>>
>>> I fixed following issues for 2.0.0 RC1.
>>>
>>> https://wso2.org/jira/browse/SPI-148
>>> https://wso2.org/jira/browse/SPI-176
>>> https://wso2.org/jira/browse/SPI-179
>>> https://wso2.org/jira/browse/SPI-239
>>> https://wso2.org/jira/browse/SPI-250
>>> https://wso2.org/jira/browse/SPI-251
>>>
>>> I have attached the patches in following JIRAs. I appreciate if you can
>>> commit those! :)
>>>
>>> https://wso2.org/jira/browse/SPI-176
>>> https://wso2.org/jira/browse/SPI-179
>>> https://wso2.org/jira/browse/SPI-250
>>>
>>> Please revert any changes before apply patches
>>>
>>> As you requested, for SPI-179 issue, I have added an ajax loading image
>>> and I refresh the table using jQuery every 10 seconds.
>>>
>>> Could you please test and let me know whether the fix is okay. You need
>>> to build following components and copy to SC.
>>>
>>> org.wso2.carbon.adc.mgt:2.1.3
>>> org.wso2.carbon.adc.mgt.stub:4.1.3
>>> org.wso2.carbon.cartridge.mgt.ui:2.1.3
>>>
>>> Thanks.
>>>
>>> PS: Please note, please build the CLI if you want to test that also! :)
>>>
>>> --
>>> Isuru Perera
>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> Twitter: http://twitter.com/chrishantha | LinkedIn:
>>> http://lk.linkedin.com/in/chrishantha/
>>>
>>>
>>
>>
>> --
>> Lakmal Warusawithana
>> Software Architect; WSO2 Inc.
>> Mobile : +94714289692
>>
>>
>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> Twitter: http://twitter.com/chrishantha | LinkedIn:
> http://lk.linkedin.com/in/chrishantha/
>



-- 

Thanks & regards,
Nirmal

Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] StartupFinalizerServiceComponent Waiting for required OSGi services issue

[Nuwan Dias]

Hi,

This is regarding [1]. We have been doing some long running tests on a lab
setup. The test was done on the API Gateway. But when attempted to restart
the API Gateway server, the following issue has been occurring.

*WARN - StartupFinalizerServiceComponent Waiting for required OSGi services:
*
*
 
org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService,org.wso2.carbon.server.admin.common.IServerAdmin,org.wso2.carbon.throttling.agent.ThrottlingAgent,
*

This delays the server startup significantly. What can be the cause of this?

Some points to note are that this is not reproducable in any other setups
other than this specific lab setup. The Gateway is running on a machine
which is 90% disk full and AFAIR there were some other servers running too.
The server was killed with a kill -9 while it was still receiving requests
and I assume that restart had been attempted while the client was still
sending requests to the server.

Any hints on how we could tackle this?

[1] - https://wso2.org/jira/browse/APIMANAGER-1321

-- 
Nuwan Dias

Member, Management Committee - Solutions Technology Group
Senior Software Engineer - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] StartupFinalizerServiceComponent Waiting for required OSGi services issue

[Afkham Azeez]

On Tue, May 28, 2013 at 7:48 PM, Nuwan Dias  wrote:

> Hi,
>
> This is regarding [1]. We have been doing some long running tests on a lab
> setup. The test was done on the API Gateway. But when attempted to restart
> the API Gateway server, the following issue has been occurring.
>
> *WARN - StartupFinalizerServiceComponent Waiting for required OSGi
> services:*
> *
>  
> org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService,org.wso2.carbon.server.admin.common.IServerAdmin,org.wso2.carbon.throttling.agent.ThrottlingAgent,
> *
>

>
> This delays the server startup significantly. What can be the cause of
> this?
>

You need to figure out why the  *SynapseEnvironmentService OSGi service is
taking a long time to load. Running this with JProfiler may give you a clue
as to where the time is spent most.*

>
> Some points to note are that this is not reproducable in any other setups
> other than this specific lab setup. The Gateway is running on a machine
> which is 90% disk full and AFAIR there were some other servers running too.
> The server was killed with a kill -9 while it was still receiving requests
> and I assume that restart had been attempted while the client was still
> sending requests to the server.
>
> Any hints on how we could tackle this?
>
> [1] - https://wso2.org/jira/browse/APIMANAGER-1321
>
> --
> Nuwan Dias
>
> Member, Management Committee - Solutions Technology Group
> Senior Software Engineer - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 
*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*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] platform/branches/4.1.0/dependencies/orbit/juddi/3.1.5-wso2v1/pom.xml has 1 error

[Subash Chaturanga]

On Tue, May 28, 2013 at 7:00 PM, Lahiru Sandaruwan  wrote:

> Hi Subash,
>
> "dependencies/orbit/juddi/3.1.5-wso2v1/pom.xml" points to a non-existing
> parent pom.
>

Fixed. Please update the pom.

>
> Thanks.
>
>
> On Mon, May 27, 2013 at 4:52 PM, Subash Chaturanga wrote:
>
>> Hi
>> Have you updated dependencies/juddi and dependencies/orbit/juddi both.
>> and try to build dependencies again.
>>
>> On Mon, May 27, 2013 at 12:32 PM, Punnadi Gunarathna wrote:
>>
>>> Hi,
>>>
>>> I cannot build
>>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/dependencies/orbit/juddi/3.1.5-wso2v1as
>>>  it gives the below error:
>>>
>>> The project org.apache.juddi.wso2:juddi:3.1.5.wso2v1
>>> (/home/punnadi/wso2/source/platform/4.1.0/dependencies/orbit/juddi/3.1.5-wso2v1/pom.xml)
>>> has 1 error
>>> [ERROR] Non-resolvable parent POM: Could not find artifact
>>> org.wso2.carbon:carbon-dependents:pom:4.1.0 in central (
>>> http://repo.maven.apache.org/maven2) and 'parent.relativePath' points
>>> at wrong local POM @ line 22, column 13 -> [Help 2]
>>>
>>> I was able to correct it by replacing the below changes:
>>>
>>>  
>>> org.wso2.carbon
>>> carbon-dependents
>>> 4.1.0
>>> ../../../pom.xml
>>>  
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Punnadi Gunarathna
>>> Senior Software Engineer, WSO2, Inc.; http://wso2.com 
>>> email: punn...@wso2.com 
>>>
>>>  
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks
>> /subash
>>
>> *Subash Chaturanga*
>> Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com
>>
>> email: sub...@wso2.com
>> blog:  http://subashsdm.blogspot.com/
>> twitter: @subash89
>> phone: +9477 2225922
>> Lean . Enterprise . Middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahi...@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>


-- 
Thanks
/subash

*Subash Chaturanga*
Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com

email: sub...@wso2.com
blog:  http://subashsdm.blogspot.com/
twitter: @subash89
phone: +9477 2225922
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to reconnect to a topic publisher automatically?

[Nirmal Fernando]

Hi Shammi,

This still fails to me. When I shutdown the server where the topic lives, I
see following error [1].

Note that what I'm using is a Topic.

And my client is at [2], am I doing something wrong?

[1]

TID: [0] [ELB] [2013-05-28 15:12:47,589] ERROR
{org.wso2.andes.client.state.AMQStateManager} -  No Waiters for error
saving as last error:Exception thrown against AMQConnection:
Host: cc.wso2.com
Port: 5673
Virtual Host: carbon
Client ID: clientID
Active session count: 1: org.wso2.andes.AMQDisconnectedException: Server
closed connection and reconnection not permitted.
{org.wso2.andes.client.state.AMQStateManager}
TID: [0] [ELB] [2013-05-28 15:12:47,590] ERROR
{org.wso2.andes.client.AMQConnection} -  Throwable Received but no listener
set: org.wso2.andes.AMQDisconnectedException: Server closed connection and
reconnection not permitted. {org.wso2.andes.client.AMQConnection}

[2]

Properties initialContextProperties = new Properties();
initialContextProperties.put("java.naming.factory.initial",
"org.wso2.andes.jndi.PropertiesFileInitialContextFactory");

String mbServerUrl = null;
if (ConfigHolder.getInstance().getLbConfig() != null) {
mbServerUrl =
ConfigHolder.getInstance().getLbConfig().getLoadBalancerConfig().getMbServerUrl();
}
String connectionString =
"amqp://admin:admin@clientID/carbon?brokerlist='tcp://" +
(mbServerUrl == null ?
TopologyConstants.DEFAULT_MB_SERVER_URL : mbServerUrl) +
"'&reconnect='true'";

initialContextProperties.put("connectionfactory.qpidConnectionfactory",
connectionString);

try {
InitialContext initialContext = new
InitialContext(initialContextProperties);
TopicConnectionFactory topicConnectionFactory =
(TopicConnectionFactory)
initialContext.lookup("qpidConnectionfactory");
TopicConnection topicConnection =
topicConnectionFactory.createTopicConnection();
topicConnection.start();
TopicSession topicSession =
topicConnection.createTopicSession(false,
Session.AUTO_ACKNOWLEDGE);

Topic topic = topicSession.createTopic(topicName);
TopicSubscriber topicSubscriber =
topicSession.createSubscriber(topic);

topicSubscriber.setMessageListener(new TopologyListener());

} catch (NamingException e) {
log.error(e.getMessage(), e);
} catch (JMSException e) {
log.error(e.getMessage(), e);
}



On Mon, May 27, 2013 at 10:46 PM, Nirmal Fernando  wrote:

> Great... Thanks a lot Shammi!! I'll try this.
>
>
> On Mon, May 27, 2013 at 10:44 PM, Shammi Jayasinghe wrote:
>
>> Hi Nirmal,
>>
>> It seems the problem is with your connection URL. The way you have
>> created the connection string should be as bellow[1]. I have checked and
>> verified the the re-connection of the subscriber with the following client
>> code[2].
>>
>> [1]
>>String connectionString = "amqp://admin:admin@clientID
>> /carbon?brokerlist='tcp://localhost:5672'&reconnect='true'";
>>
>> [2]
>> Properties initialContextProperties = new Properties();
>> initialContextProperties.put("java.naming.factory.initial",
>>
>> "org.wso2.andes.jndi.PropertiesFileInitialContextFactory");
>> String connectionString = "amqp://admin:admin@clientID
>> /carbon?brokerlist='tcp://localhost:5672'&reconnect='true'";
>>
>> initialContextProperties.put("connectionfactory.qpidConnectionfactory",
>> connectionString);
>> String queueName = "bar";
>> initialContextProperties.put("queue."+queueName, queueName);
>>
>>
>> try {
>> InitialContext initialContext = new
>> InitialContext(initialContextProperties);
>> ConnectionFactory queueConnectionFactory
>> = (ConnectionFactory)
>> initialContext.lookup("qpidConnectionfactory");
>> Destination destination = (Destination)
>> initialContext.lookup(queueName);
>> int count = 0;
>>
>> Connection queueConnection =
>> queueConnectionFactory.createConnection();
>> queueConnection.start();
>>
>>
>> try {
>> Session queueSession =
>> queueConnection.createSession(false, QueueSession.AUTO_ACKNOWLEDGE);
>>
>>
>> MessageConsumer messageConsumer =
>> queueSession.createConsumer(destination);
>> while (true) {
>>
>> try {
>> TextMessage textMessage = (TextMessage)
>> messageConsumer.receive();
>> if (textMessage != null) {
>> textMessage.getJMSRedelivered();
>> System.out.println("textMessage = " +
>> textMessage);
>> System.out.println("got the message = " +
>> count);
>> System.out.println("ReceivedTime = " +
>> System.currentTimeMillis());
>> 

[Dev] Build fails at branch 4.1.3

[Lahiru Sandaruwan]

$subject, Any thing missed?

Error,

[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 5:35.403s
[INFO] Finished at: Tue May 28 21:41:50 IST 2013
[INFO] Final Memory: 534M/953M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project org.wso2.carbon.registry.indexing: Compilation
failure: Compilation failure:
[ERROR]
/home/lahiru/work/carbonSource/branch4/platform/4.1.0/components/registry/org.wso2.carbon.registry.indexing/4.1.3/src/main/java/org/wso2/carbon/registry/indexing/service/ContentBasedSearchService.java:[118,41]
cannot find symbol
[ERROR] symbol  : method getLimit()
[ERROR] location: class
org.wso2.carbon.registry.core.utils.PaginationContext
[ERROR]
/home/lahiru/work/carbonSource/branch4/platform/4.1.0/components/registry/org.wso2.carbon.registry.indexing/4.1.3/src/main/java/org/wso2/carbon/registry/indexing/service/ContentBasedSearchService.java:[118,106]
cannot find symbol
[ERROR] symbol  : method getLimit()
[ERROR] location: class
org.wso2.carbon.registry.core.utils.PaginationContext
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :org.wso2.carbon.registry.indexing


Thanks.

-- 
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

email: lahi...@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Stratos2] 2.0.0 RC1 Fixes

[Isuru Perera]

Thanks Nirmal! I will verify and resolve.

--
Sent from my mobile
On May 28, 2013 7:15 PM, "Nirmal Fernando"  wrote:

> Committed the modified patches and updated the JIRAs. IsuruP, please
> verify and resolve the JIRAs.
>
>
> On Tue, May 28, 2013 at 9:01 AM, Isuru Perera  wrote:
>
>> Hi Nirmal,
>>
>> I have attached more patches to following JIRAs
>>
>>
>> https://wso2.org/jira/browse/SPI-176
>> https://wso2.org/jira/browse/SPI-179
>> https://wso2.org/jira/browse/SPI-250
>>
>> The patches also fixes following JIRAs.
>> https://wso2.org/jira/browse/SPI-236
>> https://wso2.org/jira/browse/SPI-263
>> https://wso2.org/jira/browse/SPI-255
>> https://wso2.org/jira/browse/SPI-265
>>
>> As I have informed you earlier, could you also please delete following.
>>
>> *In org.wso2.carbon.adc.mgt/2.1.3:*
>>
>>
>> src/main/java/org/wso2/carbon/adc/mgt/exception/ADCRegistryResourceException.java
>>
>> src/main/java/org/wso2/carbon/adc/mgt/internal/HostingManagementServiceComponent.java
>> src/test/java/org/wso2/carbon/hosting
>>
>> *In org.wso2.carbon.adc.mgt.cli/2.1.3:
>> *
>> src/main/java/org/wso2/carbon/adc/mgt/cli/HelpPrinter.java
>> src/main/java/org/wso2/carbon/adc/mgt/cli/ParsedCliCommandManager.java
>>
>> src/main/java/org/wso2/carbon/adc/mgt/cli/clients/BasicAuthApplicationManagementServiceClient.java
>> src/main/java/org/wso2/carbon/adc/mgt/cli/parsers
>> src/main/java/org/wso2/carbon/adc/mgt/cli/parsers/AbstractParser.java
>> src/main/java/org/wso2/carbon/adc/mgt/cli/parsers/ArrayParser.java
>> src/main/java/org/wso2/carbon/adc/mgt/cli/parsers/LineParser.java
>>
>>
>> *In org.wso2.carbon.cartridge.mgt.ui/2.1.3:*
>>
>> src/main/java/org/wso2/carbon/cartridge/mgt/ui/CartridgeConstans.java
>> src/main/resources/web/cartridge-mgt/list.jsp
>>
>> Thanks!
>>
>>
>> On Thu, May 23, 2013 at 8:20 PM, Lakmal Warusawithana wrote:
>>
>>> Great wrok Isuru!!!
>>>
>>>
>>> On Thu, May 23, 2013 at 8:16 PM, Nirmal Fernando wrote:
>>>
 Great work, IsuruP. Will commit the fixes soon.

 Sent via my mobile
 -- Nirmal --
 On May 23, 2013 6:34 PM, "Isuru Perera"  wrote:

 Hi Nirmal,

 I fixed following issues for 2.0.0 RC1.

 https://wso2.org/jira/browse/SPI-148
 https://wso2.org/jira/browse/SPI-176
 https://wso2.org/jira/browse/SPI-179
 https://wso2.org/jira/browse/SPI-239
 https://wso2.org/jira/browse/SPI-250
 https://wso2.org/jira/browse/SPI-251

 I have attached the patches in following JIRAs. I appreciate if you can
 commit those! :)

 https://wso2.org/jira/browse/SPI-176
 https://wso2.org/jira/browse/SPI-179
 https://wso2.org/jira/browse/SPI-250

 Please revert any changes before apply patches

 As you requested, for SPI-179 issue, I have added an ajax loading image
 and I refresh the table using jQuery every 10 seconds.

 Could you please test and let me know whether the fix is okay. You need
 to build following components and copy to SC.

 org.wso2.carbon.adc.mgt:2.1.3
 org.wso2.carbon.adc.mgt.stub:4.1.3
 org.wso2.carbon.cartridge.mgt.ui:2.1.3

 Thanks.

 PS: Please note, please build the CLI if you want to test that also! :)

 --
 Isuru Perera
 Senior Software Engineer | WSO2, Inc. | http://wso2.com/
 Lean . Enterprise . Middleware

 Twitter: http://twitter.com/chrishantha | LinkedIn:
 http://lk.linkedin.com/in/chrishantha/


>>>
>>>
>>> --
>>> Lakmal Warusawithana
>>> Software Architect; WSO2 Inc.
>>> Mobile : +94714289692
>>>
>>>
>>
>>
>> --
>> Isuru Perera
>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> Twitter: http://twitter.com/chrishantha | LinkedIn:
>> http://lk.linkedin.com/in/chrishantha/
>>
>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] StartupFinalizerServiceComponent Waiting for required OSGi services issue

[Sumedha Rubasinghe]

On Tue, May 28, 2013 at 7:51 PM, Afkham Azeez  wrote:

>
>
> On Tue, May 28, 2013 at 7:48 PM, Nuwan Dias  wrote:
>
>> Hi,
>>
>> This is regarding [1]. We have been doing some long running tests on a
>> lab setup. The test was done on the API Gateway. But when attempted to
>> restart the API Gateway server, the following issue has been occurring.
>>
>> *WARN - StartupFinalizerServiceComponent Waiting for required OSGi
>> services:*
>> *
>>  
>> org.wso2.carbon.mediation.initializer.services.SynapseEnvironmentService,org.wso2.carbon.server.admin.common.IServerAdmin,org.wso2.carbon.throttling.agent.ThrottlingAgent,
>> *
>>
>
>>
>> This delays the server startup significantly. What can be the cause of
>> this?
>>
>
> You need to figure out why the  *SynapseEnvironmentService OSGi service
> is taking a long time to load. Running this with JProfiler may give you a
> clue as to where the time is spent most.*
>

What I suspected was the local H2 database. But it was a guess & not based
on profiler analysis.

>
>> Some points to note are that this is not reproducable in any other setups
>> other than this specific lab setup. The Gateway is running on a machine
>> which is 90% disk full and AFAIR there were some other servers running too.
>> The server was killed with a kill -9 while it was still receiving requests
>> and I assume that restart had been attempted while the client was still
>> sending requests to the server.
>>
>> Any hints on how we could tackle this?
>>
>> [1] - https://wso2.org/jira/browse/APIMANAGER-1321
>>
>> --
>> Nuwan Dias
>>
>> Member, Management Committee - Solutions Technology Group
>> Senior Software Engineer - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
> *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*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
/sumedha
m: +94 773017743
b :  bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Need occasional DepSync polling or depsync message replay

[Shariq Muhammed]

On Fri, May 24, 2013 at 11:19 PM, Afkham Azeez  wrote:

>
>
> On Sat, May 25, 2013 at 11:37 AM, Supun Malinga  wrote:
>
>>  --
>> Supun Malinga
>> Sent from my phone.
>>
>> On 24 May 2013 02:37, "Afkham Azeez"  wrote:
>> >
>> > There is no guarantee that the cluster message will be reliably
>> delivered to all members. For instance, due to a momentary network delay or
>> delay in the node, other members may detect that a member has left, but in
>> reality, that member may be still running. If a cluster message, such as a
>> DepSync message is sent in such a scenario, the node will not receive that
>> message, and may never update its deployment repo.
>>
>> Hi azeez,
>>
>> I understand the requirement and the need. But if the clustering has
>> failed(member dropped) means that node will no longer receive load from the
>> load balancer right?
>>
>
> There can be momentary failures due to delays in the nodes or network.
> When this happens, nodes will detect that the member has left. However,
> later, when the nodes become reachable again, they will be added back to
> the cluster. They would have missed message which were received during the
> time they were removed from the cluster. The solution would be to replay
> selected messages from the past 5 minutes to any new node that joins.
>

Something I've noticed is, say we deploy a webapp to a 3 node cluster and
only 2 nodes get the cluster message, then when we access the webapp from
UI, somehow the LB send the request to the node that hasn't been updated
and hence we see the old webapp. This is kinda a nasty situation :) ..
Wonder if there a mechanism other than cluster message, like subscribe to a
queue and poll periodically.

On a side note though, as NuwanD mentioned in a production env, we wont be
updating artifacts so frequently, that's also something that should be
taken into consideration, as in defining the deployment ...


>
>> >
>> > We could implement one of the following solutions;
>> > 1. For selected cluster messages, we could replay them if a new member
>> becomes available. We can't blindly replay all messages, but replaying the
>> depsync message will cause no harm because the depsync operation is
>> idempotent
>> >
>> > 2. For depsync, we can have periodic polling, but the polling interval
>> should vary from about 1 minute to 5 minutes.
>> >
>> > --
>> > 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
>> >
>> > ___
>> > Dev mailing list
>> > Dev@wso2.org
>> > http://wso2.org/cgi-bin/mailman/listinfo/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*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks,
Shariq.
Phone: +94 777 202 225
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Appfactory] Timeout occurred when a tenant is logged for the first time in ESB instance.

[Shamika Ariyawansa]

Hi,

This is occurred when authorizing user roles for the the topics
in org.wso2.carbon.event.core component

for (String role : userRealm.getUserStoreManager().getRoleNames()) {
userRealm.getAuthorizationManager().authorizeRole(
role, topicStoragePath,
EventBrokerConstants.EB_PERMISSION_SUBSCRIBE);
userRealm.getAuthorizationManager().authorizeRole(
role, topicStoragePath,
EventBrokerConstants.EB_PERMISSION_PUBLISH);
}

There are 6 roles in appfac (dev,qa, devops etc) and this authorization for
the topic is done for each role, which takes apprx 2 mins time.

As a solution a patch is introduced such that not to authorize these roles
if no topic is set in event-broker.xml.

Thanks


On Tue, May 28, 2013 at 5:12 PM, Dimuthu Leelarathne wrote:

> Hi Srinath,
>
> Why would the following take so much time? Can ESB run without it?
>
> thanks,
> dimuthu
>
> On Tue, May 28, 2013 at 4:25 PM, Shamika Ariyawansa wrote:
>
>> Hi
>>
>> This timeout occurs when calling  creatingConfigurationContext method of
>> the the following class.
>>
>>
>> org.wso2.carbon.event.core.internal.builder.EventAxis2ConfigurationContextObserver
>>
>> This call is one of 20 osgi calls. All the others returned with maximum
>> of 1 s but this one takes about 2 mins.
>>
>>
>>
>>
>>
>> On Tue, May 28, 2013 at 10:32 AM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>>
>>>
>>>
>>> On Tue, May 28, 2013 at 5:05 AM, Dimuthu Leelarathne 
>>> wrote:
>>>
 Hi Shamika,

 Did we try to put logs in "private static ConfigurationContext
 createTenantConfigurationContext" in TenantAxisUtils ? We need to put debug
 logs along the path and see what takes all the time?

>>>
>>> We did put some debug logs at there as-well. But that was not the issue
>>> when we investigated it. The issue is, it takes 2mins for the login action
>>> to return and then the call comes to this method. The issue should be
>>> before this. So I believe we should investigate on that path.
>>>
>>> @Shamika, can you share the latest logs which explains the
>>> above observation?
>>>
>>>
>>>
 thanks,
 dimuthu


 On Tue, May 28, 2013 at 2:38 AM, Shamika Ariyawansa 
 wrote:

> Hi,
>
> Following observation was made wrt the ESB 4.6.0 instance which was
> spawned from the S2 ESB cartridge.
>
> 1. When the tenant user is logged for the first time the page keeps on
> loading and after few minutes the page gets timeout
> Refer the following log.
>
> TID: [0] [ESB] [2013-05-27 06:10:16,510]  INFO
> {org.wso2.carbon.appfactory.userstore.AppFactoryRealmConfigBuilder} -  Get
> the tenant ( tenant id=142) detlail.
> {org.wso2.carbon.appfactory.userstore.AppFactoryRealmConfigBuilder}
> TID: [0] [ESB] [2013-05-27 06:10:16,522]  INFO
> {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} -  LDAP
> connection created successfully in read-write mode
> {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager}
> TID: [0] [ESB] [2013-05-27 06:10:16,561]  INFO
> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
> to mount at config in 3ms
> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
> TID: [0] [ESB] [2013-05-27 06:10:16,690]  INFO
> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
> to mount at governance in 2ms
> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
> TID: [0] [ESB] [2013-05-27 06:10:16,819]  INFO
> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
>  'ad...@admin.com@proximit_esb_1 [142]' logged in at [2013-05-27
> 06:10:16,818-0700]
> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil}
> TID: [0] [ESB] [2013-05-27 06:12:17,207] DEBUG
> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSyncAxis2ConfigurationContextObserver}
> -  Initializing the deployment synchronizer for tenant: 142
> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSyncAxis2ConfigurationContextObserver}
> TID: [0] [ESB] [2013-05-27 06:12:17,456]  INFO
> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer} 
> -
>  Doing initial sync up...
> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer}
> TID: [0] [ESB] [2013-05-27 06:12:17,456]  INFO
> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer} 
> -
>  Checking out...
> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer}
> TID: [0] [ESB] [2013-05-27 06:12:17,456] DEBUG
> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer} 
> -
>  Started checkout to /mnt/
> 10.98.175.203/wso2esb-4.6.0/repository/tenants/142 {org.w
>
>
> The time gap between the highlighted par

Re: [Dev] [Appfactory] Timeout occurred when a tenant is logged for the first time in ESB instance.

[Dimuthu Leelarathne]

Hi Shamika,


On Wed, May 29, 2013 at 1:17 AM, Shamika Ariyawansa wrote:

> Hi,
>
> This is occurred when authorizing user roles for the the topics
> in org.wso2.carbon.event.core component
>
> for (String role : userRealm.getUserStoreManager().getRoleNames()) {
> userRealm.getAuthorizationManager().authorizeRole(
> role, topicStoragePath,
> EventBrokerConstants.EB_PERMISSION_SUBSCRIBE);
> userRealm.getAuthorizationManager().authorizeRole(
> role, topicStoragePath,
> EventBrokerConstants.EB_PERMISSION_PUBLISH);
> }
>
> There are 6 roles in appfac (dev,qa, devops etc) and this authorization
> for the topic is done for each role, which takes apprx 2 mins time.
>
>
Went through the code. If there are 6 calls, this will generate 24 database
calls. How?

6 (roles) * 2 (calling authorize twice here) * 2 (we have 2 db calls in one
authorize method, 4.1.0 code this is reduced to 1)

As a fix for event.core we can avoid all of these db calls if check
isAuthorized before adding permission. Why? Because permissions are cached.
That way it will be slow only in the first tenant load, even then when ESB
is released with 4.1.0 kernel it will only have 12 db calls. So only 1
minute.

thanks,
dimuthu


> As a solution a patch is introduced such that not to authorize these roles
> if no topic is set in event-broker.xml.
>
> Thanks
>
>
> On Tue, May 28, 2013 at 5:12 PM, Dimuthu Leelarathne wrote:
>
>> Hi Srinath,
>>
>> Why would the following take so much time? Can ESB run without it?
>>
>> thanks,
>> dimuthu
>>
>> On Tue, May 28, 2013 at 4:25 PM, Shamika Ariyawansa wrote:
>>
>>> Hi
>>>
>>> This timeout occurs when calling  creatingConfigurationContext method of
>>> the the following class.
>>>
>>>
>>> org.wso2.carbon.event.core.internal.builder.EventAxis2ConfigurationContextObserver
>>>
>>> This call is one of 20 osgi calls. All the others returned with maximum
>>> of 1 s but this one takes about 2 mins.
>>>
>>>
>>>
>>>
>>>
>>> On Tue, May 28, 2013 at 10:32 AM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>



 On Tue, May 28, 2013 at 5:05 AM, Dimuthu Leelarathne >>> > wrote:

> Hi Shamika,
>
> Did we try to put logs in "private static ConfigurationContext
> createTenantConfigurationContext" in TenantAxisUtils ? We need to put 
> debug
> logs along the path and see what takes all the time?
>

 We did put some debug logs at there as-well. But that was not the issue
 when we investigated it. The issue is, it takes 2mins for the login action
 to return and then the call comes to this method. The issue should be
 before this. So I believe we should investigate on that path.

 @Shamika, can you share the latest logs which explains the
 above observation?



> thanks,
> dimuthu
>
>
> On Tue, May 28, 2013 at 2:38 AM, Shamika Ariyawansa 
> wrote:
>
>> Hi,
>>
>> Following observation was made wrt the ESB 4.6.0 instance which was
>> spawned from the S2 ESB cartridge.
>>
>> 1. When the tenant user is logged for the first time the page keeps
>> on loading and after few minutes the page gets timeout
>> Refer the following log.
>>
>> TID: [0] [ESB] [2013-05-27 06:10:16,510]  INFO
>> {org.wso2.carbon.appfactory.userstore.AppFactoryRealmConfigBuilder} -  
>> Get
>> the tenant ( tenant id=142) detlail.
>> {org.wso2.carbon.appfactory.userstore.AppFactoryRealmConfigBuilder}
>> TID: [0] [ESB] [2013-05-27 06:10:16,522]  INFO
>> {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} -  LDAP
>> connection created successfully in read-write mode
>> {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager}
>> TID: [0] [ESB] [2013-05-27 06:10:16,561]  INFO
>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
>> to mount at config in 3ms
>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
>> TID: [0] [ESB] [2013-05-27 06:10:16,690]  INFO
>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
>> to mount at governance in 2ms
>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
>> TID: [0] [ESB] [2013-05-27 06:10:16,819]  INFO
>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
>>  'ad...@admin.com@proximit_esb_1 [142]' logged in at [2013-05-27
>> 06:10:16,818-0700]
>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil}
>> TID: [0] [ESB] [2013-05-27 06:12:17,207] DEBUG
>> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSyncAxis2ConfigurationContextObserver}
>> -  Initializing the deployment synchronizer for tenant: 142
>> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSyncAxis2ConfigurationContextObserver}
>> TID: [0] [ESB] [2013-05-27 06:1

Re: [Dev] BAM 2.3.0 RC is ready for QA

[Samisa Abeysinghe]

BAM still have 17 L2s. I hope we are planning to fix them all. We cannot
release with L2s open!


On Tue, May 28, 2013 at 11:14 AM, Chamara Ariyarathne wrote:

> Testing is in Progress.
>
> Me, Shavantha and Ashan is involved.
>
>
> On Mon, May 27, 2013 at 11:28 PM, Malith Dhanushka wrote:
>
>> Hi QA Team,
>>
>> Please find the BAM 2.3.0 RC pack for QA testing and other 4.1.2 release
>> artifacts at [1].
>>
>> These were built with a clean repo with test enabled from the revision
>> 173244.
>>
>> [1] http://173.164.178.33/builds/BAM-2.3.0/releasepacks/
>>
>> Thanks,
>> Malith
>>
>> --
>> Malith Dhanushka
>>
>> Engineer - Data Technologies
>> *WSO2, Inc. : wso2.com*
>> lean.enterprise.middleware.
>>
>> *Blog* :  mmalithh.blogspot.com
>> *Linked-i*n  :   http://lk.linkedin.com/in/malithd
>> *Twitter* :   https://twitter.com/MalithWD
>>
>> *Mobile*  : +94 716 506 693
>>
>
>
>
> --
> *Chamara Ariyarathne*
> Senior Software Engineer - QA;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; *+94772786766*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Thanks,
Samisa...

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

Re: [Dev] [Appfactory] Timeout occurred when a tenant is logged for the first time in ESB instance.

[Dimuthu Leelarathne]

Hi Shamika,

Fixed the event.core to check authorizations before adding them. Now the
tenant loading will be faster from the second-time onwards. Meanwhile
created a JIRA to do a proper long term fix.

https://wso2.org/jira/browse/MB-269

thanks,
dimuthu

On Wed, May 29, 2013 at 5:43 AM, Dimuthu Leelarathne wrote:

> Hi Shamika,
>
>
> On Wed, May 29, 2013 at 1:17 AM, Shamika Ariyawansa wrote:
>
>> Hi,
>>
>> This is occurred when authorizing user roles for the the topics
>> in org.wso2.carbon.event.core component
>>
>> for (String role : userRealm.getUserStoreManager().getRoleNames()) {
>> userRealm.getAuthorizationManager().authorizeRole(
>> role, topicStoragePath,
>> EventBrokerConstants.EB_PERMISSION_SUBSCRIBE);
>> userRealm.getAuthorizationManager().authorizeRole(
>> role, topicStoragePath,
>> EventBrokerConstants.EB_PERMISSION_PUBLISH);
>> }
>>
>> There are 6 roles in appfac (dev,qa, devops etc) and this authorization
>> for the topic is done for each role, which takes apprx 2 mins time.
>>
>>
> Went through the code. If there are 6 calls, this will generate 24
> database calls. How?
>
> 6 (roles) * 2 (calling authorize twice here) * 2 (we have 2 db calls in
> one authorize method, 4.1.0 code this is reduced to 1)
>
> As a fix for event.core we can avoid all of these db calls if check
> isAuthorized before adding permission. Why? Because permissions are cached.
> That way it will be slow only in the first tenant load, even then when ESB
> is released with 4.1.0 kernel it will only have 12 db calls. So only 1
> minute.
>
> thanks,
> dimuthu
>
>
>> As a solution a patch is introduced such that not to authorize these
>> roles if no topic is set in event-broker.xml.
>>
>> Thanks
>>
>>
>> On Tue, May 28, 2013 at 5:12 PM, Dimuthu Leelarathne 
>> wrote:
>>
>>> Hi Srinath,
>>>
>>> Why would the following take so much time? Can ESB run without it?
>>>
>>> thanks,
>>> dimuthu
>>>
>>> On Tue, May 28, 2013 at 4:25 PM, Shamika Ariyawansa wrote:
>>>
 Hi

 This timeout occurs when calling  creatingConfigurationContext method
 of the the following class.


 org.wso2.carbon.event.core.internal.builder.EventAxis2ConfigurationContextObserver

 This call is one of 20 osgi calls. All the others returned with maximum
 of 1 s but this one takes about 2 mins.





 On Tue, May 28, 2013 at 10:32 AM, Kishanthan Thangarajah <
 kishant...@wso2.com> wrote:

>
>
>
> On Tue, May 28, 2013 at 5:05 AM, Dimuthu Leelarathne <
> dimut...@wso2.com> wrote:
>
>> Hi Shamika,
>>
>> Did we try to put logs in "private static ConfigurationContext
>> createTenantConfigurationContext" in TenantAxisUtils ? We need to put 
>> debug
>> logs along the path and see what takes all the time?
>>
>
> We did put some debug logs at there as-well. But that was not the
> issue when we investigated it. The issue is, it takes 2mins for the login
> action to return and then the call comes to this method. The issue should
> be before this. So I believe we should investigate on that path.
>
> @Shamika, can you share the latest logs which explains the
> above observation?
>
>
>
>> thanks,
>> dimuthu
>>
>>
>> On Tue, May 28, 2013 at 2:38 AM, Shamika Ariyawansa > > wrote:
>>
>>> Hi,
>>>
>>> Following observation was made wrt the ESB 4.6.0 instance which was
>>> spawned from the S2 ESB cartridge.
>>>
>>> 1. When the tenant user is logged for the first time the page keeps
>>> on loading and after few minutes the page gets timeout
>>> Refer the following log.
>>>
>>> TID: [0] [ESB] [2013-05-27 06:10:16,510]  INFO
>>> {org.wso2.carbon.appfactory.userstore.AppFactoryRealmConfigBuilder} -  
>>> Get
>>> the tenant ( tenant id=142) detlail.
>>> {org.wso2.carbon.appfactory.userstore.AppFactoryRealmConfigBuilder}
>>> TID: [0] [ESB] [2013-05-27 06:10:16,522]  INFO
>>> {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} -  LDAP
>>> connection created successfully in read-write mode
>>> {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager}
>>> TID: [0] [ESB] [2013-05-27 06:10:16,561]  INFO
>>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  
>>> Connected
>>> to mount at config in 3ms
>>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
>>> TID: [0] [ESB] [2013-05-27 06:10:16,690]  INFO
>>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  
>>> Connected
>>> to mount at governance in 2ms
>>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
>>> TID: [0] [ESB] [2013-05-27 06:10:16,819]  INFO
>>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
>>>  'ad...@admin.com@proximi

[Dev] [Jaggery] Content-Type of HTTP post is changed internally by Jaggery to ContentType: application/x-www-form-urlencoded; charset=UTF-8

[Gayan Dhanushka]

Hi,

Note $subject as we discovered yesterday. It is there in the latest
jaggery-0.9.0.ALPHA3-wso2v6 pack as well.

I'm sending a rest call to BAM using Jaggery and following are my optional
headers.

*{
"Accept": "application/json",
"Content-Type": "application/json",
"Authorization": "Basic YWRtaW46YWRtaW4="
}

*
In the BAM server log it says,

*No operation matching request path "/datareceiver/1.0.0/streams" is found,
Relative Path: /, HTTP Method: POST, ContentType:
application/x-www-form-urlencoded;charset=UTF-8, Accept: application/json*

I may proceed correcting this manually. What is the path for the .js file
which contains post method implementation?

Thanks.

-- 

Gayan Dhanushka
Software Engineer
WSO2 Inc.
http://wso2.com

Mobile : 0716662327
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to reconnect to a topic publisher automatically?

[Shammi Jayasinghe]

Hi Nirmal,

As we discussed offline, we ll have to retry for creating the connection to
the server , once it is got disconnected. AFAIK we need to handle it with
our client code to make the connection to the server once it got
disconnected.

Thanks
Shammi



On Tue, May 28, 2013 at 9:31 PM, Nirmal Fernando  wrote:

> Hi Shammi,
>
> This still fails to me. When I shutdown the server where the topic lives,
> I see following error [1].
>
> Note that what I'm using is a Topic.
>
> And my client is at [2], am I doing something wrong?
>
> [1]
>
> TID: [0] [ELB] [2013-05-28 15:12:47,589] ERROR
> {org.wso2.andes.client.state.AMQStateManager} -  No Waiters for error
> saving as last error:Exception thrown against AMQConnection:
>
> Host: cc.wso2.com
> Port: 5673
> Virtual Host: carbon
> Client ID: clientID
> Active session count: 1: org.wso2.andes.AMQDisconnectedException: Server
> closed connection and reconnection not permitted.
> {org.wso2.andes.client.state.AMQStateManager}
> TID: [0] [ELB] [2013-05-28 15:12:47,590] ERROR
> {org.wso2.andes.client.AMQConnection} -  Throwable Received but no listener
> set: org.wso2.andes.AMQDisconnectedException: Server closed connection and
> reconnection not permitted. {org.wso2.andes.client.AMQConnection}
>
>
> [2]
>
> Properties initialContextProperties = new Properties();
> initialContextProperties.put("java.naming.factory.initial",
> "org.wso2.andes.jndi.PropertiesFileInitialContextFactory");
>
> String mbServerUrl = null;
> if (ConfigHolder.getInstance().getLbConfig() != null) {
> mbServerUrl =
> ConfigHolder.getInstance().getLbConfig().getLoadBalancerConfig().getMbServerUrl();
>
> }
> String connectionString =
> "amqp://admin:admin@clientID/carbon?brokerlist='tcp://" +
> (mbServerUrl == null ?
> TopologyConstants.DEFAULT_MB_SERVER_URL : mbServerUrl) +
> "'&reconnect='true'";
>
> initialContextProperties.put("connectionfactory.qpidConnectionfactory",
> connectionString);
>
> try {
> InitialContext initialContext = new
> InitialContext(initialContextProperties);
> TopicConnectionFactory topicConnectionFactory =
> (TopicConnectionFactory)
> initialContext.lookup("qpidConnectionfactory");
> TopicConnection topicConnection =
> topicConnectionFactory.createTopicConnection();
> topicConnection.start();
> TopicSession topicSession =
> topicConnection.createTopicSession(false,
> Session.AUTO_ACKNOWLEDGE);
>
> Topic topic = topicSession.createTopic(topicName);
> TopicSubscriber topicSubscriber =
> topicSession.createSubscriber(topic);
>
> topicSubscriber.setMessageListener(new TopologyListener());
>
> } catch (NamingException e) {
> log.error(e.getMessage(), e);
> } catch (JMSException e) {
> log.error(e.getMessage(), e);
> }
>
>
>
> On Mon, May 27, 2013 at 10:46 PM, Nirmal Fernando  wrote:
>
>> Great... Thanks a lot Shammi!! I'll try this.
>>
>>
>> On Mon, May 27, 2013 at 10:44 PM, Shammi Jayasinghe wrote:
>>
>>> Hi Nirmal,
>>>
>>> It seems the problem is with your connection URL. The way you have
>>> created the connection string should be as bellow[1]. I have checked and
>>> verified the the re-connection of the subscriber with the following client
>>> code[2].
>>>
>>> [1]
>>>String connectionString = "amqp://admin:admin@clientID
>>> /carbon?brokerlist='tcp://localhost:5672'&reconnect='true'";
>>>
>>> [2]
>>> Properties initialContextProperties = new Properties();
>>> initialContextProperties.put("java.naming.factory.initial",
>>>
>>> "org.wso2.andes.jndi.PropertiesFileInitialContextFactory");
>>> String connectionString = "amqp://admin:admin@clientID
>>> /carbon?brokerlist='tcp://localhost:5672'&reconnect='true'";
>>>
>>> initialContextProperties.put("connectionfactory.qpidConnectionfactory",
>>> connectionString);
>>> String queueName = "bar";
>>> initialContextProperties.put("queue."+queueName, queueName);
>>>
>>>
>>> try {
>>> InitialContext initialContext = new
>>> InitialContext(initialContextProperties);
>>> ConnectionFactory queueConnectionFactory
>>> = (ConnectionFactory)
>>> initialContext.lookup("qpidConnectionfactory");
>>> Destination destination = (Destination)
>>> initialContext.lookup(queueName);
>>> int count = 0;
>>>
>>> Connection queueConnection =
>>> queueConnectionFactory.createConnection();
>>> queueConnection.start();
>>>
>>>
>>> try {
>>> Session queueSession =
>>> queueConnection.createSession(false, QueueSession.AUTO_ACKNOWLEDGE);
>>>
>>>
>>> MessageConsumer messageConsumer =
>>> queueSession.createConsumer(destination);
>>> while (true) {
>>>
>>>  

Re: [Dev] How to reconnect to a topic publisher automatically?

[Shammi Jayasinghe]

Hi Nirmal,

With using following[1] kind of code segment we ll be able to do that.

Thanks
Shammi
[1]
   while (true) {

try {
TextMessage textMessage = (TextMessage)
topicSubscriber.receive();
if (textMessage != null) {
System.out.println("textMessage = " +
textMessage);
}
} catch (JMSException e) {

try {
if (topicSubscriber != null) {
topicSubscriber.close();
}

if (topicSession != null) {
topicSession.close();
}

if (topicConnection != null) {
topicConnection.close();
}
} catch (JMSException e1) {
//ignore
} finally {
try {
topicConnection =
topicConnectionFactory.createTopicConnection();
topicConnection.start();
topicSession =
topicConnection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
topic = (Topic)ctx.lookup(topicName);
topicSubscriber =
topicSession.createSubscriber(topic);


} catch (NamingException e1) {
e1.printStackTrace();
} catch (JMSException e1) {
e1.printStackTrace();
}
}

}
}



On Wed, May 29, 2013 at 10:17 AM, Shammi Jayasinghe  wrote:

> Hi Nirmal,
>
> As we discussed offline, we ll have to retry for creating the connection
> to the server , once it is got disconnected. AFAIK we need to handle it
> with our client code to make the connection to the server once it got
> disconnected.
>
> Thanks
> Shammi
>
>
>
> On Tue, May 28, 2013 at 9:31 PM, Nirmal Fernando  wrote:
>
>> Hi Shammi,
>>
>> This still fails to me. When I shutdown the server where the topic lives,
>> I see following error [1].
>>
>> Note that what I'm using is a Topic.
>>
>> And my client is at [2], am I doing something wrong?
>>
>> [1]
>>
>> TID: [0] [ELB] [2013-05-28 15:12:47,589] ERROR
>> {org.wso2.andes.client.state.AMQStateManager} -  No Waiters for error
>> saving as last error:Exception thrown against AMQConnection:
>>
>> Host: cc.wso2.com
>> Port: 5673
>> Virtual Host: carbon
>> Client ID: clientID
>> Active session count: 1: org.wso2.andes.AMQDisconnectedException: Server
>> closed connection and reconnection not permitted.
>> {org.wso2.andes.client.state.AMQStateManager}
>>  TID: [0] [ELB] [2013-05-28 15:12:47,590] ERROR
>> {org.wso2.andes.client.AMQConnection} -  Throwable Received but no listener
>> set: org.wso2.andes.AMQDisconnectedException: Server closed connection and
>> reconnection not permitted. {org.wso2.andes.client.AMQConnection}
>>
>>
>> [2]
>>
>> Properties initialContextProperties = new Properties();
>> initialContextProperties.put("java.naming.factory.initial",
>> "org.wso2.andes.jndi.PropertiesFileInitialContextFactory");
>>
>> String mbServerUrl = null;
>> if (ConfigHolder.getInstance().getLbConfig() != null) {
>> mbServerUrl =
>> ConfigHolder.getInstance().getLbConfig().getLoadBalancerConfig().getMbServerUrl();
>>
>> }
>> String connectionString =
>> "amqp://admin:admin@clientID/carbon?brokerlist='tcp://" +
>> (mbServerUrl == null ?
>> TopologyConstants.DEFAULT_MB_SERVER_URL : mbServerUrl) +
>> "'&reconnect='true'";
>>
>> initialContextProperties.put("connectionfactory.qpidConnectionfactory",
>> connectionString);
>>
>> try {
>> InitialContext initialContext = new
>> InitialContext(initialContextProperties);
>> TopicConnectionFactory topicConnectionFactory =
>> (TopicConnectionFactory)
>> initialContext.lookup("qpidConnectionfactory");
>> TopicConnection topicConnection =
>> topicConnectionFactory.createTopicConnection();
>> topicConnection.start();
>> TopicSession topicSession =
>> topicConnection.createTopicSession(false,
>> Session.AUTO_ACKNOWLEDGE);
>>
>> Topic topic = topicSession.createTopic(topicName);
>> TopicSubscriber topicSubscriber =
>> topicSession.createSubscriber(topic);
>>
>> topicSubscriber.setMessageListener(new TopologyListener());
>>
>> } catch (NamingException e) {
>> log.error(e.

Re: [Dev] [Jaggery] Content-Type of HTTP post is changed internally by Jaggery to ContentType: application/x-www-form-urlencoded; charset=UTF-8

[Nuwan Bandara]

Can you share you jaggery code that does the HTTP call.

Regards,
/Nuwan


On Wed, May 29, 2013 at 10:17 AM, Gayan Dhanushka  wrote:

> Hi,
>
> Note $subject as we discovered yesterday. It is there in the latest
> jaggery-0.9.0.ALPHA3-wso2v6 pack as well.
>
> I'm sending a rest call to BAM using Jaggery and following are my optional
> headers.
>
> *{
> "Accept": "application/json",
> "Content-Type": "application/json",
> "Authorization": "Basic YWRtaW46YWRtaW4="
> }
>
> *
> In the BAM server log it says,
>
> *No operation matching request path "/datareceiver/1.0.0/streams" is
> found, Relative Path: /, HTTP Method: POST, ContentType:
> application/x-www-form-urlencoded;charset=UTF-8, Accept: application/json*
>
> I may proceed correcting this manually. What is the path for the .js file
> which contains post method implementation?
>
> Thanks.
>
> --
>
> Gayan Dhanushka
> Software Engineer
> WSO2 Inc.
> http://wso2.com
>
> Mobile : 0716662327
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Thanks & Regards,

Nuwan Bandara
Technical Lead & Member, MC, Development Technologies
WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763 9629
*

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

Re: [Dev] [Jaggery] Content-Type of HTTP post is changed internally by Jaggery to ContentType: application/x-www-form-urlencoded; charset=UTF-8

[Manuranga Perera]

bug fixed thanks for reporting.
please open JIRAs for bugs in the future, it's easer to keep track that way.


On Wed, May 29, 2013 at 10:33 AM, Nuwan Bandara  wrote:

> Can you share you jaggery code that does the HTTP call.
>
> Regards,
> /Nuwan
>
>
> On Wed, May 29, 2013 at 10:17 AM, Gayan Dhanushka  wrote:
>
>> Hi,
>>
>> Note $subject as we discovered yesterday. It is there in the latest
>> jaggery-0.9.0.ALPHA3-wso2v6 pack as well.
>>
>> I'm sending a rest call to BAM using Jaggery and following are my
>> optional headers.
>>
>> *{
>> "Accept": "application/json",
>> "Content-Type": "application/json",
>> "Authorization": "Basic YWRtaW46YWRtaW4="
>> }
>>
>> *
>> In the BAM server log it says,
>>
>> *No operation matching request path "/datareceiver/1.0.0/streams" is
>> found, Relative Path: /, HTTP Method: POST, ContentType:
>> application/x-www-form-urlencoded;charset=UTF-8, Accept: application/json
>> *
>>
>> I may proceed correcting this manually. What is the path for the .js file
>> which contains post method implementation?
>>
>> Thanks.
>>
>> --
>>
>> Gayan Dhanushka
>> Software Engineer
>> WSO2 Inc.
>> http://wso2.com
>>
>> Mobile : 0716662327
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Thanks & Regards,
>
> Nuwan Bandara
> Technical Lead & Member, MC, Development Technologies
> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
> 9629
> *
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
With regards,
*Manu*ranga Perera.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Jaggery] Content-Type of HTTP post is changed internally by Jaggery to ContentType: application/x-www-form-urlencoded; charset=UTF-8

[Nuwan Bandara]

+1, anything related to jaggery please use
https://github.com/wso2/caramel/issues


On Wed, May 29, 2013 at 10:38 AM, Manuranga Perera  wrote:

> bug fixed thanks for reporting.
> please open JIRAs for bugs in the future, it's easer to keep track that
> way.
>
>
> On Wed, May 29, 2013 at 10:33 AM, Nuwan Bandara  wrote:
>
>> Can you share you jaggery code that does the HTTP call.
>>
>> Regards,
>> /Nuwan
>>
>>
>> On Wed, May 29, 2013 at 10:17 AM, Gayan Dhanushka wrote:
>>
>>> Hi,
>>>
>>> Note $subject as we discovered yesterday. It is there in the latest
>>> jaggery-0.9.0.ALPHA3-wso2v6 pack as well.
>>>
>>> I'm sending a rest call to BAM using Jaggery and following are my
>>> optional headers.
>>>
>>> *{
>>> "Accept": "application/json",
>>> "Content-Type": "application/json",
>>> "Authorization": "Basic YWRtaW46YWRtaW4="
>>> }
>>>
>>> *
>>> In the BAM server log it says,
>>>
>>> *No operation matching request path "/datareceiver/1.0.0/streams" is
>>> found, Relative Path: /, HTTP Method: POST, ContentType:
>>> application/x-www-form-urlencoded;charset=UTF-8, Accept:
>>> application/json*
>>>
>>> I may proceed correcting this manually. What is the path for the .js
>>> file which contains post method implementation?
>>>
>>> Thanks.
>>>
>>> --
>>>
>>> Gayan Dhanushka
>>> Software Engineer
>>> WSO2 Inc.
>>> http://wso2.com
>>>
>>> Mobile : 0716662327
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Thanks & Regards,
>>
>> Nuwan Bandara
>> Technical Lead & Member, MC, Development Technologies
>> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
>> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
>> 9629
>> *
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
>


-- 
*Thanks & Regards,

Nuwan Bandara
Technical Lead & Member, MC, Development Technologies
WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763 9629
*

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

Re: [Dev] [Jaggery] Content-Type of HTTP post is changed internally by Jaggery to ContentType: application/x-www-form-urlencoded; charset=UTF-8

[Gayan Dhanushka]

Hi Nuwan,

I have two files bamUtil.js and bam.jag

bamUtil.js

*var createStream = function(createStreamDefnURL , streamDefn,
optionalHeaders){
var result = post(createStreamDefnURL, streamDefn, optionalHeaders);
 };

*
bam.jag

<%
 var bamUtils = require("bamUtil.js");
var streamDefn = stringify( {
  "name":"stockquote.stream",
  "version": "1.0.2",
  "nickName": "Stock Quote Information",
  "description": "Some Desc",
  "tags":["foo", "bar"],
  "metaData":[
   {
 "name":"ipAdd",
 "type":"STRING"
   }
  ],
  "payloadData":[
  {
"name":"symbol",
"type":"string"
  },
  {
"name":"price",
"type":"double"
  },
  {
"name":"volume",
"type":"int"
  },
  {
"name":"max",
"type":"double"
  },
  {
"name":"min",
"type":"double"
  }
 ]
});

var events = stringify([
 {
   "payloadData" : ["IBM", 26.0, 848, 43.33, 2.3] ,
   "metaData" : ["123.233.0.1"] ,
   "timeStamp" : 1312345432
 },
 {
  "payloadData" : ["MSFT", 22.0, 233, 22.22, 4.3] ,
  "metaData" : ["5.211.1.1"]
 }
]);
var optionalHeaders = {
"Accept": "application/json",
"Content-Type": "application/json",
"Authorization": "Basic YWRtaW46YWRtaW4="};
   var createStreamDefnURL = '
https://localhost:9443/datareceiver/1.0.0/streams';
 var publishEventURL = '
https://localhost:9443/datareceiver/1.0.0/stream/stockquote.stream/1.0.2/';
var result = bamUtils.createStream(createStreamDefnURL,streamDefn,
optionalHeaders);
//var result1 = bamUtils.publishEvent(publishEventURL,events,
optionalHeaders);

   %>

This is for the record Nuwan. Manu has fixed it thanks Manu and noted.



On Wed, May 29, 2013 at 10:33 AM, Nuwan Bandara  wrote:

> Can you share you jaggery code that does the HTTP call.
>
> Regards,
> /Nuwan
>
>
> On Wed, May 29, 2013 at 10:17 AM, Gayan Dhanushka  wrote:
>
>> Hi,
>>
>> Note $subject as we discovered yesterday. It is there in the latest
>> jaggery-0.9.0.ALPHA3-wso2v6 pack as well.
>>
>> I'm sending a rest call to BAM using Jaggery and following are my
>> optional headers.
>>
>> *{
>> "Accept": "application/json",
>> "Content-Type": "application/json",
>> "Authorization": "Basic YWRtaW46YWRtaW4="
>> }
>>
>> *
>> In the BAM server log it says,
>>
>> *No operation matching request path "/datareceiver/1.0.0/streams" is
>> found, Relative Path: /, HTTP Method: POST, ContentType:
>> application/x-www-form-urlencoded;charset=UTF-8, Accept: application/json
>> *
>>
>> I may proceed correcting this manually. What is the path for the .js file
>> which contains post method implementation?
>>
>> Thanks.
>>
>> --
>>
>> Gayan Dhanushka
>> Software Engineer
>> WSO2 Inc.
>> http://wso2.com
>>
>> Mobile : 0716662327
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Thanks & Regards,
>
> Nuwan Bandara
> Technical Lead & Member, MC, Development Technologies
> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
> 9629
> *
> 
>



-- 

Gayan Dhanushka
Software Engineer
WSO2 Inc.
http://wso2.com

Mobile : 0716662327
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] default parameters in axis.xml in products

[Supun Malinga]

Hi guys,

There are several product cluster specific paramaters we have defined in
axis2.xml. Since we use seperate axis2.xml s in each product I see an
improvement we can do to have these params by default customised to
individual product.

For eg:
domain name
localMemberPort

Each time we do a clustered deployment we need to change these values to be
unique for each product cluster/instance. So it helps to set a default
unique value for these.

thanks,
-- 
Supun Malinga,

Senior Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - sup...@wso2.com 
mobile - 071 56 91 321
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Warning when building Test Automation Framework on 4.1.3 branch

[Senaka Fernando]

FYI,

[WARNING] Using platform encoding (Cp1252 actually) to copy filtered
resources, i.e. build is platform dependent!

Thanks,
Senaka.

-- 
*Senaka Fernando*
Member - Integration Technologies Management Committee;
Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Warning when building Test Automation Framework on 4.1.3 branch

[Dharshana Warusavitharana]

Hi Senaka,

All encoding added to UTF-8 this is fixed thank you for pointing out.

thank You,
Dharshana


On Wed, May 29, 2013 at 11:40 AM, Senaka Fernando  wrote:

> FYI,
>
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered
> resources, i.e. build is platform dependent!
>
> Thanks,
> Senaka.
>
> --
> *Senaka Fernando*
> Member - Integration Technologies Management Committee;
> Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>



-- 

Dharshana Warusavitharana
Senior Software Engineer , Test Automation
WSO2 Inc. http://wso2.com
email : dharsha...@wso2.com 
cell : +94772202595
blog : http://dharshanaw.blogspot.com

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev