VMware Cloud Community
kurtduncan
Contributor
Contributor
Jump to solution

vco 7.4 maven repository unavailable

After deploying vra7.4, with vco up and running, maven cannot access the archetype xml file.

I get the following diagnostic:

Caused by: org.apache.maven.wagon.providers.http.httpclient.conn.HttpHostConnectException: Connect to kdvra:8281 [kdvra/10.128.225.40] failed: Connection refused (Connection refused)

How can I go about determining the root cause of this?

0 Kudos
1 Solution

Accepted Solutions
iiliev
VMware Employee
VMware Employee
Jump to solution

Hi,

The first problem is the port number.

  • vRO server is accessible on port 8281 in case of vRO standalone appliance
  • vRO server is accessible on port 443 in case of vRO embedded in vRA appliance

The second problem - in case of vRO embedded in vRA appliance, I think there is no hosted Maven repository available. I'm not 100% sure (have to double check this), but in this case you'll have to deploy a standalone vRO appliance.

Another possible problem you can hit is that the newer Maven versions could have issues with the latest Maven archetype plug-in. You can resolve it by forcing Maven to use the slightly older version 2.4 of this plug-in; if you are unsure how to do so you may check eg. https://communities.vmware.com/message/2707795#2707795 or https://www.virtualvcp.com/vmware-vrealize-automation-vcac/229-vro-plugin-development-getting-maven-...

View solution in original post

0 Kudos
1 Reply
iiliev
VMware Employee
VMware Employee
Jump to solution

Hi,

The first problem is the port number.

  • vRO server is accessible on port 8281 in case of vRO standalone appliance
  • vRO server is accessible on port 443 in case of vRO embedded in vRA appliance

The second problem - in case of vRO embedded in vRA appliance, I think there is no hosted Maven repository available. I'm not 100% sure (have to double check this), but in this case you'll have to deploy a standalone vRO appliance.

Another possible problem you can hit is that the newer Maven versions could have issues with the latest Maven archetype plug-in. You can resolve it by forcing Maven to use the slightly older version 2.4 of this plug-in; if you are unsure how to do so you may check eg. https://communities.vmware.com/message/2707795#2707795 or https://www.virtualvcp.com/vmware-vrealize-automation-vcac/229-vro-plugin-development-getting-maven-...

0 Kudos