NO-JIRA add DB upgrade instructions for 2.21.0

This commit is contained in:
Justin Bertram 2022-05-31 23:11:11 -05:00
parent 2e1bf7fbf7
commit 73758c91f4
No known key found for this signature in database
GPG Key ID: F41830B875BB8633
1 changed files with 23 additions and 13 deletions

View File

@ -35,21 +35,31 @@ Highlights:
#### Upgrading from older versions
Due to XML schema changes to correct an inaccurate domain name 2 files will need to
be updated:
1. Due to XML schema changes to correct an inaccurate domain name 2 files will need to
be updated:
1. `etc/bootstrap.xml`
2. `etc/management.xml`
1. `etc/bootstrap.xml`
2. `etc/management.xml`
In both files change the XML namespace from `activemq.org` to `activemq.apache.org`,
e.g. in `bootsrap.xml` use:
```xml
<broker xmlns="http://activemq.apache.org/schema">
```
And in `management.xml` use:
```xml
<management-context xmlns="http://activemq.apache.org/schema">
```
In both files change the XML namespace from `activemq.org` to `activemq.apache.org`,
e.g. in `bootsrap.xml` use:
```xml
<broker xmlns="http://activemq.apache.org/schema">
```
And in `management.xml` use:
```xml
<management-context xmlns="http://activemq.apache.org/schema">
```
2. **If you're using [JDBC persistence](persistence.md#jdbc-persistence)** then due
to the changes in [ARTEMIS-3679](https://issues.apache.org/jira/browse/ARTEMIS-3679)
you'll need to update your database. The column `HOLDER_EXPIRATION_TIME` on the
`NODE_MANAGER_STORE`changed from a `TIMESTAMP` to a `BIGINT` (or `NUMBER(19)` on
Oracle). You will have to stop any broker that is accessing that table and either
drop it or execute the proper `ALTER TABLE` statement for your database. If you
drop the table then it will be automatically recreated when broker restarts and
repopulated with a new, auto-generated node ID.
## 2.20.0
[Full release notes](https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350581&projectId=12315920).