14 Replies Latest reply on Mar 22, 2013 3:55 PM by Danah Warren

    VDB deployed but not active

    Danah Warren Newbie

      I'm trying to access my dynamic VDB through JDBC in Eclipse and I've installed JBoss AS and Teiid 8.3 locally. I've been reviewing all of the support docs (quick start, client developers guide, admin guide, ect.) on standalone applications but I still have a problem. The server is deploying my VDB but when I execute my java class I get the following errors:

       

      Exception in thread "main" java.lang.reflect.UndeclaredThrowableException

                at com.sun.proxy.$Proxy0.logon(Unknown Source)

                at org.teiid.net.socket.SocketServerConnection.logon(SocketServerConnection.java:173)

                at org.teiid.net.socket.SocketServerConnection.selectServerInstance(SocketServerConnection.java:125)

                at org.teiid.net.socket.SocketServerConnection.<init>(SocketServerConnection.java:92)

                at org.teiid.net.socket.SocketServerConnectionFactory.getConnection(SocketServerConnectionFactory.java:312)

                at org.teiid.jdbc.SocketProfile.connect(SocketProfile.java:54)

                at org.teiid.jdbc.TeiidDriver.connect(TeiidDriver.java:107)

                at org.teiid.jdbc.TeiidDriver.connect(TeiidDriver.java:55)

                at java.sql.DriverManager.getConnection(DriverManager.java:579)

                at java.sql.DriverManager.getConnection(DriverManager.java:221)

                at DataAccess.main(DataAccess.java:46)

       

      Caused by: org.teiid.client.security.TeiidSecurityException: TEIID40046 Remote org.teiid.client.security.LogonException: TEIID40046 VDB "Baseball" version "latest" does not exist.

                at org.teiid.transport.LogonImpl.logon(LogonImpl.java:116)

                at org.teiid.transport.LogonImpl.logon(LogonImpl.java:82)

                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

                at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

                at java.lang.reflect.Method.invoke(Unknown Source)

                at org.teiid.transport.ServerWorkItem.run(ServerWorkItem.java:87)

                at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:264)

                at org.teiid.transport.SocketClientInstance.processMessagePacket(SocketClientInstance.java:166)

                at org.teiid.transport.SocketClientInstance.receivedMessage(SocketClientInstance.java:152)

                at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:210)

                at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:100)

                at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)

                at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:783)

                at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:149)

                at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)

                at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:783)

                at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302)

                at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317)

                at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)

                at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)

                at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80)

                at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)

                at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)

                at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)

                at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)

                at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:351)

                at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:282)

                at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:202)

                at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)

                at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44)

                at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

                at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

                at java.lang.Thread.run(Unknown Source)

       

      Caused by: org.teiid.client.security.TeiidSecurityException: TEIID40046 Remote org.teiid.dqp.service.SessionServiceException: TEIID40046 VDB "Baseball" version "latest" does not exist.

                at org.teiid.services.SessionServiceImpl.getActiveVDB(SessionServiceImpl.java:259)

                at org.teiid.services.SessionServiceImpl.createSession(SessionServiceImpl.java:140)

                at org.teiid.transport.LogonImpl.logon(LogonImpl.java:99)

       

      Please provide any and all feedback/suggestions you may have. I'm about to go crazy.

       

      Thanks in advance!

        • 1. Re: VDB deployed but not active
          Mark Drilling Novice

          In your server log, you should see something like this when the dynamic vdb deploys:

          12:26:07,102 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7)  JBAS015876: Starting deployment of "importVDB-vdb.xml"

          12:26:07,786 INFO  [org.teiid.RUNTIME] (MSC service thread 1-6)  TEIID50029 VDB importVDB.1 model "importVDBSrcModel" metadata is currently being loaded. Start Time: 3/22/13 12:26 PM

          12:26:07,805 INFO  [org.teiid.RUNTIME] (teiid-async-threads - 1)  TEIID50030 VDB importVDB.1 model "importVDBSrcModel" metadata loaded. End Time: 3/22/13 12:26 PM

          12:26:07,809 INFO  [org.teiid.RUNTIME] (teiid-async-threads - 1)  TEIID40003 VDB importVDB.1 is set to ACTIVE

          12:26:07,997 INFO  [org.jboss.as.server] (management-handler-thread - 2)  JBAS018559: Deployed "importVDB-vdb.xml"

           

          In your server log, do you see that your vdb deploys and goes to ACTIVE?  If different than above, please paste the log snippet

          Thanks

          Mark

          • 2. Re: VDB deployed but not active
            Steven Hawkins Master

            It may also be good to use an admin connection or one of the admin consoles to understand what vdbs you have deployed and what state they are in.

             

            It should be unrelated to any problems you are having on the server-side, but you may have a classpath issue with your eclipse setup as the exception should eventually be thrown as a normal SQLException and not originate as an UndeclaredThrowableException.

             

            Steve

            • 3. Re: VDB deployed but not active
              Danah Warren Newbie

              Here is the output from the command : standalone.bat -c standalone-teiid.xml

               

              ===============================================================================

               

               

                JBoss Bootstrap Environment

               

               

                JBOSS_HOME: C:\Teiid 8.3\JBoss

               

               

                JAVA: java

               

               

                JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx51

              2M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.se

              rver.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.war

              ning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.default.c

              onfig=standalone.xml

               

               

              ===============================================================================

               

               

              13:35:59,307 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

              13:35:59,501 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

              13:35:59,543 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" sta

              rting

              13:36:00,550 INFO  [org.jboss.as.server] JBAS015888: Creating http management se

              rvice using socket-binding (management-http)

              13:36:00,550 INFO  [org.xnio] XNIO Version 3.0.3.GA

              13:36:00,564 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA

              13:36:00,573 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA

              13:36:00,594 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log han

              dlers

              13:36:00,615 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 27)

              JBAS016200: Activating ConfigAdmin Subsystem

              13:36:00,621 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 39)  JBAS

              011800: Activating Naming Subsystem

              13:36:00,620 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 50)

              JBAS015537: Activating WebServices Extension

              13:36:00,619 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 40)  JBAS01

              1940: Activating OSGi Subsystem

              13:36:00,618 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 45)  JB

              AS013101: Activating Security Subsystem

              13:36:00,615 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Po

              ol -- 32)  JBAS010280: Activating Infinispan subsystem.

              13:36:00,689 INFO  [org.jboss.as.security] (MSC service thread 1-8)  JBAS013100:

              Current PicketBox version=4.0.7.Final

              13:36:00,859 INFO  [org.jboss.as.connector] (MSC service thread 1-4)  JBAS010408

              : Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

              13:36:01,247 INFO  [org.jboss.as.naming] (MSC service thread 1-4)  JBAS011802: S

              tarting Naming Service

              13:36:01,257 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-4)  JBAS0

              15400: Bound mail session [java:jboss/mail/Default]

              13:36:01,268 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerServic

              e Thread Pool -- 28)  JBAS010403: Deploying JDBC-compliant driver class org.h2.D

              river (version 1.3)

              13:36:01,300 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerServic

              e Thread Pool -- 28)  JBAS010404: Deploying non-JDBC-compliant driver class org.

              teiid.jdbc.TeiidDriver (version 8.3)

              13:36:01,303 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerServic

              e Thread Pool -- 28)  JBAS010404: Deploying non-JDBC-compliant driver class org.

              teiid.jdbc.TeiidDriver (version 8.3)

              13:36:01,374 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC se

              rvice thread 1-6)  JBoss Web Services - Stack CXF Server 4.0.2.GA

              13:36:01,387 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread

              1-7)  Starting Coyote HTTP/1.1 on http--127.0.0.1-8080

              13:36:01,824 INFO  [org.teiid.SECURITY] (ServerService Thread Pool -- 46)  TEIID

              50011 Security enabled for transport "jdbc" with security-domain set to teiid-se

              curity

              13:36:01,832 INFO  [org.teiid.SECURITY] (ServerService Thread Pool -- 46)  TEIID

              50011 Security enabled for transport "odata" with security-domain set to teiid-s

              ecurity

              13:36:01,838 INFO  [org.teiid.SECURITY] (ServerService Thread Pool -- 46)  TEIID

              50011 Security enabled for transport "odbc" with security-domain set to teiid-se

              curity

              13:36:01,913 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "access" added.

              13:36:01,937 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service

              thread 1-7)  JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

              13:36:01,937 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service

              thread 1-6)  JBAS010400: Bound data source [java:/teiidDS]

              13:36:01,946 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "db2" added.

              13:36:02,012 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "derby" added.

              13:36:02,023 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "file" added.

              13:36:02,078 INFO  [org.infinispan.factories.GlobalComponentRegistry] (pool-12-t

              hread-1)  ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.2.FINAL

              13:36:02,081 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "h2" added.

              13:36:02,095 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "hive" added.

              13:36:02,117 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "hsql" added.

              13:36:02,129 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "infinispan-cache" added.

              13:36:02,152 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "informix" added.

              13:36:02,391 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "ingres" added.

              13:36:02,431 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "ingres93" added.

              13:36:02,460 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "intersystems-cache" added.

              13:36:02,472 INFO  [org.infinispan.jmx.CacheJmxRegistration] (pool-12-thread-1)

              ISPN000031: MBeans were successfully registered to the platform mbean server.

              13:36:02,477 INFO  [org.infinispan.jmx.CacheJmxRegistration] (pool-10-thread-1)

              ISPN000031: MBeans were successfully registered to the platform mbean server.

              13:36:02,477 INFO  [org.jboss.as.clustering.infinispan] (pool-12-thread-1)  JBAS

              010281: Started preparedplan cache from teiid container

              13:36:02,480 INFO  [org.jboss.as.clustering.infinispan] (pool-10-thread-1)  JBAS

              010281: Started resultset cache from teiid container

              13:36:02,477 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "jdbc-ansi" added.

              13:36:02,492 INFO  [org.infinispan.jmx.CacheJmxRegistration] (pool-11-thread-1)

              ISPN000031: MBeans were successfully registered to the platform mbean server.

              13:36:02,497 INFO  [org.jboss.as.clustering.infinispan] (pool-11-thread-1)  JBAS

              010281: Started resultset-repl cache from teiid container

              13:36:02,498 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "jdbc-simple" added.

              13:36:02,509 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "jpa2" added.

              13:36:02,520 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "ldap" added.

              13:36:02,535 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "loopback" added.

              13:36:02,541 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "map-cache" added.

              13:36:02,564 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "metamatrix" added.

              13:36:02,593 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "modeshape" added.

              13:36:02,758 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "mysql" added.

              13:36:02,788 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "mysql5" added.

              13:36:02,816 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "netezza" added.

              13:36:02,828 INFO  [org.teiid.RUNTIME] (MSC service thread 1-5)  TEIID50001 Teii

              d Engine 8.3.0.Final Started = Fri Mar 22 13:36:02 EDT 2013

              13:36:02,837 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "odata" added.

              13:36:02,839 INFO  [org.teiid.RUNTIME] (MSC service thread 1-8)  TEIID50038 Teii

              d Embedded transport enabled. Bound to: teiid/queryengine/odata

              13:36:02,849 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "olap" added.

              13:36:02,887 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "oracle" added.

              13:36:02,880 INFO  [org.teiid.RUNTIME] (MSC service thread 1-2)  TEIID50038 Teii

              d Embedded transport enabled. Bound to: teiid/queryengine/embedded

              13:36:02,915 INFO  [org.teiid.RUNTIME] (MSC service thread 1-5)  TEIID50037 Teii

              d ODBC - Name = odbc, Host = 127.0.0.1,  Port = 35432, SSL = OFF, security-domai

              ns = [teiid-security]

              13:36:02,918 INFO  [org.teiid.RUNTIME] (MSC service thread 1-4)  TEIID50012 Teii

              d JDBC - Name = jdbc, Host = 127.0.0.1,  Port = 31000, SSL = OFF, security-domai

              ns = [teiid-security]

              13:36:02,923 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "postgresql" added.

              13:36:02,937 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "salesforce" added.

              13:36:02,970 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "sqlserver" added.

              13:36:02,998 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "sybase" added.

              13:36:03,027 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "teiid" added.

              13:36:03,055 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "teradata" added.

              13:36:03,063 INFO  [org.teiid.RUNTIME] (ServerService Thread Pool -- 46)  TEIID5

              0006 Teiid translator "ws" added.

              13:36:03,088 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5)  JB

              AS015876: Starting deployment of "teiid-odata-8.3.0.Final.war"

              13:36:03,113 INFO  [org.jboss.as.remoting] (MSC service thread 1-2)  JBAS017100:

              Listening on /127.0.0.1:9999

              13:36:03,114 INFO  [org.jboss.as.remoting] (MSC service thread 1-6)  JBAS017100:

              Listening on 127.0.0.1/127.0.0.1:4447

              13:36:03,136 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread

              1-7)  JBAS015012: Started FileSystemDeploymentService for directory C:\Teiid 8.3

              \JBoss\standalone\deployments

              13:36:03,154 WARN  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-t

              hreads - 1)  JBAS015002: Deployment of 'baseball.vdb' requested, but the deploym

              ent is not present

              13:36:03,631 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thre

              ad 1-5)  Deploying javax.ws.rs.core.Application: class org.teiid.odata.TeiidODat

              aApplication

              13:36:03,769 INFO  [org.jboss.web] (MSC service thread 1-5)  JBAS018210: Registe

              ring web context: /odata

              13:36:03,785 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 46)  JBAS

              018559: Deployed "teiid-odata-8.3.0.Final.war"

              13:36:03,809 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5)  JB

              AS015876: Starting deployment of "baseball.vdb.xml"

              13:36:03,812 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4)  JB

              AS015876: Starting deployment of "teiid-8.3.0.Final-jdbc.jar"

              13:36:03,817 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1)  JB

              AS015876: Starting deployment of "teiid-connector-file.rar"

              13:36:03,819 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6)  JB

              AS015876: Starting deployment of "teiid-connector-ldap.rar"

              13:36:03,819 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5)  JB

              AS015876: Starting deployment of "teiid-connector-google.rar"

              13:36:03,825 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1)  JB

              AS015876: Starting deployment of "teiid-connector-infinispan.rar"

              13:36:03,825 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7)  JB

              AS015876: Starting deployment of "teiid-connector-salesforce.rar"

              13:36:03,828 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2)  JB

              AS015876: Starting deployment of "teiid-connector-ws.rar"

              13:36:03,968 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7)  J

              BAS018567: Deployment "deployment.teiid-connector-ws.rar" is using a private mod

              ule ("org.apache.cxf:main") which may be changed or removed in future versions w

              ithout notice.

              13:36:03,972 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7)  J

              BAS018567: Deployment "deployment.teiid-connector-ws.rar" is using a private mod

              ule ("org.apache.cxf:main") which may be changed or removed in future versions w

              ithout notice.

              13:36:03,987 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4)  J

              BAS018567: Deployment "deployment.teiid-connector-infinispan.rar" is using a pri

              vate module ("org.infinispan.client.hotrod:main") which may be changed or remove

              d in future versions without notice.

              13:36:03,999 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4)  J

              BAS018567: Deployment "deployment.teiid-connector-infinispan.rar" is using a pri

              vate module ("org.infinispan.cachestore.remote:main") which may be changed or re

              moved in future versions without notice.

              13:36:04,008 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3)  J

              BAS018567: Deployment "deployment.teiid-connector-salesforce.rar" is using a pri

              vate module ("org.apache.cxf:main") which may be changed or removed in future ve

              rsions without notice.

              13:36:04,011 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4)  J

              BAS018567: Deployment "deployment.teiid-connector-infinispan.rar" is using a pri

              vate module ("org.jboss.as.clustering.infinispan:main") which may be changed or

              removed in future versions without notice.

              13:36:04,019 INFO  [org.jboss.as.connector.deployers.RADeployer] (MSC service th

              read 1-1)  IJ020001: Required license terms for file:/C:/Teiid%208.3/JBoss/stand

              alone/tmp/vfs/temp30c0e4cae11e0628/teiid-connector-ws.rar-981de872e984ea06/conte

              nts/

              13:36:04,016 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3)  J

              BAS018567: Deployment "deployment.teiid-connector-salesforce.rar" is using a pri

              vate module ("org.apache.cxf:main") which may be changed or removed in future ve

              rsions without notice.

              13:36:04,025 INFO  [org.jboss.as.connector.deployers.RADeployer] (MSC service th

              read 1-5)  IJ020001: Required license terms for file:/C:/Teiid%208.3/JBoss/stand

              alone/tmp/vfs/temp30c0e4cae11e0628/teiid-connector-ldap.rar-8a7ac4a8de904c/conte

              nts/

              13:36:04,061 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4)  J

              BAS018567: Deployment "deployment.teiid-connector-infinispan.rar" is using a pri

              vate module ("org.infinispan.client.hotrod:main") which may be changed or remove

              d in future versions without notice.

              13:36:04,091 INFO  [org.jboss.as.connector.deployers.RADeployer] (MSC service th

              read 1-7)  IJ020001: Required license terms for file:/C:/Teiid%208.3/JBoss/stand

              alone/tmp/vfs/temp30c0e4cae11e0628/teiid-connector-file.rar-3e279dfbf51a2da3/con

              tents/

              13:36:04,088 INFO  [org.jboss.as.connector.deployers.RADeployer] (MSC service th

              read 1-3)  IJ020001: Required license terms for file:/C:/Teiid%208.3/JBoss/stand

              alone/tmp/vfs/temp30c0e4cae11e0628/teiid-connector-google.rar-2b8f881dbcef22b6/c

              ontents/

              13:36:04,080 INFO  [org.jboss.as.connector.deployers.RADeployer] (MSC service th

              read 1-2)  IJ020001: Required license terms for file:/C:/Teiid%208.3/JBoss/stand

              alone/tmp/vfs/temp30c0e4cae11e0628/teiid-connector-salesforce.rar-9104a8abcff3c3

              45/contents/

              13:36:04,096 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4)  J

              BAS018567: Deployment "deployment.teiid-connector-infinispan.rar" is using a pri

              vate module ("org.infinispan.cachestore.remote:main") which may be changed or re

              moved in future versions without notice.

              13:36:04,113 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4)  J

              BAS018567: Deployment "deployment.teiid-connector-infinispan.rar" is using a pri

              vate module ("org.jboss.as.clustering.infinispan:main") which may be changed or

              removed in future versions without notice.

              13:36:04,108 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1

              -8)  JBAS010404: Deploying non-JDBC-compliant driver class org.teiid.jdbc.TeiidD

              river (version 8.3)

              13:36:04,120 INFO  [org.jboss.as.connector.deployers.RADeployer] (MSC service th

              read 1-4)  IJ020001: Required license terms for file:/C:/Teiid%208.3/JBoss/stand

              alone/tmp/vfs/temp30c0e4cae11e0628/teiid-connector-infinispan.rar-6b968959ff4bef

              22/contents/

              13:36:04,153 INFO  [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service

              thread 1-7)  IJ020001: Required license terms for file:/C:/Teiid%208.3/JBoss/st

              andalone/tmp/vfs/temp30c0e4cae11e0628/teiid-connector-file.rar-3e279dfbf51a2da3/

              contents/

              13:36:04,163 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-7)

              JBAS010406: Registered connection factory java:/allstar-file

              13:36:04,170 INFO  [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service

              thread 1-7)  IJ020002: Deployed: file:/C:/Teiid%208.3/JBoss/standalone/tmp/vfs/

              temp30c0e4cae11e0628/teiid-connector-file.rar-3e279dfbf51a2da3/contents/

              13:36:04,175 INFO  [org.jboss.as.deployment.connector] (MSC service thread 1-6)

              JBAS010401: Bound JCA ConnectionFactory [java:/allstar-file]

              13:36:04,177 INFO  [org.jboss.as] (MSC service thread 1-2)  JBAS015951: Admin co

              nsole listening on http://127.0.0.1:9990

              13:36:04,183 INFO  [org.jboss.as] (MSC service thread 1-2)  JBAS015874: JBoss AS

              7.1.1.Final "Brontes" started in 5087ms - Started 425 of 533 services (106 serv

              ices are passive or on-demand)

              13:36:04,228 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2)  JBAS01

              8559: Deployed "teiid-connector-ws.rar"

              13:36:04,229 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2)  JBAS01

              8559: Deployed "teiid-connector-salesforce.rar"

              13:36:04,232 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2)  JBAS01

              8559: Deployed "teiid-connector-ldap.rar"

              13:36:04,233 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2)  JBAS01

              8559: Deployed "teiid-connector-infinispan.rar"

              13:36:04,235 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2)  JBAS01

              8559: Deployed "teiid-connector-google.rar"

              13:36:04,236 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2)  JBAS01

              8559: Deployed "teiid-connector-file.rar"

              13:36:04,238 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2)  JBAS01

              8559: Deployed "teiid-8.3.0.Final-jdbc.jar"

              13:36:04,239 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2)  JBAS01

              8559: Deployed "baseball.vdb.xml"

               

              The allstar-file is the jndi name for my CSV text file (which is my only data source in the VDB).

               

              Thanks!

              • 4. Re: VDB deployed but not active
                Mark Drilling Novice

                Teiid expects your dynamic vdbs to be named *-vdb.xml,  so just change your baseball vdb to "baseball-vdb.xml" - then you should be good.

                • 5. Re: VDB deployed but not active
                  Danah Warren Newbie

                  Hi Mark,

                   

                  I tried that.

                   

                  I got tons of errors.

                   

                  Some of them were "Failed to process phase PARSE of deployment of baseball-vdb.xml" and "Failed to process phase STRUCTURE of deployment of baseball-vdb.xml".

                   

                  Also, in the Administrators Guide in Section 2.1 Direct File Deployment on page 9, its says " For example, if your vdb name is "enterprise.vdb", then marker file name should be "enterprise.vdb.dodeploy"...this only works in Standalone mode".

                   

                  I followed those instructions verbatim.

                   

                  I've also tried using the Teiid Designer but I get a "Failed to make a connection to the Teiid JDBC source" error.

                   

                  Believe me, I have all the guides, quick starts, and examples printed out and right in front of me. I've followed the instructions religiously.

                   

                  Please tell me, is this correct for creating a VDB with only one data source, which is a CSV file:

                   

                  1. Make the dynamic VDB in xml

                  2. Add the teiid-local jdbc data source to the datasources section of standalone-teiid.xml

                  3. Add the file connection definitions & properties of my CSV file to the resource adapters section of standalone-teiid.xml

                  4. Make the empty dodeploy file for the VDB

                  5. Add the jdbc jar to the build path of my project in Eclipse

                  6. Run the teiid server

                  7. Execute the java class

                   

                  What am i missing??

                   

                  Is it mandatory is use Maven in Eclipse?

                  • 6. Re: VDB deployed but not active
                    Mark Drilling Novice

                    Hi Danah,

                    1) The "Direct File Deployment" section is referring to the standard "archive" style of VDB.  The documentation could probably be more specific - recommend you log a teiid jira, and the teiid team can evaluate and reword it.

                    The dynamic vdb is picked up by the teiid server based on the name *-vdb.xml.  See https://docs.jboss.org/author/display/teiid830final/Dynamic+VDBs - which shows the name pattern requirement.

                     

                    2) Also, here is an example of a dynamic VDB file format from the documentation - https://docs.jboss.org/author/display/teiid830final/Portfolio+VDB

                     

                    So the "Failed to process phase PARSE ...." message indicates a formatting problem with your baseball-vdb.xml file.  You can compare it with the example from #2 to see if you can identify.

                     

                    In your steps, you dont need step #4 - the server should pick it up and deploy it.

                    • 7. Re: VDB deployed but not active
                      Steven Hawkins Master

                      > Some of them were "Failed to process phase PARSE of deployment of baseball-vdb.xml" and "Failed to process phase STRUCTURE of deployment of baseball-vdb.xml".

                       

                      That means that your xml is invalid.  There should be errors in the log, or you can validate against the schema - https://github.com/teiid/teiid/blob/master/client/src/main/resources/vdb-deployer.xsd

                       

                      All of the other problems you are seeing need to wait until you at least have a valid file to deploy.

                       

                      > I followed those instructions verbatim.

                       

                      It's meant to be more generic.  To deploy artifact x, you use x.dodeploy - so with baseball-vdb.xml you would use baseball-vdb.xml.dodeploy

                       

                      See also the github quickstarts - https://github.com/teiid/teiid-quickstarts/tree/master/dynamicvdb-dataroles/src/vdb

                       

                      > Please tell me, is this correct for creating a VDB with only one data source, which is a CSV file:

                       

                      Step 2 is only needed if you will be making local in-vm connections to Teiid.  It is not needed for remote access.

                       

                      > Is it mandatory is use Maven in Eclipse?

                       

                      No.  For remote access just adding the final client jar to the classpath is suffcient.

                      • 8. Re: VDB deployed but not active
                        Danah Warren Newbie

                        Hi,

                         

                        First of all, you both are being so helpful. I really really appreciate this.

                         

                        Okay, so I renamed my VDB correctly and I removed the teiid-local data source from standalone-teiid.xml. The Teiid JDBC jar is configured in my build path.

                         

                        I ran the server and it says it was deployed, that's it. No models, not metadata, no Active. And i'm getting the same errors in Eclipse.

                         

                        In particular, what does this one mean:

                         

                        Caused by: org.teiid.client.security.TeiidSecurityException: TEIID40046 Remote org.teiid.client.security.LogonException: TEIID40046 VDB "Baseball" version "latest" does not exist.

                         

                        Here is my URL: String url = "jdbc:teiid:Baseball@mm://localhost:31000";

                         

                        Should I add "PassthroughAuthentication = true" to my URL?

                         

                        I used the code from the Standalone Java Application code in the Quick Start Guide.

                         

                        Again, thanks.

                        • 9. Re: VDB deployed but not active
                          Mark Drilling Novice

                          The vdb is still not deployed, so you will not be able to connect to it.  You need a message similar to the one I posted first that indicates the vdb metadata has loaded and the vdb is active

                          • 10. Re: VDB deployed but not active
                            Danah Warren Newbie

                            Hi Mark,

                             

                            Yes, I agree. I realize that I cannot proceed until the metadata is loaded and the VDB is active.

                             

                            So what shoud I do? I believe I've done everything correctly, especially now with you guys's help.

                             

                            What am i missing?

                             

                            Would it be possible for us to communicate via phone so you can help me more directly?

                            • 11. Re: VDB deployed but not active
                              Steven Hawkins Master

                              > I ran the server and it says it was deployed, that's it. No models, not metadata, no Active. And i'm getting the same errors in Eclipse.

                               

                              Sounds like there's something still not correct about your vdb.xml.  You should post your vdb.xml if you can or just follow the twitter quick start just to get something working - https://github.com/teiid/teiid-quickstarts/tree/master/dynamicvdb-webservices-to-twitter

                               

                              If that gives you problems, just start with an extremely simple vdb.xml that has no sources -

                               

                              {code}

                              <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

                              <vdb name="test" version="1">

                                   <model name="test" type="VIRTUAL">

                                       <metadata type="DDL"><![CDATA[

                              CREATE VIEW helloworld as SELECT 'HELLO WORLD';

                              ]]> </metadata>

                                  </model>

                              </vdb>

                              {code}

                               

                              NOTE: that for some reason this is displaying for me with \]\]>, but it should be ]]>

                               

                              Then connect to the test vdb and issue "select * from helloworld".

                               

                              > In particular, what does this one mean:

                               

                              It means that the server does not have a Baseball vdb deployed.

                               

                              > Should I add "PassthroughAuthentication = true" to my URL?

                               

                              No that is not applicapble to remote connections.

                               

                              Steve

                              • 12. Re: VDB deployed but not active
                                Mark Drilling Novice

                                Let's start by looking at your dynamic vdb.  Is the name of the vdb "baseball-vdb.xml" now?  Is that what your server log says deployed?  You can attach the -vdb.xml and we will take a look at it.

                                • 13. Re: VDB deployed but not active
                                  Danah Warren Newbie

                                  You guys are awesome.

                                   

                                  Mark,

                                   

                                  Yes, my local Teiid server says 'JBAS018559: Deployed "baseball-vdb.xml" ' and here it is:

                                   

                                  <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

                                  <vdb name="Baseball" version="1">

                                   

                                      <description>Baseball Archive</description>

                                   

                                      <!--

                                        Setting to use connector supplied metadata. Can be "true" or "cached".

                                        "true" will obtain metadata once for every launch of Teiid.

                                        "cached" will save a file containing the metadata into

                                        the deploy/<vdb name>/<vdb version/META-INF directory

                                      -->

                                      <property name="UseConnectorMetadata" value="true" />

                                   

                                      <!--

                                        Each model represents a access to one or more sources.

                                        The name of the model will be used as a top level schema name

                                        for all of the metadata imported from the connector.

                                   

                                        NOTE: Multiple models, with different import settings, can be bound to

                                        the same connector binding and will be treated as the same source at

                                        runtime.

                                      -->

                                      <model name="HomeRun">

                                          <!--

                                              Each source represents a translator and data source. There are

                                              pre-defined translators, or you can create one.

                                          -->

                                          <source name="text-connector" translator-name="file" connection-jndi-name="java:/allstar-file"/>

                                      </model>

                                   

                                  </vdb>

                                   

                                  Directory structure:

                                   

                                  allstarfull file: standalone > deployments > baseball > data > allstarfull.csv

                                  VDB xml file: standalone > deployments > baseball

                                   

                                  ------------------------------------------------------------------

                                   

                                  Steven, I'm trying your idea right now.

                                   

                                  Thanks.

                                  • 14. Re: VDB deployed but not active
                                    Danah Warren Newbie

                                    OMG! I'm so happy!

                                     

                                    Finally, I just ran it. The metadata loaded, it was deployed and now set to ACTIVE!

                                     

                                    Now I'm back in Eclipse, and I have more errors, but different ones. Im using the following SQL command:

                                     

                                    SQL string: "select stock.* from (call HomeRun.getTextFiles('*.csv')) f, TEXTTABLE(f.file COLUMNS playerID string, yearID long HEADER) stock";

                                     

                                    Error: TEIID30504 text-connector: File not found *.csv

                                     

                                    Is my file located in the wrong place?

                                     

                                    I'm debugging now =)