Databases
StackOverflow2013
Postsdbo
POUsing JBoss 4.2.x, how can I deploy a new data source without undeploying existing ones?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing JBoss 4.2.x, how can I deploy a new data source without undeploying existing ones?
    primarykey
    data
    text
    <p>Configuration management for our EE application requires us to create a new database connection datasource from time to time. We do this right now by modifying the deploy/[dbtype]-ds.xml file, inserting an additional connection definition into this file. The problem is, doing so causes the existing connections to be undeployed and redeployed in addition to the new one being created.</p> <p>From the JBoss log:</p> <pre><code>12:52:13,096 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=dsmDS' from JNDI name 'java:dsmDS' 12:52:13,386 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=ecourierDS' from JNDI name 'java:ecourierDS' 12:52:20,321 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=ecourierDS' to JNDI name 'java:ecourierDS' 12:52:20,671 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=dsmDS' to JNDI name 'java:dsmDS' 12:52:26,512 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=ecourier-core360aDS' to JNDI name 'java:ecourier-core360aDS' </code></pre> <p>Is there a way to deploy a new data source (or remove or modify an existing one) without unbinding any otherwise-unaffected data sources?</p> <p>(edit) It was suggested that we just add the data source in a new file, but that doesn't work, at least not out of the box; if I add the core360aDS data source in a file named <code>core360aDS.xml</code> in the deploy directory, these error messages are issued:</p> <pre><code>--- Packages waiting for a deployer --- org.jboss.deployment.DeploymentInfo@3ccd9d83 { url=file:/home/rosec/testing/ecas/var/jboss/server/core41/deploy/core360aDS.xml } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/home/rosec/testing/ecas/var/jboss/server/core41/deploy/core360aDS.xml altDD: null lastDeployed: 1235079499893 lastModified: 1235079499000 mbeans: --- Incompletely deployed packages --- org.jboss.deployment.DeploymentInfo@3ccd9d83 { url=file:/home/rosec/testing/ecas/var/jboss/server/core41/deploy/core360aDS.xml } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/home/rosec/testing/ecas/var/jboss/server/core41/deploy/core360aDS.xml altDD: null lastDeployed: 1235079499893 lastModified: 1235079499000 mbeans: </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USChris R
    1. USChris R
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUsing JBoss 4.2.x, how can I deploy a new data source without undeploying existing ones?
      1. USsourcerebels
      1. VTFavorite
    2. VO
      singulars
      1. POUsing JBoss 4.2.x, how can I deploy a new data source without undeploying existing ones?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload