[
https://issues.jboss.org/browse/TEIID-4174?page=com.atlassian.jira.plugin...
]
Steve Tran updated TEIID-4174:
------------------------------
Description:
With any source control tool, if I clone/checkout a VDB project, the name of the project
must match the name it was created with. All the internal references are using an
absolute path with the original project name as the root. This makes VDB projects less
portable because someone who comes in and does a git clone <git url>
<their_name> will have an unstable project unless they change <their_name> to
what the VDB is hard-coded to.
I'm seeing if there's a workaround, such as renaming the internal references, but
it looks like a lot of work.
was:
Getting an error while replacing an existing VDB with JDV 6.2.4. I think the logging
level is inappropriate since the VDB has full functionality since I am able to connect and
execute some queries. Could lead to something more serious though, so reporting it as a
bug until proven innocent.
{code}
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,954 WARN
[org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already
registered MBean: jgroups:type=protocol,cluster
="STEVE.1",protocol=UFCESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,955 WARN
[org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already
registered MBean: jgroups:type=protocol,cluster
="STEVE.1",protocol=GMSESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,957 WARN
[org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already
registered MBean: jgroups:type=protocol,cluster
="STEVE.1",protocol=STABLEESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,958 WARN
[org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already
registered MBean: jgroups:type=protocol,cluster
="STEVE.1",protocol=UNICAST2ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,959 WARN
[org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already
registered MBean: jgroups:type=protocol,cluster
="STEVE.1",protocol=NAKACKESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,961 WARN
[org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already
registered MBean: jgroups:type=protocol,cluster
="STEVE.1",protocol=BARRIERESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,961 WARN
[org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already
registered MBean: jgroups:type=protocol,cluster
="STEVE.1",protocol=VERIFY_SUSPECTESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,962 WARN
[org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already
registered MBean: jgroups:type=protocol,cluster
="STEVE.1",protocol=FDESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,963 WARN
[org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already
registered MBean:
jgroups:type=protocol,cluster="STEVE.1",protocol=FD_SOCKESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,964 WARN
[org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already
registered MBean: jgroups:type=protocol,cluster="STEVE.1",protocol=MERGE2ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,964 WARN
[org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already
registered MBean:
jgroups:type=protocol,cluster="STEVE.1",protocol=TCPPINGESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,965 WARN
[org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already
registered MBean: jgroups:type=protocol,cluster="STEVE.1",protocol=TCPESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[33m22:08:39,968 WARN
[org.jgroups.jmx.JmxConfigurator] (teiid-async-threads - 8) unregistering already
registered MBean: jgroups:type=channel,cluster="STEVE.1"ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[33mESC[0mESC[31m22:08:39,969 ERROR [org.teiid.RUNTIME]
(teiid-async-threads - 8) TEIID40088 Could not replicate object
org.teiid.query.tempdata.GlobalTableStoreImpl@6518dd87: java.lang.IllegalStateException:
cluster 'STEVE.1' is already connected to singleton transport:
[dummy-1461636444525, dummy-1461636519952, PHX_ODS_DMM_LEGACY.1, PHX_ODS_DBA.1,
Odata_TEST.1, ProjectionsUSHSI.1, ImputationV1.1, GMR_SQLDB_TEST.1, UK_PBS_VDB.1,
EDE_US.1, BDF_CorrectionsVDB_V1.1, ImputationV1_DEV.1, HSISIT.1, UKPROJECTION.1, Gossip.1,
HCR_CADM_CR_PROC.1, HSIWIP.1, MyVDB.1, dummy-1460722343623, HSIRES.1,
KnowledgeFactory_Job.1, HSITEST.1, HCR_CADM_SYNDICATED.1, COL_VDB.1, dummy-1460722100133,
$TEIID_BM$, BDF_CorrectionsVDB_SIT.1, dummy-1460720870935, PROJECTIONTEMPVDB.1,
UK_PBS_Project_VDB.1, PROJECTIONVDB.1, $TEIID_ED$, DeployVDB.1, GMR_SQLDB_DBA.1,
teiid-cache, STEVE.1, dummy-1460722176622, HCR_CADM.1, HSI.1, dummy-1461636277237,
DedupsVdb.1, IMPUTATION_FRANCE.1, dummy-1460720872393, MSTRTestVdb.1]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at
org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:919)
[jgroups-3.2.15.Final-redhat-1.jar:3.2.15.Final-redhat-1]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at
org.jgroups.JChannel.startStack(JChannel.java:827)
[jgroups-3.2.15.Final-redhat-1.jar:3.2.15.Final-redhat-1]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at
org.jgroups.JChannel._preConnect(JChannel.java:525)
[jgroups-3.2.15.Final-redhat-1.jar:3.2.15.Final-redhat-1]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at org.jgroups.JChannel.connect(JChannel.java:277)
[jgroups-3.2.15.Final-redhat-1.jar:3.2.15.Final-redhat-1]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at org.jgroups.JChannel.connect(JChannel.java:268)
[jgroups-3.2.15.Final-redhat-1.jar:3.2.15.Final-redhat-1]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at
org.teiid.replication.jgroups.JGroupsObjectReplicator.replicate(JGroupsObjectReplicator.java:564)
[teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at
org.teiid.deployers.CompositeGlobalTableStore.createInstance(CompositeGlobalTableStore.java:57)
[teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]
ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at
org.teiid.jboss.VDBService$1.finishedDeployment(VDBService.java:156)
[teiid-jboss-integration-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at
org.teiid.deployers.VDBRepository.notifyFinished(VDBRepository.java:348)
[teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at
org.teiid.deployers.VDBRepository.finishDeployment(VDBRepository.java:304)
[teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at
org.teiid.runtime.AbstractVDBDeployer.metadataLoaded(AbstractVDBDeployer.java:202)
[teiid-runtime-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at
org.teiid.jboss.VDBService.access$1100(VDBService.java:85)
[teiid-jboss-integration-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at
org.teiid.jboss.VDBService$6.run(VDBService.java:408)
[teiid-jboss-integration-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at
org.teiid.jboss.VDBService$7.run(VDBService.java:439)
[teiid-jboss-integration-8.7.5.6_2-redhat-2.jar:8.7.5.6_2-redhat-2]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_75]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_75]ESC[0m
[Server:cdtssoa126d-jdv-one] ESC[31m at java.lang.Thread.run(Thread.java:745)
[rt.jar:1.7.0_75]ESC[0m
{code}
Local project name baked into VDB
---------------------------------
Key: TEIID-4174
URL:
https://issues.jboss.org/browse/TEIID-4174
Project: Teiid
Issue Type: Bug
Environment: Red Hat JBoss Data Virtualization 6.2.4 on EAP patched to version
6.4.6, on Oracle Linux 6
JBoss Developer Studio 8.1.0GA with Teiid Designer
9.0.6.Final-v20160316-1409-B1242 org.teiid.designer.feature.feature.group JBoss by Red
Hat, Inc.
64-bit Windows 7 environment
Reporter: Steve Tran
Assignee: Steven Hawkins
With any source control tool, if I clone/checkout a VDB project, the name of the project
must match the name it was created with. All the internal references are using an
absolute path with the original project name as the root. This makes VDB projects less
portable because someone who comes in and does a git clone <git url>
<their_name> will have an unstable project unless they change <their_name> to
what the VDB is hard-coded to.
I'm seeing if there's a workaround, such as renaming the internal references, but
it looks like a lot of work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)