[JBoss JIRA] (TEIID-2235) MetadataRepository scope confusion
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2235:
-------------------------------------
Summary: MetadataRepository scope confusion
Key: TEIID-2235
URL: https://issues.jboss.org/browse/TEIID-2235
Project: Teiid
Issue Type: Quality Risk
Components: Server
Affects Versions: 8.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
MetadataRepository instances are ill-defined as to their scope. In the worst case this means that present logic inappropriately chains off of shared instances.
We should clarify the scope of constructed instances and have an appropriate chaining implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIID-2208) NPE in server log when triggering operation from admin console
by Van Halbert (JIRA)
Van Halbert created TEIID-2208:
----------------------------------
Summary: NPE in server log when triggering operation from admin console
Key: TEIID-2208
URL: https://issues.jboss.org/browse/TEIID-2208
Project: Teiid
Issue Type: Bug
Components: Jopr Plugin
Affects Versions: 7.7.1
Reporter: Van Halbert
Assignee: Steven Hawkins
When using admin console, saw the following NPE in the server log:
08:15:40,928 ERROR [MeasurementManager] Could not get measurement values
java.lang.NullPointerException
at org.teiid.rhq.admin.DQPManagementView.getErrorCount(DQPManagementView.java:666)
at org.teiid.rhq.admin.DQPManagementView.getVdbMetric(DQPManagementView.java:158)
at org.teiid.rhq.admin.DQPManagementView.getMetric(DQPManagementView.java:110)
at org.teiid.rhq.plugin.VDBComponent.getValues(VDBComponent.java:178)
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:597)
at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
Not sure what combination of control operations that I pressed that caused this. And I've yet to duplicate.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIID-2216) Refreshing VDB display may show all VDBs as DOWN
by Paul Nittel (JIRA)
Paul Nittel created TEIID-2216:
----------------------------------
Summary: Refreshing VDB display may show all VDBs as DOWN
Key: TEIID-2216
URL: https://issues.jboss.org/browse/TEIID-2216
Project: Teiid
Issue Type: Bug
Components: Jopr Plugin
Reporter: Paul Nittel
Assignee: Steven Hawkins
Priority: Minor
I've noticed this on several occasions and it doesn't seem to be readily repeatable (sorry). Under the right(?) circumstances, refreshing the VDB display shows all the VDBs to be DOWN.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIID-2181) SYS queries should filter by schema/table
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2181:
-------------------------------------
Summary: SYS queries should filter by schema/table
Key: TEIID-2181
URL: https://issues.jboss.org/browse/TEIID-2181
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
The tables returned by datatiermanagerimpl are returned in full for each request generating a lot of tuple garbage. It would be better to allow filtering (ideally using schema/table name lookups) as we build the result.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIID-2212) IllegalStateException occuring during the shutdown of server when there is Dynamic VDB deployed
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2212:
-----------------------------------
Summary: IllegalStateException occuring during the shutdown of server when there is Dynamic VDB deployed
Key: TEIID-2212
URL: https://issues.jboss.org/browse/TEIID-2212
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.1
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.2
{code}
15:02:36,097 ERROR [org.jboss.as.server.deployment] JBAS015892: Deployment unit processor org.teiid.jboss.VDBDeployer@a63fe8 unexpectedly threw an exception during undeploy phase INSTALL of deployment "portfolio-vdb.xml": java.lang.IllegalStateException
at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.teiid.jboss.TeiidAdd$VDBStatusCheckerExecutorService.getVDBRepository(TeiidAdd.java:550)
at org.teiid.jboss.VDBDeployer.undeploy(VDBDeployer.java:351)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:167) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:161) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month