April 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-457) In Admin Console, when a Connector is in "Not Started" state, the start button is grayed out

by Ramesh Reddy (JIRA)

In Admin Console, when a Connector is in "Not Started" state, the start button is grayed out -------------------------------------------------------------------------------------------- Key: TEIID-457 URL: https://jira.jboss.org/jira/browse/TEIID-457 Project: Teiid Issue Type: Bug Components: Console Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Priority: Minor Fix For: 6.1.0 In Console in the system state panel, if some reason the Connector is started due to errors, it shows "Show Error" button. However, after fixing the error, you have option to start the connector again, except for stop and start PSC. The start button should not be grayed out. -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-460) SOAP module should not depend on the common-internal

by Ramesh Reddy (JIRA)

SOAP module should not depend on the common-internal ---------------------------------------------------- Key: TEIID-460 URL: https://jira.jboss.org/jira/browse/TEIID-460 Project: Teiid Issue Type: Task Components: Common Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Minor Fix For: 6.1.0 Ths SOAP project module has common-internal as the dependency. This needs to be removed. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-458) Admin api server discovery should cache cluster information

by Steven Hawkins (JIRA)

Admin api server discovery should cache cluster information ----------------------------------------------------------- Key: TEIID-458 URL: https://jira.jboss.org/jira/browse/TEIID-458 Project: Teiid Issue Type: Task Components: JDBC Driver Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.1.0 See also TEIID-190. Our prior comm layer cached cluster information, this one should do the same to prevent excessive calls and to perform active discovery. -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-459) Minor shutdown issues

by Steven Hawkins (JIRA)

Minor shutdown issues --------------------- Key: TEIID-459 URL: https://jira.jboss.org/jira/browse/TEIID-459 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 Configuration service shutdown has a missing message key Registry shutdown may still have listeners that act against an invalid cache The ProcessConroller is adding a redundant shutdown hook ... -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-442) Simplify configuration mechanics

by Steven Hawkins (JIRA)

Simplify configuration mechanics -------------------------------- Key: TEIID-442 URL: https://jira.jboss.org/jira/browse/TEIID-442 Project: Teiid Issue Type: Task Components: Common, Console, Server Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 6.1.0 The current differentiation between start up and next startup is tenuous. After talking with Van and Ramesh a better simplified approach is to have a single live configuration, which essentially removes the notion of a startup configuration. As configuration changes are made, TEIID-441 will do a better job of informing the admin what should be restarted. When a host controller is asked to start processes it will save the current state of the configuration to the filesystem. And instead of keeping a single backup, we'll keep some rotating number of them. -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-454) VM and Queue statistics should represent the new pool stats

by Steven Hawkins (JIRA)

VM and Queue statistics should represent the new pool stats ----------------------------------------------------------- Key: TEIID-454 URL: https://jira.jboss.org/jira/browse/TEIID-454 Project: Teiid Issue Type: Bug Components: Common, Console Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 The workerpool changes were never fully propagated to the console/adminapi. We need to remove the notion of ephemeral stats (enqueued/dequeued/highwatermark), and instead expose more of the over all stats current/highest thread/queue and total submitted/completed. This also affects the queueworkerpool adminapi object. -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Closed: (TEIID-397) Console Error after changing Root Admin password

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-397?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-397. -------------------------------- Resolution: Done Removed the retry logic and added a specific message for authentication failure. > Console Error after changing Root Admin password > ------------------------------------------------ > > Key: TEIID-397 > URL: https://jira.jboss.org/jira/browse/TEIID-397 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.0.0 > Environment: Windows client running against Windows Server > Reporter: Warren Gibson > Assignee: Steven Hawkins > Fix For: 6.1.0 > > > 1. Went into Security/Summary and changed MetaMatrixAdmin password. > 2. Bounced the server. > 3. Console hung for about 10 minutes and finally returned with the below Error message. > 4. Console was unstable. > 5. Shut down Console and Restarted and everything seemed to be fine with the new password. > com.metamatrix.console.util.ExternalException[0]: com.metamatrix.api.exception.ComponentCommunicationException[0]: com.metamatrix.common.comm.exception.ConnectionException[0]: com.metamatrix.api.exception.security.LogonException[0]: [MetaMatrixAuthenticationException]The username "metamatrixadmin" and/or password and/or payload token could not be authenticated by any membership domain. > at com.metamatrix.platform.security.session.service.SessionServiceImpl.authenticateUser(SessionServiceImpl.java:431) > at com.metamatrix.platform.security.session.service.SessionServiceImpl.createSession(SessionServiceImpl.java:624) > at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.metamatrix.platform.service.proxy.SingleInvokationProxy.invoke(SingleInvokationProxy.java:48) > at $Proxy7.createSession(Unknown Source) > at com.metamatrix.platform.security.session.service.LogonHelper.logon(LogonHelper.java:69) > at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.metamatrix.platform.service.proxy.ProxyManager$WrappedDelegator.invoke(ProxyManager.java:41) > at $Proxy8.logon(Unknown Source) > at com.metamatrix.common.comm.platform.socket.SocketLogon.logon(SocketLogon.java:133) > at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) > 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.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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-456) Remove server db platform code

by Steven Hawkins (JIRA)

Remove server db platform code ------------------------------ Key: TEIID-456 URL: https://jira.jboss.org/jira/browse/TEIID-456 Project: Teiid Issue Type: Task Components: Server Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.1.0 Most of the platform code is unused and can have the logic that is used replaced easily. -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-443) Failure in JGroups Communication

by Ramesh Reddy (JIRA)

Failure in JGroups Communication -------------------------------- Key: TEIID-443 URL: https://jira.jboss.org/jira/browse/TEIID-443 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.1.0 ERROR Incoming-2,teiid,10.15.208.35:47163 org.jgroups.protocols.pbcast.NAKACK - failed reading retransmitted message java.io.IOException: failed reading header at org.jgroups.Message.readHeader(Message.java:787) at org.jgroups.Message.readFrom(Message.java:673) at org.jgroups.util.Util.byteBufferToMessage(Util.java:808) at org.jgroups.protocols.pbcast.NAKACK.handleXmitRsp(NAKACK.java:1038) at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:709) at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167) at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:308) at org.jgroups.protocols.MERGE2.up(MERGE2.java:144) at org.jgroups.protocols.Discovery.up(Discovery.java:263) at org.jgroups.protocols.TP.passMessageUp(TP.java:1275) at org.jgroups.protocols.TP.access$100(TP.java:49) at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1818) at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1797) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.InstantiationException: com.metamatrix.common.messaging.jgroups.JGroupsMessageBus$FederateHeader at java.lang.Class.newInstance0(Class.java:340) at java.lang.Class.newInstance(Class.java:308) at org.jgroups.Message.readHeader(Message.java:777) -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-418) Server Extensions should be loaded from a Extension classpath

by Ramesh Reddy (JIRA)

Server Extensions should be loaded from a Extension classpath ------------------------------------------------------------- Key: TEIID-418 URL: https://jira.jboss.org/jira/browse/TEIID-418 Project: Teiid Issue Type: Feature Request Components: Build/Kits, Common, Server Affects Versions: 6.x Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.1.0 Currently the MembershipDomain, CustomTracker load from libraries which are defined as part of the boot class path, these need to be loaded from the extension classpath, so that they can be added or removed without server re-start. -- 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, 9 months

2
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2009