Hi Clovis,
These are parameters are passed as JVM properties along with server startup
script. And these configurations are resolved at runtime based on the
respective values for those properties.
If you are using the IoT server version 3.0.0, then it's passed as shown
below via
gt; Thanks,
>
> On Thu, Mar 30, 2017 at 3:35 PM, Sinthuja Ragendran <sinth...@wso2.com>
> wrote:
>
>> Hi Madhawa,
>>
>> The error comes from [1], and it's using the carbon.mediation.version,
>> and it's referring to SNAPSHOT [2].
>>
>> [1] https://
ithub.com/wso2/product-ei/blob/master/pom.xml#L1271
>
> Thanks,
> Madhawa
>
> On Thu, Mar 30, 2017 at 3:19 PM, Sinthuja Ragendran <sinth...@wso2.com>
> wrote:
>
>> Hi,
>>
>> I'm getting the below error when building the product-ei master. Please
>> note
Hi,
I'm getting the below error when building the product-ei master. Please
note, I have tried building with java 1.7 and 1.8. Also with clean m2, but
no luck.
An error occurred while configuring the installed items
session context was:(profile=default,
Hi Chamara,
Please find the commit in [1] to fix this issue. I remember Madara was
recently checking on a similar issue recently.
[1]
https://github.com/wso2/product-ds/commit/3f1d3739f351e3c08dee68c46cc5be143b2e3b9b
Thanks,
Sinthuja.
On Tue, Mar 21, 2017 at 11:28 AM, Chamara Silva
Hi All,
It's my pleasure to welcome Nisala Nanayakkara as a WSO2 Committer.
Nisala has been a valuable contributor to the Dashboard Server Team and
then Platform Team. In recognition of his contribution, dedication and
commitment he has been voted as a WSO2 committer.
Nisala, welcome aboard and
Hi Megala,
On Wed, Dec 21, 2016 at 1:55 PM, Megala Uthayakumar wrote:
> Hi Vishanth,
>
> Please find my comments inline.
>
> On Wed, Dec 21, 2016 at 1:08 PM, Vishanth Balasubramaniam <
> vishan...@wso2.com> wrote:
>
>> Hi Sinthuja,
>>
>> While testing the multi tenancy flow in
Hi,
Have you configured parameter in the task-config.xml?
AFAIR the server will wait for the configured number of nodes to be present
before trying to schedule the task.
Thanks,
Sinthuja.
On Mon, Nov 7, 2016 at 4:57 PM, Dilshani Subasinghe
wrote:
> Hi Shazni,
>
> AFAIK
Hi all,
It's my pleasure to announce Megala Uthayakumar as a WSO2 Committer. Megala
had been a valuable contributor for Dashboard Server product, and now for
EMM/IoT Products. And in recognition of her contribution to WSO2, she has
been voted as a WSO2 Committer.
Megala, Keep up the good work
Hi Dillini,
I have added the close method to websocket host object in the
v0.12.8-SNAPSHOT, please do a build and test it out.
Thanks,
Sinthuja.
On Mon, Aug 29, 2016 at 2:02 PM, Dilini Muthumala wrote:
> Hi Manu,
>
> If the websocket client has not being authenticated, the
Hi Susinda,
On Mon, Aug 22, 2016 at 10:16 AM, Susinda Perera <susi...@wso2.com> wrote:
>
>
> On Sun, Aug 21, 2016 at 5:06 PM, Sinthuja Ragendran <sinth...@wso2.com>
> wrote:
>
>> Hi Nisala,
>>
>> So lets create a new repo for our new maven plugin, an
Hi Nisala,
So lets create a new repo for our new maven plugin, and lets include source
there as per Susinda.
@Susinda,
Can you please elaborate bit more with what is the expected outcome when
DevS based tooling using this maven plugin for DS? Because in the context,
DS it self is a tool to
Hi,
On Thu, Aug 18, 2016 at 10:12 PM, Tanya Madurapperuma
wrote:
>
>
> On Thu, Aug 18, 2016 at 9:18 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>>
>>
>> On Thu, Aug 18, 2016 at 3:55 PM, Tanya Madurapperuma
>> wrote:
>>
>>> This warning is
Hi Rasika,
As discussed in offline, this improvement is helpful in the standalone
setup for the developer, and hence for the moment I'll merge your change.
But finally we need to provide the log4j.properties in the application
level to really address this issue, but due to time limitations let's
Hi Rasika,
On Wed, Aug 3, 2016 at 3:48 PM, Rasika Perera wrote:
> [Adding Sinthuja & Manu]
>
> Hi Dilan and All,
>
> I have done a small fix to Jaggery Core level to support log4j.properties
> file.
>
> *Current Implementation*
> With the current jaggery implementation; All
Hi Nirmal,
ReconnectionService is not something associated with main publishing logic,
and it's used for the health check of the receivers. Therefore calling
shutdownNow() for the that doesn't break anything on event publishing flow.
Thanks,
Sinthuja.
On Tue, Aug 2, 2016 at 11:56 PM, Nirmal
Hi Dunith,
On Thu, Jul 21, 2016 at 6:41 PM, Dunith Dhanushka wrote:
> Hi DS team,
>
> I've noticed following behavior with latest carbon-dashboards.
>
> 1. Accessed a dashboard using its direct URL.
> E.g https://localhost:9443/portal/dashboards/esb-analytics
>
> 2. If the user
Hi KasunG,
On Mon, Jul 18, 2016 at 5:31 PM, KasunG Gajasinghe wrote:
>
>
> On Mon, Jul 18, 2016 at 2:45 PM, Nisala Nanayakkara
> wrote:
>
>> Hi KasunG,
>>
>> Yes.This is the branch. Currently we are maintaining two branches as this
>> tomcat version(tomcat 8)
Hi Chamila,
I appreciate if you create a public JIRA in this issue, hence we can make
sure these issues are actually fixed for DS 2.1.0 release. And did you try
on chrome, and still do you see the problem? Please do mention what are
versions of browsers, java version, and OS did you test it upon
Hi,
Anyhow ultimately when all the carbon products move to AS 6.0 based
platform, we can merge all those into one.
Thanks,
Sinthuja.
On Mon, Jul 4, 2016 at 12:38 PM, Nisala Nanayakkara wrote:
> Hi Kasun,
>
> Yes.We can do a performance round. Currently we manage the Tomcat
gt; it comes to the dashboard view. IMO I think its better we give an option to
>>> the user to enable the editing mode by giving a switcher/button etc ...
>>>
>>> WDYT?
>>>
>>> Cheers!
>>> Jerad
>>>
>>> On Mon, Jun 27, 2016 at 9:45 PM, S
for
>> designers and admins. And end users will have the capable of doing simple
>> modifications on view mode it self.
>>
>> I believe in this case we will have a dynamic layout on view mode by
>> default.
>>
>> Cheers!
>> Jerad
>>
>> On M
Hi Udara,
On Mon, Jun 27, 2016 at 1:27 PM, Tanya Madurapperuma wrote:
> Hi Udara,
>
>
> On Mon, Jun 27, 2016 at 12:41 PM, Udara Rathnayake
> wrote:
>
>> Hi UX team,
>>
>> Requirement is to provide simple dashboard viewer level customization
>> within the
WSO2 Dashboard Server 2.1.0-M3 Released!
WSO2 Dashboard Server team is pleased to announce the release of WSO2
Dashboard Server 2.1.0 Milestone 3. This release comes with the following
bug fixes and features. You can download the distribution from [1].
Bug
[UES-924] - In drill down dashboards
Adding Sumedha and Ayoob.
On Sun, Jun 5, 2016 at 12:16 AM, Sinthuja Ragendran <sinth...@wso2.com>
wrote:
> Hi,
>
> I noticed $subject in IoT alpha pack as well as the snapshot version. I
> installed the agent by downloading into the laptop and transferring into
&g
Hi,
I noticed $subject in IoT alpha pack as well as the snapshot version. I
installed the agent by downloading into the laptop and transferring into
the phone manually, but the given OOB download options are not working. I
have tried with Samsung Galaxy S4. Is this the know issue? Or I'm missing
Hi Sumedha/Ayoob,
In the graphs I was not able to see the light and rotation sensor stats,
but in the mobile agent sensors configuration, I don't see the rotation
sensor in the list provided, therefore I can think it's not sending and
hence it's not showing . But for light sensor, it's there in
Hi,
I see the light is being correctly measured in the phone app, and the
values are correctly changing. But it's not getting sent to IoT server, I
checked the data explorer (DAS component) in IoT server, but this seems to
be not there. Is it know issue?
Thanks,
Sinthuja.
--
*Sinthuja
s other tenant user's registry correctly by starting correct tenant
> flow.
>
> Regards,
> Chandana
> On Jun 2, 2016 1:15 PM, "Sinthuja Ragendran" <sinth...@wso2.com> wrote:
>
>> Hi Chandana,
>>
>> I also had a doubt about starting the tenant flow, b
icular tenant user beforehand and close it
> after performing the registry operation. I don't see any code used here to
> start a super tenant flow before accessing the super tenant registry.
>
> Regards,
> Chandana
> On Jun 2, 2016 12:46 PM, "Sinthuja Ragendran&qu
Hi,
I did some further testing, and it looks like we are replicating the super
tenant cache entries to tenant cache, when the tenant is loading at the
first time. Because if I first create the dashboard (a registry resource)
in super tenant and configured it to be shared by all nodes, and
Looping in registry team. Is this the known issue? Megala, I think you
tested with 4.5.4 carbon-registry version.
On Wed, Jun 1, 2016 at 10:08 PM, Megala Uthayakumar wrote:
> Hi All,
>
> We are developing a shared dashboard feature for Dashboard Server. This
> feature allows
Hi Udara,
As discussed offline we need to have following as well.
- A name for each view so that if a user could see both views he/she should
be able switch.
- A default view should not be existing, and that should be associated with
roles selection option when the 'role based view' option is
gt;> bhath...@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> +Ruwan
>>>>>>>>>>
>>>>>>>>>> On Fri, May 27, 2016 at 10:20 AM, Megala Uthayakumar <
>>>>&g
Hi Dhanushka,
You don't need to do any special changes, just include the server side code
as shown in the sample [1] in a jag file, and mention that jag URL in the
client side to connect via web socket. As per the example, the jaggery app
for ws server side should be in below format.
- sample
-server feature generation?
> +1
> So that every product using shindig does not have to unzip and zip the war
> file to fix it.
>
> Cheers,
> Ruwan
>
> On Wed, May 18, 2016 at 12:01 PM, Sinthuja Ragendran <sinth...@wso2.com>
> wrote:
>
>> Hi Tanya,
>>
>
Hi Tanya,
Can't we fix this during the shinding-server feature generation?
Thanks,
Sinthuja.
On Wed, May 18, 2016 at 11:56 AM, Harsha Kumara wrote:
> Adding Bhathiya.
>
> We got same exception yesterday in APIM as well. We will need to same
> thing for DS as well.
>
>
Hi Megala,
>From the dashboard server point of view, we just need to have permission
tree as,
- Portal
- Login
- Dashboard
- Create
- Delete
- Settings
In this model, the create permission is required for the user to create the
dashboard, and similarly for other operations.
Hi all,
It's my pleasure to welcome Nipuna Chandradasa as WSO2 committer. Nipuna is
a key member of dashboard server team, and has contributed a lot to the DS
2.0.0 release including doing the performance test. Hence in recognition of
his contributions, ownership shown towards the tasks and
Hi all,
It's my pleasure to welcome Lasantha Samarakoon as a WSO2 Committer.
LasanthaS was a key member in dashboard server team, and he has contributed
in developing several features for the DS 2.0.0 release. In recognition of
his contributions, ownership shown towards the tasks and
It's already added to the dashboard server roadmap, until it's completed
you can go ahead with Dunith's option.
Thanks,
Sinthuja.
On Tue, Apr 5, 2016 at 3:27 PM, Dunith Dhanushka wrote:
> We had the same requirement in the ESB analytics dashboard. What we did
> was hiding
mediator? Can you share the BAM mediator configuration, and proxy
configuration?
Thanks,
Sinthuja.
>
> Thanks and Regards,
> Lakshitha.
>
> On Wed, Mar 2, 2016 at 1:41 PM, Sinthuja Ragendran <sinth...@wso2.com>
> wrote:
>
>> Hi Lakshitha,
>>
>>
that were sent along with the event,
and if so, you can use the data explorer [1] to see the results.
Thanks,
Sinthuja.
[1] https://docs.wso2.com/display/DAS300/Data+Explorer
>
> Regards,
> Lakshitha.
>
> On Wed, Mar 2, 2016 at 1:22 PM, Sinthuja Ragendran <sinth...@wso2.com>
> w
Hi Lakshitha,
On Wed, Mar 2, 2016 at 1:20 PM, Lakshitha Warnakulasuriya <
lakshitha...@gmail.com> wrote:
> Thanx Ayyoob.
>
> I'm using ESB(4.8.1) and DAS(3.0.0) for publish data from ESB to DAS.
>
> For the testing, I want to publish string from ESB to DAS. I followed
> below steps for do that.
Hi Lalanke,
On Fri, Feb 26, 2016 at 7:56 PM, Lalanke Athauda wrote:
> Hi,
> Please review and merge the PR [1].
> [1] https://github.com/wso2/jaggery/pull/149
>
Done.
Thanks,
Sinthuja.
>
>
> --
> Lalanke Athauda
> Software Engineer
> WSO2 Inc.
> Mobile: 0772264301
>
--
Hi,
Did testing on following.
- Verify user is directed to the dashboard creation page when there are
no dashboards (super tenant, tenant)
- Verify user is directed to the dashboard when there are is exactly one
dashboard (super tenant, tenant)
- Verify user is directed to the
Hi,
I have tested below.
- Verify user is directed to the dashboard creation page when there are
no dashboards (super tenant, tenant)
- Verify user is directed to the dashboard when there are is exactly one
dashboard (super tenant, tenant)
- Verify user is directed to the
On Wed, Jan 27, 2016 at 12:42 PM, Anjana Fernando wrote:
> Hi Gimantha,
>
> On Wed, Jan 27, 2016 at 11:26 AM, Gimantha Bandara
> wrote:
>
>> @Vithulan/Malith
>>
>>
>> On Tue, Jan 26, 2016 at 7:38 PM, Malith Dhanushka
>> wrote:
>>
>>> Hi
Hi Tanya,
Please check on this.
Thanks,
Sinthuja.
On Mon, Jan 18, 2016 at 5:09 PM, Lahiru Cooray wrote:
> adding Manu and Sinthuja
>
> On Mon, Jan 18, 2016 at 5:07 PM, Lahiru Cooray wrote:
>
>> Hi Dakshika,
>> Currently we are using Jaggery Server Feature
Hi,
This is not because of DAS, rather its from Service Stats Publisher
component which engages a global axis2 module to collect the service
requests/response related stats. And from
WSO2_HOME/repository/conf/etc/bam.xml,
you can globally enable/disable this module. Anyhow you can resolve this,
Hi Roshan,
This jar is basically used as custom UDF for spark to find the country name
from the IP for that sample.
Thanks,
Sinthuja.
On Wed, Dec 9, 2015 at 9:26 AM, Roshan Wijesena wrote:
> This is the sample [1]
>
> [1]
Hi,
On Wed, Dec 2, 2015 at 11:05 AM, Anjana Fernando wrote:
> On Wed, Dec 2, 2015 at 10:17 AM, Sachith Withana wrote:
>
>> Now that we are using logstash out of the box, without the DASConnector,
>> it won't do that.
>>
>> The logstash would just start
d in
> order to support merging table schemas. For that event persist feature
> should have a flag to enable/disable merging table schemas.
>
> Thanks,
>
> On Wed, Dec 2, 2015 at 1:30 PM, Sinthuja Ragendran <sinth...@wso2.com>
> wrote:
>
>> Hi,
>>
>> On Wed, Dec 2
On Wed, Dec 2, 2015 at 4:53 PM, Malith Dhanushka <mal...@wso2.com> wrote:
>
>
> On Wed, Dec 2, 2015 at 4:47 PM, Sinthuja Ragendran <sinth...@wso2.com>
> wrote:
>
>> Hi Malith,
>>
>> On Wed, Dec 2, 2015 at 4:41 PM, Malith Dhanushka <mal...@
Hi,
The way forward to go on log monitoring is with Log Analytics solution that
we are working on. Anyhow the old logging publishing method is broken and
cannot be used with latest carbon release products, because that's tightly
coupled with cassandra, Hadoop, etc, and hence we can't use that
l...@wso2.com> wrote:
>
>> Yes. Log analyzer which is being written on top of DAS platform will be
>> based on log stash http publisher.
>>
>> Thanks
>>
>> On Wed, Dec 2, 2015 at 11:58 AM, Sinthuja Ragendran <sinth...@wso2.com>
>> wrote:
>&
Hi Dinali,
Please find the documentation [1] for interacting with the data which is
stored in DAL via REST api. For each scenarios you can see a sample
request, and according to that you need to send the authentication headers
with your request. You can first try with curl or any other REST API
Hi IsuruP,
There are two issues we saw in the metrics-datasource configurations for
other datasources such as MySQL, MSSQL than H2.
1) The JNDI config is mentioned as below. As there is already default
configurations provided for the database, the jndi config also needed to be
default. If we
Hi all,
The installation guide seems bit outdated, we will update the
documentation, and the public JIRA reported [1] to track this.
@Jorge, actually you don't need hadoop or cygwin to run DAS in windows. Can
you please elaborate your setup? What is your record store, is it RDBMS (by
default H2
Hi Rushmin,
Spark JDBC connector first drops the existing table and recreates, but
anyhow to execute for the first time you need to have the table created.
Therefore please create the tables in the database by running mysql script
[1] which was given in the blog post.
[1]
ble was gone after the auto-commit error,
> causing the subsequent error messages.
>
> I could reproduce it consistently.
>
> Thanks
> Rushhmin
>
>
> On Wed, Nov 4, 2015 at 2:09 PM, Sinthuja Ragendran <sinth...@wso2.com>
> wrote:
>
>> Hi Rushmin,
ation
part didn't happen and only dropping the table was executed.
Thanks,
Sinthuja.
>
> Thank you for your clarification.
>
> Thanks
> Rushmin
>
> On Wed, Nov 4, 2015 at 2:20 PM, Sinthuja Ragendran <sinth...@wso2.com>
> wrote:
>
>> Hi Rus
Hi Udara,
AFAIK there is no such limitation as you cannot configure the cron below 1
minute, can you please share the doc link where it's stated as such? And
your cron expression is correct and this will work in BAM, this will
trigger every 30 seconds as explained in quartz docs.
Thanks,
AM while the first triggered task is
running, then even though next trigger time is met it will not be
triggered.
Thanks,
Sinthuja.
>
>
> Thanks,
> Gayan
>
> On Sat, Oct 31, 2015 at 10:44 PM, Sinthuja Ragendran <sinth...@wso2.com
> <javascript:_e(%7B%7D,'cvml','sinth...@ws
Hi,
I did a smoke test on below, and didn't get any issues.
1) Scripts add/edit/execute/execute-in-backgroud/scheduling
2) Activity Explorer
3) Message Explorer
4) Dashboard
[x] Stable - Go ahead and Release
Thanks,
Sinthuja.
On Mon, Oct 26, 2015 at 9:09 AM, Rukshan Premathunga
Hi Niranda,
On Thu, Oct 1, 2015 at 1:28 PM, Niranda Perera wrote:
> Hi Thanuja and Imesh,
>
> let me clarify the use of the term "create temporary table" with regard to
> Spark.
> inside DAS we save ('persist') data in DAL (Dara access layer) tables. So
> in order for us to
Hi Niranda,
On Thu, Oct 1, 2015 at 2:28 PM, Inosh Goonewardena <in...@wso2.com> wrote:
> Hi Niranda,
>
> On Thu, Oct 1, 2015 at 1:33 PM, Sinthuja Ragendran <sinth...@wso2.com>
> wrote:
>
>> Hi Niranda,
>>
>> On Thu, Oct 1, 2015 at 1:28 PM, Niran
adding Dunith,
I think it should be possible, and should be same as gadget. Are you
experiencing any exception when you do so?
Thanks,
Sinthuja.
On Thu, Sep 17, 2015 at 12:26 PM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:
> Hi Devs,
>
> I refer this document [1] to create car
her all dependent artifacts are included in cApp file :
> /home/thanujau/Music/wso2das-3.0.0-SNAPSHOT/repository/deployment/server/carbonapps/Stratos-Metering-Service.car
>
> Thanks.
>
> On Thu, Sep 17, 2015 at 12:33 PM, Sinthuja Ragendran <sinth...@wso2.com>
> wrote:
>
Hi,
At the time when APIM got released the new data publisher was just finished
development and not fully tested, hence it was using the old one. But
anyhow the upcoming any product releases need to use the new one as it's
now tested reasonably, and we are going to deprecate the old one soon.
*
> Senior Software Engineer
>
> *WSO2, Inc.*lean.enterprise.middleware.
>
> *Blog* : http://maninda.blogspot.com/
> *E-mail* : mani...@wso2.com
> *Skype* : @manindae
> *Twitter* : @maninda
>
> On Mon, Aug 31, 2015 at 8:08 PM, Sinthuja Ragendran <sinth...@wso2.com>
hreaddump of DAS to confirm this.
Thanks,
Sinthuja.
> Cheers,
> Anjana.
>
> On Tue, Sep 1, 2015 at 10:47 AM, Sinthuja Ragendran <sinth...@wso2.com>
> wrote:
>
>> Hi Maninda,
>>
>> I did a test with MySQL, and I was able to publish 10M events. There were
>
Fernando <nir...@wso2.com> wrote:
> Hi Sinthuja,
>
> On Tue, Sep 1, 2015 at 11:12 AM, Sinthuja Ragendran <sinth...@wso2.com>
> wrote:
>
>> Hi Nirmal,
>>
>> Yes that is the expected behaviour, when the receiver queue is full.
>>
>
> Exactly,
.
On Mon, Aug 31, 2015 at 10:37 PM, Nirmal Fernando <nir...@wso2.com> wrote:
> All,
>
> Sorry for jumping in. But, shouldn't we expect this behaviour when we are
> using a blocking executor?
>
> On Tue, Sep 1, 2015 at 11:00 AM, Sinthuja Ragendran <sinth...@wso2.c
m/
> *E-mail* : mani...@wso2.com
> *Skype* : @manindae
> *Twitter* : @maninda
>
> On Tue, Sep 1, 2015 at 8:06 AM, Sinthuja Ragendran <sinth...@wso2.com>
> wrote:
>
>> Hi Maninda,
>>
>> I tested this locally now, and I was able to see some hickups when
Are you running with debug mode in logging? And can you constantly
reproduce this? Or it's intermittent?
Please provide the publisher and receiver side configs to test this and
see. As I have already tested more than 10M records, I'm not sure what is
the case here.
Thanks,
Sinthuja.
On Monday,
.
Thanks,
Sinthuja.
On Fri, Aug 28, 2015 at 9:15 AM, Sinthuja Ragendran sinth...@wso2.com
wrote:
Hi Thanuja,
Yes, the entire sample was working before. Let me check with latest pack
and see whether there are issues.
Thanks,
Sinthuja
On Friday, August 28, 2015, Thanuja Uruththirakodeeswaran
the sample car
file to DAS, but I couldn't see its dashboard or gadgets in DAS analytics
dashboard portal.
Thanks.
On Mon, Aug 17, 2015 at 5:47 PM, Sinthuja Ragendran sinth...@wso2.com
javascript:_e(%7B%7D,'cvml','sinth...@wso2.com'); wrote:
Hi Thanuja,
On Mon, Aug 17, 2015 at 5:38 PM
Hi Chanaka,
Now there are no different APIs exist for loadbalancing endpoint and single
endpoint, and same DataPublisher API will be used to both. For example, if
you need loadbalancing endpoints, then you can pass the URL as comma
separated as before to the DataPublisher API, then it will
into the sample.
Regards,
Chanaka
On Wed, Aug 26, 2015 at 8:48 PM, Sinthuja Ragendran sinth...@wso2.com
wrote:
Hi Chanaka,
Now there are no different APIs exist for loadbalancing endpoint and
single endpoint, and same DataPublisher API will be used to both. For
example, if you need
Hi Thanuja,
You can set the cron expression with CronExpression element in the spark
script artifact xml as shown below.
?xml version=1.0 encoding=UTF-8 standalone=yes?
Analytics
NameAddNewScriptTestWithouTask/Name
Scriptdefine table TEST_CAPP (server_name string, ip STRING, tenant
/blob/master/modules/samples/capps/Httpd_Log_Analytics/artifacts.xml
Thanks.
On Mon, Aug 17, 2015 at 4:21 PM, Sinthuja Ragendran sinth...@wso2.com
wrote:
Hi Thanuja,
You can set the cron expression with CronExpression element in the spark
script artifact xml as shown below.
?xml version=1.0
the purging task and come-up with suitable input like
retention period, purge enabled tables etc.
Regards,
Gihan
On Mon, Jun 29, 2015 at 2:38 PM, Sinthuja Ragendran sinth...@wso2.com
wrote:
Hi Nirmal,
When the purging disabled, if there is already registered purging task
then it'll
)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
On Mon, Jun 29, 2015 at 12:16 PM, Sinthuja Ragendran sinth...@wso2.com
wrote:
Hi nirmal,
DAS features such as scripts scheduling, purging,etc are used
Hi nirmal,
DAS features such as scripts scheduling, purging,etc are used to submit the
jobs (only spark queries) to external spark cluster, rather those DAS
features jars doesn't need to exists within the external spark cluster
instance. For example, if we consider spark script scheduled
/purge-include-table-patterns
data-retention-days365/data-retention-days
/analytics-data-purging
On Mon, Jun 29, 2015 at 1:57 PM, Sinthuja Ragendran sinth...@wso2.com
wrote:
Hi Nirmal,
Thanks for sharing the necessary details. It's due to the data purging
configuration has been
On Sunday, June 28, 2015, Niranda Perera nira...@wso2.com wrote:
Hi all,
I'm in the process of upgrading spark-core to 1.4. on of it's dependencies
needs guava 15.0 in runtime.
I see that data bridge core and event receiver core bundles use guava
14.0.1. would it be a problem if I update
Hi Rukshan,
I believe you are looking into the persisting the stream events into DAS.
For that, first you need to enable the persisting for the stream. Then you
need to create the EventReceiver for the specific stream with the type of
event you are going to receive, therefore if you are going
Hi sajith,
This happens because you are using the same streamd Id (stream name +
version), and expecting to have two different stream definitions, which is
wrong. Therefore please change the stream Id by changing the stream name Or
the version in the BAM mediator, and update the necessary proxy
that exception even after rectifying stream
definition errors.
On Mon, Jun 22, 2015 at 12:35 PM, Sinthuja Ragendran sinth...@wso2.com
wrote:
Hi sajith,
This happens because you are using the same streamd Id (stream name +
version), and expecting to have two different stream definitions, which
, 2015 at 4:21 PM, Sinthuja Ragendran sinth...@wso2.com
wrote:
Hi Niranjan,
Do we have the cipher tool as a feature now? If so can you please provide
the name of the feature we need to include in the product.
Thanks,
Sinthuja
On Mon, May 25, 2015 at 1:06 PM, Niranjan Karunanandham
niran
Hi Nirmal,
This is fixed in master branch [1], and will be available in DAS beta pack.
[1] https://wso2.org/jira/browse/BAM-2043
Thanks,
Sinthuja
On Wed, Jun 17, 2015 at 12:21 PM, Nirmal Fernando nir...@wso2.com wrote:
Thanks Tharik. Why can't we have the empty directories? This would help
Hi Niranjan,
Do we have the cipher tool as a feature now? If so can you please provide
the name of the feature we need to include in the product.
Thanks,
Sinthuja
On Mon, May 25, 2015 at 1:06 PM, Niranjan Karunanandham niran...@wso2.com
wrote:
Hi Hemika,
Currently we are in the process of
Hi all,
It is already fixed as I mentioned in the other mail thread.
Thanks,
Sinthuja.
On Wed, Jun 17, 2015 at 2:10 PM, Anjana Fernando anj...@wso2.com wrote:
It may not be by default created. When you add a new stream, it will be
created. And also, we already have a JIRA for cleaning up the
Hi,
On Fri, May 22, 2015 at 11:19 AM, Niranjan Karunanandham niran...@wso2.com
wrote:
Hi Anjana,
Kind reminder.
Regards,
Nira
On Thu, May 21, 2015 at 4:49 PM, Ruchira Wageesha ruch...@wso2.com
wrote:
On Tue, May 19, 2015 at 5:52 PM, Niranjan Karunanandham
niran...@wso2.com wrote:
Hi,
Our DAS is a combination of realtime (CEP) and batch processing analytics.
Therefore DAS have included all CEP related features. Currently the CEP
related features are listed as attached screenshot, under 'Event
Processor'. But this current separation is not intuitive, and doesn't show
the
Hi,
AFAIR this happens if any uncaught exception thrown during the bundle
activate method. Try to catch with throwable and see whether you are
getting any sort of runtime exceptions.
Thanks,
Sinthuja
On Thu, May 7, 2015 at 6:59 PM, Bhathiya Jayasekara bhath...@wso2.com
wrote:
Hi all,
I'm
/api/lifecycle/APIManagerConfigurationChangeTest.java
Thanks and Best Regards,
Saneth Dharmakeerthi
Senior Software Engineer
WSO2, Inc.
Mobile: +94772325511
On Wed, Apr 22, 2015 at 7:32 PM, Sinthuja Ragendran sinth...@wso2.com
wrote:
Hi QAA team,
I have a requirement in DAS integration
Hi QAA team,
I have a requirement in DAS integration test to change a configuration file
and run the whole integration tests again.
Basically in DAS we have a core API which can run in LOCAL mode by using
osgi services, and REMOTE mode by connecting to a remote services in a
distributed setup.
Hi,
The WSO2 DAS team is pleased to announce the fourth milestone release of
WSO2 DAS v3.0. The distribution is available at [1]. The release includes
the following new features, improvements, and tasks.
Improvement
- [BAM-1975 https://wso2.org/jira/browse/BAM-1975] - Need to ensure
that
1 - 100 of 284 matches
Mail list logo