[JBoss JIRA] (TEIID-4141) Move REST auto-generate code into in its own module
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-4141:
-----------------------------------
Summary: Move REST auto-generate code into in its own module
Key: TEIID-4141
URL: https://issues.jboss.org/browse/TEIID-4141
Project: Teiid
Issue Type: Task
Components: Build/Kits
Affects Versions: 9.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Move the REST generation stuff into its own module, as this is bringing in whole lot of swagger dependencies and as well others. Will also help if we ever decide to remove this altogether.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-4139) Session/Connection to VDB gets closed after 2 minutes of innactivity
by Jorge Herrera (JIRA)
[ https://issues.jboss.org/browse/TEIID-4139?page=com.atlassian.jira.plugin... ]
Jorge Herrera commented on TEIID-4139:
--------------------------------------
Ok. As you mentioned the load balancer might be the problem, I will work on that side and re-test, then I will update this ticket. Thank you so much!
> Session/Connection to VDB gets closed after 2 minutes of innactivity
> --------------------------------------------------------------------
>
> Key: TEIID-4139
> URL: https://issues.jboss.org/browse/TEIID-4139
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1
> Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
> JBoss Data Virtualization 6.1.0.ER4
> Reporter: Jorge Herrera
> Assignee: Steven Hawkins
> Attachments: jdv-jdbc-config.txt, server.log
>
>
> When setting up a VDB connecting (using jdbc over ssl) to either another VDB in the same server or directly to a RDBMS (Amazon Redshift in this case), if you execute queries one after the other the server works as expected. But if you let the session idle, or just looking at the result set for more than 2 minutes, session gets disconnected with the following message:
> _______________________________________________
> DBCException: SQL Error [08S01]: org.teiid.net.socket.SingleInstanceCommunicationException
> SQL Error [08S01]: org.teiid.net.socket.SingleInstanceCommunicationException
> TeiidSQLException: org.teiid.net.socket.SingleInstanceCommunicationException
> org.teiid.net.socket.SingleInstanceCommunicationException
> SingleInstanceCommunicationException
> org.teiid.net.socket.SingleInstanceCommunicationException
> EOFException
> java.io.EOFException
> _______________________________________________
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-2694) Support for Blob Input in Teiid REST services
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2694?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2694.
-----------------------------------
Fix Version/s: 9.0
8.12.5
(was: 8.10)
Resolution: Done
Labels: (was: Final)
Changed the isAssignable checks and added a little more null handling. It's still not well handled when no response document is returned, but that is a separate issue.
> Support for Blob Input in Teiid REST services
> ---------------------------------------------
>
> Key: TEIID-2694
> URL: https://issues.jboss.org/browse/TEIID-2694
> Project: Teiid
> Issue Type: Enhancement
> Affects Versions: 8.5
> Environment: EAP 6.1 Alpha , Teiid 8.5
> Reporter: Madhu Garimilla
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5
>
>
> We are trying to upload large files as Blobs using Teiid REST service through VDB. Though we are writing the Blob objects to HttpUrlConnection object, it is not received on REST method. As per the conversation in the thread "https://community.jboss.org/thread/232840" Current parameter handling is done through strings and needs be enhanced to support Blob objects.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-4139) Session/Connection to VDB gets closed after 2 minutes of innactivity
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4139?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4139:
----------------------------------
Priority: Major (was: Blocker)
The log does not show any org.teiid.SECURITY context messages indicating that the server is terminating the session. Ensure that you are logging at a debug level on that context as well.
We do see several instances each of:
2016-04-08 11:11:57,313 [New I/O worker #94] WARN [org.teiid.TRANSPORT] TEIID40114 Unhandled exception, closing client instance: not an SSL/TLS record: 000000800003000075736572006a65636f6c656d61006461746162617365006d61726b6574696e675f76646d00636c69656e745f656e636f64696e67005554463800446174655374796c650049534f0054696d655a6f6e6500416d65726963612f4e65775f596f726b0065787472615f666c6f61745f64696769747300320000
2016-04-08 12:48:45,448 [New I/O worker #68] WARN [org.teiid.TRANSPORT] TEIID40114 Unhandled exception, closing client instance: Received fatal alert: certificate_unknown
This is not expected from the Teiid client. More than likely a load balancer is sending unexpected traffic.
Since there are a number of sessions being created and queries after that point in the log it's unclear how that correlates to the exception you've shown in the description. If this could be repeated for just a single session with a correlated client log, that could help narrow in.
> Session/Connection to VDB gets closed after 2 minutes of innactivity
> --------------------------------------------------------------------
>
> Key: TEIID-4139
> URL: https://issues.jboss.org/browse/TEIID-4139
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1
> Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
> JBoss Data Virtualization 6.1.0.ER4
> Reporter: Jorge Herrera
> Assignee: Steven Hawkins
> Attachments: jdv-jdbc-config.txt, server.log
>
>
> When setting up a VDB connecting (using jdbc over ssl) to either another VDB in the same server or directly to a RDBMS (Amazon Redshift in this case), if you execute queries one after the other the server works as expected. But if you let the session idle, or just looking at the result set for more than 2 minutes, session gets disconnected with the following message:
> _______________________________________________
> DBCException: SQL Error [08S01]: org.teiid.net.socket.SingleInstanceCommunicationException
> SQL Error [08S01]: org.teiid.net.socket.SingleInstanceCommunicationException
> TeiidSQLException: org.teiid.net.socket.SingleInstanceCommunicationException
> org.teiid.net.socket.SingleInstanceCommunicationException
> SingleInstanceCommunicationException
> org.teiid.net.socket.SingleInstanceCommunicationException
> EOFException
> java.io.EOFException
> _______________________________________________
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-4049) OData 4 query hangs in test run
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4049?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4049.
-----------------------------------
Resolution: Rejected
It seems that a native thread can't be created and the exception is being swallowed (not in Teiid) and no result is being delivered.
> OData 4 query hangs in test run
> -------------------------------
>
> Key: TEIID-4049
> URL: https://issues.jboss.org/browse/TEIID-4049
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> During the run of:
> org.teiid.olingo.TestODataIntegration.testExpandSimple(TestODataIntegration.java:988)
> The server seems to be in an indefinite wait state:
> "qtp1207140081-380" #380 prio=5 os_prio=0 tid=0x00007f7c94bbb800 nid=0x3642 in Object.wait() [0x00007f7c6a6cc000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:287)
> - locked <0x0000000770e1c130> (a org.teiid.dqp.internal.process.RequestWorkItem)
> at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:313)
> at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:245)
> at sun.reflect.GeneratedMethodAccessor103.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:190)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:260)
> at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:188)
> at com.sun.proxy.$Proxy15.executeRequest(Unknown Source)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:673)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:539)
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:260)
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:73)
> at org.teiid.olingo.service.LocalClient.executeSQL(LocalClient.java:228)
> at org.teiid.olingo.service.TeiidServiceHandler.executeQuery(TeiidServiceHandler.java:347)
> at org.teiid.olingo.service.TeiidServiceHandler.read(TeiidServiceHandler.java:167)
> at org.apache.olingo.server.core.requests.DataRequest$EntityRequest.execute(DataRequest.java:302)
> at org.apache.olingo.server.core.requests.DataRequest.execute(DataRequest.java:245)
> at org.apache.olingo.server.core.ServiceDispatcher.execute(ServiceDispatcher.java:117)
> at org.apache.olingo.server.core.OData4HttpHandler.process(OData4HttpHandler.java:65)
> at org.teiid.olingo.web.ODataServlet.service(ODataServlet.java:50)
> Just trying to run the test or the whole test class in isolation through many iterations has not reproduced this, so I'm logging this for now in hopes that if others see this we may get more details as to when it occurs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-4139) Session/Connection to VDB gets closed after 2 minutes of innactivity
by Jorge Herrera (JIRA)
Jorge Herrera created TEIID-4139:
------------------------------------
Summary: Session/Connection to VDB gets closed after 2 minutes of innactivity
Key: TEIID-4139
URL: https://issues.jboss.org/browse/TEIID-4139
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.7.1
Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
JBoss Data Virtualization 6.1.0.ER4
Reporter: Jorge Herrera
Assignee: Steven Hawkins
Priority: Blocker
Attachments: jdv-jdbc-config.txt, server.log
When setting up a VDB connecting (using jdbc over ssl) to either another VDB in the same server or directly to a RDBMS (Amazon Redshift in this case), if you execute queries one after the other the server works as expected. But if you let the session idle, or just looking at the result set for more than 2 minutes, session gets disconnected with the following message:
_______________________________________________
DBCException: SQL Error [08S01]: org.teiid.net.socket.SingleInstanceCommunicationException
SQL Error [08S01]: org.teiid.net.socket.SingleInstanceCommunicationException
TeiidSQLException: org.teiid.net.socket.SingleInstanceCommunicationException
org.teiid.net.socket.SingleInstanceCommunicationException
SingleInstanceCommunicationException
org.teiid.net.socket.SingleInstanceCommunicationException
EOFException
java.io.EOFException
_______________________________________________
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months