[JBoss JIRA] Created: (TEIID-1317) Limit keyword causes class cast exception running query against DB2 translator
by Howard Abrams (JIRA)
Limit keyword causes class cast exception running query against DB2 translator
------------------------------------------------------------------------------
Key: TEIID-1317
URL: https://jira.jboss.org/browse/TEIID-1317
Project: Teiid
Issue Type: Bug
Affects Versions: 7.1, 7.0, 6.2.0
Reporter: Howard Abrams
Assignee: Steven Hawkins
When running a query that uses the limit keyword against a DB2 database/translator, teiid will throw the exception below (From the 7.1 codebase, but I got the same exception a while back playing with 7.0 as well as 6.2). The same query against the same schema in a different database (H2 for example) works fine. It appears it also works fin on DB2 if you leave off the starting rowing from the expression.
Examples:
/*works on H2*/
SELECT * FROM MYSCHEMA.FOO LIMIT 0,10
/*fails on DB2*/
SELECT * FROM MYSCHEMA.FOO LIMIT 0,10
/*fails on DB2*/
SELECT * FROM MYSCHEMA.FOO LIMIT 10,10
/*works on DB2*/
SELECT * FROM MYSCHEMA.FOO LIMIT 10
java.lang.ClassCastException: org.teiid.language.Function cannot be cast to org.teiid.language.Literal
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:719)
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:211)
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:130)
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:215)
at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:181)
at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:53)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:89)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:86)
at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:107)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:116)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:290)
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:637)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (TEIID-1321) Error message when connecting to missing VDB is misleading (makes it sound like it exists)
by Paul Nittel (JIRA)
Error message when connecting to missing VDB is misleading (makes it sound like it exists)
------------------------------------------------------------------------------------------
Key: TEIID-1321
URL: https://jira.jboss.org/browse/TEIID-1321
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Affects Versions: 7.1.1
Environment: Fedora 12, SOA-P ER3
Reporter: Paul Nittel
Assignee: Steven Hawkins
Fix For: 7.1.1
I was using the simpleclient to query an XML document model, but misspelled the name of the VDB. The error I received was that the subject VDB was not active. Actually, it didn't exist and that distinction could have saved me a bunch of time trying to figure out why it appeared to be active, but wasn't. Here's an example (this VDB does not exist):
./run.sh localhost 31000 barfingToad "select * from booksdoc.booksetmixeddocument"
Executing using the TeiidDriver
Oct 25, 2010 12:45:07 PM org.teiid.jdbc.SocketProfile connect
SEVERE: Could not create connection
[ConnectionException]Remote org.teiid.client.security.LogonException: VDB "barfingToad" version "latest" is not in "active" status.
1 [LogonException]Remote org.teiid.client.security.LogonException: VDB "barfingToad" version "latest" is not in "active" status.
2 [TeiidSecurityException]Remote org.teiid.dqp.service.SessionServiceException: VDB "barfingToad" version "latest" is not in "active" status.
at org.teiid.net.socket.SocketServerConnection.selectServerInstance(SocketServerConnection.java:143)
at org.teiid.net.socket.SocketServerConnection.<init>(SocketServerConnection.java:94)
at org.teiid.net.socket.SocketServerConnectionFactory.getConnection(SocketServerConnectionFactory.java:310)
at org.teiid.jdbc.SocketProfile.createConnection(SocketProfile.java:104)
at org.teiid.jdbc.SocketProfile.connect(SocketProfile.java:88)
at org.teiid.jdbc.TeiidDriver.connect(TeiidDriver.java:87)
at java.sql.DriverManager.getConnection(DriverManager.java:620)
at java.sql.DriverManager.getConnection(DriverManager.java:200)
at JDBCClient.getDriverConnection(JDBCClient.java:53)
at JDBCClient.main(JDBCClient.java:41)
Caused by: [LogonException]Remote org.teiid.client.security.LogonException: VDB "barfingToad" version "latest" is not in "active" status.
1 [TeiidSecurityException]Remote org.teiid.dqp.service.SessionServiceException: VDB "barfingToad" version "latest" is not in "active" status.
at org.teiid.transport.LogonImpl.logon(LogonImpl.java:84)
at sun.reflect.GeneratedMethodAccessor1087.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.teiid.transport.ServerWorkItem.run(ServerWorkItem.java:81)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:189)
at org.teiid.transport.SocketClientInstance.processMessagePacket(SocketClientInstance.java:160)
at org.teiid.transport.SocketClientInstance.receivedMessage(SocketClientInstance.java:149)
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:545)
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754)
at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:144)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545)
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754)
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:545)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:540)
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:349)
at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:281)
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:201)
at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
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:619)
Caused by: [TeiidSecurityException]Remote org.teiid.dqp.service.SessionServiceException: VDB "barfingToad" version "latest" is not in "active" status.
at org.teiid.services.SessionServiceImpl.getActiveVDB(SessionServiceImpl.java:225)
at org.teiid.services.SessionServiceImpl.createSession(SessionServiceImpl.java:157)
at org.teiid.transport.LogonImpl.logon(LogonImpl.java:75)
... 31 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (TEIID-1315) Teiid misinterprets relative location of XSD when doc model is in different folder: causes Unknown Query Metadata error
by Paul Nittel (JIRA)
Teiid misinterprets relative location of XSD when doc model is in different folder: causes Unknown Query Metadata error
-----------------------------------------------------------------------------------------------------------------------
Key: TEIID-1315
URL: https://jira.jboss.org/browse/TEIID-1315
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.1.1
Environment: SOA-P ER3, JBDS 4.0.0 Beta 1
Reporter: Paul Nittel
Assignee: Steven Hawkins
Fix For: 7.1.1
I executed E2eAudioBooksVdbExecutionTestScript_Teiid7 and found I could not query the BookSetMixed document. I received an exception which referred to "Unknown Query Metadata". The test calls for refactoring the models into various folders and the XML doc model winds up in <proj>/View/XMLDocuments. The XML Schemas are in <proj>/Source/XMLSchemas. In the VDB's index file for the XML document model, the path to the XSD is, for example: ../../Source/XmlSchemas/BookDatatypes.xsd. The query engine is not treating this as a file system, however, and is unable to locate the XSD.
We refactored the XML document into the same fodler as the XSDs and the query then worked.
I'll attach some artifacts.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (TEIID-1276) Updating an existing VDB via copy-paste in the filesystem causes ConcurrentModificationException
by John Doyle (JIRA)
Updating an existing VDB via copy-paste in the filesystem causes ConcurrentModificationException
------------------------------------------------------------------------------------------------
Key: TEIID-1276
URL: https://jira.jboss.org/browse/TEIID-1276
Project: Teiid
Issue Type: Bug
Affects Versions: 7.1.1
Reporter: John Doyle
Assignee: Steven Hawkins
If you have a vdb deployed in Teiid and deploy an updated version by pasting the VDB into the deploy directory, a ConcurrentModificationException is thrown. It appears that the original is undeployed, but the new one is not deployed. You cannot connect to the VDB after the exception.
11:51:12,223 INFO [RUNTIME] VDB "Lobs.1[OracleClobs[OracleClobs/oracle/OracleClobs]]" undeployed.
11:51:12,615 INFO [PROCESSOR] Clearing prepared plan cache
11:51:12,616 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/NotBackedUp/jdoyle/Teiid_955/jboss-5.1.0.GA/server/default/deploy/Lobs.vdb/ state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/NotBackedUp/jdoyle/Teiid_955/jboss-5.1.0.GA/server/default/deploy/Lobs.vdb/
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:362)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
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:619)
Caused by: java.util.ConcurrentModificationException
at java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:373)
at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:384)
at org.teiid.dqp.internal.process.SessionAwareCache.clearCache(SessionAwareCache.java:185)
at org.teiid.dqp.internal.process.SessionAwareCache.clearForVDB(SessionAwareCache.java:179)
at org.teiid.dqp.internal.process.DQPCore.clearPlanCache(DQPCore.java:560)
at org.teiid.dqp.internal.process.DQPCore.clearCache(DQPCore.java:612)
at org.teiid.jboss.deployers.RuntimeEngineDeployer$1.added(RuntimeEngineDeployer.java:214)
at org.teiid.deployers.VDBRepository.notifyAdd(VDBRepository.java:225)
at org.teiid.deployers.VDBRepository.addVDB(VDBRepository.java:84)
at org.teiid.deployers.VDBDeployer.deploy(VDBDeployer.java:145)
at org.teiid.deployers.VDBDeployer.deploy(VDBDeployer.java:60)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
... 24 more
11:51:12,619 WARN [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS IN ERROR: Name -> Error
vfszip:/NotBackedUp/jdoyle/Teiid_955/jboss-5.1.0.GA/server/default/deploy/Lobs.vdb/ -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/NotBackedUp/jdoyle/Teiid_955/jboss-5.1.0.GA/server/default/deploy/Lobs.vdb/
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/NotBackedUp/jdoyle/Teiid_955/jboss-5.1.0.GA/server/default/deploy/Lobs.vdb/" is in error due to the following reason(s): java.util.ConcurrentModificationException
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:369)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
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:619)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months