Bug 778816 (SOA-1266) - Scout creates a new AuthToken for every invocation through BusinessQuery/BusinessLifecycle Managers
Summary: Scout creates a new AuthToken for every invocation through BusinessQuery/Busi...
Keywords:
Status: NEW
Alias: SOA-1266
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.3 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: FUTURE
Assignee: Nobody
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-01 05:59 UTC by Taro Yasuma
Modified: 2021-10-15 11:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug

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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1266 0 Major Closed Scout creates a new AuthToken for every invocation through BusinessQuery/BusinessLifecycle Managers 2013-01-22 06:47:01 UTC

Description Taro Yasuma 2009-04-01 05:59:02 UTC 
Date of First Response: 2009-04-23 05:09:06
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/265664
project_key: SOA

See JBESB-3447.
Comment 1 Taro Yasuma 2009-04-01 05:59:59 UTC 
Link: Added: This issue depends JBESB-2442
Comment 2 Taro Yasuma 2009-04-01 08:03:50 UTC 
The other support case opened: https://enterprise.redhat.com/issue-tracker/281654
Comment 4 Kevin Conner 2009-10-23 17:12:54 UTC 
This has been deferred from the current ESB trunk until we integrate juddi v3, as the scout release is already complete.  This will be included in a subsequent scout release and may make it into SOA 5.0, depending on progress during productisation.
Comment 5 David Le Sage 2010-02-10 04:37:03 UTC 
This has been documented for the Release Notes.  Here is the current draft text:


https://jira.jboss.org/jira/browse/SOA-1266

    Currently, Scout creates a new AuthToken for every invocation that occurs through the
    BusinessQuery/BusinessLifecycle Managers. This results in rapid growth of the jUDDI
    authentication table.

    A possibly way to work around this problem is to delete rows within certain timestamp parameters.
    For instance, all rows created more than ten minutes ago could be removed.
Comment 6 Kevin Conner 2010-08-09 13:55:31 UTC 
Link: Removed: This issue depends JBESB-2442
Comment 7 Kevin Conner 2010-08-09 13:55:42 UTC 
Link: Added: This issue depends JBESB-3447
Comment 8 Rick Wagner 2011-12-05 20:51:48 UTC 
Rick reviewing old JIRAs.  JBESB-3447 still open, looks valid.  Left Open.
Note You need to log in before you can comment on or make changes to this bug.