Re: [Dev] Tenant specific receiver deploys before the streams and becomes inactive

[Ayyoob Hamza]

I was able to reproduce this on DAS-3.1.0, I'll further analyze this and
will update about this.

*Ayyoob Hamza*
*Senior Software Engineer*
WSO2 Inc.; http://wso2.com
email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>

On Thu, May 11, 2017 at 4:10 PM, Ayyoob Hamza  wrote:

> Hi Damith,
>
> Tried in cep 4.2.0 and couldn't reproduce it. May I know the version ? I
>> believe after creating the artifacts you just restarted the server and
>> tried to logged into the tenant ?
>>
>
> We are trying to load the tenant from the tenant specific reciever in
> super tenant space with the fix suggested from the email [1]. However the
> behaviour would similar to what you have mentioned. I can reproduce the
> issue through the login as well.
>
> We are using the analytics commons version 5.1.17.
>
> [1] tenant specific MQTT receivers in DAS , not listening to topics once
> tenant get unloaded
>
> Thanks,
> Ayyoob
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Tenant specific receiver deploys before the streams and becomes inactive

[Ayyoob Hamza]

Hi Damith,

Tried in cep 4.2.0 and couldn't reproduce it. May I know the version ? I
> believe after creating the artifacts you just restarted the server and
> tried to logged into the tenant ?
>

We are trying to load the tenant from the tenant specific reciever in super
tenant space with the fix suggested from the email [1]. However the
behaviour would similar to what you have mentioned. I can reproduce the
issue through the login as well.

We are using the analytics commons version 5.1.17.

[1] tenant specific MQTT receivers in DAS , not listening to topics once
tenant get unloaded

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

Re: [Dev] Tenant specific receiver deploys before the streams and becomes inactive

[Damith Wickramasinghe]

Hi Ayyoob,

Tried in cep 4.2.0 and couldn't reproduce it. May I know the version ? I
believe after creating the artifacts you just restarted the server and
tried to logged into the tenant ?

Regards,
Damith

On Wed, May 10, 2017 at 4:05 PM, Ayyoob Hamza  wrote:

> Hi All,
>
> In a multi-tenant flow when a tenant loads up then It deploys event
> receiver artifacts before deploying the stream, because of this the
> receiver becomes inactive.  however, the receiver deploys if we manually
> activate it after the stream is loaded.
>
> Could it be possible to load the inactive receivers after the streams are
> deployed through the code?. Have we come across this scenario in a
> multi-tenant environment, if so is there any alternative solution.
>
> Thanks
> *Ayyoob Hamza*
> *Senior Software Engineer*
> WSO2 Inc.; http://wso2.com
> email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>
>



-- 
Senior Software Engineer
WSO2 Inc.; http://wso2.com

lean.enterprise.middleware

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

[Dev] Tenant specific receiver deploys before the streams and becomes inactive

[Ayyoob Hamza]

Hi All,

In a multi-tenant flow when a tenant loads up then It deploys event
receiver artifacts before deploying the stream, because of this the
receiver becomes inactive.  however, the receiver deploys if we manually
activate it after the stream is loaded.

Could it be possible to load the inactive receivers after the streams are
deployed through the code?. Have we come across this scenario in a
multi-tenant environment, if so is there any alternative solution.

Thanks
*Ayyoob Hamza*
*Senior Software Engineer*
WSO2 Inc.; http://wso2.com
email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev