[JBoss JIRA] (TEIID-5249) Infinispan: Should make use of Remote Cache Creation in Infinispan
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-5249:
-----------------------------------
Summary: Infinispan: Should make use of Remote Cache Creation in Infinispan
Key: TEIID-5249
URL: https://issues.jboss.org/browse/TEIID-5249
Project: Teiid
Issue Type: Enhancement
Components: Infinispan, Misc. Connectors
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
The current implementation of Infinispan for materialization purpose still treats the Infinispan as the external source where the user needs to configure the Infinispan source and then do various other steps to use it as a Materialization target. Using remote cache creation feature, the process can be streamlined to behave like an internal cache.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (TEIID-5244) Text Based LoginModule does not find properties files
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5244?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-5244.
---------------------------------
Fix Version/s: 10.2
Assignee: Ramesh Reddy (was: Steven Hawkins)
Resolution: Done
Fixed the documentation to use ${property}
> Text Based LoginModule does not find properties files
> -----------------------------------------------------
>
> Key: TEIID-5244
> URL: https://issues.jboss.org/browse/TEIID-5244
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 10.1
> Reporter: Bram Gadeyne
> Assignee: Ramesh Reddy
> Fix For: 10.2
>
>
> Hi,
> I have this in my configuration:
> {code:xml}
> <security-domain name="teiid-security" cache-type="default">
> <authentication>
> <login-module code="UsersRoles" flag="required">
> <module-option name="usersProperties" value="$(jboss.server.config.dir)/teiid-security-users.properties"/>
> <module-option name="rolesProperties" value="$(jboss.server.config.dir)/teiid-security-roles.properties"/>
> </login-module>
> </authentication>
> </security-domain>
> {code}
> The two files teiid-security-roles.properties and teiid-security-users.properties are located in the configuration directory of wildfly.
> I see this error message in the logs: It seems like teiid is using the value as a directory.
> 2018-02-01 15:20:40,918 ERROR [org.jboss.security] (NIO1) PBOX00261: Failed to load users/passwords/roles files: java.io.IOException: PBOX00072: Properties file $(jboss.server.config.dir)/teiid-security-users.properties/defaultUsers.properties not found
> at org.jboss.security.auth.spi.Util.loadProperties(Util.java:212)
> at org.jboss.security.auth.spi.UsersRolesLoginModule.loadUsers(UsersRolesLoginModule.java:205)
> at org.jboss.security.auth.spi.UsersRolesLoginModule.createUsers(UsersRolesLoginModule.java:219)
> at org.jboss.security.auth.spi.UsersRolesLoginModule.initialize(UsersRolesLoginModule.java:146)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (TEIID-5248) Upgrade to v4 api for google spreadsheets
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5248:
-------------------------------------
Summary: Upgrade to v4 api for google spreadsheets
Key: TEIID-5248
URL: https://issues.jboss.org/browse/TEIID-5248
Project: Teiid
Issue Type: Quality Risk
Components: Misc. Connectors
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.2
Our integration is based upon the v3 api, which will soon be deprecated. This will be a large change given the api differences. We can also look to include TEIID-5040
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (TEIID-5244) Text Based LoginModule does not find properties files
by Bram Gadeyne (JIRA)
[ https://issues.jboss.org/browse/TEIID-5244?page=com.atlassian.jira.plugin... ]
Bram Gadeyne commented on TEIID-5244:
-------------------------------------
That does work! But it was mentioned with $() in the [documentation|https://teiid.gitbooks.io/documents/content/v/10.1.x/security/LoginModules.html]:
> Text Based LoginModule does not find properties files
> -----------------------------------------------------
>
> Key: TEIID-5244
> URL: https://issues.jboss.org/browse/TEIID-5244
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 10.1
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
>
> Hi,
> I have this in my configuration:
> {code:xml}
> <security-domain name="teiid-security" cache-type="default">
> <authentication>
> <login-module code="UsersRoles" flag="required">
> <module-option name="usersProperties" value="$(jboss.server.config.dir)/teiid-security-users.properties"/>
> <module-option name="rolesProperties" value="$(jboss.server.config.dir)/teiid-security-roles.properties"/>
> </login-module>
> </authentication>
> </security-domain>
> {code}
> The two files teiid-security-roles.properties and teiid-security-users.properties are located in the configuration directory of wildfly.
> I see this error message in the logs: It seems like teiid is using the value as a directory.
> 2018-02-01 15:20:40,918 ERROR [org.jboss.security] (NIO1) PBOX00261: Failed to load users/passwords/roles files: java.io.IOException: PBOX00072: Properties file $(jboss.server.config.dir)/teiid-security-users.properties/defaultUsers.properties not found
> at org.jboss.security.auth.spi.Util.loadProperties(Util.java:212)
> at org.jboss.security.auth.spi.UsersRolesLoginModule.loadUsers(UsersRolesLoginModule.java:205)
> at org.jboss.security.auth.spi.UsersRolesLoginModule.createUsers(UsersRolesLoginModule.java:219)
> at org.jboss.security.auth.spi.UsersRolesLoginModule.initialize(UsersRolesLoginModule.java:146)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (TEIID-5126) Osisoft translator - SUBSTRING fails when start > string length
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-5126?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-5126:
------------------------------------------------
Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1506519|https://bugzilla.redhat.com/show_bug.cgi?id=1506519] from ON_QA to CLOSED
> Osisoft translator - SUBSTRING fails when start > string length
> ---------------------------------------------------------------
>
> Key: TEIID-5126
> URL: https://issues.jboss.org/browse/TEIID-5126
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 8.12.x-6.4
> Reporter: Andrej Šmigala
> Assignee: Ramesh Reddy
> Priority: Minor
> Fix For: 10.1
>
>
> Calling a query such as
> {code:sql}
> SELECT cast(TIMESTAMPVALUE as string), SUBSTRING(TIMESTAMPVALUE, 22, 0) FROM BQT1.SmallA
> {code}
> fails with the following (the length of timestampvalue converted to string is 20):
> {noformat}
> Connector worker process failed for atomic-request=HOiQATHW3fPH.12.0.9: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [SQL: SELECT TOP 100 cast(g_0.TimestampValue AS String) AS c_0, SUBSTR(cast(g_0.TimestampValue AS String), 22, 0) AS c_1 FROM dvqe..SmallA AS g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:363)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_141]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_141]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_141]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_141]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy79.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_141]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_141]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]
> Caused by: java.sql.SQLException: [PIOLEDBENT] Arguments are invalid.
> at com.osisoft.jdbc.StatementImpl.executeQuery(StatementImpl.java:360)
> at org.jboss.jca.adapters.jdbc.WrappedStatement.executeQuery(WrappedStatement.java:344)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:119) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> ... 18 more
> Caused by: com.osisoft.rdsa.RdsaException: [PIOLEDBENT] Arguments are invalid.
> at com.osisoft.rdsa.Command.ExecuteReader(Native Method)
> at com.osisoft.rdsa.Command.executeReader(Command.java:79)
> at com.osisoft.jdbc.StatementImpl.executeQuery(StatementImpl.java:356)
> ... 20 more
> {noformat}
> This appears to be an issue with the SUBSTR implementation on the PI server, we are ok with either a workaround or documenting as KI.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (TEIID-5246) Simplify Teiid configuration when using an external load balancer
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5246?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5246.
-----------------------------------
Resolution: Done
Switched the logic so that we'll only check for orphaned inactive connections - those that are maintained when using Teiid load balancing. A client ping will no longer be sent when connecting to a 10.2+ server and it's not required to set the server system property checkPing=false.
> Simplify Teiid configuration when using an external load balancer
> -----------------------------------------------------------------
>
> Key: TEIID-5246
> URL: https://issues.jboss.org/browse/TEIID-5246
> Project: Teiid
> Issue Type: Quality Risk
> Components: Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.2
>
>
> When using an external load balancer it requires that the server disable ping checks and set max session age (to clean up any orphaned sessions). This is not specifically called out in the documentation. For future releases we should eliminate the need to explicitly change the configuration when using an external load balancer.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (TEIID-5246) Simplify Teiid configuration when using an external load balancer
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5246:
-------------------------------------
Summary: Simplify Teiid configuration when using an external load balancer
Key: TEIID-5246
URL: https://issues.jboss.org/browse/TEIID-5246
Project: Teiid
Issue Type: Quality Risk
Components: Server
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.2
When using an external load balancer it requires that the server disable ping checks and set max session age (to clean up any orphaned sessions). This is not specifically called out in the documentation. For future releases we should eliminate the need to explicitly change the configuration when using an external load balancer.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months