[JBoss JIRA] (TEIID-3181) Use Teiid as default JAAS application name
by Cristiano Nicolai (JIRA)
Cristiano Nicolai created TEIID-3181:
----------------------------------------
Summary: Use Teiid as default JAAS application name
Key: TEIID-3181
URL: https://issues.jboss.org/browse/TEIID-3181
Project: Teiid
Issue Type: Enhancement
Reporter: Cristiano Nicolai
Assignee: Steven Hawkins
Enhancement for the client side of setting up JDBC connections using GSS API. Suggestion is to use "Teiid" as default JAAS application name. This is to be used in case jaasName is not supplied in the connection properties.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (TEIID-3180) Use TEIID/hostname as default Kerberos principal name
by Cristiano Nicolai (JIRA)
Cristiano Nicolai created TEIID-3180:
----------------------------------------
Summary: Use TEIID/hostname as default Kerberos principal name
Key: TEIID-3180
URL: https://issues.jboss.org/browse/TEIID-3180
Project: Teiid
Issue Type: Enhancement
Reporter: Cristiano Nicolai
Assignee: Steven Hawkins
Enhancement for the client side of setting up JDBC connections using GSS API. Suggestion is to use TEIID as service name, combined with the hostname used to create the Teiid connection. This is tu be used in case kerberosServicePrincipleName is not supplied in the connection properties.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (TEIID-3095) Expose system and pushdown functions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3095?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3095.
-----------------------------------
Resolution: Done
Marking as resolved since the original issue is addressed. It will be a separate task to expose pushdown and system functions in generated ddl - note that it's already somewhat possible when using the importer option to add the pushdown functions to the imported schema.
> Expose system and pushdown functions
> ------------------------------------
>
> Key: TEIID-3095
> URL: https://issues.jboss.org/browse/TEIID-3095
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Affects Versions: 8.9
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> The system functions and pushdown functions are not added as normal schema scoped functions, and thus were not exposed by TEIID-3044. We should properly expose them and if possible also add uuids and the ability to lookup system properties.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (TEIID-3070) Netty worker threads cause system high cpu
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3070?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3070:
-------------------------------------
Since we advocate the community to be using the latest versions, I think defining the fix on the JIRA enough.
> 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, 8.9
> 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)
9 years, 8 months
[JBoss JIRA] (TEIID-3070) Netty worker threads cause system high cpu
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3070?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3070:
---------------------------------------
Updated master to 3.6.10 and addressed the test failure that Kylin was seeing. The shutdown logic needed adjusting with the updated Netty, but is backwards compatible, so the change was good to commit and can be backported as well. So the only thing left would be patching instructions for the community version. Is this a common enough issue that we want that on the download page or should we just put the instructions in this issue and/or the release notes?
> 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, 8.9
> 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)
9 years, 8 months