Hi All - I recently upgraded to vRealize Automation 6.2 and am working with vRealize Orchestrator to create workflows. I've created HTTP-REST workflows to request/release an IP address from our IPAM system (VitalQIP) and it seems to be failing with the following description/exception:
Connection pool shutdown (Workflow:Request-IP-from-QIP / Scripting (item3)#14)
Looking in the Schema>Scripting line #14 is in red below:
//Do not edit
var inParamtersValues = [subnet, hostname, ddns, mac, type, w2kdom, comment];
var request = restOperation.createRequest(inParamtersValues, null);
//set the request content type
request.contentType = "";
System.log("Request: " + request);
System.log("Request URL: " + request.fullUrl);
//Customize the request here
//Do not edit
var response = request.execute();
//prepare output parameters
System.log("Response: " + response);
statusCode = response.statusCode;
statusCodeAttribute = statusCode;
System.log("Status code: " + statusCode);
contentLength = response.contentLength;
headers = response.getAllHeaders();
contentAsString = response.contentAsString;
System.log("Content as string: " + contentAsString);
// Grep for IPaddress
var patt = ("IP Address.*");
var ipaddress = contentAsString.match(patt).toString();
ipaddress = ipaddress.split(/[\s,]+/);
ipaddress = ipaddress;
System.log ("IP Address := " +ipaddress);
I am unsure of how to get around this issue and am looking for some assistance as I am fairly new to vRO. Thanks much!
Phew!! You are a life saver sir! Correcting the permissions on the original files resolved the issue and allows me to log back in. Let me go ahead and replace the files again with the 4.4 versions, correct permissions and test. Will report back soon
Edit: Thanks again igaydajiev. This has worked with the newer files and can login to vRO 6.0 but it has not resolved the "Connection pool shut down" error when running my workflow
Any luck with this issue? I'm experiencing the same symptoms, and replaced the jar files as you detailed to no avail.
Things were working with the embedded vCO server on the vCAC 6.0 GA appliance, and when migrating workflows to a 6.2 instance I am getting connection pool shut down as indicated.
I was able to sort this out as outlined above by downgrading the libraries. For those following the thread:
1) Snapshot your appliance, backup, etc.
2) Delete the current httpclient and httpcore jar files.
3) Replace with downgraded httpclient-4.3.4.jar and httpcore-4.3.2.jar, both of which can be found here:
4) Restart vCO using the configuration page, or service vco-server restart.
As detailed above the library files are located in the following directory
Nothing official. From what I know the problem should get fixed in some of the upcoming releases.
I would suggest opening SRs so a solution can be provided to you.
There is now an official fix for this issue : Technical preview version of REST plug-in
Please provide feedback.
I also experienced this issue in multiple environments against our F5's. I can confirm that this preview REST update plugin has resolved our issues.
Hi, Something not related specifically to this subject, but we're looking to do the same thing at our place. Integrating our vRA / vRO deployment with Vital QIP IPAM enterprise solution.
If possible, can you tell me or direct to documentation so we can get starting on our end?
Internally, we have little to no help.
Hi virtualhobo, unfortunately I do not have any documentation for this and eventually gave up on trying to integrate this with QIP. The documentation that I was working off of was provided by an internal VMware rep for legacy 6.x version s of QIP whereas I am running a newer 7.x platform. In order for us to continue with this we would have needed to engage Professional Services to help us and we were not ready to do that yet. I do apologize for not being able to assist any further.
Finally we did the same thing, and at the moment, since we're stuck with QIP, we're using the cli to get the IP, create the entry,
It required more work since the CLI requires files manipulation, but it works and our telecom team are happy.
Thanks and Good luck!