[JBoss JIRA] (TEIID-3584) NoSuchMethodError when issuing show plan request -IBM JDK 1.6
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3584?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3584:
---------------------------------------
This must be an issue with the IBM JRE (and may have been addressed in a later version of their JRE) as the method is expected - http://docs.oracle.com/javase/6/docs/api/javax/xml/stream/XMLOutputFactor...
In any case, given that 1.6 is out of support, I would mark this as won't fix.
> NoSuchMethodError when issuing show plan request -IBM JDK 1.6
> -------------------------------------------------------------
>
> Key: TEIID-3584
> URL: https://issues.jboss.org/browse/TEIID-3584
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 8.7.1
> Environment: IBM JDK 1.6
> Reporter: Filip Elias
> Assignee: Steven Hawkins
>
> Teiid client throws an error[1] when processing "show plan;" request. This issue exist only on IBM jdk 1.6. The error is thrown at client side.
> [1]
> {code}
> Exception in thread "main" java.lang.NoSuchMethodError: javax/xml/stream/XMLOutputFactory.newFactory()Ljavax/xml/stream/XMLOutputFactory;
> at org.teiid.client.plan.PlanNode.toXml(PlanNode.java:175)
> at org.teiid.jdbc.StatementImpl.executeShow(StatementImpl.java:556)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:502)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:393)
> at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:327)
> at JDBCClient.execute(JDBCClient.java:93)
> at JDBCClient.main(JDBCClient.java:47)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3584) NoSuchMethodError when issuing show plan request -IBM JDK 1.6
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3584?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-3584:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1245158
> NoSuchMethodError when issuing show plan request -IBM JDK 1.6
> -------------------------------------------------------------
>
> Key: TEIID-3584
> URL: https://issues.jboss.org/browse/TEIID-3584
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 8.7.1
> Environment: IBM JDK 1.6
> Reporter: Filip Elias
> Assignee: Steven Hawkins
>
> Teiid client throws an error[1] when processing "show plan;" request. This issue exist only on IBM jdk 1.6. The error is thrown at client side.
> [1]
> {code}
> Exception in thread "main" java.lang.NoSuchMethodError: javax/xml/stream/XMLOutputFactory.newFactory()Ljavax/xml/stream/XMLOutputFactory;
> at org.teiid.client.plan.PlanNode.toXml(PlanNode.java:175)
> at org.teiid.jdbc.StatementImpl.executeShow(StatementImpl.java:556)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:502)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:393)
> at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:327)
> at JDBCClient.execute(JDBCClient.java:93)
> at JDBCClient.main(JDBCClient.java:47)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3584) NoSuchMethodError when issuing show plan request -IBM JDK 1.6
by Filip Elias (JIRA)
Filip Elias created TEIID-3584:
----------------------------------
Summary: NoSuchMethodError when issuing show plan request -IBM JDK 1.6
Key: TEIID-3584
URL: https://issues.jboss.org/browse/TEIID-3584
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Affects Versions: 8.7.1
Environment: IBM JDK 1.6
Reporter: Filip Elias
Assignee: Steven Hawkins
Teiid client throws an error[1] when processing "show plan;" request. This issue exist only on IBM jdk 1.6. The error is thrown at client side.
[1]
{code}
Exception in thread "main" java.lang.NoSuchMethodError: javax/xml/stream/XMLOutputFactory.newFactory()Ljavax/xml/stream/XMLOutputFactory;
at org.teiid.client.plan.PlanNode.toXml(PlanNode.java:175)
at org.teiid.jdbc.StatementImpl.executeShow(StatementImpl.java:556)
at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:502)
at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:393)
at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:327)
at JDBCClient.execute(JDBCClient.java:93)
at JDBCClient.main(JDBCClient.java:47)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3583) Need documentation on possible property settings to use
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3583?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3583:
---------------------------------------
> what is considered a large intermediate results
scrolling cursors or sorting over millions of rows
> how much to increase max-processing-kb based on how large
> how much to decrease max-reserve-kb base on how large
My belief it that we shouldn't be too specific here as this is reactive / based upon the workload and already an uncommon case - large intermediate results and ideally a low query volume. Given the amount to increase / decrease is highly dependent upon the query / workload specifics it seems more straight-forward to describe the concept. It would probably make just as much sense to just reference this scenario or auto-tune for example we perform more than a 2-pass sort due to memory being held by other processing - rather than expecting anyone to make the determination on their own.
> Need documentation on possible property settings to use
> -------------------------------------------------------
>
> Key: TEIID-3583
> URL: https://issues.jboss.org/browse/TEIID-3583
> Project: Teiid
> Issue Type: Enhancement
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> In the Administration and Configuration Guide there is some indication on how to perform active heap throttling.
> "Memory Management Considerations " there is a reference to parameters like:
> max-processing-kb and the max-reserve-kb.
> Anyway there is no indication of the indicative values to associate to those parameters to obtain a certain result.
> It would be good to get some examples to understand the cause and effect of the changes ( max-reserve-kb and related settings ).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3583) Need documentation on possible property settings to use
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3583?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-3583:
------------------------------------
example, the doc says:
In systems where large intermediate results are normal (scrolling cursors or sorting over millions of rows) you can consider increasing the max-processing-kb and decreasing the max-reserve-kb so that each request has access to an effectively smaller buffer space.
Looking at the above statement, how can quantity boundaries be applied?
- what is considered a large intermediate results
- how much to increase max-processing-kb based on how large
- how much to decrease max-reserve-kb base on how large
> Need documentation on possible property settings to use
> -------------------------------------------------------
>
> Key: TEIID-3583
> URL: https://issues.jboss.org/browse/TEIID-3583
> Project: Teiid
> Issue Type: Enhancement
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> In the Administration and Configuration Guide there is some indication on how to perform active heap throttling.
> "Memory Management Considerations " there is a reference to parameters like:
> max-processing-kb and the max-reserve-kb.
> Anyway there is no indication of the indicative values to associate to those parameters to obtain a certain result.
> It would be good to get some examples to understand the cause and effect of the changes ( max-reserve-kb and related settings ).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3492) Provide a mechanism for users to modify the salesforce api version
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3492?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3492:
---------------------------------------
> So, in that case there is no real precedent for us to provide version 34 and lock ourselves in.
Except for ease of use.
> We can provide a template project with all the required changes except version information, that user can provide and build and follow deploy instructions. Is that seems like viable approach?
That seems to be about it. Unless sf release a true api layer or we radically alter our code there's just no good way of doing this. So we'd expect them to extend the translator and use a different translator name, create an updated sf module and a new rar that reference the updated module.
> Provide a mechanism for users to modify the salesforce api version
> ------------------------------------------------------------------
>
> Key: TEIID-3492
> URL: https://issues.jboss.org/browse/TEIID-3492
> Project: Teiid
> Issue Type: Feature Request
> Components: Salesforce Connector
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 8.12
>
>
> We should provide a mechanism to easily target a different salesforce api version. We are currently defaulting to v22, which is quite old. The version change must be controlled as the metadata and the sf jars can be incompatible - if you for example build a model from v22, then you must stay on v22, and then recreate the model once you want to move to a later version.
> Currently the update procedure would be to copy/modify the salesforce translator module and have it point to newer wsc and partner api jars (which are java api compatible from what I have seen) and then change the any salesforce resource adapters to use the new api url.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3583) Need documentation on possible property settings to use
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3583?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3583:
---------------------------------------
Is this a community, product issue or both? https://docs.jboss.org/author/display/TEIID/Memory+Management does explain both properties and they which are typically left to the defaults (which is explained / calculated) and the rationale for changes explained. What else is needed on the community side?
> Need documentation on possible property settings to use
> -------------------------------------------------------
>
> Key: TEIID-3583
> URL: https://issues.jboss.org/browse/TEIID-3583
> Project: Teiid
> Issue Type: Enhancement
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> In the Administration and Configuration Guide there is some indication on how to perform active heap throttling.
> "Memory Management Considerations " there is a reference to parameters like:
> max-processing-kb and the max-reserve-kb.
> Anyway there is no indication of the indicative values to associate to those parameters to obtain a certain result.
> It would be good to get some examples to understand the cause and effect of the changes ( max-reserve-kb and related settings ).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3575) ODBC: NullPointerException after accessing non existing vdb
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3575?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3575:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1243500|https://bugzilla.redhat.com/show_bug.cgi?id=1243500] from NEW to MODIFIED
> ODBC: NullPointerException after accessing non existing vdb
> -----------------------------------------------------------
>
> Key: TEIID-3575
> URL: https://issues.jboss.org/browse/TEIID-3575
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7.1.6_2
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Fix For: 8.7.1.6_2
>
>
> When trying to access non existing vdb via ODBC driver, two exception stack traces are written into server console. One complains about non-existing vdb. The second is NullPointerException.
> The first part of this problem is connected to TEIID-3574 . The other part - NullPointerException - is unique to this issue.
> # LogonException
> {code:plain}
> 11:01:14,919 ERROR [org.teiid.ODBC] (New I/O worker #7) TEIID40015 Unexpected error occurred: org.teiid.client.security.LogonException: TEIID40046 VDB "TextEmployeeCombined" version "latest" does not exist.
> at org.teiid.services.SessionServiceImpl.getAuthenticationType(SessionServiceImpl.java:479) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.odbc.ODBCServerRemoteImpl.getAuthenticationType(ODBCServerRemoteImpl.java:219) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.odbc.ODBCServerRemoteImpl.initialize(ODBCServerRemoteImpl.java:197) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at sun.reflect.GeneratedMethodAccessor190.invoke(Unknown Source) [:1.7.0_75]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_75]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_75]
> at org.teiid.transport.ODBCClientInstance.processMessage(ODBCClientInstance.java:127) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.transport.ODBCClientInstance.receivedMessage(ODBCClientInstance.java:116) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:211) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:328) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]
> Caused by: org.teiid.dqp.service.SessionServiceException: TEIID40046 VDB "TextEmployeeCombined" version "latest" does not exist.
> at org.teiid.services.SessionServiceImpl.getActiveVDB(SessionServiceImpl.java:269) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.services.SessionServiceImpl.getAuthenticationType(SessionServiceImpl.java:477) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> ... 30 more
> {code}
> # NullPointerException
> {code:plain}
> 11:01:14,928 ERROR [org.teiid.ODBC] (New I/O worker #7) TEIID40015 Unexpected error occurred: java.lang.NullPointerException
> at org.teiid.odbc.ODBCServerRemoteImpl.initialize(ODBCServerRemoteImpl.java:203) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at sun.reflect.GeneratedMethodAccessor190.invoke(Unknown Source) [:1.7.0_75]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_75]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_75]
> at org.teiid.transport.ODBCClientInstance.processMessage(ODBCClientInstance.java:127) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.transport.ODBCClientInstance.receivedMessage(ODBCClientInstance.java:116) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:211) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:328) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3575) ODBC: NullPointerException after accessing non existing vdb
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3575?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3575.
-----------------------------------
Resolution: Done
Added a targeted back port and included another one from TEIID-3568
> ODBC: NullPointerException after accessing non existing vdb
> -----------------------------------------------------------
>
> Key: TEIID-3575
> URL: https://issues.jboss.org/browse/TEIID-3575
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7.1.6_2
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Fix For: 8.7.1.6_2
>
>
> When trying to access non existing vdb via ODBC driver, two exception stack traces are written into server console. One complains about non-existing vdb. The second is NullPointerException.
> The first part of this problem is connected to TEIID-3574 . The other part - NullPointerException - is unique to this issue.
> # LogonException
> {code:plain}
> 11:01:14,919 ERROR [org.teiid.ODBC] (New I/O worker #7) TEIID40015 Unexpected error occurred: org.teiid.client.security.LogonException: TEIID40046 VDB "TextEmployeeCombined" version "latest" does not exist.
> at org.teiid.services.SessionServiceImpl.getAuthenticationType(SessionServiceImpl.java:479) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.odbc.ODBCServerRemoteImpl.getAuthenticationType(ODBCServerRemoteImpl.java:219) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.odbc.ODBCServerRemoteImpl.initialize(ODBCServerRemoteImpl.java:197) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at sun.reflect.GeneratedMethodAccessor190.invoke(Unknown Source) [:1.7.0_75]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_75]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_75]
> at org.teiid.transport.ODBCClientInstance.processMessage(ODBCClientInstance.java:127) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.transport.ODBCClientInstance.receivedMessage(ODBCClientInstance.java:116) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:211) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:328) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]
> Caused by: org.teiid.dqp.service.SessionServiceException: TEIID40046 VDB "TextEmployeeCombined" version "latest" does not exist.
> at org.teiid.services.SessionServiceImpl.getActiveVDB(SessionServiceImpl.java:269) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.services.SessionServiceImpl.getAuthenticationType(SessionServiceImpl.java:477) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> ... 30 more
> {code}
> # NullPointerException
> {code:plain}
> 11:01:14,928 ERROR [org.teiid.ODBC] (New I/O worker #7) TEIID40015 Unexpected error occurred: java.lang.NullPointerException
> at org.teiid.odbc.ODBCServerRemoteImpl.initialize(ODBCServerRemoteImpl.java:203) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at sun.reflect.GeneratedMethodAccessor190.invoke(Unknown Source) [:1.7.0_75]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_75]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_75]
> at org.teiid.transport.ODBCClientInstance.processMessage(ODBCClientInstance.java:127) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.transport.ODBCClientInstance.receivedMessage(ODBCClientInstance.java:116) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:211) [teiid-runtime-8.7.1.6_2-redhat-3.jar:8.7.1.6_2-redhat-3]
> at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:328) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3581) Add a system function for EDS-DV Server connection
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3581?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3581:
---------------------------------------
We need to be careful here. Embedded / non-AS depoyments will not have the same notion of node id as AS (which looks like it would just be the jboss.server.name system property). Also since it is straight-forward to use a udf for this, are we sure a system function is needed?
> Add a system function for EDS-DV Server connection
> --------------------------------------------------
>
> Key: TEIID-3581
> URL: https://issues.jboss.org/browse/TEIID-3581
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> A user has a 4 node Cluster and would like to get not only the sessionid, vdb and user but the node of the cluster that the user is connected to
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months