[
https://issues.jboss.org/browse/TEIID-3747?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-3747:
------------------------------------
The deleting before redeploying doesn't make sense. The deployment model has always
been that a new vdb by the same name can be deployed. And if the current VDB is in use,
existing logged in users will have to log out and log back in to use the new version.
And I'm almost %100 certain designer doesn't do a check and remove a vdb prior to
redeployment. This would be no different than a user who deploys using the
admin-console. You're saying they would have to delete the prior VDB before
redeploying a subsequent version of the same named VDB. That wouldn't work, because
there would be a gap in between when the VDB is actually accessible (between when its
deleted and redeployed).
Deploying a .vdb where a dynamic vdb has already been deployed, fails
due to duplicates
---------------------------------------------------------------------------------------
Key: TEIID-3747
URL:
https://issues.jboss.org/browse/TEIID-3747
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.7.1.6_2
Reporter: Van Halbert
Assignee: Steven Hawkins
deployed a dynamic vdb using CLI: deploy teiidfiles/vdb/portfolio-vdb.xml
then in Designer, tried to deploy the same named VDB, but as a .vdb and the deployment
fails with errors indicating duplicate service:
11:26:31,301 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001:
Failed to start service jboss.deployment.unit."Portfolio.vdb".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."Portfolio.vdb".INSTALL: JBAS018733: Failed to process
phase INSTALL of deployment "Portfolio.vdb"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166)
[jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980)
[jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913)
[jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_55]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_55]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_55]
Caused by: org.jboss.msc.service.DuplicateServiceException: Service
jboss.teiid.ds-listener.Portfolio.1./accounts-ds is already registered
at
org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
[jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)