Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 8.12, 8.11.3, 8.7.5, 8.7.2.6_2
Affects Version/s: 8.7.3
Component/s: Server
Labels:
None

Steps to Reproduce:

Hide

1. Deploy JDBC driver
2. Create datasource using above driver
3. Deploy VDB using above datasource
4. Restart server until race condition occurs

Show
1. Deploy JDBC driver 2. Create datasource using above driver 3. Deploy VDB using above datasource 4. Restart server until race condition occurs
Bugzilla References:
https://bugzilla.redhat.com/show_bug.cgi?id=1268409, https://bugzilla.redhat.com/show_bug.cgi?id=1268410

Description

A VDB can be deployed before the datasources it depends on are fully deployed and bound, resulting in the VDB never being marked as ACTIVE. This appears to be exclusive to environments where the JDBC driver for the datasource is deployed through use of the standalone deployments/ directory. If the driver is deployed as a module, then the risk of the issue is lowered or eliminated.

Attachments

Activity

People

Assignee:: Steven Hawkins

Reporter:: Marc Shirley (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2015/08/28 2:47 PM

Updated:: 2016/02/10 3:52 AM

Resolved:: 2015/12/03 12:38 PM