September 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3138) EmbeddedServer does not shutdown the session monitor

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3138: ------------------------------------- Summary: EmbeddedServer does not shutdown the session monitor Key: TEIID-3138 URL: https://issues.jboss.org/browse/TEIID-3138 Project: Teiid Issue Type: Bug Components: Embedded Affects Versions: 8.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7 The session service has a timer thread which should be shutdown when the embedded server is shutdown. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2848) MongoDB: Provide Array support

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2848?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2848. --------------------------------- Labels: Beta2 (was: CR1) Resolution: Done Fixed the error, fix will be in 8.9 Beta2 > MongoDB: Provide Array support > ------------------------------- > > Key: TEIID-2848 > URL: https://issues.jboss.org/browse/TEIID-2848 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta2 > Fix For: 8.7.1, 8.8 > > > Provide array support for primitive data types in MongoDB translator. The arrays are supported but as embedded documents in the one-2-many situation. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2911) Guard against external entity resolving

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2911?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2911: ------------------------------------------------ Chess Hazlett <chazlett(a)redhat.com> changed the Status of [bug 1085554|https://bugzilla.redhat.com/show_bug.cgi?id=1085554] from NEW to CLOSED > Guard against external entity resolving > --------------------------------------- > > Key: TEIID-2911 > URL: https://issues.jboss.org/browse/TEIID-2911 > Project: Teiid > Issue Type: Bug > Components: OData, Query Engine > Affects Versions: 7.7, 8.4 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7, 8.4.3 > > Attachments: org.odata4j.stax2.staximpl.StaxXMLFactoryProvider2.diff > > > if applications that expose RESTEasy XML endpoints, add the following snippet to their web.xml file to disable entity expansion in RESTEasy: > <context-param> > <param-name>resteasy.document.expand.entity.references</param-name> > <param-value>false</param-value> > </context-param> > Note that this <context-param> setting has precedence over <init-param>, and will override a contrary setting in an <init-param> element. > However this is not sufficient for OData as OData4j is responsible for parsing the Atom feed. StaxXMLFactoryProvider2 simply creates XMLInputFactories without any options, thus they will perform external entity resolving by default. An issue will need to be opened against OData4j. > For SQL/XML, the XMLType input factory needs to disable external entity resolving (via experimentation just setting the relevant property doesn't always work, so like other projects we'll set an XMLResolver, which does work). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3070) Netty worker threads cause system high cpu

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3070?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3070: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1134393, https://bugzilla.redhat.com/show_bug.cgi?id=1141826, https://bugzilla.redhat.com/show_bug.cgi?id=1145789 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1134393, https://bugzilla.redhat.com/show_bug.cgi?id=1141826) > Netty worker threads cause system high cpu > ------------------------------------------ > > Key: TEIID-3070 > URL: https://issues.jboss.org/browse/TEIID-3070 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7 > Environment: JDV 6.1.0.DR2 > JDV 6.0 > Reporter: Kylin Soong > Assignee: Kylin Soong > > I have hit this issue many times in deploying a VDB to JDV, All CPU be used by netty worker threads: > ~~~ > "New I/O worker #3" daemon prio=10 tid=0x00007fc71c0d2000 nid=0x320b runnable [0x00007fc7074f3000] > java.lang.Thread.State: RUNNABLE > at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) > at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269) > at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:79) > at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:87) > - locked <0x00000000c42b4318> (a sun.nio.ch.Util$2) > - locked <0x00000000c42b4328> (a java.util.Collections$UnmodifiableSet) > - locked <0x00000000c42b42d0> (a sun.nio.ch.EPollSelectorImpl) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:98) > at org.jboss.netty.channel.socket.nio.SelectorUtil.select(SelectorUtil.java:64) > ~~~ > Seems this is a exist netty issue, search "jboss netty high cpu" via google we can get lots of result. > Below link have detailed depiction about this issue; > https://github.com/kylinsoong/teiid-samples/tree/master/highcpu -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3137) Change infinispan-cache translator to support JDG 6 and no longer support pre 6.0 infinispan

by Van Halbert (JIRA)

Van Halbert created TEIID-3137: ---------------------------------- Summary: Change infinispan-cache translator to support JDG 6 and no longer support pre 6.0 infinispan Key: TEIID-3137 URL: https://issues.jboss.org/browse/TEIID-3137 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 8.7.1, 8.9 Reporter: Van Halbert Assignee: Steven Hawkins Change the infinispan-cache translator to support JDG 6 using library mode. Also, remove support for infinispan v.5. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3137) Change infinispan-cache translator to support JDG 6 and no longer support pre 6.0 infinispan

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3137?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-3137: ---------------------------------- Assignee: Van Halbert (was: Steven Hawkins) > Change infinispan-cache translator to support JDG 6 and no longer support pre 6.0 infinispan > -------------------------------------------------------------------------------------------- > > Key: TEIID-3137 > URL: https://issues.jboss.org/browse/TEIID-3137 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > Change the infinispan-cache translator to support JDG 6 using library mode. Also, remove support for infinispan v.5. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3137) Change infinispan-cache translator to support JDG 6 and no longer support pre 6.0 infinispan

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3137?page=com.atlassian.jira.plugin... ] Work on TEIID-3137 started by Van Halbert. ------------------------------------------ > Change infinispan-cache translator to support JDG 6 and no longer support pre 6.0 infinispan > -------------------------------------------------------------------------------------------- > > Key: TEIID-3137 > URL: https://issues.jboss.org/browse/TEIID-3137 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > Change the infinispan-cache translator to support JDG 6 using library mode. Also, remove support for infinispan v.5. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3134) Impala sorting Issue

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3134?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3134: --------------------------------------- Any update on this? > Impala sorting Issue > -------------------- > > Key: TEIID-3134 > URL: https://issues.jboss.org/browse/TEIID-3134 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > > String sorting of impala is inconsistent with our expectations: > Impala sorting > --------------------------- > SELECT BQT1.SmallA.StringNum FROM BQT1.SmallA > Results > 1: -1 > 2: -10 > 3: -11 > 4: -12 > 5: -13 > 6: -14 > 7: -15 > 8: -16 > 9: -17 > 10: -18 > 11: -19 > 12: -2 > 13: -20 > 14: -21 > 15: -22 > 16: -24 > 17: -3 > 18: -4 > 19: -5 > 20: -6 > 21: -8 > 22: -9 > 23: 0 > 24: 1 > 25: 10 > 26: 11 > 27: 12 > 28: 13 > 29: 14 > 30: 15 > 31: 16 > 32: 17 > 33: 18 > 34: 19 > 35: 2 > 36: 20 > 37: 21 > 38: 22 > 39: 23 > 40: 24 > 41: 3 > 42: 4 > 43: 5 > 44: 6 > 45: 7 > 46: 8 > 47: null > 48: null > 49: null > 50: null > Expected > --------------------------- > While we expect sorting to be consistent with other sources: > 1: 0 > 2: 1 > 3: -1 > 4: 10 > 5: -10 > 6: 11 > 7: -11 > 8: 12 > 9: -12 > 10: 13 > 11: -13 > 12: 14 > 13: -14 > 14: 15 > 15: -15 > 16: 16 > 17: -16 > 18: 17 > 19: -17 > 20: 18 > 21: -18 > 22: 19 > 23: -19 > 24: 2 > 25: -2 > 26: 20 > 27: -20 > 28: 21 > 29: -21 > 30: 22 > 31: -22 > 32: 23 > 33: 24 > 34: -24 > 35: 3 > 36: -3 > 37: 4 > 38: -4 > 39: 5 > 40: -5 > 41: 6 > 42: -6 > 43: 7 > 44: 8 > 45: -8 > 46: -9 > 47: null > 48: null > 49: null > 50: null -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2831) Add a full ddl example to the ldap translator docs

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-2831?page=com.atlassian.jira.plugin... ] Kylin Soong updated TEIID-2831: ------------------------------- Forum Reference: https://developer.jboss.org/message/742528, https://developer.jboss.org/thread/227937 (was: https://developer.jboss.org/message/742528) > Add a full ddl example to the ldap translator docs > -------------------------------------------------- > > Key: TEIID-2831 > URL: https://issues.jboss.org/browse/TEIID-2831 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Steven Hawkins > Assignee: Kylin Soong > > It would be helpful to have a full example of LDAP metadata. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3136) Possible threading issues with index metadata loading

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3136: ------------------------------------- Summary: Possible threading issues with index metadata loading Key: TEIID-3136 URL: https://issues.jboss.org/browse/TEIID-3136 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.9 Index metadata can be processed by several threads such that the modifications may not be seen appropriately by other threads. This could include the materialization table not being set appropriately and model not found errors. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 September 2014