-
1. Re: Error deploying the VDB with the Text File DataSource
rareddy Jul 5, 2013 9:43 AM (in response to aswathkhan)No need to post multiple duplicate discussions, https://community.jboss.org/message/826581#826581
You need to find the root cause as to why the rar file is not deploying, there must have been an error in the JBoss startup console window or in the log file as to why the RAR file failed to deploy.
-
2. Re: Error deploying the VDB with the Text File DataSource
aswathkhan Jul 8, 2013 6:21 AM (in response to rareddy)Ramesh, This is not the duplicate discussion. This error is on another instance.
Sorry for the type above. I'm using Teiid Server 8.3 not 8.1
I'm using the folloiwng
-JBoss AS 7.1.1 Final
- Teiid Server 8.3 jboss dist
- Teiid Designer 8.2 Alpha1
- Eclipse Juno Win32
- JBoss Tools 4.0.0
When I create the VDB, it does gets created but it throws the following errors whenever the a query is executed.
I get the following error, whenever I query the text file vdb.
Starting run
SELECT * FROM "NEW_view"."New"
org.teiid.jdbc.TeiidSQLException: TEIID30504 New_Source: TEIID30481 Failed to find the Connection Factory with JNDI name New_Source. Please check the name or deploy the Connection Factory with specified name.Note: Screen shots attached for your reference
-
Text file VDB error.docx 281.0 KB
-
-
3. Re: Error deploying the VDB with the Text File DataSource
rareddy Jul 8, 2013 9:12 AM (in response to aswathkhan)Aswath,
You need to check the server log and see why the data source is not being created. Most of the team this is due to typo in the userid/password you used to create the data source. You can check the "standalone-teiid.xml" file under "resource-adapters" section as to what you have entered on the JBoss AS server. Fix, restart the server.
Ramesh..
-
4. Re: Error deploying the VDB with the Text File DataSource
aswathkhan Jul 10, 2013 7:32 AM (in response to rareddy)It worked for me now.
I did see no issue with the resource-adapters' section of standalone-teiid.xml file.
All I did was, I undeployed the VDB and restarted the server and redeployed it , it is working fine.
Thanks anyway Ramesh