Symptoms:
### ERROR ### — [ool-2-thread-13] c.v.b.p.s.PipelineRequestPostProcessor [lambda$processPipelineRequests$2] : statusMessage : [{"messageId":"LCMBLACKSTONE213012","message":"LCMBLACKSTONE213012","eventId":"###","retry":false,"exceptionMessage":"Received exception while triggering pipeline action on blackstone.","exceptionStackTrace":"com.vmware.vrealize.lcm.common.exception.LcmException: Request execution failed at blackstone, with error : {\"summaryMessage\":\"Failed to deploy contents\",\"failures\":[{\"errorMessage\":\"Failed to deploy the content : ### to the endpoint: ###, Error: Exception occurred, exception message : 400 Status : 400 BAD_REQUEST, Error :
{\\\"message\\\":\\\"Invalid deployment filter id specified: ERROR: too many connections for database \\\\\\\"catalog-db\\\\\\\"\\\\n Where: parallel worker.\\\",\\\"statusCode\\\":400,\\\"errorCode\\\":20003}
### ERROR X — [pool-2-thread-8] c.v.b.p.s.PipelineRequestPostProcessor [lambda$processPipelineRequests$2] : statusMessage : [{"messageId":"LCMBLACKSTONE213012","message":"LCMBLACKSTONE213012","eventId":"###","retry":false,"exceptionMessage":"Received exception while triggering pipeline action on blackstone.","exceptionStackTrace":"com.vmware.vrealize.lcm.common.exception.LcmException: Request execution timed out while waiting for completion.\n\tat com.vmware.vrealize.lcm.blackstone.core.task.BlackStoneBaseTask.pollPipelineRequest(BlackStoneBaseTask.java:140)\n\tat com.vmware.vrealize.lcm.blackstone.core.task.BlackStoneReleaseTask.execute(BlackStoneReleaseTask.java:96)\n\tat com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:62)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)\n\tat java.base/java.lang.Thread.run(Unknown Source)\n","localizedMessageId":"BlACKSTONE_BASE_TASK_ERROR_00001","parameters":null,"properties":{}}]
Aria Suite Lifecycle 8.18.1
The default blackstone-external-8.18.0.jar file reaches the page size limit set for deployments.
If you encounter this issue raise a ticket with Broadcom support and reference this article id 393303