[JBoss JIRA] (TEIID-3689) StaxSource error with a comment
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3689:
-------------------------------------
Summary: StaxSource error with a comment
Key: TEIID-3689
URL: https://issues.jboss.org/browse/TEIID-3689
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.12
Having a stax source such as a streaming result from a web service that is processed by xmltable that contains comments will result in an exception such as:
14:39:23,673 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2) TEIID30019 Unexpected exception for request Wel3MG40y9Hs.0: java.lang.UnsupportedOperationException: append() method is not supported in this class
at net.sf.saxon.event.ProxyReceiver.append(ProxyReceiver.java:229) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.evpull.EventIteratorToReceiver.copy(EventIteratorToReceiver.java:50) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.event.Sender.sendPullEventSource(Sender.java:523) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.event.Sender.send(Sender.java:148) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.Configuration.buildDocument(Configuration.java:3317) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.Configuration.buildDocument(Configuration.java:3262) [saxonhe-9.2.1.5.jar:]
at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:152) [teiid-engine-8.7.3.redhat-2.jar:8.7.3.redhat-2]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (TEIID-3688) StaxSource error with a comment
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3688?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3688:
---------------------------------------
There are two issues here. One is that XMLEventStreamReader cannot handle comments, which doesn't seem to be a pervasive issue since there are no comments in the json to xml conversion and sources should return xml stream readers. The other issue is that the Saxon logic is incorrect in 9.2 - the append method should not be called at all. Rather the comment event should be directed to the comment method on the PathMapFilter. This is corrected in the later Saxon 9.5 - TEIID-3030
So this will need to be handled as two different issues and a fix for 8.7 will be more involved as we'll need to add append handling into the PathMapFilter.
> StaxSource error with a comment
> -------------------------------
>
> Key: TEIID-3688
> URL: https://issues.jboss.org/browse/TEIID-3688
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.12
>
>
> Having a stax source such as a streaming result from a web service that is processed by xmltable that contains comments will result in an exception such as:
> 14:39:23,673 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2) TEIID30019 Unexpected exception for request Wel3MG40y9Hs.0: java.lang.UnsupportedOperationException: append() method is not supported in this class
> at net.sf.saxon.event.ProxyReceiver.append(ProxyReceiver.java:229) [saxonhe-9.2.1.5.jar:]
> at net.sf.saxon.evpull.EventIteratorToReceiver.copy(EventIteratorToReceiver.java:50) [saxonhe-9.2.1.5.jar:]
> at net.sf.saxon.event.Sender.sendPullEventSource(Sender.java:523) [saxonhe-9.2.1.5.jar:]
> at net.sf.saxon.event.Sender.send(Sender.java:148) [saxonhe-9.2.1.5.jar:]
> at net.sf.saxon.Configuration.buildDocument(Configuration.java:3317) [saxonhe-9.2.1.5.jar:]
> at net.sf.saxon.Configuration.buildDocument(Configuration.java:3262) [saxonhe-9.2.1.5.jar:]
> at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:152) [teiid-engine-8.7.3.redhat-2.jar:8.7.3.redhat-2]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (TEIID-3688) StaxSource error with a comment
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3688?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3688:
----------------------------------
Description:
Having a stax source such as a streaming result from a web service that is processed by xmltable that contains comments will result in an exception such as:
14:39:23,673 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2) TEIID30019 Unexpected exception for request Wel3MG40y9Hs.0: java.lang.UnsupportedOperationException: append() method is not supported in this class
at net.sf.saxon.event.ProxyReceiver.append(ProxyReceiver.java:229) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.evpull.EventIteratorToReceiver.copy(EventIteratorToReceiver.java:50) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.event.Sender.sendPullEventSource(Sender.java:523) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.event.Sender.send(Sender.java:148) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.Configuration.buildDocument(Configuration.java:3317) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.Configuration.buildDocument(Configuration.java:3262) [saxonhe-9.2.1.5.jar:]
at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:152) [teiid-engine-8.7.3.redhat-2.jar:8.7.3.redhat-2]
was:
Having a stax source such as a streaming result from a web service that is processed by xmltable in a non-streaming fashion that contains comments will result in an exception such as:
14:39:23,673 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2) TEIID30019 Unexpected exception for request Wel3MG40y9Hs.0: java.lang.UnsupportedOperationException: append() method is not supported in this class
at net.sf.saxon.event.ProxyReceiver.append(ProxyReceiver.java:229) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.evpull.EventIteratorToReceiver.copy(EventIteratorToReceiver.java:50) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.event.Sender.sendPullEventSource(Sender.java:523) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.event.Sender.send(Sender.java:148) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.Configuration.buildDocument(Configuration.java:3317) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.Configuration.buildDocument(Configuration.java:3262) [saxonhe-9.2.1.5.jar:]
at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:152) [teiid-engine-8.7.3.redhat-2.jar:8.7.3.redhat-2]
Summary: StaxSource error with a comment (was: StaxSource processed without streaming error with a comment)
> StaxSource error with a comment
> -------------------------------
>
> Key: TEIID-3688
> URL: https://issues.jboss.org/browse/TEIID-3688
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.12
>
>
> Having a stax source such as a streaming result from a web service that is processed by xmltable that contains comments will result in an exception such as:
> 14:39:23,673 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2) TEIID30019 Unexpected exception for request Wel3MG40y9Hs.0: java.lang.UnsupportedOperationException: append() method is not supported in this class
> at net.sf.saxon.event.ProxyReceiver.append(ProxyReceiver.java:229) [saxonhe-9.2.1.5.jar:]
> at net.sf.saxon.evpull.EventIteratorToReceiver.copy(EventIteratorToReceiver.java:50) [saxonhe-9.2.1.5.jar:]
> at net.sf.saxon.event.Sender.sendPullEventSource(Sender.java:523) [saxonhe-9.2.1.5.jar:]
> at net.sf.saxon.event.Sender.send(Sender.java:148) [saxonhe-9.2.1.5.jar:]
> at net.sf.saxon.Configuration.buildDocument(Configuration.java:3317) [saxonhe-9.2.1.5.jar:]
> at net.sf.saxon.Configuration.buildDocument(Configuration.java:3262) [saxonhe-9.2.1.5.jar:]
> at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:152) [teiid-engine-8.7.3.redhat-2.jar:8.7.3.redhat-2]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (TEIID-3688) StaxSource processed without streaming error with a comment
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3688:
-------------------------------------
Summary: StaxSource processed without streaming error with a comment
Key: TEIID-3688
URL: https://issues.jboss.org/browse/TEIID-3688
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.12
Having a stax source such as a streaming result from a web service that is processed by xmltable in a non-streaming fashion that contains comments will result in an exception such as:
14:39:23,673 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2) TEIID30019 Unexpected exception for request Wel3MG40y9Hs.0: java.lang.UnsupportedOperationException: append() method is not supported in this class
at net.sf.saxon.event.ProxyReceiver.append(ProxyReceiver.java:229) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.evpull.EventIteratorToReceiver.copy(EventIteratorToReceiver.java:50) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.event.Sender.sendPullEventSource(Sender.java:523) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.event.Sender.send(Sender.java:148) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.Configuration.buildDocument(Configuration.java:3317) [saxonhe-9.2.1.5.jar:]
at net.sf.saxon.Configuration.buildDocument(Configuration.java:3262) [saxonhe-9.2.1.5.jar:]
at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:152) [teiid-engine-8.7.3.redhat-2.jar:8.7.3.redhat-2]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (TEIID-3684) RoleBasedCredentialMapIdentityLoginModule throws exception at startup time
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3684?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3684:
-------------------------------------
I think we should remove this LoginModule, I do not know of any one actually using this and does not see that useful anyways, as it is doing to role to password matching, and real world that seems unlikely.
> RoleBasedCredentialMapIdentityLoginModule throws exception at startup time
> --------------------------------------------------------------------------
>
> Key: TEIID-3684
> URL: https://issues.jboss.org/browse/TEIID-3684
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Ramesh Reddy
>
> If a data source is configured to use RoleBasedCredentialMapIdentityLoginModule, then exception is thrown at startup \[1\], because default username and password are null. Please, add module options "username" and "password" to set up default user (similar functionality have e.g. CallerIdentityLoginModule and PassthroughIdentityLoginModule), so DV is able to properly load data source at startup when no user is authenticated and therefore no mapping could be performed.
> Example configuration \[2\]. Note, there is no exception if UsersRoles login module is used instead of RealDirect. However, it means that EAP users are separate from DV users.
> *FYI:*
> - credentialMap module option should be defined as URL (file://...). It would be nice to have this information in the documentation.
> - I tried to use unauthenticatedIdentity module option for RealmDirect, but same exception has been thrown with different root cause (realm 'ApplicationRealm' not found). I do not know why.
> \[1\]
> ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-5) Exception during createSubject()PBOX000016: Access denied: authentication failed: java.lang.SecurityException: PBOX000016: Access denied: authentication failed
> at org.jboss.security.plugins.JBossSecuritySubjectFactory.createSubject(JBossSecuritySubjectFactory.java:84)
> at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:1084)
> at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:1079)
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0_40]
> at org.jboss.jca.deployers.common.AbstractDsDeployer.createSubject(AbstractDsDeployer.java:1078)
> at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:600)
> at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:282)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:316)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:120)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_40]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_40]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_40]
> \[2\]
> {code:xml}
> <security-domain name="my-sec">
> <authentication>
> <login-module code="RealmDirect" flag="required">
> <module-option name="password-stacking" value="tryFirstPass"/>
> <!--<module-option name="unauthenticatedIdentity" value="guest"/>-->
> </login-module>
> <login-module code="org.teiid.jboss.RoleBasedCredentialMapIdentityLoginModule" module="org.jboss.teiid" flag="required">
> <module-option name="password-stacking" value="useFirstPass"/>
> <module-option name="credentialMap" value="file://${jboss.server.config.dir}/teiid-credentialmap.properties"/>
> </login-module>
> </authentication>
> </security-domain>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (TEIID-3684) RoleBasedCredentialMapIdentityLoginModule throws exception at startup time
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3684?page=com.atlassian.jira.plugin... ]
Ramesh Reddy reassigned TEIID-3684:
-----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> RoleBasedCredentialMapIdentityLoginModule throws exception at startup time
> --------------------------------------------------------------------------
>
> Key: TEIID-3684
> URL: https://issues.jboss.org/browse/TEIID-3684
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Ramesh Reddy
>
> If a data source is configured to use RoleBasedCredentialMapIdentityLoginModule, then exception is thrown at startup \[1\], because default username and password are null. Please, add module options "username" and "password" to set up default user (similar functionality have e.g. CallerIdentityLoginModule and PassthroughIdentityLoginModule), so DV is able to properly load data source at startup when no user is authenticated and therefore no mapping could be performed.
> Example configuration \[2\]. Note, there is no exception if UsersRoles login module is used instead of RealDirect. However, it means that EAP users are separate from DV users.
> *FYI:*
> - credentialMap module option should be defined as URL (file://...). It would be nice to have this information in the documentation.
> - I tried to use unauthenticatedIdentity module option for RealmDirect, but same exception has been thrown with different root cause (realm 'ApplicationRealm' not found). I do not know why.
> \[1\]
> ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-5) Exception during createSubject()PBOX000016: Access denied: authentication failed: java.lang.SecurityException: PBOX000016: Access denied: authentication failed
> at org.jboss.security.plugins.JBossSecuritySubjectFactory.createSubject(JBossSecuritySubjectFactory.java:84)
> at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:1084)
> at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:1079)
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0_40]
> at org.jboss.jca.deployers.common.AbstractDsDeployer.createSubject(AbstractDsDeployer.java:1078)
> at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:600)
> at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:282)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:316)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:120)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_40]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_40]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_40]
> \[2\]
> {code:xml}
> <security-domain name="my-sec">
> <authentication>
> <login-module code="RealmDirect" flag="required">
> <module-option name="password-stacking" value="tryFirstPass"/>
> <!--<module-option name="unauthenticatedIdentity" value="guest"/>-->
> </login-module>
> <login-module code="org.teiid.jboss.RoleBasedCredentialMapIdentityLoginModule" module="org.jboss.teiid" flag="required">
> <module-option name="password-stacking" value="useFirstPass"/>
> <module-option name="credentialMap" value="file://${jboss.server.config.dir}/teiid-credentialmap.properties"/>
> </login-module>
> </authentication>
> </security-domain>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (TEIID-3685) org.teiid.padSpace does not affect to the "IN" operator
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3685?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3685.
-----------------------------------
Fix Version/s: 8.12
8.11.4
Resolution: Done
The issue here is that we were creating a hash set for non-hashable values, which results in no match when a match is expected. This should be considered for backport as well.
> org.teiid.padSpace does not affect to the "IN" operator
> -------------------------------------------------------
>
> Key: TEIID-3685
> URL: https://issues.jboss.org/browse/TEIID-3685
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7.1
> Environment: JBoss DV 6.1.2
> Reporter: hisao furuichi
> Assignee: Steven Hawkins
> Fix For: 8.12, 8.11.4
>
> Attachments: datasert.csv, INTERNAL_TEST.zip
>
>
> org.teiid.padSpace does affect to "=" operator. But does not affect to "IN" operator.
> [data for a column named "id"]
> {noformat}
> "test1 "
> {noformat}
> ["=" operator] I can get a result
> {noformat}
> SELECT * FROM ViewModel.originalViewTable WHERE ViewModel.originalViewTable.id ='TEST1';
> {noformat}
> ["IN" operator] I can not get a result
> {noformat}
> SELECT * FROM ViewModel.originalViewTable WHERE ViewModel.originalViewTable.id IN ('TEST1', 'TEST2');
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (TEIID-3686) OData DELETE nonexisting row - wrong response code
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3686?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3686.
---------------------------------
Fix Version/s: 8.12
Resolution: Done
Labels: CR1 (was: )
Added check to see if the entity is found or not for delete and update operations, and then return the right response codes
success - 200 OK
not-found - 404
update-success - 204 no-content
> OData DELETE nonexisting row - wrong response code
> --------------------------------------------------
>
> Key: TEIID-3686
> URL: https://issues.jboss.org/browse/TEIID-3686
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.7.1.6_2
> Reporter: Michal Sanitrak
> Assignee: Ramesh Reddy
> Labels: CR1
> Fix For: 8.12
>
>
> I deployed VDB that can be accessed with OData. When I perform DELETE request to remove row for first time response code is 200 OK (maybe it should be 204) but when I repeat the same DELETE request and tried to delete already deleted entry, response is again 200 OK, but it should be 404 Not Found. Same thing happens even I when tried to delete entry with id that doesn't exist at all.
> Only indication of this problem is in the server log:
> {code:plain}INFO [org.teiid.ODATA] (http-/127.0.0.1:8080-1) no entity to delete in = BooksMySQL.BOOKS with key= ('1')
> {code}
> I think that response code for deleting row that doesn't exist should be different than 200 OK.
> For example the service at odata.org returns following content with response code 404 Not Found:
> {code:xml}
> <?xml version="1.0" encoding="utf-8" standalone="yes"?>
> <error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
> <code></code>
> <message xml:lang="en-US">Resource not found for the segment 'Products'.</message>
> </error>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months