]
Debbie Steigner commented on TEIID-4957:
----------------------------------------
[~jolee] The workaround is to manually edit the /META-INF/vdb.xml file inside your VDB
archive file and set the Connection type before deploying it so that it's permanently
set:
At the top of the vdb.xml after the description add the connection-type and value.
<?xml version="1.0" encoding="UTF-8"
standalone="yes"?>
<vdb name="sample" version="1">
<description></description>
<connection-type>NONE</connection-type>
<property name="preview" value="false"/>
<property name="validationDateTime" value="Fri Feb 10 07:27:53 CST
2017"/>
<property name="validationVersion" value="8.12.8"/>
<model name=....
Setting Connection Type on VDB of a Domain Managed server gets set
back to default after server restart
-------------------------------------------------------------------------------------------------------
Key: TEIID-4957
URL:
https://issues.jboss.org/browse/TEIID-4957
Project: Teiid
Issue Type: Bug
Components: VDB
Affects Versions: 8.12.10.6_3
Reporter: Debbie Steigner
Assignee: Ramesh Reddy
Fix For: 10.0
After deploying a VDB to a managed server group, set the Connection type to anything but
the default of By_Version, so None or Any. Now restart the server and you'll see the
Connection type is reset to the default.
What I see is that when the change is made a vdb.xml with that new connection-type is
written to the /DVserverhome/domain/servers/server-two/data/teiid-data/SampleVDB_1 folder,
this folder is deleted upon a restart though so the change is not kept.
This only happens in Domain mode, running in Standalone mode saves the change because the
teiid-data is not deleted on a restart.