April 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Moved: (TEIID-521) Prepared statement methods addBatch() and clearBatch() can cause NullPointerException

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-521?page=com.atlassian.jira.plug... ] Steven Hawkins moved JBEDSP-1017 to TEIID-521: ---------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-521 (was: JBEDSP-1017) Component/s: JDBC Connector (was: JDBC) Affects Version/s: 6.0.0 (was: 5.5.3) (was: 5.5.2) > Prepared statement methods addBatch() and clearBatch() can cause NullPointerException > ------------------------------------------------------------------------------------- > > Key: TEIID-521 > URL: https://jira.jboss.org/jira/browse/TEIID-521 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 6.0.0 > Reporter: Larry O'Leary > Fix For: 6.1.0 > > > When attempting to debug an unrelated issue I discovered that the batch processing methods on a prepared statement can result in a NullPointerException depending on when the methods are called. > For example: > java.lang.NullPointerException > at com.metamatrix.jdbc.MMStatement.clearBatch(MMStatement.java:274) > at com.metamatrix.jdbc.TestPreparedStatementBatchedUpdate.testInserts(TestPreparedStatementBatchedUpdate.java:102) > 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 junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) > Is a result of calling clearBatch() on a statement after it was done executing a batched update. It appears this is simply a need of NOT calling clearBatch() at the wrong time but I feel that we should gracefully handle this situation as a clearBatch() call may appear in a try/catch/finally block. > The same goes for addBatch() if no parameters have been set. Not sure if we should actually throw an exception in such a case or not as it makes no sense to call addBatch() with no parameters defined but it would also make sense that we would not throw a nasty NPE in such a case. > I have only seen this on R050502 and R050503 and have not looked at R050504c or Teiid. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-521) Prepared statement methods addBatch() and clearBatch() can cause NullPointerException

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-521?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-521: --------------------------------- Fix Version/s: 6.1.0 Complexity: Low > Prepared statement methods addBatch() and clearBatch() can cause NullPointerException > ------------------------------------------------------------------------------------- > > Key: TEIID-521 > URL: https://jira.jboss.org/jira/browse/TEIID-521 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 6.0.0 > Reporter: Larry O'Leary > Fix For: 6.1.0 > > > When attempting to debug an unrelated issue I discovered that the batch processing methods on a prepared statement can result in a NullPointerException depending on when the methods are called. > For example: > java.lang.NullPointerException > at com.metamatrix.jdbc.MMStatement.clearBatch(MMStatement.java:274) > at com.metamatrix.jdbc.TestPreparedStatementBatchedUpdate.testInserts(TestPreparedStatementBatchedUpdate.java:102) > 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 junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) > Is a result of calling clearBatch() on a statement after it was done executing a batched update. It appears this is simply a need of NOT calling clearBatch() at the wrong time but I feel that we should gracefully handle this situation as a clearBatch() call may appear in a try/catch/finally block. > The same goes for addBatch() if no parameters have been set. Not sure if we should actually throw an exception in such a case or not as it makes no sense to call addBatch() with no parameters defined but it would also make sense that we would not throw a nasty NPE in such a case. > I have only seen this on R050502 and R050503 and have not looked at R050504c or Teiid. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-520) removing the Resource Connection Pool administration option in the console for Westport.

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-520?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-520: --------------------------------- Fix Version/s: 6.1.0 > removing the Resource Connection Pool administration option in the console for Westport. > ---------------------------------------------------------------------------------------- > > Key: TEIID-520 > URL: https://jira.jboss.org/jira/browse/TEIID-520 > Project: Teiid > Issue Type: Feature Request > Components: Console, Documentation > Affects Versions: Westport > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: Westport > > > removing the Resource Connection Pool administration option in the console for Westport. > Why? > 1. Because we developed 2 connection pooling frameworks in our product, and we don't need them both > 2. The Resource Connection Pool never became a feature of any value to the product, just overhead in the maintenance department > 3. Removing it from exposure will enable the server to eliminate multiple locations of connection properties (1. config.xml and 2. metamatrix.properties). The config.xml will no longer contain the ConnectionPool section. > 4. Remove any confusion in the console as to administrating the connection pool. > However, the monitoring of the Resource Connection Pool will still be seen in the console, so that monitoring of the connections can still be done (unless there's a decision to remove it also). -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-517) Deploying VDB attempts by Product Admin has unnecessary steps before advising user they are "not authorized"

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-517?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-517: --------------------------------- Fix Version/s: 6.1.1 > Deploying VDB attempts by Product Admin has unnecessary steps before advising user they are "not authorized" > ------------------------------------------------------------------------------------------------------------ > > Key: TEIID-517 > URL: https://jira.jboss.org/jira/browse/TEIID-517 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.0.0 > Environment: Windows client running Console and Windows server running MetaMatrix server > Reporter: Warren Gibson > Priority: Minor > Fix For: 6.1.1 > > > ReadOnly Admin is not authorized to deploy VDBs and is presented all grayed out buttons on the Virtual Databases screen except for the Export button. > ProductAdmin is also not authrized to deploy VDBs but all the buttons on the Virtual Databases screen are activated and the user can go through several steps in the New Virtual Database Wizard before selecting the Finish button at which time they are informed: "The client is not authorized to attempt this operation". The ProductAdmin interface should be the same as the ReadOnly Admin since they are both not authorized to deploy VDBs. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-515) Console View > Refresh does not show values changed by mmadmin

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-515?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-515: --------------------------------- Fix Version/s: 6.1.1 > Console View > Refresh does not show values changed by mmadmin > -------------------------------------------------------------- > > Key: TEIID-515 > URL: https://jira.jboss.org/jira/browse/TEIID-515 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Paul Nittel > Assignee: Ramesh Reddy > Priority: Minor > Fix For: 6.1.1 > > > I ran a script through mmadmin and did setSystemProperty("metamatrix.audit.enabled", "false" ). From the Console, the value does not appear to have changed. View > Refresh does nothing. Switching from the System Properties panel to another and then back does nothing. Only exiting the Console showed the new value. > (Hey, "Console" isn't a JIRA component?) -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-516) Importing a VDB via Console does not refresh the Bindings panel to show new bindings

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-516?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-516: --------------------------------- Fix Version/s: 6.1.1 > Importing a VDB via Console does not refresh the Bindings panel to show new bindings > ------------------------------------------------------------------------------------ > > Key: TEIID-516 > URL: https://jira.jboss.org/jira/browse/TEIID-516 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Paul Nittel > Priority: Minor > Fix For: 6.1.1 > > Attachments: ODBCvdb.vdb > > > If I import a VDB and then switch to the Connector Bindings panel, I must click View > Refresh to be able to see the added bindings. I'm quite sure this used to happen without manually refreshing. > I'll attach a VDB so you can try it! -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-519) move datasource and metamatrix command logging to logging configuration

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-519?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-519: --------------------------------- Fix Version/s: 6.1.1 > move datasource and metamatrix command logging to logging configuration > ----------------------------------------------------------------------- > > Key: TEIID-519 > URL: https://jira.jboss.org/jira/browse/TEIID-519 > Project: Teiid > Issue Type: Quality Risk > Components: Console > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.1.1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > move datasource and metamatrix command logging to logging configuration. They are currently under transaction, but logically belong under logging. References to these properties in the Tracking service will need to be updated as well. Values passed into custom command loggers should be based off of the old property names for backward compatibility. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-518) Invalid Message in Console Deploying VDB

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-518?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-518: --------------------------------- Fix Version/s: 6.1.1 > Invalid Message in Console Deploying VDB > ---------------------------------------- > > Key: TEIID-518 > URL: https://jira.jboss.org/jira/browse/TEIID-518 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.0.0 > Reporter: Ted Jones > Fix For: 6.1.1 > > Attachments: snapshot1.png > > > I deployed a new VDB in the console using a VDB from the repository that had connector binding defined. The message I received prior to deployment was the all models had binding associated with them and the VDB would be deployed with the status of INACTIVE. Should be ACTIVE (and was deployed as such). -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-330) Need a better runtimestate monitor in the console

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-330?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-330: --------------------------------- Fix Version/s: 6.1.1 (was: 6.1.0) Priority: Minor (was: Major) > Need a better runtimestate monitor in the console > ------------------------------------------------- > > Key: TEIID-330 > URL: https://jira.jboss.org/jira/browse/TEIID-330 > Project: Teiid > Issue Type: Task > Components: Console > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.1.1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > As part of other refactorings, the runtimestate refresh was changed from a server push to a console poll. We should add a method to quickly determine whether there has been a state change rather than pulling the entire state at a low refresh rate. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-330) Need a better runtimestate monitor in the console

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-330?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-330: --------------------------------- Assignee: (was: Steven Hawkins) > Need a better runtimestate monitor in the console > ------------------------------------------------- > > Key: TEIID-330 > URL: https://jira.jboss.org/jira/browse/TEIID-330 > Project: Teiid > Issue Type: Task > Components: Console > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Minor > Fix For: 6.1.1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > As part of other refactorings, the runtimestate refresh was changed from a server push to a console poll. We should add a method to quickly determine whether there has been a state change rather than pulling the entire state at a low refresh rate. -- 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, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2009