Bug 781035 (SOA-3521)

Summary: Add/Remove operations on a VDB should block other operations on the VDB
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Marc Shirley <mshirley>
Component: ToolingAssignee: Van Halbert <vhalbert>
Status: CLOSED WORKSFORME QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: atangrin, felias, fnguyen, ldimaggi, lfabriko, vhalbert
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-3521
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
When UNC paths were being used, VDB dependencies were not being resolved correctly and an ArrayIndexOutOfBoundsException was being thrown. The VdbModelEntry.synchronizeModelEntry method has been modified to use the more relaible org.eclipse.core.runtime.URIUtil package to handle the URI.
Story Points: ---
Clone Of:
: TEIIDDES-1118 (view as bug list) Environment:
Windows
Last Closed: 2014-08-26 15:42:40 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:

Description Marc Shirley 2011-10-24 19:24:54 UTC
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000008SP5t
Steps to Reproduce: In workspace stored on network filesystem, perform below steps with any existing VDB.
1) Remove model from VDB
2) Immediately add same model back into VDB
Workaround Description: The network filesystem is mapped to a drive letter in a Windows environment.  Instead of using the UNC Path for the model, use the mapped drive, to import the model.
project_key: SOA

As adding/removing objects from a VDB results in filesystem operations of adding/removing indexes, this should result in a blocking of additional operations against the VDB.  If latency with the filesystem is large enough (for example, on a network filesystem) and no blocking is performed, multiple operations can be performed on the VDB resulting in the below exception:
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.ArrayIndexOutOfBoundsException: 0
	at org.teiid.designer.vdb.VdbModelEntry.synchronizeModelEntry(VdbModelEntry.java:435)
	at org.teiid.designer.vdb.Vdb.addModelEntry(Vdb.java:244)
	at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor$25.selected(VdbEditor.java:1709)
	at com.metamatrix.ui.table.TableAndToolBar$2.run(TableAndToolBar.java:79)
	at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
	at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
	at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1384)

Comment 1 Van Halbert 2011-10-24 19:24:54 UTC
Link: Added: This issue Cloned from TEIIDDES-1118


Comment 2 Van Halbert 2011-10-24 19:25:59 UTC
Security: Added: JBoss Internal


Comment 3 Van Halbert 2011-11-02 19:19:26 UTC
Workaround Description: Added: The network filesystem is mapped to a drive letter in a Windows environment.  Instead of using the UNC Path for the model, use the mapped drive, to import the model.


Comment 4 JBoss JIRA Server 2012-12-14 19:45:22 UTC
Barry LaFond <blafond> updated the status of jira TEIIDDES-1118 to Closed

Comment 5 JBoss JIRA Server 2012-12-14 19:45:22 UTC
Barry LaFond <blafond> made a comment on jira TEIIDDES-1118

Version 8.0 Final is released

Comment 9 belong 2013-11-19 23:29:15 UTC
Fixed before GA - setting to requires_doc_text- accordingly

Comment 10 JBoss JIRA Server 2014-02-05 11:48:59 UTC
Lucie Fabrikova <lfabriko> updated the status of jira TEIIDDES-1118 to Reopened

Comment 11 Lucie Fabrikova 2014-02-05 13:01:53 UTC
Encountered a problem with adding web service models to VDB, viz TEIIDDES-1118.

Comment 12 JBoss JIRA Server 2014-08-26 15:24:59 UTC
Barry LaFond <blafond> updated the status of jira TEIIDDES-1118 to Resolved

Comment 14 JBoss JIRA Server 2014-11-17 16:22:09 UTC
Barry LaFond <blafond> updated the status of jira TEIIDDES-1118 to Closed