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.com>wrote:
>
>> 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.com>wrote:
>>>
>>>> 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
>>>>> 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.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:513)
>>>>> at
>>>>> org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:290)
>>>>> at
>>>>> org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:118)
>>>>> at
>>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:847)
>>>>> at
>>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>>> at
>>>>> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
>>>>>
>>>>>
>>>>> What could be the problem?
>>>>>
>>>>> --
>>>>> *Afkham Azeez*
>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>>> * <http://www.apache.org/>**
>>>>> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919
>>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>>>>> twitter:
>>>>> **http://twitter.com/afkham_azeez*<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
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Sanjeewa Malalgoda*
>>>> WSO2 Inc.
>>>> Mobile : +14084122175 | +94713068779
>>>>
>>>> <http://sanjeewamalalgoda.blogspot.com/>blog
>>>> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/>
>>>>
>>>
>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * <http://www.apache.org/>**
>>> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919
>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>> *
>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>
>>
>>
>> --
>> *Sanjeewa Malalgoda*
>> WSO2 Inc.
>> Mobile : +14084122175 | +94713068779
>>
>> <http://sanjeewamalalgoda.blogspot.com/>blog
>> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/>
>>
>
>
>
> --
> Regards,
>
> Tharindu Mathew
>
> Associate Technical Lead, WSO2 BAM
> Member - Data Mgmt. Committee
>
> blog: http://tharindumathew.com/
> M: +94777759908
>
--
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +14084122175 | +94713068779
<http://sanjeewamalalgoda.blogspot.com/>blog
:http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
