Bug 778437 (SOA-919) - The ESB EPRs can cause failure of registration of ESB service
Summary: The ESB EPRs can cause failure of registration of ESB service
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-919
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Build Process, Configuration
Version: 4.3 IR5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 CP02
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-06 11:03 UTC by Jiri Pechanec
Modified: 2009-08-18 11:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-18 11:40:14 UTC
Type: Feature Request

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778436 0 high CLOSED Rel Notes - Document the potential issue with ACCESS_POINT_URL field 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 778885 0 high CLOSED 'access_point_url' column in jUDDI schema too short 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-919 0 None None None Never

Internal Links: 778436 778885

Description Jiri Pechanec 2008-10-06 11:03:43 UTC 
Affects: Release Notes
Date of First Response: 2009-05-28 09:47:09
project_key: SOA

When EPR for service is registered it is by default quite long. It can happen that it will not fit to 2000 chars limit that is in jUDDI create table SQL scripts (ACCESS_POINT_URL in BINDING_TEMPLATE table). The default value should be changed to 4000.
Comment 1 Jiri Pechanec 2008-10-06 11:04:14 UTC 
Link: Added: This issue related SOA-918
Comment 2 Kevin Conner 2009-05-21 10:42:17 UTC 
Link: Added: This issue depends JBESB-2579
Comment 3 Julian Coleman 2009-05-27 20:29:49 UTC 
Link: Added: This issue related SOA-1327
Comment 4 Julian Coleman 2009-05-28 13:47:09 UTC 
We will work round this in the platform, in the same way that SOA-1327 does for 4.2 CP04.
Comment 5 Julian Coleman 2009-05-28 13:48:20 UTC 
Affects: Added: [Release Notes]
Comment 6 Julian Coleman 2009-06-23 15:19:24 UTC 
Fixed with revision 3194 (4.3 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-919
  
  Upgrade scripts for jUDDI DB's.

and revision 3196 (4.3 branch) of:
  builders/eap/build.xml

Commit message: 
  JIRA SOA-919
  
  Merge changes from revisions 3087 and 3092 from the 4.2.0 branch:
  
  > Change ACCESS_POINT_URL from 2000 to 4000 characters for:  
  >  db2, hsqldb, mysql, oracle, postgresql   
  
  > Install jUDDI DB upgrade scripts.
Comment 7 Dana Mison 2009-07-06 07:29:02 UTC 
Same text as SOA-1327 is being added to release notes in "upgrade from earlier versions" section
Comment 8 Dana Mison 2009-08-04 04:39:06 UTC 
also added to the 4.3.CP02 release notes as resolved:

JBESB-919 - 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 CP02 or later. Refer to Section Upgrading from an earlier version for additional details.
Comment 9 Jiri Pechanec 2009-08-18 11:40:14 UTC 
Verified in CR2
Note You need to log in before you can comment on or make changes to this bug.