Bug 780227 (SOA-2614) - Juddi oracle db in clause limit
Summary: Juddi oracle db in clause limit
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-2614
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: jUDDI - within SOA
Version: 5.1.0.ER4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: FUTURE
Assignee: Kurt Stam
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-26 16:21 UTC by Jiri Sedlacek
Modified: 2015-08-02 23:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
oracle 10g db
Last Closed: 2011-12-06 22:01:32 UTC
Type: Bug


Attachments (Terms of Use)
juddi_oracle.tgz (3.76 KB, application/x-compressed-tar)
2010-11-26 16:23 UTC, Jiri Sedlacek
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2614 0 Major Closed Juddi oracle db in clause limit 2014-05-20 18:13:35 UTC

Description Jiri Sedlacek 2010-11-26 16:21:05 UTC
Affects: Release Notes
project_key: SOA

juddi in soa-platfrom configured with oracle db has got problem if more than 1000 services are inserted and searched.

Quickstart to reproduce the issue is attached.

Comment 1 Jiri Sedlacek 2010-11-26 16:23:04 UTC
untar in quickstarts dir, configure server to use oracle db for juddi and run ant

Comment 2 Jiri Sedlacek 2010-11-26 16:23:04 UTC
Attachment: Added: juddi_oracle.tgz


Comment 3 Anne-Louise Tangring 2010-12-01 17:55:00 UTC
Affects: Added: [Release Notes]


Comment 4 Kurt Stam 2011-06-10 17:46:19 UTC
http://issues.apache.org/jira/browse/JUDDI-89.

Comment 5 Anne-Louise Tangring 2011-10-05 10:36:29 UTC
This issue is not fixed in our current version of jUDDI and we do not expect to get another update prior to releasing SOA 5.2. Moving to Future.

Comment 6 Kurt Stam 2011-12-07 17:23:43 UTC
This is an issue with other databases as well and it *will* be addressed by in the project. So I'd rather not close, but move it out to some future release.


Note You need to log in before you can comment on or make changes to this bug.