| Summary: | jUDDI console unable to find services | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Julian Coleman <jcoleman> |
| Component: | jUDDI - within SOA | Assignee: | Julian Coleman <jcoleman> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.1.0.ER3 | ||
| Target Milestone: | --- | ||
| Target Release: | 5.1.0 GA, 5.1.0.ER5 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-2429 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
SOA 5.1.0 ER3
|
|
| Last Closed: | 2011-02-07 14:56:14 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: | |
This is definitely a bug in the juddi console, triggered by a configuration file pulled in from Riftsaw. 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. 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. 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 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. 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. The uddi-console included in ER4 contains uddi-portlets 3.0.4, which has a fix for JUDDI-420. Verified fixed in ER4 build - the jbossesb_BusinessEntity.xml file has been removed. RiftSaw requires the BusinessEntity file to be present.. 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. Labels: Removed: rn-dmison rn-not-needed Added: rn-not-needed Release Notes Docs Status: Added: Not Required Writer: Added: dlesage Verified fixed in ER9 build. |
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