April 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4150) Infinispan dsl resource-adapter has not valid module.xml

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4150?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4150: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1328436 Bugzilla Update: Perform > Infinispan dsl resource-adapter has not valid module.xml > -------------------------------------------------------- > > Key: TEIID-4150 > URL: https://issues.jboss.org/browse/TEIID-4150 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Jan Stastny > Assignee: Steven Hawkins > > There is a problem in mentioned module when server attempts to load it: > {code:plain} > [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=infinispandsl:add(module=org.jboss.teiid.resource-adapter.infinispan.dsl) > { > "outcome" => "failed", > "failure-description" => "JBAS010473: Failed to load module for RA [org.jboss.teiid.resource-adapter.infinispan.dsl]", > "rolled-back" => true > } > {code} > It is not valid module according to the 'urn:jboss:module:1.1' schema. > Problematic fragment: > {code:xml} > <dependencies> > ... > <module name="org.infinispan.query" slot="jdg-6.6" optional="true" export="true" services="true" /> > ... > </dependencies> > {code} > According to the mentioned schema the attribute 'services' can have only values: > * none > * import > * export > This issue prevents a user from using the adapter. > Furthermore I am not sure that name 'org.infinispan.query' of the dependency module is correct. I haven't found such module in jdg client libs, there are two possible candidates though: > * org.infinispan.query.dsl > * org.infinispan.query.remote.client -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4150) Infinispan dsl resource-adapter has not valid module.xml

by Jan Stastny (JIRA)

Jan Stastny created TEIID-4150: ---------------------------------- Summary: Infinispan dsl resource-adapter has not valid module.xml Key: TEIID-4150 URL: https://issues.jboss.org/browse/TEIID-4150 Project: Teiid Issue Type: Bug Components: Misc. Connectors Reporter: Jan Stastny Assignee: Steven Hawkins There is a problem in mentioned module when server attempts to load it: {code:plain} [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=infinispandsl:add(module=org.jboss.teiid.resource-adapter.infinispan.dsl) { "outcome" => "failed", "failure-description" => "JBAS010473: Failed to load module for RA [org.jboss.teiid.resource-adapter.infinispan.dsl]", "rolled-back" => true } {code} It is not valid module according to the 'urn:jboss:module:1.1' schema. Problematic fragment: {code:xml} <dependencies> ... <module name="org.infinispan.query" slot="jdg-6.6" optional="true" export="true" services="true" /> ... </dependencies> {code} According to the mentioned schema the attribute 'services' can have only values: * none * import * export This issue prevents a user from using the adapter. Furthermore I am not sure that name 'org.infinispan.query' of the dependency module is correct. I haven't found such module in jdg client libs, there are two possible candidates though: * org.infinispan.query.dsl * org.infinispan.query.remote.client -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4143) Wrong Content-Type in error response from odata

by Anu Saji (JIRA)

[ https://issues.jboss.org/browse/TEIID-4143?page=com.atlassian.jira.plugin... ] Anu Saji reassigned TEIID-4143: ------------------------------- Assignee: Ramesh Reddy (was: Anu Saji) > Wrong Content-Type in error response from odata > ----------------------------------------------- > > Key: TEIID-4143 > URL: https://issues.jboss.org/browse/TEIID-4143 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.x > Reporter: Andrej Šmigala > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 8.12.5 > > > When submitting an odata request that causes an error on server side, the response has the Content-Type header set to just "application", which causes clients to fail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4143) Wrong Content-Type in error response from odata

by Anu Saji (JIRA)

[ https://issues.jboss.org/browse/TEIID-4143?page=com.atlassian.jira.plugin... ] Work on TEIID-4143 started by Anu Saji. --------------------------------------- > Wrong Content-Type in error response from odata > ----------------------------------------------- > > Key: TEIID-4143 > URL: https://issues.jboss.org/browse/TEIID-4143 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.x > Reporter: Andrej Šmigala > Assignee: Anu Saji > Priority: Blocker > Fix For: 8.12.5 > > > When submitting an odata request that causes an error on server side, the response has the Content-Type header set to just "application", which causes clients to fail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4143) Wrong Content-Type in error response from odata

by Anu Saji (JIRA)

[ https://issues.jboss.org/browse/TEIID-4143?page=com.atlassian.jira.plugin... ] Work on TEIID-4143 stopped by Anu Saji. --------------------------------------- > Wrong Content-Type in error response from odata > ----------------------------------------------- > > Key: TEIID-4143 > URL: https://issues.jboss.org/browse/TEIID-4143 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.x > Reporter: Andrej Šmigala > Assignee: Anu Saji > Priority: Blocker > Fix For: 8.12.5 > > > When submitting an odata request that causes an error on server side, the response has the Content-Type header set to just "application", which causes clients to fail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4139) Session/Connection to VDB gets closed after 2 minutes of innactivity

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4139?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4139: --------------------------------------- Thanks for following up Jorge. Is there anything that needs to be captured here for the project or product? > Session/Connection to VDB gets closed after 2 minutes of innactivity > -------------------------------------------------------------------- > > Key: TEIID-4139 > URL: https://issues.jboss.org/browse/TEIID-4139 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1 > Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA > JBoss Data Virtualization 6.1.0.ER4 > Reporter: Jorge Herrera > Assignee: Steven Hawkins > Attachments: jdv-jdbc-config.txt, server.log > > > When setting up a VDB connecting (using jdbc over ssl) to either another VDB in the same server or directly to a RDBMS (Amazon Redshift in this case), if you execute queries one after the other the server works as expected. But if you let the session idle, or just looking at the result set for more than 2 minutes, session gets disconnected with the following message: > _______________________________________________ > DBCException: SQL Error [08S01]: org.teiid.net.socket.SingleInstanceCommunicationException > SQL Error [08S01]: org.teiid.net.socket.SingleInstanceCommunicationException > TeiidSQLException: org.teiid.net.socket.SingleInstanceCommunicationException > org.teiid.net.socket.SingleInstanceCommunicationException > SingleInstanceCommunicationException > org.teiid.net.socket.SingleInstanceCommunicationException > EOFException > java.io.EOFException > _______________________________________________ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4139) Session/Connection to VDB gets closed after 2 minutes of innactivity

by Jorge Herrera (JIRA)

[ https://issues.jboss.org/browse/TEIID-4139?page=com.atlassian.jira.plugin... ] Jorge Herrera closed TEIID-4139. -------------------------------- Release Notes Text: Problem is not with Jboss but with load balancer Resolution: Rejected Problem is not with Jboss but with load balancer > Session/Connection to VDB gets closed after 2 minutes of innactivity > -------------------------------------------------------------------- > > Key: TEIID-4139 > URL: https://issues.jboss.org/browse/TEIID-4139 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1 > Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA > JBoss Data Virtualization 6.1.0.ER4 > Reporter: Jorge Herrera > Assignee: Steven Hawkins > Attachments: jdv-jdbc-config.txt, server.log > > > When setting up a VDB connecting (using jdbc over ssl) to either another VDB in the same server or directly to a RDBMS (Amazon Redshift in this case), if you execute queries one after the other the server works as expected. But if you let the session idle, or just looking at the result set for more than 2 minutes, session gets disconnected with the following message: > _______________________________________________ > DBCException: SQL Error [08S01]: org.teiid.net.socket.SingleInstanceCommunicationException > SQL Error [08S01]: org.teiid.net.socket.SingleInstanceCommunicationException > TeiidSQLException: org.teiid.net.socket.SingleInstanceCommunicationException > org.teiid.net.socket.SingleInstanceCommunicationException > SingleInstanceCommunicationException > org.teiid.net.socket.SingleInstanceCommunicationException > EOFException > java.io.EOFException > _______________________________________________ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3462) Add support for semantic versioning of VDBs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3462?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3462: --------------------------------------- After looking at the changes for rest, I'm uneasy with the current state of things. It does seem to be a better option to just go ahead and introduce a breaking change so that the version field can be a string rather than an int. This would introduce a minor breaking change into: CommandLogMessage VDB Session EventListener VDBImport ExecutionContext Duplicate methods on: EventDistributor MetadataRepository Admin AdminShell could just accept Object for the version, rather than adding methods. Additionally materialization status tables would need the vdbversion column changed to string. This is much more logically consistent with the original intent of having the version field. > Add support for semantic versioning of VDBs > ------------------------------------------- > > Key: TEIID-3462 > URL: https://issues.jboss.org/browse/TEIID-3462 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.7 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 9.0 > > > Semantic versioning [1] should be supported in the VDB versioning in order to be able to easier determine whether there are breaking changes from the client perspective and to more easily establish a link between client software versions and the VDBs they rely upon. > [1] http://semver.org/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4146) Using JDG Library Mode, unable to perform insert (

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4146?page=com.atlassian.jira.plugin... ] Work on TEIID-4146 started by Van Halbert. ------------------------------------------ > Using JDG Library Mode, unable to perform insert ( > -------------------------------------------------- > > Key: TEIID-4146 > URL: https://issues.jboss.org/browse/TEIID-4146 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.5 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > > Trying to run the JDG local cache quickstart, get the following error when trying to perform an insert: > 15:09:34,027 WARN [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue12) TEIID30020 Processing exception for request O25SlCY41bD5.6 'TEIID30492 Element StockCache.Stock.StockObject of StockCache.Stock is neither nullable nor has a default value. A value must be specified in the insert.'. Originally QueryValidatorException Request.java:330. Enable more detailed logging to see the entire stacktrace. > The issue is because the StockObject column is set to be NullType.unknown, instead of NullType.Nullable. This is because the metadata processor in the translator-object is setting it incorrectly. > Workaround: > - Using Teiid Designer to import the source model and change the null type. > - use dynamic vdb and define the DDL metadata to set the null type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4148) Add "org.modeshape.jdbc" dependency to teiid jdbc translator module

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4148?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4148: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1315397 Bugzilla Update: Perform > Add "org.modeshape.jdbc" dependency to teiid jdbc translator module > ------------------------------------------------------------------- > > Key: TEIID-4148 > URL: https://issues.jboss.org/browse/TEIID-4148 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.5 > Reporter: Van Halbert > Assignee: Van Halbert > > the "org.jboss.teiid.translator.jdbc" module (where the query originates from) has to list "org.modeshape.jdbc" as a dependency so that ModeShape's CP can be accessible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2016