wso2carbon

ERROR - ListenerManager Couldn't initialize the httpstransport listener - WSO2

£可爱£侵袭症+ 提交于 2019-12-02 01:20:08
问题 I started fresh copy of the WSO2 API Manager 1.8 and get below error for no reason. ERROR - ListenerManager Couldn't initialize the httpstransport listener How can I fix this? 回答1: Check the system hostname by running following command $ hostname try to ping to the output for that hostname. $ ping <output of the hostname command> If that gives an error check the /etc/hosts file. At least it should have a host entry to 127.0.0.1 127.0.0.1 <hostname> or <local ip> <hostname> 回答2: Type root@S-06

How to create a custom asset-attributes.hbs for each new artifact for the STORE?

眉间皱痕 提交于 2019-12-02 00:53:28
Im using WSO2 Governance Registry 5.2.0. When I create a new artifact type, it containt a lot of new fields (You create and define this XML in the CARBON ADMIN CONSOLE). So in the PUBLISHER you can see the new fields, create and consult a new item of the artifact. But the problem is in the STORE, I cannot see the this new fields. So in order to do this, I made the custom fields available by modifying GREG_HOME>/repository/deployment/server/jaggeryapps/store/extensions/app/greg-store-defaults/themes/store/partials/asset-attributes.hbs file. Thanks to Malintha's Blog , This is perhaps an answer,

ERROR - ListenerManager Couldn't initialize the httpstransport listener - WSO2

☆樱花仙子☆ 提交于 2019-12-01 21:56:10
I started fresh copy of the WSO2 API Manager 1.8 and get below error for no reason. ERROR - ListenerManager Couldn't initialize the httpstransport listener How can I fix this? Check the system hostname by running following command $ hostname try to ping to the output for that hostname. $ ping <output of the hostname command> If that gives an error check the /etc/hosts file. At least it should have a host entry to 127.0.0.1 127.0.0.1 <hostname> or <local ip> <hostname> Type root@S-06:hostname S-06 Type get your IP root@S-06:ifconfig Add it to vim /etc/hosts as a record. 192.168.4.123 S-06 来源:

RabbitMQ AMQP Transport Support in WSO2 ESB 4.8

半腔热情 提交于 2019-12-01 14:02:11
http://docs.wso2.org/display/ESB480/RabbitMQ+AMQP+Transport i have gone through this example to get RabbitMQ AMQP transport support in WSO2 ESB 4.8 but i am getting following error during the Creation of the RabbitMQ Proxy Service. Unable to generate proxy data from source: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[16,93]Message: The reference to entity 'rabbitmq.server.port' must end with the ';' delimiter. any solution ?? thanks Admin console "complains" about unescaped & (ampersand) character. If you change the line with endpoint address by replacing & with & you should

WSO2 API Manager - Expose Publisher & Store URLs to public

|▌冷眼眸甩不掉的悲伤 提交于 2019-12-01 12:19:07
问题 I'm using WSO2 API Manager for creating and managing a developer community. According to my knowledge API manager is driven on WSO2 Carbon Server which again runs on Apache Tomcat. Up to now I'm able to run WSO2 API manager without any issues. I could open up store and publisher using below urls. https://<MyHostName>:9443/publisher https://<MyHostName>:9443/store What I want to know is, how can I expose these two URLs to public? I would like something like below as URLs(without ports). https:

Working example on Spring Mediator in WSO2 ESB 4.6.0

一笑奈何 提交于 2019-12-01 11:58:38
Hi i am working on Spring Mediator in WSO2 ESB 4.6.0, using this and this tutorial I am getting the Error as follows: ERROR - SpringMediator Cannot look up Spring configuration conf/sample/resources/spring/springsample.xml ERROR - SpringMediatorCannot reference application context with key : conf/sample/resources/spring/springsample.xml Could you please explain me how to solve this. I got to work this as below, The class should extends AbstractMediator and override the mediate() method as follows, package com.test.spring.mediator.workingexampleonspringmediator; import org.apache.synapse

WSO2 API Manager - Expose Publisher & Store URLs to public

≯℡__Kan透↙ 提交于 2019-12-01 11:51:25
I'm using WSO2 API Manager for creating and managing a developer community. According to my knowledge API manager is driven on WSO2 Carbon Server which again runs on Apache Tomcat. Up to now I'm able to run WSO2 API manager without any issues. I could open up store and publisher using below urls. https://<MyHostName>:9443/publisher https://<MyHostName>:9443/store What I want to know is, how can I expose these two URLs to public? I would like something like below as URLs(without ports). https://<MyHostName>/publisher https://<MyHostName>/store or https://publisher.<MyHostName> https://store.

Working example on Spring Mediator in WSO2 ESB 4.6.0

大兔子大兔子 提交于 2019-12-01 10:07:59
问题 Hi i am working on Spring Mediator in WSO2 ESB 4.6.0, using this and this tutorial I am getting the Error as follows: ERROR - SpringMediator Cannot look up Spring configuration conf/sample/resources/spring/springsample.xml ERROR - SpringMediatorCannot reference application context with key : conf/sample/resources/spring/springsample.xml Could you please explain me how to solve this. 回答1: I got to work this as below, The class should extends AbstractMediator and override the mediate() method

Error while trying to connect to the endpoint. Cannot borrow client for ssl

百般思念 提交于 2019-12-01 04:48:21
This error is being printed in the WSO2 API Manager wso2carbon.log.. sun.security.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:88) at org.wso2.carbon.databridge.agent.endpoint.binary.BinarySecureClientPoolFactory.createClient(BinarySecureClientPoolFactory.java:53) ... 9 more TID: [-1] [] [2016-12-28 22:16:04,043] ERROR {org.wso2.carbon.databridge.agent.endpoint.DataEndpointConnectionWorker} - Error while trying to connect to the endpoint. Cannot borrow client for ssl://192.168.1.36:9711 {org.wso2.carbon.databridge.agent.endpoint.DataEndpointConnectionWorker} org.wso2.carbon

getPayloadJSON returning an empty object

折月煮酒 提交于 2019-11-30 23:44:50
I am doing some very simple script mediation as a test to see if I can change the payload being returned by my server. My unmediated payload comes out as: {"origin":"202.37.75.130"} Then I try doing a very simple check to see whether get and set work for payloads: <script language="js"> var older = mc.getPayloadJSON(); var newer=older; mc.setPayloadJSON(newer); </script> My result from this is: {"jsonObject":""} I have done testing that shows that setPayloadJSON() works, which means that my getPayloadJSON must be returning an empty object. Looking at the log file shows this: ERROR {org.apache