8:39 a.m.
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:41 a.m.
New subject: [JBoss JIRA] Updated: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g
[
https://issues.jboss.org/browse/TEIID-1559?page=com.atlassian.jira.plugin...
]
Boris Belovic updated TEIID-1559:
---------------------------------
Attachment: mytext-ds.xml
myvdb-vdb.xml
oracle-ds.xml
Attaching VDB file and both datasources.
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:53 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g
[
https://issues.jboss.org/browse/TEIID-1559?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-1559:
------------------------------------
Change the -vdb.xml setting: <property name="importer.useFullSchemaName"
value="false"/>
to "true".
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:05 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g
[
https://issues.jboss.org/browse/TEIID-1559?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-1559:
------------------------------------
The database doesn't contain any tables, its empty. But Teiid doesn't seem to
stop or throw an exception indicating that it can't load the metadata. Logging was
turned up to DEBUG and TRACE and neither produced any additional information. The only
message that is seen is: VDB "myvdb-1" - "Employees" model metadata
is currently being loaded. Start Time: 4/19/11 9:48 AM.
Need some indication that Teiid is done and can't load metadata.
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:12 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g
[
https://issues.jboss.org/browse/TEIID-1559?page=com.atlassian.jira.plugin...
]
Van Halbert edited comment on TEIID-1559 at 4/19/11 11:12 AM:
--------------------------------------------------------------
Change that. It took a long time for squirrel to come back and finally load the
metadata. I'm watching the admin console and the server log to see if Teiid
eventually loads the metadata.
was (Author: van.halbert):
Change that. I took a long time for squirrel to come back and finally load the
metadata. I'm watching the admin console and the server log to see if Teiid
eventually loads the metadata.
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:12 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g
[
https://issues.jboss.org/browse/TEIID-1559?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-1559:
------------------------------------
Change that. I took a long time for squirrel to come back and finally load the metadata.
I'm watching the admin console and the server log to see if Teiid eventually loads
the metadata.
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:14 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g
[
https://issues.jboss.org/browse/TEIID-1559?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1559:
---------------------------------------
I don't understand your last comment. The exception above indicates a duplicate table
name, but you're saying the database is empty? You also will get a message if you
fail to load. It looks like we could be skipping showing a message in the case when we
have finished successfully loading the metadata for a single source, but there are
additional errors/sources that prevent us from being in a valid state.
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:22 a.m.
New subject: [JBoss JIRA] Updated: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g
[
https://issues.jboss.org/browse/TEIID-1559?page=com.atlassian.jira.plugin...
]
Van Halbert updated TEIID-1559:
-------------------------------
Comment: was deleted
(was: The database doesn't contain any tables, its empty. But Teiid doesn't seem
to stop or throw an exception indicating that it can't load the metadata. Logging
was turned up to DEBUG and TRACE and neither produced any additional information. The
only message that is seen is: VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 9:48 AM.
Need some indication that Teiid is done and can't load metadata.)
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:24 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g
[
https://issues.jboss.org/browse/TEIID-1559?page=com.atlassian.jira.plugin...
]
Van Halbert edited comment on TEIID-1559 at 4/19/11 11:23 AM:
--------------------------------------------------------------
It took a long time for squirrel to come back and finally load the metadata. I'm
watching the admin console and the server log to see if Teiid eventually loads the
metadata.
When the -vdb.xml was not set to use fully qualified name, teiid was able to fail
immediately upon finding a duplicate. However, when usefullyqualfiedname was set to true,
reading the metadata is taking a real long time.
was (Author: van.halbert):
Change that. It took a long time for squirrel to come back and finally load the
metadata. I'm watching the admin console and the server log to see if Teiid
eventually loads the metadata.
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:16 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g
[
https://issues.jboss.org/browse/TEIID-1559?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-1559:
------------------------------------
Since the last log entry: 2011-04-19 09:51:49,935 INFO
there has been no change in the vdb status. Checking the admin console, the vdb is still
in the inactive state with the same error message.
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:45 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g
[
https://issues.jboss.org/browse/TEIID-1559?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-1559:
------------------------------------
No luck, the vdb never became active. So I assume it never finished loading the
metadata.
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:14 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g
[
https://issues.jboss.org/browse/TEIID-1559?page=com.atlassian.jira.plugin...
]
Boris Belovic commented on TEIID-1559:
--------------------------------------
Just to sum up what my case is doing:
1. start SOA-P server
2. create Employees table in DB and insert 4 Employee object into DB (this is done through
Hibernate)
3. deploy WAR file, ESB file and dynamic VDB
4. query VDB
5. undeploy everything and delete table from database.
6. stop SOA-P server
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:02 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g
[
https://issues.jboss.org/browse/TEIID-1559?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1559:
---------------------------------------
Why are there no restrictions on what is being imported? Given this is Oracle, all of the
database metadata is likely being retrieved.
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:28 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g
[
https://issues.jboss.org/browse/TEIID-1559?page=com.atlassian.jira.plugin...
]
Boris Belovic commented on TEIID-1559:
--------------------------------------
OK, so is this some configuration issue? Like I set some property to improper value? Or is
this an issue within Teiid?
What restrictions should be set for this issue to disappear? I built my use case upon
Portfolio example and run it against all databases supported by SOA-P 5.1 and I see this
issue only on Oracle 11g R2.
Anyway, were you able to reproduce the problem?
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:24 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g
[
https://issues.jboss.org/browse/TEIID-1559?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1559:
---------------------------------------
There are several issues here:
1. the initial import was erroring due to a duplicate table being created in Teiid.
The resolution is to use the full schema name.
2. the import from oracle appears to never return.
As the reference warns, the default importer settings crawl all available metadata. So
one resolution is to limit what you are importing, see the reference for
importer.schemaPattern
The other question would be, suppose we do want to import all of the metadata, is it
taking too long? That could be harder to determine. The import code is rather
straightforward. We are just asking DatabaseMetadata for tables/columns limited by the
given patterns. I would have you try the first option - limit the metadata your importing
and see if you get an appropriate load time.
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:53 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g
[
https://issues.jboss.org/browse/TEIID-1559?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1559:
---------------------------------------
Any update on this issue?
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:22 a.m.
New subject: [JBoss JIRA] Resolved: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g
[
https://issues.jboss.org/browse/TEIID-1559?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1559.
-----------------------------------
Resolution: Incomplete Description
There was no update on the load time if the metadata retrieved was limited.
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:37 a.m.
New subject: [JBoss JIRA] Closed: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g
[
https://issues.jboss.org/browse/TEIID-1559?page=com.atlassian.jira.plugin...
]
Steven Hawkins closed TEIID-1559.
---------------------------------
Dynamic VDB deployed in inactive state on Oracle11g
---------------------------------------------------
Key: TEIID-1559
URL: https://issues.jboss.org/browse/TEIID-1559
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: Oracle 11g R2, driver version: 11.2.0.1.0
Teiid 7.1.1 in SOA-P 5.1
Reporter: Boris Belovic
Assignee: Steven Hawkins
Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g
R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself.
But the VDB remains in inactive state, despite all datasources referred by this VDB are in
place (= deployed correctly). Few seconds after deployment of VDB I got this exception
from the server.
08:42:24,335 INFO [RUNTIME] VDB "myvdb-1" - "Employees" model
metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
08:42:24,355 INFO [PROCESSOR] Clearing prepared plan cache
08:42:24,358 INFO [RUNTIME] VDB
"myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS],
TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
08:42:50,307 WARN [RunnableTaskWrapper] Unhandled throwable for runnable:
org.teiid.deployers.VDBDeployer$1@13bf30c
java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
at org.teiid.metadata.Schema.addTable(Schema.java:42)
at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
at
org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
at
org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
at
org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed
without any problems or exceptions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4891
days inactive
5011
days old
17 comments
3 participants
participants (3)
-
Boris Belovic (JIRA) -
Steven Hawkins (JIRA)
-
Van Halbert (JIRA)