Hi,
We use the "worker" module ALONE, and the EI_Analytics_StatApp.siddhi file
alone too (all other siddhi files removed form the repository
worker/deployment/siddhi-files.
So I do NOT need the WSO2AM_MGW_ANALYTICS_DB database, but if not defined in
the worker file deployment.yaml I get this error :
[2019-04-15 13:57:03,201] ERROR
{org.wso2.extension.siddhi.io.mgwfile.MGWFileSourceDS} - error occurred while
fetching the data source.
org.wso2.carbon.datasource.core.exception.DataSourceException: Cannot find the
data source: WSO2AM_MGW_ANALYTICS_DB
at
org.wso2.carbon.datasource.core.impl.DataSourceServiceImpl.getDataSource(DataSourceServiceImpl.java:42)
at
org.wso2.extension.siddhi.io.mgwfile.MGWFileSourceDS.onDataSourceServiceReady(MGWFileSourceDS.java:138)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:376)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:444)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bind(ServiceComponentProp.java:218)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:343)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:109)
at
org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:915)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:862)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:801)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:127)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:225)
at
org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:464)
at
org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:482)
at
org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:999)
at
org.wso2.carbon.datasource.core.internal.DataSourceListenerComponent.onAllRequiredCapabilitiesAvailable(DataSourceListenerComponent.java:128)
at
org.wso2.carbon.kernel.internal.startupresolver.StartupComponentManager.lambda$notifySatisfiableComponents$7(StartupComponentManager.java:266)
at java.util.ArrayList.forEach(ArrayList.java:1257)
at
org.wso2.carbon.kernel.internal.startupresolver.StartupComponentManager.notifySatisfiableComponents(StartupComponentManager.java:252)
at
org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver$1.run(StartupOrderResolver.java:204)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
[2019-04-15 13:57:03,441] INFO
{org.wso2.carbon.event.simulator.core.service.CSVFileDeployer} - CSV file
deployer initiated.
[2019-04-15 13:57:03,451] INFO
{org.wso2.carbon.event.simulator.core.service.SimulationConfigDeployer} -
Simulation config deployer initiated.
[2019-04-15 13:57:03,556] INFO {org.wso2.msf4j.MicroservicesRunner} -
Microservices server started in 95ms
[2019-04-15 13:57:03,556] INFO {org.wso2.msf4j.MicroservicesRunner} -
Microservices server started in 96ms
[2019-04-15 13:57:03,577] INFO
{org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector}
- HTTP(S) Interface starting on host 0.0.0.0 and port 7443
[2019-04-15 13:57:03,577] INFO
{org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector}
- HTTP(S) Interface starting on host 0.0.0.0 and port 7070
[2019-04-15 13:57:03,581] INFO
{org.wso2.carbon.stream.processor.statistics.api.StatisticsApi} -
org.wso2.carbon.stream.processor.statistics.api.StatisticsApi service component
has started.
[2019-04-15 13:57:03,583] INFO
{org.wso2.carbon.stream.processor.statistics.internal.service.OperatingSystemMetricsServiceComponent}
- OperatingSystemMetricsService Component activated
[2019-04-15 13:57:03,627] INFO
{org.wso2.carbon.databridge.receiver.binary.internal.BinaryDataReceiverServiceComponent}
- org.wso2.carbon.databridge.receiver.binary.internal.Service Component is
activated
[2019-04-15 13:57:03,641] INFO
{org.wso2.carbon.databridge.receiver.binary.internal.BinaryDataReceiver} -
Started Binary SSL Transport on port : 9712
[2019-04-15 13:57:03,644] INFO
{org.wso2.carbon.databridge.receiver.binary.internal.BinaryDataReceiver} -
Started Binary TCP Transport on port : 9612
[2019-04-15 13:57:03,646] INFO
{org.wso2.carbon.databridge.receiver.thrift.internal.ThriftDataReceiverDS} -
Service Component is activated
[2019-04-15 13:57:03,661] INFO
{org.wso2.carbon.databridge.receiver.thrift.ThriftDataReceiver} - Thrift Server
started at 0.0.0.0
[2019-04-15 13:57:03,673] INFO
{org.wso2.carbon.databridge.receiver.thrift.ThriftDataReceiver} - Thrift SSL
port : 7712
[2019-04-15 13:57:03,677] INFO
{org.wso2.carbon.databridge.receiver.thrift.ThriftDataReceiver} - Thrift port :
7612
[2019-04-15 13:57:04,130] INFO {org.wso2.msf4j.internal.MicroservicesServerSC}
- All microservices are available
[2019-04-15 13:57:04,148] INFO
{org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector}
- HTTP(S) Interface starting on host 0.0.0.0 and port 9090
[2019-04-15 13:57:04,148] INFO
{org.wso2.transport.http.netty.contractimpl.listener.ServerConnectorBootstrap$HttpServerConnector}
- HTTP(S) Interface starting on host 0.0.0.0 and port 9443
[2019-04-15 13:57:04,217] ERROR
{org.wso2.extension.siddhi.io.mgwfile.task.MGWFileCleanUpTask} - Error occurred
while cleaning the uploaded usage data.
org.wso2.extension.siddhi.io.mgwfile.exception.MGWFileSourceException: Error
occurred while deleting old uploaded files.
at
org.wso2.extension.siddhi.io.mgwfile.dao.MGWFileSourceDAO.deleteProcessedOldFiles(MGWFileSourceDAO.java:257)
at
org.wso2.extension.siddhi.io.mgwfile.task.MGWFileCleanUpTask.run(MGWFileCleanUpTask.java:66)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Caused by: java.sql.SQLException: Data source is not configured properly.
at
org.wso2.extension.siddhi.io.mgwfile.util.MGWFileSourceDBUtil.getConnection(MGWFileSourceDBUtil.java:49)
at
org.wso2.extension.siddhi.io.mgwfile.dao.MGWFileSourceDAO.deleteProcessedOldFiles(MGWFileSourceDAO.java:242)
... 3 more
[2019-04-15 13:57:04,970] INFO {org.quartz.impl.StdSchedulerFactory} - Using
default implementation for ThreadExecutor
[2019-04-15 13:57:04,973] INFO {org.quartz.simpl.SimpleThreadPool} - Job
execution threads will use class loader of thread: Timer-0
[2019-04-15 13:57:05,011] INFO {org.quartz.core.SchedulerSignalerImpl} -
Initialized Scheduler Signaller of type: class
org.quartz.core.SchedulerSignalerImpl
[2019-04-15 13:57:05,012] INFO {org.quartz.core.QuartzScheduler} - Quartz
Scheduler v.2.1.1 created.
[2019-04-15 13:57:05,014] INFO {org.quartz.simpl.RAMJobStore} - RAMJobStore
initialized.
[2019-04-15 13:57:05,016] INFO {org.quartz.core.QuartzScheduler} - Scheduler
meta-data: Quartz Scheduler (v2.1.1) 'DefaultQuartzScheduler' with instanceId
'NON_CLUSTERED'
Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support
persistence. and is not clustered.
[2019-04-15 13:57:05,016] INFO {org.quartz.impl.StdSchedulerFactory} - Quartz
scheduler 'DefaultQuartzScheduler' initialized from default resource file in
Quartz package: 'quartz.properties'
[2019-04-15 13:57:05,016] INFO {org.quartz.impl.StdSchedulerFactory} - Quartz
scheduler version: 2.1.1
[2019-04-15 13:57:05,017] INFO {org.quartz.core.QuartzScheduler} - Scheduler
DefaultQuartzScheduler_$_NON_CLUSTERED started.
[2019-04-15 13:57:05,379] INFO
{org.wso2.siddhi.core.aggregation.IncrementalDataPurging} - Data purging has
enabled for tables: SECONDS,MINUTES,HOURS,DAYS,MONTHS,YEARS, with an interval
of 3600 seconds in ESBStatAgg aggregation
[2019-04-15 13:57:05,379] INFO
{org.wso2.siddhi.core.aggregation.IncrementalDataPurging} - Data purging has
enabled for tables: SECONDS,MINUTES,HOURS,DAYS,MONTHS,YEARS, with an interval
of 3600 seconds in MediatorStatAgg aggregation
[2019-04-15 13:57:05,381] INFO
{org.wso2.carbon.stream.processor.core.internal.StreamProcessorService} -
Siddhi App EI_Analytics_StatApp deployed successfully
[2019-04-15 13:57:05,387] INFO
{org.wso2.carbon.kernel.internal.CarbonStartupHandler} - WSO2 Stream Processor
started in 7.140 sec
Bernard
Le 15 avr. 2019 à 02:13, Eranga Liyanage
<[email protected]<mailto:[email protected]>> a écrit :
Hi All,
Tested Editor Tour Guide, Simulator and Dashboard Monitor and Portal.
[+] Stable - go ahead and release
Regards
Eranga.
On Sun, Apr 14, 2019 at 12:19 AM Tishan Dahanayakage
<[email protected]<mailto:[email protected]>> wrote:
Hi all,
Testes NATS based distributed deployment. No issues found.
Stable - go ahead and release
Thanks,
/Tishan
On Sat, Apr 13, 2019 at 9:59 PM Chiran Fernando
<[email protected]<mailto:[email protected]>> wrote:
HI all,
Tested HTTP source/sink samples, admin REST APIs and simulation. No issues
found.
+1 Go ahead with the release.
On Sat, Apr 13, 2019 at 1:10 PM Damith Wickramasinghe
<[email protected]<mailto:[email protected]>> wrote:
Hi all,
Tested editor design view, fault streams , tour guide, simulation, operator
finder. No issues found.
+1 go ahead and release.
Regards,
Damith
On Sat, Apr 13, 2019 at 3:26 AM Mohanadarshan Vivekanandalingam
<[email protected]<mailto:[email protected]>> wrote:
Hi All,
WSO2 Stream Processor team is pleased to announce the second release candidate
of WSO2 Stream Processor 4.4.0.
WSO2 Stream Processor is an open source embodiment of the WSO2 Analytics
platform, of which the real-time, incremental & intelligent data processing
capabilities let digital businesses create actionable business insights and
data products.
Please find the improvements and fixes related to this release:
*
siddhi<https://github.com/siddhi-io/siddhi/issues?utf8=%E2%9C%93&q=is%3Aissue+closed%3A2018-10-12..2019-04-13>
*
carbon-analytics-common<https://github.com/wso2/carbon-analytics-common/issues?utf8=%E2%9C%93&q=is%3Aissue+closed%3A2018-10-12..2019-04-13>
*
carbon-analytics<https://github.com/wso2/carbon-analytics/issues?utf8=%E2%9C%93&q=is%3Aissue+closed%3A2018-10-12..2019-04-13>
*
carbon-dashboards<https://github.com/wso2/carbon-dashboards/issues?utf8=%E2%9C%93&q=is%3Aissue+closed%3A2018-10-12..2019-04-13>
*
analytics-solutions<https://github.com/wso2/analytics-solutions/issues?utf8=%E2%9C%93&q=is%3Aissue+closed%3A2018-10-12..2019-04-13>
*
product-sp<https://github.com/wso2/product-sp/issues?utf8=%E2%9C%93&q=is%3Aissue+closed%3A2018-10-12..2019-04-13>
You can download the product distribution from
here<https://github.com/wso2/product-sp/releases/download/v4.4.0-RC2/wso2sp-4.4.0-rc2.zip>
The tag to be voted upon:
https://github.com/wso2/product-sp/releases/edit/v4.4.0-RC2
Please download, test the product and vote.
[+] Stable - go ahead and release
[-] Broken - do not release (explain why)
You can find the official documentation in https://docs.wso2.com/display/SP440
<https://docs.wso2.com/display/SP440>
Thanks,
WSO2 Stream Processor Team
--
V. Mohanadarshan | Senior Technical Lead | WSO2 Inc.<http://www.wso2.com/> |
(M) 94-771117673 | (E) [email protected]<mailto:[email protected]> |
GET INTEGRATION AGILE
Integration Agility for Digitally Driven Business
--
Associate Technical Lead | WSO2 Inc.
lean.enterprise.middleware
mobile: +94728671315
_______________________________________________
Dev mailing list
[email protected]<mailto:[email protected]>
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Chiran Fernando
Senior Software Engineer | WSO2
Email : [email protected]<mailto:[email protected]>
Mobile : +94716007376
[http://c.content.wso2.com/signatures/wso2-signature-general.png]<http://wso2.com/signature>
_______________________________________________
Dev mailing list
[email protected]<mailto:[email protected]>
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Tishan Dahanayakage | Associate Technical Lead | WSO2 Inc.
(m) +94716481328 | (w) +94112145345 | (e)
[email protected]<mailto:[email protected]>
GET INTEGRATION AGILE
Integration Agility for Digitally Driven Business
Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not the
intended recipient/s, or believe that you may have received this communication
in error, please reply to the sender indicating that fact and delete the copy
you received and in addition, you should not print, copy, re-transmit,
disseminate, or otherwise use the information contained in this communication.
Internet communications cannot be guaranteed to be timely, secure, error or
virus-free. The sender does not accept liability for any errors or omissions.
_______________________________________________
Architecture mailing list
[email protected]<mailto:[email protected]>
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
Eranga Liyanage | Senior UX Engineer | WSO2 Inc.<https://wso2.com/>
(m) 0773956666 | (e) [email protected]<mailto:[email protected]> | (b)
@erangatl<https://medium.com/@erangatl>
[http://c.content.wso2.com/signatures/wso2-mail-signature-general.png]
_______________________________________________
Dev mailing list
[email protected]<mailto:[email protected]>
http://wso2.org/cgi-bin/mailman/listinfo/dev
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
