[JBoss JIRA] (TEIID-2382) File Translator Problem
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2382?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2382:
---------------------------------------
Some of the messages indicate that you are exceeding the pool max (which defaults to 10) and have timed out (30 seconds). You'll probably want to better understand what connection you are putting on the pool and any long running connection usage.
In general the default Teiid logic will not hold a file connection for any extended period of time as once the files are returned the accessnode should auto close the connectorworkitem. If you have some scenarios where you are returning lots of files, then we may be holding the connection pending the retrieval of other parts of the plan in which case the simple solution is to just increase the size of the pool.
> File Translator Problem
> -----------------------
>
> Key: TEIID-2382
> URL: https://issues.jboss.org/browse/TEIID-2382
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.1
> Environment: zOS, Windows
> Reporter: Gautam Banerjee
> Assignee: Steven Hawkins
> Attachments: server.log
>
>
> We are getting datasource exceptions with file translator. Can we define the max and min connections as in connection pool for file translator?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (TEIID-2382) File Translator Problem
by Gautam Banerjee (JIRA)
[ https://issues.jboss.org/browse/TEIID-2382?page=com.atlassian.jira.plugin... ]
Gautam Banerjee commented on TEIID-2382:
----------------------------------------
We are having intermittent problems with the file translator datasource. Please let us know why the file translator is unable to get connection from the datasource.
<errMsg>
<systemLayer>
<layer>Unknown</layer>
</systemLayer>
<messageString>An unknown error has occurred: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/CHORUS-PLATFORM-METADATA-FILE-DS</messageString>
<messageId>NOCODE</messageId>
<isOverridable>true</isOverridable>
<messageDetails>
<string>javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/CHORUS-PLATFORM-METADATA-FILE-DS</string>
</messageDetails>
<msgTemplate>
<id>NOCODE</id>
<statusCode>0</statusCode>
<actionCode>For a message definition and recommended resolution, highlight the message ID and click the question mark icon in the upper-right corner of the error dialog. The Knowledge Center will open with a link to the message definition and resolution</actionCode>
<reasonCode></reasonCode>
<messageTemplate>An unknown error has occurred: %s</messageTemplate>
<overridable>true</overridable>
<formatCode>ERROR_XML</formatCode>
</msgTemplate>
</errMsg>
Thanks
Gautam
> File Translator Problem
> -----------------------
>
> Key: TEIID-2382
> URL: https://issues.jboss.org/browse/TEIID-2382
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.1
> Environment: zOS, Windows
> Reporter: Gautam Banerjee
> Assignee: Steven Hawkins
> Attachments: server.log
>
>
> We are getting datasource exceptions with file translator. Can we define the max and min connections as in connection pool for file translator?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (TEIID-2382) File Translator Problem
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2382?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2382.
-----------------------------------
Resolution: Incomplete Description
This seems more like a forum question than an issue. Yes, you can set the pool size for the file datasource which is underneath a file translator. However file connections currently do not maintain much state so restricting their creation won't generally improve utilization. Also the log does not appear to contain Teiid specific errors.
> File Translator Problem
> -----------------------
>
> Key: TEIID-2382
> URL: https://issues.jboss.org/browse/TEIID-2382
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.1
> Environment: zOS, Windows
> Reporter: Gautam Banerjee
> Assignee: Steven Hawkins
> Attachments: server.log
>
>
> We are getting datasource exceptions with file translator. Can we define the max and min connections as in connection pool for file translator?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (TEIID-2382) File Translator Problem
by Gautam Banerjee (JIRA)
Gautam Banerjee created TEIID-2382:
--------------------------------------
Summary: File Translator Problem
Key: TEIID-2382
URL: https://issues.jboss.org/browse/TEIID-2382
Project: Teiid
Issue Type: Bug
Affects Versions: 8.1
Environment: zOS, Windows
Reporter: Gautam Banerjee
Assignee: Steven Hawkins
We are getting datasource exceptions with file translator. Can we define the max and min connections as in connection pool for file translator?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (TEIID-2381) Expanded source hint support
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2381?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2381:
---------------------------------------
Considerations for this issue include:
* expanded placement of the hint in the user query (parser changes)
* alternatively or additionally whether some sort of global hint syntax, rather than just source name, would be a better approach to indicate where a source hint is applicable.
* additional placements of the hint in the source sql (would require translator/design changes). For example to be able to push multiple hints in multiple query locations in the same pushdown query, such as one in the SELECT and one in a WITH clause/subquery.
* general definition of how multiple hints interact at different levels (in views which is currently mostly ignored)/placements in the user query.
> Expanded source hint support
> ----------------------------
>
> Key: TEIID-2381
> URL: https://issues.jboss.org/browse/TEIID-2381
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> We currently look at the source hint in only the root user query (not in subqueries nor the with clause) and only consider it in a very narrow set of circumstances when it's used in a view.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months