Bug 729846 - Datasource created through CLI not discovered by JBoss AS plugin.
Datasource created through CLI not discovered by JBoss AS plugin.
Status: NEW
Product: RHQ Project
Classification: Other
Component: Plugins (Show other bugs)
All All
low Severity low (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
Depends On:
  Show dependency treegraph
Reported: 2011-08-10 22:39 EDT by Ondřej Žižka
Modified: 2011-08-17 11:26 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ondřej Žižka 2011-08-10 22:39:01 EDT

Create a datasource through CLI.
The DS is created, but not discovered.
When I want to create it again, EAP 5.1.1 says:


java.io.SyncFailedException: Deployment content already exists: /root/eap/server/all/deploy/cliTestDS-ds.xml
        at org.jboss.system.server.profileservice.repository.BasicDeploymentRepository.addDeploymentContent(BasicDeploymentRepository.java:177)
        at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.handleStream(AbstractDeployHandler.java:288)
        at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.handleStream(AbstractDeployHandler.java:63)
        at org.jboss.remoting.ServerInvoker.handleInternalInvocation(ServerInvoker.java:1885)
        at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:954)
        at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
        at org.jboss.remoting.Client.invoke(Client.java:2055)
        at org.jboss.remoting.Client.invoke(Client.java:879)
        at org.jboss.remoting.Client.invoke(Client.java:1758)
Comment 1 Ondřej Žižka 2011-08-10 22:41:33 EDT
CLI code:

    var appTypeName = "No Tx Datasource";
    var appType = ResourceTypeManager.getResourceTypeByNameAndPlugin( appTypeName, "JBossAS5" );

    var deployConfig = new Configuration();
    deployConfig.put( new PropertySimple("jndi-name", "cliTestDS"));
    deployConfig.put( new PropertySimple("driver-class", "org.hsqldb.jdbc.JDBCDriver"));
    deployConfig.put( new PropertySimple("connection-url", "jdbc:hsqldb:mem:."));

    var as = findJBossAS();
    ResourceFactoryManager.createResource( as.id, appType.id,   "cliTestDS-res",   null, deployConfig );
Comment 2 Ondřej Žižka 2011-08-10 22:56:05 EDT
Note that discovery or discovery --full did not help.

Note You need to log in before you can comment on or make changes to this bug.