[Dev] Error while starting BAM with API-M toolbox.
[2013-04-02 14:34:01,540] INFO
{org.wso2.carbon.bam.toolbox.deployer.core.BAMToolBoxDeployer} - Deployed
successfully file:
/Users/azeez/software/wso2bam-2.2.0/repository/deployment/server/bam-toolbox/API_Manager_Analytics.tbox
[2013-04-02 14:34:01,549] ERROR
{org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Error in
scheduling task: The task with name: am_stats_analyzer_115, already started.
org.wso2.carbon.ntask.common.TaskException: The task with name:
am_stats_analyzer_115, already started.
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalTask(AbstractQuartzTaskManager.java:195)
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalTask(AbstractQuartzTaskManager.java:183)
at
org.wso2.carbon.ntask.core.impl.standalone.StandaloneTaskManager.scheduleTask(StandaloneTaskManager.java:43)
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalAllTasks(AbstractQuartzTaskManager.java:174)
at
org.wso2.carbon.ntask.core.impl.standalone.StandaloneTaskManager.scheduleAllTasks(StandaloneTaskManager.java:38)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.initTaskManagersForType(TaskServiceImpl.java:119)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.serverInitialized(TaskServiceImpl.java:154)
at
org.wso2.carbon.ntask.core.TaskStartupHandler.invoke(TaskStartupHandler.java:39)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.startup(CarbonCoreServiceComponent.java:169)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:202)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:279)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
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:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.server.admin.internal.ServerAdminServiceComponent.activate(ServerAdminServiceComponent.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
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:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
Re: [Dev] Error while starting BAM with API-M toolbox.
More errors when the task runs.
[2013-04-02 14:38:00,004] INFO
{org.wso2.carbon.analytics.hive.task.HiveScriptExecutorTask} - Running
script executor task for script am_stats_analyzer_115. [Tue Apr 02 14:38:00
IST 2013]
Hive history
file=/Users/azeez/software/wso2bam-2.2.0/tmp/hive/wso2-querylogs/hive_job_log_azeez_201304021436_493388221.txt
[2013-04-02 14:38:00,207] ERROR
{org.apache.hadoop.hive.cassandra.CassandraProxyClient} - Error while
trying to connect to cassandra host:127.0.0.1
org.apache.hadoop.hive.cassandra.CassandraException: unable to connect to
server
at
org.apache.hadoop.hive.cassandra.CassandraClientHolder.initClient(CassandraClientHolder.java:57)
at
org.apache.hadoop.hive.cassandra.CassandraClientHolder.init(CassandraClientHolder.java:37)
at
org.apache.hadoop.hive.cassandra.CassandraProxyClient.createConnection(CassandraProxyClient.java:181)
at
org.apache.hadoop.hive.cassandra.CassandraProxyClient.initializeConnection(CassandraProxyClient.java:207)
at
org.apache.hadoop.hive.cassandra.CassandraProxyClient.init(CassandraProxyClient.java:144)
at
org.apache.hadoop.hive.cassandra.CassandraManager.openConnection(CassandraManager.java:113)
at
org.apache.hadoop.hive.cassandra.CassandraStorageHandler.preCreateTable(CassandraStorageHandler.java:168)
at
org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:397)
at org.apache.hadoop.hive.ql.metadata.Hive.createTable(Hive.java:540)
at org.apache.hadoop.hive.ql.exec.DDLTask.createTable(DDLTask.java:3479)
at org.apache.hadoop.hive.ql.exec.DDLTask.execute(DDLTask.java:225)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:133)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1351)
at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1126)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:934)
at
org.apache.hadoop.hive.service.HiveServer$HiveServerHandler.execute(HiveServer.java:201)
at
org.apache.hadoop.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:187)
at
org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl$ScriptCallable.call(HiveExecutorServiceImpl.java:317)
at
org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl$ScriptCallable.call(HiveExecutorServiceImpl.java:217)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:680)
Caused by: org.apache.thrift.transport.TTransportException:
java.net.ConnectException: Connection refused
at org.apache.thrift.transport.TSocket.open(TSocket.java:183)
at
org.apache.thrift.transport.TFramedTransport.open(TFramedTransport.java:81)
at
org.apache.hadoop.hive.cassandra.CassandraClientHolder.initClient(CassandraClientHolder.java:54)
... 24 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432)
at java.net.Socket.connect(Socket.java:529)
at org.apache.thrift.transport.TSocket.open(TSocket.java:178)
... 26 more
FAILED: Error in metadata: java.lang.NullPointerException
[2013-04-02 14:38:00,209] ERROR {org.apache.hadoop.hive.ql.exec.Task} -
FAILED: Error in metadata: java.lang.NullPointerException
org.apache.hadoop.hive.ql.metadata.HiveException:
java.lang.NullPointerException
at org.apache.hadoop.hive.ql.metadata.Hive.createTable(Hive.java:546)
at org.apache.hadoop.hive.ql.exec.DDLTask.createTable(DDLTask.java:3479)
at org.apache.hadoop.hive.ql.exec.DDLTask.execute(DDLTask.java:225)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:133)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1351)
at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1126)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:934)
at
org.apache.hadoop.hive.service.HiveServer$HiveServerHandler.execute(HiveServer.java:201)
at
org.apache.hadoop.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:187)
at
org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl$ScriptCallable.call(HiveExecutorServiceImpl.java:317)
at
org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl$ScriptCallable.call(HiveExecutorServiceImpl.java:217)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
Re: [Dev] Error while starting BAM with API-M toolbox.
Yes we have tested bam 2.0.1 with AM 1.3.1 and worked fine.
Thanks.
Sanjeewa.
On Tue, Apr 2, 2013 at 3:13 PM, Afkham Azeez az...@wso2.com wrote:
Yes, BAM 2.2.0. So, if I use an older version of BAM will it work?
On Tue, Apr 2, 2013 at 2:58 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Hi Azeez,
Its seems you are using BAM 2.2.0. There were known bug in integrating AM
1.4.0 and BAM 2.2.0. BAM team identified the reason for that and they will
fix it for next release. But the errors reported by you are bit different
with what we got. We will investigate more and update thread.
Thanks.
Sanjeewa.
On Tue, Apr 2, 2013 at 2:35 PM, Afkham Azeez az...@wso2.com wrote:
[2013-04-02 14:34:01,540] INFO
{org.wso2.carbon.bam.toolbox.deployer.core.BAMToolBoxDeployer} - Deployed
successfully file:
/Users/azeez/software/wso2bam-2.2.0/repository/deployment/server/bam-toolbox/API_Manager_Analytics.tbox
[2013-04-02 14:34:01,549] ERROR
{org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Error in
scheduling task: The task with name: am_stats_analyzer_115, already started.
org.wso2.carbon.ntask.common.TaskException: The task with name:
am_stats_analyzer_115, already started.
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalTask(AbstractQuartzTaskManager.java:195)
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalTask(AbstractQuartzTaskManager.java:183)
at
org.wso2.carbon.ntask.core.impl.standalone.StandaloneTaskManager.scheduleTask(StandaloneTaskManager.java:43)
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalAllTasks(AbstractQuartzTaskManager.java:174)
at
org.wso2.carbon.ntask.core.impl.standalone.StandaloneTaskManager.scheduleAllTasks(StandaloneTaskManager.java:38)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.initTaskManagersForType(TaskServiceImpl.java:119)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.serverInitialized(TaskServiceImpl.java:154)
at
org.wso2.carbon.ntask.core.TaskStartupHandler.invoke(TaskStartupHandler.java:39)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.startup(CarbonCoreServiceComponent.java:169)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:202)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:279)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
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:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.server.admin.internal.ServerAdminServiceComponent.activate(ServerAdminServiceComponent.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
Re: [Dev] Error while starting BAM with API-M toolbox.
Hi Azeez,
The reason for this exception is:
The AM folks assume you will run the BAM ports with offset 1. I assume your
port offset is different? The ports are embedded in the scripts which is
causing the error. The connection refused error is the clue to this.
It would be great if you can log any of these issues as JIRAs as we are
doing a release focused on bug fixes and usability improvements for BAM
2.3.0.
Sanjeewa, this is not the first person who ran into these issues with AM
and BAM. I'm wondering why this wasn't noticed before (not tested?).
Anyways, please shout if anything is not working as breaking compatibility
between minor releases should not happen. I believe we need to fix this for
BAM 2.3.0.
On Tue, Apr 2, 2013 at 2:48 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Yes we have tested bam 2.0.1 with AM 1.3.1 and worked fine.
Thanks.
Sanjeewa.
On Tue, Apr 2, 2013 at 3:13 PM, Afkham Azeez az...@wso2.com wrote:
Yes, BAM 2.2.0. So, if I use an older version of BAM will it work?
On Tue, Apr 2, 2013 at 2:58 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Hi Azeez,
Its seems you are using BAM 2.2.0. There were known bug in integrating
AM 1.4.0 and BAM 2.2.0. BAM team identified the reason for that and they
will fix it for next release. But the errors reported by you are bit
different with what we got. We will investigate more and update thread.
Thanks.
Sanjeewa.
On Tue, Apr 2, 2013 at 2:35 PM, Afkham Azeez az...@wso2.com wrote:
[2013-04-02 14:34:01,540] INFO
{org.wso2.carbon.bam.toolbox.deployer.core.BAMToolBoxDeployer} - Deployed
successfully file:
/Users/azeez/software/wso2bam-2.2.0/repository/deployment/server/bam-toolbox/API_Manager_Analytics.tbox
[2013-04-02 14:34:01,549] ERROR
{org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Error in
scheduling task: The task with name: am_stats_analyzer_115, already
started.
org.wso2.carbon.ntask.common.TaskException: The task with name:
am_stats_analyzer_115, already started.
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalTask(AbstractQuartzTaskManager.java:195)
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalTask(AbstractQuartzTaskManager.java:183)
at
org.wso2.carbon.ntask.core.impl.standalone.StandaloneTaskManager.scheduleTask(StandaloneTaskManager.java:43)
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalAllTasks(AbstractQuartzTaskManager.java:174)
at
org.wso2.carbon.ntask.core.impl.standalone.StandaloneTaskManager.scheduleAllTasks(StandaloneTaskManager.java:38)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.initTaskManagersForType(TaskServiceImpl.java:119)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.serverInitialized(TaskServiceImpl.java:154)
at
org.wso2.carbon.ntask.core.TaskStartupHandler.invoke(TaskStartupHandler.java:39)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.startup(CarbonCoreServiceComponent.java:169)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:202)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:279)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
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:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.server.admin.internal.ServerAdminServiceComponent.activate(ServerAdminServiceComponent.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
Re: [Dev] Error while starting BAM with API-M toolbox.
On Tue, Apr 2, 2013 at 11:45 PM, Tharindu Mathew thari...@wso2.com wrote:
Hi Azeez,
The reason for this exception is:
The AM folks assume you will run the BAM ports with offset 1. I assume
your port offset is different? The ports are embedded in the scripts which
is causing the error. The connection refused error is the clue to this.
It would be great if you can log any of these issues as JIRAs as we are
doing a release focused on bug fixes and usability improvements for BAM
2.3.0.
Sanjeewa, this is not the first person who ran into these issues with AM
and BAM. I'm wondering why this wasn't noticed before (not tested?).
Anyways, please shout if anything is not working as breaking compatibility
between minor releases should not happen. I believe we need to fix this for
BAM 2.3.0.
Hi Tharindhu,
Noted your point. Instructions about port offset is clearly documented in
statistics readme file. See following instruction[1]. The issue mentioned
by me is not related to port offset and it is still under separate internal
discussion. When we release API manager 1.3.1 we did test with bam 2.0.1
and now for API manager 1.4.0 we started testing with BAM 2.2.0
and uncovered this bug. From here onward we will test toolbox and stats
related operations for BAM releases as well.
[1]
-
Configuring BAM
-
1. Extract the BAM binary distribution to your local file system.
2. Change port offset to 1 by editing the repository/conf/carbon.xml
3. Copy the API_Manager_Analytics.tbox to
repository/deployment/server/bam-toolbox
Thanks.
Sanjeewa.
On Tue, Apr 2, 2013 at 2:48 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Yes we have tested bam 2.0.1 with AM 1.3.1 and worked fine.
Thanks.
Sanjeewa.
On Tue, Apr 2, 2013 at 3:13 PM, Afkham Azeez az...@wso2.com wrote:
Yes, BAM 2.2.0. So, if I use an older version of BAM will it work?
On Tue, Apr 2, 2013 at 2:58 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Hi Azeez,
Its seems you are using BAM 2.2.0. There were known bug in integrating
AM 1.4.0 and BAM 2.2.0. BAM team identified the reason for that and they
will fix it for next release. But the errors reported by you are bit
different with what we got. We will investigate more and update thread.
Thanks.
Sanjeewa.
On Tue, Apr 2, 2013 at 2:35 PM, Afkham Azeez az...@wso2.com wrote:
[2013-04-02 14:34:01,540] INFO
{org.wso2.carbon.bam.toolbox.deployer.core.BAMToolBoxDeployer} - Deployed
successfully file:
/Users/azeez/software/wso2bam-2.2.0/repository/deployment/server/bam-toolbox/API_Manager_Analytics.tbox
[2013-04-02 14:34:01,549] ERROR
{org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Error in
scheduling task: The task with name: am_stats_analyzer_115, already
started.
org.wso2.carbon.ntask.common.TaskException: The task with name:
am_stats_analyzer_115, already started.
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalTask(AbstractQuartzTaskManager.java:195)
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalTask(AbstractQuartzTaskManager.java:183)
at
org.wso2.carbon.ntask.core.impl.standalone.StandaloneTaskManager.scheduleTask(StandaloneTaskManager.java:43)
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalAllTasks(AbstractQuartzTaskManager.java:174)
at
org.wso2.carbon.ntask.core.impl.standalone.StandaloneTaskManager.scheduleAllTasks(StandaloneTaskManager.java:38)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.initTaskManagersForType(TaskServiceImpl.java:119)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.serverInitialized(TaskServiceImpl.java:154)
at
org.wso2.carbon.ntask.core.TaskStartupHandler.invoke(TaskStartupHandler.java:39)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.startup(CarbonCoreServiceComponent.java:169)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:202)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:279)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
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:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
