[JBoss JIRA] (TEIID-2719) IllegalAccessError When OData URL is invoked
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2719?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2719.
---------------------------------
Labels: Beta1 (was: )
Resolution: Done
Modified the WAR file classpath (re-shuffled it), that seem to fix it, but I have to say I do not fully understand why this occurred. The same setup worked worked before with out any issues before. Added a integration test to to make sure it works before a release.
The integration test involves automatic upgrading of the RestEasy jars for OData fix that is required.
> IllegalAccessError When OData URL is invoked
> --------------------------------------------
>
> Key: TEIID-2719
> URL: https://issues.jboss.org/browse/TEIID-2719
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.6
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: Beta1
> Fix For: 8.6
>
>
> Any OData access invoked throws exception
> {code}
> Caused by: java.lang.IllegalAccessError: tried to access class org.teiid.jdbc.SocketProfile from class org.teiid.jdbc.TeiidDriver
> at org.teiid.jdbc.TeiidDriver.<init>(TeiidDriver.java:72) [teiid-admin-8.6.0.Alpha3-SNAPSHOT.jar:8.6.0.Alpha3-SNAPSHOT]
> at org.teiid.jdbc.TeiidDriver.<clinit>(TeiidDriver.java:60) [teiid-admin-8.6.0.Alpha3-SNAPSHOT.jar:8.6.0.Alpha3-SNAPSHOT]
> at org.teiid.odata.LocalClient.<init>(LocalClient.java:89) [classes:]
> at org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:78) [classes:]
> at org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:37) [classes:]
> at org.odata4j.producer.resources.BaseResource.getODataProducer(BaseResource.java:119) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.odata4j.producer.resources.EntitiesRequestResource.getEntities(EntitiesRequestResource.java:264) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_35]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_35]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_35]
> at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_35]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.7.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.7.Final.jar:]
> ... 20 more
> {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
10 years, 6 months
[JBoss JIRA] (TEIID-2718) NPE During OData Access
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2718?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2718.
---------------------------------
Fix Version/s: 8.4.1
Resolution: Done
Fixed the error message when non-existent VDB is queried. Corrected NPE, by correcting access to table that has unique key but does not have PK.
> NPE During OData Access
> -----------------------
>
> Key: TEIID-2718
> URL: https://issues.jboss.org/browse/TEIID-2718
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.4.1, 8.6
>
>
> While issuing a query like
> {code}
> http://localhost:8080/odata/{vdb-name}.1/SYS.Properties
> {code}
> it resulted in
> {code}
> 12:07:38,308 ERROR [org.teiid.ODATA] (http-/127.0.0.1:8080-2) null TEIID16013 Error occured producing OData result.: java.lang.NullPointerException
> at org.teiid.odata.ODataSQLBuilder.selectString(ODataSQLBuilder.java:210) [classes:]
> at org.teiid.odata.TeiidProducer.getNavProperty(TeiidProducer.java:86) [classes:]
> at org.teiid.odata.TeiidProducer.getEntities(TeiidProducer.java:79) [classes:]
> at org.odata4j.producer.resources.EntitiesRequestResource.getEntitiesImpl(EntitiesRequestResource.java:371) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.odata4j.producer.resources.EntitiesRequestResource.getEntities(EntitiesRequestResource.java:266) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_35]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_35]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_35]
> at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_35]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:97) [classes:]
> at org.teiid.odata.ODataServlet.service(ODataServlet.java:61) [classes:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-red
> {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
10 years, 6 months
[JBoss JIRA] (TEIID-2721) Resolving an aliased view prevents inherent update from working
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2721?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2721:
----------------------------------
Attachment: 2721-77x.patch
Patch for the older branch with an adapted test case.
> Resolving an aliased view prevents inherent update from working
> ---------------------------------------------------------------
>
> Key: TEIID-2721
> URL: https://issues.jboss.org/browse/TEIID-2721
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.6
>
> Attachments: 2721-77x.patch
>
>
> If an aliased form of an inherently updatable view is resolved first, we will cache invalid update info which prevents inherent insert/update from functioning correctly.
> For example with the view gx, first running:
> select * from gx as x
>
> will prevent an inherent insert such as:
> insert into gx (e1, e2, e3, e4) select * from pm1.g1
> from working as expected
--
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
10 years, 6 months
[JBoss JIRA] (TEIID-2721) Resolving an aliased view prevents inherent update from working
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2721?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2721.
-----------------------------------
Fix Version/s: 8.6
Resolution: Done
The fix is to ensure that the update validator uses the proper view symbols.
This should be rare on 8.0+ as the metadata validation will properly initialize the cached metadata, but since the entries can expire from the cache it's possible that it could occur.
> Resolving an aliased view prevents inherent update from working
> ---------------------------------------------------------------
>
> Key: TEIID-2721
> URL: https://issues.jboss.org/browse/TEIID-2721
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.6
>
> Attachments: 2721-77x.patch
>
>
> If an aliased form of an inherently updatable view is resolved first, we will cache invalid update info which prevents inherent insert/update from functioning correctly.
> For example with the view gx, first running:
> select * from gx as x
>
> will prevent an inherent insert such as:
> insert into gx (e1, e2, e3, e4) select * from pm1.g1
> from working as expected
--
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
10 years, 6 months
[JBoss JIRA] (TEIID-2721) Resolving an aliased view prevents inherent update from working
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2721:
-------------------------------------
Summary: Resolving an aliased view prevents inherent update from working
Key: TEIID-2721
URL: https://issues.jboss.org/browse/TEIID-2721
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
If an aliased form of an inherently updatable view is resolved first, we will cache invalid update info which prevents inherent insert/update from functioning correctly.
For example with the view gx, first running:
select * from gx as x
will prevent an inherent insert such as:
insert into gx (e1, e2, e3, e4) select * from pm1.g1
from working as expected
--
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
10 years, 6 months