September 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3102) Provide a facility to restrict OData access to defined VDB

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3102?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3102. --------------------------------- Labels: Beta1 (was: ) Fix Version/s: 8.7.1 8.9 Resolution: Done Added code to allow a single vdb through "odata" WAR file. In order to control single VDB per WAR file do the following 1) Make a copy of "modules/org/jboss/teiid/main/deployments/teiid-odata-{version}.WAR 2) Add new WAR file name entry in the "deployments.properties" file in same location. 3) Edit the copied WAR file's web.xml and add "allow-vdb" property. Supply the VDB name to allow through this WAR file 4) Edit the copied WAR file's "jboss-web.xml" file, and change the context from "odata" to any other context of your choice. 5) You can also change the security-domain if you would like 6) Remove the original WAR file if you do not choose to have "odata" based context available any more. 7) Start the server Now if you issue queries like http://host:port/<your context>/$metadata > Provide a facility to restrict OData access to defined VDB > ----------------------------------------------------------- > > Key: TEIID-3102 > URL: https://issues.jboss.org/browse/TEIID-3102 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.7.1, 8.9 > > > The current OData interface in the Teiid provides one context for the web-application, thus restricting additional security/per VDB. > The alternative proposed is restrict the current web-app to single VDB, then provide a mechanism to alter the context and any necessary security domain stuff. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 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 Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1134393 > Netty worker threads cause system high cpu > ------------------------------------------ > > Key: TEIID-3070 > URL: https://issues.jboss.org/browse/TEIID-3070 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.7 > Environment: JDV 6.1.0.DR2 > JDV 6.0 > Reporter: Kylin Soong > Assignee: Steven Hawkins > > 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)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3098) Expose the ModeShape JCR functions in the modeshape translator metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3098?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3098: --------------------------------------- Based upon the pull requests this is taking the pushdown functions and making them schema scoped. That is not desirable. > Expose the ModeShape JCR functions in the modeshape translator metadata > ------------------------------------------------------------------------ > > Key: TEIID-3098 > URL: https://issues.jboss.org/browse/TEIID-3098 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Expose the ModeShape JCR functions in the metadata in the modeshape translator. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3106) BufferManager Cleaner consuming 90% of total CPU time

by Mark Addleman (JIRA)

[ https://issues.jboss.org/browse/TEIID-3106?page=com.atlassian.jira.plugin... ] Mark Addleman commented on TEIID-3106: -------------------------------------- > But that would imply that more than 2 billion reads had occurred, which seems unlikely for start up. Agreed. I was looking through invokers of new CacheKey to see if I could spot an underflow from them. I didn't but I did see a possible anomaly: The starting values for lastAccess and orderingValue are zero from almost all clients except org.teiid.common.buffer.impl.BufferFrontedFileStoreCache.get(PhysicalInfo, Long, WeakReference<? extends Serializer<?>>) where they are one. This strikes me as odd but there could be good reason for it. > BufferManager Cleaner consuming 90% of total CPU time > ----------------------------------------------------- > > Key: TEIID-3106 > URL: https://issues.jboss.org/browse/TEIID-3106 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Query Engine > Affects Versions: 8.7 > Environment: zOS > Reporter: Devesh Mishra > Assignee: Steven Hawkins > Labels: teiid-engine > Attachments: BufferManagerImpl.java, CacheKey_Loog.patch > > > BufferManager Cleaner thread is consuming almost all of the CPU utilized by the jboss process. Thread dump shows following information. > 3XMTHREADINFO "BufferManager Cleaner" J9VMThread:0x0000004C41CFEB00, j9thread_t:0x0000004C52B85AE0, java/lang/Thread:0x000000481C036E20, state:CW, prio=5 > 3XMJAVALTHREAD (java/lang/Thread getId:0x76, isDaemon:true) > 3XMTHREADINFO1 (native thread ID:0x3AEC2600, native priority:0x5, native policy:UNKNOWN) > 3XMHEAPALLOC Heap bytes allocated since last GC cycle=2609184 (0x27D020) > 3XMTHREADINFO3 Java callstack: > 4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.doRemove(ConcurrentSkipListMap.java:1070(Compiled Code)) > 4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.remove(ConcurrentSkipListMap.java:1659(Compiled Code)) > 4XESTACKTRACE at org/teiid/common/buffer/impl/LrfuEvictionQueue.remove(LrfuEvictionQueue.java:60(Compiled Code)) > 4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl.doEvictions(BufferManagerImpl.java:854(Compiled Code)) > 5XESTACKTRACE (entered lock: org/teiid/common/buffer/CacheEntry@0x00000048393C2598, entry count: 1) > 4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl$Cleaner.run(BufferManagerImpl.java:108) > 4XESTACKTRACE at java/util/TimerThread.mainLoop(Timer.java:555) > 4XESTACKTRACE at java/util/TimerThread.run(Timer.java:505) > When we added log statements around the BufferManagerImpl.doEvictions() it loops through the remove and firstEntry loop. > Forum discussion link : https://community.jboss.org/message/901792 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3098) Expose the ModeShape JCR functions in the modeshape translator metadata

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3098?page=com.atlassian.jira.plugin... ] Work on TEIID-3098 stopped by Van Halbert. ------------------------------------------ > Expose the ModeShape JCR functions in the modeshape translator metadata > ------------------------------------------------------------------------ > > Key: TEIID-3098 > URL: https://issues.jboss.org/browse/TEIID-3098 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > > Expose the ModeShape JCR functions in the metadata in the modeshape translator. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3098) Expose the ModeShape JCR functions in the modeshape translator metadata

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3098?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3098: ------------------------------- Assignee: Steven Hawkins (was: Van Halbert) > Expose the ModeShape JCR functions in the modeshape translator metadata > ------------------------------------------------------------------------ > > Key: TEIID-3098 > URL: https://issues.jboss.org/browse/TEIID-3098 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Expose the ModeShape JCR functions in the metadata in the modeshape translator. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3098) Expose the ModeShape JCR functions in the modeshape translator metadata

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3098?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3098: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/316, https://github.com/teiid/teiid/pull/317 2 different PR's were required. 316 for master, and 317 for 8.7.x, due to a difference in DDLStringVisitor > Expose the ModeShape JCR functions in the modeshape translator metadata > ------------------------------------------------------------------------ > > Key: TEIID-3098 > URL: https://issues.jboss.org/browse/TEIID-3098 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > > Expose the ModeShape JCR functions in the metadata in the modeshape translator. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3100) SOLR: Connector ignores CoreName property

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3100?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3100: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1133848|https://bugzilla.redhat.com/show_bug.cgi?id=1133848] from NEW to MODIFIED > SOLR: Connector ignores CoreName property > ----------------------------------------- > > Key: TEIID-3100 > URL: https://issues.jboss.org/browse/TEIID-3100 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Connector API > Affects Versions: 8.7 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.7.1, 8.9 > > > SOLR connector ignores CoreName property. It uses first or active core (by default "collection1"). CoreName should be appended to the Solr Server's baseUrl. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3100) SOLR: Connector ignores CoreName property

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3100?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3100. --------------------------------- Labels: Beta1 (was: ) Resolution: Done CoreName is now appended to the Base URL. Make sure the core name is not added to URL in the configuration > SOLR: Connector ignores CoreName property > ----------------------------------------- > > Key: TEIID-3100 > URL: https://issues.jboss.org/browse/TEIID-3100 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Connector API > Affects Versions: 8.7 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.7.1, 8.9 > > > SOLR connector ignores CoreName property. It uses first or active core (by default "collection1"). CoreName should be appended to the Solr Server's baseUrl. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3111) Function with multi-part names not resolving correctly

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3111?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3111: ---------------------------------- Summary: Function with multi-part names not resolving correctly (was: Expose group name, defined for functions, in the exposed metadata) Issue Type: Bug (was: Enhancement) Fix Version/s: 8.9 8.7 Description: When a function has multi-part name, like JCR for the modeshape functions, it won't resolve without the JCR prefix. That is SYS.JCR.function works JCR.function works but just function doesn't work. was:When a function has a defined group, like JCR for the modeshape functions, it should be exposed somehow in the metadata. Otherwise, user will never know to use the group name (i.e., JCR.JCR_ISCHILDNODE(rc."jcr:path", rt."jcr:path") ) unless they goto the documentation. Affects Version/s: 7.3 (was: 8.9) Component/s: Query Engine (was: Server) > Function with multi-part names not resolving correctly > ------------------------------------------------------ > > Key: TEIID-3111 > URL: https://issues.jboss.org/browse/TEIID-3111 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Query Engine > Affects Versions: 7.3 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.7, 8.9 > > > When a function has multi-part name, like JCR for the modeshape functions, it won't resolve without the JCR prefix. That is > SYS.JCR.function works > JCR.function works > but just function doesn't work. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2014