An unexpected error in the RSS API prevented your request to be processed

[pacasa2]

Hi! We're trying to deploy the lastest version of the BAE using Docker-Compose. We've created the file "docker-compose.yml" and configured it with our keys,URLs and oAuth keys. When we deploy the containers, all of them seem to be running correctly. We can access the web portal and login with Fiware Global Instance IDM as admin role, but when we try to create a Catalog or Revenue Sharing system we get the following error: proxy_1 | 2019-03-28 11:50:36.103 - WARN: TMF - 8a011722-f5c2-484c-b00b-5674fdb49f6d - ::ffff:147.156.222.120 - infosistemas - GET: /DSRevenueSharing/rss/models?action=count&providerId=infosistemas - Pre-Validation (DSRevenueSharing): An unexpected error in the RSS API prevented your request to be processed

We must be missing something about Logic Proxy configuration. We tried modifying external ports in etc/config.js without success as it seems this file is being ignored.

Is there any tests we can make in order to check if all services are running properly?

Regards, Pablo

[fdelavega]

What version of the software are you using? Did you try with version 7.6.0?

[pacasa2]

I'm using the docker-compose file in this same repository here

I assume this uses the last version of BAE

[fdelavega]

um, it looks like the docker-compose file was not updated. I have updated it now, so it should be working if you redeploy

[pacasa2]

I've redeployed and that error has gone. Now I'm able to create RevenueSharing, Catalogs, Categories and Product Specifications. But I am not able to create Product Offers following these steps I get the following error: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'EXCLUSIVITY' in 'field list' And it's failing regardless of the chosen License Type.

[fdelavega]

Thats is due to the fact that the develop image that was included in docker-compose file pointed to version 7.4 and changes has been made in the APIs database. If you don't have important information in the databases, you can just remove the volumes and it will be created with the proper tables.

In this is not feasible I can provide a migration script.