| Summary: | 'access_point_url' column in jUDDI schema too short | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Lukáš Petrovický <lpetrovi> |
| Component: | JBossESB | Assignee: | Dana Mison <dmison> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2 CP04 | Keywords: | Regression |
| Target Milestone: | --- | ||
| Target Release: | 4.2 CP04 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-1327 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-06-12 07:17:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Lukáš Petrovický
2009-05-25 13:19:40 UTC
Link: Added: This issue depends JBESB-2590 This will be worked around in the platform build for now. Link: Added: This issue is related to SOA-919 Worked around in revision 3087 (4.2.0 branch) of: build-tools/builders/eap/build.xml build-tools/builders/esb/build.xml Commit message: JIRA SOA-1327 Change ACCESS_POINT_URL from 2000 to 4000 characters for: db2, hsqldb, mysql, oracle, postgresql This change will require an upgrade script and an entry in the release notes. Affects: Added: [Release Notes] Upgrade scripts added and installed: Revision 3091 (4.2.0 branch) of: build-tools/resource/upgrade-juddi-sybase.txt build-tools/resource/upgrade-juddi-postgresql.txt build-tools/resource/upgrade-juddi-oracle.txt build-tools/resource/upgrade-juddi-mysql.txt build-tools/resource/upgrade-juddi-db2.txt build-tools/resource/upgrade-juddi-hsqldb.txt Commit message: JIRA SOA-1327 Upgrade scripts for jUDDI DB's. Revision 3092 (4.2.0 branch) of: build-tools/builders/eap/build.xml build-tools/builders/esb/build.xml Commit message: JIRA SOA-1327 Install jUDDI DB upgrade scripts. Proposed release notes text, for the "Upgrading from 4.2.CP03 to 4.2.CP04" section: jUDDI database changes It is possible in some circumstances to exceed the length for the `ACCESS_POINT_URL' column in the `BINDING_TEMPLATE' table of the jUDDI database. New installations will increase the length of this column from 2000 to 4000 characters. For existing installations, upgrade scripts, named "upgrade-juddi-<database>.txt", are provided in the "jboss-as" directory of the binary distributions. Note, that each database requires a slightly different SQL syntax for this operation, so you must use the script appropriate for your database, for example, "upgrade-juddi-postgresql.txt". See JIRA issues <a href="https://jira.jboss.org/jira/browse/SOA-1327">SOA-1327</a> and <a href="https://jira.jboss.org/jira/browse/JBESB-2590">JBESB-2590</a> for more information. need to include this in the getting started guide as well content added to Getting Started Guide in upgrading section: jUDDI database changes from 4.2.CP03 to 4.2.CP04 In 4.2.CP04 the ACCESS_POINT_URL column of the BINDING_TEMPLATE table in the jUDDI database has been extended from 2000 characters to 4000. If you are upgrading an existing SOA Platform installation then you need to apply this change. There are upgrade scripts for each supported database in the jboss-as directory with the name of upgrade-juddi-DATABASE.txt Each database requires a slightly different SQL syntax for this operation, so you must use the script appropriate for your database, e.g. upgrade-juddi-postgresql.txt for PostgreSQL. Additional information: https://jira.jboss.org/jira/browse/SOA-1327. Link: Added: This issue is related to SOA-1351 Added as Jboss ESB resolved JIRA https://jira.jboss.org/jira/browse/SOA-1327 The ACCESS_POINT_URL column of the BINDING_TEMPLATE table in the jUDDI database has been extended from 2000 characters to 4000 to allow for very long URLs. This step must be performed manually when upgrading to CP04 or later. Additional details on performing this update can be found in the Getting Started Guide. Verified in CR4 |