Bug 779520 (SOA-1902) - juddiDB resource is shown as DOWN in JON
Summary: juddiDB resource is shown as DOWN in JON
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1902
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JON
Version: 5.0.0 ER7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-28 16:00 UTC by Jaroslaw Kijanowski
Modified: 2010-09-22 15:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
JON 2.3.1 8436 Sun 1.6 RHEL5
Last Closed: 2010-09-22 15:51:54 UTC
Type: Bug


Attachments (Terms of Use)
juddi-ds.xml (913 bytes, text/xml)
2010-01-29 16:52 UTC, Jaroslaw Kijanowski
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1902 0 None None None Never

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



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