[+ WSO2 Dev] Hi Marco,
I have copied this mail to WSO2 Dev, please find my comments inline: On Tue, Oct 6, 2015 at 11:28 PM, Monaco Marco <[email protected]> wrote: > > > firstly I would like to notify you that I found some issues on DAS > Cartridge template modules. > > In the file > ./template/repository/conf/data-bridge/data-bridge-config.xml.template you > have an invalid property that raise exception and prevent the start of the > thrift agent, so cartridge will never boot up since py-cartridge-agent > hangs in waiting for the port 7611 to be active. > > That line is <eventBufferSize>2000</eventBufferSize> but it should be > <eventBufferCapacity>2000</eventBufferCapacity> in order to boot up the > agent correctly. > > It looks like you are using the template module under virtual hackathon branch. The official one is in 4.2.0 branch and we will be moving it to the new cartridges repository [1] in another few days. @Chanika: Can you please comment on this problem? > Secondly I would like to notify a problem for nginx extension template. If > is used as included in the github it will not work for https (incoming > requests for https endpoint will be routed to https port but with http > protocol). Plus there were other incorrect lines of code that prevented the > extension to startup. This is our final version of template, you can share > with nginx extension dev. > Great! Thank you very much! May be you can send pull request here [2] (to notify that you contributed it). > Finally I would like to inform you that we produced template-module for > WSO2 ESB 4.9.1 (is based on Carbon core 4.4.1 so we used the same patches > used for DAS cartridge - patch9999 with private-paas membership scheme > patch). It seems like to work, ESB comes up and successfully finds the > worker nodes in the same cluster. If you need it I can send you the .zip > (so you can even validate it). > > Awesome! Please send a pull request to new cartridges repo [1]. This is much appreciated. > We decided to use ESB 4.9.1 because we need to provide support for MQTT > transport, but we need to do something more: we need to create REST API > that will accept Rest HTTP calls and forward the payload to an MQTT topic > of external WSO2 MB 3.0.0. > We followed this resources: > > - https://gist.github.com/pzfreo/9703155 > - > https://docs.wso2.com/display/ESB490/Sample+272%3AMQTT+axis2+transport > - > > https://docs.wso2.com/display/ESB490/Sample+906%3A+Inbound+Endpoint+MQTT+Protocol+Sample > > We can't be able to succeed on this task, we receive a lot of exceptions > and messages does not flow to MB topic. Can you please tell me the mail of > a WSO2ESB developer in order to ask him for support? > > If you can describe the issues you found we should be able to help on that. Any product related issues can be send to WSO2 Dev, it is visible to all the product teams. Thanks [1] https://github.com/wso2/private-paas-cartridges [2] https://github.com/apache/stratos On Tue, Oct 6, 2015 at 11:28 PM, Monaco Marco <[email protected]> wrote: > Hi Imesh, > > firstly I would like to notify you that I found some issues on DAS > Cartridge template modules. > > In the file > ./template/repository/conf/data-bridge/data-bridge-config.xml.template you > have an invalid property that raise exception and prevent the start of the > thrift agent, so cartridge will never boot up since py-cartridge-agent > hangs in waiting for the port 7611 to be active. > > That line is <eventBufferSize>2000</eventBufferSize> but it should be > <eventBufferCapacity>2000</eventBufferCapacity> in order to boot up the > agent correctly. > > Secondly I would like to notify a problem for nginx extension template. If > is used as included in the github it will not work for https (incoming > requests for https endpoint will be routed to https port but with http > protocol). Plus there were other incorrect lines of code that prevented the > extension to startup. This is our final version of template, you can share > with nginx extension dev. > > events { > worker_connections 1024; > } > > #foreach( $port in $portlist ) > http { > server_names_hash_bucket_size 128; > #set( $hostnameServerMap = $servermap.get($port.proxy) ) > #foreach( $hostname in $hostnameServerMap.keySet() ) > upstream $hostname { > ## Uncomment below when sticky secession is needed by particular server > #if( $$hostname == "wso2is.almatest.it" ) > ip_hash; > #end > #set ($servers = $hostnameServerMap.get($hostname) ) > #foreach ( $server in $servers) > server $server; > #end > } > > server { > #if ($port.protocol == "https") > listen $port.proxy ssl; > #else > listen $port.proxy; > #end > server_name $hostname; > location / { > proxy_set_header X-Forwarded-Host $host; > proxy_set_header X-Forwarded-Server $host; > proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; > proxy_set_header Host $http_host; > proxy_read_timeout 5m; > proxy_send_timeout 5m; > #if ($port.protocol == "https") > proxy_pass https://$hostname; > #else > proxy_pass http://$hostname; > #end > } > location /nginx_status { > stub_status on; > access_log off; > allow 127.0.0.1; > deny all; > } > #if ($port.protocol == "https") > ssl on; > ssl_certificate /etc/nginx/ssl/server.crt; > ssl_certificate_key /etc/nginx/ssl/server.key; > > #end > } > #end > } > #end > > > Finally I would like to inform you that we produced template-module for > WSO2 ESB 4.9.1 (is based on Carbon core 4.4.1 so we used the same patches > used for DAS cartridge - patch9999 with private-paas membership scheme > patch). It seems like to work, ESB comes up and successfully finds the > worker nodes in the same cluster. If you need it I can send you the .zip > (so you can even validate it). > > We decided to use ESB 4.9.1 because we need to provide support for MQTT > transport, but we need to do something more: we need to create REST API > that will accept Rest HTTP calls and forward the payload to an MQTT topic > of external WSO2 MB 3.0.0. > We followed this resources: > > - https://gist.github.com/pzfreo/9703155 > - > https://docs.wso2.com/display/ESB490/Sample+272%3AMQTT+axis2+transport > - > > https://docs.wso2.com/display/ESB490/Sample+906%3A+Inbound+Endpoint+MQTT+Protocol+Sample > > We can't be able to succeed on this task, we receive a lot of exceptions > and messages does not flow to MB topic. Can you please tell me the mail of > a WSO2ESB developer in order to ask him for support? > > thank you very much, > > Marco > > -- *Imesh Gunaratne* Senior Technical Lead WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: http://imesh.gunaratne.org Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
