[JBoss JIRA] Created: (TEIID-857) MalformedURLException when connecting to teiid vdb.
by John Doyle (JIRA)
MalformedURLException when connecting to teiid vdb.
---------------------------------------------------
Key: TEIID-857
URL: https://jira.jboss.org/jira/browse/TEIID-857
Project: Teiid
Issue Type: Bug
Components: Embedded
Affects Versions: 6.2.0
Environment: Teiid 6.2 embedded using the filepath configuration.
Reporter: John Doyle
Assignee: Steven Hawkins
I'm not getting a log file from Teiid. I've just dropped a VDB into an unmodified 6.2 image and get the following when connecting.
log4j:ERROR Could not parse url [mmfile:/home/jdoyle/NotBackedUp/teiid-6.2.0/deploy/log4j.xml].
java.net.MalformedURLException: unknown protocol: mmfile
at java.net.URL.<init>(URL.java:574)
at java.net.URL.<init>(URL.java:464)
at java.net.URL.<init>(URL.java:413)
at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:650)
at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:186)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:225)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:180)
at org.apache.log4j.xml.DOMConfigurator$2.parse(DOMConfigurator.java:612)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:711)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618)
at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:470)
at org.apache.log4j.LogManager.<clinit>(LogManager.java:122)
at org.apache.log4j.Logger.getLogger(Logger.java:104)
at com.metamatrix.jdbc.Log4JUtil.getLogger(Log4JUtil.java:91)
at com.metamatrix.jdbc.LogConfigurationProvider$Log4JLogConfiguration.isEnabled(LogConfigurationProvider.java:74)
at com.metamatrix.common.log.LogManager.isMessageToBeRecorded(LogManager.java:358)
at com.metamatrix.common.log.LogManager.logMessage(LogManager.java:364)
at com.metamatrix.common.log.LogManager.logInfo(LogManager.java:214)
at com.metamatrix.dqp.embedded.DQPEmbeddedPlugin.logInfo(DQPEmbeddedPlugin.java:71)
at com.metamatrix.dqp.embedded.services.EmbeddedConfigurationService.initializeService(EmbeddedConfigurationService.java:975)
at com.metamatrix.dqp.embedded.services.EmbeddedBaseDQPService.initialize(EmbeddedBaseDQPService.java:60)
at org.teiid.dqp.internal.process.DQPCore.start(DQPCore.java:615)
...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (TEIID-866) AdminShell is not able to handle SELECT * INTO #TEMP FROM foo; (statement does not return a result set)
by Paul Nittel (JIRA)
AdminShell is not able to handle SELECT * INTO #TEMP FROM foo; (statement does not return a result set)
-------------------------------------------------------------------------------------------------------
Key: TEIID-866
URL: https://jira.jboss.org/jira/browse/TEIID-866
Project: Teiid
Issue Type: Bug
Components: Tools
Affects Versions: 6.2.0
Environment: Fedora 10, 6.2 Stable (GA)
Reporter: Paul Nittel
Assignee: Steven Hawkins
Here's the crux of the issue:
select * into #temp from bqt1.smalla;
// Error: // Uncaught Exception: TargetError : at Line: 165 : in file: URL: jar:file:/home/pnittel/teiid62/adminshell/lib/teiid-adminshell-6.2.0.jar!/scripts/jdbc.bsh : throw e ;
Target exception: com.metamatrix.jdbc.MMSQLException: Statement does not return a result set.
Steve H. put it this way:
"The into clause turns the statement into an insert, which does not have a result set - it only returns an update count. It does seem like AdminShell should handle that case. It's probably doing some parsing of the command and expecting it to return a resultset..."
This same statement works fine in SQL Explorer.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months