429 Too Many Requests to liquibase.org

We’re working on a version that breaks our customers out from a shared schema solution to a schema per customer approach. When our app servers start up they try to run liquibase against each customer schema. Each server runs a max of 5 customers concurrently. We typically only have 2 servers that have the ability to run these. So at startup we could potentially be running as many as 10 liquibase processes against different schemas from within our network. Wer’e running into an issue where some of the threads will receive throttling errors:

Caused by: java.io.IOException: Server returned HTTP response code: 429 for URL: http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.4.xsd
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1924)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1520)
	at java.xml/com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:676)
	at java.xml/com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:150)
	at java.xml/com.sun.org.apache.xerces.internal.impl.xs.opti.SchemaParsingConfig.parse(SchemaParsingConfig.java:593)
	at java.xml/com.sun.org.apache.xerces.internal.impl.xs.opti.SchemaParsingConfig.parse(SchemaParsingConfig.java:696)
	at java.xml/com.sun.org.apache.xerces.internal.impl.xs.opti.SchemaDOMParser.parse(SchemaDOMParser.java:530)
	at java.xml/com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getSchemaDocument(XSDHandler.java:2226)

What is the throttling rate we’re up against? Also is there a way for us to avoid having to make these requests to liquibase.org? Is it as simple as copying the schema definition to our own location?

Thank you

Hi @mnesic ,

I believe our developers would be the best person to address this question. Do you mind taking at look at it @NathanVoxland @MikeOlivas ?

What version of Liquibase are you running? We shouldn’t be making any requests, but there have been a couple versions where that has not been the case.

Does the current 4.4.1 version fix the problem for you?


We got around the issue twice, kind of. We originally got around the issue by copying the schema XSDs to our own location and changing our change sets to reference that instead of the liquibase.org schemas. Then we found that upgrading got rid of that problem so we reverted that first change and now all is good. Thank you for the responses. We’ve been using this for probably over 10 years now and we love it!