February 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2857) Build Error with Teiid POM Dependency

by Ivan Chan (JIRA)

Ivan Chan created TEIID-2857: -------------------------------- Summary: Build Error with Teiid POM Dependency Key: TEIID-2857 URL: https://issues.jboss.org/browse/TEIID-2857 Project: Teiid Issue Type: Bug Components: Embedded Affects Versions: 8.6 Reporter: Ivan Chan Assignee: Steven Hawkins In the jboss public maven repository: https://repository.jboss.org/nexus/content/groups/public The teiid-parent-8.6.0.Final.pom file has two dependencies which look to be Teiid build/configuration bugs. These two issues are causing our source code build to fail. The pom file is located here: https://repository.jboss.org/nexus/content/groups/public/org/jboss/teiid/... In this pom file there are two declared dependencies: <version.org.jboss.integration-platform>6.0.0-SNAPSHOT</version.org.jboss.integration-platform> <jbossas-version>7.2.0.Alpha1-redhat-4</jbossas-version> <dependency> <groupId>org.jboss.integration-platform</groupId> <artifactId>jboss-integration-platform-bom</artifactId> <version>${version.org.jboss.integration-platform}</version> <scope>import</scope> <type>pom</type> </dependency> <dependency> <groupId>org.jboss.as</groupId> <artifactId>jboss-as-parent</artifactId> <version>${jbossas-version}</version> <type>pom</type> <scope>import</scope> </dependency> Here are the issues: 1) Snapshot dependency existing in the 8.6.0-FINAL Release - jboss-integration-platform-bom/6.0.0-SNAPSHOT 2) Declared dependency does not exist in the repo repository.jboss.org - jboss-as-parent/7.2.0.Alpha1-redhat-4 - We see dependencies only for: - 7.2.0.Alpha1-SNAPSHOT - 7.2.0.Fina I'm not sure why these dependencies are needed when pulling in the Teiid artifacts, but perhaps because the <scope> of these dependencies is set to "import" (<scope>import</scope>) Our usage of the repository.jboss.org is to have snapshots disabled. So that is why the 6.0.0-SNAPSHOT fails to be found. For the 7.2.0.Alpha1-redhat-4 dependency, it does not exist in repository.jboss.org so this also fails. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2854) bounded-queue-thread-pool silently drops tasks after the queue length is exceeded

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2854?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2854: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1067164 > bounded-queue-thread-pool silently drops tasks after the queue length is exceeded > --------------------------------------------------------------------------------- > > Key: TEIID-2854 > URL: https://issues.jboss.org/browse/TEIID-2854 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.5 > Environment: JBoss EAP 6.1.0 Alpha and Teiid 8.5 > Reporter: Rakesh Balguri > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7 > > > The bounded-queue-thread-pool apparently needs a handoff executor configured otherwise it silently drops tasks after the queue length is exceeded. > See the discussion for more information. > https://community.jboss.org/thread/236744 -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2844) remove unauthorized columns from select *

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2844?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2844. ----------------------------------- Resolution: Done Added a release note and documentation about the system property. Will likely address the client usability with a follow-on issue, such as allowing the client set statement to set session variables. > remove unauthorized columns from select * > ----------------------------------------- > > Key: TEIID-2844 > URL: https://issues.jboss.org/browse/TEIID-2844 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7 > > > For ease of use with entitlement checking enabled, user queries with select * and *.tbl, should simply not treat unauthorized columns as selectable. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2813) Report translator CPU time

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2813?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2813: --------------------------------------- Mark, Are you still waiting on approval? > Report translator CPU time > -------------------------- > > Key: TEIID-2813 > URL: https://issues.jboss.org/browse/TEIID-2813 > Project: Teiid > Issue Type: Feature Request > Reporter: Mark Addleman > Assignee: Steven Hawkins > > The COMMAND_LOG ought to report the CPU time accumulated by the translator for performance tuning purposes. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2856) IP address incorrectly exposed via SECURITY logger

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2856?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2856. ----------------------------------- Fix Version/s: 8.7 Resolution: Done Added the client ip as known to the server for ODBC. Updated the JDBC client side logic to use the actual connection to determine the local address, rather than just getLocalHost. > IP address incorrectly exposed via SECURITY logger > -------------------------------------------------- > > Key: TEIID-2856 > URL: https://issues.jboss.org/browse/TEIID-2856 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.5 > Environment: RHEL6 linux 2.6.32-431.1.2.el6.x86_64 #1 SMP Sun Nov 24 09:37:37 EST 2013 x86_64 x86_64 x86_64 GNU/Linux > jbossas-standalone 7.2.1 6.Final_redhat_10.1.ep6.el6 > Reporter: Marco Grigull > Assignee: Steven Hawkins > Fix For: 8.7 > > > After configuring a logger for org.teiid.SECURITY debug level, fields for IP address information appears to be supplied by the client and not observed from the connection itself (odbc connections). It is reported as null for psql based connections. > This had previously been reported as TEIID-1586 and TEIID-1672 . IT still presents an issue where audit trail is required. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2856) IP address incorrectly exposed via SECURITY logger

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2856?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2856: --------------------------------------- Yes, ODBC does not currently capture that information. The best we can do there is determine the IP of the incoming socket connection as we don't have any influence over the protocol to add information. As for the JDBC side, those values are all reported by the client but using just the getLocalHost call. Is the issue here that you have multiple interfaces and the correct one is not being reported? > IP address incorrectly exposed via SECURITY logger > -------------------------------------------------- > > Key: TEIID-2856 > URL: https://issues.jboss.org/browse/TEIID-2856 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.5 > Environment: RHEL6 linux 2.6.32-431.1.2.el6.x86_64 #1 SMP Sun Nov 24 09:37:37 EST 2013 x86_64 x86_64 x86_64 GNU/Linux > jbossas-standalone 7.2.1 6.Final_redhat_10.1.ep6.el6 > Reporter: Marco Grigull > Assignee: Steven Hawkins > > After configuring a logger for org.teiid.SECURITY debug level, fields for IP address information appears to be supplied by the client and not observed from the connection itself (odbc connections). It is reported as null for psql based connections. > This had previously been reported as TEIID-1586 and TEIID-1672 . IT still presents an issue where audit trail is required. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2856) IP address incorrectly exposed via SECURITY logger

by Marco Grigull (JIRA)

[ https://issues.jboss.org/browse/TEIID-2856?page=com.atlassian.jira.plugin... ] Marco Grigull commented on TEIID-2856: -------------------------------------- JDBC 2014-02-19 15:03:29,844 DEBUG [org.teiid.SECURITY] (New I/O worker #2:) Logon successful, created session: sessionid=xDc8ma7VHRAG; userName=protected_user@teiid-security; vdbName=raw; vdbVersion=1; createdTime=Wed Feb 19 15:03:29 EST 2014; applicationName=JDBC; clientHostName=<user_reported_hostname>; clientHardwareAddress=null; IPAddress=10.x.x.x; securityDomain=teiid-security; lastPingTime=Wed Feb 19 15:03:29 EST 2014 The IPAddress was incorrect, it was not related to the client or the server in any way. The clientHostName reported did not have a reverse entry and reported a forward only hostname ODBC/psql client: 2014-02-19 14:50:46,606 DEBUG [org.teiid.SECURITY] (New I/O worker #3:) Logon successful, created session: sessionid=IRhteOhG5nj1; userName=another_user@teiid-security; vdbName=public; vdbVersion=1; createdTime=Wed Feb 19 14:50:46 EST 2014; applicationName=ODBC; clientHostName=null; clientHardwareAddress=null; IPAddress=null; securityDomain=teiid-security; lastPingTime=Wed Feb 19 14:50:46 EST 2014 > IP address incorrectly exposed via SECURITY logger > -------------------------------------------------- > > Key: TEIID-2856 > URL: https://issues.jboss.org/browse/TEIID-2856 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.5 > Environment: RHEL6 linux 2.6.32-431.1.2.el6.x86_64 #1 SMP Sun Nov 24 09:37:37 EST 2013 x86_64 x86_64 x86_64 GNU/Linux > jbossas-standalone 7.2.1 6.Final_redhat_10.1.ep6.el6 > Reporter: Marco Grigull > Assignee: Steven Hawkins > > After configuring a logger for org.teiid.SECURITY debug level, fields for IP address information appears to be supplied by the client and not observed from the connection itself (odbc connections). It is reported as null for psql based connections. > This had previously been reported as TEIID-1586 and TEIID-1672 . IT still presents an issue where audit trail is required. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2856) IP address incorrectly exposed via SECURITY logger

by Marco Grigull (JIRA)

Marco Grigull created TEIID-2856: ------------------------------------ Summary: IP address incorrectly exposed via SECURITY logger Key: TEIID-2856 URL: https://issues.jboss.org/browse/TEIID-2856 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.5 Environment: RHEL6 linux 2.6.32-431.1.2.el6.x86_64 #1 SMP Sun Nov 24 09:37:37 EST 2013 x86_64 x86_64 x86_64 GNU/Linux jbossas-standalone 7.2.1 6.Final_redhat_10.1.ep6.el6 Reporter: Marco Grigull Assignee: Steven Hawkins After configuring a logger for org.teiid.SECURITY debug level, fields for IP address information appears to be supplied by the client and not observed from the connection itself (odbc connections). It is reported as null for psql based connections. This had previously been reported as TEIID-1586 and TEIID-1672 . IT still presents an issue where audit trail is required. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2855) adding possibility to proxy URI in odata server

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2855?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-2855: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > adding possibility to proxy URI in odata server > ----------------------------------------------- > > Key: TEIID-2855 > URL: https://issues.jboss.org/browse/TEIID-2855 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.6 > Reporter: luca gioppo > Assignee: Ramesh Reddy > > As for https://community.jboss.org/thread/237239 there is the need to proxy the URI exposed by the odata server when this is behind a proxy and we do not want the URi to disclose and invalidate the reference. > The odata server should have some parameters gotten from deployment for proxy hostname and port and path up to the VDB name -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2854) bounded-queue-thread-pool silently drops tasks after the queue length is exceeded

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2854?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2854: ---------------------------------- Priority: Critical (was: Major) Workaround Description: Alter the AS configuration to use an unbounded-queue-thread-pool for Teiid asynch work. Workaround: Workaround Exists Component/s: Server (was: AdminApi) > bounded-queue-thread-pool silently drops tasks after the queue length is exceeded > --------------------------------------------------------------------------------- > > Key: TEIID-2854 > URL: https://issues.jboss.org/browse/TEIID-2854 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.5 > Environment: JBoss EAP 6.1.0 Alpha and Teiid 8.5 > Reporter: Rakesh Balguri > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7 > > > The bounded-queue-thread-pool apparently needs a handoff executor configured otherwise it silently drops tasks after the queue length is exceeded. > See the discussion for more information. > https://community.jboss.org/thread/236744 -- 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

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2014