Bug 779520 (SOA-1902)

Summary: juddiDB resource is shown as DOWN in JON
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Jaroslaw Kijanowski <kijanowski>
Component: JONAssignee: Default User <jbpapp-maint>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 ER7CC: ian.springer
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1902
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
JON 2.3.1 8436 Sun 1.6 RHEL5
Last Closed: 2010-09-22 15:51:54 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:
Attachments:
Description Flags
juddi-ds.xml none

Description Jaroslaw Kijanowski 2010-01-28 16:00:31 UTC 
Date of First Response: 2010-01-29 12:38:30
project_key: SOA

The juddiDB resource is shown as DOWN in JON (Resources -> Datasources -> Local Tx Datasources). This might be related to JOPR-426, however in JON-2.3.1 (8436) I haven't seen that issue anymore (it was always reproducible in JON-2.3.0).

To fix this I had to replace juddiDB with juddiDS in:
deploy/jbossesb-registry.sar/META-INF/jboss-service.xml
deploy/jbossesb-registry.sar/juddi_config/META-INF/persistence.xml
deploy/jbossesb-registry.sar/juddi-ds.xml
Comment 1 Jaroslaw Kijanowski 2010-01-29 16:52:29 UTC 
Attachment: Added: juddi-ds.xml
Comment 2 Charles Crouch 2010-01-29 17:38:30 UTC 
With Jarek to try see if taking a working datasource e.g. defaultDS, and changing it to have a jndi-name of defaultDB causes a problem in his environment.
Comment 3 Jaroslaw Kijanowski 2010-01-29 18:02:08 UTC 
ech... I guess it was too beautiful to be true...

So I've deployed a 2nd datasource called DefaultDB and it was discovered properly... and also the juddiDB looks good now...
This time JbpmDS is flagged as red... So looks like I was hit again by JOPR-426 which is not fixed.
Comment 4 Ian Springer 2010-02-03 15:42:51 UTC 
Link: Added: This issue depends JOPR-426