[Dev] [APIM] APIManagerComponent Exception occurred while creating JMS Event Adapter

2017-12-04 Thread Senuwan Withana
Hi Team,

I have created a Gateway Cluster following the document [1]. When I started
the server using ./wso2server.sh -Dprofile=gateway-worker command I got
below errors.  Without -Dprofile server was up correctly.

[2017-12-05 09:14:25,262]  INFO - JMSTransportHandler Starting jms topic
consumer thread...
[2017-12-05 09:14:25,284]  WARN - APIManagerComponent Exception occurred
while creating JMS Event Adapter. Request Blocking may not work properly
org.wso2.carbon.event.output.adapter.core.exception.OutputEventAdapterException:
Output Event Adapter not created as no adapter factory is registered with
type jms
at
org.wso2.carbon.event.output.adapter.core.internal.CarbonOutputEventAdapterService.create(CarbonOutputEventAdapterService.java:89)
at
org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.configureJMSPublisher(APIManagerComponent.java:574)
at
org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.activate(APIManagerComponent.java:221)
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.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
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:107)
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:514)
at
org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:94)
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.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
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:107)
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

Re: [Dev] [APIM] APIManagerComponent Exception occurred while creating JMS Event Adapter

2017-12-04 Thread Krishan Wijesena
Hi senuwan,

Before you start server as gateway worker you need to do setup [1]. please
check you did it correctly.

[1]https://docs.wso2.com/display/AM210/Product+Profiles#GWW

Thanks,
krishan.

On Tue, Dec 5, 2017 at 9:22 AM, Senuwan Withana  wrote:

> Hi Team,
>
> I have created a Gateway Cluster following the document [1]. When I
> started the server using ./wso2server.sh -Dprofile=gateway-worker command I
> got below errors.  Without -Dprofile server was up correctly.
>
> [2017-12-05 09:14:25,262]  INFO - JMSTransportHandler Starting jms topic
> consumer thread...
> [2017-12-05 09:14:25,284]  WARN - APIManagerComponent Exception occurred
> while creating JMS Event Adapter. Request Blocking may not work properly
> org.wso2.carbon.event.output.adapter.core.exception.OutputEventAdapterException:
> Output Event Adapter not created as no adapter factory is registered with
> type jms
> at org.wso2.carbon.event.output.adapter.core.internal.
> CarbonOutputEventAdapterService.create(CarbonOutputEventAdapterServic
> e.java:89)
> at org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.
> configureJMSPublisher(APIManagerComponent.java:574)
> at org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.
> activate(APIManagerComponent.java:221)
> 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.ServiceComponent.
> activate(ServiceComponent.java:260)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
> activate(ServiceComponentProp.java:146)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
> build(ServiceComponentProp.java:345)
> 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:107)
> 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:514)
> at org.wso2.carbon.core.init.CarbonServerManager.start(
> CarbonServerManager.java:219)
> at org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(
> CarbonCoreServiceComponent.java:94)
> 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.ServiceComponent.
> activate(ServiceComponent.java:260)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
> activate(ServiceComponentProp.java:146)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
> build(ServiceComponentProp.java:345)
> 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:107)
> 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.
> dispa

Re: [Dev] [APIM] APIManagerComponent Exception occurred while creating JMS Event Adapter

2017-12-04 Thread Samitha Chathuranga
Hi Senuwan,

Please check whether the connection configs to TM is correct, in
api-manager.xml under  under 
as in [1] under the section "Step 3.5 - Configure the Gateway".

[1]
https://docs.wso2.com/display/AM210/Distributed+Deployment+of+API+Manager#DistributedDeploymentofAPIManager-Step3.5-ConfiguretheGateway

Regards,
Samitha

On Tue, Dec 5, 2017 at 9:39 AM, Krishan Wijesena  wrote:

> Hi senuwan,
>
> Before you start server as gateway worker you need to do setup [1]. please
> check you did it correctly.
>
> [1]https://docs.wso2.com/display/AM210/Product+Profiles#GWW
>
> Thanks,
> krishan.
>
> On Tue, Dec 5, 2017 at 9:22 AM, Senuwan Withana  wrote:
>
>> Hi Team,
>>
>> I have created a Gateway Cluster following the document [1]. When I
>> started the server using ./wso2server.sh -Dprofile=gateway-worker command I
>> got below errors.  Without -Dprofile server was up correctly.
>>
>> [2017-12-05 09:14:25,262]  INFO - JMSTransportHandler Starting jms topic
>> consumer thread...
>> [2017-12-05 09:14:25,284]  WARN - APIManagerComponent Exception occurred
>> while creating JMS Event Adapter. Request Blocking may not work properly
>> org.wso2.carbon.event.output.adapter.core.exception.OutputEventAdapterException:
>> Output Event Adapter not created as no adapter factory is registered with
>> type jms
>> at org.wso2.carbon.event.output.adapter.core.internal.CarbonOut
>> putEventAdapterService.create(CarbonOutputEventAdapterService.java:89)
>> at org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.con
>> figureJMSPublisher(APIManagerComponent.java:574)
>> at org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.act
>> ivate(APIManagerComponent.java:221)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponent.activ
>> ate(ServiceComponent.java:260)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.a
>> ctivate(ServiceComponentProp.java:146)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b
>> uild(ServiceComponentProp.java:345)
>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>> nt(InstanceProcess.java:620)
>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>> nts(InstanceProcess.java:197)
>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolve
>> r.java:343)
>> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SC
>> RManager.java:222)
>> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceLis
>> tener.serviceChanged(FilteredServiceListener.java:107)
>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.d
>> ispatchEvent(BundleContextImpl.java:861)
>> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve
>> nt(EventManager.java:230)
>> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEv
>> entSynchronous(ListenerQueue.java:148)
>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.pu
>> blishServiceEventPrivileged(ServiceRegistry.java:819)
>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.pu
>> blishServiceEvent(ServiceRegistry.java:771)
>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistratio
>> nImpl.register(ServiceRegistrationImpl.java:130)
>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.re
>> gisterService(ServiceRegistry.java:214)
>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.r
>> egisterService(BundleContextImpl.java:433)
>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.r
>> egisterService(BundleContextImpl.java:451)
>> at org.wso2.carbon.core.init.CarbonServerManager.initializeCarb
>> on(CarbonServerManager.java:514)
>> at org.wso2.carbon.core.init.CarbonServerManager.start(CarbonSe
>> rverManager.java:219)
>> at org.wso2.carbon.core.internal.CarbonCoreServiceComponent.act
>> ivate(CarbonCoreServiceComponent.java:94)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponent.activ
>> ate(ServiceComponent.java:260)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.a
>> ctivate(ServiceComponentProp.java:146)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b
>> uild(ServiceComponentProp.java:345)
>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>> nt(InstanceProcess.java:620)
>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>> nts(InstanceProcess.java:197)
>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Reso

Re: [Dev] [APIM] APIManagerComponent Exception occurred while creating JMS Event Adapter

2017-12-05 Thread Senuwan Withana
Hi Guys,

Thanks for the update.
I have double checked the mentioned steps. However still I could not able
to find the root cause of this error. I have followed the document
mentioned steps clearly.

Regards,
*Senuwan Withana*
Software Engineer - Support Team | WSO2

Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com



On Tue, Dec 5, 2017 at 10:52 AM, Samitha Chathuranga 
wrote:

> Hi Senuwan,
>
> Please check whether the connection configs to TM is correct, in
> api-manager.xml under  under
>  as in [1] under the section "Step 3.5 -
> Configure the Gateway".
>
> [1] https://docs.wso2.com/display/AM210/Distributed+Deployment+
> of+API+Manager#DistributedDeploymentofAPIManager-Step3.5-
> ConfiguretheGateway
>
> Regards,
> Samitha
>
> On Tue, Dec 5, 2017 at 9:39 AM, Krishan Wijesena 
> wrote:
>
>> Hi senuwan,
>>
>> Before you start server as gateway worker you need to do setup [1].
>> please check you did it correctly.
>>
>> [1]https://docs.wso2.com/display/AM210/Product+Profiles#GWW
>>
>> Thanks,
>> krishan.
>>
>> On Tue, Dec 5, 2017 at 9:22 AM, Senuwan Withana  wrote:
>>
>>> Hi Team,
>>>
>>> I have created a Gateway Cluster following the document [1]. When I
>>> started the server using ./wso2server.sh -Dprofile=gateway-worker command I
>>> got below errors.  Without -Dprofile server was up correctly.
>>>
>>> [2017-12-05 09:14:25,262]  INFO - JMSTransportHandler Starting jms topic
>>> consumer thread...
>>> [2017-12-05 09:14:25,284]  WARN - APIManagerComponent Exception occurred
>>> while creating JMS Event Adapter. Request Blocking may not work properly
>>> org.wso2.carbon.event.output.adapter.core.exception.OutputEventAdapterException:
>>> Output Event Adapter not created as no adapter factory is registered with
>>> type jms
>>> at org.wso2.carbon.event.output.adapter.core.internal.CarbonOut
>>> putEventAdapterService.create(CarbonOutputEventAdapterService.java:89)
>>> at org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.con
>>> figureJMSPublisher(APIManagerComponent.java:574)
>>> at org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.act
>>> ivate(APIManagerComponent.java:221)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>>> ssorImpl.java:62)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>>> thodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>> at org.eclipse.equinox.internal.ds.model.ServiceComponent.activ
>>> ate(ServiceComponent.java:260)
>>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.a
>>> ctivate(ServiceComponentProp.java:146)
>>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b
>>> uild(ServiceComponentProp.java:345)
>>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>>> nt(InstanceProcess.java:620)
>>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>>> nts(InstanceProcess.java:197)
>>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolve
>>> r.java:343)
>>> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SC
>>> RManager.java:222)
>>> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceLis
>>> tener.serviceChanged(FilteredServiceListener.java:107)
>>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.d
>>> ispatchEvent(BundleContextImpl.java:861)
>>> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve
>>> nt(EventManager.java:230)
>>> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEv
>>> entSynchronous(ListenerQueue.java:148)
>>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.pu
>>> blishServiceEventPrivileged(ServiceRegistry.java:819)
>>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.pu
>>> blishServiceEvent(ServiceRegistry.java:771)
>>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistratio
>>> nImpl.register(ServiceRegistrationImpl.java:130)
>>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.re
>>> gisterService(ServiceRegistry.java:214)
>>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.r
>>> egisterService(BundleContextImpl.java:433)
>>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.r
>>> egisterService(BundleContextImpl.java:451)
>>> at org.wso2.carbon.core.init.CarbonServerManager.initializeCarb
>>> on(CarbonServerManager.java:514)
>>> at org.wso2.carbon.core.init.CarbonServerManager.start(CarbonSe
>>> rverManager.java:219)
>>> at org.wso2.carbon.core.internal.CarbonCoreServiceComponent.act
>>> ivate(CarbonCoreServiceComponent.java:94)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>>> ssorImpl.java:62)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>>> thodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>> at org.eclipse.equinox.internal.ds.model.ServiceComponent

Re: [Dev] [APIM] APIManagerComponent Exception occurred while creating JMS Event Adapter

2017-12-05 Thread Abimaran Kugathasan
Hi Senuwan,

The exception says GW can't connect to tcp://10.100.7.13:5674. Have you
telnetted to that IP PORT? If you have distributed set up, have you start
up Traffic Manager?

On Tue, Dec 5, 2017 at 4:27 PM, Senuwan Withana  wrote:

> Hi Guys,
>
> Thanks for the update.
> I have double checked the mentioned steps. However still I could not able
> to find the root cause of this error. I have followed the document
> mentioned steps clearly.
>
> Regards,
> *Senuwan Withana*
> Software Engineer - Support Team | WSO2
>
> Email : senu...@wso2.com
> Mobile: 94773212853
> Web: http://www.wso2.com
>
>
>
> On Tue, Dec 5, 2017 at 10:52 AM, Samitha Chathuranga 
> wrote:
>
>> Hi Senuwan,
>>
>> Please check whether the connection configs to TM is correct, in
>> api-manager.xml under  under
>>  as in [1] under the section "Step 3.5 -
>> Configure the Gateway".
>>
>> [1] https://docs.wso2.com/display/AM210/Distributed+Deployment+o
>> f+API+Manager#DistributedDeploymentofAPIManager-Step3.5-Conf
>> iguretheGateway
>>
>> Regards,
>> Samitha
>>
>> On Tue, Dec 5, 2017 at 9:39 AM, Krishan Wijesena 
>> wrote:
>>
>>> Hi senuwan,
>>>
>>> Before you start server as gateway worker you need to do setup [1].
>>> please check you did it correctly.
>>>
>>> [1]https://docs.wso2.com/display/AM210/Product+Profiles#GWW
>>>
>>> Thanks,
>>> krishan.
>>>
>>> On Tue, Dec 5, 2017 at 9:22 AM, Senuwan Withana 
>>> wrote:
>>>
 Hi Team,

 I have created a Gateway Cluster following the document [1]. When I
 started the server using ./wso2server.sh -Dprofile=gateway-worker command I
 got below errors.  Without -Dprofile server was up correctly.

 [2017-12-05 09:14:25,262]  INFO - JMSTransportHandler Starting jms
 topic consumer thread...
 [2017-12-05 09:14:25,284]  WARN - APIManagerComponent Exception
 occurred while creating JMS Event Adapter. Request Blocking may not work
 properly
 org.wso2.carbon.event.output.adapter.core.exception.OutputEventAdapterException:
 Output Event Adapter not created as no adapter factory is registered with
 type jms
 at org.wso2.carbon.event.output.adapter.core.internal.CarbonOut
 putEventAdapterService.create(CarbonOutputEventAdapterService.java:89)
 at org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.con
 figureJMSPublisher(APIManagerComponent.java:574)
 at org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.act
 ivate(APIManagerComponent.java:221)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
 ssorImpl.java:62)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
 thodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at org.eclipse.equinox.internal.ds.model.ServiceComponent.activ
 ate(ServiceComponent.java:260)
 at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.a
 ctivate(ServiceComponentProp.java:146)
 at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b
 uild(ServiceComponentProp.java:345)
 at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
 nt(InstanceProcess.java:620)
 at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
 nts(InstanceProcess.java:197)
 at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolve
 r.java:343)
 at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SC
 RManager.java:222)
 at org.eclipse.osgi.internal.serviceregistry.FilteredServiceLis
 tener.serviceChanged(FilteredServiceListener.java:107)
 at org.eclipse.osgi.framework.internal.core.BundleContextImpl.d
 ispatchEvent(BundleContextImpl.java:861)
 at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve
 nt(EventManager.java:230)
 at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEv
 entSynchronous(ListenerQueue.java:148)
 at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.pu
 blishServiceEventPrivileged(ServiceRegistry.java:819)
 at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.pu
 blishServiceEvent(ServiceRegistry.java:771)
 at org.eclipse.osgi.internal.serviceregistry.ServiceRegistratio
 nImpl.register(ServiceRegistrationImpl.java:130)
 at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.re
 gisterService(ServiceRegistry.java:214)
 at org.eclipse.osgi.framework.internal.core.BundleContextImpl.r
 egisterService(BundleContextImpl.java:433)
 at org.eclipse.osgi.framework.internal.core.BundleContextImpl.r
 egisterService(BundleContextImpl.java:451)
 at org.wso2.carbon.core.init.CarbonServerManager.initializeCarb
 on(CarbonServerManager.java:514)
 at org.wso2.carbon.core.init.CarbonServerManager.start(CarbonSe
 rverManager.java:219)
 at org.wso2.carbon.core.internal.CarbonCoreServiceComponent.act
 ivate(CarbonCoreServiceComponent.java:94)

Re: [Dev] [APIM] APIManagerComponent Exception occurred while creating JMS Event Adapter

2017-12-05 Thread Chamin Dias
Hi,

Similar issue  has been
reported previously (APIMANAGER-5292) and there it suggests a workaround.
You can try that as well.

Thanks.

On Tue, Dec 5, 2017 at 4:45 PM, Abimaran Kugathasan 
wrote:

> Hi Senuwan,
>
> The exception says GW can't connect to tcp://10.100.7.13:5674. Have you
> telnetted to that IP PORT? If you have distributed set up, have you start
> up Traffic Manager?
>
> On Tue, Dec 5, 2017 at 4:27 PM, Senuwan Withana  wrote:
>
>> Hi Guys,
>>
>> Thanks for the update.
>> I have double checked the mentioned steps. However still I could not able
>> to find the root cause of this error. I have followed the document
>> mentioned steps clearly.
>>
>> Regards,
>> *Senuwan Withana*
>> Software Engineer - Support Team | WSO2
>>
>> Email : senu...@wso2.com
>> Mobile: 94773212853
>> Web: http://www.wso2.com
>>
>>
>>
>> On Tue, Dec 5, 2017 at 10:52 AM, Samitha Chathuranga 
>> wrote:
>>
>>> Hi Senuwan,
>>>
>>> Please check whether the connection configs to TM is correct, in
>>> api-manager.xml under  under
>>>  as in [1] under the section "Step 3.5 -
>>> Configure the Gateway".
>>>
>>> [1] https://docs.wso2.com/display/AM210/Distributed+Deployment+o
>>> f+API+Manager#DistributedDeploymentofAPIManager-Step3.5-Conf
>>> iguretheGateway
>>>
>>> Regards,
>>> Samitha
>>>
>>> On Tue, Dec 5, 2017 at 9:39 AM, Krishan Wijesena 
>>> wrote:
>>>
 Hi senuwan,

 Before you start server as gateway worker you need to do setup [1].
 please check you did it correctly.

 [1]https://docs.wso2.com/display/AM210/Product+Profiles#GWW

 Thanks,
 krishan.

 On Tue, Dec 5, 2017 at 9:22 AM, Senuwan Withana 
 wrote:

> Hi Team,
>
> I have created a Gateway Cluster following the document [1]. When I
> started the server using ./wso2server.sh -Dprofile=gateway-worker command 
> I
> got below errors.  Without -Dprofile server was up correctly.
>
> [2017-12-05 09:14:25,262]  INFO - JMSTransportHandler Starting jms
> topic consumer thread...
> [2017-12-05 09:14:25,284]  WARN - APIManagerComponent Exception
> occurred while creating JMS Event Adapter. Request Blocking may not work
> properly
> org.wso2.carbon.event.output.adapter.core.exception.OutputEventAdapterException:
> Output Event Adapter not created as no adapter factory is registered with
> type jms
> at org.wso2.carbon.event.output.adapter.core.internal.CarbonOut
> putEventAdapterService.create(CarbonOutputEventAdapterService.java:89)
> at org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.con
> figureJMSPublisher(APIManagerComponent.java:574)
> at org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.act
> ivate(APIManagerComponent.java:221)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
> ssorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
> thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.internal.ds.model.ServiceComponent.activ
> ate(ServiceComponent.java:260)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.a
> ctivate(ServiceComponentProp.java:146)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b
> uild(ServiceComponentProp.java:345)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
> nt(InstanceProcess.java:620)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
> nts(InstanceProcess.java:197)
> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolve
> r.java:343)
> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SC
> RManager.java:222)
> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceLis
> tener.serviceChanged(FilteredServiceListener.java:107)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.d
> ispatchEvent(BundleContextImpl.java:861)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve
> nt(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEv
> entSynchronous(ListenerQueue.java:148)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.pu
> blishServiceEventPrivileged(ServiceRegistry.java:819)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.pu
> blishServiceEvent(ServiceRegistry.java:771)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistratio
> nImpl.register(ServiceRegistrationImpl.java:130)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.re
> gisterService(ServiceRegistry.java:214)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.r
> egisterService(BundleContextImpl.java:433)
> at org.eclipse.osgi.framework.internal.core.BundleConte

Re: [Dev] [APIM] APIManagerComponent Exception occurred while creating JMS Event Adapter

2017-12-05 Thread Harsha Kumara
This is a known issue when you start with the profiles. Please comment out
the JMSEventPublisherParameters section in the api-manager.xml. It's stated
in [1].

[1] https://docs.wso2.com/display/CLUSTER44x/Clustering+API+Manager+2.0.0

On Tue, Dec 5, 2017 at 6:32 PM, Chamin Dias  wrote:

> Hi,
>
> Similar issue  has been
> reported previously (APIMANAGER-5292) and there it suggests a workaround.
> You can try that as well.
>
> Thanks.
>
> On Tue, Dec 5, 2017 at 4:45 PM, Abimaran Kugathasan 
> wrote:
>
>> Hi Senuwan,
>>
>> The exception says GW can't connect to tcp://10.100.7.13:5674. Have you
>> telnetted to that IP PORT? If you have distributed set up, have you start
>> up Traffic Manager?
>>
>> On Tue, Dec 5, 2017 at 4:27 PM, Senuwan Withana  wrote:
>>
>>> Hi Guys,
>>>
>>> Thanks for the update.
>>> I have double checked the mentioned steps. However still I could not
>>> able to find the root cause of this error. I have followed the document
>>> mentioned steps clearly.
>>>
>>> Regards,
>>> *Senuwan Withana*
>>> Software Engineer - Support Team | WSO2
>>>
>>> Email : senu...@wso2.com
>>> Mobile: 94773212853
>>> Web: http://www.wso2.com
>>>
>>>
>>>
>>> On Tue, Dec 5, 2017 at 10:52 AM, Samitha Chathuranga 
>>> wrote:
>>>
 Hi Senuwan,

 Please check whether the connection configs to TM is correct, in
 api-manager.xml under  under
  as in [1] under the section "Step 3.5 -
 Configure the Gateway".

 [1] https://docs.wso2.com/display/AM210/Distributed+Deployment+o
 f+API+Manager#DistributedDeploymentofAPIManager-Step3.5-Conf
 iguretheGateway

 Regards,
 Samitha

 On Tue, Dec 5, 2017 at 9:39 AM, Krishan Wijesena 
 wrote:

> Hi senuwan,
>
> Before you start server as gateway worker you need to do setup [1].
> please check you did it correctly.
>
> [1]https://docs.wso2.com/display/AM210/Product+Profiles#GWW
>
> Thanks,
> krishan.
>
> On Tue, Dec 5, 2017 at 9:22 AM, Senuwan Withana 
> wrote:
>
>> Hi Team,
>>
>> I have created a Gateway Cluster following the document [1]. When I
>> started the server using ./wso2server.sh -Dprofile=gateway-worker 
>> command I
>> got below errors.  Without -Dprofile server was up correctly.
>>
>> [2017-12-05 09:14:25,262]  INFO - JMSTransportHandler Starting jms
>> topic consumer thread...
>> [2017-12-05 09:14:25,284]  WARN - APIManagerComponent Exception
>> occurred while creating JMS Event Adapter. Request Blocking may not work
>> properly
>> org.wso2.carbon.event.output.adapter.core.exception.OutputEventAdapterException:
>> Output Event Adapter not created as no adapter factory is registered with
>> type jms
>> at org.wso2.carbon.event.output.adapter.core.internal.CarbonOut
>> putEventAdapterService.create(CarbonOutputEventAdapterServic
>> e.java:89)
>> at org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.con
>> figureJMSPublisher(APIManagerComponent.java:574)
>> at org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.act
>> ivate(APIManagerComponent.java:221)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponent.activ
>> ate(ServiceComponent.java:260)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.a
>> ctivate(ServiceComponentProp.java:146)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b
>> uild(ServiceComponentProp.java:345)
>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>> nt(InstanceProcess.java:620)
>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>> nts(InstanceProcess.java:197)
>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolve
>> r.java:343)
>> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SC
>> RManager.java:222)
>> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceLis
>> tener.serviceChanged(FilteredServiceListener.java:107)
>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.d
>> ispatchEvent(BundleContextImpl.java:861)
>> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve
>> nt(EventManager.java:230)
>> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEv
>> entSynchronous(ListenerQueue.java:148)
>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.pu
>> blishServiceEventPrivileged(ServiceRegistry.java:819)
>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.pu
>> blishServiceEvent(ServiceRegistry.java:7

Re: [Dev] [APIM] APIManagerComponent Exception occurred while creating JMS Event Adapter

2017-12-05 Thread Harsha Kumara
Hi Mari,

We need to update the latest docs as well.

[1 ]https://docs.wso2.com/display/AM210/Product+Profiles#GWW

Thanks,
Harsha

On Tue, Dec 5, 2017 at 6:54 PM, Harsha Kumara  wrote:

> This is a known issue when you start with the profiles. Please comment out
> the JMSEventPublisherParameters section in the api-manager.xml. It's stated
> in [1].
>
> [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+API+Manager+2.0.0
>
> On Tue, Dec 5, 2017 at 6:32 PM, Chamin Dias  wrote:
>
>> Hi,
>>
>> Similar issue  has been
>> reported previously (APIMANAGER-5292) and there it suggests a workaround.
>> You can try that as well.
>>
>> Thanks.
>>
>> On Tue, Dec 5, 2017 at 4:45 PM, Abimaran Kugathasan 
>> wrote:
>>
>>> Hi Senuwan,
>>>
>>> The exception says GW can't connect to tcp://10.100.7.13:5674. Have you
>>> telnetted to that IP PORT? If you have distributed set up, have you start
>>> up Traffic Manager?
>>>
>>> On Tue, Dec 5, 2017 at 4:27 PM, Senuwan Withana 
>>> wrote:
>>>
 Hi Guys,

 Thanks for the update.
 I have double checked the mentioned steps. However still I could not
 able to find the root cause of this error. I have followed the document
 mentioned steps clearly.

 Regards,
 *Senuwan Withana*
 Software Engineer - Support Team | WSO2

 Email : senu...@wso2.com
 Mobile: 94773212853
 Web: http://www.wso2.com



 On Tue, Dec 5, 2017 at 10:52 AM, Samitha Chathuranga 
 wrote:

> Hi Senuwan,
>
> Please check whether the connection configs to TM is correct, in
> api-manager.xml under  under
>  as in [1] under the section "Step 3.5 -
> Configure the Gateway".
>
> [1] https://docs.wso2.com/display/AM210/Distributed+Deployment+o
> f+API+Manager#DistributedDeploymentofAPIManager-Step3.5-Conf
> iguretheGateway
>
> Regards,
> Samitha
>
> On Tue, Dec 5, 2017 at 9:39 AM, Krishan Wijesena 
> wrote:
>
>> Hi senuwan,
>>
>> Before you start server as gateway worker you need to do setup [1].
>> please check you did it correctly.
>>
>> [1]https://docs.wso2.com/display/AM210/Product+Profiles#GWW
>>
>> Thanks,
>> krishan.
>>
>> On Tue, Dec 5, 2017 at 9:22 AM, Senuwan Withana 
>> wrote:
>>
>>> Hi Team,
>>>
>>> I have created a Gateway Cluster following the document [1]. When I
>>> started the server using ./wso2server.sh -Dprofile=gateway-worker 
>>> command I
>>> got below errors.  Without -Dprofile server was up correctly.
>>>
>>> [2017-12-05 09:14:25,262]  INFO - JMSTransportHandler Starting jms
>>> topic consumer thread...
>>> [2017-12-05 09:14:25,284]  WARN - APIManagerComponent Exception
>>> occurred while creating JMS Event Adapter. Request Blocking may not work
>>> properly
>>> org.wso2.carbon.event.output.adapter.core.exception.OutputEventAdapterException:
>>> Output Event Adapter not created as no adapter factory is registered 
>>> with
>>> type jms
>>> at org.wso2.carbon.event.output.adapter.core.internal.CarbonOut
>>> putEventAdapterService.create(CarbonOutputEventAdapterServic
>>> e.java:89)
>>> at org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.con
>>> figureJMSPublisher(APIManagerComponent.java:574)
>>> at org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.act
>>> ivate(APIManagerComponent.java:221)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>>> ssorImpl.java:62)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>>> thodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>> at org.eclipse.equinox.internal.ds.model.ServiceComponent.activ
>>> ate(ServiceComponent.java:260)
>>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.a
>>> ctivate(ServiceComponentProp.java:146)
>>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b
>>> uild(ServiceComponentProp.java:345)
>>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>>> nt(InstanceProcess.java:620)
>>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>>> nts(InstanceProcess.java:197)
>>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolve
>>> r.java:343)
>>> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SC
>>> RManager.java:222)
>>> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceLis
>>> tener.serviceChanged(FilteredServiceListener.java:107)
>>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.d
>>> ispatchEvent(BundleContextImpl.java:861)
>>> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve
>>> nt(EventManager.java:230)
>>> at org.eclipse.osgi.framework

Re: [Dev] [APIM] APIManagerComponent Exception occurred while creating JMS Event Adapter

2017-12-05 Thread Senuwan Withana
Hi Guys

Again Thanks for quick responses. I have looked all the comments and done
the relevant changes
Eg: Comment out the JMSEventPublisherParameters section, Up the TM first.
so on.  However still i got below errors.


[2017-12-05 19:38:30,393]  INFO - JMSTransportHandler Starting jms topic
consumer thread...
[2017-12-05 19:38:30,443]  INFO - APIManagerComponent JMS Publisher not
enabled.
[2017-12-05 19:38:30,632]  INFO - AMQConnection Unable to connect to broker
at tcp://172.16.2.39:5674
org.wso2.andes.transport.TransportException: Could not open connection
at
org.wso2.andes.transport.network.mina.MinaNetworkTransport$IoConnectorCreator.connect(MinaNetworkTransport.java:216)
at
org.wso2.andes.transport.network.mina.MinaNetworkTransport.connect(MinaNetworkTransport.java:74)
at
org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:130)
at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:631)
at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:628)
at java.security.AccessController.doPrivileged(Native Method)
at
org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:628)
at org.wso2.andes.client.AMQConnection.(AMQConnection.java:409)
at
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:351)
at
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:40)
at
org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils.createConnection(JMSUtils.java:387)
at
org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.checkJMSConnection(JMSListener.java:137)
at
org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.start(JMSListener.java:79)
at
org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.run(JMSListener.java:186)
at java.lang.Thread.run(Thread.java:748)
org.wso2.andes.AMQConnectionFailureException: Could not open connection
at org.wso2.andes.client.AMQConnection.(AMQConnection.java:486)
at
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:351)
at
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:40)
at
org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils.createConnection(JMSUtils.java:387)
at
org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.checkJMSConnection(JMSListener.java:137)
at
org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.start(JMSListener.java:79)
at
org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.run(JMSListener.java:186)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.wso2.andes.transport.TransportException: Could not open
connection
at
org.wso2.andes.transport.network.mina.MinaNetworkTransport$IoConnectorCreator.connect(MinaNetworkTransport.java:216)
at
org.wso2.andes.transport.network.mina.MinaNetworkTransport.connect(MinaNetworkTransport.java:74)
at
org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:130)
at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:631)
at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:628)
at java.security.AccessController.doPrivileged(Native Method)
at
org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:628)
at org.wso2.andes.client.AMQConnection.(AMQConnection.java:409)
... 7 more
[2017-12-05 19:38:30,641] ERROR - JMSListener Unable to continue server
startup as it seems the JMS Provider is not yet started. Please start the
JMS provider now.
[2017-12-05 19:38:30,644] ERROR - JMSListener Connection attempt : 1 for
JMS Provider failed. Next retry in 20 seconds
[2017-12-05 19:38:30,733]  INFO - TenantLoadingConfig Using tenant lazy
loading policy...
[2017-12-05 19:38:30,743]  INFO - PermissionUpdater Permission cache
updated for tenant -1234
[2017-12-05 19:38:31,031]  INFO - UserStoreMgtDSComponent Claim manager set
for class org.wso2.carbon.user.core.common.DefaultRealm
[2017-12-05 19:38:31,032]  INFO - UserStoreMgtDSComponent Claim manager set
for class org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager
[2017-12-05 19:38:31,110]  INFO - OAuth2ServiceComponent PKCE Support
enabled.
[2017-12-05 19:38:31,386]  INFO - ServiceBusInitializer Starting ESB...
[2017-12-05 19:38:31,393]  INFO - ServiceBusInitializer Initializing Apache
Synapse...
[2017-12-05 19:38:32,302]  INFO - SynapseControllerFactory Using Synapse
home : /home/senuwan/BackupAssg/WorkerGW/.
[2017-12-05 19:38:32,303]  INFO - SynapseControllerFactory Using
synapse.xml location :
/home/senuwan/BackupAssg/WorkerGW/././repository/deployment/server/synapse-configs/default
[2017-12-05 19:38:32,303]  INFO - SynapseControllerFactory Using server
name : localhost
[2017-12-05 19:38:32,313]  INFO - SynapseControllerFactory The timeout
handler will run every : 15s
[2017-12-05 19:38:32,322]  INFO - Axis2SynapseController Initializing
Synapse at : Tue Dec 05 19:38:32 IST 2017
[2017-12-05 19:38:32,331]  INFO - CarbonSynapseController Loading the
mediation configuration from the file syste

Re: [Dev] [APIM] APIManagerComponent Exception occurred while creating JMS Event Adapter

2017-12-05 Thread Harsha Kumara
Is your TM running with port offset 2?

On Tue, Dec 5, 2017 at 7:43 PM, Senuwan Withana  wrote:

> Hi Guys
>
> Again Thanks for quick responses. I have looked all the comments and done
> the relevant changes
> Eg: Comment out the JMSEventPublisherParameters section, Up the TM first.
> so on.  However still i got below errors.
>
>
> [2017-12-05 19:38:30,393]  INFO - JMSTransportHandler Starting jms topic
> consumer thread...
> [2017-12-05 19:38:30,443]  INFO - APIManagerComponent JMS Publisher not
> enabled.
> [2017-12-05 19:38:30,632]  INFO - AMQConnection Unable to connect to
> broker at tcp://172.16.2.39:5674
> org.wso2.andes.transport.TransportException: Could not open connection
> at org.wso2.andes.transport.network.mina.MinaNetworkTransport$
> IoConnectorCreator.connect(MinaNetworkTransport.java:216)
> at org.wso2.andes.transport.network.mina.MinaNetworkTransport.connect(
> MinaNetworkTransport.java:74)
> at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(
> AMQConnectionDelegate_8_0.java:130)
> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:631)
> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:628)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wso2.andes.client.AMQConnection.makeBrokerConnection(
> AMQConnection.java:628)
> at org.wso2.andes.client.AMQConnection.(AMQConnection.java:409)
> at org.wso2.andes.client.AMQConnectionFactory.createConnection(
> AMQConnectionFactory.java:351)
> at org.wso2.andes.client.AMQConnectionFactory.createConnection(
> AMQConnectionFactory.java:40)
> at org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils.
> createConnection(JMSUtils.java:387)
> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.
> checkJMSConnection(JMSListener.java:137)
> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.
> start(JMSListener.java:79)
> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.
> run(JMSListener.java:186)
> at java.lang.Thread.run(Thread.java:748)
> org.wso2.andes.AMQConnectionFailureException: Could not open connection
> at org.wso2.andes.client.AMQConnection.(AMQConnection.java:486)
> at org.wso2.andes.client.AMQConnectionFactory.createConnection(
> AMQConnectionFactory.java:351)
> at org.wso2.andes.client.AMQConnectionFactory.createConnection(
> AMQConnectionFactory.java:40)
> at org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils.
> createConnection(JMSUtils.java:387)
> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.
> checkJMSConnection(JMSListener.java:137)
> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.
> start(JMSListener.java:79)
> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.
> run(JMSListener.java:186)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.wso2.andes.transport.TransportException: Could not open
> connection
> at org.wso2.andes.transport.network.mina.MinaNetworkTransport$
> IoConnectorCreator.connect(MinaNetworkTransport.java:216)
> at org.wso2.andes.transport.network.mina.MinaNetworkTransport.connect(
> MinaNetworkTransport.java:74)
> at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(
> AMQConnectionDelegate_8_0.java:130)
> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:631)
> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:628)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wso2.andes.client.AMQConnection.makeBrokerConnection(
> AMQConnection.java:628)
> at org.wso2.andes.client.AMQConnection.(AMQConnection.java:409)
> ... 7 more
> [2017-12-05 19:38:30,641] ERROR - JMSListener Unable to continue server
> startup as it seems the JMS Provider is not yet started. Please start the
> JMS provider now.
> [2017-12-05 19:38:30,644] ERROR - JMSListener Connection attempt : 1 for
> JMS Provider failed. Next retry in 20 seconds
> [2017-12-05 19:38:30,733]  INFO - TenantLoadingConfig Using tenant lazy
> loading policy...
> [2017-12-05 19:38:30,743]  INFO - PermissionUpdater Permission cache
> updated for tenant -1234
> [2017-12-05 19:38:31,031]  INFO - UserStoreMgtDSComponent Claim manager
> set for class org.wso2.carbon.user.core.common.DefaultRealm
> [2017-12-05 19:38:31,032]  INFO - UserStoreMgtDSComponent Claim manager
> set for class org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager
> [2017-12-05 19:38:31,110]  INFO - OAuth2ServiceComponent PKCE Support
> enabled.
> [2017-12-05 19:38:31,386]  INFO - ServiceBusInitializer Starting ESB...
> [2017-12-05 19:38:31,393]  INFO - ServiceBusInitializer Initializing
> Apache Synapse...
> [2017-12-05 19:38:32,302]  INFO - SynapseControllerFactory Using Synapse
> home : /home/senuwan/BackupAssg/WorkerGW/.
> [2017-12-05 19:38:32,303]  INFO - SynapseControllerFactory Using
> synapse.xml location : /home/senuwan/BackupAssg/WorkerGW/././repository/
> deployment/server/synapse-configs/default
> [2017-12-05 19:38:32,303]  INFO - SynapseControllerFactory Using server
> name : localhost
> [2017-12-05 19:38:

Re: [Dev] [APIM] APIManagerComponent Exception occurred while creating JMS Event Adapter

2017-12-05 Thread Senuwan Withana
Yes

*Senuwan Withana*
Software Engineer - Support Team | WSO2

Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com



On Tue, Dec 5, 2017 at 7:55 PM, Harsha Kumara  wrote:

> Is your TM running with port offset 2?
>
> On Tue, Dec 5, 2017 at 7:43 PM, Senuwan Withana  wrote:
>
>> Hi Guys
>>
>> Again Thanks for quick responses. I have looked all the comments and done
>> the relevant changes
>> Eg: Comment out the JMSEventPublisherParameters section, Up the TM
>> first. so on.  However still i got below errors.
>>
>>
>> [2017-12-05 19:38:30,393]  INFO - JMSTransportHandler Starting jms topic
>> consumer thread...
>> [2017-12-05 19:38:30,443]  INFO - APIManagerComponent JMS Publisher not
>> enabled.
>> [2017-12-05 19:38:30,632]  INFO - AMQConnection Unable to connect to
>> broker at tcp://172.16.2.39:5674
>> org.wso2.andes.transport.TransportException: Could not open connection
>> at org.wso2.andes.transport.network.mina.MinaNetworkTransport$I
>> oConnectorCreator.connect(MinaNetworkTransport.java:216)
>> at org.wso2.andes.transport.network.mina.MinaNetworkTransport.
>> connect(MinaNetworkTransport.java:74)
>> at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerCo
>> nnection(AMQConnectionDelegate_8_0.java:130)
>> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:631)
>> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:628)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQ
>> Connection.java:628)
>> at org.wso2.andes.client.AMQConnection.(AMQConnection.java:409)
>> at org.wso2.andes.client.AMQConnectionFactory.createConnection(
>> AMQConnectionFactory.java:351)
>> at org.wso2.andes.client.AMQConnectionFactory.createConnection(
>> AMQConnectionFactory.java:40)
>> at org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils.createCon
>> nection(JMSUtils.java:387)
>> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.checkJ
>> MSConnection(JMSListener.java:137)
>> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.start(
>> JMSListener.java:79)
>> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.run(
>> JMSListener.java:186)
>> at java.lang.Thread.run(Thread.java:748)
>> org.wso2.andes.AMQConnectionFailureException: Could not open connection
>> at org.wso2.andes.client.AMQConnection.(AMQConnection.java:486)
>> at org.wso2.andes.client.AMQConnectionFactory.createConnection(
>> AMQConnectionFactory.java:351)
>> at org.wso2.andes.client.AMQConnectionFactory.createConnection(
>> AMQConnectionFactory.java:40)
>> at org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils.createCon
>> nection(JMSUtils.java:387)
>> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.checkJ
>> MSConnection(JMSListener.java:137)
>> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.start(
>> JMSListener.java:79)
>> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.run(
>> JMSListener.java:186)
>> at java.lang.Thread.run(Thread.java:748)
>> Caused by: org.wso2.andes.transport.TransportException: Could not open
>> connection
>> at org.wso2.andes.transport.network.mina.MinaNetworkTransport$I
>> oConnectorCreator.connect(MinaNetworkTransport.java:216)
>> at org.wso2.andes.transport.network.mina.MinaNetworkTransport.
>> connect(MinaNetworkTransport.java:74)
>> at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerCo
>> nnection(AMQConnectionDelegate_8_0.java:130)
>> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:631)
>> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:628)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQ
>> Connection.java:628)
>> at org.wso2.andes.client.AMQConnection.(AMQConnection.java:409)
>> ... 7 more
>> [2017-12-05 19:38:30,641] ERROR - JMSListener Unable to continue server
>> startup as it seems the JMS Provider is not yet started. Please start the
>> JMS provider now.
>> [2017-12-05 19:38:30,644] ERROR - JMSListener Connection attempt : 1 for
>> JMS Provider failed. Next retry in 20 seconds
>> [2017-12-05 19:38:30,733]  INFO - TenantLoadingConfig Using tenant lazy
>> loading policy...
>> [2017-12-05 19:38:30,743]  INFO - PermissionUpdater Permission cache
>> updated for tenant -1234
>> [2017-12-05 19:38:31,031]  INFO - UserStoreMgtDSComponent Claim manager
>> set for class org.wso2.carbon.user.core.common.DefaultRealm
>> [2017-12-05 19:38:31,032]  INFO - UserStoreMgtDSComponent Claim manager
>> set for class org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager
>> [2017-12-05 19:38:31,110]  INFO - OAuth2ServiceComponent PKCE Support
>> enabled.
>> [2017-12-05 19:38:31,386]  INFO - ServiceBusInitializer Starting ESB...
>> [2017-12-05 19:38:31,393]  INFO - ServiceBusInitializer Initializing
>> Apache Synapse...
>> [2017-12-05 19:38:32,302]  INFO - SynapseControllerFactory Using Synapse
>> home : /home/senuwan/BackupAssg/WorkerGW/.
>> [2017-12

Re: [Dev] [APIM] APIManagerComponent Exception occurred while creating JMS Event Adapter

2017-12-05 Thread Harsha Kumara
You can telnet to 172.16.2.39 9713. and see it's open or not. Looks like
it's not open.

On Tue, Dec 5, 2017 at 8:15 PM, Senuwan Withana  wrote:

> Yes
>
> *Senuwan Withana*
> Software Engineer - Support Team | WSO2
>
> Email : senu...@wso2.com
> Mobile: 94773212853
> Web: http://www.wso2.com
>
>
>
> On Tue, Dec 5, 2017 at 7:55 PM, Harsha Kumara  wrote:
>
>> Is your TM running with port offset 2?
>>
>> On Tue, Dec 5, 2017 at 7:43 PM, Senuwan Withana  wrote:
>>
>>> Hi Guys
>>>
>>> Again Thanks for quick responses. I have looked all the comments and
>>> done the relevant changes
>>> Eg: Comment out the JMSEventPublisherParameters section, Up the TM
>>> first. so on.  However still i got below errors.
>>>
>>>
>>> [2017-12-05 19:38:30,393]  INFO - JMSTransportHandler Starting jms topic
>>> consumer thread...
>>> [2017-12-05 19:38:30,443]  INFO - APIManagerComponent JMS Publisher not
>>> enabled.
>>> [2017-12-05 19:38:30,632]  INFO - AMQConnection Unable to connect to
>>> broker at tcp://172.16.2.39:5674
>>> org.wso2.andes.transport.TransportException: Could not open connection
>>> at org.wso2.andes.transport.network.mina.MinaNetworkTransport$I
>>> oConnectorCreator.connect(MinaNetworkTransport.java:216)
>>> at org.wso2.andes.transport.network.mina.MinaNetworkTransport.c
>>> onnect(MinaNetworkTransport.java:74)
>>> at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerCo
>>> nnection(AMQConnectionDelegate_8_0.java:130)
>>> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:631)
>>> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:628)
>>> at java.security.AccessController.doPrivileged(Native Method)
>>> at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQ
>>> Connection.java:628)
>>> at org.wso2.andes.client.AMQConnection.(AMQConnection.java:409)
>>> at org.wso2.andes.client.AMQConnectionFactory.createConnection(
>>> AMQConnectionFactory.java:351)
>>> at org.wso2.andes.client.AMQConnectionFactory.createConnection(
>>> AMQConnectionFactory.java:40)
>>> at org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils.createCon
>>> nection(JMSUtils.java:387)
>>> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.checkJ
>>> MSConnection(JMSListener.java:137)
>>> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.start(
>>> JMSListener.java:79)
>>> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.run(JM
>>> SListener.java:186)
>>> at java.lang.Thread.run(Thread.java:748)
>>> org.wso2.andes.AMQConnectionFailureException: Could not open connection
>>> at org.wso2.andes.client.AMQConnection.(AMQConnection.java:486)
>>> at org.wso2.andes.client.AMQConnectionFactory.createConnection(
>>> AMQConnectionFactory.java:351)
>>> at org.wso2.andes.client.AMQConnectionFactory.createConnection(
>>> AMQConnectionFactory.java:40)
>>> at org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils.createCon
>>> nection(JMSUtils.java:387)
>>> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.checkJ
>>> MSConnection(JMSListener.java:137)
>>> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.start(
>>> JMSListener.java:79)
>>> at org.wso2.carbon.apimgt.jms.listener.utils.JMSListener.run(JM
>>> SListener.java:186)
>>> at java.lang.Thread.run(Thread.java:748)
>>> Caused by: org.wso2.andes.transport.TransportException: Could not open
>>> connection
>>> at org.wso2.andes.transport.network.mina.MinaNetworkTransport$I
>>> oConnectorCreator.connect(MinaNetworkTransport.java:216)
>>> at org.wso2.andes.transport.network.mina.MinaNetworkTransport.c
>>> onnect(MinaNetworkTransport.java:74)
>>> at org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerCo
>>> nnection(AMQConnectionDelegate_8_0.java:130)
>>> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:631)
>>> at org.wso2.andes.client.AMQConnection$2.run(AMQConnection.java:628)
>>> at java.security.AccessController.doPrivileged(Native Method)
>>> at org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQ
>>> Connection.java:628)
>>> at org.wso2.andes.client.AMQConnection.(AMQConnection.java:409)
>>> ... 7 more
>>> [2017-12-05 19:38:30,641] ERROR - JMSListener Unable to continue server
>>> startup as it seems the JMS Provider is not yet started. Please start the
>>> JMS provider now.
>>> [2017-12-05 19:38:30,644] ERROR - JMSListener Connection attempt : 1 for
>>> JMS Provider failed. Next retry in 20 seconds
>>> [2017-12-05 19:38:30,733]  INFO - TenantLoadingConfig Using tenant lazy
>>> loading policy...
>>> [2017-12-05 19:38:30,743]  INFO - PermissionUpdater Permission cache
>>> updated for tenant -1234
>>> [2017-12-05 19:38:31,031]  INFO - UserStoreMgtDSComponent Claim manager
>>> set for class org.wso2.carbon.user.core.common.DefaultRealm
>>> [2017-12-05 19:38:31,032]  INFO - UserStoreMgtDSComponent Claim manager
>>> set for class org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager
>>> [2017-12-05 19:38:31,110]  INFO - OAuth2ServiceComponent PKCE Support
>>> enabled.
>>> [2017-12-05 19:38:31,386]  INFO - ServiceB