Bug 780064 (SOA-2429) - jUDDI console unable to find services
Summary: jUDDI console unable to find services
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2429
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: jUDDI - within SOA
Version: 5.1.0.ER3
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.1.0 GA,5.1.0.ER5
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-17 14:48 UTC by Julian Coleman
Modified: 2011-02-07 14:56 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
SOA 5.1.0 ER3
Last Closed: 2011-02-07 14:56:14 UTC
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-2429 0 None None None Never

Description Julian Coleman 2010-10-17 14:48:28 UTC 
Workaround Description: Remove the jbossesb_BusinessEntity.xml file *before* starting the server for the first time.  If the server has already been started then the registry must be cleaned out.
project_key: SOA

When the jUDDI console is started, a popup dialog box containing "error: null"
is displayed, along with a server stacktrace, starting:

  16:44:13,041 ERROR [FindServiceImpl] Could not obtain token. null
  java.lang.NullPointerException
        at org.apache.juddi.portlets.server.service.FindServiceImpl.getBusinesses(FindServiceImpl.java:88)

jUDDI version is 3.0.4-SNAPSHOT
uddi-console version is 3.0.1
Comment 1 Kevin Conner 2010-10-18 08:52:18 UTC 
This is definitely a bug in the juddi console, triggered by a configuration file pulled in from Riftsaw.
Comment 2 Kevin Conner 2010-10-18 09:03:38 UTC 
Riftsaw has added a configuration file into the ESB registry configuration, jbossesb_BusinessEntity.xml, which claims to be ESB related.

The quick fix is to remove this file *before* the server starts for the first time.
Comment 3 Kevin Conner 2010-10-18 09:04:46 UTC 
Workaround Description: Added: Remove the jbossesb_BusinessEntity.xml file *before* starting the server for the first time.  If the server has already been started then the registry must be cleaned out.
Comment 4 Kurt Stam 2010-10-19 02:50:30 UTC 
If a business does not have any services, then the returning structure is null. The console should not be throwing an NPE for this. 

https://issues.apache.org/jira/browse/JUDDI-420
Comment 5 Kevin Conner 2010-10-19 08:25:24 UTC 
Yes, that is the console bug.  I am going to ask for the jbossesb_BusinessEntity.xml to be removed from the ESB configuration since that is not related to anything we do.
Comment 6 Julian Coleman 2010-10-20 10:02:16 UTC 
jbossesb_BusinessEntity.xml removed in revision 7023 of:
  build-tools/builders/riftsaw/build.xml

Commit message:
  SOA-2429
  Remove jbossesb_BusinessEntity.xml from our RiftSaw installation.
Comment 7 Julian Coleman 2010-11-08 14:05:29 UTC 
The uddi-console included in ER4 contains uddi-portlets 3.0.4,
which has a fix for JUDDI-420.
Comment 8 Len DiMaggio 2010-11-22 13:21:32 UTC 
Verified fixed in ER4 build - the jbossesb_BusinessEntity.xml file has been removed.
Comment 9 Julian Coleman 2010-12-03 11:54:36 UTC 
RiftSaw requires the BusinessEntity file to be present..
Comment 10 Julian Coleman 2010-12-03 12:01:47 UTC 
Resolved with revision 7502 of:

  build-tools/builders/riftsaw/build.xml

Commit message:

  SOA-2429
  Rename "jbossesb_BusinessEntity.xml" to "riftsaw_BusinessEntity.xml" in order
  to properly reflect its source.
Comment 11 Julian Coleman 2010-12-03 12:01:48 UTC 
Labels: Removed: rn-dmison rn-not-needed Added: rn-not-needed
Comment 12 Laura Bailey 2010-12-17 01:00:58 UTC 
Release Notes Docs Status: Added: Not Required
Comment 14 Dana Mison 2011-01-05 00:14:35 UTC 
Writer: Added: dlesage
Comment 15 Len DiMaggio 2011-02-07 14:56:14 UTC 
Verified fixed in ER9 build.
Note You need to log in before you can comment on or make changes to this bug.