[JBoss JIRA] Created: (TEIID-1187) Refine vdb version logic
by Steve Hawkins (JIRA)
Refine vdb version logic
------------------------
Key: TEIID-1187
URL: https://jira.jboss.org/browse/TEIID-1187
Project: Teiid
Issue Type: Quality Risk
Components: Server
Affects Versions: 7.1
Reporter: Steve Hawkins
Assignee: Steve Hawkins
Fix For: 7.1
We no longer have a built in configuration repository and we rely on container scans to do deploys, so we have lost the ability to internally control the notion of a deployed vdb version.
We should strive for the following:
1. Overwrite of a deployed vdb should not invalidate or otherwise corrupt current connections.
2. Switching to a different vdb as the new default for a particular name should not require two deployments of the same vdb.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (TEIID-1055) Secure profile service access
by Ramesh Reddy (JIRA)
Secure profile service access
-----------------------------
Key: TEIID-1055
URL: https://jira.jboss.org/jira/browse/TEIID-1055
Project: Teiid
Issue Type: Task
Components: AdminApi
Affects Versions: 7.0
Reporter: Ramesh Reddy
Fix For: 7.0
As of 7.0 M3 release, the "Profile Service" access is not secure. Currently the JOPR plug-in and Teiid Admin API, force users to authenticate with "jmx-console" security domain, both these do not prevent the direct access to the "Profile Service" EJB directly.
Profile Service can be deployed as secure EJB, such that it would require a login context to be authenticated before user has access to this bean. This needs to be configured and tested. Also document, how to configure the profile service as secure service.
Also, AdminFactory class, which provides Admin connections, need to work with secure "Profile Service".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (TEIID-1211) Refine load-balancing support in AS
by Steve Hawkins (JIRA)
Refine load-balancing support in AS
-----------------------------------
Key: TEIID-1211
URL: https://jira.jboss.org/browse/TEIID-1211
Project: Teiid
Issue Type: Quality Risk
Components: JDBC Driver
Affects Versions: 7.1
Reporter: Steve Hawkins
Assignee: Steve Hawkins
Fix For: 7.1.1
In an AS connection pool, an XAConnection does not receive a notification of a connection.close, so our post-connection load-balancing logic will never kick in. For environments with a low/infrequent number of client connections, this will produce a poor load distribution.
Possible Solutions:
1. Ensure proper tracking of the transation state and switch servers after a commit/rollback. This however would also require that session level temporary tables are replicated (although that replication logic should be added as part of the materialization feature). And would cause potential cache misses or other minor issues with session level deterministic functions.
2. Promote the use of Teiid directly through our own DataSource and handle transaction enlist/delist logic appropriately. Users would instead use a jboss beans.xml file to create a named instance of the datasource in JNDI. The appeal of this solution is that it we are architected to not require the use of a pool (settings for max connections, statement pooling, are mostly irrelevant for local connections to Teiid). We have our own thread pooling, etc.
3. See if we can get some AS patch to also pass connection events to PooledConnections.
Another thing that may need addressed is runtime discovery of additional hosts, if not we could also add an option to pick up hosts and connection information from an external file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (TEIID-1188) Error while reading the template properties for LDAP
by Ramesh Reddy (JIRA)
Error while reading the template properties for LDAP
----------------------------------------------------
Key: TEIID-1188
URL: https://jira.jboss.org/browse/TEIID-1188
Project: Teiid
Issue Type: Bug
Components: LDAP Connector
Affects Versions: 7.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Priority: Minor
Fix For: 7.1
groovy:000> getTemplatePropertyDefinitions("connector-ldap");
ERROR org.teiid.adminapi.AdminComponentException:
Failed to find template for: translator-connector-ldap
at org.teiid.client.util.ExceptionUtil.convertException (ExceptionUtil.java:72)
at org.teiid.net.socket.SocketServerConnection$ServerConnectionInvocationHandler.invoke (SocketServerConnection.java:239)
at $Proxy7.getTemplatePropertyDefinitions (Unknown Source
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months