September 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-706) Deployed vdbs should have a consistent unzipped location.

by Steven Hawkins (JIRA)

Deployed vdbs should have a consistent unzipped location. --------------------------------------------------------- Key: TEIID-706 URL: https://jira.jboss.org/jira/browse/TEIID-706 Project: Teiid Issue Type: Sub-task Components: Embedded, Query Engine Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 Deployed vdbs, or vdb less configurationinfo.def files should have a consistent location for their exploded form. Under <teiid home>/deploy there will be folders <vdb name>/<vdb version> - with lower cased names. On the initial scan for vdbs and def files we will use the corresponding def file to see if the <teiid home>/deploy/<vdb name>/<vdb version> already exists. If it does not we will create the exploded location, otherwise we'll use it rather than the archive file itself. Any changes after deployment time ConfigurationInfo, roles, etc. will only be made to the exploded location. This will make it easy to document how to modify these files without constantly zipping and unzipping them. Ideally this exploded location should also be used by the index file logic rather than using yet another temporary location. -- 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

16 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-698) Create AdminShell Kit

by Ramesh Reddy (JIRA)

Create AdminShell Kit --------------------- Key: TEIID-698 URL: https://jira.jboss.org/jira/browse/TEIID-698 Project: Teiid Issue Type: Task Components: AdminApi, Common, Tools Reporter: Ramesh Reddy Priority: Blocker Fix For: 6.2.0 Create the AdminShell kit for the Teiid runtime. This will be used as the external tool to manage the Teiid runtime environment. -- 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

16 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-702) Define/Provide ways to create and use encrypted passwords in Teiid

by Ramesh Reddy (JIRA)

Define/Provide ways to create and use encrypted passwords in Teiid ------------------------------------------------------------------ Key: TEIID-702 URL: https://jira.jboss.org/jira/browse/TEIID-702 Project: Teiid Issue Type: Task Components: Common Reporter: Ramesh Reddy Fix For: 6.2.0 Teiid runtime is capable of decrypting the encrypted passwords from the Teiid Designer (when the same key certs are used), however does not provide a mechanism to provide a utility to encrypt passwords itself. Often times the Designer might be using a different certificate or may be the user did not use the Designer at all. So, Teiid needs 1) Script to create a new certificate for password encryption 2) Script to encrypt a given password 3) Integration of the this cert with runtime, such that it can decrypt password(s) at runtime. 4) Documentation as how this can be done. -- 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

16 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-666) Add "Session" service

by Ramesh Reddy (JIRA)

Add "Session" service --------------------- Key: TEIID-666 URL: https://jira.jboss.org/jira/browse/TEIID-666 Project: Teiid Issue Type: Sub-task Components: Embedded, Query Engine, Server Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.2.0 Add "session" service to "embedded" that tracks the users that are logged into the system. -- 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

16 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-680) Add "socket" transport as service

by Ramesh Reddy (JIRA)

Add "socket" transport as service ---------------------------------- Key: TEIID-680 URL: https://jira.jboss.org/jira/browse/TEIID-680 Project: Teiid Issue Type: Sub-task Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 Add mechanism to start a socket transport as service when query engine starts. The socket transport can be used in two fold. 1) In client/server mode 2) In embedded mode (on demand). When a embedded is started then socket transport is started, then some other client can connect to it until "embedded" is alive. -- 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

16 years, 6 months

2
4
0 / 0

[JBoss JIRA] Closed: (TEIID-420) VDB Deployment buttons are activated for Product Admin but error is produced on final Finish

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-420?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-420. -------------------------------- > VDB Deployment buttons are activated for Product Admin but error is produced on final Finish > -------------------------------------------------------------------------------------------- > > Key: TEIID-420 > URL: https://jira.jboss.org/jira/browse/TEIID-420 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.0.0 > Environment: Windows client against Windows server with Entitlements turned on > Reporter: Warren Gibson > Assignee: Steven Hawkins > Fix For: 6.1.0 > > Attachments: console_Log.log > > > Logged in as a Product Admin user and attempted to deploy a VDB. Everything worked fine until the final Finish button when an error was produced. > [AuthorizationException] ERR.014.001.0008: The client is not authorized to attempt this operation. User: SessionToken[pjones@MyLDAP,3653,slntmm05_15301] Role: Admin.SystemAdmin > at com.metamatrix.platform.admin.apiimpl.AdminHelper.checkForRequiredRole(AdminHelper.java:102) > at com.metamatrix.platform.admin.apiimpl.AdminAPIHelper.checkForRequiredRole(AdminAPIHelper.java:71) > at com.metamatrix.platform.admin.apiimpl.ConfigurationAdminAPIImpl.checkPropertiesDecryptable(ConfigurationAdminAPIImpl.java:1254) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.metamatrix.core.proxy.ServiceInvocation.invokeOn(ServiceInvocation.java:91) > at com.metamatrix.core.proxy.DefaultTerminalServiceInterceptor.invoke(DefaultTerminalServiceInterceptor.java:29) > at com.metamatrix.core.proxy.SecureTerminalServiceInterceptor.invoke(SecureTerminalServiceInterceptor.java:45) > at com.metamatrix.core.proxy.ServiceInvocation.invokeNext(ServiceInvocation.java:87) > at com.metamatrix.core.proxy.ServerSecurityServiceInterceptor.invoke(ServerSecurityServiceInterceptor.java:23) > at com.metamatrix.core.proxy.ServiceInvocation.invokeNext(ServiceInvocation.java:87) > at com.metamatrix.common.comm.platform.server.MessageServiceAgent.receiveLocal(MessageServiceAgent.java:90) > at com.metamatrix.common.comm.platform.server.MessageServiceAgent.receive(MessageServiceAgent.java:114) > at com.metamatrix.common.comm.platform.server.MessageFilterServiceAgent.receive(MessageFilterServiceAgent.java:99) > at com.metamatrix.platform.admin.apiimpl.RuntimeStateListenerAgent.receive(RuntimeStateListenerAgent.java:103) > at com.metamatrix.common.comm.platform.socket.SocketVMController.receive(SocketVMController.java:388) > at com.metamatrix.common.comm.platform.socket.server.ServerSynchronousWorkItem.process(ServerSynchronousWorkItem.java:36) > at com.metamatrix.common.comm.platform.socket.server.SocketServerWorker.process(SocketServerWorker.java:35) > at com.metamatrix.common.queue.QueueWorker.run(QueueWorker.java:64) -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-606) Connector Bindings password property is not shown on Connector Bindings Properties panel until user checks "include optional properties" box

by Warren Gibson (JIRA)

Connector Bindings password property is not shown on Connector Bindings Properties panel until user checks "include optional properties" box -------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-606 URL: https://jira.jboss.org/jira/browse/TEIID-606 Project: Teiid Issue Type: Bug Components: Console Affects Versions: 6.0.0 Environment: Teiid Console on Windows Reporter: Warren Gibson Assignee: Steven Hawkins The Teiid Console connector bindings properties panel does not show the Password property until the user checks the optional properties box. The password property has always been visable without requiring user to check the optional properties. It seems more like a primary property than an optional property and from a usability standpoint should not be hidden. -- 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

16 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-602) Connecting to server from client fails with SingleInstanceCommunicationException and MMProcess goes into a loop

by Paul Nittel (JIRA)

Connecting to server from client fails with SingleInstanceCommunicationException and MMProcess goes into a loop --------------------------------------------------------------------------------------------------------------- Key: TEIID-602 URL: https://jira.jboss.org/jira/browse/TEIID-602 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.0.0 Environment: Fedora 10, JBEDSP 13 May Reporter: Paul Nittel Assignee: Steven Hawkins Priority: Blocker I tried to connect to the server from SQuirreL and, while it appeared to be on its way to success, finally failed with the exception noted above. As I have noted a few times now, the jvm running MMProcess is in a loop, consuming 99+% of the CPU. I did a kill -3 and will attach the host controller log to the Jira. -- 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

16 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-624) ConvertPassword utility has the default location for the Crypto Key File set to the <install>/lib directory, should be config

by Van Halbert (JIRA)

ConvertPassword utility has the default location for the Crypto Key File set to the <install>/lib directory, should be config ----------------------------------------------------------------------------------------------------------------------------- Key: TEIID-624 URL: https://jira.jboss.org/jira/browse/TEIID-624 Project: Teiid Issue Type: Bug Affects Versions: 6.1.1 Reporter: Van Halbert Assignee: Van Halbert The FilePasswordConverter class has the DEFAULT_KEY_FILE set to expect the keystore file in the lib directory, however it has been changed to be in the config directory. -- 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

16 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-670) Query Testing returned 0 rows on 16 queries when results were expected - Involves FoatNum, LongNum, DoubleNum, BigDecimalValue, and BigIntegerValue

by Warren Gibson (JIRA)

Query Testing returned 0 rows on 16 queries when results were expected - Involves FoatNum, LongNum, DoubleNum, BigDecimalValue, and BigIntegerValue --------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-670 URL: https://jira.jboss.org/jira/browse/TEIID-670 Project: Teiid Issue Type: Bug Affects Versions: 6.1.0 Environment: CTC Reporter: Warren Gibson Assignee: Steven Hawkins Attachments: NoRecordReturned.ods Teiid Query Testing 1. Ran CTC query testing against Teiid and "no results" were returned on 16 queries which was expecting results. 2. The queries contained FloatNum, LongNum, DoubleNum, and BigDecimalValue and BigIntegerValue. 3. Attached is a spreadsheet with the results and the queries. -- 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

16 years, 6 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2009