March 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Moved: (TEIID-428) System Property Changes - Not showing up in Audit Log and System Log has entry but doesn't state what property was changed

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-428?page=com.atlassian.jira.plug... ] Steven Hawkins moved JBEDSP-994 to TEIID-428: --------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-428 (was: JBEDSP-994) Issue Type: Feature Request (was: Bug) Component/s: Server (was: Console) Fix Version/s: 6.1.0 (was: 5.5.3 CCE) Affects Version/s: 6.0.0 (was: 5.5.2) > System Property Changes - Not showing up in Audit Log and System Log has entry but doesn't state what property was changed > -------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-428 > URL: https://jira.jboss.org/jira/browse/TEIID-428 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 6.0.0 > Environment: Windows client running against Windows server > Reporter: Warren Gibson > Fix For: 6.1.0 > > Attachments: log.rtf > > > I changed 4 System Properties and found no entries in the Audit log but entries did show up in the System Log. However the entries in the System log does not specify which property was changed. Changes to System Properties should show up in Audit Log. This is one example. See attachment for other examples: > My action - Encryption - Unchecked Client Side Password. > Log: > Mar 06, 2009 14:07:47.500 [SocketWorkerQueue_Worker_52|0] ERROR <AUDIT_ADMIN|0> Administrator [ssmith@NewLDAP], session [7512] requesting access which requires role [Admin.SystemAdmin] to method [ConfigurationAdminAPIImpl.executeTransaction([Set ConfigurationID Next Startup; new value = false, previous value = true])]. > Mar 06, 2009 14:07:47.500 [SocketWorkerQueue_Worker_52|0] ERROR <AUDIT_ADMIN|0> Administrator [ssmith@NewLDAP], session [7512] granted access to method [ConfigurationAdminAPIImpl.executeTransaction([Set ConfigurationID Next Startup; new value = false, previous value = true])]. > Mar 06, 2009 14:07:47.515 [SocketWorkerQueue_Worker_52|0] INFO <CONFIG|0> Completed execution of actions. > Mar 06, 2009 14:07:47.546 [SocketWorkerQueue_Worker_52|0] INFO <CONFIG|0> Configuration Next Startup document written successfully to stream. -- 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

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-413) Create Zip file for each connector with its dependencies for server setup

by Ramesh Reddy (JIRA)

Create Zip file for each connector with its dependencies for server setup ------------------------------------------------------------------------- Key: TEIID-413 URL: https://jira.jboss.org/jira/browse/TEIID-413 Project: Teiid Issue Type: Task Components: Build/Kits Affects Versions: 6.x Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.0.0 Right now server pulls dependencies as whole, so it can not distinguish the dependencies between connector or itself. This poses issue in defining the files for the extension modules. So, these need to be come as whole with their dependencies. -- 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

15 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-425) Add back instance pooling

by Steven Hawkins (JIRA)

Add back instance pooling ------------------------- Key: TEIID-425 URL: https://jira.jboss.org/jira/browse/TEIID-425 Project: Teiid Issue Type: Sub-task Components: JDBC Driver Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.0.0 Instance pooling was initially removed in favor of holding all connected instances on the same connection. For large cluster sizes this could lead to a large number of idle connections. As a simple alternative, idle socketserverinstances should be kept in a simple pool of a configurable size. -- 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

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-424) Update client properties

by Steven Hawkins (JIRA)

Update client properties ------------------------ Key: TEIID-424 URL: https://jira.jboss.org/jira/browse/TEIID-424 Project: Teiid Issue Type: Task Reporter: Steven Hawkins Assignee: Steven Hawkins The client properties for socket and ssl configuration need to reflect the current state of the code. They should also use org.teiid instead of com.metamatrix. Providing backwards compatibility will be addressed later. -- 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

15 years, 2 months

1
2
0 / 0

[JBoss JIRA] Closed: (TEIID-292) use non-nio client sockets

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-292?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-292. -------------------------------- Fix Version/s: 6.0.0 (was: 6.1.0) Resolution: Done Added back synch io approach with a simple socket implementation. Added and slightly modified the netty specific codec for serialization. > use non-nio client sockets > -------------------------- > > Key: TEIID-292 > URL: https://jira.jboss.org/jira/browse/TEIID-292 > Project: Teiid > Issue Type: Task > Components: JDBC Driver > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.0.0 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > We could use non-nio client sockets to remove the netty library from the client. To allow for our current usage model, we would still need to allow for multi-threaded calls and client timeouts. We could optionally not use a separate reader thread. -- 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

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-421) Membership Domain Provider reference still exists after Provider deleted

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-421?page=com.atlassian.jira.plug... ] Steven Hawkins moved JBEDSP-986 to TEIID-421: --------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-421 (was: JBEDSP-986) Issue Type: Feature Request (was: Bug) Component/s: Console (was: Console) Fix Version/s: 6.1.0 (was: 5.5.3 CCE) Affects Version/s: 6.0.0 (was: 5.5.2) > Membership Domain Provider reference still exists after Provider deleted > ------------------------------------------------------------------------ > > Key: TEIID-421 > URL: https://jira.jboss.org/jira/browse/TEIID-421 > Project: Teiid > Issue Type: Feature Request > Components: Console > Affects Versions: 6.0.0 > Environment: Windows client running against Windows server > Reporter: Warren Gibson > Fix For: 6.1.0 > > > 1. Had two Membership Domain Providers in Console. > 2. Deleted 1 Provider. > 3. Exit Console > 4. Started Console > 5. Started to add more Admin Roles. > 6. The Select Group (Step 1) screen has a drop down for Domain. > 7. The drop down still shows the previously deleted Membership Domain Provider even though it doesn't exist. -- 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

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Moved: (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 moved JBEDSP-985 to TEIID-420: --------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-420 (was: JBEDSP-985) Component/s: Console (was: Console) Fix Version/s: 6.1.0 (was: 5.5.3 CCE) Affects Version/s: 6.0.0 (was: 5.5.2) > 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 > 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

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-419) Missing message for key "WorkerPool.New_thread" in: com.metamatrix.common.i18n

by Larry O'Leary (JIRA)

Missing message for key "WorkerPool.New_thread" in: com.metamatrix.common.i18n ------------------------------------------------------------------------------ Key: TEIID-419 URL: https://jira.jboss.org/jira/browse/TEIID-419 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 6.0.0 Reporter: Larry O'Leary Assignee: Steven Hawkins Priority: Minor Enabled trace logging with all context and ran some server side code and see a few of these in log output: <Missing message for key "WorkerPool.New_thread" in: com.metamatrix.common.i18n> -- 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

15 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-395) Command Log logs a modfieid version of MMCommand

by Larry O'Leary (JIRA)

Command Log logs a modfieid version of MMCommand ------------------------------------------------ Key: TEIID-395 URL: https://jira.jboss.org/jira/browse/TEIID-395 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.0.0 Reporter: Larry O'Leary Assignee: Larry O'Leary Fix For: 6.0.0 The FileCommandLogger may be logging a different user command than the command the user actually submitted. This was originally reported on 5.5.3 and may not affect Teiid but it should be verified and fixed if needed. Also, the tracking service interface should be modified to accept a String as the SQL command instead of a Command object. The Command object serves no purpose to the tracking service and a String will produce less overhead. -- 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

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Closed: (TEIID-54) Fix for NPE when handling LOB returned from a UDF

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-54?page=com.atlassian.jira.plugi... ] Steven Hawkins closed TEIID-54. ------------------------------- Resolution: Done Addressed with a fix to BufferManagerImpl > Fix for NPE when handling LOB returned from a UDF > ------------------------------------------------- > > Key: TEIID-54 > URL: https://jira.jboss.org/jira/browse/TEIID-54 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Environment: All server environments. > Reporter: Jerry Helbling > Assignee: Jerry Helbling > Priority: Minor > Fix For: 6.0.0 > > > Refer to internal case 185912. -- 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

15 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2009